4 ms·
Only because HN is IPv4-only. I'm sitting in a remote office on my laptop this morning, and it has an IPv6 address. When I visit google.com, it's over IPv6.
by jrockway 14y ago
Only because HN is IPv4-only. I'm sitting in a remote office on my laptop this morning, and it has an IPv6 address. When I visit google.com, it's over IPv6.
It's happening.
- geofft 14y agoWhy is HN IPv4-only? And why should they bother to spend any effort fixing it? Given that, e.g., techcrunch.com and github.com and everything else linked from HN is IPv4-only, you can't usefully use Hacker News from an IPv6-only connection, so why should HN care? You're expecting altruism or geekiness on the part of every single website ever -- it's fair to expect that from Google, but not from everyone. The transition may or may not be happen_ing_, but it will never finish.
- jrockway 14y agoNo I'm not, I'm expecting anti-altruism from low-cost ISPs. (Name one consumer ISP that you think is altruistic.) Then, to capture that market, servers will start deploying IPv6. Today, IPv6 is billed as a premium feature. Tomorrow, IPv4 will be the premium feature.
- geofft 14y agoWait, you expect any low-cost ISPs to offer IPv6-only, and have any customers at all? And that IPv4-only sites will say "gee, better support those IPv6-only users" instead of saying "get a better ISP" (or more likely "We have no idea what's wrong, but it works from Comcast, complain to your ISP")? I don't think you understand how the Internet works. Or business. There is no foreseeable point at which it makes sense to bill an "Internet" service that's IPv6-only. That's doable _after_ the transition, but expecting that to happen now is not a transition.
- rdl 14y agoI think for the same reason HN doesn't do DNSSEC or HSTS -- pg isn't a full-time sysadmin.