I listened to your podcast with nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7208x3z. I enjoyed your discussion of different styles of interaction and how different tool align to them / create experiences suitable for them. Interactions around git issues and PRs aren't all the same and don't all happened in one place.

Github provides a consistent UI which is geared towards one style of interaction.

On nostr there are many tools which create different experiences. Relays and kinds can be used to separate discussion.

This could enrich the overall experience or degrade from it depending on the choices we make.

I'd be interested in exploring with you and the community how can we nudge things in the right direction.

Not all 'other stuff' content types have the same desired outcomes. Some want to maximise engagement. Some want to create healthy and fulfilling social interactions. Some, like git issues and PRs, want productive conversation that is actionable and easy to review and get up to speed with.

The right approach for podcasts might not be the right approach for git issues.

Right now the deep threads that happen in kind 1 comments lead to conversations that are hard the review after the fact, particularly when there are multiple birsts of activity common on git stuff. Perhaps its not inherent to thw threading approach but down to the UX of reviewing them in gitworkshop And other clients.