view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Friends don't let friends use Snap.
Proprietary when flatpak exists, and it doesn't properly address how apps should dynamically request access to things they need. Every time I've used either solution I've run into some permissions problem.
flatpak just makes sense imo
For desktop apps maybe. How do you run a flatpak from the cli? "flatpak run org.something.Command". Awesome.
Both suffer from not making it obvious what directories your application can access and not providing a clear message when you try to access files it can't. The user experience sucks.
The one thing snap does that flatpak doesn't is provide CLI applications. But then nix also does that, so snap can go pound salt.