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
Given that chrome has a near monopoly don't you think you should maybe not ship something as stable before other browsers have it to not reinforce the monopoly?
FWIW this is how the web has ALWAYS evolved. Almost all APIs we use today we're shipped in the dominant engine prior to a standard being ratified (IE, Netscape, WebKit, now chromium). JavaScript language is a notable and impressive counter-example.
Standards processes are not designed to arbitrate feature quality, and disagreements within standards bodies often bear little overlap with actual developer concerns and are usually silent on deadweight loss costs. So we ask developers for feedback, e.g. through Origin Trials.
BTW, does it still hold that to become approved by standards body, feature needs at least two independent and interoperable implementations?
How does an *"experimental feature not adopted by a standards body shipped in a single browser to possibly gather developer feedback with multiple objections to the implementation and the API"* become *"it's a standard now lol"*? Asking for a friend
Another question for a friend: how does this whole issue fit into Part 2 of Effective Standards work? https://infrequently.org/2018/06/effective-standards-work-part-2-threading-the-needle/ …
I apologize to be this direct, but this is a literal definition of strong arming a conversation. You realize this, do you? The conversation is about standards of the web and you're abusing your position as the leader to secure your future and lock features.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.