Lots of excitement today with confirmation of the EU's breakthrough #DMA legislation, mandating that big tech must provide documented open comms APIs. 🎉🎊😱 But there's also been concern that open APIs could undermine E2E encryption: our viewpoint is at https://matrix.org/blog/2022/03/25/interoperability-without-sacrificing-privacy-matrix-and-the-dma
I still have concerns with #Matrix and #privacy, https://www.aminda.eu/blog/english/2021/08/03/matrix-perfect-privacy-not.html#you-mentioned-privacy
In this case #WhatsApp would provide self-destructing messages that
@matrix doesn't support unless you count m.room.retention that is apparently experimental and shouldn't be used. https://github.com/matrix-org/synapse/issues/11279
Sure there is a ticket since 2016, but not much activity that I can publicly see https://github.com/vector-im/element-meta/issues/82
#Signal, for example, has had self-destructing messages for a long time, but if I send someone a password by means of a self-destructing message, I can be pretty sure the recipient will save that message somewhere before it disappears. And that "somewhere" is probably less secure than the encrypted message it is in Signal.
Same goes for every kind of self-destructing message: it may help to keep information private, but it's certainly not the silver bullet some think it is.
@mikaela @matrix #Interoperability doesn't mean that you have to have complete feature parity on all sides. (The text was already weakened to make the requirements even less strict; only some chats will be covered.)
For instance, bridging a Matrix room and an IRC channel makes no sense for an encrypted Matrix room.
If the rag-tag Matrix ecosystem can do it, it doesn’t seem unreasonable to think that a $600B company like Meta can figure it out too...
Amen!