Nostr Web Client

Started working on a “forwarder” for noteguard. The way this works is that any incoming note into the damus relay can be sent to another relay. We will be using this to forward notes to our push notification relay.

Our push notification relay does not write to disk, so you will able to point your clients at it to send notifications without necessarily storing that note on the public damus relay. This will be helpful for situations where you are running a private pool of relays, and still want push notifications to work.

Right now we support apple push notifications, but in the future we will add google and maybe even things like webhooks? nostr:note16qhndtt6krgz34dk9pvlvaw8g3de7ama4ftp3425ll2620upgqrsz8v7w5

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 1y ago

Are you planning on supporting authed relays for notifications? If so, we need to figure out a way for the Push service to auth on behalf of the user to pull DMs from the private inbox relay.

I am testing this NIP below. It's similar to a key delegation, but only for AUTH. The user authorizes another key to AUTH on their behalf. https://github.com/nostr-protocol/nips/pull/1148

jb55 1y ago

The damus notification relay doesn’t pull anything, damus will just have an option to push to the notification relay when push notifications are enabled. It will be up to whatever client to push notes to that relay if they want the user to be notified. I will have to update the users relay list when push notifications are enabled I guess. 🤔

Vitor Pamplona 1y ago

So, it's up to the sender's client to send the event to the PushNotif relay of the receiver?

People could add the relay to their NIP-65 list and it will work already. They can also that the relay to the NIP-17 DM Relay List and that could work.

Apps should just know that the Push Relay is not queriable, otherwise it might allow tracking of the notifications by the public.

jb55 1y ago

yeah they will see that when they try to query it, i want something myself that i can use for sending notes privately that can notify people. We are also going to e2e encrypt the notifications so not even apple can see the contents. Right nostr:npub13v47pg9dxjq96an8jfev9znhm0k7ntwtlh9y335paj9kyjsjpznqzzl3l8 ? 😁

Vitor Pamplona 1y ago

I think you can just remove the query out of the relay. Basically no one can query. It's a "relay" that only receives "EVENT'" commands and sends to the Push system. Super simple.

On the E2E, just giftwrap them without destination (the destination is the device ID, not the pubkey). Super easy.

jb55 1y ago

that’s the plan

pleblee 1y ago

Amazing work! I'm still running a modified strfr-policies that first checks if an npub is within a given set. I keep sets of npubs that are designated as within my web of trust, currently with three tiers. Then I apply different filtering depending on whether your npub is in the set. Mostly cribbed from nostr:nprofile1qqsydl97xpj74udw0qg5vkfyujyjxd3l706jd0t0w0turp93d0vvungppemhxue69uhkummn9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshsz8thwden5te0dehhxarj9ekh2arfdeuhwctvd3jhgtnrdakj70vc385 and that one vegan guy.