Re: [w3c/push-api] A javascript api for sending push notifications to others (#303)

Probably getting a bit off-track from the original request here. Looping back, the original requirements were 
A PWA that creates a push subscription between two parties that can be used later. The PWA would store data locally.  The road block was that some Push Services block CORS requests. 

I think that's the crux of the problem we're being asked to resolve.

Do we feel that a subscription service should allow Javascript services to POST data? I'm OK with that, mostly because of all the reasons we're mentioning here. Plus, the levels of spam our servers get pretty much indicate that CORS isn't doing much to prevent that. (Our biggest issue are around Subscription Servers that happily ignore 404/410 responses.)

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

Message ID: <w3c/push-api/issues/303/998175681@github.com>