Remember read/unread status of tweets

I know this one's already assigned, but it seems Ed already has about 20 other things with higher priority assigned - I figure it's easier to review a diff and merge.

I'm not sure if this is the approach you'd want to take - if maybe it goes against any optimizations or whatnot, but here's a simple solution. I basically added a db query called Spaz.DB.isRead(entryId), which returns boolean. Then, when parsing the timeline, it calls that query and sets a "read" parameter on the tweet (data) object, and finally in the template, it sets the html class to "new" or "read".

And that's enough spaz for me tonight. It's been fun!

Mark (enobrev)

MARK!

This is great!

I think for now, this gets us there. Ultimately we're using a
schemaless lawnchair-based setup to store message data, but this may
be quite adequate for now. Small steps.

One potential issue here is that messages aren't namespaced. If a user
switches between Twitter and StatusNet, for example, there could be
conflicts.

for now I think I'm gonna patch this, though. Big thanks for stepping up!

This one is kinda working okay, but the synchronous connection is slowing us down a bit. we need to refactor the approach some before 0.10

In git spaz-desktop-air master does not remember marked as read on RT, nor DM tweets.

Neither does Mark on the "Tweet's you've sent" View.

Yes, the saving of read state is mucked up, and honestly it should
probably be almost entirely redone. not sure right now whether to
patch up what we have to redo it all. Probably the former.

[bulk edit]

[bulk edit]