Raul Tambre

I checked netdata, and it seems after enabling IPv6, an IPv4 socket leak has manifested:  The leaks seems to...

Since a node balancer is now used, could this change be attempted again? Node balancers proxy traffic to servers over IPv4 so the IPv6 socket leak shouldn't occur. As for...

Didn't realize stuff's now in Terraform – neat! Had a go at it with #283. `cdn.changelog.com` doesn't seem to be in Terraform though.

Awesome, thanks! A few more things: - [ ] Images on the blog are from `changelog-assets.s3.amazonaws.com`. Use `changelog-assets.s3.dualstack.us-east-1.amazonaws.com` instead for IPv6 support. ~~IPv6 on `thechangelog.com` and `nightly.changelog.com`?~~

@gerhard My bash knowledge is non-existant and I don't have a Linux machine on hand, so I'm afraid I'm unable to help with the tests.

@gerhard https://changelog.com/nightly has a link pointing to http://nightly.changelog.com/2016/10/06/. Not sure how I stumbled upon `thechangelog.com`.

`nightly.changelog.com` is on DO. [Their guide for enabling IPv6](https://www.digitalocean.com/docs/networking/ipv6/how-to/enable/) (unfortunately not enabled by default unlike Linode).

@gerhard Thank you very much for finally getting around to this! I clicked around a bit and reported #419 and #420. They're smaller and hopefully fairly contained, so should make...

Updated [Steam Networking](https://partner.steamgames.com/doc/features/multiplayer/networking) [protobufs include a field for IPv6](https://github.com/SteamDatabase/SteamTracking/commit/3457ab4e9db51d8eb09c373914a69cb2e3c9815c#diff-23b34e68362f5f00c56eb6c084651179R9).

[Steam Client Beta has received an update](https://steamcommunity.com/groups/SteamClientBeta/announcements/detail/1703951108822305086) to support downloads over IPv6. Another protobuf update [has added support for an IPv6 address](https://github.com/SteamDatabase/SteamTracking/commit/84a6dd4b50ff8258d3ee9f94082f517e2a897a08#diff-b518a5ac8fef862890bd268408b7d725R51) in one of the messages.