Backend subscription endpoint changed
Site
dev.phanpy.social
Version
2025.01.06.3df20a5
Instance
gelato.steffo.eu
Browser
- Vivaldi 7.0.3495.27 (Stable channel) stable (64-bit)
Bug description
An unusually technical message appears when opening the Settings menu on an Iceshrimp.NET instance.
I'm not sure of what it means or what it's caused by...
(Does Iceshrimp.NET have support for Push Notifications...?)
To reproduce
- Log in to an Iceshrimp.NET instance
- Open the Settings menu
- Enable Push Notifications
- Close the Settings menu
- Open the Settings menu again
Expected behavior
No message to appear.
Other
No response
This is also one of the weird things I've seen when implementing push notifications. This shows up when backend's push notification server endpoint changes, which I don't understand why… 😅. I don't see this often at least on mastodon.social instance, which I also don't understand why… so I suspect it's "random".
I've tried researching on this and seems like some clients will just unsub and re-register the push notification subscription when this happens. This means Phanpy, on client-side, will have to remember what the user subscribes (it's not doing this yet) and re-subscribe when there's something changed like this 'endpoint changed' case (I haven't work on this yet)