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

Allow users to edit their own content - Minimal User Identity #48

Open
chadoh opened this issue Oct 23, 2017 · 3 comments
Open

Allow users to edit their own content - Minimal User Identity #48

chadoh opened this issue Oct 23, 2017 · 3 comments

Comments

@chadoh
Copy link
Contributor

chadoh commented Oct 23, 2017

Research needed. I'm not sure if this is even possible, prior to building some sort of authentication/identity system.

Goals:

  • Associate some sort of ID with a specific browser (probably separate from the username being added in author field on posts #47) which uniquely identifies a give user/browser and associates it with content they create (how? public/private key pair? public key signing of created content? sounds complicated! also, sounds risky to store a private key in local storage!)
  • If a certain user/browser has signed certain posts, also allow this user/browser to edit the caption (see Add captions to GIFs #28) and username (see author field on posts #47) associated with those posts

We may also want to limit post deletion to only the user who created the content. However, this requires discussion. Since people can post anonymously, it would be easy to infiltrate a board with loads of spam. We may want to give anyone the ability to delete any content, in lieu of any centrally manageable censorship ability.

@chadoh chadoh added this to the Step 3: UX and Boards milestone Oct 23, 2017
@chadoh chadoh mentioned this issue Oct 23, 2017
3 tasks
@chadoh
Copy link
Contributor Author

chadoh commented Nov 27, 2017

@AquiGorka how feasible does this seem to you, at this point?

@AquiGorka
Copy link
Contributor

Hmmm. I have seen that IPFS & YJS data can be signed and we could implement a only if you hold the key you can edit this type-of-layer without having to go full user/ownership on Thicket.

Feasible: sure. How long? No idea. I'd have to research.

@chadoh
Copy link
Contributor Author

chadoh commented Nov 28, 2017

Ok, maybe we can end here. Hopefully you/we can work on this the week of Dec 11.

@chadoh chadoh removed this from the Step 3: Make it functional milestone Nov 28, 2017
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

2 participants