Nostr Web Client

Good catch, challenge accepted.

Zap addresses are already an implementation detail under nostr events - people zap a profile, they don't care what 'zap address' is.

But we could go further, I could write something like my_npub@provider_npub as my zap address in profile and if clients could talk to provider_npub using ephemeral events then we'd get rid of urls. This would allow one to accept zaps to their LN node behind NAT. IIRC you were proposing something similar during zap nip discussion?

fiatjaf 2y ago

But relays are URLs, you can't escape that. I don't know why you think URLs are so bad. It seems like you want a fully p2p network, in that case other means should be preferred over Nostr. I think trying to turn all internet communication into events inevitably leads to a slow, bloated and nonfunctioning experience.

Reply to this note

Please Login to reply.

Discussion

Cameri🐦‍🔥 2y ago

We have kind 2 recommend_server events which could be useful for that.

brugeman 2y ago

I don't like switching btw my nostr app and web. I don't like looking for relays on some clunky websites, and copy paste meaningless relay urls. I don't like when domains I use are blocked by local firewalls. If we abstract them away nostr experience might be smoother. I am fine with urls under the hood.

What do you think about nip97?

fiatjaf 2y ago

At first glance I don't like it because it tries to shove p2p communication into Nostr, like many other proposals floating out there, and I don't see how that can scale. But I haven't inspected it very closely yet.

brugeman 2y ago

Thanks for the feedback.

fiatjaf 2y ago

I don't like clunky websites either, but I think they are necessary if we want Nostr to keep working without becoming the silo of some centralized app that makes everything easy. I could be wrong. The experience of finding relays and other URL-based services could also be much better and not necessarily require clunky websites.