Are these all teenagers?

It just means you get different kinds of assholes who are better at navigating around the CoC or even weaponizing it.

Yes but it was always this way. Any organisation with rules can suffer from rules lawyers as a lot of people who have tried to contribute to wilipedia/serve on a committee of a voluntary organisation etc will testify.

Perhaps but in this case the style does make it harder to read the substance.

I take the opposite approach: wash everything on the default setting and whatever survives (almost everything) is now confirmed safe for that setting. Keeps things simpler and has the advantage that you can cut of those scratchy labels that are always attached in the most uncomfortable places possible.

Darwinian washing. I like it.

If I have to choose anything but the default wash and dry setting, I'm not worthy of wearing it.

Webp is also an incredibly bad animation format since it drops most of the inter-frame compression features of the video codec it was derived from.

Video files are not supported in <img> tags.

Do browsers support progressive enhancement from gif to animated avif without javascript? The royally messed that up for animated webp.

Yes, by using the <picture> element with <source> elements declaring the individual formats with the last one being a regular <img> with the gif.

Or you could use content-negotiation to only send avif when it's supported, but IMO the HTML way with <picture> is perhaps clearer for the client and end user.

I think the webp problem was due to browsers supporting webp but not supporting animation, transparency or other features, so content negotiation based on mime types (either via <picture> or HTTP content-negotiation) did not work properly. Safari 16.1-16.3 has the same problem with AVIF, but that is a smaller problem than it was with webp.

Unfortunately browser vendors didn't want to support silent looping videos in <img> tags so gif stays relevant.

Use better software - ideally open source software so that in the worst case you can just add support yourself.

For many relevant specs you can find "draft versions" that are essentially the final version without the official stamp on the open web so there isn't that much of a need.