Block it and move on with your life?

I think I have a simple function in my .zshrc file that updates flatpaks and runs dnf or zypper depending on what the system uses. This file is synced between machines as part of my dotfiles sync so I don’t have to install anything separate. The interface of most package managers is stable, so I didn’t have to touch the function.

This way I don’t have to deal with a package that’s on a different version in different software repositories (depending on distribution) or manually install and update it.

But that’s just me, I tend to keep it as simple as possible for maximum portability. I also avoid having too many abstraction layers.

That’s mostly down to Teams though (being the bloated web app that it is), and not the underlying operating system.

When talking about the kernel, Windows actually skipped 3 major versions iirc from the top of my head. Windows 8 was Windows (NT) 6.2, and Windows 10 skipped that version number to, well, 10.

Why when a simple alias will do?

The list of “Healthy Games” is a great resource to have!

I also experienced less “hiccups” since switching to Linux with KDE but I’d like to know on what combination of hardware and Windows you experienced anywhere close to an average of 1s response time to “any input”.

Technically no, but if you want to install apps from the App Store, then yes.

I expected something more shocking when I read “working with Russia”.

Kagi uses multiple search backends, and of course it needs to forward search terms to these backends. These backends probably can’t trace the searches back to the individual Kagi user though, but Yandex could still analyze search trends for example.

What’s worse is that - unless they use Yandex’ API for free - customers indirectly (and likely unknowingly) support a Russian company with their paid Kagi subscription.

Kagi should at the very least release a statement about this claim.

Bitwarden keeps working just fine.

Sorry, I don’t know of a guide for other distributions.

This being displayed as “Unknown” is likely just a bug or an app you (very) recently uninstalled. And you probably opened the camera app by accidentally swiping right to left on the lock screen. Even just a slight swipe will launch the app so it’s ready when you’re done swiping.

And I’m not even sure what you’re talking about regarding your QR code.

Android is not de facto superior to iOS, nor is the opposite the case.

If you’re really that paranoid, even GrapheneOS on a Pixel shouldn’t calm you down because it also requires proprietary firmware by Google (and possibly other vendors) to run on these proprietary devices. In this case my advice would be to stop using smartphones altogether and rely on open source computers (couple of RISC-V options out there I think) for your computing needs.

Yes! Can I haz pancakes too?

Pretty calm here for a “panic”.

It’s kind of in the word distribution, no? Distros package and … distribute software.

Larger distros usually do a quite a bit of kernel work as well, and they often include bugfixes or other changes in their kernel that isn’t in mainline or stable. Enterprise-grade distributions often backport hardware support from newer kernels into their older kernels. But even distros with close-to-latest kernels like Tumbleweed or Fedora do this to a certain extent. This isn’t limited to the kernel and often extends to many other packages.

They also do a lot of (automated) testing, just look at openQA for example. That’s a big part of the reason why Tumbleweed (relatively) rarely breaks. If all they did was collect an up-to-date version of every package they want to ship, it’d probably be permanently broken.

Also, saying they “just” update the desktop environment doesn’t do it justice. DEs like KDE and GNOME are a lot more than just something that draws application windows on your screen. They come with userspace applications and frameworks. They introduce features like vastly improved HDR support (KDE 6.2, usually along with updates to Wayland etc.).

Some of the rolling (Tumbleweed) or more regular (Fedora) releases also push for more technical changes. Fedora dropped X11 by default on their KDE spin with v40, and will likely drop X11 with their default GNOME distro as well, now that GNOME no longer requires it even when running Wayland. Tumbleweed is actively pushing for great systemd-boot support, and while it’s still experimental it’s already in a decent state (not ready for prime time yet though).

Then, distros also integrate packages to work together. A good example of this is the built-in enabled-by-default snapshot system of Tumbleweed (you might’ve figured out that I’m a Tumbleweed user by now): it uses snapper to create btrfs snapshots on every zypper (package manager) system update, and not only can you rollback a running system, you can boot older snapshots directly from the grub2 or systemd-boot bootloader. You can replicate this on pretty much any distro (btrfs support is in the kernel, snapper is made by an openSUSE member but available for other distros etc.), but it’s all integrated and ready to go out of the box. You don’t have to configure your package manager to automatically create snapshots with snapper, the btrfs subvolume layout is already setup for you in a way that makes sense, you don’t have to think about how you want to add these snapshots to your bootloader, etc.

So distros or their authors do a lot and their releases can be exciting in a way, but maybe not all of that excitement is directly user-facing.

What do you mean by “option for remote”?

Passed openQA in Tumbleweed, so should be available with 20241007.

This is the way.

Exactly. If anything, signs like these drag the attention away from the actual issue.

I just use whatever is included with the desktop environment. On KDE and GNOME launching an application involves pressing the Super (“Windows”) key, typing the first couple of letters of the application I want to launch and pressing the return key.

I might be missing something here but I don’t know how other launchers could possibly make this a simpler process.