Oddbean new post about | logout
 The same goes for the rest of you.
https://i.nostr.build/6G09W.jpg 

nostr:nevent1qvzqqqqqqypzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ceqythwumn8ghj7mtvv44h2tnwdaehgu339e3k7mf0qydhwumn8ghj7argv4nx7un9wd6zumn0wd68yvfwvdhk6tcqyz2q7lyr4drnx6grn33cwvh7a5xuc8qyaajar3rc0sd9sc2zl26ckkcj30p 
 I'm @Silberengel on there, if you're wondering who the nag -- errrr.... I mean, "tester" -- is. 😁 
 And, for everyone who hasn't heard it a million times: 

Our Linux client is going to use Ngit as the CLI and you can use GitWorkshop when you're on your phone or otherwise away from your PC. These are a suite of interoperable Ngit tools for different user bases and environments, not direct competitors.

Please move onto Ngit immediately. We at @GitCitadel  are also on Ngit. Thank you. 
 One of the reasons we've decided to use Ngit as our CLI is to ensure interoperability dynamically, rather than through written specs. This means that if we need some new CLI feature, we'll be making a ngit proposal.

I've been testing the CLI for months now, and have had no problems working together with Dan, so we want to use his stuff and maintain the collaboration.
He's very responsive and hard-working, and his own ngit and gitworkshop repos are listed on the first page. 
 Replies to ngit-generated events are handled in Gossip, Nostrudel, Coracle, Freerse, and Amethyst. Probably also in Damus, but I don't have an iPhone.

That means you can write an issue proposal in Ngit or GitWorkshop and then chat about it in any of those apps or continue the conversation on GitWorkshop.