One mystery solved, *so* many more revealed: https://twitter.com/slightlylate/status/1184958694523453440 …pic.twitter.com/qHj0uyb9lh
Chrome Project
& Web Standards TL; Blink API OWNER
Named PWAs w/ @phae; probably making her
DMs open. Tweets my own; press@google.com for official comms.
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
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
One mystery solved, *so* many more revealed: https://twitter.com/slightlylate/status/1184958694523453440 …pic.twitter.com/qHj0uyb9lh
It uses Promises...which we designed, in part, for the `fetch()`...which we designed, in part, because we didn't want sync tasks within Service Workers.
I am not aware of a browser that supports arrows and promises but doesn't have `fetch()`.

*PERHAPS* the developer said to themselves "I don't want to include a full fetch polyfill" (although the same file pulls in rando core-js polyfill this-and-that) and leaned on Babel or whatevs to desugar arrows/promises?...on a site that loads more than 850KiB of (compressed) JS
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
Hrm, curious to see the bug. Either way, you can still eval JSON off-thread using fetch API.
The off thread eval sounds like a big upside, I had no idea XHR forced it to happen on-thread... good to know the next time I use JSON
It's a side-effect of JSON.parse() being synchronous.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.