iansmith_hn

I'll give him credit for taking responsibility, but I have to admit that Claude had nothing to do with the issue. You could have taken somebody else's project with a few uses of curl and git. There may be many things wrong with Claude or even AI in general, but this isn't one of them.

Talk about rose-colored glasses and "the good ol' days". All I can remember are the animated gifs flash and spinning around on people's pages...

Does this suggest a subscription(ish) business where you pay the hosting company for N years and then they ensure your website stays up and unchanged for N years after you die? Quality control issue?

Given how many things want me to pay a subscription while I'm alive, surely somebody will start charging me when I'm dead. It is the logical conclusion of SaaS. I wanted to create an acronym for this, but death as a service didn't seem like the best choice.

I would say the fact so few people follow your advice and are meat-puppets generating enormous tomes intended for others read/understand may, in fact, save white collar job market.

"Who can understand your insurance plan better than a human who has done it for 25 years! You can just mail them your Claude response and they'll tell you what it means!"

Are adversary agents a solution here? I've had good success using them to prevent the base agent from going off plan.

Does anybody have a filter for cryptography posts of the form:

AES IS BROKEN: Making giant assumption XYZ and requiring a less capable AES in ABC way, we've reduce the amount of operations needed to break AES from 10^X to 10^X-1!

These are tedious for people who are interested in cryptography but are not researchers in the field. (For the researchers, this type of thing may be useful.). The fact that AI is now "generating crypto results", suggests that soon we will soon have crypto-post-slop as clickbait...

Or waiting for Claude's outages to clear up.

Thanks for the link to the CVE. Are we likely to ever get a full breakdown of the exploit? I guess when artifactory is patched and deployed widely? Although I must admit my interest in mostly curiosity, but perhaps a full disclosure and explanation might give other folks guidance about much they need to lock down their code or maybe even a construction in java (?) to avoid?

Agreed. Along those same lines, their startup time claim "faster than go", gives me concern because the slowest part of go startup is the various GC-related initializations. If they are doing GC, then you would assume their times would be broadly similar.

Fair enough. Is the right enforcement then to ignore the "token resellers" and go after the credit card business listed at the "upstream" on his post?