51–60 of 99 posts
Earlier quoted context omitted.
How so less appropriate? Lack of link to Matrix? Going out of beta we had to decide on something which was really carrying what the app is, we loved Vector but it has always been a code-name and a nice pun on Matrix :) Riot is more representative of what the app can do and its ambitions! Break the barriers between apps, give the control back to the user to choose their client, if they want to encrypt, host themselves…
People probably associate the word with people rioting in the street which is a terrible link... I don't get why you would rename Vector, feels like everyone recommending 'Vector' to friends and family has wasted their time.
Looks like this is a rebranding of the existing Vector app. Here's the blog post from the creators: https://medium.com/@RiotChat/lets-riot-f5b0aa99dc8e#.3toozs7...
Indeed, it is exactly that. The old title of this post reflect that. I don't know why it was changed.
Link to the server repo? Only seeing clients on GH.
Others are in development at http://matrix.org/docs/projects/try-matrix-now.html#servers but they are all alpha at the moment.
Earlier quoted context omitted.
sigh As parent said, XMPP covers all of these cases with plugins. The FAQ you link says, over and over again, "the base setup doesn't cover these features, but plugins do," and doesn't explain away writing improved plugins or XMPP spec extensions. All I see is "buttt it'ss haaaaarrdddd". > Rather than fighting over which open interoperable communication standard works the best, we should just collaborate and bridge e…
shrug Matrix actually has a good point about the spec extensions though: if your spec is that minimal, nobody is going to be able to agree on what feature set to support. As a Schemer, I can attest to that. >Absolutely dripping with irony. As is your comment. Matrix made a different set of design tradeoffs, and is a legitimate protocol in its own right. And yet every time it pops up on HN, people complain about how w…
If that were true, nobody would agree on which Matrix features to support either. What difference would it make if Matrix just-so-happened to be defined as "XMPP, plus the following extensions..."?
> As a Schemer, I can attest to that.
It's one thing to say "the Scheme spec is too minimal; I'm going to make Racket a hard dependency", it's quite another to say "the Scheme spec is too minimal; I'm going to invent my own Python derivative"
It's really good. I recommended it to 7 people and every single one liked it, even got 5 of them to set up their own federated homeservers. We're thinking about moving a ~60-people skype group there as well.
Only issue I had is Synapse hogging the CPU and getting laggy with a large room (#matrix:matrix.org with its 4 thousand members). I'm using scaleway's 3 EUR/month Starter VC1S server for Synapse though. Hopefully it will get even better with time.
Anyone else reminded of https://xkcd.com/927/ ?
An end-to-end solution for interop between the two ought to be insanely high on the priority list. By this I mean it should be braindead obvious if I want to try one of them how to chat with a user of the other. Obviously this is bigger than just the protocol but so what, it's the problem that needs to be solved.
I can't even imagine how working together would not be top of everyone's mind in this space, since chat is all about network effects. The incentives to cooperate are huge.