Re: [w3c/push-api] Some things about the PushEncryptionKeys p256dh and auth are not clear enough (#212)

late to the game, but maybe of help regarding that last question.

When you ask for the subscription on the client side and send the subscription information to the server, you can make sure to have a login or some other identifier to distinguish your users and add that data. Otherwise all the subscriptions are basically anonymous if you leave out the user agent. In my case I only ask for subscription data, when the user is logged in. Next I can save the subscription with the user in reference on the server side. When sending something to certain users (notifications on personal events in the application) I have one or more subscriptions to send to. If any error occurs, that leads to a retracted/general broken subscription, I delete the subscription on my side (or flag it). Since I only send to certain users, I have no use case like "send to everyone", that may differ from scenarios like a newspaper urging everyone to read a new article without bothering who it is, as long as there is a valid subscription in storage.

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

Message ID: <w3c/push-api/issues/212/1916897803@github.com>