Great talk from Jake Archibald about how the browser event loop works. This stuff can be really hard to grok, but his visualizations are great. https://youtu.be/cCOL7MC4Pl0
For Mastodon, we added an explicit user setting for "prefers reduced motion" (https://github.com/tootsuite/mastodon/pull/5393), but this is cumbersome and isn't scalable across the entire web. Nobody's going to configure NYTimes and The Guardian and every other website to do this.
Imagine if users could just do a one-time setting in their browser, and have a reasonable expectation that websites would honor this setting. And imagine if web authors could just use a single CSS media query to support it.
It's been neat to watch PWAs go from this weird thing the Chrome team was pushing, to a handful of "hello world" apps, to some impressive apps for emerging markets like Flipkart and Konga, to a mainstream thing that all browsers are embracing and big players like Twitter and Instagram are building for as well.
BTW fun fact: every Mastodon instance is its own PWA. 😁
One neat thing I noticed about writing e2e tests: it kind of forces you to get a11y right. If something isn't observable for your tests, it probably isn't observable to an AT.
Centralized systems will always be more convenient to use than decentralized systems. Maybe the trick is rebranding the decentralized alternatives as a "hobby" or "lifestyle choice."
WFH today (I'm a software developer), and my son, who has taken an interest in "functions and variables" comes to ask what I'm currently doing. This is the exchange:
Son: "Hey dad... whatcha doin now?" Me: "Well, the last thing I did... see how that has a period?" Son: "Yeah" Me: "See how that doesn't?" Son: "Yeah" Me: "Well, it shouldn't have one, so I removed it" Son: *pauses for a moment*...Then, thoughtfully: "And you get paid for this?"
@Wolf480pl@gcupc This is also a thing that browsers do, yeah. Although it's less about "worst-performing JS" and more about "stuff the user is probably not interested in right this very moment," e.g. background tabs, cross-origin iframes (ads), etc.
Every browser has different mitigations in place for this, but a good place to get a feel for what's been implemented is the "interventions" repo: https://github.com/wicg/interventions
Unfortunately a lot of the problems are low-level: subtle inconsistencies between implementations, unspecced behavior, "living specs" that update too fast, etc. Luckily that's slowly getting better too: https://www.youtube.com/watch?v=ipfPyM-Kwyk I'm cautiously optimistic. 🙂
Yo admins! In preparation for a better joinmastodon.org sign-up wizard, https://instances.social directory now lets you set a category for your instance, in the admin area.
The categories are: art, music, books, activism, sports, games, tech, academia. It's ok to not have a category, too, like for example octodon.social is just a general purpose instance. But if yours is themed, you better categorize it.
If you think a crucial category is missing, tag @TheKinrar