-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: does this project can handle web push notification for any web application ? #70
Comments
Web Push is compatible with UnifiedPush. There are currently some missing functionalities (like VAPID) but they will be integrated soon : you don't need any proxy for that. But, you can't receive (yet) web push notifications on your browser because the browser needs to support UnifiedPush |
Do you know any web browser on android that support UnifiedPush ? Is it possible to have a web push client that is not a web browser ? |
Not yet. I may be looking into it in some time
Sure, for instance Mastodon and Telegram use (a deprecated version of) webpush. They use a gateway to push to APNS (apple) and FCM (google) servers. And both services have clients supporting UnifiedPush: they don't need a gateway. |
Do you think it is possible to trick a website by suscribing to it's web push using mastodon so ? |
This may sound like a stupid question:
I want to remove my dependency to google Firebase and then run a degooglised android phone. However I couldn't anymore subscribe to push notification of web apps as phenix (firefox android) have no alternative to google firebase yet.
I wanted to know if it is possible either to have a web push->unifiedpush bridge that I could run on a homeserver to subscribe to web push notifications for me and relay on unifiedpush provider like ntfy.sh.
So, my question is, can this proxy handle this goal and make me able to receive web push notification of a website (that I couldn't change the backend to support UP out of the box) with UP provider like ntfy.sh android app ?
Thank you for your help
The text was updated successfully, but these errors were encountered: