XSF Discussion - 2020-07-05

  1. Zash

    LNJ: Maybe check or ask what existing implementations do, if that part is implemented anywhere.

  2. MattJ

    Just a heads-up that there may be some temporary unavailability of the mailing lists tomorrow (6 July) between 13:00-15:00 UTC. Jonathan will be upgrading the OS on that host. Best case, nobody notices :)

  3. pep.

    "email is reliable anyway"!!

  4. strypey

    jonas’: > I love it when people equate OMEMO and Jabber. The UX of OMEMO is part of the UX of jabber as a chat network.

  5. pep.

    no it isn't

  6. pep.

    it's part of the UX of set of clients that implement OMEMO at most

  7. strypey

    !XSF_Martin: > strypey: If you want to be able to decrypt your messages later on a new device you should use an e2ee without forward secrecy, If I can decrypt a message more than once using the same account on the same app/ device, it's only reasonable to expect that either a) I will be able to decrypt past messages by logging into the same account on a new app/ device, OR b) the encrypted history will not be loaded into the new app. Having message history that I can't decrypt appear in the new app is a UX fail on both counts.

  8. pep.

    But I'd say really "the UX of OMEMO" is part of the set of clients that want to have a similar UX. And different set of UX guidelines may have different incompatible UX for OMEMO, which is fine if their goal is not to interoperate.