this post was submitted on 18 Jan 2026
52 points (94.8% liked)
Selfhosted
60210 readers
951 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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Disclaimer: I might be talking out of my ass here but this is how I think it works, to the best of my knowledge.
The safest way would be to make an instance that only hosts the communities; it has no users and therefore federates no subscriptions of other communities who’s content you may need to police for stuff like CSAM that isn’t caught right away. You’d only need to monitor and moderate your own communities created on the instance.
I’m not sure but you might need one account to be an admin/ moderator for the communities you create? Just don’t subscribe to any off-instance communities with it and it shouldn’t federate those posts.
Folks on other communities will interact with it via someone from their instance subscribing to it; so discoverability might present an issue.