trulyrandom

Does GitHub's container registry still require authentication for pulls?

Just to add a non-problematic experience report to the mix: I've been using 6.10 for months on two AMD machines with different hardware (one with a 7840U and one with a 5700XT) without any issues whatsoever.

On Linux, "net.ipv4.ping_group_range" is typically used to allow unprivileged users to do ICMP echo requests. Setting the setuid bit or granting a capability are both very old ways of doing this.

Repeat after me: I will never, ever, use proprietary software for important data again.

This requires a more comprehensive redesign of the build process. Most Linux distributions also run the tests of the project they're building as part of the build process.

Really? Is the new implementation of the sync server finally stable? For years we've been stuck between the old Python 2 implementation and the new incomplete Rust implementation.

I remember there being talks of a complete rewrite of Newpipe. Did anything come of that? I'm a happy user, so I don't really have an opinion on whether it should happen or not.

I'm always excited to see developments in the Nix ecosystem, but I can't help but feel that this is a little bit tone-deaf. Nix flakes is a sensitive topic in the Nix community. Instead of spending time gracefully stabilizing the currently experimental feature, some of the core contributors to Nix apparently feel that doubling down and building a product on top of it instead is a better way to spend time.

In addition, we're invited to join the discussion on Discord, of all places, instead of the other two standard messaging platforms that the Nix community typically uses (Matrix and IRC)

I share your frustration about the Nvidia situation. However, if you want to run a certain operating system and have a good experience, you need to buy hardware that's well-supported on that operating system. It's as simple as that. This is a little like buying an M1 Mac and complaining that Linux doesn't run well on it.