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

Remove the rate limiting section per PING review. #155

Merged
merged 1 commit into from
Jul 22, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 1 addition & 17 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -613,8 +613,7 @@ <h4 id="identifying-users-across-contexts">
</p>
<p>
This theoretical attack is mitigated by [[[#data-minimization]]],
[[[#user-attention]]], [[[#user-mediated-action]]] and
[[[#rate-limiting-change-notifications]]].
[[[#user-attention]]] and [[[#user-mediated-action]]].
</p>
<h4>
Cross-origin iframes
Expand Down Expand Up @@ -687,21 +686,6 @@ <h4 id="user-mediated-action">
user's learned expectations for an outcome of such an action.
</p>
</section>
<section>
<h4 id="rate-limiting-change-notifications">
Rate-limiting change notifications
</h4>
<p>
The API is designed to minimize the rate at which posture state
changes are reported. A change is only reported throught this API
when an implementation-defined threshold is crossed per [=posture
values table=]. Given the small number of states and a wide range
of angles that correlate with the default
"{{DevicePostureType/continuous}}" state, the rate of notifications
is limited. We playfully call this mitigation a physical
human-computer interface rate limiter.
</p>
</section>
</section>
</section>
<section>
Expand Down
Loading