2 ms·
Yep, twitter is not the classical realtime taught in school. He probably would have done better by referring to it as "everyone in the same living room comment
by protomyth 14y ago
Yep, twitter is not the classical realtime taught in school. He probably would have done better by referring to it as "everyone in the same living room commenting on the TV". Its timeliness is directly linked to how many people are at / watching the same event. The tweets about a NASCAR race or the plane coming down in the Hudson really would be a pain / confusing if received hours later. For a lot of stuff, this doesn't matter so much (like e-mail).
"Pause and Consider" is pretty much a lost concept in the online news world. Look at the Apple screw fiasco for a point when the repeaters didn't. Maybe having a distributed network of sorta timely servers wouldn't be such a bad thing. I seem to remember debates happening fairly rapidly on USENET.
- thinkingisfun 14y agoThere ought to be a way to bring IRC into all this..
- ChiperSoft 14y agoExactly, IRC networks have been realtime AND decentralized for decades, they even solved the redundant data problem.
- mbell 14y ago> Maybe having a distributed network of sorta timely servers wouldn't be such a bad thing. I seem to remember debates happening fairly rapidly on USENET. I believe this is what twitter does. At least that is the impression I have as a user. Having 'watched' a number of live events on twitter I tend to get a floods of 10-30 tweets at a time all in the same language. I presume this means there is a delay related to geographic servers packing up multiple tweet for replication.