Discord flags lack of IPv6 as "intended"
github.com
Discord flags lack of IPv6 as "intended"
1–4 of 4 posts
Re: Discord flags lack of IPv6 as "intended"
#2I’ve been doing IPv4 networking for decades, and recently decided to take plunge and update all my gear and systems to IPv6.
So far, it’s a train wreck.
20 years in, and none of the major platforms support IPv6 in a consistent way (DHCP6 vs. SLAAC, anyone?), there is little to no analytical or diagnostic tooling, no (working) walkthroughs of equivalencies to standard IPv4 practices, little security clarity, …
This IPv6 debacle is a self-own of major proportions.
Re: Discord flags lack of IPv6 as "intended"
#3I’ve been doing IPv4 networking for decades, and recently decided to take plunge and update all my gear and systems to IPv6. So far, it’s a train wreck. 20 years in, and none of the major platforms support IPv6 in a consistent way (DHCP6 vs. SLAAC, anyone?), there is little to no analytical or diagnostic tooling, no (working) walkthroughs of equivalencies to standard IPv4 practices, little security clarity, … This IP…
Note Google shows 0% of people using 6to4/teredo. That fits my experience that 6to4/teredo didn't work when I tried it.
My ISP is struggling to replace copper with fiber. That's something that makes a difference in my life. IPv6 doesn't make a difference. If anything it's a submarine network that could hide security problems.
Re: Discord flags lack of IPv6 as "intended"
#4[deleted]