Thomas Steiner 🦖🎗 @tomayac@toot.cafe

Despite having been killed what feels ages ago, this conserved (stale) copy of Google Reader feels surprisingly fresh design-wise:.
RIP, Google Reader, you’re missed. 😢 @Feedly@twitter.com has mostly replaced Google Reader for me, but I still feel sentimental. https://twitter.com/somebitsLinks/status/1013842506025394177
RT @somebitsLinks@twitter.com Google Reader time capsule: Mihai saved away a copy of the code plus a data snapshot to run it http://dlvr.it/QZDyv2

RT @paulcalvano@twitter.com: Are larger pages more likely to be slower? And what can you do about page bloat on your site? I correlated page weight to real user performance data for more than 1000 sites using @ChromeUXReport@twitter.com and @HTTPArchive@twitter.com. Check it out here - https://paulcalvano.com/index.php/2018/07/02/impact-of-page-weight-on-load-time/

RT @mxbck@twitter.com: Did you know you can use the Network Information API to make a website adapt to different connection speeds? 2G/3G: <img>, 4G: <video>

✏️ New Post & Demo: https://mxb.at/blog/connection-aware-components/

RT @igrigorik@twitter.com: best practices for `localhost` TLS certificates: http://bit.ly/2tKCFIz — great tips, courtesy of @letsencrypt@twitter.com.

RT @HTTPArchive@twitter.com: 📈 The 2018_07_01 crawl running today is the first time we're testing over 1 million URLs.

It's a stress test of our infrastructure so let's hope it goes smoothly! 😬🤞

Cool blog post by @kosamari@twitter.com on the subtle differences between `input.onchange` and `input.oninput`/`input.onclick`:.

I think we need native `on{event}debounced` and `on{event}throttled events (like in @AMPhtml@twitter.com: https://www.ampproject.org/docs/interaction_dynamic/amp-actions-and-events).

(CC: @paul_irish@twitter.com) https://twitter.com/kosamari/status/1012781658595057664

RT @kosamari@twitter.com 📣Part 2 of "It always starts with messy code"
🔗https://kosamari.com/notes/is-change-committed
📚Read on for annoying browser variance on `change` event & find out what is considered browser "bug"

…but it is mostly monologue on when I got message from @paul_irish@twitter.com & how I tried to save my butt 😂

RT @HTTPArchive@twitter.com: With 200TB of data in HTTP Archive's BigQuery repository, sometimes your analytical queries get really BIG.

This walkthrough by @rick_viscomi@twitter.com shows how to ensure that your queries don't time out.

Interesting read even if you don't need to query 50B rows!
https://discuss.httparchive.org/t/really-big-queries-on-bigquery/1397

RT @gaddafirusli@twitter.com: Finally @tryshotsnapp@twitter.com is now launched on @ProductHunt@twitter.com 🎉. Make sure to give it a shot ⬆️ https://www.producthunt.com/posts/shotsnapp

In my timeline this article https://lwn.net/SubscriberLink/758159/f1f631e1535ab9d6/ about @python@twitter.com 3 is making the rounds. Honest question to people in the community: In the JavaScript world, people go the extra mile with transpilers like @babeljs@twitter.com just to use the latest and greatest. Why not in Python? 🐍

So far we seem to have general positive feedback on the proposed Boolean context media query (https://www.w3.org/TR/mediaqueries-4/#mq-boolean-context) to solve 🔙 #backButtonGate:
@.media navigation-controls {
#backButton {
display: none;
}
}
👉Any more feedback, please chime in: https://github.com/w3c/manifest/issues/693 https://twitter.com/ChromiumDev/status/1012065260625383425

RT @ChromiumDev@twitter.com Not all PWAs need a 🔙 button, but some do.
Depending on the `display` mode, not all browsers, 🖥/📱 OSs, or devices show or have one. We're thinking of a Media Query to find out, so you never have 2 (screenshot) or 0 buttons, when you need 1. Opinions? 🗣 https://github.com/w3c/manifest/issues/693

Hackathon task at the #GoogleWebDevDay in @GoogleDE@twitter.com Hamburg: nothing less than building @YouTube@twitter.com with ⚡️ @AMPhtml@twitter.com. Here’s my poor-ish tutor example: https://tomayac.github.io/amp-tube/ (focus was on @____lighthouse@twitter.com 3.0 score). People hacked together some amazing apps!

RT @samthor@twitter.com: fastgif, and how it's done to parse GIFs fast on the web with Web Assembly: https://dev.to/samthor/fast-gif-parsing-on-the-web-with-wasm--wuffs-48l4

RT @zeratax@twitter.com: @aemkei@twitter.com @FakeUnicode@twitter.com turned this into a FIGlet font:
https://github.com/ZerataX/figlet-moonfont

RT @ahopebailie@twitter.com: The @w3c@twitter.com Payment Handler API is coming to Chrome. Kudos to @Google@twitter.com for supporting an open ecosystem. Hoping @Microsoft@twitter.com and @Apple@twitter.com follow soon behind. (@mozilla plan to implement in @firefox@twitter.com when roadmap allows)

Thanks @justmoon@twitter.com for the help writing this: https://medium.com/coil/standardizing-payments-with-the-payment-handler-api-1bb8cefa702d

RT @samthor@twitter.com: Decode GIFs 2x as fast using Web Assembly:
https://samthor.github.io/fastgif/fastgif.html
(those times are decompress/parse/build ImageData)

RT @ChromiumDev@twitter.com: Not all PWAs need a 🔙 button, but some do.
Depending on the `display` mode, not all browsers, 🖥/📱 OSs, or devices show or have one. We're thinking of a Media Query to find out, so you never have 2 (screenshot) or 0 buttons, when you need 1. Opinions? 🗣 https://github.com/w3c/manifest/issues/693

Anyone remember when #FollowerFriday #FF was still a thing? @jennylg@twitter.com has collected some highly knowledgable people (and me) and their particular fields that you might want to follow, and this on a Thursday… 😱

We're hiring for a Google Developer Advocate position with a special focus on ✨ Web Assembly ✨ (#WASM): https://careers.google.com/jobs?jid=4017740033?!t=jo#!t=jo&jid=/google/developer-advocate-web-assembly-google-building-41-1600-amphitheatre-4017740033&. Ping me if you're interested.