Nostr Web Client

Its off the screen on android, fix coming in the next release

The subscriptions are NIP-88 subscriptions; think like having a Google play or icloud subscriptions manager thats native to nostr and handles all your recurrent payments in a way that absolutely any wallet/client can interact with

Max 1y ago 💬 2

I found 5 different NIP-88s, none of them are about subscriptions...

Do you have a link?

Reply to this note

Please Login to reply.

Discussion

Derek Ross 1y ago 💬 1

I don't think it's ever been merged?

https://github.com/nostr-protocol/nips/pull/901

Derek Ross 1y ago

Though now with 2 implementations, it sounds like we may be able to merge it.

Max 1y ago 💬 2

Thanks!

Why unsigned events nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z?

Vitor Pamplona 1y ago 💬 1

I don't think this is what nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft is talking about. The notify is just a way for relays to display a message to the user directly.

Max 1y ago 💬 1

NIP numbers are broken AF...

To your NIP88, buy why wouldn't the user want to verify the message is authentic from the relay?

Vitor Pamplona 1y ago

Mostly because relays don't have a pubkey for themselves. To use a relay, users just add the url itself to their settings, not a pubkey. There is no relay pubkey on Nostr yet. So there is nothing to verify against.

Max 1y ago

And I guess the websocket is https anyhow...

Derek Ross 1y ago

Oof. Okay. We'll have to wait for the man to confirm then. This use case really sounds like the same implementation though.