Re: [w3c/push-api] Push subscription endpoint autodiscovery in HTML page: rel="alternate" type="urn:ietf:params:push" (#299)

There are no plans in adding such machinery.

We [decided](https://github.com/w3c/push-api/issues/243#issuecomment-286782918) against the bring-your-own-push-service model because it would negate a lot of the resource usage reductions enabled by the Push API. As far as I'm aware, none of the current implementations provides users with an option to change push service either, which would be a prerequisite to developing a discovery mechanism. This is captured in the [Security and Privacy Considerations](https://w3c.github.io/push-api/#security-and-privacy-considerations) in the specification.

-- 
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/issues/299#issuecomment-416556254

Received on Tuesday, 28 August 2018 11:53:42 UTC