You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Parsing 1 GB of JSON/XML can be different than opening it in text editor. Text editor doesn't have to parse the text. Sure, there can be syntax highlighting, but it can be optimized to be much faster than parsing.
The cluelessness of people giving examples like they're good reasons for all this bs and not realizing that they're exemplifying the problem is deeply sad.
I honestly don't understand what you mean by that? What I said was that opening 1 GB JSON file in text editor could in theory be faster than actually parsing it into a tree because it can make do with less work. In no way did I mean that having 1 GB JSON file is a good idea.
It should take approx 100ms to parse a gigabyte of JSON. The timeframe that you, and most programmers think is an acceptable amount of time for any computation is off by several orders of magnitude.
"Opening a text file in an editor is faster than parsing" - Objective argument. Response: No arguments, no explanations. Not helpful, not educational. Just a cheap stab at someone. You just made twitter worse doing what people hate about twitter.
Thank you for acknowledging what I couldn't articulate to even myself 
I was kinda surprised about many people negatively piling on my comment, when I didn't even understand which problem I'm a part of 
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
New website: 
