Comment

themagzuz@lemmy.blahaj.zone ⁨5⁩ ⁨days⁩ ago

i honestly think that if revolt had federation, then it would be the obvious choice for me, but alas. personally i’m still hopeful for polyproto getting off the ground, but the boring realistic choice for the time being is probably something like XMPP + mumble

source

Sort:hotnew top

renegadespork@lemmy.jelliefrontier.net ⁨4⁩ ⁨days⁩ ago
I’m getting an HTTP 522 from that link. What’s Polyproto?

Also, is there a reason you’re not considering Matrix?

source
- themagzuz@lemmy.blahaj.zone ⁨4⁩ ⁨days⁩ ago
  oh yea their website seems to be down. surely a good sign… in the meantime, you can look at the website/spec through their codeberg repos.
  
  i’m not a huge fan of matrix because it seems very bad to selfhost. from my understanding, if anyone using your homeserver joins a big channel, your homeserver will have to store the entire history of that channel and keep it up to date. on top of that, it very much seems like the spec isn’t being developed by the community, but more that element implements some feature and then forces that into the spec. also polyproto claims to be much more resilient, allowing you to migrate to a new homeserver, even if your old one is already dead.
  
  also a lot of matrix’s funding comes from crypto, ai and venture capital, so i think it’s just a matter of time before the whole project becomes completely subsumed by capital interests
  
  source
aBundleOfFerrets@sh.itjust.works ⁨3⁩ ⁨days⁩ ago
It looks like polyproto doesn’t have any intent to implement voice chat or screen sharing?

source
- themagzuz@lemmy.blahaj.zone ⁨3⁩ ⁨days⁩ ago
  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)
  
  source