Pretty sure that this requires the client to actually honor this setting. If you use another client you can probably just disable it anyways, but im not 100% sure on that. But yeah do not use the matrix.org server, that is like matrix rule number 1 in any introduction to matrix. The people running matrix.org have said themselves that they dont want any more users, which is why they started implementing limits for users that dont pay them.
Read receipts aren’t end to end encrypted.
Reactions aren’t either.
You should be able to disable it clientside.
What the fuck?
Basically the only thing actually encrypted in matrix e2e are the message contents itself. All other possible types of associated metadata, aren’t.
Is there a given reason for this? Is it something they’re working on changing? I know very little about cybersecurity, but that sounds like a suboptimal situation.
- There are efforts to encrypt more information and metadata, and to reduce the extent metadata can be correlated
- The primary reason that things aren’t encrypted is to allow the server to perform necessary parts of the protocol, like deciding who is in a room, what the title of the room is and to whom should messages be delivered.
I wonder if something like onion routing could be helpful?
Good to know, thanks!
I didn’t know that could be possible. Clients can generally disable it, and server software like Continuwuity can also toggle it off at the server level.
Perhaps you should try with a different provider
