Re: [w3c/push-api] Declarative Web Push (Issue #360)

Thank you, those answers do address most of my initial concerns. 

For what it's worth, we generally see fairly large payloads (although I suspect that's mostly due to padding). I can see how the structured form could impact the amount of data being exchanged, but I also expect that it might address some other security concerns. 

I also wonder how or if this modification would see adoption unless there's a concerted effort to either promote it or some other incentive for publishers to adopt it? FWIW, even 8 years after the release of RFC 8030, and three years after a personal effort to have a majority of Push libraries change their default, half our subscription load still uses the older "aesgcm" encoding, indicating that A LOT of publishers never update their code. Hopefully, the "You don't need to copy/paste your service worker code", will provide enough incentive for those publishers, but I suspect that problem is out of scope of this proposal.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/360#issuecomment-2474117620
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/issues/360/2474117620@github.com>