What is Nostr?
Yonle
npub1x3a…g4el
2023-11-02 23:43:22
in reply to nevent1q…7ynm

Yonle on Nostr: > 1. Yes, we should consider implementing what PABLOF7z suggests, but we should give ...


> 1. Yes, we should consider implementing what PABLOF7z (npub1l2v…ajft) suggests, but we should give clients time (90 days+) from merging the NIP to implement it before clients offer this tool to their users. (reviewers: hodlbod (npub1jlr…ynqn), Vitor Pamplona (npub1gcx…nj5z), jb55 (npub1xts…kk5s), JeffG (npub1zuu…c2uc))

Requiring every single clients to support this NIP just for this function? Sounds like rewriting an standardized RFC to achieve what you exactly wanted.

Requiring them 90 days to implement this feature is BS. No. We do NOT need this NIP in every nostr client. Let the developer decide.

I even personally think this NIP is stupid. Just let the client tell to the follower that this user has been migrated to new pubkey by reusing the `kind 0`, By putting `moving` as the new pubkey.
Author Public Key
npub1x3azxuysp5vmfer4vgs4jn5tmfcx4ew8sh0qnev7gczljxsr7jwqa3g4el