Wow, Great comment! I should zap this! Oh wait, this client hasn't loaded in their kind 0 to zap Okay ~ opens other app -app locks up before being able to zap Okay ~ opens up third nostr app ~kind 0 loads and profile is zappable ~Creates invoice ~Opens zapping app ~ *Zaps* ๐Ÿซ  Nostr is life. View quoted note โ†’

Replies (8)

imho, profiles get updated so infrequently, it is the hardest thing to run a relay for without getting overrun by spam and such. and the hardest thing for clients to query for. clients and relays could benefit from names, and zap details on each note and cut way down on some serious complexity that is a major annoyance.
Completely get that! Been suggesting that we cache kind 0s (of course, clients should be caching a lot of things, but kind0 at the minimum) rather than retrieving everything each time. But yours, which i'm interpreting as an update to nip19 + convention of broadcasting the event a user interacts with, makes more sense.
even if zapping some old note, the odds are your client has a newer note and can compensate. but finding some ancient kind zero, who do they think i am, indiana jones? ๐Ÿ˜Ž๐Ÿ˜ well maybe i am.
โ†‘