Andrey Meshkov
Andrey Meshkov
I guess for @gorhill's approach it won't be that good as he sends a web request to detect if WS connection should be blocked or not. But in our case...
Well, when we experimented with Windows 10 VPN API many years ago (when mobile Windows was still alive), it was full of bugs and tbh almost unusable. Actually, the point...
There are two solutions: 1. Provide a protocol that Windows natively support. 2. Implement a VPN service using `Windows.Networking.Vpn`, this way we can use AdGuard VPN proto. The first option...
That's the problem with this kind of setup, it's very hard to debug it in general:( Maybe there's something useful in Windows event log?
Well, the proper reaction to redirect directive should be failing the build completely
The point is that when this happens we should react accordingly and change the FiltersRegistry
Hmm, I am not sure about this. You see, AdGuard already has a clear distinction between "content blocking lists" and "DNS filtering blocklists". This feature would make perfect sense if...
Let's wait until the "HostlistsRegistry" repo is up, it makes sense to add this feature request there.
@DandelionSprout regarding the first one, we do not support custom pseudo-classes for the sake of the proper cross-browser support. The second one looks like a bug.