PABLOF7z on Nostr: what if... (and you probably know what I'm going to say...) we publish these features ...
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 Highlighter (npub1w0r…cu4x)
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 elsat (npub1zaf…26k5) , 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.
we publish these features on nostr.
Say for example I add "pin-note" support to Highlighter (npub1w0r…cu4x)
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 elsat (npub1zaf…26k5) , 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.
quoting nevent1q…43u3If somebody wants to create and maintain a public feature matrix for nostr clients, that would be massively valuable.
note1hur…xmyf