Congrats. You may not realize it, but nostr actually would not exist without the git use case. I've also been working on it for 4 years, but in my case relays are not a storage system, they relay git events from one repo to another. Hopefully our ideas can find an intersection.
I meant, our team is growing, at nostr:npub1s3ht77dq4zqnya8vjun5jp3p44pr794ru36d0ltxu65chljw8xjqd975wz . Just added another scientist, yesterday, to work on our models.
Discussion
If you get your events compatible with the "Git Stuff" NIP, we can read them.
nostr:npub1wqfzz2p880wq0tumuae9lfwyhs8uz35xd0kr34zrvrwyh3kvrzuskcqsyn found another one.
I see a different intersection. My Git NIP predates NIP-34 and I've been iterating on it 4-5 years until it's exactly what I want. However I can use git with ngit becasue its compatible with git. Just like I use it with radicle. In this case the common territory is git and nostr. Rather than a bespoke NIP. One thing that i need is the equivalent of "github pages" and radicle has implemented that, as have I. If I used ngit too, that would be the first thing that I would look at.
Let me correct this. Having looked through the details, the two are compatible. Fortunately we managed to converge on the same idea due to good luck.
Ah, I see, it's influenced on my NIP-17 already