One mystery solved, *so* many more revealed: https://twitter.com/slightlylate/status/1184958694523453440 …pic.twitter.com/qHj0uyb9lh
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
maybe it's because fetch() was (is?) broken in chrome and i'm sure probably in other browsers. specifically the cors implementation was just silently busted, which forced me to abandon it
"accept a value from the spec but silently ignore it" is not something i am happy to see in a shipping release channel browser, even if i can find documentation for that bug on monorail
Am I to understand that fetch() is better for performance than XHR in modern browsers?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.