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
IMO this isn't a valid excuse for a bad user experience even if it's a valid reason. From the user's standpoint, the app owns the entire experience. Every company I've worked for has deployed numerous workarounds for hardware bugs instead of saying "yolo, it's hardware's fault".
It's not uncommon for cloud vendors to get hardware firmware in order to fix bugs, but twitter can't fix bugs in open source browsers? It might be the right business decision to ship an app where text input is broken but, IMO, that doesn't somehow make it the browser's fault.
I agree! Not an excuse, just providing historical/technical context for the curious!
IMO the bugs are rooted in fundamental design flaws in the browser editing component. There was a proposal to redesign the APIs, but the w3c discussion ran into an impasse that is too complicated to fit in this tweet.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
