The hyperloglog unit tests depend on the presence of /usr/share/dict/words (see https://github.com/tylertreat/BoomFilters/blob/611b3dbe80e85df3a0a10a43997d4d5784e86245/hyperloglog_test.go#L34). It would be helpful to include the test data in the repo to ensure the tests work without modification on systems that don't follow that dictionary path convention or don't load a dictionary package.

For some use-cases, Xor filters are supposed to be faster and smaller than Bloom and Cuckoo filters.
Recently, support for strings was added to the xorfilter Rust crate:
https://github.com/bnclabs/xorfilter/blob/master/tests/xorfilter.rs#L56
We should test that to see if they make our wasm binary smaller.

If someone wants to give this a shot, please write

Hello old friends,

Galaxy has shipped v3.0.0a1 but links to the v2 docs as the v3 docs aren't being built:

https://github.com/galaxyproject/tools-iuc/blob/60e2302cfac90d0c909ef61815aaaafaaad5816a/tools/khmer/macros.xml#L2

https://github.com/galaxyproject/tools-iuc/blob/60e2302cfac90d0c909ef61815aaaafaaad5816a/tools/khmer/macros.xml#L92

https://khmer.readthedocs.io/en/v3.0.0a1/

Ch

Currently, threads are only used for testing framework (and not testing cases themselves). IMO, it's better to shift responsibility for running tests in parallel to the testing environment (make test -j8) and decouple it from the testing code.

Following a previous issue, #34:

I would also prefer a simple solution that doesn't require Threads. I've written a small unit test framework for CA

Currently the wallet displays a QR for the latest 'new' address, however there is no way to have it show a QR for a previously used address.
We should expose such functionality via the address book, as well as potentially via right click (or a button) in the transaction list screen.

The documentation link at the bottom of the readme page seems to jump to a local up address. I think maybe needs updating?