adam:ONE® assist
Allows the user to easily initiate an unblock request when an HTTPS site was denied by the adam:ONE® system.
Total ratings
4.33
(Rating count:
18)Review summary
These summaries are automatically generated weekly using AI based on recent user reviews.
Chrome Web Store does not verify user reviews, so some user reviews may be inaccurate,
spammy, or outdated. Pros
- Provides valuable functionality for managing white-lists.
- Indispensable when used with other extensions like HTTP Request Blocker.
- Simple and straightforward to use.
- Excellent at solving specific problems for users.
- Utilizes Layer 2 protection by evaluating domain reputation before connections.
Cons
- Lacks transparency about background listeners and data collection.
- Potentially impacts user privacy by capturing entire browsing history.
- Performance concerns when sending traffic through the extension's site.
Most mentioned
- Need for better disclosure regarding data collection and privacy.
- Helps in whitelisting and managing connections effectively.
- Users express high frequency of using the extension daily.
Upgrade to see all 16 reviews
Recent reviews
Recent rating average:
4.20
All time rating average:
4.33
Upgrade to see all 16 reviews
Rating filters
5 star 4 star
3 star
2 star
1 star
| Date | Author | Rating | Lang | Comment |
|---|---|---|---|---|
| 2019-08-13 |  | | 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. | |
| 2019-08-14 |  | | en | 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. |
| 2019-02-08 |  | | 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! | |
| 2019-02-08 |  | | en | 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! |
| 2018-07-19 |  | | Simple, straigforward, valuable. Indispensable for using with HTTP Request Blocker extension. | |
| 2018-07-19 |  | | en | Simple, straigforward, valuable. Indispensable for using with HTTP Request Blocker extension. |
| 2018-03-28 |  | | Makes whitelisting possible! | |
| 2018-03-28 |  | | en | Makes whitelisting possible! |
| 2017-03-15 |  | | Excellent! Solved my problem! | |
| 2017-03-15 |  | | en | Excellent! Solved my problem! |
Upgrade to see all 16 reviews