Updates spec, removes section

w3c · Jun 27, 2019 · 5f6795d · 5f6795d
1 parent 26ab42f
commit 5f6795d
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 2 deletions.
diff --git a/explainer.md b/explainer.md
@@ -273,5 +273,3 @@ full power of showing a native badge.
 
 ### Security and Privacy Considerations
 The API is set only, so data badged can't be used to track a user. Whether the API is present could possibly be used as a bit of entropy to fingerprint users, but this is the case for all new APIs.
-
-A potential concern is that a web application could trick users into unnecessarily opening the application by showing a badge. By opening the application, the user could unintentionally expose private information. This is similar to the risk posed by notifications.
diff --git a/index.html b/index.html
@@ -111,6 +111,7 @@ <h2>
         If the application's badge is <b>nothing</b>, the badge is said to be
         "<dfn>cleared</dfn>". Otherwise, it is said to be "<dfn>set</dfn>".
       </p>
+      <p>Note: The API is set only, so the badge data cannot be used to identify users.</p>
     </section>
     <section>
       <h2>
Original file line number	Diff line number	Diff line change
Expand Up		@@ -273,5 +273,3 @@ full power of showing a native badge.

		### Security and Privacy Considerations
		The API is set only, so data badged can't be used to track a user. Whether the API is present could possibly be used as a bit of entropy to fingerprint users, but this is the case for all new APIs.

		A potential concern is that a web application could trick users into unnecessarily opening the application by showing a badge. By opening the application, the user could unintentionally expose private information. This is similar to the risk posed by notifications.