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
My kingdom for someone who can solve the signal-to-noise problem with JS error reporting in browsers. Right now it's a nightmare separating errors you've caused from errors caused by plugins, weird browsers, scrapers trying to run JS, etc.
Honestly I think the only reasonable solution is to minimize the amount of JS used that production error reporting isn't necessary
You can't build something like Execute Program that way, though. Or, well, you can, but it involves a round-trip to the server for every single action the user takes, hitting a backend VM each time. Huge amounts of operational complexity to avoid client-side JS.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
