mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-12-24 01:42:10 +00:00
New note: Reporting API and informed consent
This commit is contained in:
parent
ca386ed375
commit
5da5ca4cb1
1 changed files with 13 additions and 0 deletions
13
content/notes/reporting-api-and-informed-consent.md
Normal file
13
content/notes/reporting-api-and-informed-consent.md
Normal file
|
@ -0,0 +1,13 @@
|
|||
---
|
||||
title: "Reporting API and informed consent"
|
||||
date: 2022-09-04T19:38:30-07:00
|
||||
replyURI: "https://github.com/w3c/reporting/issues/168#issuecomment-746633069"
|
||||
replyTitle: "pretty much all of the telemetry is used by websites in order to realize some clear benefits for the user"
|
||||
replyType: "DiscussionForumPosting"
|
||||
replyAuthor: "arturjanc"
|
||||
replyAuthorURI: "https://arturjanc.com/"
|
||||
---
|
||||
|
||||
Whether or not increasing a user's fingerprint (potentially crossing the uniquely-identifiable threshold) is "worth it" is something for the user to decide, not a webmaster. Studies need the consent of all subjects involved, even if researchers believe that it's in the subjects' best interests. Users can make informed consent after being informed of the scope of telemetry, how it will be used, and how it will be shared.
|
||||
|
||||
A user (like me) who visits a website one time probably doesn't care if the website "improves their experience" if they don't intend to re-visit it. They probably wouldn't consider "collect and share information about your setup, in exchange for a better site in the future" a fair trade. From the perspective of a one-time user, the Reporting API serves only to fingerprint.
|
Loading…
Reference in a new issue