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

Hi @kael! 👋 I _think_ I understand what you're asking (please let me know if I've misunderstood), but we aren't planning to let sites specify their own push server.

One of the advantages of push is that the browser, or the device, only needs to maintain a single connection to receive messages. Supporting many push servers means the browser would need to maintain multiple persistent connections, one for each server. At that point, it would be more efficient for the site to open a WebSocket or `EventSource` stream to its own server, and bypass push completely.

Further, the browser and push service might use a different protocol; for example, Firefox uses JSON messages over a WebSocket, and I think FCM uses XMPP. In theory, RFC 8030 specifies this interface, too; in practice, I'm not sure if anyone implements it.

> The current way to discover the Push service with the popup is not perhaps the best approach from a UX perspective.
>
> For example, Firefox keeps pop'ing up notifications subscriptions request despite I had previously clicked on "Never", and although it's a matter of implementation, it's really annoying.

Ah, I see what you mean. "Push service discovery", in the spec, means "letting the browser connect to a different push server"...not "seeing if the site supports push," which I think is what you're asking about. (In fact, the permissions UI isn't related to the push server at all).

For Firefox specifically, you can block all notification requests by opening `about:preferences#privacy`, scrolling down to the "Permissions" section, clicking "Settings..." next to "Notifications", and checking "Block new requests asking to allow notifications".

But you're totally right that it's an implementation detail, and the spec doesn't (can't?) have an opinion on how a browser presents its permissions UI.

-- 
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-417156613