Closed JMoVS closed 1 year ago
Duplicate of #7499.
@pixlwave doesn't seem to be the same as the recipient can decrypt the message
Sadly I believe its all related as the Rust crytpo isn't multi-process safe. We're disabling all extensions that write to the crypto db in #7618.
ok, thx
Sadly I believe its all related as the Rust crytpo isn't multi-process safe. We're disabling all extensions that write to the crypto db in #7618.
@pixlwave I believe a better way would be to move back to the old crypto unless Rust is fixed instead of removing elementary features which are part of Element since years (and any other messaging app).
How should we explain to our users that we've chosen the only platform where you can' share from other apps after we hardly worked to get people away from walled garden mainstream?
@jacotec I would suggest taking this to https://github.com/vector-im/element-meta/discussions there's not much I can personally do about the decision.
@pixlwave Is there already a discussion, or should I open a new one?
Steps to reproduce
Outcome
What did you expect?
No encryption error
What happened instead?
one message stating an encryption error and one that is the real message
Your phone model
No response
Operating system version
iOS 16.5.1a
Application version
No response
Homeserver
No response
Will you send logs?
Yes