THE CHAT PROTOCOL OF THE FUTURE
-
THE CHAT PROTOCOL OF THE FUTURE
-
THE CHAT PROTOCOL OF THE FUTURE
like with all things there is a solution: using terraform to manage the channels in the space
-
like with all things there is a solution: using terraform to manage the channels in the space
the terraform provider creates and owns the channel. it is the only user with the right to turn on encryption for said channels. voila. this is a perfectly reasonable solution.
-
the terraform provider creates and owns the channel. it is the only user with the right to turn on encryption for said channels. voila. this is a perfectly reasonable solution.
matrix E2EE channels are fucking stupid because they leak all sorts of metadata
for example, the topic is unencrypted
reactions are unencrypted
replies reference unencrypted MXIDs so you can tell what is being replied to even if the payload itself is encrypted
do not use them. do not waste your time on them. it is not worth it.
-
matrix E2EE channels are fucking stupid because they leak all sorts of metadata
for example, the topic is unencrypted
reactions are unencrypted
replies reference unencrypted MXIDs so you can tell what is being replied to even if the payload itself is encrypted
do not use them. do not waste your time on them. it is not worth it.
or as I put it in the Bundernet #known-issues room which is acting as an FAQ
-
R relay@relay.an.exchange shared this topic
-
I incentive moved this topic from Uncategorized
-
or as I put it in the Bundernet #known-issues room which is acting as an FAQ
@ariadne Matrix also allows unencrypted messages in encrypted rooms, and the information that a room is encrypted may not reach a client. I reported this to both clients and the matrix spec, but was told that this was expected behaviour both times ("because we want to allow bots"). Dumbest E2E impl out there.
-
R relay@relay.infosec.exchange shared this topic
-
matrix E2EE channels are fucking stupid because they leak all sorts of metadata
for example, the topic is unencrypted
reactions are unencrypted
replies reference unencrypted MXIDs so you can tell what is being replied to even if the payload itself is encrypted
do not use them. do not waste your time on them. it is not worth it.
@ariadne is this something that could be fixed or is it too fundamental to how Matrix works?
