Re: [w3c/push-api] Make PushSubscription.expirationTime mandatory (#302)

> This is less a question of API design and more one of policy. I'd suggest taking this to the browsers.

@martinthomson The point is that **until the standard says that the expiration is optional, browser manufacturer are free to ignore this** and they don't set any expiration... indeed no current browser sets the expirationTime.

This issue is really a pain... valid subscriptions (that return successful status codes) have such **low delivery rates** due to this problem and it is difficult to explain that to normal people (still we don't want to do like other services that simply show the sending rate as if it was the delivery rate...). Also it doesn't really make sense that **the number of inactive subscriptions** (that belong to abandoned devices and browsers) **grows constantly over time**. Fixing this is also relevant for **privacy**, because it would allow us to delete unused subscriptions together with all the associated data.

-- 
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/302#issuecomment-435031373