You don't, because if you knew you would do it yourself.

Unless you're lazy. In that case instead of writing code to do it you write English and tell the user to do it.

Reply to this note

Please Login to reply.

Discussion

“It appears this note had other plans and showing up wasn’t one of them”

Yes, and besides the nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 type message, whats the next step?

>button< shut it all down, go bloom outside

Error messages for non-compatible features would be nice too.

This note includes a feed, it opens empty on Damus, has just the nostr:addr… on Primal.

nostr:note1n9z7fltdg5u638rfa5gc8k4p5yln4pndvs7wq20esenw3su8lyhq2h0rwc

Nostur has a nice link back to Coracle. Great job nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe

#networkeffects

Thanks nostr:npub1a7n2h5y3gt90y00mwrknhx74fyzzjqw25ehkscje58x9tfyhqd5snyvfnu

I think this points to handling unknown event kinds, and recommended app handler NIPs, which damus has yet to implement.

Nice work nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe !

Thanks nostr:npub1a7n2h5y3gt90y00mwrknhx74fyzzjqw25ehkscje58x9tfyhqd5snyvfnu and nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5, this is indeed handling of unknown event kinds, I added this after nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft suggested it in nostr:note16pgkeuxvkl3y8c7zgn9zvnn8w4xwqals9henwag5edez3gx8e9wqm33qep

More clients should implement this, its one of the few ways we leverage the current kind-1 network effect to grow the Other Stuff