threads would be lit imo & replies showing HTML-escaped quotes and angle brackets seem like an obvious bug, idk what its markdown handling looks like yet
Conversation
grapheneos uses a bridge to a telegram channel which seems cool but would be nice to support without extra effort (i was into adversarial intercompatibility before cory doctorow named it)
1
2
Replying to
surprisingly the and matrix rooms do not have e2e encryption turned on according to the element app, they're meant to be public rooms but it's not clear what features you miss out on by enabling e2e
2
2
They're public rooms and not only can anyone join but anyone can view without joining. Matrix E2EE doesn't scale to a room with thousands of members and it would essentially brick them to enable it. It wouldn't provide privacy and would lose features like server-based search.
1
1
5
Also note that Matrix E2EE only encrypts message content. It doesn't encrypt any of the metadata for messages such as the time it was sent and who sent it or even emoji reactions to messages. It also doesn't encrypt state events like join, leave, kick, ban and the rest of them.
1
3
7
You can see how much it doesn't encrypt by making a new session and looking at your private rooms without cross-verifying your new session to get the keys synced to it. You can see everyone in the room, all the messages and state events, etc. You just can't see message content.
2
6
There are large public rooms with E2EE encrypted because they're sharing illegal content and want to make it substantially more difficult for servers to moderate it or handle takedown requests. It's mainly a way of certain sketchy servers to try to disown responsibility for it.
1
8
An E2EE public room is generally either a mistake or a strong sign the room is intended for sharing CSAM material and other illegal content. Certain servers are friendly to pedophiles but require that they use E2EE rooms in an attempt to disown the legal responsibility for it...
the material benefit of e2ee does indeed seem to be removed without also restricting new people from joining outside of hosting liability
1