A friend came up with a good idea: Twitterbacks, Pingbacks for Twitter. I suggest that Summize jump on that, but that's because I like Summize more than the others.

Primarily because it will take a live, up-to-the-second, service that has made its mark with being a live, up-to-the-second service and spits on that entire concept. If you add decentralization, meaning multiple servers with copies of the same data, what happens is that you no longer have a live service. Depending on the number of servers you have in your swarm, the time it takes for information to be completely, identically cloned increases x-seconds per server in the swarm. And the number of servers that Twitter would need for an effective approach would make the cloning process take at least 30 seconds*. And that's how long it would take for you to be sure that every person on your list has your latest tweet. Now I answer questions I was never asked. (more…)

As of this post, Twitter is still down. And barring server problems, I place the blame on Ruby on Rails. I fucking hate RoR, and all projects that use it are marred in failure. I just wanted you to know that. Later on, I'll make a longer post about why I don't like RoR, but for now I have work to do and have wasted enough time on Twitter.

I was doing a little something with the Twitter API, and noticed the page had been removed for whatever reason. I found it in Google Cache. And since you know how finicky GC can be, I've included it in this post. After the beep. (Click on more to hear the beep) (more…)