Danilo Bargen

Nice idea!

Right now when starting discovery, a node that is broadcasting multiple advertisement frames with different data will only be discovered once. For using beacons as a means to transfer data,...

It seems that the pinout didn't change, so yes, it should be compatible :slightly_smiling_face: I didn't test it though.

Mostly done in 54138a2575a1b6e84074caa8629e294d85aa45b2

We can't set env vars in the hook files. Someone on Arch IRC suggested to either hardcode the UID (or make it configurable), or to try to detect users with...

@rnestler great, it works! I'm not sure if this is something that could be part of the AUR package? (Or maybe just a separate package that depends on `reboot-arch-btw`.)

The print is needed if you want the log output to show up in the terminal for failed tests. Why would you want it suppressed?

Thanks for the PR! The tests currently fail. Do you plan to update your branch?

What test runner are you using, `cargo test`? That should usually capture all test output, and only show it for failing tests.

We could add a Cargo build flag to suppress log output. I don't want to remove the print in the crate's default behavior though, it is very useful to debug...