Re: [push-api] Technique to Detect Endpoint Prior to register() (#95)

Just to say, I don't want this to entrench proprietary protocols.

If anything ships with proprietary protocol usage however, the Push API will be horrible to use for a developer and a user. Dev - has to handle the period before the open standard is supported. User - has to handle not getting it after granting permission or expecting stuff to work, it doesn't and then makes the web as a whole seem inferior.

We have two options - help by supplying the endpoint url and info before requiring permission to use push, or cross our fingers and hope that developers and users figure stuff out and deal with any unusual issues.

I hadn't considered treating the endpoint URL as leaking information on the user - although I imagine this just masks the issues and encourages the use of UA sniffing to infer the endpoint, for the dedicated developers. (i.e. you're on Safari, probably Apples Push Service, you're on Chrome, probably GCM etc).

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/95#issuecomment-69062582