XF 2.3 How do you all handle expiring push notifications?
- Thread starter TheGroove
- Start date
unproperlypropagated
Member
If a site force me to enable push notifications I'll never use that site again.
Push notifications is an awful idea that quickly got taken over by scammers and ad companies.
It's the first thing I disable in a browser and I sleep very well.
Push notifications is an awful idea that quickly got taken over by scammers and ad companies.
It's the first thing I disable in a browser and I sleep very well.
TheGroove
Well-known member
Fair enough, but if you opt-in why should you be forced to re-opt-in all the time. This should be a setting that does not expire. In the end it cripples the service and people quit using it as a result of having to repeat all those steps on a regular basis.
There is no forced opt in in XF - it's up to each member whether they want to allow them or not.
The push notification approval is stored in the browser.
If members are being prompted to sign up again then it's either a browser issue, or they have removed the push notification setting for the site.
The push notification approval is stored in the browser.
If members are being prompted to sign up again then it's either a browser issue, or they have removed the push notification setting for the site.
TheGroove
Well-known member
Right, being stored in the browser makes it subject to being timed out, this happens to all of the users on my site. If this were a tick in the DB it would be a set it and forget it setting.
My goal here is to see how many others are dealing with this and whether or not they've either come up with a better solution or have just given up on it. This feature is indeed crippled by design.
It doesn't work like that.
It's a per browser/device setting.
XF does not control the specifications for push notifications and how browsers handle them.
This is not something we've ever had anyone complaining about previously.
I have never had to re-enable push notifications on any device.
digitalpoint
Well-known member
The reason iOS users “lose” their push notification subscriptions with the PWA is because XenForo is relying on a browser’s willingness to resubscribe to the push notification without human interaction (a click for example). iOS/Safari doesn’t allow this, so push notification subscriptions are lost if you need to reauthenticate (logging into admin or redoing your two-step auth after 30 days).
See:
Was able to work-around XenForo’s behavior (mostly) with this addon:
…but the “right” thing to do is for XenForo to not rely on a browser’s willingness to subscribe to push notifications without human interaction.
See:
Was able to work-around XenForo’s behavior (mostly) with this addon:
![[DigitalPoint] PWA](/community/data/resource_icons/9/9231.jpg?1692634306){kind=icon}
…but the “right” thing to do is for XenForo to not rely on a browser’s willingness to subscribe to push notifications without human interaction.
digitalpoint
Well-known member
For now… Safari doesn’t allow tend to be first with tightening security/privacy. I wouldn’t rely on other browsers not following suit.Figures it's a Safari only issue
Purely from a security/privacy standpoint, it does probably make sense to not allow websites to sneak a push notification subscription without user interaction.
Basically XenForo is relying on something that probably is going to be “fixed” someday in other browsers beyond Safari. It’s similar to how back in the day browsers could throw popups without a user clicking something, but browsers locked that down and you can’t do that anymore.
digitalpoint
Well-known member
Indirectly, ya… because of the same reason. XenForo deletes push subscriptions on its backend if the user isn’t logged in, rather than flag it as inactive.
TheGroove
Well-known member
Thank you, this is really useful.The reason iOS users “lose” their push notification subscriptions with the PWA is because XenForo is relying on a browser’s willingness to resubscribe to the push notification without human interaction (a click for example). iOS/Safari doesn’t allow this, so push notification subscriptions are lost if you need to reauthenticate (logging into admin or redoing your two-step auth after 30 days).
See:
Was able to work-around XenForo’s behavior (mostly) with this addon:
…but the “right” thing to do is for XenForo to not rely on a browser’s willingness to subscribe to push notifications without human interaction.
Which is used by nearly all iOS users who want to use Xenforo notifications as it relies on it for the push.Figures it's a Safari only issue
digitalpoint
Well-known member
Also future-proofs the situation where other browsers decide maybe it’s not such a great idea to allow push subscriptions without a user triggered event (like a confirmation or click).Easy solution:
Don't use Apple hardware and enjoy proper PWA support
That being said, it really would be nice if XenForo just disabled push subscriptions in the DB instead of deleting them.
TheGroove
Well-known member
You bet, there are only 1.46 billion of them, I'll get a memo out.Easy solution:
Don't use Apple hardware and enjoy proper PWA support
That being said, it really would be nice if XenForo just disabled push subscriptions in the DB instead of deleting them.
Similar threads
- Question
- Question
- Question