The gamescope micro compositor does make games run better. You can obviously run that on others distros as well, but on SteamOS it’s out-of-the-box.

Is SteamOS immutable though? I thought that was just Bazzite.

Thank you a lot, this also seems to be a great list. And it comes with list of lists as well! I will have a deep look and see which games match my criteria.

Hi! Although the engine is free, the game assets seem to be proprietary. Still thanks for sharing the suggestion.

Thank you for this recommendation, but although the code is GPL-2.0, some of the assets for BAR are proprietary.

Thanks a lot. This seems to be a very complete list, I will have a look and see which ones match my criteria. If you have any one you like in particular, feel free to share.

Thank you very much, I will have a thorough browse and filter the games that match my requisites. If you have any one you like in particular, feel free to share.

Fair enough, in that case let’s add it. But if you don’t mind me sharing my opinion: you say everywhere that it’s a pre-release software, and the 0.x.x version supports this hypothesis. If you think it’s ready to be considered a completed project (but not necessarily also finished) you might want to be more explicit about it.

Hi! So nice to see you here!

I hope you don’t mind, I would prefer to only keep finished games on this list. There already are lots of awesome curated lists which include pre-release FOSS games.

You might have a point… I didn’t post on Reddit because it doesn’t feel like a place where I belong, Lemmy does.

Unfortunately GitHub still feels like a place where I belong, as that’s where most of the FOSS devs publish, despite its proprietary nature.

I do realize the irony. Perhaps when Forgejo federation will be fully implemented and enabled on Codeberg I will stop hosting on GitHub and hopefully other devs will too. But for now I think that’s what makes the most sense.

Unfortunately GitHub is the most popular, but if GitHub bothers you I understand, so here’s a copy hosted on my self-hosted forge.

https://git.fabioiotti.com/bruce965/awesome-foss-games

Personally I tried Bazzite because it was the recommended distro for a gaming device, and I liked it so much that it quickly became my main.

Bazzite may present a bit more friction if you want to do something “advanced” that would otherwise be trivial on other distros perhaps with just a couple terminal commands, but it makes all the “simple” things super-duper easy, and the system is almost impossible to break.

I would say this model makes sense for “ordinary” users that just need a computer to read email, view cat videos, open office documents, and in the specific case of Bazzite also gaming. In my specific case I also needed to write code (I use VSCode + Godot), besides the initial friction of learning to work with containers and SELinux, Bazzite seems to be fit for coding.

Thus, I hope immutable distros will stay and thrive. I hope that one day someone will make a distro that you can just set and forget on your grandma’s laptop, and I think this distro should be immutable, like Bazzite.

No, only the local FS. But they have recommendations in their README for integrating with S3 with the help of other tools.

You are invited to join the CopyParty! This has a web UI accessible from the browser, also from mobile, files are stored directly on the filesystem (not encrypted or on a database) and you can mount it as a network drive on Windows and Linux. But it doesn’t let you sync files for offline use, at least not without the help of some auxiliary tools.

You won’t find anything simpler to install and configure than this.

Thanks for sharing your opinion and expanding.

In the past I used to think the same. Or rather, probably naïvely, I considered the GPL to be a bit of a nuisance, and preferred LGPL or MIT software.

Now I’ve changed my mind and started preferring AGPL for all my code. If a big company likes your MIT or LGPL code, they can legally steal it. If it’s GPL at least you get some safeguards, but they can still take it and put it on a server without the need to release the source code. That’s why I started to believe AGPL is the only “safe” license approved by the OSI, at least at the moment.

Of course I agree that MIT and GPL or LGPL make sense in some cases, but I would say in general they don’t protect users’ freedom anymore in today’s cloud-first world.

I would say AGPL is the “safest” license still approved by the OSI. Could you share your opinion?

I am not OP, but that would be the ideal solution for me. Unfortunately, KPXC does not support communication with the GPG agent and the team is not interested in adding this feature due to it being «[…] far more complicated than ssh-key management. There are already excellent tools for this, Kleopatra being the best».

You will have to transfer your containers before you can see them.

From Docker to Podman: full migration to rootless

Perhaps a bit unconventional, but CloudFlare R2 gives 10GB of free storage accessible as S3 with rclone.

Ah I see… I keep container configs in a specific directory, which contains one directory per-service, which contain all the config files + a compose.yml file to place them in the correct path in the container. I could commit everything to Git if I wanted to.

Regarding network and firewall, you could make a symlink to a versioned file and keep your config with the containers. Same for firewall rules.

I’m not sure what you mean by file sharing permissions. With containers you could give a different user to each service.

If you are worried about memory and disk usage, another option I’ve been exploring recently is using OverlayFS, which, among other things, allows you to inject a directory at a specific path. Again, this would let you keep all your configs where you fancy the best. I use it through Bubblewrap.

Anyways I realize that what I just described is far from standard… hopefully other users will suggest something less custom.

If your goal is to host services, I would recommend looking into Docker, and eventually Podman. Containerization lets you keep the configuration wherever you want, personally I use a dedicated a directory for each service.

Also, please note that a container is not a VM. It’s just a way to keep everything in one place.