Skip to content
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

Reporting API #3

Open
pes10k opened this issue Jul 22, 2019 · 1 comment
Open

Reporting API #3

pes10k opened this issue Jul 22, 2019 · 1 comment

Comments

@pes10k
Copy link

pes10k commented Jul 22, 2019

https://w3c.github.io/reporting/

Reporting API aims to be a generalization of CSP reporting, but for use in other cases (crash reports, network errors, deprecation errors, etc).

I think we should not implement unless its opt in, for two broad reasons:

not user serving
This is explicitly designed to help web application developers, an individual user, at the margin, sees no benefit from it (and some harm / privacy risk). Its a favor from the user to the site owner, and should be treated as such (e.g. opt in). w3c/reporting#168

privacy concerns
These have a weird lifetime (they live beyond the lifetime of the page), currently have no restriction on who they can be communicated to, they send message as POST so less info for URL based blocking to operate, etc. w3c/reporting#169

My vote is to push for making the above changes to the standard, w/ the current authors, and to revisit a brave position if thats not successful

@fmarier
Copy link

fmarier commented Jul 22, 2019

That second link should be w3c/reporting#169.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants