MSC3813: Obfuscated events #3813
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
turt2live
reviewed
May 10, 2022
proposals/3813-obfuscated-events.md
Outdated
Comment on lines
3
to
19
| <!--*Note: Text written in italics represents notes about the section or proposal process. This document | ||
| serves as an example of what a proposal could look like (in this case, a proposal to have a template) | ||
| and should be used where possible.* | ||
|
|
||
| *In this first section, be sure to cover your problem and a broad overview of the solution. Covering | ||
| related details, such as the expected impact, can also be a good idea. The example in this document | ||
| says that we're missing a template and that things are confusing and goes on to say the solution is | ||
| a template. There's no major expected impact in this proposal, so it doesn't list one. If your proposal | ||
| was more invasive (such as proposing a change to how servers discover each other) then that would be | ||
| a good thing to list here.* | ||
|
|
||
| *If you're having troubles coming up with a description, a good question to ask is "how | ||
| does this proposal improve Matrix?" - the answer could reveal a small impact, and that is okay.* | ||
|
|
||
| There can never be enough templates in the world, and MSCs shouldn't be any different. The level | ||
| of detail expected of proposals can be unclear - this is what this example proposal (which doubles | ||
| as a template itself) aims to resolve.--> |
There was a problem hiding this comment.
don't forget to remove the template comments from the proposal :)
There was a problem hiding this comment.
Fixed in #tusooa/pull/1
Now #tusooa/pull/4
turt2live
added
proposal
i'll squash the commits later |
turt2live
added
the
needs-implementation
|
I wonder if this PR could be implemented along with MSC3414 ( #3414 ), both would mean a very high metadata resistance, which would benefit the privacy of users. The only thing I don't like about Matrix are the metadata leaks along with the centralized identity system. Anyways, It would be interesting to see how these two proposals scale to Matrix P2P. |
ghost
mentioned this pull request
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.