71
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Nov 2026
71 points (74.1% liked)
Linux Gaming
28478 readers
230 users here now
Discussions and news about gaming on the GNU/Linux family of operating systems (including the Steam Deck). Potentially a $HOME away from home for disgruntled /r/linux_gaming denizens of the redditarian demesne.
This page can be subscribed to via RSS.
Original /r/linux_gaming pengwing by uoou.
No memes/shitposts/low-effort posts, please.
That includes posts generated by LLMs. It doesn’t matter if you “don’t have the time” or “would’ve written the same anyway”, or if “everyone’s doing it geez get with the times”.
For now it’ll also include “AI”-assisted projects that haven't had at least two months of (public, verifiable) dev time behind them.
Resources
Help:
- ProtonDB
- Are We Anticheat Yet?
- r/linux_gaming FAQ
- Fork of an earlier version of the above
- PCGamingWiki
- LibreGameWiki
Launchers/Game Library Managers:
General:
Discord:
IRC:
Matrix:
Telegram:
founded 3 years ago
MODERATORS
The only thing I really use them for is to disable internet for open source applications that I trust aren't malicious, but might still have telemetry in them.
However don't let perfect be the enemy of good. Flatpak permissions are a step forward, at the very least defining a permission framework. Initially, permissions were defined but every app had all permissions, since app devs were lazy. Now, app devs are being better about defining what permissions are needed. In the future I imagine that Linux and Flatpak will lock down the security, making the permissions more concrete.
It's a step by step process.
Then I'll keep installing software I need but don't necessarily trust using Flatpak 👌