Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.