From 70094e474509f4abfa6b2853615dfd6a772599b0 Mon Sep 17 00:00:00 2001
From: "Menard, Alexis" <alexis.menard@intel.com>
Date: Fri, 19 Jul 2024 09:34:46 -0400
Subject: [PATCH] Remove the rate limiting section per PING review.

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
---
 index.html | 18 +-----------------
 1 file changed, 1 insertion(+), 17 deletions(-)

diff --git a/index.html b/index.html
index 24dd034..f4a6736 100644
--- a/index.html
+++ b/index.html
@@ -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]]], [[[#user-mediated-action]]].
         </p>
         <h4>
           Cross-origin iframes
@@ -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>