A Mastodon user stumbling upon one of these comments could easily assume that it is just another fully independent “toot” (Mastodon’s equivalent of tweet).

Wait, back up… Mastodon calls these “toots”? So, everybody is posting farts?

That’s the thing about automation and training models.

First, they implement some sort of auto-reporting bot that requires a human to review them. In the beginning, it only about 50% accurate, but as they give it more and more examples of good and bad results through the human reviews, it moves to 80%, then 90%, then 99%, then 99.99% accuracy.

After a while, the humans on the other end are so numb to the 9999 entries they have to mark as approved that they can barely tell what’s a rejection themselves, and the moderation team is asking itself just what this human review is actually doing. If it’s 99.99% accurate, why not let the bot decide?

Then, the model moves on from auto-reporting to auto-moderation.

Gee, I wonder why that so popular…

US Citizen Patents A Way To Not Buy Ford Cars

but is concerned about hosting fees for serving images to millions of people

People stopped caring about image bandwidth decades ago. Try wrangling a video-hosting problem, like PeerTube does.

Ditto.

Dev being an asshole and not accept Linus’ code review = Rust is bad?

But, as the debian dude has learned… Rust programs will 99.999 % work if they can be compiled.

That’s a dumb statement. Every tool needs unit tests. All of them!

If grep complied, but always returned nothing for every file and filter, then it’s still not “working”. But, hey, it compiled!

The OP is about packaging issues with userspace utilities due to version pinning in Rust

No, it’s about Bcachefs specifically. It’s literally in the title. Discussions around Rust version pinning are a useful side conversation, but that’s not what the OP is about.

So if your Rust app is built against up to date libraries in Cargo, it’s going to be difficult to package those apps in Debian when they ship stable, out of date libraries since Debian’s policies don’t like the idea of using outside dependencies from Cargo.

As they should. You don’t just auto-update every package to bleeding edge in a stable OS, and security goes out the window when you’re trusting a third-party’s third-party to monitor for dependency chain attacks (which they aren’t). This is how we get Crowdstrike global outages and Node.JS bitcoin miner injections.

If some Rust tool is a critical part of the toolchain, they better be testing this shit against a wide array of dependency versions, and plan for a much older baseline. If not, then they don’t get to play ball with the big Linux distros.

Debian is 100% in the right here, and I hope they continue hammering their standards into people.

Please don’t recommend the PMG investigation.

Not exactly, but it’s an interesting story

Same thing for Disco Elysium.

Did they use this AI chip system to produce this article?

Switzerland be like:

How about Da Vinci Resolve?

Use GIMP and skip the bullshit.

…I feel like openssh has a much larger attack surface than a simple binary.

Right. This is just trading one set of security pitfalls with a second, much worse set of security pitfalls.

I wish it would combine comments for crossposts. It doesn’t have to break per-server instance bans or anything like that. Just combine the comments for servers that are friendly with each other.

Agent Smth?