Replying to Avatar DanConwayDev

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

nostr:note1rs5shxk8ems0d878tymvntej4zcv4rvg7ntcpac5539xrcvvntss2vqxds

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. nostr:naddr1qqxnzde3xc6rvv3n8qun2v3eqgs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngrqsqqql8ky0uzvz

you can recommended for nip34 event kinds here:

https://nostrapp.link/a/naddr1qqxnzde3xc6rvv3n8qun2v3eqgs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngrqsqqql8ky0uzvz/users

nostr links within event content are now displayed. There are previews for repos, issue and patches.

nostr:nevent1qy2hwumn8ghj7ur4wfcxcetjv4kxz7fwvdhk6qpqrs5shxk8ems0d878tymvntej4zcv4rvg7ntcpac5539xrcvvntss5j5wak

I'm now thinking it would be a lot better to display a wiki instead of the ReadMe on the repository homepage.

What do you think nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzusk cqsyn nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z nostr:npub1896p07z8xngpct5ma00mdrad4gqfnwfwdqcl706wrm25ajynahhs27x5ge?

This would require adding support for showing wiki content but that's no bad thing. Showing the ReadMe by querying the server's Web API feels dirty. Different git server implementations use a different API. Its just not a great setup.

Reply to this note

Please Login to reply.

Discussion

this is another good reason:

nostr:note1zlhpa7jnkthezrenxw8efae3dx69550x5xa8qtrtlf05s7snmh7srahcsl

I actually meant this issue:

nostr:note1m5qmedug327a9q6a4nv8ehgg4sjn5gm00nf0nxmqtzyemfnaaypssszx8d

Looks like an option that can be set by maintainers, and default can be wiki or a long note ( readme ). At some point in time some settings will be require for a repository. I prefer local only client only, no server side, and cached if is possible.

Yeah, choice between a long-form note or a markdown file in the repo, would be nice. 🤔

#[4] #[5]

default wiki sounds good to me