News for hackers. Stuff that matters.
Re:Is a federated Twitter even possible? by mbreese on Friday August 24, 2012 @04:05PM (#4429373)
Why couldn't the user decide how to view message?

You could easily allow a user to see messages ordered by "send time" or "received time". You could even add an "unread" flag to messages, so that unread messages show up first, then migrate to their proper locations in order.

Ya know... kinda like email.

Re:Is a federated Twitter even possible? by sp332 on Friday August 24, 2012 @04:07PM (#4429385)
Sure, of course they could. The point is that you can't do both at the same time.
Re:Is a federated Twitter even possible? by rabidsnail on Friday August 24, 2012 @04:16PM (#4429428)
You can if you use vector clocks.

@sp332 You can prevent that by buffering messages. The less you tolerate messages appearing in-between messages you've seen before, the more you buffer. If the latency between your host and the host of someone you follow is high enough that it's taking more than a few seconds for you to get the message, they're effectively down. Late is better than never.

Re:Is a federated Twitter even possible? by sp332 on Friday August 24, 2012 @04:25PM (#4429454)
Vector clocks are only a partial ordering. You'd still have old events popping into the middle of your timeline.