Thanks for your reply, hodlbod. I’m really glad to be able to discuss this with nostr devs.
Regarding the auth-gated relay, I’ve thought about this too. I think the simplest approach is to grant permission directly to the push server’s pubkey — since if you want the push server to deliver notifications, it does need a certain level of access. Especially for NIP-29 closed groups, you could just add the push server’s pubkey into the group. And if there are privacy concerns, people can self-host their own push server.
About the `h` tag — great suggestion, I’ll seriously consider changing that.
For the self-hosted server idea, my initial design for the backend looks like this:
self-hosted server → distributor server (with FCM/APNs certificates) → distributor clients.
This way, we can avoid having self-hosted push server manage its own push certificates.
So my nopu client would work somewhat like nfty.sh, acting as a push distributor, but specifically for nostr.
I’ll definitely take a closer look at the PRs you mentioned, as well as anchor and the pokey client. There’s still a lot I need to learn about nostr.
sana
npub1qn…8xsha
2025-07-01 16:48:03 UTC
in reply to nevent1q…ku28
Author Public Key
npub1qn6wvpmqfnpl3xsu79yvfcgpjz4azdfe5ft220nqjmwqg223fvaq58xshaPublished at
2025-07-01 16:48:03 UTCEvent JSON
{
"id": "324206b8d7bfde4205e178ecb5c76c956613575ee90972913bea4e3d5290555d",
"pubkey": "04f4e607604cc3f89a1cf148c4e10190abd13539a256a53e6096dc0429514b3a",
"created_at": 1751388483,
"kind": 1,
"tags": [
[
"e",
"78c05ed2155eb7898d253ff2cc7df623da85d5923a0c929d3761f4d37a9e87f8",
"wss://multiplexer.huszonegy.world",
"root",
"04f4e607604cc3f89a1cf148c4e10190abd13539a256a53e6096dc0429514b3a"
],
[
"e",
"29a2a4340565de63259b63f9edca62a385a5887384c28ca77fa98fa7fd98149f",
"wss://multiplexer.huszonegy.world",
"reply"
],
[
"p",
"645681b9d067b1a362c4bee8ddff987d2466d49905c26cb8fec5e6fb73af5c84",
"wss://eden.nostr.land/"
],
[
"p",
"04f4e607604cc3f89a1cf148c4e10190abd13539a256a53e6096dc0429514b3a",
"",
"sana"
],
[
"p",
"97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322"
],
[
"r",
"wss://relay.primal.net/"
]
],
"content": "Thanks for your reply, hodlbod. I’m really glad to be able to discuss this with nostr devs.\n\nRegarding the auth-gated relay, I’ve thought about this too. I think the simplest approach is to grant permission directly to the push server’s pubkey — since if you want the push server to deliver notifications, it does need a certain level of access. Especially for NIP-29 closed groups, you could just add the push server’s pubkey into the group. And if there are privacy concerns, people can self-host their own push server.\n\nAbout the `h` tag — great suggestion, I’ll seriously consider changing that.\n\nFor the self-hosted server idea, my initial design for the backend looks like this:\nself-hosted server → distributor server (with FCM/APNs certificates) → distributor clients.\nThis way, we can avoid having self-hosted push server manage its own push certificates.\n\nSo my nopu client would work somewhat like nfty.sh, acting as a push distributor, but specifically for nostr.\n\nI’ll definitely take a closer look at the PRs you mentioned, as well as anchor and the pokey client. There’s still a lot I need to learn about nostr.",
"sig": "551b1fcf04868389da2170a139888c2781eb14a44eca5f858fdc0960efd564cc9187602701da0ffe23bc111f8cd54e49dc69275d2972a60fd6cebba6bf026f44"
}