I get the snark, but "page has to load in x time on expensive device in expensive city"... where is the human? Your audience isn't a phone.

I know I've said this a lot, but I think about the NHS digital design standards all the time, about that presentation where their lead designer talked about finding agent strings for devices like the Playstation Vita and Opera for the Nintendo DS in their logs. About how the NHS site had to work for those people too, no matter what.

https://wandering.shop/@fugueish/116695409129543894

"Your use case is, there's a fourteen year old in an emergency room at 3 AM. English is their second or maybe fourth language. They have a battered school Chromebook or a hand-me-down Android device that was the cheapest thing on the market six years ago or a PS Vita their parents don't even realize has a web browser, and they're trying to educate themselves in the middle of the single most terrifying night they've ever experienced. Your site needs to work for that person at that moment."

@mhoye How great that we've re-implemented early 2000s web browsing.

"What do you mean, you're not on this OS with these things installed using this browser with these extensions on this monitor at this resolution? It works fine for me."

@steevmi1 @mhoye I was worried about Cloudflare Turnstile on this front. For disabled people like me, it's finally an accessible CAPTCHA that we can actually use, and Cloudflare has been tracking bots on the internet for ages, so if anyone can identify them it'd probably be them. But I always did wonder, how much of this works on something that isn't modern Gecko or Chromium?
Cloudflare Turnstile requiring fingerprintable WebGL