The resistance to designing web APIs with the possibility of injecting user consent at a later date is a source of huge frustration for me.https://twitter.com/KrauseFx/status/905822185284972546 …
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
I'm guessing there is no chance of turning back time on this API?
Best retrofit here is to gate access via permission.request(), but Mozilla 
@cramforce’s law: “Every JavaScript API will eventually be asynchronous (So you might as well start there).”
Sync -> async = big refactor Async but fast -> Async and slow = often transparent.
https://www.w3.org/TR/generic-sensor/ … probably do a better job at mitigating these issues. Luckily they go original trial in Chrome soon cc @KrauseFx
Feedback welcomed when it launched https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/2zPZt3watBk … . There is still time to change stuff.
Hm, that fruit-flavored vendor sounds very familiar
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.