Retr0id

Wow. That's more than the cost of the storage space you'd be downloading onto.

Maybe a bit of that, but I think I'm just more careful about what I buy in the first place.

> read enormous amounts of generated text

This is something I avoid at all costs. If it's someone else's slop I just won't read it, and if it's "my" slop I prefer to interactively ask questions about it rather than reading a wall of text.

This article made me realize I'd never consider returning a non-defective product, I wonder why that is.

Oooh fun, the rare moderator superdownvote. My comment currently has +58 karma but it's been demoted to the bottom of the thread.

A DoS like this is quite bad (in theory at least) but I think it's the first time I've seen one dressed up with a hypeslop landing page.

This works well if there are obvious hot spots that can be easily isolated, but sometimes the perf issues are more uniformly distributed throughout a codebase.

At this point if you have a python codebase where perf is an issue, the "AI-pilled" answer is to rewrite it in a faster language.

Even ignoring learning outcomes, answer sharing was a good excuse for the nerds to talk to the not-nerds.

I don't know anything about the actual legal responsibilities, but even there aren't any, a defrauded customer takes up support resources just having the conversation about it. Upset customers (regardless of how well placed that upset is) will complain about it in reviews etc.

A lot of people aren't able to distinguish "I got scammed" from "the bank took my money away".

If it's a single particle I don't think there's much to worry about?