[w3c/push-api] Non-Browser Vendor Supplied Push Server Support (#243)

Hi all,

We (Digital Bazaar, W3C Member company) will soon be using the Web Push API in production, so first off, thanks for this feature/functionality. It's great and enabled us to deploy our digital wallet products to mobile using the Web Platform instead of native apps.

I've read through every issue that I could find relating to push service registration and note that the push service that one uses effectively boils down to either Google's servers or Mozilla's servers. While I understand the desire to get this deployed in a way that's easy for Web Developers, that the Push Notifications go through servers that we don't control is a problem for some of our more security conscious customers. We do realize that payloads can be encrypted, but we'd rather just run a Web Push service ourselves (again, it ticks a box for our customers).

My understanding is that there is no intention to support a more decentralized model for the Web Push servers and one MUST depend on the centralized Google or Mozilla servers. I haven't been involved in Web Standards for long, just over a decade, but I can't think of any other Web Platform spec that requires proprietary services (other than EME) to operate.

Has the thinking of this changed lately? If so, is there a timeline for supporting non-browser vendor supplied Push server services?

-- 
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/243