@zachleat can't be an accident right

As far as I can tell, I've successfully deleted all my tweets on the bad site, and yet, my profile claims I have a specific number of posts that I can't help but assume the site's owner has set as a *hilarious* minimum count, as he is famously so funny

@matthiasott @luca Seems to work great. Deleted about 14k so far here

@matthiasott working for me too! thanks for that

@matthiasott no but that looks like a good one to try because I'm noticing very old tweets are still findable via google even though they don't show on my profile. That script looks helpful in that it uses your archive for IDs and avoids the fetches

@matthiasott just a seemingly well-regarded script I found in some blog post that appeared to do what I'd expect... fetch latest 20 at a time, post a delete to each ID, do it again. It hit the rate limit after a while though.

I can't tell if I was able to delete all of my tweets successfully or if my account is just banned from fetching its own timeline now... (?) what stupid website

apparently when you delete 4k tweets per hour you get put in the api penalty box for a bit.

@zachleat 7 overtons imply the possibility of 7 undertons

@zachleat that's... uncommonly fast

I have a hunch that the most effective web performance teams will spend less time fighting fires and more time being Smokey Bear.

The more I tune into JS framework discussions the more I’m concerned at how few developers seem to be concerned with how their work is actually delivered. Browsers are optimized to receive websites as HTML first, yet frameworks taught a generation of developers to build blogs like they are executable files to load & boot. I was asked twice this week if I think server components are a good idea (?). Yes! Create react app was a poor fit for most sites. Stop building the Web like it’s an App Store.

I've audited a lot of large-scale server-rendered single-page-app sites in the past several weeks and it's clear that 1: frameworks finally serving HTML up-front is a welcome (long overdue) change, and yet 2: chasing it with a typical 1-to-6+ megabytes of "rehydrating" JavaScript means a lot of people are getting a site that may look usable but feels very broken. You can find them in the p25 who aren't getting "good" core web vitals.

@zachleat Given that perceived performance techniques are all about making a page appear usable before it actually is...

@zachleat Yes. I recall using a similar metaphor around 2013 about the electricity in a home being the JS and that the "shelter" part of the home should work well regardless of whether the power is on and people actually got pretty upset, but that was back when folks were writing posts saying progressive enhancement is dead.