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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
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.