Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add hint about no e2e encryption #1283

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Andre601
Copy link
Contributor

Mastodon does not yet support End-to-end encryption.

However, looking at the "Using the network features" page is this not mentioned anywhere within the direct messages section.
At most is there the small hint, that a direct message is just a post with a changed setting.

This is bad, as it doesn't tell the user, that the messages don't have any guaranteed protection against someone obtaining (and more importantly reading) their messages.

Of course someone can argue that mastodon has the note about no e2e encryption whenever you select the direct type, but this relies on using the Mastodon web-app (And I assume phone app), since 3rd-party services may not have such an important hint anywhere...
Also, if a user first reads the docs before using it in Mastodon itself should it be a good idea to inform them early.

On another, unrelated note was I also considering to add a note regarding mentioned users being added to a discussion, even if it wasn't the user's intent, as that too could be crucial information the user may want to know first. After all do you not want to share personal info in regards to someone knowing that they would be able to see it too because you mentioned them, right?
Either way, I decided to leave this PR focused on the e2e notice as this was a more important thing to mention. The other thing could still be added later on in another PR or commit.

@vercel
Copy link

vercel bot commented Aug 26, 2023

@Andre601 is attempting to deploy a commit to the Mastodon Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant