Blackberry Support

[justducky2204]

Title
Blackberry Support

Short, concise description of the idea
add Blackberry support for LJ Mobile

Full description of the ideaBlackberrys aren't just for business users anymore. They are smaller and less expensive than most Palm and Windows Mobile devices, meaning that there are a lot of us out there using Blackberry devices that would love to be

Comments

[kou]

Why do the work when you can exploit the free software community to do LiveJournal's work for free?

LiveJournal is already open source. Just add an intuitive API for certain features to talk to LiveJournal and the applications, which will then be much easier to write, will follow. XML Web Services is likely the way to go.

Already, LiveJournal supports Blogger and Atom, and LiveJournal's FOAF format has attracted interest in users who are datamining for social network graphs. You could even do it as a LiveJournal proprietary "expansion" to certain Atom fields, e.g. implementing support for LJ's security framework. Not to mention it'll pave the way for more sophisticated tools like a downloadable layout design program (pleeeeease!) and can be leveraged when including more features that would be too complex to implement in Web Interface.

The most obvious place to start is with entry posting. Then expand it into Friends Page, Communities, Community admin, Friends list, FOAF data, Inbox, Notifications, Journal Settings, etc.

My wish list:

I'd like to be able to mark Friends Page entries as "read" and skip them later.
Direct upload to LiveJournal scrapbook + posting from phone's camera = paid accounts $ revenue for LJ.
Push notifications to mobile: you can do this with raw IP, UDP or easily with Blackberry MDS. This would be an improvement over text messages, especially if the userpic appears on the phone's screen and a message preview like "(userpic) bradfitz just commented in your entry".
Please add a device login management system so our LJ password is not stored in plaintext on the mobile device or desktop client. The first web service call that logs in should generate a device specific shared-secret association key and register the "Device name". Then we can delete a device if we lose it without changing passwords everywhere.

Bandwidth reduction features through selective download of previews, etc. Need to be able to specify desired data set as an argument in the call. Should have 3 preview levels at the least, such as: "Download User's Community Names", "Download Specific Community's Recent Entry Titles" and "Download Specific Entry Text + ljcuts". Bonus for "Download first 60 characters preview of the entry". Userpics, if transmitted, should be scalable from 100x100 to 50x50 and 25x25 on the LJ serverside, if possible.