News for hackers. Stuff that matters.

A comment on Lessons learned while developing Age of Empires 1 Definitive Edition. Parent comment

Re:Lessons learned while developing Age of Empires 1 Definit... by tambre on Thursday February 15, 2018 @11:33AM (#16385319)
Steam is doing even worse with IPv6 support – in fact they have absolutely none (although their CDN provider has great support for it). Really a shame that they're missing such an useful piece of functionality in this day and age. This of course has made me consider some of the alternatives...

Unfortunately the only Steam alternatives that have some amount of IPv6 support are Humble Bundle and Green Man Gaming. Though you may as well not count Humble Bundle as accessing their website over IPv6 results in it being completely broken [1].

[1] https://vgy.me/0E4HBm.png

[ Parent | on HN ]
Re:Lessons learned while developing Age of Empires 1 Definit... by xrisk on Thursday February 15, 2018 @11:44AM (#16385429)
I'm curious -- why would IPv6 access for a website be an important matter?
[ Parent | on HN ]
Re:Lessons learned while developing Age of Empires 1 Definit... by tambre on Friday February 16, 2018 @02:08PM (#16394957)
It's faster, it's cheaper, it's easier to setup and use. As of now not everyone always has IPv4 access anymore. I conciously avoid purchasing products that have no IPv6 support, as I sometimes have an only IPv6 connection.
[ Parent | on HN ]
Re:Lessons learned while developing Age of Empires 1 Definit... by ZephyrP on Thursday February 15, 2018 @05:14PM (#16388255)
20% of the world uses it.
[ Parent | on HN ]
Re:Lessons learned while developing Age of Empires 1 Definit... by xrisk on Thursday February 15, 2018 @05:36PM (#16388407)
Okay but 100% of the world uses IPv4. Why is having IPv6 support important for a website?
[ Parent | on HN ]
Re:Lessons learned while developing Age of Empires 1 Definit... by jandrese on Friday February 16, 2018 @11:36AM (#16393518)
Because IPv4 is close to exhausted[1] and we need IPv6 support to be the rule, not the exception, by the time it's no longer affordable to get an IPv4 address.

https://en.wikipedia.org/wiki/IPv4_address_exhaustion

[ Parent | on HN ]
Re:Lessons learned while developing Age of Empires 1 Definit... by jandrese on Thursday February 15, 2018 @11:59AM (#16385564)
Not supporting IPv6 is better than breaking in mysterious ways when you have IPv6 support but have to disable it on that machine for reasons (Netflix).

I would like to see Valve get with the times on their v6 support though.

[ Parent | on HN ]
Re:Lessons learned while developing Age of Empires 1 Definit... by tambre on Friday February 16, 2018 @02:14PM (#16395028)
I've never seen a dualstack connection cause breakage. And if it does break with IPv6 support being available, then it's the developer's fault. Instead of disabling IPv6 you should alert them of the problem and if possible use an alternative service, which supports IPv6.

In the case of Humble Bundle breaking, it seems simply because some of their CDN subdomains are IPv4-only. Since the site loads various resources from those IPv4-only endpoints, it causes everything to just break when accessing over IPv6. In a way I'd argue it's still better than your browser displaying "no valid IP address for this domain" – usually you can at least find an e-mail address at the bottom of the page to alert them to the problem.

[ Parent | on HN ]
Re:Lessons learned while developing Age of Empires 1 Definit... by ac29 on Friday February 16, 2018 @12:16AM (#16390048)
>Though you may as well not count Humble Bundle as accessing their website over IPv6 results in it being completely broken

Just checked this in Firefox and it loads completely fine via IPv6 (and I verified using the devtools that it is using IPv6).

[ Parent | on HN ]
Re:Lessons learned while developing Age of Empires 1 Definit... by tambre on Friday February 16, 2018 @02:11PM (#16394990)
Should've clarified. In this case I was on a IPv6-only connection – no IPv4 access available to the outside. Loading with both IPv6 and IPv4 being available of course results in no problems, as it falls back to IPv4 for resources that are not accessible over IPv6 (which is mainly the layout scripts).
[ Parent | on HN ]