It's webscale.

There's no pretending. The text file was put there with specific instructions knowing that it will be triggered. Malicious intent matters here. The tool is the tool, the damage wasn't unintended in the slightest.

You can hear what you want. I'm neither a coder nor do I use LLMs.

But you know what I see? Someone who is so triggered and biased that they give up all logical thought in a discussion, resulting in simply attacking the person participating it (in a hilariously incorrect way). Come back when you have something meaningful to add on the topic of blaming a tool for the malicious intent of a person.

And yet it did something malicious and it was written in that way because the person expected it to do something malicious. There's nothing malicious about the act of me moving my index finger either. Are you going to tell me I did nothing wrong if that resulted in metal lever moving releasing a spring forced mechanism that hits the back of a casing full of powder causing a small explosion that propels a bullet into you. Which one of these mechanisms are you going to blame for getting shot since you clearly think the intent of the instigator is irrelevant?

The existence of a bug does not excuse the person exploiting it in a way that causes harm. He could have done something funny and harmless which would still have been newsworthy, but no, he issued instructions to a tool to delete data. I support his cause, but I hope he gets fucked for the actions he took in the name of it.

False. The guy is *now* taking a stance and mentioning it in the release notes. He initially he simply planted a poison pill, not a fun one, but one that causes actual damage. By the way putting up a sign that says I will shoot you if you come on my property doesn't actually give me legal right to shoot you if you come on my property (except maybe in Texas)

That's the difference here. I am fully in support of people taking a stance right up to the point where they cause actual harm. It's one thing to get the AI to output something silly and funny, quite another to get it to delete something someone else has worked on.

Raising awareness is good. But if I fight climate change by going and punching Shell's CEO in the face, I fully expect to be in jail at the end of the day.

Oh thank god. Next time malware wipes data from my drive I can blame the OS vendor for providing a system call that allows the removal of said entry from the filesystem. Good to know the malware author isn't to blame simply because the output of their software made a different piece of software do something.

I especially like the absurdity of your sentence. You called AI a tool. Which it is. Tools are just that, they serve a purpose. You don't blame a hammer for breaking your window, you don't blame a car for letting a bankrobber outrun cops, you don't blame a gun for someone else having pulled the trigger.

Why do you turn off your brain when it comes to using an AI tool which followed a specific instruction given by a nefarious actor? Does the phrase trigger something in you?

I wonder if the kool aid will wear off before or after you understand the concept of facetious sarcasm.

So if malware uses bitlocker to encrypt your files and doesn't share the key with you then it's Microsoft's fault rather than the malware writer?

The author of the software injected instructions to software you are running. How is it the software's fault for following instructions and using its capability?

This doesn't remove the ability to run 32bit processes. It removes the ability for a 32bit process (with 32bit pointers) to pretend it's a 64bit process. Virtually no one used this. x86 != x32. I'll bet you've never come across an x32 ARCH in the wild. No one is removing the x86 ABIs (at least not i686, some of the earlier ones are gone).

This isn't 32bit support as much as it is x64 support for a 32bit application. It has virtually no use case and wasn't really adopted for anything. Anyone wanting to use x64 instructions just compiled x64 binaries. There was a thought that maybe creating 32bit binaries with the ability to access features of x64 CPUs would improve performance, but ultimately it didn't.

Going forward you'll still be able to run 32bit software. i686 != x32 The latter is an ABI no one used and the former isn't being removed.

There's a difference in support for individual hardware, and providing support for a whole ABI. The potential attack surface and the related code is much larger for the latter.

Just like the previous announcement quite a few people focused on the loss of a HAM radio interface card, but buried the lead that the kernel actually removed a whole networking API that this card depended on instead.

Whether the police use facial recognition, or a private member of the public uses facial recognition and hands that data to the police is a distinction without a difference. While it's great that a fugitive was caught, what really needs to happen now is the journalist or rather the facial recognition data source the journalist used need to be dragged through the courts for breaching of privacy laws.

Did the journalist get clear and explicit warning to the guy for the use of facial recognition as required by the GDPR disclosure clauses?
Did the journalist use only their own tech? If not then the "Data Processors" may have something to say about their legal role here.

As far as I can see there's still a terrorist running free... and apparently working for a newspaper.

Yeah I too support anyone who goes and punches people I don't like. They are heros!

Where have I heard this before?... I was going to make a reference to Germany last century but really these days we can just cite America today.

I hope on Monday your computer is infected with ransomware. I'm sure you'll roll over and take it like a bitch, because you wouldn't be a "dork who would threaten someone for writing code" right?

It actively instructed the AI agent to delete work and attempted to obscure itself as the source of it. It may not cause harm now, but the original act was inexcusable. You are defending actual malware.