Oddbean

▲ ▼

 Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmm

▲ ▼

 I have nothing yet, this is just something that has been brewing on the back of my mind while I take a shower.

I just think repo maintainers have no incentive to manage 99% of issues on GH and the rest on nostr. That won't work, even if they like nostr, managing 2 separate issue trackers is a big no.

▲ ▼

 Have you looked at the nostrocket problem tracker?

▲ ▼

 I have heard about nostrocket on your pod. Great idea albeit ambitious.

I just checked the spec for NIP-1971 and it looks more like a replacement for complex issue tracked used internally within companies (like Youtrack, altassian, jira, zendesk, redmine) more than GH issues (which are rather simple).

Would love to see it to fruition! For now I will focus on bridging NIP34 events, gotta start small.

▲ ▼

 Are people using Nip34 with github or just their own git servers? I don't want to dissuade you just wondering if the demand is there, still a fun project regardless though

▲ ▼

 My repo uses my personal git server as primary, github as a mirror: https://gitworkshop.dev/repo/sentrum

If people mainly use GH for the social aspect and we can steal that with nip34, I believe people will naturally use other git servers since they won't depend on GH so much anymore.

▲ ▼

 There are a bunch of projects that use GH for PRs and Issues and have created a nip34 repo event. eg gossip, amber, amethyst, ndk...