5 ms·
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/_matr
by Arathorn 9y ago
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/hSmkLkFGVUnrXjtYcjsCUsyS 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 :)
- bgorman 9y agoI 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?
- Arathorn 9y agoWe spent massive effort working on: * 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?
- Arathorn 9y ago(oh, and we rewrote (almost) the whole thing in Go, too)
- acct1771 9y agoI saw someone bitching elsewhere about Python 2.7, but have yet to see any other semi-relevant complaints yet, so congrats to the team on that! Any comment on that?
- lub 9y agoThere is progress on Python 3 support: > Preparation for py3 (PR #3061, #3073, #3074, #3075, #3103, #3104, #3106, #3107, #3109, #3110) Thanks to @NotAFile! https://github.com/matrix-org/synapse/releases/tag/v0.28.0 https://github.com/matrix-org/synapse/releases/tag/v0.28.0
- egeozcan 9y agoGo is a great choice for implementing a network protocol but most of the time, rewriting is not a great choice (source needed). Do you have any public discussions or blog posts about this decision?
- fredoliveira 9y agoWhy would rewriting not be a great choice?
- ysleepy 9y agoSecond System Syndrome [1] and General experience [2] mostly because legacy systems contain a lot of implicit features and undocumented decisions that are hard to re-discover and customers get really annoyed. Maybe less of a problem in this case since it is young and rather well defined domain. [1] https://en.wikipedia.org/wiki/Second-system_effect https://en.wikipedia.org/wiki/Second-system_effect [2] https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ https://www.joelonsoftware.com/2000/04/06/things-you-should-...
- indescions_2018 9y agoI discovered Matrix through the Godot Game Engine community. It was described to me as the next-gen irc freenode chat platform for open source devs ;) Just wondering about discovery. How do I find interesting channels?
- xf86alsa 9y agoOne of the community members has a bot that travels from room to room anytime somebody mentions a room link. The list (and graph!) of all indexed rooms is here: https://t2bot.io/voyager/ https://t2bot.io/voyager/
- diegoperini 9y agoThat graph burned downed my house (Macbook Air). :)
- xf86alsa 9y agoThe bot gets around!