[0x006A]

Its mostly impossible to run servers only with IPv6 since for some reason Canonical/Ubuntu decided to require IPv4 for snap, after years of not having any issues with IPv6 only deb mirrors.

Go is also basically bound to IPv4 since it depends on github to pull packages

its time to make hall of shame for software that does not allow developers to build IPv6 only going forward.

[Kwpolska]

Your first point is easily solvable with `sudo apt remove snap`. It also solves a lot more problems and gets rid of broken software.

[jacooper]

Wait, GitHub still doesn't support IPv6?

[0xbadcafebee]

Neither does DuckDuckGo. Been a feature request for >5 years now.

I'm 99% certain that they turn off IPv6 to avoid complaints. Implementing IPv6 on a frontend load balancer is a trivial networking change. But the only way to ensure an IPv6 connection works is for the user's OS, networking, firewall, router, modem, ISP backend network, ISP DNS resolver, target website DNS, and target website load balancer & firewall, all have IPv6 configured properly. If a single step is misconfigured, or uses IPv6 tunneling/translation, every request might be blocked until the website disables IPv6. So don't support IPv6 at all and you avoid headaches.

Avoiding an unnecessary support headache is the basic reason why IPv6 has existed for 26 years and yet Google can still barely get 40% use for its own website. Everybody loves to design a spaceship, but nobody designs for moving between spaceships mid-launch.

[imoverclocked]

I’m looking forward to the day when this same argument is made for IPv4 by default instead.

[hnarn]

> Go is also basically bound to IPv4 since it depends on github to pull packages

Is this also true for the Go module proxy?

[arccy]

no:

    $ dig +short AAAA proxy.golang.org
    2a00:1450:4009:820::2011

[hnarn]

So Go is not “basically bound to IPv4” since the proxy is enabled by default.