Haven’t used GNOME for a while, but I guess that’s a problem of open source projects in general. Though GNOME at least has Red Hat behind it.

I don’t think Fedora has a “stable” channel. It has “testing” repo from which updates are pushed to “updates” repo after approval, and that’s it. My understanding is that ublue’s “latest” channel follows Fedora’s “updates”, while “stable” seems to update weekly (though it’s unclear what happens if a package update arrives in Fedora just before “stable” image is about to be built)

Does it use the same flawed approach as Manjaro by indiscriminately delaying all updates (including critical security fixes)?

Fedora is a bit too eager to deliver new updates IMO, especially KDE. As much as I love KDE, their .0 releases have had serious bugs several times in a row now. It’s always better to wait for .1 patch with Plasma. It may be hard for the user to break Kinoite, but it won’t save them from bugs.

Fedora’s mission have always been to push new stuff when it’s “mostly ready” at the cost of inconveniencing of some users, so I wouldn’t recommend it for non-tech-savvy people.

I know people say that it’s 100% stable for them (as they do for Arch, Tumbleweed, Debian Sid, etc) but that’s survirorship bias. As any bleeding edge distro, Fedora has its periods of stability that are broken by tumultuous transitions to the new and shiny tech (like it was with Pipewire, Wayland default, major DE upgrades, etc). During these times some people’s setup will break and you don’t know ahead of time if it will be yours.

You can still install RPMs through dnf. There is also dnfdragora AFAIK. Packagekit (cross-distro API and daemon that abstracts package managers like dnf and apt) is a pile of crap anyway, and is a source of many GNOME Software’s issues.

It does. This discussion is about Fedora where packagekit works with dnf and RPMs.

Not just synonymous, it the official name of DE itself.

Everyone who have use Twitter in the past 2 years is a nazi.

Arm is insanely fragmented, every device must be have dedicated drivers and hardcoded specific configuration in the kernel. And sometimes even separate kernel builds. Also Snapdragon X devices are not even fully supported upstream in the most recent kernel yet. Which means they are many years away from being supported in Debian. Unless someone makes a fork of Debian with latest kernel and not yet upstreamed Qualcomm specific patches (which how these “arm distros” are usually made).

It’s mirroring micronews.debian.org, not Twitter.

That’s the other way around. It’s an OpenGL driver that uses Vulkan under the hood. OP would need the opposite to have Vulkan on his card, but I don’t think it’s possible given that Vulkan is a lower-level API compared to OpenGL.

Well, login gating worked for Facebook, Instagram and Twitter (it’s not dead yet despite some people’s claims). We here are tiny minority of social media users.

They are currently A/B testing blocking access to videos without an account. That’s why some people are getting errors. It’s likely that it will be rolled out to everyone in the future.

How many NATO soldiers have experience fighting a full-scale war on their territory against an enemy with similar technological and production capabilities?

Anything Musk-related is a relevant content on Fediverse.

Frame it as Islamic terrorism to further prop up western alt-right parties.

Nope. My Galaxy S23 is unlocked and it has Facebook and Meta crap installed as “system” apps. Same with an older Sony phone.

Your are right, it’s not implemented yet in Plasma Wayland. It must be done in Plasma/KWin itself since top-level Wayland windows can’t position themselves on screen and don’t even know their coordinates (and doing it on the application side is not really correct since not all apps will support it and it duplication of work and code, while compositor can do it consistently for all windows). However it just doesn’t work yet.

That’s also true, but I have experienced an occasional issues when it would be stuck on downloading some package at 10 KiB/s because of bad mirror. Parallel downloads likely wouldn’t have helped in this case since it would select the same mirror. Obviously both issues need to be fixed though.

I’ve got a problem with port forwarding I can’t get working, never had that problem before and I don’t know network stuff well enough to figure it out.

Docs says that CachyOS has UFW firewall enabled by default. You can search how to configure it, it seems quite easy.

The updates are the winner for me- I don’t know how long this has been a thing with arch but downloading multiple packages at the same time. Game changer. I love Tumbleweed, but a 2gb “zypper dup” downloading package by package could take me 30 - 60 minutes.

It’s usually the issue with automatic mirror selection. If you interrupt zypper using ctrl-c (only when it’s downloading, not installing of course) then it should select a faster mirror next time you run it. Zypper devs really should work on this though.