My comment was in response to Henry, who implied that going IPv6-only would make legacy sites inaccessible.
Many ISPs around the world already go the NAT64 route, DS-LITE or various other mechanisms, it's generally transparent to the user. Full dual stack is not economically viable so you're already facing compromises with legacy traffic, and the compromises get much worse in countries where the user base is expanding rapidly.
Lots of legacy technologies are still in use, that's the point - it's not current, not preferred, and not the focus of active development. Just like it took many years for floppy drives, optical media, rotating hard drives, CRTs etc to fade away. There is also still a long tail of sites which only support HTTP/1.1 (HTTP3 is current), older TLS versions, older HTML standards etc.
The guide you linked to is about running your own NAT64 gateway, which requires that you have dual stack with at least one legacy address.
You can already use public ones simply by changing your DNS resolver (see
https://nat64.xyz). The M1 one is already used by default on their mobile service (at least when you have an iOS device) but to use it from a fibre link you need to setup the DNS64 part yourself (on pfsense its as simple as adding the nat64 prefix).
If you tether to an M1 mobile you will notice it's enabled by default, and dns lookups of any legacy sites will show v6 addresses within the NAT64 prefix range.
If you pick a random server from nat64.xyz and set your dns resolver to it on a macos device then turn off legacy ip it will just work, all you'll notice is the performance hit because the public nat64 servers are abroad. If you are able to use the local one provided by M1 there's no performance hit relative to using NAT44, in some cases it's actually faster because their gateway devices are significantly more powerful than a typical home router.
