121–130 of 204 posts
Earlier quoted context omitted.
Right now there are 4.5M registered users on the matrix.org HS alone, so I’m not sure niche is right ;)
An interesting number would be how many GCM/APN devices are registered in the matrix.org sygnal server. All of the Matrix/Riot users I know use private, non-federated home servers, but still rely on the project's Sygnal server(s) for push notifications.
I had to roll my own chat system recently because the open source solutions out there were surprisingly insufficient - nothing seems to support websockets. Looking forward to the French contributions to the ecosystem! For instance: at the moment Matrix server implementations expect clients like Riot to long-poll for JSON about each room/chat they're connected to. Alternatives like Prosody's XMPP server implementation…
Network overhead aside, long polling can be a pretty wonderful interface. “Give me what I don’t have yet, else let me know when there is something” makes for reliable transmission that is hard to screw up. Long polling requests can work idempotently and recover from network failures automatically. I think it’s an especially wise starting point.
Do the French make their own hardware? An encryption app is useless if you don't 100% trust the hardware. Tainted hardware could figure out, log and send your keystrokes from screen taps/swipes all from silicon.
Its a fallacy of composition to say that better security useless unless its perfect security. This is better that it was before. More security is better. Perfect security does not and cannot realistically exist for a complex system. I do think have a reproducible binary would be a huge win. Even if you can't verify the integrity of a single build you could verify that build by consensus.
Earlier quoted context omitted.
curl? O:-) Matrix is intended to be simple enough that you don’t even need an SDK unless you really want one. which java sdk did you try?
> Matrix is intended to be simple enough that you don’t even need an SDK unless you really want one. Huh. So Haskell + Servant might be really nice for writing a client, then, yeah?
What protocol? If you look at spec on their website[0] you'll see 4/5 of the protocols are still marked unstable. Take room state resolution as an example. It has pretty important security implications and it's nontrivial in a distributed setting. The algorithm is not stabilized, and it comes with a warning in the specification: Warning: This section documents the state resolution algorithm as implemented by Synapse…
We’re working towards a 1.0 atm, which the French govt and many others are counting on. In terms of state res not being well specified: https://matrix.org/_matrix/media/v1/download/jki.re/hSmkLkFG... is pretty comprehensive and should be merged into the spec relatively soon. I say kudos to the French govt for backing a FOSS project which is still evolving :)
Just wondering about discovery. How do I find interesting channels?
What protocol? If you look at spec on their website[0] you'll see 4/5 of the protocols are still marked unstable. Take room state resolution as an example. It has pretty important security implications and it's nontrivial in a distributed setting. The algorithm is not stabilized, and it comes with a warning in the specification: Warning: This section documents the state resolution algorithm as implemented by Synapse…
We’re working towards a 1.0 atm, which the French govt and many others are counting on. In terms of state res not being well specified: https://matrix.org/_matrix/media/v1/download/jki.re/hSmkLkFG... is pretty comprehensive and should be merged into the spec relatively soon. I say kudos to the French govt for backing a FOSS project which is still evolving :)
Earlier quoted context omitted.
> Matrix is intended to be simple enough that you don’t even need an SDK unless you really want one. Huh. So Haskell + Servant might be really nice for writing a client, then, yeah?
Anything you can make HTTP requests in really. I have messed around with sending messages from Ruby and Bash and it's quite easy. And a lot more easy if there is an SDK for your language which will handle a few things for you.
Earlier quoted context omitted.
If polish is broadly defined as "something that was hitherto still missing in (claimed-to-be) end to end encrypted chat applications", then open source and a decent profit model are definitely features lacking from WhatsApp. Telegram is open source, but one has to consciously turn on encryption and it doesn't work on the web or desktop clients (and the profit model is non-existent). Signal doesn't work without Google…
Very surprised to never see Keybase mentioned in these discussions. Everything, even the team chats, are end-to-end encrypted with a pretty slick interface. You can even send E2E-encrypted messages/files to people who haven't even joined yet! https://keybase.io/blog/keybase-chat
Earlier quoted context omitted.
We’re working towards a 1.0 atm, which the French govt and many others are counting on. In terms of state res not being well specified: https://matrix.org/_matrix/media/v1/download/jki.re/hSmkLkFG... is pretty comprehensive and should be merged into the spec relatively soon. I say kudos to the French govt for backing a FOSS project which is still evolving :)
I don't mean to be disrespectful. The first time I heard of Matrix/Riot was at OSCOn 2015. What has happened since then,and why has it taken so long to stabilize?
* implementing E2E encryption and getting it audited, which turns out to be very hard in a decentralised environment
* refining Riot as a flagship client and trying to get it to a Slack/Discord level of UX (still a work in progress)
* scaling, as the 1st gen implementation (synapse) failed to keep up with the growth of the network
* adding features like Jitsi video conferencing, Widgets, Communities, Home pages, Rich Text Editing, Read Receipts, Synchronised Read Markers and much much more.
* dealing with a major funding crisis last year.
In retrospect we probably should have spent more time finalising the current features rather than adding on new ones, and since the end of last year we've been feature-frozen in order to finish the stuff in hand and get to a 1.0.
Fixing the issues which remain in federated state resolution is probably the hardest problem to solve before a 1.0, and I'm happy to say that over the last few months we've made major progress in doing so.
Agreed that in an ideal world this would have all happened sooner, but turns out that decentralised open protocols are harder than centralised startups like Slack and friends. Who knew?
Earlier quoted context omitted.
Right now there are 4.5M registered users on the matrix.org HS alone, so I’m not sure niche is right ;)
An interesting number would be how many GCM/APN devices are registered in the matrix.org sygnal server. All of the Matrix/Riot users I know use private, non-federated home servers, but still rely on the project's Sygnal server(s) for push notifications.