Oddbean new post about login | logout NIP-31+89 support would be the absolute low-hanging fruit that would make the experience complete in a single blow. NIP-31: allow displaying what an unknown event is NIP-89: allow the user to one-tap open the event in an application that supports the unknown event
Absolutely this, it would also give damus users to an opportunity to explore other specialized nostr apps NIP-10 support would be nice, but only so that we can finally kill the legacy "e" tag threads
Thinking about nip-89… Wonder if it the user recommendation kind could be “repurposed” to serve the end user “social” needs (recommending and rating of “best recommended” clients by user) AS WELL as “client discovery” by clients themselves. What I mean is that event “content” could be used for user comments pertaining to the client being “recommended.”, and users could publish recommendations “per client” rather than just “per event kind”. Problem is that kind 31989 is (by convention) “parameterized replaceable” keyed on the event kind being recommended. WHAT IF a kind 31989 WAS NOT replaceable but a user could simply author as many as desired for a given “event kind recommendation”? This would open up possibility for so much more… Thoughts? nostr:note158d3875n59f0gp6s0c3cjv7y38sx457s32xjyhz439zx50nmx2zq5eswds