Nostr Web Client

There should be no Push notifications on nostr. Because push means there has to be some backend that uses google firebase cloud messaging or similar for sending the push notifications to your device when some conditions are met. And that means you've just introduced a centralized component in your application that is supposed to use a decentralized protocol. See the problem? The only way to be a trully decentralized client for nostr is not to use push but pull in a background service that you try as much as possible to not be killed by the system and use as little network and battery as you're able to code it. It might seem uncomfortable because you're so used to have pushs with apparently no cost to you. But there's no such thing as a free lunch. The third-party risk is there. If you want freedom tech that is trully independent of centralized clouds and backends you need to accept the cost.

Vitor Pamplona 2y ago

Every relay is technically a push server. :)

It's just too expensive to keep the app connected, so we transfer the same payload the relay would through other services.

Reply to this note

Please Login to reply.

Discussion

fmar 2y ago

My main issue is you're dependent on google centralized cloud service for a good UX of getting notifications when something happens interesting to you.

In the spirit of decentralized freedom tech which I believe nostr is, the natural path for having that nice UX feature should be to do it also in a decentralized, third-party risk free, uncensorable way.

Should not have to be too expensive to keep a socket to a few relays in the device open, or just pull then periodically.

For sure google push services also does this somewhere/somehow for connection with fcm cloud, just lower level taking advantage of privileged access to the system.

That should be a choice for the end user, not a forced dictated imposed thing.