3 ms·
Meh. I wouldn't (and didn't) trust Keybase anyway. My reasoning is that you're given some encryption software (keybase javscript on its website or browser exte
by znpy 8y ago
Meh. I wouldn't (and didn't) trust Keybase anyway.
My reasoning is that you're given some encryption software (keybase javscript on its website or browser extension) but the software is changing all the time: it might get re-downloaded on a tab refresh, the extension might download a "new version" or whatever... So basically you're supposed to trust an always changing piece of code (can you be auditing every piece of javascript that you download? every version of that javascript?) and you running in a super-connected runtime (like a browser). What could possibly go wrong?
I am not an encryption expert at all, but I feel a lot safer doing my crypto on a regular environment (linux shell or whatever) and then sending the cyphertext via any other mean (web, email, whatever).
Back in the day you could use pidgin to chat on the Facebook chat, and it was possible (and relatively easy) to use the OTR plugin to have really end-to-end encrypted chats. But (guess what?) Facebook later disabled the possibility interacting with its chat via external non-facebook-branded clients (afaik)
- fastball 8y agoFacebook later disabled the possibility interacting with its chat via external non-facebook-branded clients (afaik) I don't think that's true, actually. The existence of Caprine[0] seems to suggest otherwise! 0: https://github.com/sindresorhus/caprine https://github.com/sindresorhus/caprine
- als0 8y agoI remember when Pidgin OTR worked fine with the old Facebook Chat, which I believe was based on the XMPP protocol. The move to Facebook Messenger deprecated this API and I don't think it works anymore. In the case of Caprine, it appears not to use any official API and is just scraping the web page for the right elements. This seems quite fragile and also a non-trivial body of code.
- znpy 8y agothis is exactly what i meant. thank you.