-
Notifications
You must be signed in to change notification settings - Fork 86
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
Have an online-updatable lists for browsers, &c #25
Comments
That makes sense, thank you! |
In a related idea, is it sensible to use an app store's own browser list, e.g., Amazon's (if GPlay has 1 I can find, I'll post here, too), as a kind of automated master list of browsers, to which you folks can manually add that which isn't listed? Just trying to make this labor "UNintensive" as possible! |
Anyway we'll need to review that list manually. Look at that list, there are not only browsers |
The whole point of browser-list is that in free version ads are blocked only in browsers. If user will have the ability to edit that list the free version will become paid version. |
Anyway looks like a good idea to me, usually there's at least 1 month between versions release. If you think it's too hard to implement right now, let's plan it later |
Of course, this is true. I meant for AdGuard team's use only! ☺
There is that problem, instead. I posted that only as an example, anyway, but I'll keep looking for a better list & post if/when I find such.… ☺ |
Wikipedia has 1 also, just as a note, though not readily current. |
Here is GPlay's list of recommended mobile browsers, though this list seems less updated than Wikipedia's above. |
I am a bit sick of adding https exclusions all the time, so we'll do https whitelist update earlier than it was planned: |
Based on #22 (comment), it might be worth having the firewall whitelist (for browsers & internals like Google Play services) be updatable just like the filters, with toggled default settings. It does seem a little overkill to have to update an entire APK just to add them, considering the # & frequency of new browsers.
The text was updated successfully, but these errors were encountered: