When you try hard sticking to Boring #Haskell and then a new GHC comes out
I didn't like that "death by fancy autocorrect" meme at first, but then I've begun to be more accepting.
The idea of humanity auto-correcting itself (out of existence) by means of war and/or gross negligence has a certain ring to it.
Another batch of humanity auto-correction risks spotted
My own hypothesis is that the harmful thing is "engagement maximization" and not "social media", and that you could have engagement-maximization algorithms applied to other things and make them more harmful, but I don't have hard data to support that and I don't really even know how to start going about gathering it, or falsifying this hypothesis.
I acquired (with help) a killer audio cassette digitizing rig, and then IMMEDIATELY had to spend over 2 months digitizing 90+ cassettes from the 1999 Game Developers Conference (via a slow-and-steady workflow that got the job done without being too disruptive to any other work I was doing).
So, here we are, it's done. Go enjoy 70+ hours of presentations about all aspects of game making and producing, in 1999.
https://archive.org/details/1999_Game_Developers_Conference_Audio
Looks like this is the reason why Opus, the next-gen Xiph codec, was failed to overtake its predecessor Vorbis despide being pareto-superior to it.
The author of `stb_vorbis.h` that gets shipped far and wide found that they can't make the same for Opus due to licensing shenanigans.
https://nothings.org/stb/stb_opus.html
Mastodon monoculture problem
Toots as he pleases.