DISQUS

Tom, in the last 48 hours the Twitter API was spitting out tweets at random causing my copy of Twitterrific to fill the timeline "further down" inline with tweets I already read instead of showing new tweets on the top. That was annoying and I asked if there's a fix. I understand that there is no "received timestamp" in tweets, but Twitterific could very well record the time it got a tweet from the API.

Of course it does.with the api lagging twitter clients like twitterrific get tweets out of sync and out of order.

Technically, yes. But I (and I heard that from friends and followers, too), that it feels like a huge chat room, only that my real-life student friends don't see what I say to the indie mac devs and vice versa. But from my POV, it's all the same.

I basically agree with dave here.

> If I don't want to listen to someone on IRC, my options are to get off the channel, basically unsub from everyone, or find a way to block one person (if there is a way).

There's /ignore <nick>


>But even so, people will assume everyone can hear everyone else.

It's kinda like that in Twitter, too. Or do you have the distinct notion of you talking to an audience that chose you?

Seems to be easy to do with CouchDB and its replication system

@Regin Too many keys :p

keep 'em coming!

Woha! This is cool, thank you very much.