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

*If* we decide we need it, let's first think about what it is we want to do #1

Open
RieksJ opened this issue Dec 8, 2021 · 0 comments

Comments

@RieksJ
Copy link

RieksJ commented Dec 8, 2021

Simple forms of status lists, e.g. certificate revocation lists, already have privacy issues. The example in the draft text even shows a reason 'disciplinary action' that would be for all? to see.

I get that this is just the very beginning, but let's either stop (or leave this repo to quietly die), or otherwise let's first think about, and concretely specify

  • what the actual function(s) of it should be (so we know what we are, and are not, talking about)
  • whom it would serve, and how they would be using it (so we can decide that our 'solution' is actually fit for purpose)
  • which of the 'whom it would serve' we want, and which of those we do not want (sift the 'good' use from the 'bad' use)
  • which privacy concerns are (to be) addressed, and which are not.

And let's do that before many others, e.g. vc-ed/#9, or vc-status-list-2021/#2 are starting to refer to this or try similar things.

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