Hey, welcome to nostr! I've been working on push notifications for the past few months as well, which present some interesting challenges on nostr. I took a quick look at nopu, and just wanted to offer some design critiques: - How are you planning to grant notification server access to auth-gated relays? The way I see it there are three options: 1. share user keys or bunker access (dangerous), 2. extend the protocol so that relays can optionally support pushing events to another server (not likely to get adopted), and 3. grant access to push servers using invite codes:

GitHub

Build software better, together

GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects.

The latter is the approach I'm using, which only works if relays support that PR, but gracefully degrades. - Using `h` tags is an odd choice, NIP 29 groups bring a whole load of semantics along with them. I would use some other tag, maybe even an `a` tag referring to an existing subscription. - I like that users can self-host their notification server, but it seems like a pain for users to get their own FCM/APN keys. You can find my work on this at https://github.com/coracle-social/anchor, which takes a different approach in that it's explicitly coupled to a particular application (in my case, flotilla.social). I've put together a NIP for this over at

GitHub

Add notifiers nip by staab · Pull Request #1796 · nostr-protocol/nips

This is a generalization/update of https://github.com/0xchat-app/0xchat-core/blob/main/doc/nofitications.md with the following differences: It use...

which a few other devs have left feedback for. Also, you might take a look at Pokey by @KoalaSat, which is doing something very similar to nopu.