nostr/strfry
1
0
Fork 0
mirror of https://github.com/hoytech/strfry.git synced 2025-06-17 00:38:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

release 1.0.0

Browse Source
This commit is contained in:
Doug Hoyte
2024-09-13 01:03:36 -04:00
parent 240d251031
commit 2da619ed23
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
CHANGES
View File

@ -13,8 +13,8 @@
of negentropy fingerprints over arbitrary nostr queries. By default the of negentropy fingerprints over arbitrary nostr queries. By default the
query {} (the full DB) is tracked, but additional queries can be added query {} (the full DB) is tracked, but additional queries can be added
using the new `strfry negentropy` command. using the new `strfry negentropy` command.
* The negentropy version is now indicated in the NIP-11 relay information * Advertises NIP-77 support (negentropy syncing). The negentropy version is now
and the HTML landing page. also indicated in the NIP-11 relay information and the HTML landing page.
* Parsing-related error messages were greatly improved. Instead of just getting * Parsing-related error messages were greatly improved. Instead of just getting
"bad msg: std::get: wrong index for variant", in most situations you will "bad msg: std::get: wrong index for variant", in most situations you will
now get a more useful message such as "first element not a command like REQ" now get a more useful message such as "first element not a command like REQ"
@ -25,6 +25,7 @@
do not need to be separately installed to build strfry. do not need to be separately installed to build strfry.
* Bugfix: When querying for 2 or more tags where one of the tags was a prefix * Bugfix: When querying for 2 or more tags where one of the tags was a prefix
of the other, matching events would not be returned. Reported by mrkvon. of the other, matching events would not be returned. Reported by mrkvon.
* Updated and re-organised the README.md docs
0.9.7 0.9.7
* `--fried` support from 1.0.0 was back-ported, allowing export of DBs * `--fried` support from 1.0.0 was back-ported, allowing export of DBs