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
What's the selfhosted component of this?
Self hosting your own private P2P voice service.
Optionally use your device as a Audio relay for group calls, in which case you become the 'server' to all connected clients.
You do realise that's a contradiction, right?
Unless you're hosting a TOR node (which is outside of the scope here and, in the case of exit nodes, extremely risky), there's nothing here that's relevant to self-hosting.
I don't agree with that. Both sides are acting as a server and a client, connecting via a onion service to either parties rendezvous. And then when you include the fact that you can become a relay, that is clearly self hosting a server in a pure sense.
There are no exit nodes involved in onion services. It all stays within the network.