3 ms·
Again, the key is block vs allow by default, not whether it's per application. But yes there's real world use cases for per application filtering -- you want F
by JulianWasTaken 4y ago
Again, the key is block vs allow by default, not whether it's per application.
But yes there's real world use cases for per application filtering -- you want Facebook messenger to reach Facebook.com but probably not any other applications.
- dark-star 4y agoAh, but if I use the FB messenger, I probably trust FB enough that I also regularly visit/use it in my browser, and probably even use it to authorize other apps and services through it... So I'll have to unblock every app that uses FB services anyways. And FB's trackers and ad-services and other privacy-invading stuff is all on different sub-domains that PiHole or any other "generic" firewall blocks anyways, so again I'm fine without application-level firewalling
- throw0101a 4y ago> Ah, but if I use the FB messenger, I probably trust FB enough that I also regularly […] Except if someone sends you a specially crafted message that causes an exploit to be triggered which could contact some other site to download malware on your system. * https://www.wired.com/story/facebook-messenger-bug-bounty/ https://www.wired.com/story/facebook-messenger-bug-bounty/ Do a search for "no-click exploits": * https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-into-nso-zero-click.html https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-i... You may trust the authors of the software and how the software acts as intended, but you should also considered unintended / undesired usage.