105 Followers
366 Following
436 Posts
AU lefty in the US, feminism++, yak shaver, opinions my own, he/him
lolsob

within the past 24 hours I’ve watched two people claim there was nuance to the rsync story that made tridge right, and after not too much discussion they admitted they didn’t know rsync’s slop code only got noticed after a severe breakage occurred, or that people have evaluated the slop commits and found them to be of extraordinarily poor quality (including rendering rsync’s test suite ineffective by translating it from bash into broken python). the story they heard is that someone saw Claude in the commit log and freaked out and directed harassment towards tridge. they seemed to be under the false impression that rsync still worked fine.

how is it that the members of the supposed angry mob are doing deeper analysis than the people claiming nuance?

Mythos is not great btw. Running it over a bunch of code, it’s similar findings to tools from a few years ago. It’s marketing, essentially. Viral marketing as people doing the marketing are companies and governments.

It’s really good at finding vulns in vibe coded stuff from Claude.. because apparently AI must be both the cause and solution to all life’s problems, like beer.

I couldn't really think of any way to improve this headline:

Hackers Simply Asked Meta AI to Give Them Access to High-Profile Instagram Accounts. It Worked

https://www.404media.co/hackers-simply-asked-meta-ai-to-give-them-access-to-high-profile-instagram-accounts-it-worked/

/cc @davidgerard

Hackers Simply Asked Meta AI to Give Them Access to High-Profile Instagram Accounts. It Worked

The exploit shows the extreme risk of offloading technical support to AI.

404 Media
./configure affirmations:
-you have jobcontrol
-your fifos are usable
-your implementation is ok
-your sockets are usable
-you are normal

I’m proposing a new Law of the Internet:

In any conversation about AI agents’ flaws that lasts long enough, the probability that someone will make an unfounded assertion that everyone else is just using slightly inferior tools that they know how to get around approaches 1.

DID YOU KNOW

before language models could extrude code, there was no way to

* automate things
* make things simpler
* reduce boilerplate
* write unit tests
* learn how things work

fortunately you can now send all your money to an oligarch to do these things poorly

Regarding the Raptor Lake bug I received a couple of messages from confused users that had read articles on Tomshardware and Neowin. They asked about erratas and microcode updates which puzzled me, because that was part of my early investigation into the bug and we know that the failure is not caused by a known errata and microcode updates cannot fix broken CPUs. So why did they ask? As it turns out it was slop. Both articles are 100% slop full of confusing and inaccurate claims.
It was better as a breakfast the next day ☕️
Worth it