There's an app called nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0
What does #devstr think are best practices for nostr app discovery?
cc nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk
Discussion
#YESTR
How about discoverability *in app* (amethyst, iris, primal web etc)
As simple as searching for kind 32267 (software applications)
Thinking we should have a "supported NIP" tag in there
Does NIP-89 still work? This is a bad way to go because it assumes that discovery is made when you can't read that event or find something better. Looking at the client tag seems like the only option