its easy for maintainers to try out on an existing project without effecting your existing collaboration set up (eg GitHub). maintainers can just install ngit and run `ngit init` from their local git repository to being accepting patches / proposal 

 there is innovation happening with git and nostr in a few places. gitworkshop.dev aims to work with different approaches. ngit is more opinionated, focusing on patches over nostr with backwards-compatible and optional support for PR-like workflows 

 This seems to be a more polished but compatible version of https://patch34.pages.dev and gitstr:

nostr:nevent1qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpr9mhxue69uhhyetvv9ujuumwdae8gtnnda3kjctv9uq3gamnwvaz7tmjv4kxz7tpvfkx2tn0wfnj7qgkwaehxw309ac82unsd3jhyetvv9ujucm0d5hsqgqd6stmlmyejeynuv7r2my0kmkmf6y32gg0plzv7r047hftzz6w9ysjfwtz 

 You should rewrite it in Rust! 

 haha! it is in rust. if only there was 'you should rewrite it in go' meme... 

 You could rewrite it in Go and then rewrite it in Rust! 

 Nah fuck it. Rewrite it in C and Linus will take a look at it. 

 Wow, new cool shit! nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6w72kza 

 另一个更完善的 #Git over #Nostr 软件.
nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gpr3mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mgzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6qcyqqqqqqg9dxat3 

 มาแล้ว Client ที่คล้ายๆ GitHub
#Siamstr
nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gpr3mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mgzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6qcyqqqqqqg9dxat3 

 omg i didn't know #ngit 😲 #nostr is still new for me ... there is a lot to explore! wow 

 😍
nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gpzpmhxue69uhkummnw3ezuamfdejsyg9qpr00z4uklw56p4h6kp8gl4ts3y59m874qhd94ql732k40g6kf5psgqqqqqqsdqnae0 

 nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gppemhxue69uhkummn9ekx7mp0qgs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngrqsqqqqqppy88fm 

 I completely agree. That's why I started ngit and https://gitworkshop.dev

nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gppemhxue69uhkummn9ekx7mp0qgs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngrqsqqqqqppy88fm 

 This looks promising, but am I doing this right?

git clone https://gitworkshop.dev/repo/gitworkshop/                                     
Cloning into 'gitworkshop'...
fatal: repository 'https://gitworkshop.dev/repo/gitworkshop/' not found
zsh: exit 128   git clone https://gitworkshop.dev/repo/gitworkshop/
 

 Gitworkshop.dev and ngit handle the code collaboration but to clone a repository, use the git server listed under the repo details. 

 Got it. 

Cool project. It could have a really big impact on the way things are built. 

 Thanks for the encouragement. I might add `ngit clone nevent/identifier` to make it easier to clone projects without having to understand this distinction. ultimately I would like to create a git remote-helper for so users can do `git clone nostr@nevent...` or `git clone nostr@repo-identifier`. That way maintainers could swap out git_servers without the users having to take any action. 

 👀 

 bullish on decentralized github replacement

nostr:note1ph2p00lvnxtyj03ncdtv37mwmd8gj9fppu8ufncd7h6a9vgtfc5svfzfe0  

 Support this !

nostr:nevent1qqsqm4qhhlkfn9jf8ceux4kgldhdkn5fz5ss7r7yeuxltawjky95u2gpzpmhxue69uhkummnw3ezumt0d5hsyg9qpr00z4uklw56p4h6kp8gl4ts3y59m874qhd94ql732k40g6kf5psgqqqqqqs88ek3l