verbiricha on Nostr: > Not all 'other stuff' content types have the same desired outcomes. Some want to ...
> 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.
100%, with chachi my goal is to give you a window to all these other stuff but not create a worse version of specialized tools for those content types. In the future I'll use NIP-89 to allow you to open everything in apps endorsed by your follows and community to interact with certain types of content in a better way.
> 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.
Threading is a core part of the app and something I want to get right but I still haven't worked on a lot. I really like the approach nielliesmons (npub149p…722q) proposes of having direct replies show under the post and flattening replies deeper than that into a chat interface. This can work for any content type and using the same kind 1111.
> I'd be interested in exploring with you and the community how can we nudge things in the right direction.
Same, this is a really challenging and fun experiment! 🫂
100%, with chachi my goal is to give you a window to all these other stuff but not create a worse version of specialized tools for those content types. In the future I'll use NIP-89 to allow you to open everything in apps endorsed by your follows and community to interact with certain types of content in a better way.
> 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.
Threading is a core part of the app and something I want to get right but I still haven't worked on a lot. I really like the approach nielliesmons (npub149p…722q) proposes of having direct replies show under the post and flattening replies deeper than that into a chat interface. This can work for any content type and using the same kind 1111.
> I'd be interested in exploring with you and the community how can we nudge things in the right direction.
Same, this is a really challenging and fun experiment! 🫂