[RadiozRadioz]

I do hope they get what they need. If nothing else, I think they've chosen a solid and well-founded strategy to manage the situation - the focus areas they mentioned are more important than bridging. Maintaining bridges has always struck me as something hugely resource intensive. I applaud their stewardship.

My story with moving to Matrix is similar to many others. I was enthusiastic about it, managed to persuade my groups to try it out, but then everyone was "unable to decrypt message", lost confidence in Matrix and left. The frequency with which the Matrix folks have to repeat "this is fixed in Element X and Matrix 2.0" is worrying. They keep repeating it everywhere, constantly. This indicates to me that an extremely large percentage of people have dismissed Matrix and not looked at it since their initial bad impression. This is a tough challenge to overcome, so I see why they are prioritizing evangalizing the protocol over bridges. Reputation is valuable and they need to get it back, they're definitely trying. I hope they succeed.

[bluesomewhere]

Thank you! I am optimistic that we'll pull through.

And yes, I think you're right to be a bit worried about how frequently we need to ask people if they've tried Matrix recently. First impressions matter a lot, and a lot of early adopters had bad first impressions. At some point we need a more concerted communication and outreach strategy to address that issue.

[Arathorn]

the frustrating thing is that Element X really did fix the encryption issues. getting people to give it a second chance is hard though.

[tylergetsay]

I just downloaded it and there is no way to reset my password. I had to go to the element web interface to do so.

There is still a lot to do

[Arathorn]

This is probably because you’re using matrix.org, which hasn’t yet rolled out the new Matrix 2.0 authentication thet Element X uses (given it involves migrating 50M accounts or something). This is planned for March however.

[Arnavion]

It absolutely has not. I'm looking at messages in Element X right now that don't decrypt, ie "Waiting for this message", from one user interspersed between decrypted messages from other users. Meanwhile my other two clients (app.element.io and pantalaimon) happen to be able to read all of them.

[eredengrin]

This is quite rare but it did happen to me (exactly) once. Report it as a bug, they put very high priority on unable to decrypt reports and my issues stopped happening within a few days (can't promise that is always the result since I don't know what happens behind the scenes, but it won't hurt, and reporting bugs from within the app is pretty straightforward - hit the username icon at top left to get to settings, then "Report a problem").