The Corporation behind and the Admins of Twitter can see your “Private Messages”
The Corporation behind and the Admins of Facebook can see your “Private Messages.”
The Admins of Mastodon can see your Direct Messages. They aren’t private.
With Mastodon, you can spin up your own instance and be your own Admin.
Ultimately, don’t use any of these tools for actual private messages. Use Signal, Matrix/Riot or another end to end encrypted messaging tool.
@tinker I think the admins of both instances (the sender and the receiver) are potential threats, since the entire communication resides in the database of both instances, though the admin interface apparently only makes it easy to see the local side of the discussion.
@jerry - Yeah. Thus a consideration of implementing END-to-END crypto in Mastodon DMs. An Admin can see the end.
There might be a way to do it where the private keys are stored on a Mastodon instance. Still accessible by a Mastodon admin, but with hidden with a strong password.
Something to look into as the platform builds out.
From instance to instance, it's end-to-end encryption on Mastodon, right?
So if you trust the admins, there's no real problem?
Or, GPG encrypt your messages
@hhardy01 - Yep!
Here’s an interesting thing. Mastodon has 500 characters. How long of a GPG message can you push on that?
@tinker @hhardy01 DM encryption would be great. Mailvelope has an open issue for ECC support, which would enable it without needing Mastodon cooperation. Looks like openpgpjs supports it already, which would allow someone to add it to the Mastodon web frontend. https://github.com/mailvelope/mailvelope/issues/451
@tinker It would be neat to see Mastodon implement signal protocol e2e encrypted chat as their DM system instead
@facts_the_alt - It would still only be End-to-End. And the admin controls one End. They’d still be able to read DMs. (E2E only protects data in transit).
There are ways to protect data at rest against certain types of privileged user, but not for what we’re talking about here.
Mastodon’s answer is to let you be your own admin. And for many, thats exactly what they do.
@facts_the_alt - I should say, this only applies if you want to read the messages clear from the web app. If you sent an encrypted message and downloaded it to your host, then your host (not the Mastodon instance itself) becomes the endpoint.
You can address this without needing Mastodon to do it. You just need a thick client that can send the encrypted message through the Mastodon network.
Wouldn't it be sufficient if profiles offered to enter xmpp and/or matrix ids? Instances could possibly offer a simple #xmpp server like #prosody. I don't see any other valid #e2e solution for any #federation compatible protocol except using gpg client sided like with email.
Maybe one should discuss to remove any "direct" or "private" message features from protocol in regard to the very common misunderstandings linked 2 those terms?
I am still not knowing enough about these, maybe this would be a way. But this would mean to make it a definite standard for mastodon clients and blew the complexity and dependencies of such up. On the other hand any further encrypted communication improves privacy for everybody, so maybe it's worth the resources? 🤔
@tinker and/or encrypt using a local only tool before transmitting over any medium
@Mycroft - Exactly.
@tinker Yeah, I've just casually given up on the idea that privacy and secrecy exist on the internet.
@tinker matrix e2e is not mature enough at this point of time but I am seeing it to be a damn good tool in the few years to come.
My thoughts on this subject https://github.com/Openmedianetwork/openweb/wiki/Security-privacy
A Mastodon instance for info/cyber security-minded people.