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

Suggestion (most likely premature): Use unlisted toots and account attributes #2

Open
kyanha opened this issue Nov 20, 2022 · 0 comments

Comments

@kyanha
Copy link

kyanha commented Nov 20, 2022

I would like to suggest using unlisted toots to contain the appropriate data for remote users to establish e2ee sessions, replies to those toots to maintain updates (and to provide metadata for what key signs the new key for key continuity), and the use of one account attribute to provide a URL to the toot containing the root of the key continuity chain.

Since this is almost certainly premature as a suggestion (and offered by someone who has only the barest idea of Mastodon's privacy levels), I rather expect that this idea will get either summarily roundfiled, or put on the back burner until someone gets around to tearing holes in it. Still, it seems that it would be useful to do something like keybase did, albeit without forcing the key/account-claim data into everybody's feed.

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

No branches or pull requests

1 participant