News for hackers. Stuff that matters.
Re:Is a federated Twitter even possible? by sp332 on Friday August 24, 2012 @03:09PM (#4429123)
If it was impossible for a federated network, it would also be impossible for Twitter. They can either guarantee that messages only show up at the top, or that messages always show up in order (meaning older posts get inserted into the middle of the timeline, as you eventually receive them).
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.
Re:Is a federated Twitter even possible? by dwineman on Friday August 24, 2012 @03:33PM (#4429232)
Right, but since Twitter manages all of Twitter's servers (and the dedicated low-latency network via which they're presumably all connected) they can satisfy both of these constraints without sacrificing the third (immediacy). I'm speculating here, but I think that's why it takes a few seconds to post a tweet: it's propagating across the internal federation so that all the nodes have it before it "goes live."
Re:Is a federated Twitter even possible? by sp332 on Friday August 24, 2012 @03:37PM (#4429258)
To be specific, your tweet is not timestamped when you send it. It only gets an "official" timestamp when twitter decides to give it one, after receiving it. That means Twitter arbitrarily sets the timestamp whenever they get around to shoving it on top of your feed. So they do have the problem of tweets arriving out of order (due to network latency etc), they just hide it by rewriting timestamps!

eta: I admit this is a smaller problem for a centralized service than a federated one, but I would argue that it can work "well enough".

Re:Is a federated Twitter even possible? by fleitz on Friday August 24, 2012 @07:09PM (#4430206)
How is twitter immediate when it's down?

Twitter doesn't solve the immediacy problem with any hard guarantees either.

Most of the time email is on par with twitter.

Re:Is a federated Twitter even possible? by dwineman on Friday August 24, 2012 @08:03PM (#4430459)
Huh? When Twitter's down, no one can post, so immediacy is meaningless. This is like saying "my car's faster than yours after yours hits a tree."
Re:Is a federated Twitter even possible? by fleitz on Friday August 24, 2012 @08:07PM (#4430474)
Except that twitter does go down, so if you had a distributed car that was incapable of hitting a tree it would be an advantage.

The situ with email is that at any moment the system is up but individual nodes may be unreachable or delayed, conversely if twitter is up all nodes are reachable in constant time, but if it's down all nodes are unreachable.

In real systems these two properties are mean virtually the same thing, at any given point in time your party may or may not be reachable with a given latency.