Criminal court dockets don't include the discovery or the oral transcripts of each court hearing. They tell you almost nothing except the number of continuances that have happened.
The thing with a jury is that there are motivated experts on both sides explaining the technical details in a (hopefully) easy to understand way, a judge to help ensure fair play, and an appeals process as an escape valve.
Considering the accuracy of journalists in general (contentious subject, but the studies I've seen seem to confirm the gell-mann amnesia effect to some degree), I'd say AI Overview isn't bad at least.
Why are you casting to sockaddr_in/6? The whole point of that system is that you can just pass around the sockaddr* without even needing to have a definition for sockaddr_in or sockaddr_in6. All of the socket API functions accept sockaddr*, and if you need to get the IP or port out then you use getnameinfo(), which also takes sockaddr*. There should be little reason to ever cast to either of those types in normal use. (I can think of one or two cases where you might, but they're not common.)
Having to deal with the separate socklen_t is mildly annoying, but you can just make a little struct that holds both.
Not on all OSes.
And it's not all good to have one less socket, there are still issues with people not expecting v4 traffic on a v6-capable socket, like described here:
according to anthropic's red team not even the secret claude stuff they're holding back is able to weaponize vulnerabilities without simplifying (disabling mitigations etc).
so we might be lucky that the LLMs are able to find the vulnerabilities before they are able to weaponize them, giving defense a time window.
Your view is extremely dangerous, tbh., and rather anti-democratic.
reply