Lazy commenters need to look at the README to see that the bloom filter is mentioned as a next step. The hacker is indeed clever.

> how it could grow : Bloom filter in RAM as a fast pre-filter (skip flash for the ~99% of misses)

https://github.com/M-Abozaid/esp32-c3-adblock

The README mentions it and conventionally it seems right.

But back of the envelope it seems you're shaving not much off if the latency is primarily WiFi latency (tens of milliseconds) not flash reads (microseconds?).

If you use loads of transient clients perhaps a LRU cache would help since round trips might be quite slow.

Double space. Go from 42 bit to 46 bit and you get the same. Still wondering about the dynamic binary search. A static search can be faster, even on an AVR

I opened the article and immediately ctrl-f'd for the word "bloom". Though the author plans to use them.

What do people use bloom filters for in production? I've only ever used as part of a blacklist