Did you notice this problem with insufficient blocking on different websites, or just on that one? If former, what are other examples of such websites?
And about your other question, how did you measure the battery consumption?
PS: this article should be of interest to you...
@ShiZzO поговорил с разработчиками, советуют записать трафик на роутере во время nslookup. Сделать это можно с помощью tcpdump, например.
После этого вы увидите, что с локальных компьютеров уходят незашифрованные запросы, а на внешнем интерфейсе их уже нет.
We haven't run the extensive tests yet. Some users complain about issues on iOS12, but other claim that they have no problems. Hard to tell yet, we'll come out with an announcement (via Blog) if needed.
Hi! There will be a Blog (blog.adguard.com) article on this topic, hopefully this week. Briefly:
- Similar will happen to a lot of other extensions. Apple gets rid of older Safari extensions, plans to finish the process by December;
- For now you can simply re-enable AG extension...
@Morku apologies for not replying in time.
In your examples the highlighted text is actually not a parameter but a part of URL, so the Stealth Mode option doesn't work. We need to take this into account in our future updates, perhaps we will ebven create a userscript of some sort that can cut...
Not all URL parameters are considered tracking parameters. It is possible though that we need to update our current list. If you think some particular parameters should be blocked (and aren't currently), please list them and we'll consider including them.
I guess you were seeing a standard VPN/custom certificate notion. You can recreate it by tapping on the “network is monitored” notification, in fact, you will see it with any VPN app. This notification is forced by the system whenever any VPN is up.
Hello, sadly, Apple will not allow us any further updates neither to relaese nor to beta versions of the app. Well, unless we strip it of functions that make the difference between Pro and regular version.
@Skippermark we know about this workaround, and chose conciensely to not do it. The reason is, a lot of rules in our filters refer to each other and "work together". When you separate them into several content blockers, they can't do that anymore.
We consider finding a way to divide filters...