How would an #IPv6 only instance of Mastodon be able to play in this space? Would it be a huge irritant to other instance operators who might see it as "broken" and fill up with retries or would they simply be invisible?
@vees even if you server is #ipv6 , it is relatively easy to add a CDN like cloudflare in front of it, and reverse-proxy both IPv4 and IPv6. That's what I do with my IPv6 only server, e.g. gryphontechnology.com
That is if you still want to interoperate with the 60% of the internet that is still IPv4.
@mynacol @vees fair enough; I didn't actually realise Cloudflare did that, but I guess if I point my DNS at them, then they can take over TLS as they want.
My main sites actually use the IPv4 proxy from my hoster (Mythic Beasts), and then provide DNS64+NAT64 for outgoing. My hoster owns the physical servers, so I have to trust them.
@sgryphon My question was more along the lines of what if you don’t want to interoperate with that 60%? Are you making things harder for everybody else?
@vees I don't think it is a big issue; in 2 years IPv6 will be > 50%, and then IPv4 in the minority. Like early on a lot of things did not work for IPv6, from now on I think we will increasingly see things not working with IPv4.
@sgryphon
@vees
I am currently searching for "IPv4 as a Service" myself, but have 2 problems:
1. I try to avoid a big MitM (Cloudflare) terminating TLS before my server.
2. This works for inbound traffic only. Outbound traffic for E-Mail is cumbersome 😫
Things I wanna try:
1. Tailscale Funnel (alpha, doesn't terminate TLS I believe?)
2. vServer with public IP and some sort of VPN NATing to essentially give the IPv6-only server a public IPv4