@dymaxion @IzzyOnDroid @cstross
Using the same encryption protocol (like MLS, just standardized by IETF) or client-side bridging.
Top-level
@dymaxion @IzzyOnDroid @cstross Using the same encryption protocol (like MLS, just standardized by IETF) or client-side bridging. 3 comments
@dymaxion @IzzyOnDroid @cstross I can recommend to watch ideas how to deal with that on the DMA panel that Matrix(.org) uploaded recording of: https://www.youtube.com/watch?v=FDnUJXzVn3s Of course it's going to be hard job. |
@didek
If they use the same protocol, you end up with both lowest common denominator security and making it largely impossible to add features — and that's assuming interop even works. Client side bridging requires that every client implement every protocol, yielding the superset of vulnerabilities — and that's before we start dealing with how you present so many different sets of features in the UI in usable ways. Then we get to talk about how anti-spam is going to work in an ecosystem like this, not to mention impersonation, etc.
@IzzyOnDroid @cstross
@didek
If they use the same protocol, you end up with both lowest common denominator security and making it largely impossible to add features — and that's assuming interop even works. Client side bridging requires that every client implement every protocol, yielding the superset of vulnerabilities — and that's before we start dealing with how you present so many different sets of features in the UI in usable ways. Then we get to talk about how anti-spam is going to work in an ecosystem like this,...