p03locke

Was banned for saying that it’s not very difficult to self-med on !@[email protected] due to “bad advice”

Because you're not a doctor, or any sort of medical professional, and even if you were, you couldn't recommend medicine to other people for self-medication. Everybody's different, and responds to medication differently.

Literally 1984.

Literally.

In general self-medicating safely is something us ADHDers should come together around and build a community to share advice on how to do it while minimizing harm.

How about coming together, gather around Congress, and get them to change the law? Or broadcast what this bullshit is to more people? Or vote for people who push this as an issue?

That seems a helluva lot more useful than a community of people pretending they know what they are talking about and literally dying because somebody recommended they go order black market tainted shit online.

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.

What are you doing browsing the internet at work?

Or... you could just watch the video. Considering this is the Video community.

Benn Jordan keeps it entertaining.

It's a somewhat new job title, but it's now becoming standard across the movie industry.

Let's go one step further and require robocallers to disclose that they are robocallers.

Also, this won't work in non-US countries, where 98% of the spam calls come from.

With this change, extensions can “only” alter/inspect/redirect/block 30,000 domains if they use the webRequest API. That’s not enough to build uBlock Origin with, but at least there’s limit now.

That seems like an arbitrary number. Why not 20,000? Or 300,000? What the hell is this limit even for? Even malware can still target 10 domains and do some significant damage. So, what the hell is the point?

Remember, politicians don't pass racist laws by directly saying they are excluding PoC into the law. They do it by targeting commonalities that happen to apply to PoC.

Google isn't going to flat-out say they are blocking uBlock Origin. They are going to do it by implementing "security features" that just so happen to target only uBlock Origin.

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

Starting off with a false dichotomy, conflating that no one else is trying so you’re their only hope

I'm sorry, but who else is trying?