I think #[3] has something like this?
Discussion
Piping the diff to a nostr cli client it's a good start
Yup and I’m making it even easier (rewriting in rust). Right now it’s a bit clunky to install and use.
Wicked!
I wish people actually used it 😆 I think I only ever got a patch from #[5]
I'm getting a discounted phone soon. Debating between yet another Samsung or an iPhone. Might get the iPhone just for Damus.
This is what made me think it has to be insanely easy or no one will use it. Unfortunately that means gui tools ☠️
Dunno, if someone is motivated enough to write a patch, they will spend a (one-time) 2-3 mins to figure out how to send the patch.
I don't think it has to necessarily be insanely easy.
From a GitHub replacement perspective, I’m hearing the following as most critical:
1. search (nostr is super weak here)
2. issue tracking (nostr ok through thread following)
3. social layer (nostr is great)
💯
What about verifying an authorised state when the list of maintainers evolves overtime?
Something that might be viable (it'd take a lot of effort, though, and I'd have to look into what licenses the codebase was released under) would be forking/re-working some of the tech used on keybase.io; it has built-in git repos and could be modified to work with nostr IMO
nostr:npub1f3t5xtuxzchx0xswmf0wjpaua9r5c429jk6n9dla5x5ysdwmgv0q9u9s4n Github conversation
My patch was for nostril and it was actually was a bad patch that broke nostril, so I couldn't send the patch as it was using the broken nostril under the hood.
Rust? Now we are talking
yessss
I think this is compatible with yours, but I'm yet to try it: https://github.com/npub1zenn0/go-git-nostr