npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/src/lib/login/existing.rs, branch v2.0.0Personal mirror of DanConwayDev/ngit-cli on git.upleb.uk
https://upleb.uk/npub1tkq8unhsd5jqx6ueex5lcpsgknrpquxuk44ftpjlpm3ulaake7xs76txrw/ngit-cli-mirror/atom?h=v2.0.02025-04-01T13:35:50+00:00chore: bump rust-nostr v0.37 ~> v0.402025-04-01T13:35:50+00:00DanConwayDevDanConwayDev@protonmail.com2025-04-01T13:31:34+00:00urn:sha1:948fe972eb2bddf187b79f2673a091b6331cfd90
and fix all of the breaking changes
chore: bump nix flake rust nightly `fmt` overlay2024-12-16T09:46:30+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-16T09:00:46+00:00urn:sha1:4ee83e2fe5335a8afd78439c35f029c4a472e797
update the rust nightly `fmt` overlay which needs to be pinned
to a specific version (this case by date)
update formatting in main files via `cargo fmt`
fix: fetch user relays for `send`,`push` & `init`2024-12-09T15:35:18+00:00DanConwayDevDanConwayDev@protonmail.com2024-12-09T15:35:18+00:00urn:sha1:d8f4f7641312bff32f772cbc070b3f99ced0c8fe
get the latest user relay list before pushing patches and repo
announcement events
feat(login): contact remote signer when needed2024-11-27T17:20:28+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T17:20:28+00:00urn:sha1:75cd323e2481502671aa1f62b28875d95f9863c3
for existing login, the remote signer should only be called when an
event needs to be signed. This might be a AUTH event so we still
need to call it during read scenarios.
a feature was added to rust-nostr to enable this.
feat(export-keys): to use in other clients2024-11-27T07:41:25+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-27T07:41:25+00:00urn:sha1:c92e252adc9990fa4d147bad0a8bccafc19dfbb8
as part of the easy on-boaridng flow
test(login): update `ngit login` test2024-11-26T16:28:09+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-26T16:28:09+00:00urn:sha1:bdf71cb3d5a5ff8399c10c8d2492d3dd01c5fa33
to reflect the new interface and testing only nsec login
refactor: err msgs 'cannot' > 'failed to'2024-11-26T12:26:47+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-26T07:48:30+00:00urn:sha1:a0593e3aa9b19b9ca3c3881cbe0d9d207fe46d2c
in nearly all cases 'cannot' was used when an action was tried and
failed. 'failed to' is strictly better because:
* just because the action didn't work that time doesnt mean it
cannot work
* it is better at drawing the users attention to a problem
feat(login): overhaul login experience2024-11-21T16:53:17+00:00DanConwayDevDanConwayDev@protonmail.com2024-11-21T16:53:17+00:00urn:sha1:f79014235e85554e3661b3f2a02b8fa88bc192ff
* simplify login menu, making it more accessable to newcomers and
easier to select remote signer options
* enable `ngit login` to work from anywhere (not just a git repo)
* assume fresh login details saved to global git config but fallback
to local repository
* maintain local repository login via `ngit login --local`
* maintain login via CLI arguments eg `ngit send --nsec nsec123`
* nudge users to remember nsec when pasting in ncryptsec for a
better UX, whilst maintaining the option to be prompted for
password everytime
* create placeholder menu items for help menu and create account