Use `ngit acount login -I --signer-relay wss://example.relay123.com --signer-relay was://example.relay456.com` to use different signer relays. Also use --verbose for more logging.

i understand i login once per machine, not once per repository right? I logged in before and published a repo two days ago - everything was smooth. Ok, trying to relogin

so it asked me to logout which i confirmed, and then at the end failed with ``` Error: a different signer credential is already stored for @npub1lczx...wxyr; refusing to replace it. Re-run with `--alias <name>` to store this remote signer connection separately ``` without telling how to clean this up. I figured to delete ~/.local/share/ngit but error message could be better (or better yet it should clean up on logout i understand)

Yes. I suspect there are probelms connecting/publishing to the default signing relays. I found it supprisingly difficult to chose defaults that were reliable consistently.

after this `ngit init` worked, so indeed it was the issue with relays? Is it Amber bug? It should have been reading events from the relays in the previous login right?

btw i remember the doc i read explicitly said "do not relogin, just restart your bunker/signer". Here

OpenSats

Good Luck Banning a Key Pair

We can bring back git's decentralised roots with nostr.

> If ngit init or a git push ever hangs, Ctrl+C it, restart the bunker and run it again, no new login needed. so maybe need to update the guides.. Because this is really frustrating

I've found connection problems on the amber aide and the relay side. Sometimes I find amber isn't connected to relays and force quiting and reopening is the quickest way to fix the connection. I wouldn't be surprised though if it works with your custom set of signed relays for a while and then has periods where it just didn't. It took a lot of trial and error to choose the defaults but reliably changes over time. I should probably setup some logging and slowly rotate the defaults based on data.

I see. I wonder if it the nature of android networking overall when connections can die silently and not much the app can do, will the signer on the laptop work better?

Thanks for this feedback. Its designed to make it easier to use multiple accounts. You have to use `ngit account logout --forget` to remove the association. I should certainly improve that error message to indicate this.

The ideal setup rn is a desktop signer running with a local relay. I think we have work to do in the nostr ecosystem for desktop signing UX.

I'm really open to suggestions for the doc site:

ngit documentation

Accounts and keys | ngit

Store identities safely, use remote signers and aliases, and select keys for automation.

I've tried to as much as possible indicate in the CLI when it is waiting for a signer. Personally I manually sign quite of lot of things in Amber and really like the experience. Particularly if an agent is doing things, so I can review everything it pushes with my main account and not @DanConwayDev's Agent