Replying to Avatar rabble

You could run your own push notification service or generate them locally within the app or have empty silent notifications which trigger the app looking for new content on relays. But the notifications have to have a key for the ‘service’ and the client app.

I think most nostr apps that do notifications do the cloud bot method. The code for the various solutions are on github.
Avatar
petri 2y ago

Maybe the local app background fetch is the way to do it decentralised.

Not sure whether it works with PWAs even though Apple allows them to have push notifications.

Reply to this note

Please Login to reply.

Discussion

Avatar
daniele 2y ago

The problem are the multiple background tasks (one per app), usually not specific and so quite resources hungry.

Check this: https://grapheneos.org/faq#notifications

Avatar
petri 2y ago

A feature in relays that keeps the state of the app’s notifications what it has and what’s new and then it collects those notifications and when the app pings it in some frequency (e.g. 5/10/60)min it sends the new notifications?

The client does not need to harvest all the stuff on background but just the bundled package at once.