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
No, that’s what you’re not getting. It really is the fragility of the interface that gets you the “It returns content by default, hope you’re smart enough to check the error code, what do you mean nothing did” surprise not surprised dynamic
Again, that "it returns content by default" is a *consequence* of the streaming design of the interface. It would be *exactly the same* as a shared library, with that design constraint. You'd end up with a "more data" callback getting called before the main entry returns error.
I mean, look, you have the same failure mode all over the place so the bug is in the interface. API plus developer equaled insecure code. Thems the breaks. You could make a case the streaming API is the issue and not pipe vs shared lib. But then the streaming API deprecates.
There’s a mismatch between API expectations we have a sufficient sample size to witness.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
