Niel Liesmons's avatar
Niel Liesmons 8 months ago
I think we can do better than the "copy GitHub and add stuff" approach @Biz . 1) Once you have a reply section on the repo event, the Issues can be :110percent: focussed on bugs and requests. 2) I think a solution that lets the author target his repo to multiple communities is better than having a chat per repo. Why do you even need a chat for the repo, if you already have a reply section on it + a gazillion other events in there that can each receive replies too. The conversations already happen there and in the Communities (plural!!) that work with this repo. Look into #communikeys for making that part work. 3) Why not use Indexed Wiki entries (30040 with 30818s inside) for :docs: Docs? 4) Labels > Stars 5) Zaps & Pricing are huge for collaboration

Replies (1)

Thanks for the your thoughts and suggestions! There's a lot to think about when it comes to communities but at the end of the day shipping something and iterate on user demand will be most prioritized. I read your spec(and saw you launched your communikey, congrats!) but will be more confident in my assessment of the communikey approach when I see more things fleshed out. As to the reply sections, I believe there is room (pun intended) for more frequent and less formal discussions around nip34 events, and a place to post the more formal stuff (repo relays). Any community could set up its own moderated space around any repos is good overall I think. Zaps are a great thing but not strictly necessary to launch something useful in my mind. Also, copying some stuff that github does well doesn't hurt. It's about fusing github and discord with nostr paradigms, that creates a unique end result. This is the best thing about nostr: the better UX wins, and ppl can target multiple niches. All the best, and keep building!