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.
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
It looks like polyproto doesn’t have any intent to implement voice chat or screen sharing?
i think for my purposes i'm fine with hosting that through a separate service, so instead of XMPP + mumble i would run polyproto + mumble (or some other voip solution, screen sharing seems to be a decent way away in mumble)
but (as i understand it), polyproto isn't a chat protocol per se, but more a protocol for federated message authentication. as an application of this protocol, they're building polyproto-chat, which is a chat protocol. in theory, one could then also build a polyproto-voice so you can use the same account for both chatting and voice calls. i still think this is pretty far away, considering how young polyproto is, which is why my current vision is chat and voice as two separate services (which i also prefer because i imagine it makes the technology simpler and hosting easier)