Our great sponsors
-
-
matrix-doc
Discontinued Proposals for changes to the matrix specification [Moved to: https://github.com/matrix-org/matrix-spec-proposals]
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
Git
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
I wish Matrix would instead focus on fixing all the existing encryption usability issues instead of these new features:
https://github.com/vector-im/element-web/issues?q=label%3AA-...
I would love to migrate my family to Element (and also friends, and eventually also recommend it to employers if they're ever choosing something other than Teams) but can't until it's reliable as webmail. I also wrote this comment:
https://news.ycombinator.com/item?id=25271512
Sorunume suggested just + then later Alch-Emi made the case for just #.
https://github.com/matrix-org/matrix-doc/pull/1772#discussio...
Matrix's bot support should be excellent? It's arguably more robust than Discord's given it's an open API and there are tonnes of SDKs and bots building on it: https://github.com/turt2live/matrix-bot-sdk, https://matrix.org/docs/guides/usage-of-matrix-bot-sdkhttps:..., etc.
What do you mean by 'smart widgets based on url'?
Solving conflict resolution should be doable - it's just that it's literally the most critical and important bit of the entire Matrix ecosystem, and any changes have to be done very deliberately and carefully, ideally with formal proofs that it's not going to break stuff. It's the equivalent of switching out Git's merge algorithm (https://github.com/git/git/blob/master/Documentation/technic...) or switching out for a new kernel scheduler implementation. Any bugs or thinkos there mean that the whole fabric falls apart, hence wanting to consider it separately to Spaces.