-
Notifications
You must be signed in to change notification settings - Fork 21
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
Rate limiting does not seem related to privacy #154
Labels
privacy-tracker
Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
Comments
pes10k
added
the
privacy-tracker
Group bringing to attention of Privacy, or tracked by the Privacy Group but not needing response.
label
Jul 18, 2024
darktears
added a commit
to darktears/device-posture
that referenced
this issue
Jul 19, 2024
We don't have rate limiting mechanism since the posture changes are triggered by a human interaction (opening/closing the device for example). Also posture changes are not happening often and rapidly. Fixes w3c#154
I'd just add that the text is fairly recent -- it was added in #145 although it was kind of rewording and reorganizing existing content. I agree that the section doesn't look like an actual mitigation, but rather a description of how the API works. |
darktears
added a commit
to darktears/device-posture
that referenced
this issue
Jul 22, 2024
We don't have rate limiting mechanism since the posture changes are triggered by a human interaction (opening/closing the device for example). Also posture changes are not happening often and rapidly. Fixes w3c#154
darktears
added a commit
that referenced
this issue
Jul 22, 2024
We don't have rate limiting mechanism since the posture changes are triggered by a human interaction (opening/closing the device for example). Also posture changes are not happening often and rapidly. Fixes #154
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.
This issue is being filed as part of the PING review requested here w3cping/privacy-request#136
Section 10.4.2 notes that the API is rate limited as a strategy for protecting user privacy. I do not think this is provides any privacy improvement. My understanding from the PING call is that this is legacy / cruft text, and not related to the current API. I suggest removing or reworking this subsection then
The text was updated successfully, but these errors were encountered: