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

Not sure we're talking about the same thing.

I was thinking to HTML autodiscovery mechanisms:

```html
<!-- ATOM/RSS -->
<link rel="alternate" type="application/atom+xml">
<link rel="alternate" type="application/rdf+xml">
<link rel="alternate" type="application/rss+xml">

<!-- OpenSearch -->
<link rel="search" type="application/opensearchdescription+xml">

<!-- PWA -->
<link rel="manifest">

<!-- XMPP XEP-0240: Auto-Discovery of JabberIDs - https://xmpp.org/extensions/xep-0240.html -->
<link href='xmpp:pubsub.jabber.org?;node=xeps' rel='alternate'/>

<!-- PuSH - https://pubsubhubbub.github.io/PubSubHubbub/pubsubhubbub-core-0.4.html -->
<link rel="hub">

<!-- Salmon Protocol - http://www.salmon-protocol.org/salmon-protocol-summary -->
<link rel="salmon">

<!-- Webmention - https://www.w3.org/TR/webmention -->
<link href="http://aaronpk.example/webmention-endpoint" rel="webmention" />

<!-- GitHub WebSocket (dunno what it does) -->
<link rel="web-socket" href="wss://live.github.com/_sockets/*">
```

So I was thinking to a similar mechanism for Push autodiscovery. It would "logically" replace the RSS icon, well at least theoretically.

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.

Having an HTML autodiscovery mechanism could be an alternate way to engage users in Push subscriptions, or at least a pre-step.

I'm not sure I see the big picture, mainly thinking the thing from a user point of view, and had the idea while scrapping some HTML pages metadata. But perhaps there could be something to think deeper.

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