Sir, I actually like this idea, but then here's the kicker, we have to have devs support this feature to keep their clients change log and feature list up to date.
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.
Discussion
Not really, you could create a NIP-89 for someone else’s app and publish these “features events for it
Or probably there’s no need for the owner of the nip-89 to publish the feature events, it could be essentially “Derek Ross claims amethyst supports live streams”
(Before the “oh nooooo anyone can claim anything!!!!! Dooooom! Who’s going to think about the children?!
WoT filtering 🙄)
My thoughts exactly. See, this is why you get paid the big zaps.
What do we have to do to get this added to nostrapps.com nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac 🥹
I had this idea months ago. Published an interactive wireframe for all to see. Scrounged up just enough funding that I could get MVP out the door on my own. Have been working non stop for months to get alpha stable.
Just saying … this is actually in the works.
nostr:note1n56dpv3ck393nz9axmf5j9esnyaj642sfawqne4zs9ufy9865cvqu056gx
The “social onboarding” client I’m about to push will do exactly this. (In a not to distant stable release)
