

As someone who has a 1x11, all I have to say is:
Push click, push click, push, push… push…
As someone who has a 1x11, all I have to say is:
Push click, push click, push, push… push…
Honestly, I’ve had access to tons of Nvidia cards (1050, 1060, 1080, 3070, etc). All of them worked great for gaming whenever I tried in Debian or Ubuntu, using whatever drivers were latest at the time.
The ONLY place I had issue was specific settings (HDR + 120hz over HDMI) in Bazzite. I wanted a new card back then anyway so I got an AMD. But I’ve heard their Nvidia image is great, now.
And providing needed context that drinking more is an option.
Before you get too far, consider setting up users with a domain like Samba-Domain. This way you get centralized user management for anything you decide to host alongside it.
Also, ZFS is great for backups.
Are you using/going to use LibreOffice or OnlyOffice? Libre is more popular, but Only was built for web and has better MS compatibility.
I bet this could be used to load balance regional servers with a bit of tweaking. (I made Plex-sync a long time ago for a similar purpose)
“Immutable”: A term to describe Linux operating systems that do not follow the traditional filesystem layout where every single file can be removed by the user with root privileges. It is more nuanced than this in the case of Bazzite, but is still considered “immutable” from the point of view of the extended Linux community. The Bazzite team would not describe Bazzite as an “immutable” operating system.
https://docs.bazzite.gg/General/terms/
I’m a big fan of Bazzite, but as stated in the docs, “immutable” is a term the community uses to describe it.
Education is the key to reducing confusion, not pretending a system architecture doesn’t exist or matter.
Pretend your running a live OS off a read-only USB, yet any changes (app installs, config changes, etc) you make are saved to the HD. A new version of the OS comes out, so you write a new ISO to your USB, and upon booting it, all you changes are applied on top.
This is a simplistic view of immutable distros, but thwy wrk more like snapshots. It allows for rollback. So you install v1, then v2 is a newer snapshot of the base OS, v3 is another, always building.
The catch is they often require apps to run under things like flatpak so you don’t have to alter the OS packages. Personally, I’m not a fan for a daily driver, but it’s great for distros like Bazzite.
Since OP didn’t mention, the pasted content is not the full article. Click through and read it if you like, as since it’s Medium, it helps the author out. 😉
Wut? You’re responding to a trend graph for Fedora’s immutable (Atomic) forks.
Built on Fedora’s rpm-ostree system, Bazzite uses an immutable design with atomic updates and rollback functionality.
https://en.m.wikipedia.org/wiki/Bazzite_(operating_system)
But yes, since the trend chart is showing immutable distros and how Bazzite is growing, I am saying the fact that Bazzite is immutable has nothing to do with it’s growth.
Edit: Reading again, I realize you might not know that Fedora Atomic is the immutable base. 😉
A lot of answers here, but some are dated, as the “fix” isn’t in the models. MCP is a main fix for items like this. It’s a standardized protocol for LLMs to talk to tools and data stores, like calculators and dictionaries. This way the token effect doesn’t matter, and system prompts only need a small configuration which process much faster.
Everywhere I have lived and visited that was car centric has had local dairy farms with ice cream nearby. Lucky? Or do I just look around more than others?
I designed one of these that works with an XBox controller. It was clip-on, but would be easy enough to make magsafe with a $0.20 magnet ring.
Calibre is a fantastic peice of software. Buuut…
I’m surprised people still use it so much. With server software that does mostly the same thing for general use cases (even Calibre-web, but more Kavita and the like), I can’t imagine so many people using a desktop tool. Is it habit?
This helps for context: https://techcrunch.com/2025/08/21/ecosia-has-offered-to-take-stewardship-of-chrome-and-its-not-a-bad-idea/
TLDR; If the lawsuit goes bad, and Google is forced to sell Chrome, it’s a way for them to retain ownership while working with an existing partner to overcome the monopoly ruling.
Still a win win in my book.
But “being immutable” is not why Bazzite is growing.
All fair. For me, their SSL direction is a good one. Most self-hosters use a central proxy, so why maintain one users just ask to disable.
I do run mine behind a VPN, always will and recommend others do the same.
The upward trend is not because Bazzite is immutable.
Bazzite is not growing because it’s immutable.
Well, I wouldn’t say the media issues are worse than a full domain access issue, but despite my comment above, I agree with you.
The security split-issue feels reminiscent of when Plex didn’t use SSL and wouldn’t implement it until a white-hat POC token exploit was produced and provided to them (of which I was the author). If JF was my project, these would be top of my list.
Syd and Mackey for cycling.
Jammy Gits for adventure.