Luke Dashjr

specifically in output-1.39.0/libcore.rlib.c

aed9b3665c39f594f4cf8c46afe5048655a72c77 is the first bad commit (for the `-ll` thing)

Trying 6f42b7415dc6c91ba41f8afb7d9e807e7c139c38, `output/cargo` fails with ``` thread 'main' panicked at 'assertion failed: `(left == right)` left: `1`, right: `0`', rustc-1.39.0-src/vendor/hashbrown/src/raw/mod.rs:1086:59 Process was terminated with signal 6 FAILING COMMAND: /var/tmp/portage/dev-lang/rust-1.40.0_p20220113/work/rustc-1.40.0-src/mrustc/output/cargo-build/build_miniz-sys-0_1_11_run thread...

As of f08a7cb0641fed5410b4c92f3e4446413c897d2f trying to build 1.39.0: ``` ... (17/112) BUILDING cc v1.0.35 > /mnt/hd2019c-nobackup/dev/rust/mrustc/bin/mrustc rustc-1.39.0-src/vendor/cc/src/lib.rs -o output-1.39.0/rustc-build/libcc-1_0_35.rlib --crate-name cc --crate-type rlib -C emit-depfile=output-1.39.0/rustc-build/libcc-1_0_35.rlib.d --crate-tag 1_0_35 -g --cfg debug_assertions -O...

What if you don't care about pairing with Apple stuff, and only want to use openhaystack?

@brianr2600 The mentioned "Keys" subdirectory doesn't appear to exist in Big Sur at least.

#37 mentions a "MasterBeacons" directory, which does exist with files for each airtag, but I don't really have time to investigate if there's a way to use those.

> libkscreen should have no dependency outside of qt. Oh, it very much does: Wayland stuff. I just opened #1068 here as a result...

This seems to be based on the assumption that the DoS is attacking disk space, but bandwidth tends to be more limited than space, and it makes that worse even...

Is there a reason to not just prune the block index under some conditions?