Pain points of ESP32-C3 Adblock solution
Problem
The ESP32-C3 is being used for ad‑blocking, yet users encounter hash collisions causing false positives, a weak built‑in antenna, inefficient implementation, and poor documentation, which hinder its scalability and performance for large‑scale blocking.
Pain points
- Hash collisions causing false positives
- Weak built‑in antenna
- Poor documentation with AI‑generated content
- Low implementation efficiency, need for better allowlist/Bloom Filter approach
Questions to verify
- Would you consider using a Bloom Filter‑based allowlist implementation in a real project?
- How satisfied are you with the current documentation's readability and technical depth?
- Do you need a stronger collision‑resistant hash implementation to avoid false positives?
Evidence
quote · @匿名
Weird how the readme talks about hash collisions, but not in the way I would expect. Two blocked domains with the same hash isn't a problem, they both need to be blocked.Where hash collisions matter is false positives, e.g. if hash(google.com) = hash(adserver.com). There does appear to be a web dashboard and /unblock api so should be straightforward to resolve.
quote · @匿名
I'm a bit of a paranoid freak that likes lists, so I've got a PiHole that has a total list of 14-16M blocked domains.Great idea, and good for casual blocking, but I'm almost moving to an "allow list" mindset. This solution would probably work better for that, I wonder if the good parts of the internet would fit into an 140k list.
quote · @匿名
I think it could fit even more domains using a Bloom Filter or similar probabilistic data structure. With a chance of false-positives of course. But that's a trade-off the project already makes.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.