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

Questions from a web-USER (not a developer.) #56

Open
ParaplegicRacehorse opened this issue Oct 11, 2021 · 0 comments
Open

Questions from a web-USER (not a developer.) #56

ParaplegicRacehorse opened this issue Oct 11, 2021 · 0 comments

Comments

@ParaplegicRacehorse
Copy link

Lots of reasons why/how this could benefit developers -- especially developers who participate in the surveillance-economy -- but zero explanation about how this could benefit regular users.

As a user, I certainly do not want my computer or mobile device more accurately singled-out or identified by a some bit of injected js. Far too much of this is already happening without this.

If this is to be established as a standard, the question of how it benefits users and not just developers and site hosts, must be answered.

  1. What risks of abuse does this create? (I can think of dozens. Can you?)
  2. How are those risks mitigated in code?
  3. What benefit is provided to a site or web-application's users?
  4. What alternative means of providing [benefit] already exist?
  5. How does this improve upon prior art?
  6. In what ways is this inferior to prior art?
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