In terms of an optimal load spread, it’s best if the lemmiverse is split into multiple equally sized instances. If you use an instance just for yourself, it doesn’t actually decrease the load on the main servers in any way. The only thing you get is a guarantee that your instance won’t suddenly go down.
If you use an instance just for yourself, it doesn’t actually decrease the load on the main servers in any way.
That’s not completely true. Yeah, it still loads another server a bit, but the server-to-server federation traffic is much more lightweight than the client-to-server traffic that would be involved with you having an account on that server and accessing it that way.
But yeah, multiple, equally-sized communities on different instances is the ideal situation. The only sticky part right now is FOMO because you’d have to constantly watch for new SelfHosted communities and join them. Hopefully some frontend tools come along soon to make joining/managing multiple communities like that more streamlined.
Yes, ideally you‘d want to have a few large communties on each instance and not all topics with a single userbase on one. This not only decreases the load but also prevents scenarios in which a single admin starts to capsule their instance with a large userbase away from the federation.
What kind of “control” do you mean? Your posts/comments get replicated across all the other instances. You can’t really “guarantee” a delete, since the other instances might just ignore your request for delete.
By control, I mean I can back up my data and ensure my comments, subscribed communities, messages, etc are all available to me no matter what, I don’t have to rely on some external third-party managing it for me.
In terms of an optimal load spread, it’s best if the lemmiverse is split into multiple equally sized instances. If you use an instance just for yourself, it doesn’t actually decrease the load on the main servers in any way. The only thing you get is a guarantee that your instance won’t suddenly go down.
That’s not completely true. Yeah, it still loads another server a bit, but the server-to-server federation traffic is much more lightweight than the client-to-server traffic that would be involved with you having an account on that server and accessing it that way.
But yeah, multiple, equally-sized communities on different instances is the ideal situation. The only sticky part right now is FOMO because you’d have to constantly watch for new SelfHosted communities and join them. Hopefully some frontend tools come along soon to make joining/managing multiple communities like that more streamlined.
Yes, ideally you‘d want to have a few large communties on each instance and not all topics with a single userbase on one. This not only decreases the load but also prevents scenarios in which a single admin starts to capsule their instance with a large userbase away from the federation.
Suddenly going down seems to be a constant in my self hosted services though…
Bow chicka bow wow
ayo gurl lemme go down on your stack
I wanna self-host my own instance so I have more control over my data.
I’m going to self host my own instance so I can have a cool username
What kind of “control” do you mean? Your posts/comments get replicated across all the other instances. You can’t really “guarantee” a delete, since the other instances might just ignore your request for delete.
By control, I mean I can back up my data and ensure my comments, subscribed communities, messages, etc are all available to me no matter what, I don’t have to rely on some external third-party managing it for me.
Yes, but we’re currently evolving into a situation where everything is centralized around Lemmy.world
Also the assurance that your home instance won’t be suddenly federated from one of the major ones