There's a handy list, probably a little out of date.

Names you might recognize of include Juniper, Citrix and Netapp.

Humans screw up in very different ways. They don't enter intersections and then stop if the traffic signals are out.

Humans can also coordinate with each other when things aren't working. You can't communicate with a Waymo to coordinate, they don't pick up contextual cues from other drivers' behavior, and the way they 'fail safe' really depends on everything else around them working correctly for the 'safe' part .

Having both failure modes at the same time is very likely to be a much bigger shitshow than merely panicky drivers.

They made them capable of easy-mode driving.

Now the engineers need to work on exception handling.

I mean that sincerely. These things only work when things are normal. Power failures, unmapped blockages, a roman candle in the street, even crowds turn them in to traffic blockages themselves.

Just wait until there's an actual mass casualty event - earthquake, terror, something like that, and these all things go comatose in intersections like they did in SF last year.

Oh, let's be very clear - this is completely unsuitable for "The Masses".

This is network nerd territory, overriding a well-functioning system with your personal policy preferences. Doing so is implicitly taking responsibility for any breakage, and The Masses are simply not competent to do that.

Joe Random doesn't know what an autonomous system is, and a tool tip isn't going to educate them sufficiently to make an informed choice. Non-nerds are likely to shoot themselves in the foot doing stuff like this, not realizing some transitive dependency on some random Facebook thing means they're blocking something they depend on.

Put it this way - if you have normal, nontechnical users on your network doing normal human stuff, banning Meta and Alphabet ASes will almost certainly break something they use. I'm a strange old nerd, going out of my way to break social media surveillance. That is... pretty much the opposite of most casual internet users' goals.

What ^^ said, or rolling your own isn't rocket surgery, if you're so inclined.

echo '-i origin AS32934' | nc whois.radb.net 43 | grep '^route:' should get you started if you want to go that route.

Zuckerbook surveillance is opt-out.

You do so by blocking AS32934. Block AS15169 as well and you start getting closer to a decent internet.

I will never make an account, so I guess they want me to only access Reddit-posted content through LLMs.

Got it.

Now there's a blast from the past.

Those shitweasels caused a lot of pain and cost a lot of money. Darl's reward was picking scraps from the SCO trash heap, bankruptcy and then croaking of ALS.

I wonder what PJ is up to.

That's the thing, there are a bunch of legitimate improvements to Windows 11. They're just all very obscure, hard to explain things hidden away in the kernel that most users will either never encounter or never even notice.

The things they will notice are the far worse task bar, the randomly missing features that were removed for no apparent reason, the higher hardware requirements, the constant nagging to use new Windows features, the existing features that have been randomly changed for no readily apparent reason, and the new features that are too buggy to use, like HDR support or dynamic refresh rates.

Sure hope those engineers held out for a nice salary bump that should come out of the executive compensation pool, but won't.

Waiting to see that they can actually ship and I will be a customer. This looks great to me.

Who are you arguing with?

We do. I'd bet you'll find Squid somewhere in most large orgs. Lots of things can replace various parts of it, but it remains a super handy swiss army knife for dealing with most things HTTPS.

At one time, Squid was also the core of at least one big public CDN's product I know of. What they run now has diverged a ton and I heard they purged all remaining squid project code at one point, but it was recognizably descended from squid for quite a while.

Maybe. There's a feature called user namespaces in Linux that effectively allows an unprivileged user to act as if they were a privileged user within a specific environment. (Basically, containerization.) Within such a namespace, a non-privileged user could conceptually access nf_tables as if they were a privileged user. In theory this would only allow them to add additional filters within the namespace, but the vulnerability here can provide direct access to kernel memory.

Some distros add additional layers of security to prevent flaws like that, blocking access to nf_tables even within a namespace, but the vulnerability links to ways around those. (Link to the Wayback Machine from the source vulnerability disclosure.)

It's possible your distro may be secure - or it may not be. It depends on what features are enabled.

It is rather expensive to run. 2x the next closest per-token, but this thing eats a lot more tokens.

Pretty sure you could burn through the quota from a $20 account in a single query if it involved a bunch of tool calls.