@micahflee Another reason why the "Pick a server that you trust!" blurb on Mastodon's front page makes me skittish.
For me at least, there aren't any!
@lambadalambda @micahflee but that's the tool people are using. I use XMPP+OTR, e-mail+PGP, Signal, etc., but if somebody is not as tech-savvy but is already here, I don't see why they should not have the option of encrypting private messages.
Or, put a bit differently: https://mastodon.social/media/N9MHhHNBYckrKdO8bPc
@lambadalambda @micahflee Yes, that is a concern. Still better than nothing though.
Also, you're completely ignoring apps. If #Mastodon has official and standardized support for #e2e #encryption, apps can implement it, closing the JS loophole.
@pettter @rysiek @micahflee FWIW, I agree with @lambadalambda - it can be argued that private messages are simply a misfeature in OStatus since they cannot be truly private without extra (non-standard) hacks.
Keeping things simple is valuable; using the right tool for the job (some other protocol for private messages) is good engineering.
@lieselotte @pettter @rysiek @micahflee @lambadalambda Well, I'd venture that poor engineering usually leads to a poor user experience sooner or later. The fundamental user expectation is "software that works".
Mastodon and GNU Social and others could all agree to integrate XMPP (or even SMTP) for direct messages. It doesn't need to be in the OStatus protocol.
@lambadalambda @micahflee @rysiek Not completely. Riseup rolled out a system a few weeks ago that encrypts all emails with your login passwords. So if they have to hand out data, it will be encrypted data. https://0xacab.org/riseuplabs/trees
Philosophically: The same thing. Granted.
Practically: Huge difference if you ask me.