4 ms·
> It's a misconception that you have to wait with IPv6. Yes and no. As I stated at the end of my comment, the problem w/ IPv6 is that who's benefitting the mos
by 1_player 8y ago
> It's a misconception that you have to wait with IPv6.
Yes and no. As I stated at the end of my comment, the problem w/ IPv6 is that who's benefitting the most isn't clear: I am interested in it, as a power user. Average Joe doesn't care. App developer doesn't care (no killer IPv6 apps yet). Large ISPs with extensive CG-NAT deployments don't care (not worth the money, yet, see IPv6 adoption in the UK).
Who cares about HTTP/3? Average Joe — Not really. Mozilla/Google — Hell yeah they do. It'll be in Chrome before anyone else (if it isn't already). Same with nginx/Apache/any other webserver, Joe Blog with his own VPS will want to enable it. And that's all you need.
- judge2020 8y ago> (no killer IPv6 apps yet). If it helps, Apple now requires apps support IPv6-only networking. https://developer.apple.com/support/ipv6/ https://developer.apple.com/support/ipv6/
- gsich 8y agoThis is just client side, any tunneling or NAT64 is still allowed.
- the8472 8y agoRunning any kind of p2p client is more feasible with ipv6 if your v4 is behind a CGNAT.