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.
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.
I've been using Borg for years. It's great! The deduplication feature allows me to take a "full" backup of my work station hourly. Taking frequent backups like this has already saved my bacon a number times in cases where I accidentally mangled/deleted a file I didn't mean to touch.
I believe fish already does some of these things. For example: if there is no binary available in PATH for one of the commands in your history, that command won't be suggested. Same goes for commands that have file/directory names in them that don't exist.
Indeed. It wasn't that long ago that Material components for Android finally got proper support for Material 2 in a stable release of the library. But everything started too look too nice and consistent, so now we're getting steamrolled with Material 3.
Hah, I know that pain. I'm optimistic about the future though. I recently installed Ubuntu on my new work laptop and soon after it offered to update the firmware of my Dell docking station. I was pleasantly surprised to see that.
71 in total. I store all tokens in Aegis and have automatic backups configured, so I don't find it to be too unmanageable. It's seem like a lot, but then again I also have hundreds accounts in my password manager at this point.
You can set up 2FA through one of the other options first. After that, TOTP should be available as an option as well. After setting TOTP up, you can remove the other one.
They're probably hiding the TOTP option because the backup story for Google Authenticator is really poor. If you lose your device, you lose access to all of the accounts you had set up 2FA for with Google Authenticator. Of course, there are other TOTP apps that are better in this regard, but Google is unlikely to promote those because then they'd lose some control over the authentication flow.
I enjoyed reading this article, thanks for sharing it. It would have been nice if the pictures that these probes took were also included in the article.
What is the proper automated way to get vendorSha256? Currently I always set it to lib.fakeSha256 first, then run the build and obtain the hash from the error message.