Interesting to see that "end-to-end crypto" is becoming a frontpage feature for messaging apps.
Vector is now called Riot
21–30 of 99 posts
Re: Vector is now called Riot
#22First impressions:
- Hmm... sounds a lot like Apache (née Google) Wave
- Intro thingy has definite zombo.com vibe
(yes, I do realize that I'm getting old..)
On a more serious note, this could be really good concept if executed well. Time will tell, I hope for the best.
Re: Vector is now called Riot
#23Anyone else reminded of https://xkcd.com/927/ ?
Absolutely; as much as the Matrix people claim they're not doing that by "interoperating with other protocols" they don't seem to understand that it's exactly what they're doing. The existing standards (XMPP) already interop in exactly the same way (gateways/transports), so making another protocol instead of improving the gateway / transport story on an existing one is just silly.
Mmm... I wouldn't quite call it silly. The protocol does support better stuff than XMPP. We're talking about single view notifications across multiple clients and other goodies sometimes implemented by XMPP plugins. And quite frankly from what I've heard the plugins are a pain. I do think a fresh break is what's needed.
Re: Vector is now called Riot
#24Earlier quoted context omitted.
Absolutely; as much as the Matrix people claim they're not doing that by "interoperating with other protocols" they don't seem to understand that it's exactly what they're doing. The existing standards (XMPP) already interop in exactly the same way (gateways/transports), so making another protocol instead of improving the gateway / transport story on an existing one is just silly.
Mmm... I wouldn't quite call it silly. The protocol does support better stuff than XMPP. We're talking about single view notifications across multiple clients and other goodies sometimes implemented by XMPP plugins . And quite frankly from what I've heard the plugins are a pain. I do think a fresh break is what's needed.
I don't disagree that XMPP has problems, like anything, but having multiple federated protocols defeats part of the purpose of federation. Also, as far as I can tell, Matrix just carried over most of the same problems because they don't have 20 years of fixing edge cases and making sure things are scalable and easy. I'm not sure why plugins would be a pain; I'm sure making recommendations could be done better, but otherwise they're no more difficult to implement than the same things in the Matrix core spec. A fresh break is most cretainly not what's needed; we just need people to volunteer their time and effort and help make things better, not make up new protocols to compete with the old ones and make the messaging ecosystem more fragmented than it already is.
Re: Vector is now called Riot
#25Chat Services Timeline (https://cdn.sameroom.io/chat-timeline.pdf) needs another update.
Re: Vector is now called Riot
#26> "Riot is more than a messaging app"
This said to me "Riot is just a messaging app" and I bounced. I'd recommend changing that tagline to indicate briefly why a user might use Riot instead of Slack or Whatsapp
Re: Vector is now called Riot
#27> "Riot is more than a messaging app" This said to me "Riot is just a messaging app" and I bounced. I'd recommend changing that tagline to indicate briefly why a user might use Riot instead of Slack or Whatsapp
Riot is based on Matrix. If you scrolled down, it would tell you that it's got strong crypto, you can run your own servers, it's got really good cross-protocol bridges, and a ton of other stuff. And it's totally free, save the cost of running your own server if you choose to do so.
Re: Vector is now called Riot
#28First impressions: - Hmm... sounds a lot like Apache (née Google) Wave - Intro thingy has definite zombo.com vibe (yes, I do realize that I'm getting old..) On a more serious note, this could be really good concept if executed well. Time will tell, I hope for the best.
It's based on the Matrix protocol, which you may have heard of. So, yes, it bears more than a little resemblance to Wave by way of IRC, and was built to fix IRC's problems (lack of identity, poor netsplit tolerance, weak extension support, etc.), and also provide strong capabilities for bridging between protocols, so it doesn't wind up in an xkcd.com/927 type scenario.
Re: Vector is now called Riot
#29[deleted]