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!
view the rest of the comments
One of the devs mentioned that the biggest draw on server resources is the direct web interaction, and loading pages, not the behind-the-scenes federation, where the database queries are simpler and the actions can be queued up and retried as needed. (I think apps would have the same issue since the server's going to be doing the same kind of massive database queries to build your feed.)
If your comment takes a few minutes to get from your home server to another one when the site's overloaded, it's not a huge deal, but if your comment takes a few minutes to get from your browser to your server, the site's basically down.
So moving yourself to a new server takes over the entire real-time load you would have been using, and the additional background load of sending threads to/from your server is a lot smaller.