1538
Well well 🤨
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Jul 2023
1538 points (96.5% liked)
Selfhosted
40717 readers
259 users here now
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!
founded 2 years ago
MODERATORS
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.