Allows the user to easily initiate an unblock request when an HTTPS site was denied by the adam:ONE® system.
You really need to disclose that you have a listener set up in the background via blockedhttpsdetector_background.js that literally catches ALL error URLs, and apparently ALL headers of sites I browse to your site of http://mytools.management/isblocked". Nowhere in the description or installation does it inform me as the user that my ENTIRE browsing history/activity is potentially being not only sent to your site (privacy) but then what obviously happens to my browsing performance if/when we all have to first send our traffic through your site?!? This alone takes it from a five-star extension to a one(zero)-star IMO and no way I'll continue to use it.
Before DNSThingy, I thought Cisco's Umbrella product was my best line of protection, except for the bypass of DNS lookups via HTTPS. DNSThingy's DTTS product is a singularly brilliant strategy to enforce protection at Layer 2 -- by assuring any outgoing connection is first qualified via a FQDN which allows one to evaluate the domain's reputation BEFORE allowing the connection!
Makes whitelisting possible!
Thomas Rientjes
Sabconnect++ Developers
https://clearurls.xyz
https://privacy.com
https://karakeep.app
bog
Raymond Hill (gorhill)
C.Vaes & T.Reinartz
badsgahhl
Moussekateer
http://sbussetti.github.io/deluge-siphon/
https://xbrowsersync.org
