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.

He didn't really take responsibility?

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...

Pages with personality like that are not just examples of how bad UX can be, they are examples of how UX can be used as an artistic form of self-expression.

Even commercial design was interesting and eye-catching back then.

Print designers were adapting to the web and there was a tremendous amount of technique, experience and hard work in that first batch.

Then the dictatorship of the sameness started, and we somehow ended in a world where everything kinda looks the same but is slightly different in slightly broken ways. Creativity be damned, but also other things like performance, accessibility and user-centricity are now secondary to following fashions.

You still have that sort of expression on neocities. It's a genuine treat to see what people are building over there.

https://neocities.org/browse

I miss that quite a lot. For the past 20 years the Web has been a sterile wasteland full of minimalist white and grays and 0 personality.

That's what I miss. Some level of personality is desperately missing from modern alternatives.

True, but it was all quite harmless. Today's perfectly designed web sites are made by folks who know exactly how to make you addicted to the algorithmic feed and whatnot.

I feel bad for you then if this is all you remember about Myspace.

I met so many cool people in real life I never would have other wise it would be hard to even count.

I could go for some pages that look bad vs the homogenized social media where everyone's page is the same.

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.

There’s the WordPress 100 Year Plan or 100 Year Domain: https://wordpress.com/100-year/

100-Year Plan: $38,000 (hosting and domain)

100-Year Domain: $2,000 (one-time purchase, no annual renewals)

There is certainly precedent for this - will executors for example. How about “SCITA? Service continues in the afterlife.

SCIP, in perpetuity?

Software after Death as a Service?

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?