Live data from Hacker News

Matrix 2.0: The Future of Matrix

matrix.org

41–50 of 283 posts

Re: Matrix 2.0: The Future of Matrix

#41
post #27

Earlier quoted context omitted.

What's the problem with e2e encryption for those organizations? The problem is if they give those orgs a backdoor

Oh yeah, I actually asked them about that. They said there aren't any backdoors[0]. We're all good, no worries! :) :) [0] https://mastodon.matrix.org/@element/110340953550548309

Its open source and the crypto library is also 3rd party verified. I don't get your problem.

Re: Matrix 2.0: The Future of Matrix

#42

> Therefore to use Element X, you need to be running a homeserver with Sliding Sync support, which (for now) means running a sliding-sync proxy which bolts Sliding Sync support on to existing homeservers. I am excited to try out Element X, but I do not want to administer yet another service, namely the Sliding Sync proxy. From a practical perspective, Sliding Sync (MSC3575) is still on the level of a proposal/experim…

Well you can just wait. But the proxy is really lightweight and doesn't require maintenance.

Re: Matrix 2.0: The Future of Matrix

#43

I love matrix - I've been running a Synapse homeserver for over 2 years now for friends and family. We love it. Despite minor problems (upgrading postgres for example) it has been smooth sailing. I really want to stay up to date but they don't make it easy! I'd love to add sliding-sync to my existing docker stack, but I feel like I'm in way over my head!

I love the idea of matrix (synapse + element + mobile apps) and I have started moving my family there too but we had so many problems with notifications not being sent to the phone unless you actively open the app.

There is a huge discussion about that on git and some can't reproduce, some can't get a single notification even though the apps notification checkmarks were all green.

So it had a very very low WAF [1] and I scrapped it sadly. This was a few years ago, any signs of these problems still existing?

[1] https://en.wikipedia.org/wiki/Wife_acceptance_factor

Re: Matrix 2.0: The Future of Matrix

#44
post #15

Thoughts on how this will get us towards when libre software privacy&security type people are ready to advise friends to move to Matrix for personal communication? (To be clear, the platform has to be all open source and open standards, actually decentralized, guided by those principles -- not an effectively proprietary play even if nominally open. For example, you should be able to get all the same functionality wit…

Matrix 2.0 is a major step towards getting friends & family on Matrix. Firstly, it's not introducing new features - it's just making the current featureset work super-efficiently (while retaining compatibility with today's Matrix). So there should be no fragmentation between Element/Fluffychat/Thunderbird, with the possible exception of the new scalable encrypted VoIP conferencing (but then very few Matrix clients im…

element still has serious usability issues that need to be fixed before i can get friends or family on board.

the way threads are displayed in the browser versions makes them hard to follow. in our hackerspace, where many are tech minded people, i see regular complaints about that.

scrollback to unread messages often fails. i have never had another chat application where that was a problem. this should just work.

the handling of encryption keys is very confusing. there are to many moving parts, it's not clear what i must save so that i can restore the keys in a new client.

private rooms are also confusing. i want to have a private room be the name of my chat partner, and they want it to carry my name. being able to do that would be very helpful.

i am also missing the ability to use a different nickname in every room. different groups know me under different nicknames. discord and wechat can do it. it would be great if matrix/element could do that too.

Re: Matrix 2.0: The Future of Matrix

#45

Regular reminder Matrix/Element work closely with law-enforcement to provide encrypted comms for them. It's a sector Matrix/Element actively markets to and deals with. My personal view is I'm not using a chat platform designed/developed by an organization so eager to partner with governments and law enforcement agencies. There's Element's Chief Product Officer & Managing Director presenting at the European Police Con…

I find no issue that the company is working with law-enforcement to provide secure communications. In fact this makes me feel better about the security of those communications as they are trusted by these governments (not that this is a huge mark of quality, but I would consider it positive).

I your distrust of law-enforcement so strong that any company that they purchase from must be untrustworthy? Or is there another reason that this bothers you?

Re: Matrix 2.0: The Future of Matrix

#46
post #43

I love matrix - I've been running a Synapse homeserver for over 2 years now for friends and family. We love it. Despite minor problems (upgrading postgres for example) it has been smooth sailing. I really want to stay up to date but they don't make it easy! I'd love to add sliding-sync to my existing docker stack, but I feel like I'm in way over my head!

I love the idea of matrix (synapse + element + mobile apps) and I have started moving my family there too but we had so many problems with notifications not being sent to the phone unless you actively open the app. There is a huge discussion about that on git and some can't reproduce, some can't get a single notification even though the apps notification checkmarks were all green. So it had a very very low WAF [1] an…

I had this problem 2 years ago and it ended getting fixed. Recently I seen it again and the problem was that my container running synapse did not have working DNS which caused all notifications to stop working. Once I fixed up resolv.conf all was working.

I am not suggesting that was your issue but it might help somebody.

Re: Matrix 2.0: The Future of Matrix

#47
post #44

Earlier quoted context omitted.

Matrix 2.0 is a major step towards getting friends & family on Matrix. Firstly, it's not introducing new features - it's just making the current featureset work super-efficiently (while retaining compatibility with today's Matrix). So there should be no fragmentation between Element/Fluffychat/Thunderbird, with the possible exception of the new scalable encrypted VoIP conferencing (but then very few Matrix clients im…

element still has serious usability issues that need to be fixed before i can get friends or family on board. the way threads are displayed in the browser versions makes them hard to follow. in our hackerspace, where many are tech minded people, i see regular complaints about that. scrollback to unread messages often fails. i have never had another chat application where that was a problem. this should just work. the…

Encryption in Matrix is a nightmare. I set up Synapse and pulled half a dozen or so people onto it. We have a few chat rooms. Randomly different users clients are unable to decrypt the messages of other users clients. You click some button about syncing encryption keys, and nothing happens. Then randomly a week later you can start reading each others messages again. shrug This has been going on for years now.

This alone makes Matrix the worse chat platform out there from a users perspective IMO. I invested too much effort in getting things up and running and using it now though, so I'm just hoping that this gets fixed one day, or something better comes along that I can migrate to.

Re: Matrix 2.0: The Future of Matrix

#48
post #43

I love matrix - I've been running a Synapse homeserver for over 2 years now for friends and family. We love it. Despite minor problems (upgrading postgres for example) it has been smooth sailing. I really want to stay up to date but they don't make it easy! I'd love to add sliding-sync to my existing docker stack, but I feel like I'm in way over my head!

I love the idea of matrix (synapse + element + mobile apps) and I have started moving my family there too but we had so many problems with notifications not being sent to the phone unless you actively open the app. There is a huge discussion about that on git and some can't reproduce, some can't get a single notification even though the apps notification checkmarks were all green. So it had a very very low WAF [1] an…

Hmm… we haven’t had notification problems like that in many years, from memory. Any idea if this was trying to deliver push notifs to Android without using Google? (Which historically has been painful thanks to Android OS versions terminating the app in the bg).

Element X has totally rewritten notification code (given it’s moved from Kotlin to Rust) and should be much more robust for bugs like this.

Sorry you got bitten by it.

Re: Matrix 2.0: The Future of Matrix

#49
Just a question, I haven't been paying attention, but where is Matrix on resolving the Nebuchadnezzar vulnerabilities, and is the project still tracking towards switching to MLS instead of Olm/Megolm?

Re: Matrix 2.0: The Future of Matrix

#50

How Matrix decentralisation is an improvement over Jabber's decentralisation? (disclaimer: I have no knowledge about neither spec, I'm not suggesting Jabber was better)

IIUC Jabber never really had decentralized group chats? It had MUC but these were federated, so if the server hosting the room went down the chat also died.

Matrix rooms are fully decentralized and can survive any servers failing.

(Although note that not much else in the protocol is decentralized, much of it is only federated.)

Post reply on HN