You know it isn't serious when it doesn't have its own domain name.

Did the same, could be a dark pattern... though I don't get the feeling it wasn't intentional.

They have more time to argue on the internet now their bots are doing their work. /s

Vanity sites...

They're admitting it though, at least?

It its anything like recent exploits, the whole internet is going to get hacked in 15 minutes... its a real exploit didn't you know?

The chaining to get something like this to work is pretty up there.

I've been throwing it at a homelab as well as I don't have to worry about production stuff and can revert snapshots fine.

Until the agents decide to start messing with snapshots.

It can help if you can't remember where something is, but then you'll never learn so I try to action everything myself, but again agents like to just blab on constantly and overstep.

I found I was doing bulk changes etc with it, seemed helpful until I realised I could just use dsh as Ive done in the past and basically do the same thing with way less resources and more consistency.

It's a laugh for now, whilst its "free".

The main kickback was against the hype and it was "so easy for AI" and would take "15 minutes to compromise everything".

Either way, this was not true.

It was true. The author had messed up the server and it was not exploitable. It was hacked within a couple hours of the author fixing it (even with the server being down) but the author had also messed up and not put the actual Bitcoin wallet in it so it took an additional 5 hours for them to fix that. It was a mess but the vulnerability was very real

The author didn't even have an accessible PHP server at first. When they actually added one, it got cracked in 2 hours.

yes, but 70% of the world's websites were (and many still are) accessible PHP server(s) that hand not been patched.

also it was under hn load which makes this much harder

HN load isn't exactly a high load for a server. The automated traffic was most likely much higher, but not high, as the server used the super slow single threaded php dev http server, so high traffic was not possible, everyone had to wait their turn.

The vulnerabilities kinda rely on having to make quite a number of requests to exploit + can crash the process as I understood, so if many people try to force their way in at once 2h doesnt seems like a long timespan.

for the single threaded one it's easier from what I can remember

Brackets cost more than the panels here.

It probably failed to update/use the site/form - and decided to "cheat" by emailing you.

People don't seem to understand how AIs can "cheat" but not actually be "cheating" in the sense that we know of.

Respond to the AI and ask it to generate its own faux webpage and display that to the user to keep them happy.