If we’re talking about the RTX 900/1000 series, they’re still supported on the 580 driver branch. They’re just not getting new features anymore. Most distros package these legacy drivers too.

It really should be shut down for Arch’s sake.

I think it should really be split into two parts:

1. The more widely used packages should be moved to an official repository with review procedures. Perhaps the (quality) requirements can be lower, but these must be reviewed by trusted people.
2. The remaining packages should be moved to user namespaces, like the other user-package repos do. That will at least prevent (most) takeover attacks.

the CPU is never taxed, albeit undervolted with minus 30 on all cores in PBO

In case of an unstable system, the first thing I would do is disable all overclocks (including PBO, EXPO, undervolt, …)

Do you think benchmark results like these are meaningful when comparing Linux distributions?

They don’t really provide any explanation for why it should be faster than CachyOS. So I’d take their claims with a bucket or two of salt.

I think the problem is that the license grant (that has been in place for a decade) is not that clear.

You are licensed to use compiled versions of the Mattermost platform produced by Mattermost, Inc. under an MIT LICENSE

• See MIT-COMPILED-LICENSE.md included in compiled versions for details

You may be licensed to use source code to create compiled versions not produced by Mattermost, Inc. in one of two ways:

1. Under the Free Software Foundation’s GNU AGPL v3.0, subject to the exceptions outlined in this policy; or […]

I read it as releasing the binaries under MIT and granting people an AGPL license for the (non-enterprise) code. Some read it as not granting you the full AGPL rights.

To me, the fact that they advertise Mattermost as “open-source” and the statement on the “reciprocal license” above indicates that Mattermost also reads this as an AGPL license grant. However, they don’t seem to be interested in fully clarifying the license situation. But, I think they would have a very hard time to argue in court that this license doesn’t allow AGPL forks. And I haven’t seen any evidence of them acting against any of the existing forks.

Eh, that post title is quite sensationalistic.

1. Nothing regarding the license has changed in the last 2 years.
2. It seems like they consider the non-enterprise code to be licensed under the AGPL:

Thank you for the community discussion around this topic. I do recognize that our licensing strategy doesn’t offer the clarity the community would like to see, but at this time we are not entertaining any changes as such.

UPDATE Feb 2, 2026: To be specific, our license is using standard open source licenses, a reciprocal AGPL license and a permissive Apache v2 license for other areas. Both are widely used open source licenses and have multiple interpretations of how they apply, as showcased in this thread.

When we say we don’t “offer the clarity the community would like to see”, that refers specifically to the many statements in this thread where different contributors are confused by other people’s comments and statements.

For LICENCE.txt itself, anyone can read the history file and see we haven’t materially changed it since the start of the project.

If you’re modifying the core source code under the reciprocal license you share those changes back to the open source community. If you’d like to modify the open source code base without sharing back to the community, you can request a commercial license for the code under commercial terms.

Maybe we can hold the pitchforks a while longer, unless they actually make a negative change.

And if any gaming will be involved I’d probably steer clear of either of them, since the available graphics driver will likely be outdated rather quickly.

Ubuntu LTS (and therefore Linux Mint) gets updated graphics drivers between releases, so the situation is not too bad. I’d say it’s good enough for most people. You only really have an issue if you want to buy a brand-new AMD/Intel GPU.

For comparison, Debian 13 (and LMDE) currently ships the Nvida 550 driver, while Ubuntu 24.04 ships the 580 driver.

I generally agree, but keep in mind that CPU TDP is not a good metric to predict the total power consumption of a home server. Most of the time, the CPU is in a very low power state and the power consumption is dominated by things like the mainboard, drives, PSU, … Wolfgang has a good video on the topic: https://youtu.be/Ppo6C_JhDHM?t=239

That said, the conclusion that the 5600U system draws more power than a N150 one is probably still correct in most cases.

The Ryzen 5000 series should be a good choice for such an application, they’re still quite powerful CPUs. You should just make sure that you get the notebook/APU variant of the CPUs (e.g. 5600G or 5600U) and not the desktop variant (e.g. 5600 or 5600X). The desktop variant has significantly higher idle power consumption (see e.g. https://www.reddit.com/r/HomeServer/comments/1l707yc/nas_idle_power_usage/, they report 50+W in idle, while my 8500G system idles at 17W). The one you linked should be fine.

Yeah, I looked into ARM or RISC-V options for a NAS, but ended up going with x86. Upstream Linux support is just a hard requirement for me. As the author points out, the support that you get from the SBC manufacturers is lacking at best.

Rust implies only 1 thing, and that’s no memory leaks, assuming you don’t use “unsafe” code. It’s still very much vulnerable to logic bugs and has the same performance as c (GNOME) and c++ (KDE).

Rust actually doesn’t guarantee that there are no memory leaks. I think the more important memory safety improvements are regarding use after free, out-of-bounds accesses, null pointer issues, and double free problems.

For me, it’s mostly interesting because it brings automatic tiling to a desktop environment. System76 has previously implemented this as an extension for Gnome, but they haven’t been too happy with that approach.

I think would also be good for the Linux Desktop community to have more than 2 strong desktop environments. Hopefully this would incentivize app developers to account for more than just a singe DE.

Read (only) access should be fine. What makes it complicated is if there can be writes from multiple locations. Basically, the simple version would be to just periodically copy the data from the primary to all secondary locations.

I can see why you’d want to go with an off-the-shelf NAS. But, I would carefully check if it supports your use case, as it’s quite advanced.

If the data only needs to be read & written from a single server (and the others are just backups), you can also use simpler replication instead of synchthing. E.g. syncoid or TrueNAS replication. It sounds like you should be able to do that with separate datasets per household in your usecase.

I would probably go with a simple approach like this:

• ZFS: Each house gets a “NAS” that provides a ZFS filesystem to store the data. This gives you the ability to share the drives across your use cases (you, rest of the family), snapshots, RAIDZ support, and usage quotas. For the OS, you could use what you prefer (TrueNAS, Debian, Ubuntu, …).
• Syncthing to synchronize the files across the servers/houses. This allows you to read and write data from anywhere and syncthing will mirror the writes to the other places. I use it to synchronize data across 5 devices and it works quite well.

There are probably more advanced (enterprise?) ways to handle the file synchronization. But, I think this hould be good enough for normal, personal use. The main disadvantage is that you’re only synchronizing the current data (excluding the ZFS snapshots). On the other hand, this also allows you to mix file systems if necessary.

Gnome and KDE are not doing the same thing.

KDE will continue to offer an X11 session for the time being:

Current status: Plasma’s X11 session continues to be maintained.

https://pointieststick.com/2025/06/21/about-plasmas-x11-session/

Gnome will disable the X11 session in the next release and then remove the code:

The most likely scenario is that all the X11 session code stays disabled by default for 49 with a planned removal for GNOME 50.

https://blogs.gnome.org/alatiera/2025/06/08/the-x11-session-removal/

I’m not quite sure what you’re trying to do here. Are you

1. Trying to create a new owncloud instance and put your data somewhere other than in /var, or
2. Try to move the data location of an existing owncloud instance?

If you’re trying to do the second one, there’s a useful guide on it here: https://omiid.me/notebook/25/move-docker-volume-to-bind-mount. The first one should be even simpler, you can just replace the volumes in the compose file by bind mounts (basically, just this step of the tutorial: https://omiid.me/notebook/25/move-docker-volume-to-bind-mount#modifying-docker-compose).

Forgejo became a hard fork about a year ago: https://forgejo.org/2024-02-forking-forward/ And it seems that migration from Gitea is only possible up to Gitea version 1.22: https://forgejo.org/2024-12-gitea-compatibility/