You should do multi-account support in Element next, or at least make it easy to switch between different accounts. It's awesome that you made it work, but having one absurdly bloated monolithic account is not a usage pattern that should encouraged or enabled, for a variety of reasons, personally data-hygiene and privacy are the biggest ones for me.
Yes. This is requested many times (multiple accounts - one private and one for work is my use case as it is for many others), yet it is deferred and even put down from "Next" to "Later" on the public roadmap.
Multiple account support but only if I can use all of them at the same time (account per room setting & asking which account to join the room with). It should not be done like on Discord (you can switch to another account and then have to switch back to see a chat from the other account...)
- Awesome talk, awesome demos, awesome progress! - Mesh/P2P chat that actually works sounds like science fiction come true - Very hyped about governments, commercial entities, and standards bodies adopting Matrix / open technologies - Digital Markets Act sounds very interesting, hopefully that will allow interop with services like Viber which don't have third-party clients / Matrix bridges because they are extremely hostile to any third-party interop efforts - matrix-rust-sdk was painful / quite difficult to build on for me as a Rust/Matrix newcomer, didn't know it was heavily used internally which explains the learning curve - Personally still missing a hackable desktop client for power users offering customization / extensibility like mIRC/KVIrc offers for IRC, maybe full-fledged clients are still too difficult to build?
I was very impressed by the group call demo, and then y'all presented Third Room and I went nuts. Matrix has come a long way from where it was 5 years ago.
Did you set up secure message recovery when suggested by Element? I can see any other client forgetting to do that, but in Element it's a quite prominent popup on the top left.
This is not true though. Your encryption keys are stored encrypted by the recovery key you are asked to set-up at login or during your first E2EE convo. The server admin still doesn't have access to it. So it's either "have more than one device so they can share keys and don't send them on the server", "use the safe only you have the key for on the server to backup your keys" or both. In any case server admin never have access to the keys used in your conversations and cannot read your messages. See spec.matrix.org/v1.5/client-server-api/#secret-storage for the spec, and github.com/uhoreg/matrix-doc/blob/ssss/proposals/1946-secure_server-side_storage.md as well as github.com/uhoreg/matrix-doc/blob/symmetric_ssss/proposals/2472-symmetric-ssss.md for the spec changes leading to it.
Seriously incredible work, everytime I see Matrix it gets better and better!
Excited to see different codebases utilizing MatrixRTC for multiparty calls! :)
You should do multi-account support in Element next, or at least make it easy to switch between different accounts. It's awesome that you made it work, but having one absurdly bloated monolithic account is not a usage pattern that should encouraged or enabled, for a variety of reasons, personally data-hygiene and privacy are the biggest ones for me.
Agree - even just better identity management with things like making it easy to have a different display name in a different room or server.
Yes. This is requested many times (multiple accounts - one private and one for work is my use case as it is for many others), yet it is deferred and even put down from "Next" to "Later" on the public roadmap.
Multiple account support but only if I can use all of them at the same time (account per room setting & asking which account to join the room with). It should not be done like on Discord (you can switch to another account and then have to switch back to see a chat from the other account...)
Agreed! I thought of maybe putting another layer of a sidebar for accounts.
Like so: 'Accounts > Spaces > Persons/Rooms'
@@muellerhansthat seems bad from a privacy perspective
This is incredible, I feel very optimistic about the future, that we're correcting past mistakes.
So excited for the future of matrix!
Amazing, so much interesting stuff said on this conference
So awesome! 😲😲😲
Super!
Matthew sounds like he was a king in a past life.
Great presentation, and demo!
This is all great. Thank you for making this 🥳
awesome 👍
- Awesome talk, awesome demos, awesome progress!
- Mesh/P2P chat that actually works sounds like science fiction come true
- Very hyped about governments, commercial entities, and standards bodies adopting Matrix / open technologies
- Digital Markets Act sounds very interesting, hopefully that will allow interop with services like Viber which don't have third-party clients / Matrix bridges because they are extremely hostile to any third-party interop efforts
- matrix-rust-sdk was painful / quite difficult to build on for me as a Rust/Matrix newcomer, didn't know it was heavily used internally which explains the learning curve
- Personally still missing a hackable desktop client for power users offering customization / extensibility like mIRC/KVIrc offers for IRC, maybe full-fledged clients are still too difficult to build?
Great
Nice.
would love to have official support for flutter/dart sdk
XMPP is still good though! But these demos were pretty impressive.
7:56 Was that supposed to be February 2023?
yup, good spot :)
Does anyone already tried use the SFU?
I was very impressed by the group call demo, and then y'all presented Third Room and I went nuts. Matrix has come a long way from where it was 5 years ago.
Will a time come when we need Matrix address aliases like we use email aliases/masks to protect from spam or identification/profiling?
Nice but could you consider replacing Docs by Google with anything open (do your own Matrix based alternative, LOL)?
Libre office. Open office. These are some examples.
Matrix is the future of the decentralized web. Combined with Polkadot the future is looking quite Rusty indeed!
：００
Alright you're making it go vroom, but can you keep it from being unable to decrypt messages AND THUS LOSING CHAT HISTORY.
Did you set up secure message recovery when suggested by Element? I can see any other client forgetting to do that, but in Element it's a quite prominent popup on the top left.
It's either you let your server provider store your encryption keys, thus being able to read your messages, or you must never loose them.
Easy remedy is logging in on more that one device.
This is not true though. Your encryption keys are stored encrypted by the recovery key you are asked to set-up at login or during your first E2EE convo. The server admin still doesn't have access to it.
So it's either "have more than one device so they can share keys and don't send them on the server", "use the safe only you have the key for on the server to backup your keys" or both. In any case server admin never have access to the keys used in your conversations and cannot read your messages.
See spec.matrix.org/v1.5/client-server-api/#secret-storage for the spec, and github.com/uhoreg/matrix-doc/blob/ssss/proposals/1946-secure_server-side_storage.md as well as github.com/uhoreg/matrix-doc/blob/symmetric_ssss/proposals/2472-symmetric-ssss.md for the spec changes leading to it.
@@Matrixdotorg That's pretty much what i said, but in context of all messengers. Matrix is "or you must never loose them" part of my explanation.