4 ms·

You're welcome. It was my pleasure to share it. I was using IodéOS that has similar blocker built-in - but it is not open source so I was looking for no root a

You're welcome. It was my pleasure to share it. I was using IodéOS that has similar blocker built-in - but it is not open source so I was looking for no root alternative to control specific app/domain connections and this blows my mind. FOSS, pleasant UI, many very useful features for prevent leaks and so on... Btw what is different between blocking individual domains (soon in DNS) and blocking connection in firewall for specific domain?

ignoramous 4y ago
A dns name may be mapped to multiple IPs (case 1). Same IP could be mapped to multiple dns names (case 2). So, if you're blocking an IP, you might end up blocking multiple domains (case 2) or end up not even effectively blocking a single domain (case 1). This confuses users, and you get reports like: 1. I blocked a Google IP but my app still connects to google.com (case 1, since Google owns a gazillion IPs). 2. I blocked a cloudflare.com IP and now can't access reactjs.org (case 2, where IPs are shared). Some folks find it easier to reason about rules on domain names than IPs. So, blocking/allowing domain names makes for a better user experience, when implemented right.
- t0bia_s 4y ago
  Thanks!