There seem to be hard cuts in search returns at 5 and 10 years, it's been really difficult to find anything from before 2012 without incredibly specific searches. Lots and lots of link rot too so it's hard to say how much of that is google/bing/etc.

The folding@home client, for example, is written in C with a "does everything" library (called cbang if I recall correctly). The library only uses sockets with AF_INET and thus it doesn't work even with AAAA records..

WSL2 famously doesn’t support ipv6 (because of NAT) which is mightily annoying.

Why is NAT a problem here? IPv6 supports full NAT (no matter that the basic idea of ipv6 is "no nat").

The prerelease finally supports ipv6: https://github.com/microsoft/WSL/releases

Docker's support for IPv6 is really poor. Basics are still gated behind the "experimental" flag, and there are bugs that have been open for years preventing very common configurations from working.

It don't even support dynamically assigned ipv6 address. And ipv6 prefix need to be hardcoded into config. And even worse , ipv6 address is bounded directly to the container at creation time. If your ip changed for whatever reason. Best you can do is scrap the container and make a new one. I would say keep it experimental at current status is a good decision. It's simply not usable currently.

Colima on mac is struggling with ipv6. Not sure what component is responsible, but I have been unable to connect ipv6 hosts from colima containers.