Re:Large-Scale Abuse of Contact Discovery in Mobile Messenge...
by walterbell on Monday April 19, 2021 @04:57AM
(#26860463)
For those who want end-to-end encrypted messages, it's a feature that the server doesn't have a persistent archive of message history. Wire messages are on the server for a few weeks, long enough to relay those messages to transiently offline devices. Telegram is great at what it does, different use case from Wire.
[ Parent
| on HN ]
Re:Large-Scale Abuse of Contact Discovery in Mobile Messenge...
by zibzab on Monday April 19, 2021 @05:37AM
(#26860769)
I'm actually fine with the wire approach.
But it would be nice if the sender could be notified that the message was never delivered.
Re:Large-Scale Abuse of Contact Discovery in Mobile Messenge...
by walterbell on Monday April 19, 2021 @06:08AM
(#26860983)
Each Wire message has a user-visible status: Failed, Sent or Delivered.
It's not obvious, but if status never changes from "Sent", then it wasn't "Delivered".
Re:Large-Scale Abuse of Contact Discovery in Mobile Messenge...
by ckozlowski on Monday April 19, 2021 @02:34PM
(#26866388)
There's a new icon now as well with an "eyeball" that tells you if the message was viewed. The option for this read receipt can be enabled in the options if both parties enable it.
Re:Large-Scale Abuse of Contact Discovery in Mobile Messenge...
by ajconway on Monday April 19, 2021 @05:10AM
(#26860590)
Matrix does have end-to-end encrypted persistent history.
Re:Large-Scale Abuse of Contact Discovery in Mobile Messenge...
by walterbell on Monday April 19, 2021 @05:23AM
(#26860681)
Yes, it's possible. Depending on your threat model, it may or may not be a good idea to have a long-term archive of encrypted data be subject to legal process. Matrix has plans to support IETF MLS, which is a necessary precursor to messenger interoperability.
Re:Large-Scale Abuse of Contact Discovery in Mobile Messenge...
by Arathorn on Monday April 19, 2021 @06:46AM
(#26861198)
Matrix lets you configure the history retention on a per-server or per-room basis, fwiw: https://github.com/matrix-org/synapse/blob/develop/docs/mess.... From a metadata perspective, we're working on P2P to avoid metadata accumulating on servers. In terms of the OP here (address-book based contact discovery), https://github.com/matrix-org/matrix-doc/blob/hs/hash-identi... is how Matrix optionally implements it while trying to preserve privacy.
Re:Large-Scale Abuse of Contact Discovery in Mobile Messenge...
by zeitg3ist on Monday April 19, 2021 @06:13AM
(#26861008)
Yeah, I guess it’s just a different use case, but it was a behavior I didn’t expect (maybe I didn’t read the “fine print”) and it turned me off using it for long-term stuff. It’s a pity because I liked the interface and features.