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

Conflicting advice about switching networks #8

Open
estark37 opened this issue Apr 24, 2016 · 1 comment
Open

Conflicting advice about switching networks #8

estark37 opened this issue Apr 24, 2016 · 1 comment
Assignees
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. report-delivery Covers the core delivery of reports via HTTP

Comments

@estark37
Copy link

http://w3c.github.io/reporting/#delivery says: "The user agent MAY choose to withhold report delivery entirely until the user is on a fast, cheap network in order to prevent unnecessary data cost."

http://w3c.github.io/reporting/#network-leakage says "For example, we could drop reports if we change from one network to another."

While these are both just suggestions, the conflicting advice would be confusing to an implementor.

@dcreager dcreager added the report-delivery Covers the core delivery of reports via HTTP label May 22, 2018
@clelland clelland self-assigned this Jul 29, 2022
@npdoty npdoty added the privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. label Sep 15, 2022
@jyasskin
Copy link
Member

I think @clelland said we now drop reports if the user changes networks. I have one detailed question, and then we just need to specify this. Should we:

  1. record the user's network(s) when the report is created and only send it on that network, or
  2. record the networks an environment settings object connects to over its lifetime, and only send reports on those networks?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
privacy-tracker Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response. report-delivery Covers the core delivery of reports via HTTP
Projects
None yet
Development

No branches or pull requests

5 participants