DanConwayDev on Nostr: First we need to extended rich rendering of bech32 entities beyond npubs to events. ...

First we need to extended rich rendering of bech32 entities beyond npubs to events. this is tracked in:

quoting
note1rs5…qxds

Rich rendering of bech32 entities

The npub/nprofile could be rendered as the username with a link to the user profile when nevent1q…60g9 is implemented.

The nevent of an issue could be rendered as a link to the issue and the text could be the issue title. Similarly for proposals.

The naddr of a repo could be rendered as a repo card with the basic repo data.

https://gitworkshop.dev/r/naddr1qvzqqqrhnypzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqq9kw6t5wahhy6mndphhqucjqc6/issues/note1rs5shxk8ems0d878tymvntej4zcv4rvg7ntcpac5539xrcvvntss2vqxds
Then we need to enable launching unsupported events in other applications. Perhaps NIP-89 would be better than hardcoding my favorite client (eg wikifreepedia) for each kind?

Your 2) is a good idea. There are some some interesting UX options for when note recommends viewing a nostr event in a particular client by linking directly to it.

I'm not sure about 3). Wont it be clear from the context that it is the wiki landing page for the repository?

PS: I just created a NIP-89 application handler for gitworkshop.dev.

quoting naddr1qq…uzvz

{"name":"gitworkshop","display_name":"gitworkshop.dev","nip05":"","picture":"","banner":"","about":"git code collaboration via nostr. browse repositories, issues, patches and proposals.","lud16":"danconwaydev@minbits.cash","website":"https://gitworkshop.dev"}

you can recommended for nip34 event kinds here:
https://nostrapp.link/a/naddr1qqxnzde3xc6rvv3n8qun2v3eqgs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngrqsqqql8ky0uzvz/users