How Web Standards Work 1. design a flawed API (it's fine! APIs are hard) 2. ship it in the most-used browser, despite objections 3. get cross-browser working group to fix the API 4. oops, too late, that would break the webpic.twitter.com/IuU6Xxzilv
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
BTW, does it still hold that to become approved by standards body, feature needs at least two independent and interoperable implementations?
Yeah but usually the implementation happens ***after*** there's broad consensus.
See TC39 (which has superb leadership, thank you sincerely, @BrendanEich), particularly Stage 3, which is when engines usually start implementing new features.
and then we are getting into "typeof document.all == "undefined" situation, because some browser vendor was way too eager ship their innovation
That's actually a pretty fun example. Without document.all, DHTML would not have existed, and the web would likely never have become a successful app platform! document.all is a pretty great example of putting users and web developers ahead of implementers and theoretical purity.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.