what if... (and you probably know what I'm going to say...)
we publish these features on nostr.
Say for example I add "pin-note" support to nostr:npub1w0rthyjyp2f5gful0gm2500pwyxfrx93a85289xdz0sd6hyef33sh2cu4x
I publish a new event kind tagging my NIP-89 entry of Highlighter. Thus I signal that Highlighter supports that feature.
That way, say for example I later add "mute-list" support; I could just publish the event.
There is NO WAY someone, not even nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 , will be able to keep up with all the clients and all the features we are all constantly pushing.
But we can push it to the edges, me as a developer, it is basically no extra work to publish an event indicating the new feature when I cut a new version.
+1 Clients can make declarations of compliance and users can react to them with replies, reactions and even reports if they are wrong.
But we need to make it so that nuance is taken in to account. Many NIPs can are probably are just partially implemented and being able to declare what exactly should work and what will not is key.
Right. Details are important here.
