P03 Locke

It’s a thing you can look up on search engines or Wikipedia very easily: https://en.wikipedia.org/wiki/VTuber

Nobody needed a description that borders on erotica fiction.

No, I’m arguing that people shouldn’t be so fucking allergic to watching videos on this damn forum.

The what? You do realize it’s just some guy with 73 subscribers. He’s not getting paid billions of dollars.

we all know what’s going on without having to watch a youtube video

The horror. God forbid, you actually support the video uploader.

Meh… given the choice between low-effort AI art and low-effort crayon drawing, I think I’ll take the AI art, please.

Uhhhh, sure, I guess.

I’m sure it starts with C and ends with “Strike”.

It will be the opposite. Even Microsoft hates kernel-level anti-cheat.

I mean, that all depends on what the MPL allows.

Depends on the context. We’re talking about an image editor, so showing a demo of the features in video form is helpful.

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.

Switzerland be like:

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