3 ms·

Support for more clients... what does that mean? One of the reason I don't really use OTR as much as I would like to is that I cannot really take conversations

• Ihmahr 13y ago
  That is really an implementation of the app. The protocol does not prevent this in any way. You would need an app that somehow upload some info to the server and that synchronizes this info across your devices in a secure way.
  • xnyhps 13y ago
    Synchronizing that info accross your devices is exactly something you'd need a protocol for. If you want to preserve the forward-secrecy that OTR offers, then you can't just "encrypt, upload" on one client and "download, decrypt" on another. You somehow need to do a key exchange between your own devices.
    • deleted 13y ago
      [deleted]
• ef4 13y ago
  That's actually one of the main things that's addressed by this v3 protocol: > Both fragmented and unfragmented messages contain sender and recipient instance tags. This avoids an issue on IM networks that always relay all messages to all sessions of a client who is logged in multiple times. In this situation, OTR clients can attempt to establish an OTR session indefinitely if there are interleaving messages from each of the sessions. If you've ever tried to have multiple devices logged in to one account using OTR, and you've ended up with an endless spam of "invalid message, resending" or some such, this is what they're talking about. Clients that support v3 properly shouldn't do that anymore, and you should be able to keep both your PC and phone logged in without problems.
  • runn1ng 13y ago
    That seems great! Is there some app implementing it correctly, on both mobile+PC? (Linux will do)