NIP-22 has become non-optional. It solved a real problem and was a good idea, but also it was a breaking change. A non-optional breaking change. I made this point early on, calling the other devs mavericks and juggernauts.
Now we are in the situation where gossip either doesn't see anybody's replies, or it replies to their replies with kind-1 events which I am now told is a "sin". You see, I am not allowed to ignore this NIP-22. It is non-optional.
I'm not even against this being non-optional. What I am against is not running a migration campaign... not pushing everybody to upgrade to it. I warned this situation would happen and I was ignored. So now we have this mess.
I will now upgrade NIP-22, but somebody needs to go around to all the other clients and push them all to upgrade too.
nostr:npub1useke4f9maul5nf67dj0m9sq6jcsmnjzzk4ycvldwl4qss35fvgqjdk5ks nostr:npub1l3cgtsurhfchg4cyhhqudm70074sr96srhje330xc5m6czej5n9s9q6vs2 nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s
NIP-22 for "other stuff", not as a replacement for kind 1
That said though as nostr matures I don't know if we can prevent these kinds of breaking changes. for every context in nostr (social, streaming, groups, etc...) there is going to be a feature set that the majority of the clients support or are working together to support and it will put pressure on the rest of the clients to support those features
No replies yet.
