What seems most depressing about this isn't the fact that the bot is stupid; but that something about 'AI' seems to have caused people who should have known better to just ignore precautions that are old, simple, and relatively obvious.

It remains unclear whether you can solve the bots being stupid problem even in principle; but it's not like computing has never dealt with actors that either need to be saved from themselves or are likely malicious before; and between running more than a few web servers, building a browser, and slapping together an OS it's not like Google doesn't have people who know that stuff on payroll who know about that sort of thing.

In this case, the bot being a moron would have been a non-issue if it had simply been confined to running shell commands inside the project directory(which is presumably under version control, so worst case you just roll back); not above it where it can hose the entire drive.

There just seems to be something cursed about 'AI' products, not sure if it's the rush to market or if mediocre people are most fascinated with the tool, that invites really sloppy, heedless, lazy, failure to care about useful, mature, relatively simple mitigations for the well known(if not particularly well understood) faults of the 'AI' behavior itself.

There is zero value in some big scary climate risk number also being disclosed, because A that risk accounted for if you are studying the details anyway and does not help you make a rational decision, because it literally does not affect you beyond the places where it is already baked into the numbers.

If you don't care why the insurance is so expensive or unavailable (e.g. high risk of flooding) then maybe you also don't care about why the house's price is so high (e.g. nice location, good construction, etc). No need to even look at the house. Just treat the whole damn thing as an abstract exercise in numbers.

OTOH, some people might actually care about details. Maybe because they're considering living there?

There's nothing that screams 'trying to con you' quite as hard as a participant in a nominal free-market scenario trying to preserve ignorance and information asymmetry.

Why are US lawmakers so bad at their jobs that these kinds of work-arounds are a thing? Don't they get experts to write the laws, and then fire them if they screw up this badly?

I've noticed that a lot of US tech companies don't understand how this isn't normal, and when they discover that the same work-arounds don't work in Europe, they get very upset.

Or just head over to The Pirate Bay and grab everything in a DRM-free format to enjoy.

To be fair, they don't. They want to slightly reduce the sun's output, so that it offsets the greenhouse effect we have caused. So no famine, just less catastrophic climate change (which causes famine) than we would otherwise experience.

The two biggest dangers are that we screw it up and dim too much, with no way to undo it, and that we use it as an excuse to keep polluting.

The UK just agreed a "deal" with the US where the cost of medication will rise by at least 25%. The cost of living crisis is not going away, it's getting worse.

Their model seems to be people who don't use a car enough to warrant owning one, but want the convenience of having access to one and are willing to pay a premium for it.

What always puzzled me about Intel's...more peripheral...activities is that they seemed to fall into a weird, unhelpful, gap between 'doing some VC with the Xeon money; rather than just parking it in investments one notch riskier than savings accounts' and 'strategic additions to the core product'; which normally meant that the non-core stuff had limited synergies with intel systems; and had the risks associated with being a relatively minor program at a big company with a more profitable division; and thus subject to being coopted or killed at any time.

Seemed to happen both with internal projects and with acquisitions. Intel buys Altera because, um, FPGAs are cool and useful and it will 'accelerate innovation' if Intel is putting the PCIe-connected FPGA on the CPU's PCIe root complex rather than a 3rd party vendor doing it? Or something? Even at the tech demo level I'm not sure we even saw a single instance of an FPGA being put on the same package as a CPU(despite 'foveros' also being the advanced-packaging hotness that Intel assured us would make gluing IP blocks together easy and awesome). They just sort of bought them and churned them without any apparent integration. No 'FPGA with big fuck-off memory controller or PCIe root we borrowed from a xeon' type part. No 'Intel QuickAssist Technology now includes programmable FPGA blocks on select parts' CPUs or NICs. Just sort of Intel sells Altera stuff now.

On the network side, Intel just kind of did nothing with and then killed off both the internal Omni-path(good thing it didn't turn out that having an HPC focused interconnect you could run straight from your compute die would have been handy in the future...luckily NVlink never amounted to much...) and the stuff they bought from Barefoot; and at this point barely seems to ship NICs without fairly serious issues. I'm not even counting Lantiq; which they seem to have basically just spent 5 years passing on to Maxlinear with minimal effect; unless that one was somehow related to that period where they sold cable modem chipsets that really sucked. It's honestly downright weird how bad the news seems to be for anything that intel dabbles in that isn't the core business.

Not delivering on schedule is absolutely a symptom; it's just a somewhat diagnostically tricky one since the failure can come from several directions; and 'success' can be generated by gaming the system in several places, as well as by successful execution.

In the 'ideal' case things mostly happening on schedule is a good sign because it means both that the people doing the doing are productive and reliable and the people trying to plan have a decent sense(whether personally, or by knowing what they don't know and where they can get an honest assessment and doing so) of how long things are going to take; whether there's something useful that can be added or whether forcing some mythical man-month on the people already working on it would just be a burden; keeping an eye on whether there's anything in the critical path that is going to disrupt a bunch of other projects, and so on.

If you start losing your grip on the schedule, that fact alone doesn't tell you whether your execution is dysfunctional or your planners are delusional, or some combination of the two; but it's not a good sign. Unhelpfully, the relationship between how visibly the gantt charts are perturbed and how big a problem there is is non-obvious(a company whose execution is robust but whose planners live in a world of vibes-based theatre and one whose execution is dysfunctional and crumbling and whose planners are reusing estimates from the time before the rot set in might blow a roughly equal number of deadlines; despite one having mostly a fluff problem and one probably being in terminal decline); but it's never a good sign.

I'm not a US lawyer, but I'd interpret that as they need to block commercial VPN services advertised for circumventing blocks.

Once again, Open Source is embarrassed and left behind.

mplayer and mpv still, after all these years, don't have a way to prevent things from working if the content origin happens to be Netflix. It just plays on, stupidly Just Working, instead of breaking the way that Netflix realized their users want it to break.

To be fair your link does say "designed to bypass internet filtering mechanisms or content restrictions", so it sounds like SSH, work VPNs, banking etc. don't count because they aren't designed to get around the porn filters.

You make sense, but there is nothing that is "designed to bypass internet filtering mechanisms or content restrictions" more than SSH and VPNs bypass internet filtering mechanisms or content restrictions, is there? Why would anyone ever design a tool to get around filtering and restrictions, when they can already do that with established mainstream tools such as SSH or VPNs?

I can't believe the bill is intended to never be applied to anything. If we do think it's written in such a way that it never applies, I don't think it'll be litigated that way. Once it's enacted, they're going to say it applies to something, and that something is going to be anything that is secure.

You didn't read the bill very closely.

I think I read it much more closely than you did.

Sec 2(a):

"Circumvention tools" means any software, hardware, or service designed to bypass internet filtering mechanisms or content restrictions including virtual private networks, proxy servers, and encrypted tunneling methods to evade content restrictions.

This is either intended to apply to something or never apply to anything. Do we agree that the text is intended to do something, to somehow cover some possible situation which might realistically come up? You don't think they just put this in there, but with the begrudging admission that it could not ever possibly apply, do you?

Assuming you're still with me there, please give an example of what kind of tool this defines as a circumvention tool. Surely you have something in mind.

The bill is about outlawing the distribution of p0rn, and a VPN is merely listed as an unlawful circumvention tool.

That might have possibly been the original intent several years of editing ago, but I do not see anything in the definition of "circumvention tools" which even tangentially relates to porn. Do you? I think porn is 100% irrelevant in this discussion.

What I'm getting at, is that there isn't a "porn version" of Wireguard or SSH or HTTPS. They're all the same, content-neutral. The bill either bans them all, or doesn't ban anything. If you take my above bolded challenge to name a circumvention tool that this bill does address, I'm going to take all of your arguments that you give for why the law does apply to your circumvention tool example, and I am going to successfully apply them to SSH and HTTPS. And I'll be exactly as correct as you.

The only way this bill doesn't restrict SSH and HTTPS, is if it doesn't restrict anything at all. Don't agree? Then name something it does restrict.

They have given us a bit of a masterclass in engineering here. Identified a rare but important issue, took decisive action to ensure safety, and engineered a fix very quickly to get the aircraft back into service.