To be clear, I don't want to tunnel IPv6. If something should be treated as a second class citizen, it's IPv4, not IPv6. It's 2023 after all.
I just checked and at least the Document Foundation can limit your mirror to IPV6 only upon request
I contacted them ages ago about this issue but never got a reply sadly. Maybe if enough people complain, they will fix it but until then it's out of my control.
I also think that even a dynamic IPV4 would be more useful.
I disagree. Once you get used to IPv6, there is no going back. It's so much easier to deal with as a sysadmin as you no longer have to do shenanigans like NAT and whatnot. SLAAC is awesome too. IPv6 was introduced 27 years ago! If some people are too lazy to upgrade after nearly 3 decades, sucks for them, I refuse to cripple the Internet just to support their legacy crap.
I also think that even a dynamic IPV4 would be more useful.
Edit: Just remembered, your ISP only gives a public IPV4 when disabling IPV6. I had them switch my account to public IPV4 and use https://www.tunnelbroker.net/ with their Singapore server to get IPV6 connectivity.
The real issue for me is that some mirror selectors (I know of LibreOffice) always take me to your mirror, even on hosts that do not have an IPV6 address. This breaks Chocolatey and I don't know of an easy way to change the mirror there.
I just checked and at least the Document Foundation can limit your mirror to IPV6 only upon request, see https://wiki.documentfoundation.org/Infra/Mirroring#:~:text=only%20for%20IPv6%20connections
Unfortunately, it's difficult/expensive to get a static IPv4 in Asia so I won't be able to resolve this issue. I added a disclaimer on the home page at https://cyberbits.asia/ about it though.
Cannot connect to the site because it doesn't have an IPv4 entry, only IPv6.
Thank you so much for providing us with this mirror.
Just waiting for the FOSDEM team to whitelist our new IP. Everything else is back up and running. Phew.