Click here to show or hide the menubar.

Home >  Archive >  2010 >  June >  16

Previous / Next

Bootstrapping a federated Twitwork with annotations?
By Dave Winer on Wednesday, June 16, 2010 at 10:34 AM.

A picture named chairs.gifJust had an idea that with the new annotations feature coming soon in Twitter, we might have the means to bootstrap an Emergency Broadcast System.  permalink

Imagine if every tweet included info about where to find that users' status messages if Twitter is down. It could simply be the URL of a feed. Unless Twitter went down it would just be stored by your client. But if Twitter should go offline, at least you know how to find out what's going on with at least some of your associates. permalink

The point is that with annotations we have the ability to create new ad hoc flows of information, and can possibly use it to make Twitter more reliable. permalink

It's like having a place to meet your friends after a ballgame, or part of being prepared for an earthquake (I just landed in SF). You arrange for a meeting place if the normal lines of communication go down. You use the normal lines to transmit the place you will be found in cast the line goes down.  permalink

I guess it's something like DNS, where you always specify two servers and two hosts. If everything is working you only need one. But the network is designed to work even if everything isn't working. permalink

Of course it's this line of reasoning that led me to the conclusion that Twitter should just run off DNS, and Twitter should be the Verisign of this network. But that's another story.  permalink

RSS feed for Scripting News
This site contributes to the community river.

© Copyright 1997-2012 Dave Winer. Last update: Wednesday, June 16, 2010 at 2:32 PM Eastern. Last build: 8/26/2012; 5:47:52 PM. "It's even worse than it appears."

RSS feed for Scripting News

Previous / Next