Re: [w3c/push-api] Rephrase the bit about the UA chosing the push service (#287)

beverloo commented on this pull request.



> -          There is only one <a>push service</a> per <a>user agent</a> and it cannot be changed from
-          the default value. This limitation is due to a variety of performance-related concerns,
-          including the complexity of running reliable <a>push services</a> and the impact on
-          battery lifetime if there were an unbounded set of <a>push services</a> to which a device
-          could connect.
+          The <a>user agent</a> is responsible for choosing the <a>push service</a> used for
+          creating <a>push subscriptions</a>. There usually is a pre-existing relationship between
+          the <a>user agent</a> and the <a>push service</a> due to a variety of performance-related
+          concerns, including the complexity of running reliable <a>push services</a> and the impact
+          on battery lifetime if there were an unbounded set of <a>push services</a> to which a
+          device could connect.
+        </p>
+        <p class="note">
+          While the contents of a <a>push message</a> are encrypted [[!WEBPUSH-ENCRYPTION]], the
+          <a>push service</a> is still exposed to the metadata of messages sent to a
+          <a>push subscription</a> such as their frequency, timing and size.

Done.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/pull/287#discussion_r134448172