While you're here, please consider supporting GamingOnLinux on:
Reward Tiers:
Patreon. Plain Donations: 
PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers:
Patreon. Plain Donations: PayPal.This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- Survive an elevator trying to eat you in co-op horror KLETKA when it releases February 19
- Draft code submitted to KDE Plasma turns it into a full VR desktop
- Proton Experimental brings updates for MonoGame, Rockstar Launcher and more
- Valve tweak Steam AI disclosure form for developers to clarify it's for content consumed by players
- No Rest for the Wicked co-op update lands on January 22 and it hit a big sales milestone
- > See more over 30 days here
How to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
How to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck- Casual/Social places for developer chatter
- simplyseven - Will you buy the new Steam Frame?
- eev - One-time logout
- Liam Dawe - Away later this week...
- Liam Dawe - Weekend Players' Club 2026-01-16
- grigi - See more posts
I realized there's actually a Windows security feature I would love to see expanded in Linux. Especially for proprietary packages.
Rep building. The "cheap" executable signing certificates require first a few thousands accepts before stopping to generate warnings.
We already have this somewhat with testing repos, but I would love to see this expanded into flatpak and maybe even something tailored for it.
Something like a torrent based package manager where you normally install things via GUI, but if it doesn't have enough peers yet only through the CLI with a special flag that when provided is only able to install packages with few peers.
So install without flag: only peer rich packages.
Install with flag: only peer poor packages.
It doesn't have to be peers. It could be any form of traceable recommendation, such as signed hashes.
You could even build a more complicated system rep building, with certain peers carrying more weight than others if they for example run comparable packages.
Someone with commentary on this brainfart?
repbuilding: containerized proprietary packages
Non-repbuilding: containerized reproducible builds, with the source code and license(FOSSness can as such be automatically checked by building it and hash-checking)
Non-repbuilding with root: distro packages
For reference the Windows scheme is:
repbuilding: 215.99$/yr and strict signature management rules.
non-repbuilding: 279.99$/yr and very very strict signature management rules.
Root: 500$/yr, Microsoft gets to read your code and has to sign off each update.