Don't bother promoting IPv6 as "the future". It's never going to be the default.

https://feddit.nl/post/17227529

Don't bother promoting IPv6 as "the future". It's never going to be the default. - feddit.nl

Basically what the title says. Here’s the thing: It’s a solved problem. NAT already took care of this via RFC 1631. While initially presented as a temporary fix, anyone who thinks it’s going anywhere at this point is simply wrong. And then there are the downsides of IPv6: - Not all legacy equipment likes IPv6. Yes, there’s a lot of it out there. - “Nobody” remembers an IPv6 address. I know my IPv4 address, and I’m sure many others do too. Do you know your IPv6 address, though? - Everything already supports IPv4 - For IPv6 to fully replace IPv4, practically everything needs to move over. De facto standards don’t change very easily. There’s a reason why QWERTY keyboards, ASCII character tables, and E-mail are still around, despite alternatives technically being “better”. Sure, IPv6 is nice and all. But as an addition rather than as a replacement. I’ve disabled it by default for the past 10 years, as it tends to clutter up my ifconfig overview, and I’ve had no ill effects. Source: Network engineer.

I’m a web developer and I’ve never once used an IPv6 address for any circumstance. My ISP doesn’t use IPv6 either in my region (Starlink).

I’ve got Starlink and IPv6 works fine. That’s the only way I can host anything since IPv4 is CGNAT. You have to use your own router for IPv6 since theirs is a piece of junk.

My cell carrier is T-mobile and it’s IPv6 only. They do have some sort of translator for accessing legacy sites though.

IPv6 should be available for you to use on starlink. You may need to set up your router to use it.
Ah it is. I misunderstood what I looked up.