Agree. When writing a NIP I think of implementation though its hard to spare enough time to actually implement it. Until now the way I wanted to help was just writing NIPs so others that had clients/relays would implement them instead of me.
I did write some relay and client code though I need to inject some caffeine and complete the damn things.
How many of your NIPs have been adopted and merged? I know Vitor has picked up a few, but most NIPs emerge out of developers solving their own problems, not other people offering solutions.
I began my nostr journey by writing my own protocol. Fiatjaf dismissed me as an academic, until I gave up on my ivory tower and started writing real software - on nostr, because I realized I couldn't build a protocol on my own. I think he was right to do so.
I think NIP-27 and NIP-96 were very important to the protocol, although the latter was a real pain to get everybody on the same page and merge. It was also important to be there and nag about NIP-42 till nostr:nprofile1qyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qy88wumn8ghj7mn0wvhxcmmv9uqzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vahj2kfz came up with the "CLOSED" message as a solution to most problems. I like unmerged inline metadata NIP that I think nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqss2dqr is still using and I will too but I guess nobody else is for now.
Some things had to change on the protocol before being too late to change, even though I wasn't implementing anything at the time.
I see your point though.
Based
