Linked by Thom Holwerda on Sun 25th Mar 2012 21:28 UTC
In the News A few months ago, I wrote an article about comments, in which I said, among others things, that Twitter can never replace comments because not only is it effectively a one-to-one communication channel, Twitter messages are also far too short to foster any form of coherent conversation. Over the weekend, a silly link-bait story illustrated my point perfectly.
Thread beginning with comment 511879
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: 140 characters
by Doc Pain on Mon 26th Mar 2012 04:45 UTC in reply to "140 characters"
Doc Pain
Member since:
2006-10-08

I find twitter to be a complete waste of the web. I actually like the concept, but Twitter itself is stupid. This is the internet, not a cel phone messaging system. There is no reason to limit people to 140 characters at all.


Ah, I see that's why a single "Tweet" requires 2 MB of web traffic. That's 14 kB per character, or "15,000 for one", assumed that we are talking about 1-byte characters (recalculate for 2-byte UTF-8 encoding). :-)

http://mike.teczno.com/notes/bandwidth.html

Reply Parent Score: 5

RE[2]: 140 characters
by cyrilleberger on Mon 26th Mar 2012 07:01 in reply to "RE: 140 characters"
cyrilleberger Member since:
2006-02-01

Ah, I see that's why a single "Tweet" requires 2 MB of web traffic. That's 14 kB per character, or "15,000 for one", assumed that we are talking about 1-byte characters (recalculate for 2-byte UTF-8 encoding). :-)

http://mike.teczno.com/notes/bandwidth.html


What is amazing is the 1.6MB of scripts to display those 140 characters, three times as much more than OpenStreetMap that allows you to navigate the world...

Reply Parent Score: 4

RE[2]: 140 characters
by Bill Shooter of Bul on Mon 26th Mar 2012 13:38 in reply to "RE: 140 characters"
Bill Shooter of Bul Member since:
2006-07-14

Reading that link, its obvious you're grossly exaggerating. If you are talkin about the entire web page used to display a single tweet, you're right, If you are talking about the json required to send a single tweet, you're very wrong. Its quite minimal overhead. Aprox 50 bytes over head per tweet, independent of tweet length.

( Plus you do know that UTF-8, emphasis on the 8 there, only uses multiple bytes per char for non ascii chars? So, if you are typing in english its exactly the same as ascii one byte per char. )

Reply Parent Score: 2