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
They'll do it once, though. Then every time you view it, you're helping the bigger servers by serving it from your instance.
Yes. Once for every post, comment and vote.
So say you have your own personal instance, and you use that to follow community
newson lemmy.world. If throughout the day that community receives 10 new topics, 50 comments and 100 upvotes, it would have to make 160 calls to your server.So when you decide to read those 10 topics (if you even read all of them), you would then make roughly 10 api calls.
You would be saving those last mentioned 10 calls by using your own instance, but at the cost of 160 calls made throughout the day.
The thing is that when you interact with the remote server directly it's not 10 api calls, it's 10 full-blown HTML webpages that have to be served to you, which are way bigger than REST API calls.
Generally speaking, lemmy is much more cpu bound than it is bound by bandwidth - so the added bytes don't matter that much. The example above was just for 1 community. Now imagine the user is subscribed to a dozen communities, but doesn't even browse lemmy that day. That's probably thousands of api calls made to keep his server on sync, and 0 requests saved.
Like the big instances have literally hundreds of thousands of workers running in order to get all the updates out. If one of those calls fails, it gets put back into the queue for retry.
OP asked if having his server added to the lemmiverse would alleviate the load "Like with torrent". That is demonstrably not the case - it only adds more workload on the other servers, with a break even point that's highly variable. Yes, your server will be nice and snappy, but the origin servers have to pay the price - death by a thousand ~~papercuts~~ synchronisation calls.
Yeah you're right, I just felt the need to point out that API calls are not really comparable to serving a full website.
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.