48
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 25 Jul 2023
48 points (96.2% liked)
Selfhosted
40565 readers
251 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
it's partly because everything has public/private certificates, but also partly because there isn't much synchronization going on after the initial "push". if you shut an instance down and modify the database directly without informing other instances (say, you remove an account) then other instances will not be able to tell and will drift out of date, essentially making that specific thing unusable for any instance that has previously interacted with it. if you expand that out to, say, wiping and re-creating an entire database, then you end up with so much uncertainty that you may as well start over from a fresh domain