nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac proposed a custom nips for NodeCast https://nostrhub.io/naddr1qvzqqqrcvypzqx78pgq53vlnzmdr8l3u38eru0n3438lnxqz0mr39wg9e5j0dfq3qyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueqqp3kh2umfvvkhgunpvd4hx62pzs3
Login to reply
Replies (1)
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.