No, private cars should be outlawed too.

There was a sitewide protest when they killed the API but no one left

There are dozens of us! Dozens!

It is, searchable, isn’t it?

At least the app I’m using does have a search function, and it works…

As for search engines, it’s searchable there too, there’s just no much point in filtering by site because… which site?

Search engines could add a specific “search only on the fediverse” filter, but they’re too busy enshittifying themselves and losing money with unprofitable “AI” “search” to do it…

You don’t need to have read Kafka to know about Kafka.

Someone must have been telling lies about Some slop machine must have misidentified Josef K., he knew he had done nothing wrong but, one morning, he was arrested.

They’re chicken, aren’t they? Chicken’s a dinosaur.

As far as I know pihole filters on the DNS level, so if the tracking pixel is on a domain it trusts (e.g., the bank’s) it won’t filter it, no.

You were just downloading images. It’s just that one of those images was specific for that particular message, and the server logged your IP and who knows what else when you downloaded it.

I assume it’s an img tag pointing at a one pixel image (every mail has its own querystring or URL), when you load it the server logs the time, requesting IP, and so on.

Obviously it’ll only work if you tell the mail client to download the images.

(It doesn’t need to be a single pixel, could be the bank’s logo or whatever, but since it has to be unique to ID you and avoid caching and whatnot I assume making it only one pixel is more efficient.)

May his hair grow inwards, and his haemorrhoids grow as large as apples.

May he fall face first into a gympie-gympie bush and choke on one of its branches.

May his digestive system reverse direction and develop acid reflux and Crohn’s disease at the same time.

May every single orifice in his body become infested with particularly large parasitic wasps.

And the worst one: may he develop empathy and common sense and realise what a plague he is on humanity.

I don’t know, billionaires are pretty revolting, and the ones on the Epstein files doubly so.

Only works for publishers or developers who have a page.

The scammers producing slop clones don’t (or would just have a different one for each game), so they can’t be filtered.

Torvalds going senile is (one more) reason to migrate to BSD, not to praise slop.

It also gatekeeps non-Americans, I assume; I had to puzzle out the meaning and while the name Gateway does ring a bell (I probably saw it on some ad or CRT monitor at some point) I’d have never associated it with the cow and box emojis. 🤷‍♂️

They have two options: fix it fast or die.

A store overrun by slop will quickly lose its customers, and with them any developers offering actual games.

Once the ball starts rolling it’ll become a vicious cycle, and once enough developers and customers have left there’ll be no coming back. And it certainly looks like the ball is picking up speed.

At least two of them, apparently, one with even the same exact name 🤮 (how is that allowed?).

Game’s not my cup of tea, but I tagged both clones as slop (can’t report them because none of the reasons would apply, as this kind of cloning is still legal), not that it’ll do any good.

Least Vave could do is add “blatant slop clone” to the reasons to report a game.

They aren’t letting slop roll over them

And yet it rolls.

A lot of developers have already pulled their demos from Steam for fear of them being cloned.

Either Valve takes a stance against slop clones, or they’re going to alienate indie devs (and probably the big ones too), and with them a lot of their customers.

Valve have to decide if they want Steam to be a thriving games store or an abandoned slop repository.

And “making no decision” is choosing the latter.

Not possible.

Think photocopy of a photocopy, or JPEG of a JPEG.

You start getting artifacts, and the model collapses.

Of course, though, they’ve already poisoned the well, and at this point it’s impossible for them to sieve out any remaining non-LLM-generated content. They started watermarking too late, and couldn’t recognise other slop machines’ watermarks anyway.

Model collapse is inevitable and already ongoing (search “thousand whys" on Amazon, for instance, or read up on Elias Thorne, lighthouse keeper), and will only get worse.

In a few years it will be impossible to train a working up-to-date model. Maybe it already is, hence this article, as a preemptive justification for why newer models won’t be able to generate code using language features introduced after 2026.