Nostr Web Client

Replying to

Vitor Pamplona

I don't think people understand how powerful this Wallet Connect NIP is.

Here are a few ideas that can be built it top of it:

- Setup recurring payments in native Nostr (think monthly subscriptions of your favorite apps)

- Send sats in other functions (i.e. every like automatically sends 10 sats to the author)

- Send zaps to all replies of a post, or to all your follows/followers.

- Send zaps proportionally to time spent per post/thread by the end of the day/month.

There is so much it can do.

https://github.com/getAlby/nips/blob/master/47.md

KoalaSat 2y ago

Nothing you can't do with a regular API call. It sounds to me like using nostr for the sake of using nostr.

I don't believe this kind of messages should be part of the protocol, adding every single edge case to the protocol over complicates it, overcrows network and relays:ñ; and slowly makes our private keys a single point of failure.

I just implemented a wallet in Nostros by using lndhub API calls and I never had the need of using nostr.

Reply to this note

Please Login to reply.

Discussion

Vitor Pamplona 2y ago

That's true for everything in Nostr. You can do all this without Nostr, in regular calls.

The goal of the NIP is to make sure Nostr clients don't need to understand the API of each LN connection type out there.

It significantly decreases implementation time. I added it yesterday to Amethyst in under 1 hour.

BladeRunner 2y ago

Cool

fiatjaf 2y ago

Wait, isn't it true that Nostr Connect is not required for anyone? i.e. all clients can go on with their lives without ever caring about Nostr Connect and still get the same experience?

KoalaSat 2y ago

Maybe I'm a nostalgic and I miss when the protocol was really simple 😛 you can basically run with only NIP-1, I'm just wondering if there is a point where it's just too much for relays to deal with everything at the same time, everywhere