tsugu@slrpnk.net to Memes@lemmy.ml · edit-29 months agoChat Appskbin.runimagemessage-square294fedilinkarrow-up11arrow-down10file-text
arrow-up11arrow-down1imageChat Appskbin.runtsugu@slrpnk.net to Memes@lemmy.ml · edit-29 months agomessage-square294fedilinkfile-text
minus-squarewildbus8979@sh.itjust.workslinkfedilinkarrow-up0·9 months ago It didn’t have proper encryption back then. OTR predates all the commercial platforms adopting XMPP, so that’s not exactly true.
minus-squareSapphironZA@sh.itjust.workslinkfedilinkarrow-up0·9 months agoWas OTR a protocol where the server had zero knowledge of the unencrypted content? Or was it basically like SSL?
minus-squarewildbus8979@sh.itjust.workslinkfedilinkarrow-up0·9 months agoOTR is E2E, it’s the direct predecessor of OMEMO/Signal on which they are both based.
minus-squarebennypr0fane@discuss.tchncs.delinkfedilinkarrow-up0·9 months agoSure, but now you show me all the clients that supported OTR back then 😜 - or now, for that matter. Besides, OTR doesn’t work in multi user chats. OMEMO does, and support for it is still not exactly widespread…
OTR predates all the commercial platforms adopting XMPP, so that’s not exactly true.
Was OTR a protocol where the server had zero knowledge of the unencrypted content? Or was it basically like SSL?
OTR is E2E, it’s the direct predecessor of OMEMO/Signal on which they are both based.
Sure, but now you show me all the clients that supported OTR back then 😜 - or now, for that matter. Besides, OTR doesn’t work in multi user chats. OMEMO does, and support for it is still not exactly widespread…