Andrey Meshkov

Technically that's possible, but that's not an easy task. Here's how the check is done at the moment: 1. The website makes an HTTPS request to `https://{randomID}-dnscheck.adguard-dns.com/`. 2. This domain...

DNS64 is already [supported by dnsproxy](https://github.com/AdguardTeam/dnsproxy#dns64-server) which AdGuard Home uses under the hood. So this task may be split in two parts: expose DNS64 prefix setting via `AdGuardHome.yaml` (can be...

Well, on the other hand in the case of Safari declarativeNetRequest is built on Safari content blockers. Maybe it was added there as well?

Here's the relevant changeset in Safari: https://trac.webkit.org/changeset?reponame=webkit&new=287040%40trunk&old=287039%40trunk

Had a talk with a WebKit engineer. 1. `redirect` rules are actually available via content blockers file: https://github.com/WebKit/WebKit/blob/cf203f4511ff5d596126af5057da721eb625901f/Source/WebCore/contentextensions/ContentExtensionActions.cpp#L311 2. The problem is that they won't work as they require extension...

I don't get it, the point of this issue is pretty much the same as in yours -- prevent people from accidentally enabling HTTPS filtering when it can cause trouble.

It's just this issue covers more than just the HTTPS filtering, it also covers known issues.

https://github.com/AdguardTeam/AdGuardHome/wiki/Getting-Started#running-without-superuser

It's not planned on any milestone yet. The feature request is rather complicated, and the problem is websites' categorization data: 1. It's unclear where to get it. 2. If this...

@Aikatsui ideally, we'd prefer an open-source categorization solution for AdGuard Home integration (if that's possible).