News for hackers. Stuff that matters.
Re:SSH hacks – a little sanity for remote workers by mmalone on Thursday April 30, 2020 @12:01AM (#23027291)
Last time I launched a new website it took less than a month for someone to let us know that we'd forgotten to configure a AAAA and our site was inaccessible for them. And that was at new website traffic volume.

So yea, GitHub definitely knows about AAAA records and has intentionally decided not to have one. The question is: why? They must have a reason. Maybe even a good one. I'm curious.

Re:SSH hacks – a little sanity for remote workers by rob-olmos on Thursday April 30, 2020 @02:09AM (#23027895)
Interesting. Any likely reasons why not having IPv6/AAAA make the site inaccessible to them?

Sounds like most of the internet would be inaccessible to them as well?

Re:SSH hacks – a little sanity for remote workers by segfaultbuserr on Thursday April 30, 2020 @02:32AM (#23028017)
A broken AAAA record, perhaps. Sometimes the AAAA is invalid or broken without getting noticed by the sysadmin. I've personally reported broken AAAA records before.
Re:SSH hacks – a little sanity for remote workers by rob-olmos on Saturday May 02, 2020 @11:39PM (#23056697)
I see. Although from the mmalone's comment it sounded like an AAAA record wasn't set at all, rather than set incorrectly.
Re:SSH hacks – a little sanity for remote workers by segfaultbuserr on Thursday April 30, 2020 @12:20AM (#23027406)
I do find some rumors on Reddit [0], which says IPv6 is a low priority project that gives its way to other projects.

[0] https://old.reddit.com/r/ipv6/comments/ec8i7y/github_still_d...