Linked by Thom Holwerda on Sun 25th Mar 2012 21:28 UTC
Permalink for comment 511917
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



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. )