unethical_ban
Joined 13 years ago
Joined 13 years ago
But goodness, the infinite-subnets-of-same-size glitch is so amazing. I see companies all the time that struggle to subnet their sprawling enterprise. Different subnet sizes everywhere, fragmented networks, subnet migrations to try to defragment, so on.
Many orgs are so short-staffed and staffed with mediocre talent that they spend their days fighting fires and keeping their flawed current practices operating just well enough to keep the lights on and not cause outages or security breaches. Things like "optimizations" and "redesigns" of the IP stack, even in 2026, would be a 5-10 year journey without a dollar sign benefit attached to it. So they limp along until the transition is seamless and necessary or monetarily desireable.
First, IPv6 in the 90s and 00s is different from IPv6 today. Various extensions and standards have been added that make IPv6 administration easier than it was in the early days. I want to say RDNSS is one of them. Background: one of v6's early selling points was SLAAC, where DHCP could be disposed of and endpoints would auto-configure their own IPs in accordance with the network announced by a router. Problem is, without DHCP, there was no way to get DNS, and DHCPv6 wasn't widely deployed/it was discouraged... so how does one get a DNS server automatically? RDNSS came around to announce DNS servers from the router directly.
TLDR: Early IPv6 sucked more than today.
Second, it's simply a chicken-and-egg problem, particularly at the consumer network level. User-friendly IPv6 router configurations are still rare for home routers, and ISPs have simply dragged their feet. At this point, if we're going to have government mandating all manner of things for consumer products, we should be mandating IPv6 support on home routers and that ISPs delegate at least a /60 to each customer.
AV1 is the future/present: Fully open standard, better than h265. Only downside is hardware support: You need hardware made in the last few years.
An operator should be able to use their vehicle with zero remote software use. No smartphone requirement, no onboard radio requirement. This may mean that certain features like FSD or navigation tools are disabled for safety reasons, but there are plenty of useful safety features that do not require live updates.
From a privacy and utility perspective, this is a no-brainer. Second, as a software security layperson, I think this would largely eliminate any "sleeper cyber sabotage" security concerns that are cited for prohibiting Chinese vehicles.
---
Given how obvious this seems to me, I'm confident that we're really banning Chinese EVs for economic reasons.
Rucho v Common Cause, a case brought against both Dems and GOP that would have rightfully declared partisan gerrymandering an unconstitutional deprivation of voting rights, was shot down by a Conservative court. Democrats campaign on ending gerrymandering, Republicans do not. Trump demanded the recent escalation in gerrymandering by explicitly calling for political re-drawings to give Republicans more seats, and Republican governors complied. The calls to de-escalate and ban the practice federally have (almost) entirely come from Democrats.
Meanwhile my Windows install can't see either of the wifi devices, even when I try to install drivers from the manufacturer. CachyOS autodetects everything and it just works.
So, not pretending, I have fewer issues on multiple devices right now with CachyOS and Fedora than I do with Windows. If my relative had any capacity for learning new hotkeys, I'd already be wiping his machines and putting Kubuntu LTS on them.