| Age | Commit message (Collapse) | Author |
|---|
|
bump all rust-nostr packages
refactoring code based on breaking changes
upgrading to patched version to address signer issue:
nostr:nevent1qvzqqqqqqypzq6xcz9jerqgqkldy8lpg7lglcyj4g3nwzy2cs6u70wejdaj7csnjqy88wumn8ghj7mn0wvhxcmmv9uqzpsw5ph8le2n2kh6uchftawt74hddazk9tp7wjmz967y2l0uva5rc7hsstq
|
|
as sqlite is depricated in rust-nostr
|
|
which includes nip46 signer change so it can be initated
without completing connection.
|
|
bump all rust-nostr packages
|
|
changelog:
- login via nip46 QR code
- enable login directly in git plugin
- add resilience to git plugin so that a poorly formated pr will
gracefully fail and won't cause issues for other prs
and state events
|
|
or nostrconnect url string which is a much better UX flow for nip46
|
|
changelog:
* git plugin reports on event broadcasting
|
|
changelog:
- add new nostr url format that works better for MacOS users
`nostr://<*protocol>/<npub123>/<*relay-hint>/<identiifer>`
\*optional
- status updates during clone, push and fetch
- intelligent protocol selection and fallback
- unless unusual protocol specified in clone url it will try
in this order:
- fetch: https unatuth, ssh, https
- push: ssh, https auth
- save successful protocol in git config so it is tried first
next time
- enable override from nostr url (will only use this protocol)
- enable building binaries via nix
- refactor into lib and bin structure
- bump dependnancies
|
|
in the hope that it addresses the 'early EOF' error that sometimes
appears when cloning a repo.
|
|
update dependancies to latest version stated in cargo.toml
|
|
which were preventing the build process from running
|
|
changelog:
* when clone url is ssh use auth for `list` and `fetch` as
they are required
* when clone url is ssh, fallback to https so read events dont always
require auth
* stop asking for git server credentials when pushing `pr/` branch
* fix `no repo events at specified coordinates` error via rust-nostr
v0.34.1 upgrade
|
|
this fixed an efficency thing which meant we needed to increase
a timeout during the update which is reverted int his commit. see:
nostr:nevent1qvzqqqqx25pzpgqgmmc409hm4xsdd74sf68a2uyf9pwel4g9mfdg8l5244t6x4jdqy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcqyqg5lfwhruw4qjpnlzq0tct0swnuj9dvavz8gsq8npuyygznstw36882alm
|
|
bump all rust-nostr packages
I'm not sure I'm completely happy with allowing mutable_key_type
but it is just run inside tests
it appears that Event didn't have the Copy trait in v0.33.0 so I'm
not sure why this warning suddenly appeared
the timeout of client.get_events_of needed to be doubled which could
indicate that an ineffiency has been introduced in v0.34.0
the primary motivation for upgrading now was to get this fix:
nostr:nevent1qqsffl2ld678pjj77rh9k2g4edljmxdu6ew4lvgnglxv7jhu3ru8vvcpp4mhxue69uhkummn9ekx7mqzyzsq3hh327t0h2dq6matqn5064cgj2zanl2stkj6s0lg4t2h5dty6rm2ucm
as I suspect it is also effecting other repositories
eg nostr-profile-manager
|
|
changelog:
* include git plugin in release zip
|
|
changelog:
* fix clone using nostr url
|
|
changelog:
* fix only maintainers can push normal branches / tags
|
|
changelog:
* fix pushing tags in git-remote-nostr
|
|
changelog:
* add git-remote-nostr binary
|
|
to get latest fixes applied
|
|
support with optional relays as query parameter
|
|
in the future we could implement our own credentials callback function
to remove the dependancy
|
|
changelog:
- fix(init): update maintainers.yaml if identifier or relays have changed
|
|
changelog:
* NIP-46 remote signing (from Amber, etc)
* `list` breaks down proposals by status
* local cache in `.git` to enable viewing proposals offline
and reuse by other git clients
* introduced `fetch` to download recent proposals
* improved repo selection and handling of multiple maintainers
* unqiue branch names for proposals to prevent name conflicts
* login to different npubs for different repositories
* store login details in git config so they can be reused
by other git clients ran locally
* add NIP-31 alt tags to events
* add euc marker per NIP-34 tweak
* fix: ensure repo events of all maintainers are tagged in proposals
* fix: stop filtering out very large patches
|
|
into lib which makes reading and maintaining tests easier
|
|
to prevent accidental name conflicts. also moved to prs/* namespace
`pull` and `push` integration tests are intermitantly failing to end
at least for `push` they work when run individually but not
when run together
|
|
bump all rust-nostr packages
move from using patched nip46 nip05 function to profile function in v33
fix send_events_to error message
|
|
This reverts commit c6cf49d8349c7078e28a3d0e4a7628f91e0195d9
as crates.io requires all dependancies are published to crates.io
we will need to wait until rust-nostr v33 so we don't use the patched
version of v32 from the forked repo
|
|
changelog:
* add support for NIP-46 remote signer
* login to different npubs for different repositories
* store login details in git config so they can be reused by other clients
* cache profile events
* add NIP-31 alt tags to events
* add euc marker per NIP-34 tweak
* fix: ensure repo events of all maintainers are tagged in proposals
* fix: stop filtering out very large patches
|
|
currently using patched version of rust-nostr with function to fetch
nip46 relays from nip05 providers. this patch has been merged so it
will make it into the next rust-nostr release.
|
|
and save details in git config
|
|
on machines not used to compile. it produces error:
'cannot execute: required file not found'
|
|
replace ngit yaml file config with:
* nsec / ncryptsec / npub in git config in nostr.* namespace
* sql database cache for metadata and relay events
allow different logins to be used for different git repositories by
storing login in local git config
|
|
both nostr and nostr-sdk packages and also in test_utils
fix the many breaking changes
fix: ignore trailing slash when depuplicate relays for send events.
this was picked up as TagStandard::RelayMetadata has started adding
a traling slash.
refactor cli output test function `expect_send_with_progress` so that
relays can succeed / fail in a random order
|
|
bump nostr and nostr-sdk packages and also in test_utils
remove custom ncryptsec implementation and use the newly
added implementation nip49 version in rust-nostr
note a patched v0.30 is used so that log_n is exposed so that
user can be warned it might take a few seconds to decrypt.
this has now been merged into the library.
note that this will no longer decrypt existing ncryptsec values as
it is uses a longer string. this should therefore be bundled with
the upcoming change to storing nsec and ncryptsec in git config.
|
|
changelog:
*fix `ngit init` support for multiple maintainers
|
|
changelog:
* remove unreliable relay.f7z.io from default relay set
* `ngit send --in-reply-to` tag any nostr notes and npubs in proposals
* `ngit send` link to proposal on gitworkshop
|
|
changelog:
* improve relay timeout behaviour
* fix `ngit init` handling of multiple values eg `clone`
* improve reliability via with dependancy upgrade
* build via nix in ci
|
|
update dependancies to latest version stated in cargo.toml
|
|
to fix relay.get_events_of timeout
|
|
update dependancies to latest version stated in cargo.toml
|
|
yukibtc released a patch to address intermittent problem
fetching events, which caused our integration tests to fail
|
|
as patch accepted into package
|
|
to address send_event_to spurious timeout error
|
|
as it has been removed from nostr_sdk
|
|
both nostr and nostr-sdk packages and also in test_utils
|
|
update dependancies to latest version stated in cargo.toml
|
|
changelog:
* fix stack overflow bug when origin remote doesnt exist
|
|
changelog:
* `ngit send` - improve proposal commit
|
|
following semantic versioning, this release includes breaking changes
so it has a new major version
this is not reflection on its stability
|
|
update list to support rebases via proposal revisions
as created by `ngit send --in-reply-to`
or upcoming change `ngit push --force`
|
|
in preparation for issuing to crates.io
|
|
update dependancies to latest version stated in cargo.toml
|
|
this is a contribution from jk (sectore) that I rebased and squashed
into this commit.
the tests were broken in the last few commits to rush out some fixes.
this change may introduce more issues because of
Relay.respond_standard_req.
|
|
in preparation for issuing to crates.io
|
|
|
|
the branch that was referenced was merged 3 months ago but there hasn't
been a new release so targeting the merge commit
|
|
- create yaml file with maintainers and relays
- add maintainers to repo event
- add current user as maintainer
- custom repo relays from cli argument
- save git-server in repo event
|
|
replace local reference with fork on github
|
|
fix breaking changes
|
|
with `cargo update` to prevent bumping stated dependancy versions
|
|
use a patched websocket server that releases port after x connections
enabling its use in many tests included in the same test run
|
|
get user relay list and metadata events from relays when keys are
used and last fetch attempt was more than an hour ago
uses user's write relays if known, otherwise uses fallback relays
to achieve this a method for intergration testing event fetching
from relays was added
|
|
add tests but these currently don't work when run together
|
|
- add client
- use client to send event
- add async functionality - enabler for relay interaction whilst
getting cli input
|
|
update dependancies to latest version stated in cargo.toml
|
|
- identify commits
- create pull request event
- create patch events
|
|
Enables the user to only handle the nsec upon first use of the tool
by encrypting it with a password and storing it on disk in an
application cache.
The approach to encryption draws heavily from that used by the gossip
nostr client.
- unencrypted nsec is zeroed from memory
- a salt is used to defend against rainbow tables
- computationally expensive key stretching defends against
brute-force attacks of passwords with low entropy.
There is UX trade-off between decryption speed and key-stretching
computation. This UX challenge is exacerbated in a cli tool as
decryption must take place more regularly. Thought was put into the
selected n_log and a heavily reduced value is provided for long
passwords where security benefits are smaller.
A more granular reducing in computation was also considered by
rejected to avoided to revealing just how weak a password is as most
weak passwords are reused.
|
|
Create skeleton for a complete rebuild of the prototype as a production
ready product.
Includes design patterns for:
- dependency injection
- unit testing with dependency mocking
- integration testing
- error handling
- config storage
BREAKING-CHANGE: ground-up redesign with incompatible protocol standards
|
|
|