-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Pause Assitant #2226
Comments
deflecting the breakage from Ghostery and towards all ad blockers: pause flow: revoke flow: |
Copy we agreed upon with JP today: main text: revoke flow: thoughts to copy: lemme know what you think, team! |
We don't have a signal for the difference "100% sure" from "less sure", so I put the first one - we will likely use the feature for obvious (and spread) failures. |
:) I think you didn't understand it @smalluban no two options needed. we might phrase it differently (blanket) based on how sure engineering is that the page is broken by us/ad blockers and this system works here is the slight difference: |
I know what you meant. However, we have to choose one text, as the current implementation of remote config does not give information about whether it is broken 100% or might be broken - we can't create that logic in the current iteration (or we would have to change remote config - I think this is not worth it for now). |
pause flow:
Main text: Our community reports that Ghostery breaks this site. We recommend pausing it temporarily.
Additional text: Ads and trackers will not be blocked.
OK
Site works fine
revoke flow:
Our community reports that Ghostery no longer breaks this site. Resume Ghostery.
OK
another button?
We’re so glad Ghostery has your heart! Let others know—leave a review!
OK
Skip this time
The text was updated successfully, but these errors were encountered: