Re: [push-api] Provide support for subscription association (#182)

How would we confirm that the `applicationServerKeys` match without storing it? (Or a hash of the value.) It feels like a bit of a footgun if we don't throw an error for this situation.

Regarding exposing it again - it could be added to `PushSubscription`, but then it might be best to just expose the entire `PushSubscriptionOptions` object. This won't be very straightforward to implement this in Chrome and has some overhead, but we can do it.

I could live with not exposing it for a v1 as well, but I suspect that we'll get use-cases for it pretty quickly (e.g. "do I have to cycle my subscription").

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/pull/182#issuecomment-176428636