You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
What risks of abuse does this create? (I can think of dozens. Can you?)
How are those risks mitigated in code?
What benefit is provided to a site or web-application's users?
What alternative means of providing [benefit] already exist?
How does this improve upon prior art?
In what ways is this inferior to prior art?
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: