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
So you need just 15 more users on your instance to break even, if you have 17 in total, you've saved 10 calls.
In this particular example, yes. But only if those 15 people subscribe to the exact same communities. If they don't, the calculation gets even more complicated.
Some people seem to be under the impression that setting up their own personal server is relieving the pressure on the network. What I trying to get across is that's not the case, unless it's being used by a reasonable amount of people.
I can't tell you what the sweet spot is - but my guess would be that it's only going to be at least several dozen, more if their interests (subscriptions) don't overlap very well.