DanConwayDev -- 58d ngit v2.2.3 now makes it easier to customise the signer relays via `ngit account login`. also it now has hopefully better defaults. reply [1 reply]ngit v2.2.3 now makes it easier to customise the signer relays via `ngit account login`. also it now has hopefully better defaults.
thread · root e47f4b0d…a8d3 · depth 9 · · selected dfc1132e…caed
thread
root e47f4b0d…a8d3 · depth 9 · · selected dfc1132e…caed
nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngmyntqgnostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3kamnwvaz7tm5dpjkvmmjv4ehgtnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnvv9hxgtcqyp6hjpmdntls5n8aa7n7ypzlyjrv0ewch33ml3452wtjx0smhl93jakh2ck I'm getting an infinite loading screen whentrying to scan a qr code generated by ngit on both 4.1.7 and 4.1.12. Regular bunker URL generated in Amber worksfine (although with a decent delay in ngit, and with the bunker url being printed a bunch of times). Let me knowif there's any more info I can provide.
Oh, this is ngit 1.6.0, let me check for an upgrade
Still happens in ngit 2.2.0. I think the problem might be relay selections?nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3kamnwvaz7tm5dpjkvmmjv4ehgtnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnvv9hxgtcqyp6hjpmdntls5n8aa7n7ypzlyjrv0ewch33ml3452wtjx0smhl93jakh2ck the loading screen persists on every pageeven when I navigate.
What relays is it using? relay.nsec.app is not working properly sometimes.The loading screen is after accepting the connection?What version of amber are you using?
Did you also try to force close amber and opening it again?
Version is 4.1.12, closing and reopening freed it up, but the connection looks halfway broken (Amber shows itbut ngit never completes). I do think relays may have something to do with it, ngit is using relay.nsec.app andrelay.ditto.pub
relay.nsec.app is receiving the message but not replying the the ok (never replies anything)But ditto took a few seconds and worked```login to nostr with remote signer via nostr connectsaved login details to global git configsearching for profile...failed to find profile...logged in as nostr:npub1ynzq5hnhzaaqyzylz62e5y9ara549655ztk8kjnzv79vd8jyl4yspl09ty```
Other good relays for signers are are ephemeral.snowflare.cc and bucket.coracle.socialnostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3vamnwvaz7tm9v3jkutnwdaehgu3wd3skuep0qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vng9p053e
ngit v2.2.3 now makes it easier to customise the signer relays via `ngit account login`. also it now hashopefully better defaults.
Oh, this is ngit 1.6.0, let me check for an upgrade
hodlbod -- 59d [parent] | reply [1 reply]Still happens in ngit 2.2.0. I think the problem might be relay selections? nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3kamnwvaz7tm5dpjkvmmjv4ehgtnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnvv9hxgtcqyp6hjpmdntls5n8aa7n7ypzlyjrv0ewch33ml3452wtjx0smhl93jakh2ck the loading screen persists on every page even when I navigate.
7579076d…cb19 -- 59d [parent] | reply [1 reply]What relays is it using? relay.nsec.app is not working properly sometimes. The loading screen is after accepting the connection? What version of amber are you using?
7579076d…cb19 -- 59d [parent] | reply [1 reply]Did you also try to force close amber and opening it again?
hodlbod -- 59d [parent] | reply [1 reply]Version is 4.1.12, closing and reopening freed it up, but the connection looks halfway broken (Amber shows it but ngit never completes). I do think relays may have something to do with it, ngit is using relay.nsec.app and relay.ditto.pub
7579076d…cb19 -- 59d [parent] | reply [1 reply]relay.nsec.app is receiving the message but not replying the the ok (never replies anything) But ditto took a few seconds and worked ``` login to nostr with remote signer via nostr connect saved login details to global git config searching for profile... failed to find profile... logged in as nostr:npub1ynzq5hnhzaaqyzylz62e5y9ara549655ztk8kjnzv79vd8jyl4yspl09ty ```
hodlbod -- 59d [parent] | reply [1 reply]Other good relays for signers are are ephemeral.snowflare.cc and bucket.coracle.social nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3vamnwvaz7tm9v3jkutnwdaehgu3wd3skuep0qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vng9p053e
I've been testing all day and I'm getting a lot of inconsistencies. I think it is a combination of things. relays being flaky with remote signing events, a lack of full compliance with nip46 in rust-nostr and a resulting lack of resilience with Amber. i found more consistency with `nak bunker` running on the same machine. Also with opther nip46 client implementations eg nostrify one used in https://mew.ditto.pub