Okay, that's interesting and I knew I'd seen someone post about it recently, I just couldnt remember who it was. nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9un24l5p, if I may, what's the difference between 31337 and this proposal? Is there an advantage? I'm wondering, because plume is successfully pulling 31337 types now, and presenting them well, but I don't know who is implementing them elsewhere or what any possible disagreement may be.
Login to reply
Replies (2)
31337 was the old zapstr...
I have vague memories - the notes are still there, to some extent, so couldnt we just continue to use that kind? Does nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9un24l5p proposed NIP offer an advantage?