Tracking issue for sites broken by DPI protection

[sfionov]

When CoreLibs 1.9.69+ will be deployed to AG products, this list may be used for adding $stealth exclusions.

• [ ] https://www.ghxi.com/
• [ ] http://go.gov.il
• [ ] https://www.thegioididong.com/
• [ ] https://tvr.by/
• [ ] https://pravo.by/
• [ ] https://beltelecom.by/ but https://my.beltelecom.by/ works (comment)
• [ ] https://blog.torproject.org/ but https://www.torproject.org/ works (comment)
• [ ] https://github.com/AdguardTeam/CoreLibs/issues/1634
• [ ] https://github.com/AdguardTeam/CoreLibs/issues/1636
• [ ] https://github.com/AdguardTeam/CoreLibs/issues/1639

[piquark6046]

New domain: q-net.or.kr

[ameshkov]

@Alex-302 what about now? :)

[Alex-302]

@ameshkov We use it now https://github.com/AdguardTeam/AdguardFilters/commit/21a8f1a70db7c85e1cdfa3063a0ad8e162ca21e2 The problem is that these rules are often removed from optimized filters for AdGuard for Android, and we forced to use !+ NOT_OPTIMIZED for each of these rules (no equivalent directive, or switch for using full filters for modern Android devices).

[ameshkov]

@Alex-302 these rules shouldn't be optimized indeed, we'll resolve it in another task (see ADG-7346)

[ameshkov]

Closing this one since now all CoreLibs-based products support $stealth=dpi