ESP32-C3 Adblock

26 points by jayhoon 2 hours ago | 5 comments

Whitelist/allowlist is easier, e.g., it's smaller

Depends on the user but not everyone is visiting new websites everyday

Even for those that are, the number of domain-IP mappings needed will be relatively small

Definitely under 140,000

Most DNS data I use is "static", it rarely changes. As such most times I don't have to make DNS queries. I store the domain-IP mappings in proxy memory; this is faster than DNS

No "blocklist" needed

muti 1 hour ago |

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.

zamadatix 37 minutes ago | |

Yeah, I think they have it backwards. As you say, regardless of how many entries you have locally, the collision risk comes from false positive hash matches not from worrying if the positive hashes collide.

fwip 1 hour ago |

Cool idea, latency might be too high, wish the docs weren't all AI vomit.

thenthenthen 25 minutes ago | |

This will be slow for one user, let alone more than one