From 465c9aea23eb8e0dfdf6f7f3b67ec2aca487a998 Mon Sep 17 00:00:00 2001 From: Igor Lobanov Date: Thu, 19 Sep 2024 16:32:09 +0200 Subject: [PATCH] Revert "Update translations" --- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 6 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 8 +- .../solving-problems/logcat.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../solving-problems/logs.md | 6 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 12 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 4 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 4 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 648 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 6 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 4 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../solving-problems/logs.md | 2 +- .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 6 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 6 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 6 +- .../solving-problems/logcat.md | 4 +- .../solving-problems/low-level-settings.md | 6 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 6 +- .../compatibility-with-adguard-vpn.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 10 +- .../solving-problems/block-youtube-ads.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../current/adguard-for-mac/installation.md | 2 +- .../solving-problems/advanced-settings.md | 62 +- .../solving-problems/big-sur-issues.md | 44 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/icloud-private-relay.md | 22 +- .../manual-certificate-installation.md | 10 +- .../solving-problems/protect-mail-activity.md | 16 +- .../protection-cannot-be-enabled.md | 4 +- .../solving-problems/screen-time-issues.md | 10 +- .../adguard-for-safari/features/about.md | 2 +- .../solving-problems/logs.md | 10 +- .../admins-documentation.md | 4 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 8 +- .../features/home-screen.md | 2 +- .../adguard-for-windows/features/others.md | 4 +- .../adguard-for-windows/features/settings.md | 28 +- .../adguard-for-windows/installation.md | 6 +- .../solving-problems/adguard-logs.md | 14 +- .../common-installer-errors.md | 22 +- .../connection-not-trusted.md | 16 +- .../solving-problems/dns-leaks.md | 10 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 18 +- .../solving-problems/system-logs.md | 8 +- .../solving-problems/wfp-driver.md | 8 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 674 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 6 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../adguard-browser-extension/availability.md | 12 +- .../comparison-standalone.md | 10 +- .../compatibility.md | 14 +- .../features/filters.md | 2 +- .../features/other-features.md | 2 +- .../adguard-browser-extension/installation.md | 2 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../solving-problems/logs.md | 8 +- .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 6 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 8 +- .../solving-problems/logcat.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 10 +- .../solving-problems/block-youtube-ads.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../solving-problems/logs.md | 8 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 12 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 4 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 4 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 642 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 4 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../adguard-browser-extension/availability.md | 12 +- .../comparison-standalone.md | 8 +- .../compatibility.md | 14 +- .../features/filters.md | 14 +- .../features/main-menu.md | 4 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/installation.md | 2 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../solving-problems/logs.md | 10 +- .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 6 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 10 +- .../solving-problems/block-youtube-ads.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 642 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 4 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../adguard-browser-extension/availability.md | 12 +- .../comparison-standalone.md | 10 +- .../compatibility.md | 12 +- .../features/filters.md | 14 +- .../features/main-menu.md | 4 +- .../features/other-features.md | 10 +- .../features/stealth-mode.md | 2 +- .../adguard-browser-extension/installation.md | 2 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../solving-problems/logs.md | 8 +- .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 6 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 12 +- .../solving-problems/block-youtube-ads.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../current/adguard-for-mac/installation.md | 20 +- .../solving-problems/advanced-settings.md | 6 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 642 +- .../general/ad-filtering/filter-policy.md | 4 +- .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 4 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 6 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 6 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 6 +- .../solving-problems/low-level-settings.md | 14 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/system-wide-filtering.md | 2 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../solving-problems/logs.md | 6 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 58 +- .../common-installer-errors.md | 90 +- .../connection-not-trusted.md | 68 +- .../solving-problems/dns-leaks.md | 52 +- .../solving-problems/dump-file.md | 30 +- .../solving-problems/installation-logs.md | 20 +- .../solving-problems/known-issues.md | 14 +- .../solving-problems/low-level-settings.md | 210 +- .../solving-problems/system-logs.md | 36 +- .../solving-problems/wfp-driver.md | 14 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 644 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 6 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../current.json | 2 +- .../adguard-browser-extension/availability.md | 12 +- .../comparison-standalone.md | 10 +- .../compatibility.md | 16 +- .../features/filters.md | 16 +- .../features/main-menu.md | 4 +- .../features/other-features.md | 10 +- .../features/stealth-mode.md | 2 +- .../adguard-browser-extension/installation.md | 2 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../solving-problems/logs.md | 10 +- .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 6 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 6 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 6 +- .../solving-problems/low-level-settings.md | 8 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 12 +- .../solving-problems/block-youtube-ads.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../current/adguard-for-mac/installation.md | 2 +- .../solving-problems/advanced-settings.md | 104 +- .../solving-problems/big-sur-issues.md | 192 +- .../high-sierra-compatibility.md | 10 +- .../solving-problems/icloud-private-relay.md | 46 +- .../solving-problems/installation-issues.md | 28 +- .../solving-problems/launch-issues.md | 50 +- .../manual-certificate-installation.md | 22 +- .../solving-problems/protect-mail-activity.md | 40 +- .../protection-cannot-be-enabled.md | 16 +- .../solving-problems/screen-time-issues.md | 12 +- .../solving-problems/tor-filtering.md | 20 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../solving-problems/logs.md | 6 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 56 +- .../common-installer-errors.md | 90 +- .../connection-not-trusted.md | 68 +- .../solving-problems/dns-leaks.md | 52 +- .../solving-problems/dump-file.md | 30 +- .../solving-problems/installation-logs.md | 18 +- .../solving-problems/known-issues.md | 14 +- .../solving-problems/low-level-settings.md | 42 +- .../solving-problems/system-logs.md | 34 +- .../solving-problems/wfp-driver.md | 14 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 646 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../current/general/how-to-install.md | 2 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 6 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 4 +- .../current/miscellaneous/acknowledgements.md | 164 +- .../miscellaneous/contribute/beta-testing.md | 32 +- .../miscellaneous/contribute/filters.md | 18 +- .../contribute/translate/become-translator.md | 4 +- .../contribute/translate/guidelines.md | 54 +- .../contribute/translate/plural-forms.md | 144 +- .../contribute/translate/program.md | 10 +- .../contribute/translate/rewards.md | 26 +- .../translate/translation-priority.md | 24 +- .../contribute/updating-knowledge-base.md | 26 +- .../contribute/writing-about-adguard.md | 8 +- i18n/ko/docusaurus-theme-classic/footer.json | 2 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../adguard-browser-extension/availability.md | 12 +- .../comparison-standalone.md | 10 +- .../compatibility.md | 14 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 2 +- .../adguard-browser-extension/installation.md | 2 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../solving-problems/logs.md | 8 +- .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 6 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/firefox-certificates.md | 12 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 8 +- .../solving-problems/logcat.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../multiple-user-profiles.md | 12 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 12 +- .../solving-problems/block-youtube-ads.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../solving-problems/logs.md | 8 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 12 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 4 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 4 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 642 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 4 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 6 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../solving-problems/logs.md | 8 +- .../features/app-management.md | 22 +- .../adguard-for-android/features/assistant.md | 8 +- .../features/free-vs-full.mdx | 2 +- .../features/integration-with-vpn.md | 6 +- .../features/protection/ad-blocking.md | 2 +- .../features/protection/annoyance-blocking.md | 8 +- .../features/protection/browsing-security.md | 4 +- .../features/protection/dns-protection.md | 4 +- .../features/protection/firewall/firewall.md | 32 +- .../protection/firewall/quick-actions.md | 10 +- .../protection/tracking-protection.md | 50 +- .../adguard-for-android/features/rooted.md | 6 +- .../adguard-for-android/features/settings.md | 80 +- .../features/statistics.md | 4 +- .../adguard-for-android/installation.md | 6 +- .../adguard-for-android-tv.md | 4 +- .../solving-problems/background-work.md | 20 +- .../solving-problems/battery.md | 10 +- .../solving-problems/compatibility-issues.md | 4 +- .../extending-restricted-settings.md | 2 +- .../solving-problems/har.md | 12 +- .../https-certificate-for-rooted.md | 4 +- .../solving-problems/log.md | 14 +- .../solving-problems/logcat.md | 8 +- .../solving-problems/low-level-settings.md | 20 +- .../solving-problems/manual-certificate.md | 10 +- .../multiple-user-profiles.md | 6 +- .../solving-problems/outbound-proxy.md | 10 +- .../samsungpay-with-adguard-in-south-korea.md | 2 +- .../solving-problems/secure-folder.md | 2 +- .../solving-problems/tasker.md | 10 +- .../solving-problems/youtube-ads.md | 2 +- .../adguard-and-adguard-pro.md | 2 +- .../adguard-for-ios/features/activity.md | 12 +- .../features/advanced-protection.md | 8 +- .../adguard-for-ios/features/assistant.md | 2 +- .../compatibility-with-adguard-vpn.md | 22 +- .../features/dns-protection.md | 18 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../features/low-level-settings.md | 10 +- .../features/other-features.md | 10 +- .../features/safari-protection.md | 32 +- .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 6 +- .../current/adguard-for-ios/web-extension.md | 4 +- .../features/browser-assistant.md | 32 +- .../current/adguard-for-mac/features/dns.md | 2 +- .../adguard-for-mac/features/extensions.md | 8 +- .../adguard-for-mac/features/filters.md | 2 +- .../adguard-for-mac/features/general.md | 8 +- .../current/adguard-for-mac/features/main.md | 2 +- .../adguard-for-mac/features/network.md | 24 +- .../adguard-for-mac/features/security.md | 12 +- .../adguard-for-mac/features/stealth.md | 6 +- .../current/adguard-for-mac/installation.md | 4 +- .../solving-problems/advanced-settings.md | 10 +- .../solving-problems/big-sur-issues.md | 10 +- .../high-sierra-compatibility.md | 2 +- .../manual-certificate-installation.md | 10 +- .../protection-cannot-be-enabled.md | 4 +- .../solving-problems/screen-time-issues.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../solving-problems/logs.md | 6 +- .../admins-documentation.md | 4 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 8 +- .../features/home-screen.md | 2 +- .../adguard-for-windows/features/others.md | 12 +- .../adguard-for-windows/features/settings.md | 6 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 14 +- .../common-installer-errors.md | 20 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 4 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 4 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 4 +- .../current/general/account/register.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 1592 +-- .../general/ad-filtering/filter-policy.md | 4 +- .../ad-filtering/how-ad-blocking-works.md | 2 +- .../general/ad-filtering/search-ads.md | 2 +- .../tracking-filter-statistics.md | 2 +- .../current/general/browsing-security.md | 24 +- .../general/https-filtering/known-issues.md | 2 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 2 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 16 +- .../current/guides/collect-har-file.md | 8 +- .../current/guides/family-link-certificate.md | 2 +- .../current/guides/minidump.md | 2 +- .../current/guides/proxy-certificate.md | 54 +- .../current/guides/report-bugs.md | 6 +- .../current/guides/report-website.md | 12 +- .../current/guides/take-screenshot.md | 52 +- .../current/intro.md | 4 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/guidelines.md | 2 +- .../contribute/translate/plural-forms.md | 14 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 6 +- .../contribute/updating-knowledge-base.md | 2 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 6 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 2 +- .../solving-problems/logcat.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../solving-problems/logs.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 5 +- .../ad-filtering/create-own-filters.md | 649 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 2 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/minidump.md | 2 +- .../current/guides/report-bugs.md | 6 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../compatibility.md | 14 +- .../features/filters.md | 14 +- .../features/other-features.md | 2 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../solving-problems/logs.md | 52 +- .../features/app-management.md | 2 +- .../features/protection/firewall/firewall.md | 8 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../solving-problems/background-work.md | 22 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../extending-restricted-settings.md | 26 +- .../solving-problems/har.md | 8 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 8 +- .../solving-problems/logcat.md | 4 +- .../solving-problems/low-level-settings.md | 12 +- .../solving-problems/outbound-proxy.md | 30 +- .../solving-problems/tasker.md | 12 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 20 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../adguard-for-mac/features/general.md | 2 +- .../current/adguard-for-mac/installation.md | 12 +- .../solving-problems/advanced-settings.md | 12 +- .../solving-problems/big-sur-issues.md | 82 +- .../solving-problems/icloud-private-relay.md | 24 +- .../solving-problems/launch-issues.md | 48 +- .../manual-certificate-installation.md | 20 +- .../solving-problems/protect-mail-activity.md | 36 +- .../protection-cannot-be-enabled.md | 14 +- .../solving-problems/screen-time-issues.md | 10 +- .../solving-problems/tor-filtering.md | 2 +- .../solving-problems/logs.md | 8 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 4 +- .../adguard-for-windows/installation.md | 8 +- .../solving-problems/adguard-logs.md | 12 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 4 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 4 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 642 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 14 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 6 +- .../current/guides/report-bugs.md | 4 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 8 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- .../comparison-standalone.md | 6 +- .../features/filters.md | 2 +- .../features/main-menu.md | 2 +- .../features/other-features.md | 6 +- .../adguard-browser-extension/mv3-version.md | 100 - .../protected-pages.md | 2 +- .../solving-problems/debug-rules.md | 98 - .../features/app-management.md | 2 +- .../features/protection/dns-protection.md | 2 +- .../features/protection/firewall/firewall.md | 2 +- .../protection/tracking-protection.md | 2 +- .../adguard-for-android/features/rooted.md | 2 +- .../adguard-for-android/features/settings.md | 4 +- .../adguard-for-android-tv.md | 2 +- .../solving-problems/background-work.md | 4 +- .../solving-problems/battery.md | 2 +- .../solving-problems/compatibility-issues.md | 2 +- .../solving-problems/har.md | 10 +- .../https-certificate-for-rooted.md | 2 +- .../solving-problems/log.md | 4 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/manual-certificate.md | 6 +- .../solving-problems/outbound-proxy.md | 8 +- .../solving-problems/tasker.md | 4 +- .../adguard-for-ios/features/free-vs-full.md | 32 - .../current/adguard-for-ios/installation.md | 6 +- .../solving-problems/block-youtube-ads.md | 4 +- .../facetime-compatibility-issues.md | 2 +- .../solving-problems/low-level-settings.md | 4 +- .../solving-problems/advanced-settings.md | 2 +- .../solving-problems/big-sur-issues.md | 8 +- .../high-sierra-compatibility.md | 2 +- .../solving-problems/protect-mail-activity.md | 2 +- .../adguard-for-safari/features/about.md | 2 +- .../adguard-for-safari/features/rules.md | 2 +- .../admins-documentation.md | 2 +- .../adguard-for-windows/browser-assistant.md | 4 +- .../features/extensions.md | 6 +- .../adguard-for-windows/features/settings.md | 2 +- .../adguard-for-windows/installation.md | 4 +- .../solving-problems/adguard-logs.md | 10 +- .../common-installer-errors.md | 18 +- .../solving-problems/dns-leaks.md | 6 +- .../solving-problems/dump-file.md | 4 +- .../solving-problems/installation-logs.md | 2 +- .../solving-problems/low-level-settings.md | 10 +- .../solving-problems/system-logs.md | 2 +- .../solving-problems/wfp-driver.md | 4 +- .../current/general/account/features.md | 2 +- .../general/ad-filtering/adguard-filters.md | 3 +- .../ad-filtering/create-own-filters.md | 639 +- .../general/ad-filtering/filter-policy.md | 2 - .../ad-filtering/how-ad-blocking-works.md | 2 +- .../current/general/browsing-security.md | 8 +- .../what-is-https-filtering.md | 10 +- .../current/general/license/what-is.md | 4 +- .../current/general/stealth-mode.md | 10 +- .../current/general/userscripts.md | 4 +- .../current/guides/collect-har-file.md | 2 +- .../current/guides/report-bugs.md | 2 +- .../current/guides/take-screenshot.md | 18 +- .../current/intro.md | 2 +- .../miscellaneous/contribute/filters.md | 2 +- .../contribute/translate/become-translator.md | 2 +- .../contribute/translate/plural-forms.md | 2 +- .../contribute/translate/program.md | 2 +- .../translate/translation-priority.md | 4 +- .../contribute/updating-knowledge-base.md | 18 +- pnpm-lock.yaml | 11217 +++++++--------- 2150 files changed, 16979 insertions(+), 33860 deletions(-) delete mode 100644 i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md delete mode 100644 i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md delete mode 100644 i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md delete mode 100644 i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/be/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/be/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/be/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/be/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/be/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/be/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/be/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/be/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/be/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/be/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/be/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/be/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/be/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/intro.md b/i18n/be/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/be/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/bn/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/bn/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/bn/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/bn/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/intro.md b/i18n/bn/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/bn/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 22d3bf8da63..4420cc4495b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Zatímco Rozšíření prohlížeče AdGuard je zdarma, snadno se instaluje a ob ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – v rámci omezení prohlížeče a pouze v prohlížeči, ve kterém je nainstalováno; -`2` — the extension is unable to detect requests from other extensions. Pokud škodlivé nebo sledovací rozšíření odešle na svůj server požadavek na zobrazení reklamy nebo sledování vaší aktivity, Rozšíření prohlížeče AdGuard nebude schopno tento požadavek zablokovat; +`2` – rozšíření není schopno detekovat požadavky od jiných rozšíření. Pokud škodlivé nebo sledovací rozšíření odešle na svůj server požadavek na zobrazení reklamy nebo sledování vaší aktivity, Rozšíření prohlížeče AdGuard nebude schopno tento požadavek zablokovat; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Některé prvky se mohou dostat na stránku a zpomalit proces načítání. Kromě toho aplikace AdGuard na rozdíl od blokátorů reklam v prohlížeči blokuje reklamy ještě před jejich načtením do prohlížeče. To šetří provoz a zrychluje načítání stránek. +`3` – ne všechny typy reklam a hrozeb lze blokovat pomocí rozšíření prohlížeče z důvodu určitých omezení prohlížeče. Některé prvky se mohou dostat na stránku a zpomalit proces načítání. Kromě toho aplikace AdGuard na rozdíl od blokátorů reklam v prohlížeči blokuje reklamy ještě před jejich načtením do prohlížeče. To šetří provoz a zrychluje načítání stránek. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index 3afc12cf7c1..77a9b8817af 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ Všechny filtry jsou seskupeny podle své role. Existují například kategorie ## Vlastní filtry -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +Zatímco vlastnosti ostatních skupin filtrů jsou víceméně předvídatelné, existuje skupina s názvem _Vlastní_, která může vyvolat další otázky. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 1468262634b..f427beddeff 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ Hlavní stránka rozšíření je přístupná po kliknutí na ikonu rozšířen Na hlavní stránce můžete ručně skrýt libovolný prvek na libovolné stránce (příslušné pravidlo bude přidáno do _Uživatelských pravidel_), otevřít _Záznam filtrování_ a zobrazit kompletní informace o provozu prohlížeče a blokovat požadavky za chodu nebo se podívat na zprávu o zabezpečení webové stránky. Kromě toho můžete podat stížnost na jakoukoli webovou stránku (například pokud jsou na stránce zobrazené reklamy, naši technici filtrů zprávu přezkoumají a problém vyřeší) a zobrazit statistiky použitých pravidel blokování. -Všechny webové požadavky provedené prohlížečem se zobrazují v _Záznamu filtrování_ spolu s podrobnými informacemi o každém požadavku. _Záznam filtrování_ umožňuje například snadno sledovat požadavky blokované Rozšířením prohlížeče AdGuard. Kromě toho vám umožňuje zablokovat jakýkoli požadavek nebo přidat dříve zablokovaný požadavek na seznam povolených pouze dvěma kliknutími. _Záznam filtrování_ vám také nabízí širokou škálu možností pro třídění webových požadavků, což může být užitečné při vytváření vlastních pravidel filtrování. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +Všechny webové požadavky provedené prohlížečem se zobrazují v _Záznamu filtrování_ spolu s podrobnými informacemi o každém požadavku. _Záznam filtrování_ umožňuje například snadno sledovat požadavky blokované Rozšířením prohlížeče AdGuard. Kromě toho vám umožňuje zablokovat jakýkoli požadavek nebo přidat dříve zablokovaný požadavek na seznam povolených pouze dvěma kliknutími. _Záznam filtrování_ vám také nabízí širokou škálu možností pro třídění webových požadavků, což může být užitečné při vytváření vlastních pravidel filtrování. _Záznam filtrování_ můžete otevřít výběrem příslušné položky v hlavní nabídce nebo na stránce nastavení (na kartě "Další nastavení"). Kliknutím na ikony v pravém horním rohu hlavní nabídky rozšíření můžete otevřít nastavení rozšíření nebo pozastavit ochranu. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 4133016f76b..05fb82981a5 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Kromě velkých klíčových modulů rozšíření prohlížeče AdGuard existuj ## Obecné {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +Na kartě Obecné můžete povolit reklamy ve vyhledávání a [vlastní propagaci webových stránek](/general/ad-filtering/search-ads), povolit automatickou aktivaci filtrů pro jednotlivé jazyky, určit interval aktualizace filtrů atd. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Kromě toho zde můžete povolit [_Ochranu proti phishingu a malwaru_](/general/browsing-security). -Konfiguraci nastavení můžete uložit kliknutím na tlačítko _Exportovat nastavení_. Nastavení se uloží jako soubor .json. To import the previously saved settings configuration, use the _Import settings_ function. Můžete to použít i k rychlému přepínání mezi různými profily nastavení nebo dokonce k přenosu konfigurací nastavení mezi různými prohlížeči. +Konfiguraci nastavení můžete uložit kliknutím na tlačítko _Exportovat nastavení_. Nastavení se uloží jako soubor .json. Chcete-li nahrát dříve uloženou konfiguraci nastavení, použijte funkci _Importovat nastavení_. Můžete to použít i k rychlému přepínání mezi různými profily nastavení nebo dokonce k přenosu konfigurací nastavení mezi různými prohlížeči. ## Další nastavení {#misc} @@ -33,6 +33,6 @@ Kromě toho nám můžete pomoci s vývojem filtrů zasíláním statistik o pou ## Informace {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +V sekci _Informace_ najdete informace o aktuální verzi, odkazy na smlouvu EULA a zásady ochrany osobních údajů a na úložiště rozšíření prohlížeče na GitHubu. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index b6db8b29cc1..00000000000 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Omezení - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index 834d22c59d6..30047d8ceda 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Stránky chráněné prohlížečem -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index 814444ac342..00000000000 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -To je vše! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index f7d8136e9c9..542c3b37cb3 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ Z kontextového menu můžete také přistupovat ke statistikám aplikace. ### “Kompatibilní” a ”nekompatibilní” aplikace -Most apps work correctly when filtered. U takových aplikací je jejich provoz směrován skrze AdGuard a ve výchozím nastavení filtrován. +Většina aplikací funguje správně, když je filtrování povoleno. U takových aplikací je jejich provoz směrován skrze AdGuard a ve výchozím nastavení filtrován. Některé aplikace, například Správce stahování, rádio, systémové aplikace s UID 1000 a 1001 (např. služby Google Play), jsou “nekompatibilní“ a mohou při přesměrování skrze AdGuard fungovat nesprávně. Proto se při pokusu o směrování nebo filtrování všech aplikací může zobrazit následující upozornění: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 6d82f7d8efd..bc124a5d642 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ K modulu DNS ochrana se dostanete klepnutím na kartu _Ochrana_ (druhá ikona vl :::tip -DNS ochrana funguje jinak než běžné blokování reklam a slídičů. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS ochrana funguje jinak než běžné blokování reklam a slídičů. [Více informací o tom, jak to funguje, najdete ve vyhrazeném článku](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index fe82e0e5d03..d7c0dc389ca 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ Chcete-li odstranit pravidlo nebo aplikaci v části _Vlastní pravidla_, přeje ### Upozornění -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. Upozornění můžete zapnout a vypnout pro všechny aplikace nebo pro každou aplikaci zvlášť. +Pokud je tato funkce povolena, upozorní vás, když se aplikace pokusí porušit některé z pravidel brány firewall nastavených pro danou aplikaci (například získat přístup k mobilním datům, i když by neměla). Upozornění můžete zapnout a vypnout pro všechny aplikace nebo pro každou aplikaci zvlášť. Klepnutím na upozornění získáte přístup k nastavení brány firewall aplikace nebo můžete dočasně zakázat všechna pravidla brány firewall pro danou aplikaci klepnutím na příslušné tlačítko v upozornění. Můžete také ztlumit všechna upozornění brány firewall pro aplikaci klepnutím na tlačítko _Ztlumit_ v upozornění pro danou aplikaci. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index 2f3581896ec..46ff9f8ef74 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Zde jsou uvedeny aktivní funkce předkonfigurovaných úrovní: k. _Odstranit X-Client-Data hlavičku_. Tato funkce zabraňuje tomu, aby prohlížeč Google Chrome odesílal informace o své verzi a úpravách do domén společnosti Google (včetně služeb DoubleClick a Google Analytics) -Jednotlivá nastavení můžete upravit v části _Ochrana před sledováním_ a vytvořit si vlastní konfiguraci. Každé nastavení má popis, který vám pomůže pochopit jeho roli. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +Jednotlivá nastavení můžete upravit v části _Ochrana před sledováním_ a vytvořit si vlastní konfiguraci. Každé nastavení má popis, který vám pomůže pochopit jeho roli. [Další informace o tom, co dělají různá nastavení _Ochrany před sledováním_](/general/stealth-mode). Přistupujte k nim opatrně, protože některá mohou narušovat funkčnost webových stránek a rozšíření prohlížeče. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 1fe589a1c9f..f52c9526971 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt Vzhledem k bezpečnostním opatřením OS Android jsou některé funkce AdGuardu dostupné pouze na zařízeních s přístupem root. Zde je jejich seznam: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **Filtrování HTTPS filtrování ve většině aplikací** vyžaduje [instalaci certifikátu CA do systémového úložiště](/adguard-for-android/features/settings#security-certificates), protože většina aplikací nedůvěřuje certifikátům v uživatelském úložišti. Instalace certifikátu do systémového úložiště je možná pouze na zařízeních s přístupem root - [Režim směrování **Automatický proxy**](/adguard-for-android/features/settings#routing-mode) vyžaduje přístup root kvůli omezením systému Android na filtrování provozu v celém systému - [Režim směrování **Ruční proxy**](/adguard-for-android/features/settings#routing-mode) vyžaduje v systému Android 10 a novějším přístup root, protože již není možné určit název aplikace přidružené ke spojení filtrovanému AdGuardem diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 39210156e93..1aa9e864064 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -27,7 +27,7 @@ _Automatizace_ vám umožňuje spravovat AdGuard prostřednictvím aplikací Tas _Hlídací pes_ pomáhá chránit AdGuard před vypnutím systémem ([přečtěte si více o úsporném režimu baterie systému Android](/adguard-for-android/solving-problems/background-work/)). Zadaná hodnota bude interval v sekundách mezi kontrolami watchdog. -_Úroveň záznamu_ definuje, jaká data o provozu aplikace by měla být zaznamenána. Ve výchozím nastavení aplikace shromažďuje údaje o vlastních událostech. _Úroveň ladění_ zaznamenává více událostí – povolte ji, pokud o to tým AdGuardu požádá, abyste mu pomohli lépe porozumět problému. [Read more about collecting and sending logs](/adguard-for-android/solving-problems/log/) +_Úroveň záznamu_ definuje, jaká data o provozu aplikace by měla být zaznamenána. Ve výchozím nastavení aplikace shromažďuje údaje o vlastních událostech. _Úroveň ladění_ zaznamenává více událostí – povolte ji, pokud o to tým AdGuardu požádá, abyste mu pomohli lépe porozumět problému. [Přečtěte si více o shromažďování a odesílání záznamů](/adguard-for-android/solving-problems/log/) ![Advanced \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) @@ -59,7 +59,7 @@ Pokud aktivujete příliš mnoho filtrů, mohou některé webové stránky fungo ### Uživatelské skripty -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. K instalaci uživatelských skriptů potřebujete speciální správce uživatelských skriptů. AdGuard takovou funkci má a umožňuje přidávat uživatelské skripty pomocí URL nebo ze souboru. +Uživatelské skripty jsou miniprogramy napsané v jazyce JavaScript, které rozšiřují funkčnost jedné nebo více webových stránek. K instalaci uživatelských skriptů potřebujete speciální správce uživatelských skriptů. AdGuard takovou funkci má a umožňuje přidávat uživatelské skripty pomocí URL nebo ze souboru. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ V této sekci najdete informace o své licenci a můžete provádět následují - Zakoupit licenci AdGuardu pro aktivaci [funkcí plné verze](/adguard-for-android/features/free-vs-full) - Přihlásit se ke svému AdGuard účtu nebo zadat licenční klíč pro aktivaci licence - Zaregistrovat se a aktivovat si 7denní zkušební dobu, pokud jste ji ještě nevyužili -- Refresh the license status from the three-dots menu (⋮) +- Obnovit stav licence z nabídky se třemi tečkami (:) - Otevřít AdGuard účet a spravovat v něm své licence - Resetovat licenci — například pokud jste dosáhli limitu zařízení pro tuto licenci a chcete použít jinou diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index af4d2124190..e8adce36794 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro Android TV, blokátor reklam, který chrán ::: -Ve většině případů nelze do TV nainstalovat soubor ze standardních prohlížečů, ale můžete si stáhnout prohlížeč z obchodu Google Play, který tuto funkci má. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. Případně můžete použít aplikaci [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader). +Ve většině případů nelze do TV nainstalovat soubor ze standardních prohlížečů, ale můžete si stáhnout prohlížeč z obchodu Google Play, který tuto funkci má. V našem průvodci se budeme zabývat příkladem instalace pomocí prohlížeče TV Bro, ale existují i jiné možnosti a vy si můžete vybrat tu, která lépe vyhovuje vašim potřebám. Případně můžete použít aplikaci [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader). ## Instalace aplikace AdGuard pro Android TV z prohlížeče v TV diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c89764c5d53..bcb79f38993 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Hotovo! You have successfully set up AdGuard to work in the background. Chcete-li aplikaci AdGuard úspěšně spustit na pozadí, proveďte následující kroky: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +V **Nastavení** → **Aplikace** → **Spravovat aplikace** → přejděte dolů k **AdGuard**, nastavte **Automatické spuštění** na “Zapnuto“. ![Nastavení Xiaomi *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ V systému Android 11+ je na stejné obrazovce s režimem STAMINA nastavení s n Je také třeba AdGuard vyjmout z funkce úspory energie: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**Nastavení systému** ​→ **Aplikace a oznámení** ​→ **Pokročilé** ​→ **Speciální přístup aplikací** ​→ **Funkce šetření baterie** → Přepnout AdGuard na **Vyjmuto** ## Wiko diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 44d75e0334d..c8376b252dd 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. Bylo to proto, že AdGuard počítal veškerý provoz, který filtroval z různých aplikací. V důsledku toho byl podíl AdGuardu na celkovém využití dat a baterie nadhodnocen, zatímco podíl ostatních aplikací byl podhodnocen. +Na zařízeních se systémem Android 6 a starším se v integrovaných statistikách často připisovalo vysoké využití dat a/nebo baterie AdGuardu. Bylo to proto, že AdGuard počítal veškerý provoz, který filtroval z různých aplikací. V důsledku toho byl podíl AdGuardu na celkovém využití dat a baterie nadhodnocen, zatímco podíl ostatních aplikací byl podhodnocen. V Androidu 7 se však tento scénář zlepšil. Nyní se údaje uvedené ve vestavěných statistikách využití dat systému Android velmi blíží skutečnosti, i když v údajích o využití baterie jsou drobné nesrovnalosti. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 3ee6552f3ce..e2b34b3189d 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Někteří výrobci zařízení nechávají nastavení Soukromých DNS skryté a ### Prohlížeče UC: UC Browser, UC Browser pro x86, UC Mini, UC Browser HD -Aby mohl AdGuard filtrovat přenosy HTTPS, musí uživatel přidat certifikát do důvěryhodných uživatelských certifikátů zařízení. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +Aby mohl AdGuard filtrovat přenosy HTTPS, musí uživatel přidat certifikát do důvěryhodných uživatelských certifikátů zařízení. Prohlížeče z rodiny UC bohužel nedůvěřují uživatelským certifikátům, takže v nich AdGuard nemůže provádět filtrování HTTPS. - Chcete-li tento problém vyřešit, přesuňte certifikát do [systémového úložiště certifikátů](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index 67910bba588..2922a207af4 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: Jak získat soubory HAR sidebar_position: 5 --- @@ -17,11 +17,11 @@ Soubory HAR jsou zpracovávány v souladu se [Zásadami ochrany osobních údaj ## Co jsou soubory HAR? -Formát HAR (HTTP ARchive) je archivní soubor ve formátu JSON pro zaznamenávání interakce webového prohlížeče s webem. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. Podrobnější popis formátu HAR a jeho specifikace naleznete na webové stránce [ softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/). +Formát HAR (HTTP ARchive) je archivní soubor ve formátu JSON pro zaznamenávání interakce webového prohlížeče s webem. Specifikace formátu HAR definuje archivační data pro transakce HTTP, která prohlížeč používá k exportu podrobných informací o načítaných webových stránkách. Podrobnější popis formátu HAR a jeho specifikace naleznete na webové stránce [ softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/). -## How to generate HAR files +## Jak získat soubory HAR -Někdy musíme analyzovat, abychom zablokovali konkrétní reklamy, které je z nějakého důvodu obtížné reprodukovat. To get HAR files, follow these steps: +Někdy musíme analyzovat, abychom zablokovali konkrétní reklamy, které je z nějakého důvodu obtížné reprodukovat. Chcete-li získat soubory HAR, postupujte takto: 1. Otevřete AdGuard a přejděte do **Nastavení** (ikona ⚙ v pravém dolním rohu). 2. Klepněte na **Obecné** →**Pokročilé** → **Nízkoúrovňová nastavení**. @@ -31,7 +31,7 @@ Někdy musíme analyzovat, abychom zablokovali konkrétní reklamy, které je z 6. Přejděte zpět na **Pokročilé**. 7. Klepněte na **Exportovat protokoly a systémové informace** → **Povolit** (je-li to nutné) → **Uložit**. -**Send the generated file with the logs to the AdGuard support service.** +**Zašlete prosím soubor se záznamy (které jste získali jako výsledek) službě podpory AdGuardu.** :::note diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index 776701270e5..76a0a9cc5ce 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Zde je návod, jak to udělat: 1. Nainstalujte [nejnovější verzi modulu **adguardcert** Magisk](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Otevřete *Magisk → Moduly → Instalovat z úložiště* a vyberte stažený soubor **adguardcert**. The AdGuard Personal CA certificate will be copied to the system store. +1. Otevřete *Magisk → Moduly → Instalovat z úložiště* a vyberte stažený soubor **adguardcert**. Tím se AdGuard Personal CA přesune z uživatelského úložiště systémového. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index 4358a3a37ac..bc8d501d286 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -1,5 +1,5 @@ --- -title: How to collect debug logs +title: Jak shromažďovat záznamy ladění sidebar_position: 2 --- @@ -15,7 +15,7 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Záznamy ladění poskytují podrobný náhled do vnitřního fungování AdGuardu pro Android. Pokud vás tým podpory AdGuardu požádá o poskytnutí záznamů ladění, postupujte podle těchto pokynů. +V tomto článku vás provedeme procesem shromažďování záznamů ladění, což je zásadní krok při řešení složitých problémů, které mohou nastat. Záznamy ladění poskytují podrobný náhled do vnitřního fungování AdGuardu pro Android. Pokud vás tým podpory AdGuardu požádá o poskytnutí záznamů ladění, postupujte podle těchto pokynů. :::note @@ -23,9 +23,9 @@ AdGuard se zavazuje chránit vaše soukromí. Přísně dodržujeme naše [Zása ::: -### Recording debug log +### Shromažďování záznamů ladění -To collect **debug** log and send it to us, you need to perform following steps: +Chcete-li shromáždit záznam **ladění** a odeslat nám jej, musíte provést následující kroky: 1. Jděte do *Nastavení* → *Obecné* → *Pokročilé*. 1. Klepněte na *Úroveň záznamů* a nastavte ji na *Ladění*. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index 0bde452c0e6..262b698488d 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -15,7 +15,7 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -Někdy nemusí běžný záznam stačit k identifikaci původu problému. V takových případech je nutný systémový záznam. Below are instructions on how to collect and get it: via Developer options and Logcat. +Někdy nemusí běžný záznam stačit k identifikaci původu problému. V takových případech je nutný systémový záznam. Níže jsou uvedeny pokyny, jak je shromáždit a získat: prostřednictvím možností pro vývojáře a Logcat. :::note diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 5b4598da0fc..c8fcd9a6328 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Používejte to pouze pro účely ladění! #### Encrypted Client Hello -Každé šifrované internetové připojení má i nešifrovanou část. Jedná se o první paket, který obsahuje název serveru, ke kterému se připojujete. Technologie Encrypted Client Hello má tento problém vyřešit a zašifrovat poslední kousek nešifrovaných informací. Chcete-li to využít, povolte možnost *Encrypted ClientHello*. K vyhledání konfigurace ECH pro danou doménu používá místní proxy server DNS. If it is found, Client Hello packet will be encrypted. +Každé šifrované internetové připojení má i nešifrovanou část. Jedná se o první paket, který obsahuje název serveru, ke kterému se připojujete. Technologie Encrypted Client Hello má tento problém vyřešit a zašifrovat poslední kousek nešifrovaných informací. Chcete-li to využít, povolte možnost *Encrypted ClientHello*. K vyhledání konfigurace ECH pro danou doménu používá místní proxy server DNS. Pokud je nalezen, paket ClientHello bude zašifrován. #### Kontrola OCSP @@ -147,7 +147,7 @@ Zde můžete zadat rozsahy portů, které mají být filtrovány. Pokud je toto nastavení povoleno, AdGuard zaznamená blokované prvky HTML v sekci *Nedávná aktivita*. -#### Scriptlet debugging +#### Ladění skripletů Pokud je toto nastavení povoleno, bude aktivováno ladění skriptletů a protokol prohlížeče bude zaznamenávat použití pravidel skriptletů. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index e5bafacab72..14beea9efb9 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. Ve starších verzích operačního systému Android se to provádělo automaticky, ale v Androidu 11 a novějších verzích jej uživatelé musí nainstalovat ručně. +Aby bylo možné [filtrovat provoz HTTPS](/general/https-filtering/what-is-https-filtering.md) (což je velmi důležité, protože většina reklam používá HTTPS), musí AdGuard nainstalovat certifikát do uživatelského úložiště vašeho zařízení. Ve starších verzích operačního systému Android se to provádělo automaticky, ale v Androidu 11 a novějších verzích jej uživatelé musí nainstalovat ručně. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Certifikát AdGuardu nainstalujete podle následujících kroků: 1. Když uvidíte oznámení *HTTPS filtrování je vypnuto*, klepněte na *Zapnout*. 1. Poté se zobrazí tři obrazovky s vysvětlením: - Proč filtrovat HTTPS provoz - Bezpečnost tohoto procesu filtrování - - The necessity of the AdGuard certificate + - Nezbytnost AdGuard certifikátu Postupně klepněte na *Další* → *Další* → *Uložit certifikát*. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index 5b802d3e3f7..868c74f1eb6 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro Android, multifunkční blokátor reklam, kt ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Níže naleznete seznam nejznámějších aplikací, které můžete nakonfigurovat tak, aby v AdGuardu fungovaly jako proxy servery. :::note @@ -41,11 +41,11 @@ V tomto článku uvádíme příklady nastavení některých nejoblíbenějšíc | Hostitel proxy | *127.0.0.1* | | Port proxy | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Nebo můžete klepnout na **Proxy server** → **Přidat proxy server**, zadat tyto hodnoty ručně a nastavit Orbot jako výchozí proxy. 1. Zapněte hlavní přepínač Proxy a AdGuard ochranu, aby byl provoz zařízení směrován přes proxy server. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Nyní bude AdGuard přeposílat veškerý provoz přes Orbot. Pokud zakážete Orbot, připojení k Internetu bude nedostupné, dokud nezakážete nastavení odchozího proxy v AdGuardu. ### Jak používat AdGuard s PIA (Private Internet Access) @@ -157,4 +157,4 @@ Před nastavením procesu byste měli odstranit aplikaci Shadowsocks z filtrová ## Omezení -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. Chcete-li to provést, musíte přejít na **Správa aplikací**, vybrat aplikaci a zapnout **Směrovat provoz skrze AdGuard**. +Existuje faktor, který může zabránit přesměrování určitého provozu přes odchozí proxy server i po konfiguraci nastavení proxy serveru AdGuard. To se může stát, pokud aplikaci nenastavíte tak, aby odesílala provoz skrze AdGuard. Chcete-li to provést, musíte přejít na **Správa aplikací**, vybrat aplikaci a zapnout **Směrovat provoz skrze AdGuard**. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index cf1c14f5104..b50b1531004 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Nebo můžete parametry odebrání nakonfigurovat ručně: ::: -**Don't forget to include the password, package name, and class. Musíte tak učinit pro každý záměr.** +**Nezapomeňte uvést heslo jako dodatek a zmínit název balíčku a třídy. Musíte tak učinit pro každý záměr.** Dodatek: `password:*******` @@ -136,7 +136,7 @@ Třída: `com.adguard.android.receiver.AutomationReceiver` :::note -Před verzí 4.0 se třída jmenovala `com.adguard.android.receivers.AutomationReceiver`, ale pak jsme její název změnili na `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Před verzí 4.0 se třída jmenovala `com.adguard.android.receivers.AutomationReceiver`, ale pak jsme její název změnili na `com.adguard.android.receiver.AutomationReceiver`. Pokud jste tuto funkci používali, věnujte jí pozornost a používejte nový název. ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 76fce39cd39..00000000000 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Bezplatná vs. plná verze -sidebar_position: 9 ---- - -:::info - -Tento článek popisuje AdGuard pro iOS, multifunkční blokátor reklam, který chrání vaše zařízení na úrovni systému. Chcete-li se podívat, jak to funguje, [stáhněte si AdGuard pro Android](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 45f392f8ceb..a3991fdc469 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard pro iOS je aplikace uvedená v App Store. Chcete-li AdGuard nainstalovat ![Na hlavní obrazovce App Store klepněte na možnost Hledat *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Do vyhledávacího pole zadejte *adguard* a klepněte na řetězec *adguard*, který bude mezi výsledky vyhledávání. ![Do vyhledávacího pole zadejte "AdGuard" *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro je placená verze AdGuardu pro iOS, která nabízí rozšířenou sa ![Na hlavní obrazovce App Store klepněte na možnost Hledat *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Do vyhledávacího pole zadejte *adguard* a klepněte na řetězec *adGuard*, který bude mezi výsledky vyhledávání. ![Do vyhledávacího pole zadejte "AdGuard" *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. Můžete být požádáni o zadání přihlašovacího jména a hesla k Apple ID. Zadejte ho a počkejte na dokončení instalace. +Na otevřené stránce App Store klepněte na tlačítko s cenou licence pod řetězcem *AdGuard Pro-adblock*a poté klepněte na *ZAKOUPIT*. Můžete být požádáni o zadání přihlašovacího jména a hesla k Apple ID. Zadejte ho a počkejte na dokončení instalace. ![Klepněte na ZÍSKAT pod AdGuardem *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index 118c85bf79a..563da7280ca 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ Tento článek popisuje AdGuard pro iOS, multifunkční blokátor reklam, který 1. Vyberte video a klepněte na *Sdílet*. 1. Klepněte na *Více* a poté vyberte *Blokovat reklamy YouTube (pomocí AdGuardu)*. -The video now opens in AdGuard's ad-free player. +AdGuard otevře svůj přehrávač videa bez reklam. ## Jak blokovat reklamy YouTube v Safari @@ -31,4 +31,4 @@ Ujistěte se, že jste povolili AdGuardu přístup ke všem webovým stránkám. 1. Vyberte video a klepněte na *Sdílet*. 1. Klepněte na *Blokovat reklamy YouTube (pomocí AdGuardu)*. -The video now opens in AdGuard's ad-free player. +AdGuard otevře svůj přehrávač videa bez reklam. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index 91afa8e9edc..5793073b9a6 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: Jak se vyhnout problémům s kompatibilitou s FaceTime sidebar_position: 3 --- diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index d5940bd474c..c78eaeafa77 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ Chcete-li přejít na *Nízkoúrovňová nastavení*, klepněte na ikonu ozuben Existují dva hlavní režimy tunelu: *Dělený* a *Úplný*. Režim *Dělený tunel* poskytuje kompatibilitu aplikací AdGuard a takzvaných "Osobních VPN". V režimu *Úplný tunel* nemůže žádná jiná VPN pracovat současně s AdGuardem. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. V tuto chvíli nejsou blokovány žádné reklamy a provoz DNS není šifrován. +Existuje specifická funkce režimu *Dělený tunel*: pokud proxy server DNS nefunguje dobře, například pokud se odpověď ze serveru AdGuard DNS nevrátila včas, systém iOS jej "zneplatní" a přesměruje provoz přes server DNS zadaný v nastavení systému iOS. V tuto chvíli nejsou blokovány žádné reklamy a provoz DNS není šifrován. -V režimu *Úplný tunel* se používá pouze server DNS zadaný v nastavení AdGuardu. Pokud neodpovídá, internet jednoduše nefunguje. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +V režimu *Úplný tunel* se používá pouze server DNS zadaný v nastavení AdGuardu. Pokud neodpovídá, internet jednoduše nefunguje. Zapnutý režim *Úplný tunel* může způsobit nesprávný výkon některých programů (například FaceTime) a vést k problémům s aktualizacemi aplikací. Ve výchozím nastavení používá AdGuard režim *Dělený tunel* jako nejstabilnější možnost. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index c241882595c..249dd4c3d20 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Doba v sekundách před odesláním další udržovací sondy neodpovídajícím #### `network.https.ech.enabled` -Používá místní DNS proxy k vyhledání konfigurací v seznamech konfigurací ECH. If found, encrypts Client Hellos. +Používá místní DNS proxy k vyhledání konfigurací v seznamech konfigurací ECH. Pokud je nalezeno, zašifruje ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 65f486eb8a0..714ecc4bcf6 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ Používáte-li Flutter spolu s AdGuardem v režimu "Rozšíření sítě" (nebo #### Aplikace VPN se starším rozhraním API -Přestože je AdGuard v nastavení systému zobrazen jako VPN, neměl by při práci s jinými aplikacemi založenými na VPN způsobovat žádné konflikty. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Přestože je AdGuard v nastavení systému zobrazen jako VPN, neměl by při práci s jinými aplikacemi založenými na VPN způsobovat žádné konflikty. Pokud však používáte aplikaci založenou na VPN, která byla stažena mimo App Store, je možné, že používá staré rozhraní API VPN a je nutné ji z filtrování vyloučit: 1. Otevřete menu AdGuardu. 1. Vyberte *Předvolby...*. @@ -79,9 +79,9 @@ Tyto problémy již společnost Apple odstranila, ale ve starších verzích sys ### Kompatibilita s Little Snitch 5 -V tuto chvíli není režim Rozšíření sítě v AdGuardu kompatibilní s [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. Tento problém je přímo způsoben chybou v Big Sur a společnost Apple jsme o něm již informovali. To nás vede k domněnce, že tento problém bude vyřešen v některé z příštích aktualizací. +V tuto chvíli není režim Rozšíření sítě v AdGuardu kompatibilní s [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). Pokud jsou spuštěny obě aplikace, můžete se setkat s problémy s chováním různých aplikací, i když nejsou AdGuardem filtrovány. Tento problém je přímo způsoben chybou v Big Sur a společnost Apple jsme o něm již informovali. To nás vede k domněnce, že tento problém bude vyřešen v některé z příštích aktualizací. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. Doporučujeme přepnout na režim filtrování [**Automatický proxy**](#automatic-proxy) při spuštění AdGuardu spolu s Little Snitch na Big Sur, alespoň dokud Apple chybu neopraví. +Je třeba říci, že tento problém nelze vyřešit vypnutím monitorování připojení v aplikaci Little Snitch, protože tato akce neodstraní rozšíření aplikace Little Snitch ze systému. Doporučujeme přepnout na režim filtrování [**Automatický proxy**](#automatic-proxy) při spuštění AdGuardu spolu s Little Snitch na Big Sur, alespoň dokud Apple chybu neopraví. ### Kompatibilita s lokálními proxy @@ -121,7 +121,7 @@ Především potřebujete funkční server na straně proxy. S největší pravd :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +Více informací o tom, jak začít, najdete na webu [Shadowsocks](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index 5c1b8bfcf02..4f05160ca48 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ Tento článek popisuje AdGuard pro macOS, multifunkční blokátor reklam, kter ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". Jedná se o nový bezpečnostní mechanismus, který se objevil v softwaru High Sierra a vyžaduje výslovné povolení instalace systémového rozšíření třetí strany. Chcete-li dokončit instalaci AdGuardu, musíte ručně povolit načtení rozšíření v *Předvolbách systému* → *Soukromí a zabezpečení* → *Obecné*. +Během instalace AdGuardu v systému macOS High Sierra (nebo novějších verzích) se může zobrazit zpráva: "Systémové rozšíření zablokováno". Jedná se o nový bezpečnostní mechanismus, který se objevil v softwaru High Sierra a vyžaduje výslovné povolení instalace systémového rozšíření třetí strany. Chcete-li dokončit instalaci AdGuardu, musíte ručně povolit načtení rozšíření v *Předvolbách systému* → *Soukromí a zabezpečení* → *Obecné*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index d7e202fad36..fca8796d4c1 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ V důsledku toho, nemůže AdGuard spolupracovat s funkcemi soukromí iCloud Pri 1. iCloud Private Relay se použije pro připojení na úrovni knihovny — předtím, než se dostanou na úroveň, kde funguje AdGuard. 2. iCloud Private Relay používá QUIC, který AdGuard nemůže filtrovat, protože filtrování HTTP/3 ještě není k dispozici. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. V důsledku toho, AdGuard blokuje QUIC, včetně provozu iCloud Private Relay — jinak je blokování reklam nemožné. 4. Když používáte iCloud Private Relay a přepnete AdGuard do režimu "dělený tunel", nemůžete v Safari otevírat webové stránky. 5. Abychom tento problém pro Monterey obešli, použijeme pravidlo "výchozí směrování". Když iCloud Private Relay uvidí toto pravidlo, automaticky se deaktivuje. AdGuard tedy v Monterey funguje bez problémů, ale iCloud Private Relay je vypnuto. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 7ec25432d25..4c2ae99115b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ Na kartě O produktu se zobrazují informace o aktuální verzi produktu a odkaz :::note Připomínka -AdGuard pro Safari si můžete stáhnout zdarma [z App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard pro Safari si můžete stáhnout zdarma [z App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). Podrobný návod k nastavení je k dispozici v [databázi znalostí](/adguard-for-safari/installation/). ::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index dbf99590d53..94a29ec602b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: Uživatelská pravidla sidebar_position: 4 --- -K přizpůsobení blokování reklam lze použít uživatelská pravidla. Lze je přidat ručně, importovat nebo vytvořit automaticky při zablokování prvku na stránce. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +K přizpůsobení blokování reklam lze použít uživatelská pravidla. Lze je přidat ručně, importovat nebo vytvořit automaticky při zablokování prvku na stránce. Chcete-li přidávat vlastní pravidla filtrování, použijte [speciální syntaxi](/general/ad-filtering/create-own-filters). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index c8f409e3d1d..af12b825504 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -1,5 +1,5 @@ --- -title: How to collect logs in AdGuard for Safari +title: Jak shromažďovat protokoly v AdGuardu pro Safari sidebar_position: 4 --- @@ -9,9 +9,9 @@ Tento článek je o AdGuardu pro Safari, který chrání pouze váš prohlíže ::: -K analýze a diagnostice různých problémů, které mohou nastat s AdGuardem pro Safari, může služba podpory AdGuardu potřebovat soubory záznamu. Tyto soubory obsahují záznamy o chybách a dalších softwarových událostech. Below are brief instructions on how to collect logs and send them to support if necessary. +K analýze a diagnostice různých problémů, které mohou nastat s AdGuardem pro Safari, může služba podpory AdGuardu potřebovat soubory záznamu. Tyto soubory obsahují záznamy o chybách a dalších softwarových událostech. Níže jsou uvedeny stručné pokyny, jak shromažďovat protokoly a v případě potřeby je odesílat na podporu. -### How to collect logs +### Jak shromažďovat a záznamy 1. Otevřete aplikaci AdGuard pro Safari. 2. Přejděte dolů a klikněte na _Exportovat protokoly_. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 30601a9752c..0aa54e2cd86 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Upozorňujeme, že taková instalace aplikace a ruční aktualizace se nedoporu ## 5. Test instalace {#installation-test} -V cílovém počítači spusťte AdGuard. Open the license screen to check that it is using the specified license. Možná budete muset kliknout na tlačítko "Obnovit stav", aby AdGuard ověřil licenční klíč. +V cílovém počítači spusťte AdGuard. Otevřete obrazovku licence a zkontrolujte, zda používá nastavenou licenci. Možná budete muset kliknout na tlačítko "Obnovit stav", aby AdGuard ověřil licenční klíč. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index d307a998758..a2a34a2ce8d 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Základní informace: V předchozích verzích Rozšíření prohlížeče AdGuard (před verzí 3.5), pokud jste je měli nainstalované spolu s aplikací AdGuard pro Windows, převzalo rozšíření funkce Asistenta, přestalo filtrovat samo a spoléhalo se na aplikaci. -Rozšíření a aplikace fungovaly společně, ale někdy integrace selhala. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +Rozšíření a aplikace fungovaly společně, ale někdy integrace selhala. Některé webové stránky by přestaly být chráněny programem pro stolní počítače a byly by zálohovány pouze méně výkonným rozšířením. Při použití Asistenta prohlížeče všechny tyto problémy nevadí, protože v podstatě nemůže dojít k žádným konfliktům. Úloha Asistenta prohlížeče je dobře definovaná a nemůže bránit fungování hlavní aplikace, takže se nemusíte obávat. @@ -42,4 +42,4 @@ Starý Asistent je předchozí verze Asistenta, která je pouhým uživatelským Chcete-li nainstalovat Asistenta prohlížeče pro svůj výchozí prohlížeč, můžete to provést přímo v nastavení aplikace, ale máte také možnost nainstalovat jej pro jiné prohlížeče. -Asistent prohlížeče AdGuard je k dispozici pro všechny oblíbené prohlížeče: Chrome, Firefox Edge, Opera a Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. To je vše! +Asistent prohlížeče AdGuard je k dispozici pro všechny oblíbené prohlížeče: Chrome, Firefox Edge, Opera a Yandex. Chcete-li si nainstalovat ten, který potřebujete (nebo více, není to zakázáno, ale ani doporučeno), přejděte na [naše webové stránky](https://adguard.com/adguard-assistant/overview.html), klikněte na ikonu prohlížeče a poté na tlačítko *Nainstalovat*. To je vše! diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 4ddb33f3ef1..90b479859f1 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant je starší asistent, kterého můžete použít, pokud pro v Jedná se o vlastní rozšíření určené k boji proti technice opětovného vkládání blokovaných reklam — tzv. obcházení blokátorů reklam/opětovnému vkládání reklam. V obou případech se jedná o pokročilé metody proti blokování reklam, jejichž obliba mezi inzerenty stále roste. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra je v podstatě miniprogram, který změní fungování stránek tak, aby bylo pro weby mnohem obtížnější používat výše uvedené metody k obcházení blokátorů. **AdGuard blokátor vyskakovacích oken** -Toto rozšíření zabraňuje otevírání vyskakovacích oken při prohlížení webových stránek. Některá vyskakovací okna jsou považována za užitečná — mohou obsahovat nastavení pro správu webu nebo další referenční informace zobrazené po kliknutí na odkaz. Proto můžete blokátor v případě potřeby vypnout. Toto rozšíření nefunguje ani na webových stránkách přidaných do seznamu výjimek AdGuardu. Ve výchozím nastavení je vypnuto, ale můžete jej zapnout v nastavení aplikace. You will find more detailed information about this extension in our Knowledge Base. +Toto rozšíření zabraňuje otevírání vyskakovacích oken při prohlížení webových stránek. Některá vyskakovací okna jsou považována za užitečná — mohou obsahovat nastavení pro správu webu nebo další referenční informace zobrazené po kliknutí na odkaz. Proto můžete blokátor v případě potřeby vypnout. Toto rozšíření nefunguje ani na webových stránkách přidaných do seznamu výjimek AdGuardu. Ve výchozím nastavení je vypnuto, ale můžete jej zapnout v nastavení aplikace. Podrobnější informace o tomto rozšíření najdete v naší databázi znalostí. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust vám umožňuje zjistit pověst každého webu na základě názor ### Síť -Předposlední modul je věnován filtrování sítě a najdete v něm další možnosti související se sítí. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Jedná se o důležitá dodatečná opatření pro lepší filtrování webového prostoru. Většina webů nyní používá protokol HTTPS a totéž platí i pro reklamu. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +Předposlední modul je věnován filtrování sítě a najdete v něm další možnosti související se sítí. Dvě z nich jsou standardně povoleny: _Povolit filtrování provozu_ a _Filtrovat HTTPS protokol_. Jedná se o důležitá dodatečná opatření pro lepší filtrování webového prostoru. Většina webů nyní používá protokol HTTPS a totéž platí i pro reklamu. Z mnoha webů, jako je youtube.com, facebook.com a twitter.com, není možné odstranit reklamy bez HTTPS filtrování. Pokud tedy nemáte pádný důvod, ponechte funkci _Filtrovat HTTPS protokol_ povolenou. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index c03a212a61d..c97021070aa 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ _Nastavení_ je část, která vyžaduje největší pozornost. Zde můžete pro ### Obecná nastavení -Zde můžete nastavit jazyk a motiv (tmavý nebo světlý), povolit spouštění AdGuardu při startu systému a tiché automatické aktualizace, vybrat aktualizační kanál a interval kontroly aktualizací filtrů. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +Zde můžete nastavit jazyk a motiv (tmavý nebo světlý), povolit spouštění AdGuardu při startu systému a tiché automatické aktualizace, vybrat aktualizační kanál a interval kontroly aktualizací filtrů. Pokud AdGuard pro Windows nefunguje správně a tým podpory vás požádal, abyste [shromáždili _Protokoly ladění_](/adguard-for-windows/solving-problems/adguard-logs.md), přejděte do Nastavení. ![Advanced Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ Existuje několik webových stránek, ke kterým by měl být omezen přístup z Modul kontroluje obsah webových stránek otevřených v prohlížeči a filtruje ty, jejichž obsah je pro děti nežádoucí: obrázky a texty pro dospělé, hrubý jazyk, násilí, propagace drog atd. Nastavení Rodičovské ochrany jsou zabezpečena heslem, takže dítě nemůže obejít omezení. Tento modul nejenže blokuje vstup na nežádoucí stránky, ale také dokáže z výsledků vyhledávání odstranit odkazy, které jsou nevhodné pro děti. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Můžete také zaškrtnout políčko _Blokovat stahování spustitelných souborů_ a zabránit tak vašemu dítěti ve stahování a instalaci softwaru do PC. V modulu _Rodičovská ochrana_ jsou další dvě možnosti: můžete vybrat konkrétního uživatele Windows, který má být chráněn _Rodičovskou ochranou_ a nastavit heslo pro zabezpečení nastavení AdGuardu před změnami. +V modulu Rodičovská ochrana můžete povolit _Bezpečné vyhledávání_, spravovat _seznam zakázaných_, _seznam povolených_ a přizpůsobit si funkce těchto možností. Můžete také zaškrtnout políčko _Blokovat stahování spustitelných souborů_ a zabránit tak vašemu dítěti ve stahování a instalaci softwaru do PC. V modulu _Rodičovská ochrana_ jsou další dvě možnosti: můžete vybrat konkrétního uživatele Windows, který má být chráněn _Rodičovskou ochranou_ a nastavit heslo pro zabezpečení nastavení AdGuardu před změnami. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index c14950e59e5..66243433279 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ Tento článek popisuje AdGuard pro Windows, multifunkční blokátor reklam, kt Chcete-li AdGuard používat v počítači nebo tabletu se systémem Microsoft Windows, stáhněte si instalační balíček a spusťte instalační program. Proveďte následující akce: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Přejděte na web [AdGuardu](http://adguard.com) v adresním řádku a klikněte na *Stáhnout* [na otevřené stránce](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Další kroky proveďte pouze v případě, že provedení prvních dvou kroků ::: -- Vyberte *Blokátor reklam AdGuard* a *Rozšířený* typ odinstalace a poté klikněte na *Odinstalovat*. Click *Yes, continue* in the window prompt. +- Vyberte *Blokátor reklam AdGuard* a *Rozšířený* typ odinstalace a poté klikněte na *Odinstalovat*. Ve okně výzvy klikněte na *Ano, pokračovat*. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 59826c0f4cb..3bce861d630 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard logs +title: Jak shromažďovat záznamy AdGuardu sidebar_position: 3 --- @@ -15,7 +15,7 @@ Tento článek popisuje AdGuard pro Windows, multifunkční blokátor reklam, kt ::: -K analýze a diagnostice různých problémů, které mohou potenciálně nastat, může služba podpory AdGuard potřebovat soubory záznamů AdGuardu. These files contain records about errors and other events that occur with the software. Níže je uveden stručný návod popisující způsoby, jak získat soubory záznamů a v případě potřeby je odeslat službě podpory. +K analýze a diagnostice různých problémů, které mohou potenciálně nastat, může služba podpory AdGuard potřebovat soubory záznamů AdGuardu. Tyto soubory obsahují záznamy o chybách a dalších událostech, ke kterým došlo v softwaru. Níže je uveden stručný návod popisující způsoby, jak získat soubory záznamů a v případě potřeby je odeslat službě podpory. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Otevřete nastavení AdGuardu. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Otevřete nastavení AdGuardu. Přejděte do části *Obecná nastavení*, přejděte dolů na konec obrazovky a přepněte *Úroveň záznamu* na *Ladění*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Důrazně doporučujeme zaznamenat přesný čas, kdy jste problém reprodukovali: pomůže to našemu týmu podpory najít příslušné záznamy v záznamu a rychleji vyřešit problém. -1. Export the collected logs using the *Export Logs* button. +1. Exportujte záznamy pomocí tlačítka *Exportovat protokoly*. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Archiv uložte do libovolné složky. -1. **Important**: after exporting the logs, set the logging level back to *Default*. Úroveň *Ladění* zpomalí aplikaci. +1. **Důležité**: po exportu záznamů nastavte úroveň záznamu zpět na *Výchozí*. Úroveň *Ladění* zpomalí aplikaci. 1. Archiv odešlete službě podpory AdGuardu na adresu **support@adguard.com**, popište problém a nezapomeňte uvést čas, kdy jste problém reprodukovali. @@ -65,7 +65,7 @@ Pokud máte starší verzi AdGuard pro Windows, spusťte aplikaci příkazem C:\ Důrazně doporučujeme zaznamenat přesný čas, kdy jste problém reprodukovali: pomůže to našemu týmu podpory najít příslušné záznamy v záznamu a rychleji vyřešit problém. -1. Export the collected logs using the *Export Logs* button. +1. Exportujte záznamy pomocí tlačítka *Exportovat protokoly*. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index b65d16a019b..38c452c8567 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ Tento článek obsahuje některé z nejčastějších chyb, se kterými se můž ### Chyba 5: Přístup odepřen {#error-5} -This error message appears when required permissions haven't been granted. Může existovat několik různých důvodů, proč instalační program AdGuardu nemá oprávnění potřebná k řádnému dokončení procesu instalace. Můžete vyzkoušet následující kroky: +K této chybě dochází, pokud je něco v nepořádku s oprávněními. Může existovat několik různých důvodů, proč instalační program AdGuardu nemá oprávnění potřebná k řádnému dokončení procesu instalace. Můžete vyzkoušet následující kroky: -- Temporarily disable your antivirus. Některé z nich mohou v závislosti na závažnosti svého nastavení instalaci narušovat. +- Dočasně vypněte antivirové programy. Některé z nich mohou v závislosti na závažnosti svého nastavení instalaci narušovat. - Zvolte jinou složku pro instalaci. Je možné, že aktuální složka pro instalaci má nějaká omezení přístupu. Také se ujistěte, že jste nevybrali externí jednotku, virtuální jednotku atd. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. Můž ### Chyba 112: Disk je plný, Chyba 1632: Dočasná složka je plná nebo nedostupná {#error-112} -Jedná se o dvě různé chyby s velmi podobným řešením. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. Problém můžete vyřešit několika způsoby: +Jedná se o dvě různé chyby s velmi podobným řešením. Jak napovídá jejich název, instalační program AdGuardu nenašel dostatek místa na disku pro dokončení instalace. Problém můžete vyřešit několika způsoby: - Odinstalujte některé programy nebo odstraňte nepotřebné soubory z jednotky, na kterou jste chtěli nainstalovat AdGuard. -- Stáhněte, nainstalujte a spusťte [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), bezplatný software od společnosti Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. Pomůže vyčistit místo na disku. +- Stáhněte, nainstalujte a spusťte [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), bezplatný software od společnosti Malwarebytes. Mimo jiné vyčistí váš systém od nejrůznějších pozůstatků souborů, které zůstaly po nesprávně odinstalovaných programech a podobně. Pomůže vyčistit místo na disku. - Restartujte počítač. Dočasné soubory mohou někdy zabírat značné množství místa na disku a nejspolehlivějším způsobem, jak se jich zbavit, je restartování počítače. ### Chyba 1601: Instalační program pro Windows není přístupný {#error-1601} -You could say this is a particular subcategory of Error 1603. Možná řešení jsou podobná: +Dalo by se říci, že se jedná o zvláštní podtyp chyby 1603. Možná řešení jsou podobná: - Spusťte a znovu zaregistrujte službu Microsoft Installer. Vyžaduje to určitou práci. @@ -75,7 +75,7 @@ K této chybě dochází při současném spuštění několika instancí instal - Restartujte počítač a spusťte instalaci znovu. Po restartování počítače se zastaví všechny probíhající procesy, včetně všech kopií instalačního programu. -- Don't make multiple clicks on the installer even if it doesn't start right away. Zobrazení uživatelského rozhraní instalátoru může někdy trvat několik sekund. +- Na instalační program neklikejte vícekrát, i když se nespustí hned. Zobrazení uživatelského rozhraní instalátoru může někdy trvat několik sekund. ### Chyba 1638: Další verze tohoto produktu je již nainstalována {#error-1638} @@ -83,14 +83,14 @@ Je velmi pravděpodobné, že jste si AdGuard již dříve nainstalovali. - Zkontrolujte, zda je v počítači již nainstalován AdGuard. Můžete to udělat stisknutím klávesy *Win* a zadáním názvu ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Odinstalujte AdGuard pomocí našeho speciálního [nástroje pro odinstalaci](../../installation#advanced) a poté instalaci zopakujte. +- Možná tam jsou nějaké zbytky souborů z předchozí instalace AdGuardu. Odinstalujte AdGuard pomocí našeho speciálního [nástroje pro odinstalaci](../../installation#advanced) a poté instalaci zopakujte. ### Další chyby {#other} Pokud jste narazili na chybu, která není uvedena výše, je možné, že ji dokážeme vyřešit sami. K tomu však od vás potřebujeme soubory záznamů. Proveďte následující kroky: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Vyhledejte a archivujte **instalační protokoly AdGuardu** jak je popsáno v [tomto článku](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [Tento článek](../system-logs) vysvětluje, jak to udělat. +- Vyhledejte a uložte na disk **záznamy prohlížeče událostí**. [Tento článek](../system-logs) vysvětluje, jak to udělat. - Všechny tyto soubory z předchozích dvou kroků zašlete e-mailem na adresu **support@adguard.com** a v těle zprávy popište problém. Naši agenti technické podpory vám odpoví co nejdříve. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index 55008a29c2d..82740cd75e8 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ Tento článek popisuje AdGuard pro Windows, multifunkční blokátor reklam, kt AdGuard pro Windows umožňuje uživatelům zadat adresu DNS serveru pro řešení dotazů namísto systémového DNS serveru, který je poskytován ISP, pokud není v nastavení systému potlačen. Použití jiného než výchozího DNS serveru může ochránit vaše přenosy DNS před zachycením ISP. Výběrem šifrovaného a/nebo filtrujícího DNS serveru navíc získáte další vrstvu ochrany před záškodníky a obtěžujícími reklamami. -Mnoho uživatelů AdGuardu pro Windows oceňuje funkci DNS ochrany. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. V tomto článku se dozvíte, proč k tomu dochází a jak se tomu vyhnout. +Mnoho uživatelů AdGuardu pro Windows oceňuje funkci DNS ochrany. Někteří z nich se však setkávají s následujícím problémem: kontrola na webových stránkách, jako je https://ipleak.net/ ukazuje, že požadavky jsou zpracovávány výchozím DNS serverem namísto vybraným. V tomto článku se dozvíte, proč k tomu dochází a jak se tomu vyhnout. ## Bootstrap DNS adresa @@ -21,7 +21,7 @@ Adresy DNS serverů lze zapsat jako IP adresy nebo jako názvy domén. V přípa - přejděte do *Pokročilých nastavení* - přejděte dolů do sekce *Seznam vlastních bootstrap adres* -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- zadejte vlastní bootstrap adresu ve formátu IP adresy (můžete použít [seznam známých poskytovatelů DNS](https://adguard-dns.io/kb/general/dns-providers/)) - klikněte na *Uložit* ## Záložní DNS server @@ -33,7 +33,7 @@ Může se stát, že AdGuard nemůže dosáhnout zadaného serveru z důvodu sla - přejděte do *Pokročilých nastavení* - přejděte dolů do sekce *Záložní servery* - zaškrtněte možnost *Použít vlastní servery* -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- pak vyhledejte sekci *Seznam vlastních záložních serverů* a zadejte vlastní záložní servery po jednom na řádek nebo diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 29f15d70956..92294ac4511 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ Po vytvoření souboru výpisu přejděte do umístění souboru. Ihned po vytvo :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard pro Windows má dva spuštěné procesy (`Adguard.exe` a `AdguardSvc.exe`). Proto je třeba vytvořit soubor výpisu pro každý proces zvlášť. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -Při odesílání výpisu souborů týmu podpory přiložte také záznamy aplikace AdGuard, abychom měli větší šanci problém vyřešit. [Here](../adguard-logs) you can check the instructions on how to get the log file. +Při odesílání výpisu souborů týmu podpory přiložte také záznamy aplikace AdGuard, abychom měli větší šanci problém vyřešit. [Zde](../adguard-logs) si můžete prohlédnout pokyny ke shromažďování souboru záznamu. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index c471d840f8d..0863212a864 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard installation logs +title: Jak shromažďovat záznamy o instalaci AdGuardu sidebar_position: 4 --- @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the Pokud se během instalace AdGuardu vyskytnou nějaké problémy, tým podpory vás může požádat o shromáždění a zaslání záznamů o instalaci AdGuardu. V tomto případě je třeba: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. V nabídce Start vyberte příkaz *Spustit* nebo na klávesnici stiskněte kombinaci kláves *Win + R*. 1. Napište *%tmp%* a klepněte na *OK*. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 7c18fcf03cf..108f0748627 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Jakmile otevřete Pokročilá nastavení, zobrazí se vám následující možno Pokud je tato funkce povolena, zablokuje AdGuard v prohlížeči Edge funkci TCP Fast Open. Chcete-li použít nastavení, budete muset restartovat prohlížeč. -### Use Encrypted Client Hello +### Použít Encrypted ClientHello -Každé šifrované internetové připojení má i nešifrovanou část. Jedná se o první paket, který obsahuje název serveru, ke kterému se připojujete. Technologie Encrypted Client Hello má tento problém vyřešit a zašifrovat poslední kousek nešifrovaných informací. To benefit from it, enable the *Use Encrypted Client Hello* option. K vyhledání konfigurace ECH pro danou doménu používá místní proxy server DNS. If it is found, Client Hello packet will be encrypted. +Každé šifrované internetové připojení má i nešifrovanou část. Jedná se o první paket, který obsahuje název serveru, ke kterému se připojujete. Technologie Encrypted Client Hello má tento problém vyřešit a zašifrovat poslední kousek nešifrovaných informací. Chcete-li to využít, povolte možnost *Použít Encrypted ClientHello*. K vyhledání konfigurace ECH pro danou doménu používá místní proxy server DNS. Pokud je nalezen, paket ClientHello bude zašifrován. ### Zkontrolovat transparentnost certifikátů webových stránek @@ -73,7 +73,7 @@ V opačném případě bude AdGuard filtrovat veškerý provoz za běhu bez pře ### Otevřít hlavní okno při startu systému -Tuto možnost povolte, aby se po načtení systému otevřelo hlavní okno AdGuardu. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Tuto možnost povolte, aby se po načtení systému otevřelo hlavní okno AdGuardu. Všimněte si, že toto nastavení nemá vliv na to, zda je skutečná služba filtrování spuštěna, nebo ne, toto nastavení se nachází v *Nastavení → Obecná nastavení* ### Zapnout filtrování při spuštění systému @@ -95,7 +95,7 @@ Pokud nechcete, aby AdGuard filtroval určité podsítě, povolte tuto funkci a ### Povolit zápis HAR -Tato možnost by měla být zapnuta **pouze pro účely ladění**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. Tento soubor lze analyzovat pomocí aplikace Fiddler. Upozorňujeme, že to může výrazně zpomalit prohlížení webu. +Tato možnost by měla být zapnuta **pouze pro účely ladění**. Pokud zaškrtnete toto políčko, AdGuard vytvoří soubor obsahující informace o všech filtrovaných požadavcích HTTP ve formátu HAR 1.2. Tento soubor lze analyzovat pomocí aplikace Fiddler. Upozorňujeme, že to může výrazně zpomalit prohlížení webu. ### Přidat do běžného požadavku HTTP dodatečnou mezeru @@ -115,7 +115,7 @@ Tato možnost se použije pouze v případě, že je povolena možnost *Ochrana Určuje velikost fragmentace paketů TCP, čímž se zabrání hloubkové kontrole paketů. Tato možnost má vliv pouze na zabezpečený (HTTPS) provoz. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +Pokud je tato možnost povolena, AdGuard rozdělí počáteční paket TLS (paket ClientHello) na dvě části: první má zadanou délku a druhá obsahuje zbytek až do délky celého počátečního paketu TLS. Platné hodnoty: 1–1500. Pokud je zadána neplatná velikost, použije se hodnota vybraná systémem. Tato možnost se použije pouze v případě, že je povolena možnost *Ochrana před DPI* v Režimu utajení. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index e4fd3d6e4b7..fe071670e30 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect Windows system logs +title: Jak shromažďovat systémové záznamy Windows sidebar_position: 5 --- @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -K analýze a diagnostice různých problémů, které mohou potenciálně nastat, může služba podpory AdGuard potřebovat soubory záznamů Windows. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Níže je uveden stručný návod popisující způsoby, jak získat soubory záznamů a v případě potřeby je odeslat službě podpory. +K analýze a diagnostice různých problémů, které mohou potenciálně nastat, může služba podpory AdGuard potřebovat soubory záznamů Windows. Záznamy událostí systému Windows obsahují záznamy o všech chybách, které se vyskytnou v nainstalovaném softwaru, včetně AdGuardu. Níže je uveden stručný návod popisující způsoby, jak získat soubory záznamů a v případě potřeby je odeslat službě podpory. 1. Stiskněte *Win + R* diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 107eeb7cf4c..b1ecb077881 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ Tento článek popisuje AdGuard pro Windows, multifunkční blokátor reklam, kt ::: -To filter network traffic, AdGuard uses a network driver. Existují dvě možnosti: ovladač TDI a ovladač WFP. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. Tyto problémy a následné chyby mohou být v každém případě velmi odlišné. +To filter network traffic, AdGuard uses a network driver. Existují dvě možnosti: ovladač TDI a ovladač WFP. Ačkoli je ovladač WFP obecně vhodnější a je ve výchozím nastavení povolen pro všechny novější verze operačního systému Windows (Windows 8 a novější), může potenciálně způsobovat problémy s kompatibilitou, zejména s některými antiviry. Tyto problémy a následné chyby mohou být v každém případě velmi odlišné. Pokud narazíte na problém, u kterého máte podezření, že by mohl být způsoben tímto problémem, můžete vždy přejít na starší, ale stabilnější síťový ovladač TDI. K tomu je třeba: 1. Přejděte do *Nastavení → Síť*. -2. Disable the WFP driver as it’s done in this picture: +2. Deaktivujte ovladač WFP, jak je to zobrazeno na tomto obrázku: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/account/features.md index fd6c385ea93..a283ef8b455 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ V části Historie nákupů se zobrazují všechny licence, které jste kdy zako ## Kontaktování podpory -Karta Podpora obsahuje užitečné odkazy, které vám pomohou vyřešit problémy nebo najít odpovědi na vaše otázky týkající se AdGuard produktů. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +Karta Podpora obsahuje užitečné odkazy, které vám pomohou vyřešit problémy nebo najít odpovědi na vaše otázky týkající se AdGuard produktů. Jsou rozděleny do šesti oddílů: FAQ, Odeslat požadavek na chybu/funkci, Nahlásit nesprávné blokování, Kontaktovat podporu, Databáze znalostí a Diskutovat. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 55019488d2c..2e38912bc27 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ Tento článek je o filtrech, které vytváříme pro použití v AdGuardu a jin - **Experimentální filtr** slouží k testování některých nových pravidel filtrování, která mohou potenciálně způsobovat konflikty a narušovat práci webových stránek. Pokud tato pravidla fungují bez problémů, přidají se do hlavních filtrů. [Zobrazit pravidla](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Filtr mobilních reklam** blokuje reklamy v mobilních zařízeních. Obsahuje všechny známé sítě mobilní reklamy. [Zobrazit pravidla](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filtr** — (Základní filtrAdGuard, Filtr sociálních médií, Filtr ochrany sledování, Filtr mobilních reklam, EasyList a EasyPrivacy), který je zjednodušený pro lepší kompatibilitu s blokováním reklamy na úrovni DNS. Tento filtr používá servery [AdGuard DNS](https://adguard-dns.io/kb) k blokování reklam a sledování. [Zobrazit pravidla](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## Zásady AdGuard filtrů -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Pro podrobné informace si přečtěte celý text [Zásad AdGuard filtrů](../filter-policy). +Naše zásady filtrování definují, co mají filtry AdGuard blokovat a co ne a také pravidla pro přidávání a odebírání pravidel z filtrů. Pro podrobné informace si přečtěte celý text [Zásad AdGuard filtrů](../filter-policy). ## Přispět k rozvoji filtrů AdGuardu diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index e941dbd5469..846c4d01a69 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ Následující modifikátory jsou nejjednodušší a nejčastěji používané. -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — plně podporováno - ✅ * — podporováno, ale spolehlivost se může lišit nebo se mohou vyskytnout omezení; více informací naleznete v popisu modifikátoru -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — může být již implementováno ve verzích nightly nebo beta, ale není ještě podporováno ve verzích pro vydání - ❌ — nepodporováno ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — běžný název domény (`domain.com`). Odpovídá zadané doméně a jejím subdoménám. Shoduje se lexikograficky. - **`any_tld_domain`** — název domény zakončený zástupným znakem jako [veřejná přípona](https://publicsuffix.org/learn/), např. pro `example.*` je to `co.uk` v `example.co.uk`. Odpovídá zadané doméně a jejím subdoménám s libovolnou veřejnou příponou. Shoduje se lexikograficky. -- **`regexp`** — regulární výraz, který začíná a končí znakem `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — regulární výraz, který začíná a končí znakem `/`. Vzor funguje stejně jako v základních pravidlech pro URL adresy, ale znaky `/`, `$` a `,` musí být uvozeny pomocí `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Pravidla s modifikátorem `$domain` jako `regular_domain` nebo `any_tld_domain` jsou podporována všemi AdGuard produkty. ::: @@ -444,12 +442,6 @@ V následujících příkladech se předpokládá, že požadavky jsou odesílá ##### omezení modifikátoru `$domain` {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Omezení Safari nepodporuje současné použití povolených a zakázaných domén, takže pravidla jako `||baddomain.com^$domain=example.org|~foo.example.org` nebudou v AdGuardu pro iOS a AdGuardu pro Safari fungovat. @@ -555,13 +547,13 @@ Tento modifikátor omezuje rozsah pravidla na požadavky, které používají za :::caution Omezení -Pravidla se smíšenými negovanými a negovanými hodnotami jsou považována za neplatná. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Pravidla se smíšenými negovanými a negovanými hodnotami jsou považována za neplatná. Takže např. pravidlo `||evil.com^$method=get|~head` bude zamítnuto. ::: :::info Kompatibilita -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard se pokusí zavřít kartu prohlížeče s jakoukoli adresou, která odpo :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Samotná blokovací stránka může provést některé kontroly a zavřít okno, pokud se skutečně jedná o vyskakovací okno. V opačném případě by se stránka měla načíst. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Samotná blokovací stránka může provést některé kontroly a zavřít okno, pokud se skutečně jedná o vyskakovací okno. V opačném případě by se stránka měla načíst. Lze to kombinovat s dalšími modifikátory typu požadavku, jako je `$third-party` a `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Příklady** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Kompatibilita - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Příklady** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Kompatibilita - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. Např. požadavek na `example.org` z `domain.com` je požadavek třetí strany. +Omezení požadavků třetích stran a vlastních požadavků. Požadavek třetí strany je požadavek z jiné domény. Např. požadavek na `example.org` z `domain.com` je požadavek třetí strany. :::note @@ -679,7 +630,7 @@ Místo plného názvu modifikátoru můžete použít kratší název (alias): ` :::info Kompatibilita -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ V tom, jak AdGuard určuje typ obsahu na různých platformách, je velký rozd -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| ------------------------------------------------------------- |:----------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ Pravidlo se vztahuje na požadavky, jejichž typ nebyl určen nebo neodpovídá Pravidlo odpovídá požadavkům vyvolaným buď `navigator.sendBeacon()`, nebo atributem `ping` v odkazech. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Kompatibilita AdGuard pro Windows, Mac a Android často nedokáží přesně detekovat `navigator.sendBeacon()`. V seznamech filtrů, které mají používat AdGuard produkty založené na knihovně CoreLibs, se nedoporučuje používat `$ping`. -::: - -:::info Kompatibilita - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Pravidla s modifikátorem `$ping` nejsou podporována AdGuardem pro iOS a Safari. ::: @@ -817,16 +762,10 @@ Místo plného názvu modifikátoru můžete použít kratší název (alias): ` ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. V opačném případě mohou být některé hlavní stránky považovány za dílčí dokumenty. - -::: - :::info Kompatibilita +V AdGuardu pro Windows, macOS a Android jsou vnořené dokumenty detekovány hlavičkou [Sec-Fetch-Dest][sec-fetch-dest-header] pokud je přítomna. V opačném případě mohou být některé hlavní stránky považovány za dílčí dokumenty. + Pravidla s modifikátorem `$subdocument` nejsou Blokátorem obsahu AdGuard podporována. ::: @@ -835,17 +774,9 @@ Pravidla s modifikátorem `$subdocument` nejsou Blokátorem obsahu AdGuard podpo Pravidlo se vztahuje pouze na připojení WebSocket. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Kompatibilita -Modifikátor `$websocket` je podporován ve všech produktech AdGuardu kromě Blokátoru obsahu AdGuard. +Modifikátor `$websocket` je podporován ve všech produktech AdGuardu kromě Blokátoru obsahu AdGuard. Pokud jde o AdGuard pro Safari a AdGuard pro iOS, je podporován v zařízeních s macOS Monterey (verze 12) a iOS 16 nebo novějším. ::: @@ -900,17 +831,17 @@ Doporučujeme také seznámit se s [přehledem filtrů Adblock Plus](https://adb -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | -| --------------------------------------- |:----------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| --------------------------------------- |:----------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` zakáže uživatelský skript `AdGuard asistent` na `example.com`. - `@@||example.com^$extension=MyUserscript` zakáže uživatelský skript `MyUserscript` na `example.com`. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` zakáže uživatelské skripty `AdGuard asistent` a `Blokátor vyskakovacích oken` na `example.com`. - `@@||example.com^$extension=~"AdGuard Assistant"` zakáže všechny uživatelské skripty na `example.com`, kromě `AdGuard asistenta`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` zakáže všechny uživatelské skripty na `example.com`, kromě `AdGuard asistenta` a `Blokátor vyskakovacích oken`. - `@@||example.com^$extension` žádné uživatelské skripty nebudou fungovat na `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` zakáže uživatelský skript `AdGuard "Asistant"` na `example.com`. :::info Kompatibilita - Pouze AdGuard pro Windows, Mac a Android jsou technicky schopné používat pravidla s modifikátorem `$extension`. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. O pravidlech skripletů a javascriptu si můžete přečíst dále. +Zakazuje přidávání javascriptového kódu na stránku. O pravidlech skripletů a javascriptu si můžete přečíst dále. **Příklady** - `@@||example.com^$jsinject` zakáže javasript na `example.com` a všech subdoménách. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Kompatibilita - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Zakáže modul Režim utajení pro všechny odpovídající stránky a požadavky. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` znamená určité možnosti Režimu utajení deaktivované modifikátorem. The modifier can contain any number of specific options (see below) or none. V druhém případě modifikátor vypne všechny funkce Režimu utajení. Seznam dostupných možností modifikátoru: @@ -1046,13 +963,13 @@ Seznam dostupných možností modifikátoru: **Příklady** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` zakáže Režim utajení pro požadavky `example.com` (a subdomény) s výjimkou blokování cookies a skrytí sledovacích parametrů (viz níže). +- `@@||domain.com^$script,stealth,domain=example.com` zakáže Režim utajení pouze pro požadavky skriptů na `domain.com` (a subdoménách) na `example.com` a subdoménách. - `@@||example.com^$stealth=3p-cookie|dpi` zakáže blokování cookies třetích stran a opatření pro oklamání DPI pro `example.com`. :::note -Blokování cookies a odstranění sledovacích parametrů se provádí pomocí pravidel s modifikátory [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) a [`$removeparam`](#removeparam-modifier). Pravidla výjimek, která obsahují pouze modifikátor `$stealth`, tyto věci neprovedou. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blokování cookies a odstranění sledovacích parametrů se provádí pomocí pravidel s modifikátory [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) a [`$removeparam`](#removeparam-modifier). Pravidla výjimek, která obsahují pouze modifikátor `$stealth`, tyto věci neprovedou. Pokud chcete pro danou doménu zcela zakázat všechny funkce Režimu utajení, musíte uvést všechny tři modifikátory: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blokování cookies a odstranění sledovacích parametrů se provádí pomocí :::info Kompatibilita -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. Všechny ostatní produkty budou ignorovat pravidla s modifikátorem `$stealth`. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. Všechny ostatní produkty budou ignorovat pravidla s modifikátorem `$stealth`. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Zakáže blokování všech požadavků odeslaných ze stránek, které odpovíd - `@@||example.com^$urlblock` — nebudou blokovány žádné požadavky odeslané z `example.com` a ze všech subdomén. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Kompatibilita V AdGuardu pro iOS a AdGuardu pro Safari fungují pravidla `$urlblock` jako [$document exclusion](#document-modifier) — odblokování všeho. -::: - -:::info Kompatibilita - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Pravidla s modifikátorem `$urlblock` nejsou Blokátorem obsahu AdGuard podporována. ::: @@ -1124,17 +1035,11 @@ Zakáže generická základní pravidla na stránkách, které odpovídají prav - `@@||example.com^$genericblock` zakáže generická základní pravidla na `example.com` a všech subdoménách. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Kompatibilita V AdGuardu pro iOS a AdGuardu pro Safari fungují pravidla `$genericblock` jako [$document exclusion](#document-modifier) — odblokování všeho. -::: - -:::info Kompatibilita - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Pravidla s modifikátorem `$genericblock` nejsou Blokátorem obsahu AdGuard podporována. ::: @@ -1184,35 +1089,36 @@ Tyto modifikátory mohou zcela změnit chování základních pravidel. -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — plně podporováno - ✅ * — podporováno, ale spolehlivost se může lišit nebo se mohou vyskytnout omezení; více informací naleznete v popisu modifikátoru -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — může být již implementováno ve verzích nightly nebo beta, ale není ještě podporováno ve verzích pro vydání + - ❌ — nepodporováno - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ Tyto modifikátory mohou zcela změnit chování základních pravidel. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Omezení - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Kompatibilita Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` je zakázána pro `example.com` a `example.org` pomocí `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` NENÍ zakázána pro `example.com` pomocí `/some$domain=example.com|~example.org,badfilter`, protože hodnota modifikátoru `$domain` obsahuje negovanou doménu -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Kompatibilita Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ kde: - **`name`** — nepovinné, řetězec nebo regulární výraz pro přiřazení názvu cookie. - **`seconds`** — počet sekund aktuálního času pro posunutí data vypršení platnosti souboru cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — řetězec pro strategii použití cookie [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite). For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Příklady** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` odblokuje jeden soubor cookie s názvem `concept` - `@@||example.org^$cookie=/^_ga_/` odblokuje každý soubor cookie, který odpovídá regulárnímu výrazu -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Omezení -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Omezení - V hodnotě `$csp` je zakázáno několik znaků: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- Pravidla `$csp` podporují omezený seznam modifikátorů: `$domain`, `$important`, `$subdocument`. - Pravidla s direktivami `report-*` jsou považována za neplatná. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. Při odstranění segmentu se odstraní také všechny znaky, které se vztahují pouze k tomuto segmentu 1. Pokud se znak vztahuje na více segmentů a všechny tyto segmenty jsou odstraněny, je odstraněna i znak 1. Protože neexistuje způsob, jak rozpoznat různé druhy znaků podle syntaxe, rozpoznáváme všechny znaky uvedené v RFC a některé nestandardní znaky, se kterými jsme se setkali v praxi. Všechny řádky začínající na `#`. Ty, které nejsou rozpoznány jako znak, jsou předány bez úprav a nejsou porovnávány s pravidly -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. Pokud víte, co děláte, můžete pomocí pravidel `$replace` odstranit nebo přepsat pouze jeden znak ze seznamu skladeb +1. Značky nebudou přiřazeny, pokud se vztahují na celý seznam stop a k jejich odstranění nelze použít pravidla `$hls`, protože tyto typy pravidel jsou určeny pro odstraňování segmentů. Pokud víte, co děláte, můžete pomocí pravidel `$replace` odstranit nebo přepsat pouze jeden znak ze seznamu skladeb **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Omezení - Pravidla `$hls` lze použít [**pouze v důvěryhodných filtrech**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- Pravidla `$hls` jsou kompatibilní pouze s modifikátory `$domain`, `$third- party`, `$app`, `$important`, `$match- case` a `$xmlhttprequest`. - `$hls` pravidla platí pouze pro seznamy stop HLS, což je text kódovaný v UTF-8 začínající řádkem `#EXTM3U`. Jakákoli jiná odpověď nebude těmito pravidly upravena. - Pravidla `$hls` neplatí, pokud je velikost původní odpovědi větší než 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Kompatibilita -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Omezení -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` pravidla jsou kompatibilní pouze s těmito modifikátory: `$domain`, `$third-party`, `$app`, `$important`, `$match-case` a `$xmlhttprequest`. - Pravidla `$jsonprune` neplatí, pokud je velikost původní odpovědi větší než 10 MB. ::: :::info Kompatibilita -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Omezení -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` pravidla jsou kompatibilní pouze s těmito modifikátory: `$domain`, `$third-party`, `$app`, `$important`, `$match-case` a `$xmlhttprequest`. - Pravidla `$xmlprune` neplatí, pokud je velikost původní odpovědi větší než 10 MB. ::: :::info Kompatibilita -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Kompatibilita -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Další podrobnosti najdete v [prioritách pravidel](#rule-priorities). -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Kompatibilita -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Pravidla s modifikátorem `$redirect` nejsou podporována Blokátorem obsahu AdGuard, AdGuardem pro iOS a AdGuardem pro Safari. - `$redirect` v uBlock Origin podporuje zadané priority, např. `$redirect=noopjs:42`. AdGuard to nepodporuje a místo toho pouze zahodí prioritní postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Kompatibilita -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Kompatibilita -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. Pravidla s jinými modifikátory jsou považována za neplatná a budou vyřazena. +1. Pravidla `$removeheader` jsou kompatibilní s `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, a [modifikátory typu obsahu,](#content-type-modifiers) jako např. `$script` a `$stylesheet`. Pravidla s jinými modifikátory jsou považována za neplatná a budou vyřazena. ::: :::info Kompatibilita -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` odstraní parametr dotazu s názvem `param` z URL libovolného požadavku, např. požadavek na `http://example.com/page?param=1&another=2` bude transformován na `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Příklad: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Omezení - Pravidla s modifikátorem `$removeparam` lze použít [**pouze v důvěryhodných filtrech**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Kompatibilita -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Pravidla s modifikátorem `$removeparam` podporuje AdGuard pro Windows, Mac, Android a Rozšíření prohlížeče AdGuard pro Chrome, Firefox a Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - Pravidla `$replace` platí pro jakoukoli textovou odpověď, ale neplatí pro binární (`media`, `image`, `object` atd.). - Pravidla `$replace` neplatí, pokud je velikost původní odpovědi větší než 10 MB. -- Pravidla `$replace` mají vyšší prioritu než ostatní základní pravidla (**včetně** pravidel výjimek). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- Pravidla `$replace` mají vyšší prioritu než ostatní základní pravidla (**včetně** pravidel výjimek). Pokud tedy požadavek odpovídá dvěma různým pravidlům, z nichž jedno má modifikátor `$replace`, použije se toto pravidlo. - Pravidla výjimek na úrovni dokumentu s modifikátory `$content` nebo `$document` zakáží pravidla `$replace` pro požadavky, které jim odpovídají. - Ostatní pravidla výjimek na úrovni dokumentu (`$generichide`, `$elemhide` nebo modifikátory `$jsinject`) se uplatňují vedle pravidel `$replace`. To znamená, že můžete upravit obsah stránky pomocí pravidla `$replace` a zároveň zde zakázat kosmetická pravidla. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Kompatibilita -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` pravidla platí pro jakýkoli text URL požadavku. +- `$urltransform` pravidla mohou také **upravit část dotazu** URL. - `$urltransform` nebude použito, pokud je původní URL blokována jinými pravidly. - `$urltransform` se použije před pravidly `$removeparam`. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Kompatibilita - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Příklady** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Příklady** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) s negovanými doménami pomocí `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) s negovanými metodami pomocí `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - omezené [typy obsahu](#content-type-modifiers) s `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Definované modifikátory typu obsahu, definované metody, definovaná záhlaví, $all, $popup, specifické výjimky {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` nebo `$app` s povolenými doménami nebo aplikacemi {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Kategorie \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | -| ---------------------------------------- |:----------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Skrytí prvků](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [Pravidla CSS](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Rozšířené CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtrování](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlety](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Kategorie \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| ---------------------------------------- |:----------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Skrytí prvků](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [Pravidla CSS](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Rozšířené CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtrování](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlety](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Omezení** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Výjimky** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3294,11 +3089,11 @@ the element `div#match` can be selected by any of these extended selectors: ! prostý text div:contains(banner) -! regular expression -div:contains(/as .*banner/) +! regulární výraz +div:contains(/as .* banner/) -! regular expression with flags -div:contains(/it .*banner/gi) +! regulární výraz s příznaky +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — nepovinný, standardní nebo rozšířený selektor CSS může být přeskočen pro kontrolu *libovolného* prvku - `pseudo-element` — volitelný, platný standardní pseudoprvek, např. `before`, `after`, `first-line` atd. - `property` — povinný, název vlastnosti CSS, pro kterou se má prvek zkontrolovat -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. Při tomto typu porovnávání, AdGuard vždy porovnává bez ohledu na velikost písmen. V případě regulárního výrazu vypadá vzor takto: `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. Při tomto typu porovnávání, AdGuard vždy porovnává bez ohledu na velikost písmen. V případě regulárního výrazu vypadá vzor takto: `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Kompatibilita -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## Pravidla JavaScript {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — omezení domény pro dané pravidlo. Stejné zásady jako v [pravidlech pro skrývání prvků](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`skript`** — libovolný kód JavaScript **v jednom řetězci**. **Příklady** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — povinný, název skriptletu z knihovny skripletů AdGuard +- **`arguments`** — volitelnýný, seznam argumentů `string` (jiné typy argumentů nejsou podporovány) **Příklady** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Příklady** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Důvěryhodné skriptlety {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | -| ------------------------------------- |:----------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifikátor \ Produkty | [Aplikace CoreLibs][cl-apps] | [AdGuard pro Chromium][ext-chr] | [AdGuard pro Firefox][ext-ff] | [AdGuard pro iOS][ios-app] | [AdGuard pro Safari][ext-saf] | [Blokátor obsahu AdGuard][and-cb] | +| ------------------------------------- |:----------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — plně podporováno -- ✅ * — podporováno, ale spolehlivost se může lišit nebo se mohou vyskytnout omezení; více informací naleznete v popisu modifikátoru +- 🧩 — může být již implementováno ve verzích nightly nebo beta, ale není ještě podporováno ve verzích pro vydání - ❌ — nepodporováno ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Kompatibilita -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Kompatibilita -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Omezení In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Kompatibilita -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Informace pro správce filtrů If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Direktivy preprocesoru -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [zahrnutý soubor](#include-directive) - [použití pravidel podmíněně podle typu blokátoru reklam](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Zahrnutý soubor {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Podmínky {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4424,7 +4151,7 @@ kde: - `adguard_ext_edge` — Rozšíření prohlížeče AdGuard pro starší Edge - `adguard_ext_opera` — Rozšíření prohlížeče AdGuard pro Operu - `adguard_ext_android_cb` — Blokátor obsahu AdGuard pro mobilní prohlížeče Samsung a Yandex - - `ext_ublock` — special case; this one is declared when a uBlock version of a filter is compiled by the [FiltersRegistry][] + - `ext_ublock` — speciální případ; ten je deklarován, když je verze filtru uBlock kompilována pomocí [FiltersRegistry][] - `cap_html_filtering` — produkty, které podporují pravidla filtrování HTML: AdGuard pro Windows, AdGuard pro macOS a AdGuard pro Android - `!#else` — začátek bloku při nesplnění podmínek - `rules_list`, `true_conditions_rules_list`, `false_conditions_rules_list` — seznamy pravidel @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text případně parsovaného selektoru - `timings` — seznam uzlů DOM odpovídajících selektoru - `appliesCount` — celkový počet použití selektoru na stránce - `appliesTimings` — doba, po kterou byl selektor na stránce použit, pro každý případ, kdy byl použit (v milisekundách) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Zkratky produktů {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `aplikací CoreLibs` — AdGuard pro Windows, AdGuard pro Mac a AdGuard pro Android +1. `AdGuard pro Chromium` — Rozšíření prohlížeče AdGuard pro Chrome a další prohlížeče založené na Chromium, např. nový Microsoft Edge, Opera +1. `Adguard pro Firefox` — Rozšíření prohlížeče AdGuard pro Firefox +1. `AdGuard pro iOS` — AdGuard pro iOS a AdGuard pro iOS Pro (pro mobilní prohlížeč Safari) +1. `AdGuard pro Safari` — AdGuard pro stolní prohlížeč Safari `AdGuard Content Blocker` — Content Blocker pro mobilní prohlížeče Android: Samsung Internet a Yandex Browser ### Zkratky kompatibility {#what-compatibility} @@ -4758,32 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — plně podporováno - ✅ * — podporováno, ale spolehlivost se může lišit nebo se mohou vyskytnout omezení; více informací naleznete v popisu modifikátoru - 🧩 — může být již implementováno ve verzích nightly nebo beta, ale není ještě podporováno ve verzích pro vydání -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — funkce, která byla implementována nebo jejíž implementace se plánuje, ale zatím není k dispozici v žádném produktu - ❌ — nepodporováno - 👎 — deprecated; still supported but will be removed in the future - 🚫 — odstraněno a již nepodporováno ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard pro Safari" -[ext-saf]: #what-product "AdGuard for Safari" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index ce92e73e144..77f7f88401b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ Mezi AdGuard filtry blokující reklamy patří: - Základní filtr AdGuardu - Filtr mobilních reklam AdGuard - Regionální filtry rozdělené podle jazyků — čínština, holandština, francouzština, němčina, japonština, ruština, španělština/portugalština, turečtina a ukrajinština -- AdGuard Quick Fixes filter ### Účel těchto filtrů - **Základní filtr** je určen k blokování reklam na anglicky psaných webových stránkách a na těch, pro které neexistuje samostatný filtr. Obsahuje také obecná pravidla filtrování, která platí pro všechny weby bez ohledu na jazyk - **Filtr mobilních reklam** blokuje reklamy na mobilních verzích webových stránek a v mobilních aplikacích. Neexistuje žádná segmentace na základě jazyka - **Regionální filtry** se řídí stejnými zásadami jako **Základní filtr**, ale jsou omezeny na webové stránky v konkrétních jazycích -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. Cílem filtrů pro blokování reklam je blokovat všechny typy reklam na webových stránkách, v aplikacích a v některých zařízeních, která mohou načítat reklamy z internetu: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index 59624a911a3..8b77df2b1b8 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: Jak funguje blokování reklam sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. Všechny však spojuje to, že blokují reklamy a slídiče. Tento článek popisuje, jak blokování reklam funguje zevnitř. +AdGuard nabízí mnoho produktů pro blokování reklam pro různé platformy a každý produkt má své vlastní jedinečné funkce. Všechny však spojuje to, že blokují reklamy a slídiče. Tento článek popisuje, jak blokování reklam funguje zevnitř. :::note diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/browsing-security.md index 47e891c89ee..18e549a2e9b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. Snažíme se procento falešných pozitivních výsledků snížit, ale stále se vyskytují. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 1a3763f09ed..32ba0e17b72 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) je rozšíření protokolu HTTP, které podporuje šifrování pro zvýšení bezpečnosti. Tento protokol se používá k bezpečnému přenosu cenných informací, jako jsou osobní údaje, údaje o kreditních kartách atd. -Používání protokolu HTTPS je velmi výhodné, protože šifrovaný provoz je chráněn proti odposlechu třetí stranou, což můžeme jen uvítat. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Používání protokolu HTTPS je velmi výhodné, protože šifrovaný provoz je chráněn proti odposlechu třetí stranou, což můžeme jen uvítat. Přijetí protokolu HTTPS v posledních letech roste. Především proto, že je [podporován společností Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) a také díky vzniku bezplatné certifikační autority [Let's Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). Níže uvedený diagram popisuje rozdíl mezi prostým protokolem HTTP a zabezpečeným protokolem HTTPS. @@ -15,17 +15,17 @@ Níže uvedený diagram popisuje rozdíl mezi prostým protokolem HTTP a zabezpe ### Co je to bezpečnostní certifikát? -Sručně řečeno, HTTPS znamená šifrování dat. Ale stále je tu problém: jak si můžete být jisti, že jste navázali šifrované připojení se správnou webovou stránkou? Zde přicházejí ke slovu bezpečnostní certifikáty. A certificate serves as proof that the website is really who or what it claims to be. Pokud webová stránka takový certifikát nemá nebo pokud certifikát obsahuje nesprávné informace, prohlížeč vám neumožní navázat zabezpečené připojení. Je důležité, aby certifikát, který webová stránka používá, byl vydán certifikační autoritou (CA), které prohlížeč důvěřuje. Taková certifikační autorita (CA) zaručuje, že certifikát SSL je skutečně vydán vlastníkovi webových stránek. +Sručně řečeno, HTTPS znamená šifrování dat. Ale stále je tu problém: jak si můžete být jisti, že jste navázali šifrované připojení se správnou webovou stránkou? Zde přicházejí ke slovu bezpečnostní certifikáty. Certifikát slouží jako důkaz, že webová stránka je skutečně taková, jaká je. Pokud webová stránka takový certifikát nemá nebo pokud certifikát obsahuje nesprávné informace, prohlížeč vám neumožní navázat zabezpečené připojení. Je důležité, aby certifikát, který webová stránka používá, byl vydán certifikační autoritou (CA), které prohlížeč důvěřuje. Taková certifikační autorita (CA) zaručuje, že certifikát SSL je skutečně vydán vlastníkovi webových stránek. ### Proč musí být AdGuard schopen filtrovat HTTPS? -Většina webů nyní používá protokol HTTPS a totéž platí i pro reklamu. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Většina webů nyní používá protokol HTTPS a totéž platí i pro reklamu. Zde je několik populárních webových stránek, kde nelze odstranit reklamy bez filtrování HTTPS: youtube.com, facebook.com a twitter.com. ### Jak funguje HTTPS filtrování? -Kdyby to bylo snadné, protokol HTTPS by nebyl tak bezpečný. Když se prohlížeč pokusí připojit k serveru, AdGuard vytvoří dvě zabezpečená připojení: jedno s prohlížečem (nebo jinou aplikací) a druhé se serverem. Prohlížeč musí důvěřovat AdGuardu a připojením, která vytváří. Za tímto účelem AdGuard generuje speciální (a jedinečný) kořenový certifikát a instaluje jej do systému a v případě potřeby i do některých prohlížečů (např. Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +Kdyby to bylo snadné, protokol HTTPS by nebyl tak bezpečný. Když se prohlížeč pokusí připojit k serveru, AdGuard vytvoří dvě zabezpečená připojení: jedno s prohlížečem (nebo jinou aplikací) a druhé se serverem. Prohlížeč musí důvěřovat AdGuardu a připojením, která vytváří. Za tímto účelem AdGuard generuje speciální (a jedinečný) kořenový certifikát a instaluje jej do systému a v případě potřeby i do některých prohlížečů (např. Firefox). AdGuard tak může sledovat, co se děje uvnitř zabezpečeného připojení a plnit své úkoly — blokovat reklamy a slídiče. -For better understanding, we have depicted this process: +Pro lepší pochopení jsme tento proces znázornili: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/license/what-is.md index 472b767ea19..86ffa0df77a 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: Co je licence AdGuardu? sidebar_position: 1 --- @@ -12,7 +12,7 @@ Na [stránce nákupu](https://adguard.com/license.html) můžete vidět následu - **Roční předplatné** — tyto licence se obnovují automaticky každý rok nebo je lze prodloužit ručně - Osobní — až pro 3 zařízení - Rodinná — až pro 9 zařízení -- **Lifetime** — these licenses are perpetual +- **Doživotní** — tyto licence nejsou časově omezené - Osobní — až pro 3 zařízení - Rodinná — až pro 9 zařízení diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 541a57575d4..6d0b8f202c2 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Povolením této možnosti zabráníte prohlížeči odesílat data GPS, která ### Blokovat Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Zapnutím tohoto nastavení zablokuje AdGuard schopnost prohlížečů detekovat komponenty (například zásuvné moduly a objekty ActiveXObject), které umožňují zobrazování obsahu ve formátu Flash. To ve skutečnosti znamená, že prohlížeče nejsou schopny podporovat Flash. +Zásuvný modul Flash Player je stále zranitelnější vůči online hrozbám, jako jsou viry a hackeři a může také výrazně ovlivnit dobu načítání webových stránek. Zapnutím tohoto nastavení zablokuje AdGuard schopnost prohlížečů detekovat komponenty (například zásuvné moduly a objekty ActiveXObject), které umožňují zobrazování obsahu ve formátu Flash. To ve skutečnosti znamená, že prohlížeče nejsou schopny podporovat Flash. ### Blokovat Java {#java} @@ -95,7 +95,7 @@ Můžete také nastavit libovolnou hodnotu pro referenční ID zadáním do pole Všimněte si, že aby bylo možné filtrovat provoz, aplikace AdGuard "zachycují" požadavky prohlížeče na server. Požadavky na reklamní, sledovací a phishingové servery mohou být před odesláním na server změněny nebo zcela zablokovány. Totéž platí pro možnost *Skrýt třetím stranám referenční ID*: AdGuard zachycuje požadavky HTTP(S) zejména za účelem odstranění nebo změny hlavičky referenčního ID, pokud je tato možnost povolena. K tomu však dochází až poté, co tyto požadavky "opustí" prohlížeč. To znamená, že pokud sledujete referenční ID v prohlížeči (například pomocí vývojářských nástrojů Chrome), uvidíte původní referenční ID, protože požadavek ještě nedorazil do AdGuardu. Můžete použít software jako [Fiddler](https://www.telerik.com/fiddler), abyste se ujistili, že referenční ID bude změněno správně. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. Hned na místě změní referenční ID, takže nástroje pro vývojáře budou zobrazovat požadované referenční ID pro vaše požadavky. +Naopak, vzhledem k povaze všech rozšíření prohlížeče funguje Rozšíření prohlížeče AdGuard "uvnitř" prohlížeče. Hned na místě změní referenční ID, takže nástroje pro vývojáře budou zobrazovat požadované referenční ID pro vaše požadavky. ### Skrýt User-Agent {#useragent} @@ -120,9 +120,3 @@ Deep Packet Inspection je systém hloubkové analýzy a filtrování provozu pod AdGuard může upravit odchozí data paketů tak, aby klient nespadal pod kritéria blokování DPI. To znamená, že zapnutím této možnosti mohou uživatelé získat přístup k požadovanému obsahu. V současné době nelze obejít všechny systémy DPI, ale neustále pracujeme na jejich vylepšení. Funkce "Ochrana před DPI" je již implementována v aplikacích AdGuard pro Windows, AdGuard pro Mac a AdGuard pro Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/cs/docusaurus-plugin-content-docs/current/general/userscripts.md index 139514bde4c..d209c2c6768 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. Upravují nebo rozšiřují funkce jedné nebo více webových stránek. Mnoho uživatelů AdGuardu již možná zná uživatelské skripty jako AdGuard asistent, Blokátor vyskakovacích oken a AdGuard Extra. +Uživatelské skripty (říkáme jim také "rozšíření") jsou de facto miniprogramy napsané v jazyce JavaScript. Upravují nebo rozšiřují funkce jedné nebo více webových stránek. Mnoho uživatelů AdGuardu již možná zná uživatelské skripty jako AdGuard asistent, Blokátor vyskakovacích oken a AdGuard Extra. :::notePodporované aplikace @@ -134,7 +134,7 @@ Zde je [odkaz](mailto:devteam@adguard.com?Subject=Userscript%20author%20license% ##### Nepodporované vlastnosti -These properties will be simply ignored by AdGuard. +Tyto vlastnosti bude Adguard jednoduše ignorovat. ```text @unwrap diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/cs/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 8c39cb73085..176d34cdc83 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: Jak shromažďovat soubory HAR sidebar_position: 1 --- diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/cs/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 9f2db34119a..9d13b028aa8 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Zkontrolujte, zda nebyla chyba nahlášena již dříve. Doporučujeme věnovat ### Jak popsat problém -Pokuste se uvést co nejvíce podrobností — usnadníte nám tak reprodukci chyby a zjistíme, jak ji opravit. Here’s what we expect a bug report to include: +Pokuste se uvést co nejvíce podrobností — usnadníte nám tak reprodukci chyby a zjistíme, jak ji opravit. V hlášení o chybě očekáváme následující informace: - Verzi aplikace - Verzi OS @@ -26,9 +26,9 @@ Pokuste se uvést co nejvíce podrobností — usnadníte nám tak reprodukci ch - Zda se problém opakuje a s jakou frekvencí - Jestli používáte VPN nebo antivirový software -### How to collect logs +### Jak shromažďovat a záznamy -Read about collecting logs in dedicated articles for each platform. +O shromažďování záznamů se dočtete v článcích věnovaných jednotlivým platformám. ## Jak hlasovat pro hlášení chyb nebo požadavky na funkce diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/cs/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index 6194bd11d84..72ef5b87b1f 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ Na některých noteboocích musíte podržet *Fn* a pak místo toho stisknout *P Windows zachytí celou obrazovku a zkopíruje ji do schránky. -To take a screenshot of an active window, use the following shortcut keys: +Chcete-li pořídit snímek obrazovky aktivního okna, použijte následující klávesovou zkratku: - **Podržte stisknutý *Alt* a stiskněte *PrtScn* (nebo na některých noteboocích *Fn + Alt + PrtScn*)** -To take a screenshot of a specific area, use the following shortcut keys: +Chcete-li pořídit snímek obrazovky určité oblasti, použijte následující klávesovou zkratku: - ***Stiskněte ***Win + Shift + S****** -Po pořízení snímku obrazovky se snímek uloží do schránky. Ve většině případů jej budete moci vložit do dokumentu, který právě upravujete, pomocí zkratky *Ctrl + V*. Pokud potřebujete snímek obrazovky uložit do souboru, otevřete standardní program **Malování** (nebo jinou aplikaci, která umí pracovat s obrázky). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +Po pořízení snímku obrazovky se snímek uloží do schránky. Ve většině případů jej budete moci vložit do dokumentu, který právě upravujete, pomocí zkratky *Ctrl + V*. Pokud potřebujete snímek obrazovky uložit do souboru, otevřete standardní program **Malování** (nebo jinou aplikaci, která umí pracovat s obrázky). Vložte tam snímek obrazovky pomocí stejné klávesové zkratky nebo kliknutím na tlačítko Vložit (obvykle v levém horním rohu obrazovky) a poté jej uložte. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. Jakmile stisknete tyto klávesy, snímek obrazovky se automaticky uloží jako soubor do složky *Obrázky* → *Snímky obrazovky*. +Windows 8 a 10 umožňují pořídit snímek obrazovky velmi rychle pomocí klávesové zkratky *Win + PrtScn*. Jakmile stisknete tyto klávesy, snímek obrazovky se automaticky uloží jako soubor do složky *Obrázky* → *Snímky obrazovky*. K pořizování snímků obrazovky existuje také specializovaný program *Výstřižky*, který najdete v nabídce Start mezi standardními programy počítače. Výstřižky vám umožní zachytit jakoukoli oblast vaší pracovní plochy nebo celou obrazovku. Po pořízení snímku obrazovky pomocí tohoto programu můžete obrázek upravit a uložit do libovolné složky v počítači. @@ -70,26 +70,26 @@ Kromě toho můžete zkusit používat různé aplikace pro pořizování snímk ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Chcete-li pořídit snímek obrazovky v zařízení se systémem macOS, použijte následující zkratku: - ***Stiskněte a podržte ***⌘ Cmd + Shift + 3****** Váš Mac zachytí celou obrazovku a uloží ji jako soubor na plochu. -To take a screenshot of an active window, use the following shortcut keys: +Chcete-li pořídit snímek obrazovky aktivního okna, použijte následující klávesovou zkratku: - **Stiskněte a podržte *⌘ Cmd + Shift + 4 + mezerník*. Ukazatel se změní na ikonu fotoaparátu. Klikněte na okno a zachyťte snímek. Stisknutím Esc zrušíte pořizování snímku obrazovky** -To take a screenshot of a specific area, use the following shortcut keys: +Chcete-li pořídit snímek obrazovky určité oblasti, použijte následující klávesovou zkratku: - ***Stiskněte ***⌘ Cmd + Shift + 5******. Přetažením křížku vyberte potřebnou oblast. Pro pořízení snímku obrazovky, uvolněte myš nebo trackpad, pro zrušení stiskněte Esc. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +Chcete-li pořídit snímek obrazovky pomocí *Touch Bar* (MacBook Pro), použijte následující klávesové zkratky: - ***Stiskněte ***⌘ Cmd + Shift + 6****** Mac zachytí celý *Touch Bar* a uloží jej jako soubor na plochu. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +Chcete-li snímek obrazovky zkopírovat do schránky namísto uložení, podržte *Ctrl* spolu s některou z výše uvedených klávesových zkratek. Poté můžete snímek obrazovky (ze schránky) vložit do dokumentu nebo obrázku, který právě upravujete pomocí klávesových zkratek *Cmd + V*. Snímky obrazovky můžete pořizovat také pomocí **Náhled** a výběrem **Pořídit snímek obrazovky** (vybrané oblasti, okna nebo celé obrazovky). Pomocí **Náhledu** můžete ukládat snímky obrazovky ve formátech JPG, TIFF, PDF a dalších. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/intro.md b/i18n/cs/docusaurus-plugin-content-docs/current/intro.md index 1fa6c65de29..46af0c5d441 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ Vyvíjíme a spravujeme také bezplatná rozšíření prohlížeče pro všechn ## Nejen blokování reklam -Blokátor reklam AdGuard umí víc než jen blokovat reklamy. Ochrání vás před sledováním online a v mnoha ohledech posílí vaše soukromí. V závislosti na konkrétním produktu může AdGuard nabízet také takové výhody, jako je DNS filtrování pro lepší ochranu, rodičovská ochrana, která chrání vaše děti před nevhodným obsahem, záznam filtrování pro lepší kontrolu internetového provozu a další. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +Blokátor reklam AdGuard umí víc než jen blokovat reklamy. Ochrání vás před sledováním online a v mnoha ohledech posílí vaše soukromí. V závislosti na konkrétním produktu může AdGuard nabízet také takové výhody, jako je DNS filtrování pro lepší ochranu, rodičovská ochrana, která chrání vaše děti před nevhodným obsahem, záznam filtrování pro lepší kontrolu internetového provozu a další. Tato databáze znalostí obsahuje podrobné informace o všech z nich — neváhejte přejít na článek, který vás zajímá. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cc4012ad33d..3ccdecfa1f8 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Webové stránky neustále mění způsob vkládání reklam a my do našich fil Práce s filtry blokování však vyžaduje specifické dovednosti. Pokud je máte a umíte vytvářet pravidla, přejděte rovnou do našeho [repozitáře AdGuard Filters](https://github.com/AdguardTeam/AdguardFilters) na GitHubu. Najdete zde spoustu otevřených problémů, z nichž každý odkazuje na problém s nějakou webovou stránkou — nezablokovaná reklama, falešný pozitivní výsledek atd. Vyberte si, co chcete a navrhněte vlastní pravidla v komentářích. Inženýři AdGuard filtrů vaše návrhy posoudí a pokud je shledají vhodnými, budou vaše pravidla přidána do filtrů AdGuardu. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +Pokud ještě neznáte syntaxi našich pravidel filtrování nebo si ji potřebujete osvěžit, najdete základní informace o syntaxi v [naší databázi znalostí](/general/ad-filtering/create-own-filters). ### Odměny {#rewards} diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index 6b46e2ed85b..5eaa5906323 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Jak se stát se překladatelem/korektorem sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +Pokud chcete pomáhat překládat produkty, webové stránky a znalostní databáze AdGuardu, přejděte na [Crowdin](https://crowdin.com/) a zaregistrujte se/přihlaste se. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index bbf22cba04f..80bc0c722f9 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ Když se setkáte s překladem, který vyžaduje použití množného čísla, m Zde je několik zdrojů informací, které můžete použít. -[Průvodce překlady](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) obsahuje široký seznam jazyků. Počet tvarů množného čísla pro různé jazyky se zobrazuje takto: `nplurals=2`, `nplurals=4` atd. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Průvodce překlady](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) obsahuje široký seznam jazyků. Počet tvarů množného čísla pro různé jazyky se zobrazuje takto: `nplurals=2`, `nplurals=4` atd. Číslice za znaménkem rovnosti `=` znamená počet tvarů množného čísla příslušného jazyka. Informace o tvarech množného čísla můžete také získat v databázi [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). Pravidla CLDR pro množné číslo uvádějí další slovní tvar pro desetinná čísla (1,5; 2,3; 100,1…), ale v překladech AdGuardu je nepoužíváme. diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 555d2422961..fe36f9b1d1e 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: Překladatelský program AdGuardu sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Odmítnutí odpovědnosti:** můžete se nás zeptat na cokoli ohledně překladu AdGuardu zasláním e-mailu na adresu [translate@adguard.com](mailto:translate@adguard.com) nebo připojením k naší [diskuzi na Telegramu](https://t.me/joinchat/UVYTLcHbr8JmOGIy). -When it comes to translations, we at AdGuard always heavily rely on volunteers. +Pokud jde o překlady, my v AdGuardu vždy do značné míry spoléháme na dobrovolníky. -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +Ke správě překladů našich produktů používáme platformu [Crowdin](https://crowdin.com/). Toto je místo pro každého, kdo chce přispět AdGuardu překladem některého z našich produktů. -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +Pokud se chcete zařadit mezi dobrovolníky, kteří nám pomáhají překládat AdGuard, přečtěte si [jak se stát naším překladatelem](../become-translator) a [ jak s nimi spolupracujeme](../rewards). diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 780bb324537..7e5684ab59b 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: Jak upřednostnit překlady souborů na Crowdinu sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +Na serveru Crowdin je pět hlavních projektů AdGuard — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base) a [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). Nemáme jasné pokyny, se kterými soubory nebo produkty projektu *AdGuard Applications* začít. Stačí si vybrat libovolný produkt. Je tu jen pár věcí, které bychom rádi zmínili: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- Aplikaci můžete zobrazit pouze v těch jazycích, pro které jsou v aplikaci Crowdin dokončeny všechny překlady; - Popisy pro obchody s aplikacemi doporučujeme překládat až na druhém místě, protože bez překladu samotných produktů nebudou popisy potřeba. V projektu *AdGuard Websites* je situace jiná. Jazyky lze na web přidat, i když není k dispozici úplná sada překladů. To však závisí i na tom, které soubory již byly přeloženy. Proto doporučujeme začít nejdůležitějšími soubory, které jsou uvedeny níže: diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 3bc1c9ba75d..deb167d0545 100644 --- a/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/cs/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Aktualizace databáze znalostí sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. Ale věci se neustále mění a někdy už článek neodráží aktuální stav věcí. +Cílem databáze znalostí blokátoru reklam AdGuard je poskytnout všem nejaktuálnější informace o všech druzích témat souvisejících s AdGuardem. Ale věci se neustále mění a někdy už článek neodráží aktuální stav věcí. Proto jsme veškerý obsah KB (databáze znalostí) umístili na [GitHub](https://github.com/AdguardTeam/KnowledgeBase), kam nyní může přispívat doslova každý, a to jak navrhováním úprav a překladů stávajících, tak i zcela nových článků. ## Jak navrhnout změnu nebo napsat nový článek {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. Pokud neznáte principy práce s platformou, začněte přečtením [dokumentace GitHub](https://docs.github.com/en). +Pomocí výše uvedených funkcí GitHubu můžete navrhovat změny stávajících článků a přidávat nové články do databáze znalostí. Pokud neznáte principy práce s platformou, začněte přečtením [dokumentace GitHub](https://docs.github.com/en). -Jakmile budete připraveni začít, zapracujte na [repozitáři KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Mějte to na paměti při úpravách nebo psaní článků. Chcete-li se dozvědět více o syntaxi Markdown, následujte [tento odkaz](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). +Jakmile budete připraveni začít, zapracujte na [repozitáři KnowledgeBaseDNS](https://github.com/AdguardTeam/KnowledgeBase). Všechny texty v naší znalostní databázi jsou napsány ve značkovacím jazyce `Markdown`. Mějte to na paměti při úpravách nebo psaní článků. Chcete-li se dozvědět více o syntaxi Markdown, následujte [tento odkaz](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. Při navrhování změn nebo doplňků berte v úvahu, že všechny dokumenty musí být v souladu se zásadami platformy. Můžete si o nich přečíst v [průvodci Docosaurus](https://docusaurus.io/docs/category/guides). +Webová stránka databáze znalostí je vytvořena pomocí moderního generátoru statických webových stránek Docusaurus 2. Při navrhování změn nebo doplňků berte v úvahu, že všechny dokumenty musí být v souladu se zásadami platformy. Můžete si o nich přečíst v [průvodci Docosaurus](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +Tuto databázi znalostí můžete lokálně uložit do svého počítače a zobrazit náhled navrhovaných změn. Podrobný návod, jak to provést, najdete na adrese [v souboru README.md](https://github.com/AdguardTeam/KnowledgeBase#readme) na stránce GitHub této databáze znalostí. ## Překládání článků {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Překlad stávajících článků databáze znalostí se provádí na [platformě Crowdin](https://crowdin.com/profile/adguard). Všechny podrobnosti o překladech a práci s platformou Crowdin najdete [ve speciálním článku](../translate/guidelines) databáze znalostí blokátoru reklam AdGuard. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [V samostatném článku](../translate/plural-forms) jsme podrobně popsali potíže, které mohou nastat při překladu řetězců s množným číslem a poskytli jsme rozsáhlý návod, jak s nimi na platformě Crowdin pracovat. +Při práci na článcích databáze znalostí AdGuardu se můžete setkat s řetězci obsahujícími množné číslo, které byste měli překládat se zvýšenou pozorností. [V samostatném článku](../translate/plural-forms) jsme podrobně popsali potíže, které mohou nastat při překladu řetězců s množným číslem a poskytli jsme rozsáhlý návod, jak s nimi na platformě Crowdin pracovat. ## Práce na otevřených problémech -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Vyberte si téma, které vás zaujme, a začněte na něm pracovat. Pokud máte nějaké dotazy — můžete je položit přímo v komentářích k tomuto vydání. +Někdy existují [otevřené úlohy](https://github.com/AdguardTeam/KnowledgeBase/issues) související s aktualizací databáze znalostí. Můžete nám pomoci urychlit jejich dokončení [stejným způsobem](#suggest-change), jakým byste navrhli jakékoli jiné změny v této databázi znalostí. Vyberte si téma, které vás zaujme, a začněte na něm pracovat. Pokud máte nějaké dotazy — můžete je položit přímo v komentářích k tomuto vydání. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/da/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/da/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/da/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/da/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/da/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/da/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/da/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/da/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/da/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/da/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/da/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/da/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/intro.md b/i18n/da/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/da/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 901c3575501..0cc779bb650 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 3fe7781204c..3e73c3ad7c7 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ Sie können die Hauptseite der Erweiterung aufrufen, indem Sie auf das Erweiteru Auf der Hauptseite können Sie jedes Element auf jeder Seite manuell ausblenden — eine entsprechende Regel wird zu den _Benutzerregeln_ hinzugefügt. Sie können auch das _Filter-Protokoll_ öffnen, um vollständige Informationen über den Datenverkehr Ihres Browsers zu erhalten und Anfragen zu blockieren, oder einen Blick auf den Sicherheitsbericht einer Website werfen. Außerdem können Sie Statistiken über die angewandten Sperrregeln einsehen und eine Website melden, wenn z. B. Werbung nicht blockiert wurde. Unsere Filter-Ingenieure werden die Meldung prüfen und das Problem beheben. -Alle Webanfragen des Browsers werden im _Filter-Protokoll_ angezeigt, zusammen mit detaillierten Informationen zu jeder Anfrage. Zum Beispiel ermöglicht das _Filter-Protokoll_ eine einfache Überwachung der Anfragen, die von der AdGuard Browsererweiterung blockiert werden. Außerdem können Sie mit zwei Klicks jede beliebige Anfrage sperren oder eine bereits blockierte Anfrage zur Positivliste hinzufügen. Das _Filter-Protokoll_ bietet auch eine Vielzahl von Optionen zur Sortierung von Webanfragen, was bei der Erstellung eigener Filterregeln hilfreich sein kann. Sie können das _Filter-Protokoll_ öffnen, indem Sie den entsprechenden Punkt im Hauptmenü oder auf der Einstellungsseite (im Tab _Zusätzliche Einstellungen_) auswählen. +Alle Webanfragen des Browsers werden im _Filter-Protokoll_ angezeigt, zusammen mit detaillierten Informationen zu jeder Anfrage. Zum Beispiel ermöglicht das _Filter-Protokoll_ eine einfache Überwachung der Anfragen, die von der AdGuard Browsererweiterung blockiert werden. Außerdem können Sie mit zwei Klicks jede beliebige Anfrage sperren oder eine bereits blockierte Anfrage zur Positivliste hinzufügen. Das _Filter-Protokoll_ bietet auch eine Vielzahl von Optionen zur Sortierung von Webanfragen, was bei der Erstellung eigener Filterregeln hilfreich sein kann. Sie können das _Filter-Protokoll_ öffnen, indem Sie den entsprechenden Punkt im Hauptmenü oder im Tab _Zusätzliche Einstellungen_ auswählen. Wenn Sie auf die Symbole in der oberen rechten Ecke des Hauptmenüs klicken, können Sie die Einstellungen der Erweiterung öffnen oder den Schutz anhalten. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index c23babc9206..474e013d4df 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Abgesehen von den großen Hauptmodulen der AdGuard Browsererweiterung gibt es ei ## Allgemein {#general} -Im Tab _Allgemein_ können Sie Werbung in Suchmaschinen und die [Eigenwerbung von Websites](/general/ad-filtering/search-ads) zulassen, die automatische Aktivierung von sprachspezifischen Filtern aktivieren, das Aktualisierungsintervall der Filter angeben, usw. +Im Tab _Allgemein_ können Sie Suchanzeigen und die [Eigenwerbung von Websites](/general/ad-filtering/search-ads) zulassen, die automatische Aktivierung sprachspezifischer Filter aktivieren, das Aktualisierungsintervall der Filter angeben usw. ![Allgemein \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Außerdem können Sie hier [_Schutz vor Phishing und Malware_](/general/browsing-security) aktivieren. -Wenn Sie Ihre Einstellungen speichern möchten, klicken Sie auf die Schaltfläche _Einstellungen exportieren_. Die Einstellungen werden als .json-Datei gespeichert. Um die zuvor gespeicherten Einstellungen zu importieren, verwenden Sie die Funktion _Einstellungen importieren_. Sie können damit sogar schnell zwischen verschiedenen Einstellungsprofilen wechseln oder sogar Einstellungskonfigurationen zwischen verschiedenen Browsern übertragen. +Wenn Sie Ihre Einstellungen speichern möchten, klicken Sie auf die Schaltfläche _Einstellungen exportieren_. Die Einstellungen werden als .json-Datei gespeichert. Um die zuvor gespeicherte Konfiguration zu importieren, verwenden Sie die Funktion _Einstellungen importieren_. Sie können damit sogar schnell zwischen verschiedenen Einstellungsprofilen wechseln oder sogar Einstellungskonfigurationen zwischen verschiedenen Browsern übertragen. ## Zusätzliche Einstellungen {#misc} diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index 996323d7b7c..1fc4af22868 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index 1eebc8657a6..00000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -Das war's! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md index 51f4dbe5bab..6e88ab11bac 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md @@ -53,7 +53,7 @@ sidebar_position: 1 :::note -AdGuard ist dem Schutz Ihrer Privatsphäre verpflichtet. We strictly follow our [Privacy Policy](https://adguard.com/privacy/browser-extension.html) and do not collect any private information about users. Bevor Sie Ihre Protokolle an das Support-Team senden, überprüfen Sie bitte die Datei, da sie zusätzliche Informationen enthalten kann, die Sie vielleicht nicht freigeben möchten. Wenn sie solche persönlichen Informationen enthält, empfehlen wir Ihnen, sie zuerst zu löschen. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/browser-extension.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 91d3f00ddef..80787ef3af6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ Wenn Sie auf eine App tippen, können Sie deren Einstellungen verwalten: ### „Problemlose“ und „problematische“ Apps -Most apps work correctly when filtered. Bei solchen Apps wird der Datenverkehr durch AdGuard geleitet und standardmäßig gefiltert. +Die meisten Apps funktionieren ordnungsgemäß, wenn die Filterung aktiviert ist. Bei solchen Apps wird der Datenverkehr durch AdGuard geleitet und standardmäßig gefiltert. Einige Apps, wie z. B. Download Manager, Radio, System-Apps mit UID 1000 und 1001 (z. B. Google Play-Dienste), sind „problematisch“ und funktionieren möglicherweise nicht richtig, wenn sie durch AdGuard geleitet werden. Aus diesem Grund kann die folgende Warnung angezeigt werden, wenn Sie versuchen, alle Apps zu leiten oder zu filtern: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index a284393c4f4..6a89450213f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ Sie können auf das DNS-Schutzmodul zugreifen, indem Sie auf den Tab _Schutz_ (z :::tip -Die Funktionsweise des DNS-Schutzes ist anders als die normale Blockierung von Werbung und Trackern. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +Die Funktionsweise des DNS-Schutzes ist anders als die normale Blockierung von Werbung und Trackern. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 7acc8c2e8af..88b3b2abd02 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ Um eine Regel oder App aus _Benutzerdefinierte Regeln_ zu löschen, wischen Sie ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index fbb1503ac7c..a3430fb4cde 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Hier sind die aktiven Funktionen der vorkonfigurierten Ebenen: k. _X-Client-Data-Header entfernen_. Diese Funktion verhindert, dass Google Chrome seine Versions- und Änderungsinformationen an Google-Domains (einschließlich DoubleClick und Google Analytics) sendet -Sie können die einzelnen Einstellungen unter _Tracking-Schutz_ anpassen und eine individuelle Konfiguration erstellen. Zu jeder Einstellung gibt es eine Beschreibung, die Ihnen hilft, ihre Bedeutung zu verstehen. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +Sie können die einzelnen Einstellungen unter _Tracking-Schutz_ anpassen und eine individuelle Konfiguration erstellen. Zu jeder Einstellung gibt es eine Beschreibung, die Ihnen hilft, ihre Bedeutung zu verstehen. [Erfahren Sie mehr über die Auswirkungen der verschiedenen _Tracking-Schutz_-Einstellungen](/general/stealth-mode) und gehen Sie vorsichtig damit um, da einige die Funktionalität von Websites und Browsererweiterungen beeinträchtigen können. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index cd8773c7ffd..7fbabd07fdb 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc Aufgrund der Sicherheitsmaßnahmen des Android-Betriebssystems sind einige AdGuard-Funktionen nur auf gerooteten Geräten verfügbar. Hier ist eine Liste von ihnen: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS-Filterung in den meisten Apps** erfordert [Installation eines CA-Zertifikats im Systemspeicher](/adguard-for-android/features/settings#security-certificates), da die meisten Apps den Zertifikaten im Benutzerspeicher nicht vertrauen. Die Installation eines Zertifikats in den Systemspeicher ist nur auf gerooteten Geräten möglich - Der [**Automatische Proxy**-Routing-Modus](/adguard-for-android/features/settings#routing-mode) erfordert Root-Zugriff aufgrund der Einschränkungen von Android bei der systemweiten Datenverkehrsfilterung - Der [**Manuelle Proxy**-Routing-Modus](/adguard-for-android/features/settings#routing-mode) erfordert unter Android 10 und höher Root-Zugriff, da es nicht mehr möglich ist, den Namen der App zu ermitteln, die mit einer von AdGuard gefilterten Verbindung verbunden ist diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 22a9ed38d17..2c84309dc01 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -27,7 +27,7 @@ Mit _Automatisierung_ können Sie AdGuard über Tasker-Apps verwalten. _Watchdog_ hilft, AdGuard davor zu schützen, vom System deaktiviert zu werden. [Lesen Sie mehr über den Batteriesparmodus von Android](/adguard-for-android/solving-problems/background-work/). Der von Ihnen eingegebene Wert ist das Intervall in Sekunden zwischen den Watchdog-Prüfungen. -Die _Protokollierungsebene_ legt fest, welche Daten über die Funktion der App protokolliert werden sollen. Standardmäßig sammelt die App die Daten über ihre Ereignisse. Die Ebene _Fehlersuche_ protokolliert mehr Ereignisse. Aktivieren Sie sie, wenn das AdGuard-Team sie darum bittet, um ein besseres Verständnis des Problems zu erhalten. [Read more about collecting and sending logs](/adguard-for-android/solving-problems/log/) +Die _Protokollierungsebene_ legt fest, welche Daten über die Funktion der App protokolliert werden sollen. Standardmäßig sammelt die App die Daten über ihre Ereignisse. Die Ebene _Fehlersuche_ protokolliert mehr Ereignisse. Aktivieren Sie sie, wenn das AdGuard-Team sie darum bittet, um ein besseres Verständnis des Problems zu erhalten. [Erfahren Sie mehr über das Sammeln und Senden von Protokollen](/adguard-for-android/solving-problems/log/) ![Erweitert \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) @@ -59,7 +59,7 @@ Wenn Sie zu viele Filter aktivieren, kann es sein, dass einige Websites nicht ri ### Benutzerskripte -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. Um ein Benutzerskript zu installieren, benötigen Sie einen speziellen Benutzerskript-Manager. AdGuard verfügt über eine solche Funktion und ermöglicht das Hinzufügen von Benutzerskripten per URL oder aus einer Datei. +Benutzerskripte sind in JavaScript geschriebene Miniprogramme, die die Funktionalität einer oder mehrerer Websites erweitern. Um ein Benutzerskript zu installieren, benötigen Sie einen speziellen Benutzerskript-Manager. AdGuard verfügt über eine solche Funktion und ermöglicht das Hinzufügen von Benutzerskripten per URL oder aus einer Datei. ![Benutzerskripte \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In diesem Abschnitt finden Sie Informationen über Ihre Lizenz und können sie v - Eine AdGuard-Lizenz kaufen, um [die Funktionen der Vollversion](/adguard-for-android/features/free-vs-full) zu aktivieren - Sich bei Ihrem AdGuard-Konto anmelden oder den Lizenzschlüssel eingeben, um Ihre Lizenz zu aktivieren - Sich anmelden, um Ihren 7-tägigen Testzeitraum zu aktivieren, falls Sie ihn noch nicht genutzt haben -- Refresh the license status from the three-dots menu (⋮) +- Den Lizenzstatus über das Menü mit den drei Punkten (⋮) aktualisieren - Das AdGuard-Konto öffnen und Ihre Lizenz dort verwalten - Ihre Lizenz zurücksetzen — zum Beispiel, wenn Sie das Gerätelimit für diese Lizenz erreicht haben und eine andere Lizenz beantragen möchten diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index fc85796cc07..88838e6edff 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index cf63020e570..46ec096a036 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Fertig! You have successfully set up AdGuard to work in the background. Damit Ihre AdGuard-App erfolgreich im Hintergrund läuft, gehen Sie wie folgt vor: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Einstellungen *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 6e36a3b9835..863b143fbe3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 88594fff76f..cd95a0af4f9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -18,7 +18,7 @@ If you are using AdGuard in the *Local VPN* filtering mode, you cannot run other - Switch to the *Automatic proxy* mode. Wenn Sie dies tun, wird AdGuard kein lokales VPN mehr verwenden und stattdessen „iptables“ neu konfigurieren - Switch to the *Manual proxy* mode. To do this, go to *Settings* → *Filtering* → *Network* → *Routing mode* -:::note Kompatibilität +:::note Compatibility The *Automatic proxy* mode is only accessible on rooted devices. For *Manual proxy*, rooting is required on devices running on Android 10 or later. @@ -36,11 +36,11 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) -:::note Kompatibilität +:::note Compatibility Requires root access. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index f43c8dceb07..df16ca72239 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR-Dateien werden in Übereinstimmung mit der [Datenschutzrichtlinie von AdGuar ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index 08b97fc9033..2a99b056887 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index bd7763601b2..f58f38dda1b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -19,13 +19,13 @@ In this article, we'll guide you through the process of collecting debug logs, a :::note -AdGuard ist dem Schutz Ihrer Privatsphäre verpflichtet. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Bevor Sie Ihre Protokolle an das Support-Team senden, überprüfen Sie bitte die Datei, da sie zusätzliche Informationen enthalten kann, die Sie vielleicht nicht freigeben möchten. Wenn sie solche persönlichen Informationen enthält, empfehlen wir Ihnen, sie zuerst zu löschen. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index adedb852b71..97270c38b7f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -15,11 +15,11 @@ Die in den Protokollen enthaltenen Daten und/oder Dateien werden in Übereinstim ::: -Manchmal reicht ein einfaches Protokoll nicht aus, um die Ursache des Problems zu ermitteln. In solchen Fällen ist ein Systemprotokoll erforderlich. Below are instructions on how to collect and get it: via Developer options and Logcat. +Manchmal reicht ein einfaches Protokoll nicht aus, um die Ursache des Problems zu ermitteln. In solchen Fällen ist ein Systemprotokoll erforderlich. Nachfolgend finden Sie eine Anleitung zum Zusammenstellen und Abrufen der Daten: über die Entwickleroptionen und Logcat. :::note -AdGuard ist dem Schutz Ihrer Privatsphäre verpflichtet. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Bevor Sie Ihre Protokolle an das Support-Team senden, überprüfen Sie bitte die Datei, da sie zusätzliche Informationen enthalten kann, die Sie vielleicht nicht freigeben möchten. Wenn sie solche persönlichen Informationen enthält, empfehlen wir Ihnen, sie zuerst zu löschen. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index ffa13edaeb1..c9275c399b3 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Jede verschlüsselte Internetverbindung hat einen unverschlüsselten Teil. Dies ist das allererste Paket, das den Namen des Servers enthält, mit dem Sie sich verbinden. Die verschlüsselte Client-Hallo-Technologie soll dieses Problem lösen und das letzte bisschen an unverschlüsselter Information verschlüsseln. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Jede verschlüsselte Internetverbindung hat einen unverschlüsselten Teil. Dies ist das allererste Paket, das den Namen des Servers enthält, mit dem Sie sich verbinden. Die verschlüsselte Client-Hallo-Technologie soll dieses Problem lösen und das letzte bisschen an unverschlüsselter Information verschlüsseln. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. Wenn es gefunden wird, wird das ClientHello-Paket verschlüsselt. #### OCSP checking @@ -127,7 +127,7 @@ If the verification takes too long, AdGuard will allow the connection while cont If this setting is enabled, AdGuard will redirect DNS-over-HTTPS requests to the local DNS proxy in addition to plain DNS requests. We recommend disabling fallback upstreams and using only encrypted DNS servers to maintain privacy. -#### HTTP/3 filtern +#### Filter HTTP/3 If this setting is enabled, AdGuard will filter requests sent over HTTP/3 in addition to other request types. @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index c8463f1dd48..23767ec7afa 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index 65911f722f8..6a426be2c96 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ Dieser Artikel behandelt AdGuard für Android, einem multifunktionalen Werbebloc ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index d38528146f2..df842415249 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -118,7 +118,7 @@ Or you can configure remove parameters manually: `[trust]` applies for **HTTPS_CONNECT** server type only and include option **Trust any certificates**. It is necessary to set **true or false** value. -:::note Beispiel +:::note Example `setting by name`: server:MyServer @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/compatibility-with-adguard-vpn.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/compatibility-with-adguard-vpn.md index ab5d009b211..1ae48907756 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/compatibility-with-adguard-vpn.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/compatibility-with-adguard-vpn.md @@ -15,9 +15,9 @@ Dennoch ist es uns gelungen, eine Lösung zu finden, um [AdGuard VPN](https://ad Im Abschnitt _Schutz_ können Sie ganz einfach zwischen zwei Apps wechseln. -### So aktivieren Sie den Kompatibilitätsmodus +### How to enable compatibility mode -**Wenn Sie bei der Installation von AdGuard VPN bereits über AdGuard Werbeblocker verfügen, wird dieser Modus automatisch aktiviert und ermöglicht Ihnen die gleichzeitige Nutzung unserer Apps.** +**If you already have AdGuard Ad Blocker when installing AdGuard VPN, integrated (compatibility) mode will turn on automatically, allowing you to use our apps at the same time.** Wenn Sie zuerst AdGuard VPN installiert haben und sich erst dann für AdGuard Werbeblocker entschieden haben, befolgen Sie diese Schritte, um die beiden Apps zusammen zu verwenden: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 4e71462969a..00000000000 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Kostenlose Version vs. Vollversion -sidebar_position: 9 ---- - -:::info - -Dieser Artikel behandelt AdGuard für iOS, einem multifunktionalen Werbeblocker, der Ihr Gerät auf Systemebene schützt. Um zu sehen, wie es funktioniert, [laden Sie die AdGuard-App herunter](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index df96ca23e4b..b917de3d5bc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -13,15 +13,15 @@ Dieser Artikel behandelt AdGuard für iOS, einem multifunktionalen Werbeblocker, ### iPhone -Erfordert iOS 13 oder höher. +Requires iOS 13 or later. ### iPad -Erfordert iPadOS 13 oder höher. +Requires iPadOS 13 or later. ### iPod touch -Erfordert iOS 13 oder höher. +Requires iOS 13 or later. ## Installation von AdGuard für iOS @@ -29,7 +29,7 @@ AdGuard für iOS ist im App Store erhältlich. Um sie auf Ihrem Gerät zu instal ![Tippen Sie auf dem Hauptbildschirm des App Store auf Suchen *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Geben Sie *adguard* in die Suchleiste ein und tippen Sie auf die Zeichenfolge *AdGuard*, die sich unter den Suchergebnissen befinden wird. +Geben Sie *adguard* in die Suchleiste ein und tippen Sie auf die Zeichenfolge *adguard*, die sich unter den Suchergebnissen befinden wird. ![Geben Sie "AdGuard" in die Suchleiste ein *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -47,7 +47,7 @@ Geben Sie *adguard* in das Suchformular ein, und tippen Sie dann auf die Zeichen ![Geben Sie "AdGuard" in die Suchleiste ein *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -Tippen Sie auf der geöffneten Seite des App Stores auf die Schaltfläche mit den Kosten für die Lizenz unter der Zeichenfolge *AdGuard Pro — adblock*, und tippen Sie dann auf *KAUFEN*. Möglicherweise werden Sie aufgefordert, Ihre Apple-ID-Anmeldenamen und Passwort einzugeben. Geben Sie sie ein und warten Sie, bis die Installation abgeschlossen ist. +Tippen Sie auf der geöffneten Seite des App Stores auf die Schaltfläche mit den Lizenzkosten unter der Zeichenfolge *AdGuard Pro — adblock* und tippen Sie dann auf *Kaufen*. Möglicherweise werden Sie aufgefordert, Ihre Apple-ID-Anmeldenamen und Passwort einzugeben. Geben Sie sie ein und warten Sie, bis die Installation abgeschlossen ist. ![Tippen Sie auf GET unterhalb der AdGuard-App *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index aede0acb89a..5a403ef3010 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ Dieser Artikel behandelt AdGuard für iOS, einem multifunktionalen Werbeblocker, 1. Wählen Sie ein Video aus und tippen Sie auf *Teilen*. 1. Tippen Sie auf *Mehr* und wählen Sie dann *YouTube-Werbung blockieren (von AdGuard)*. -Das Video wird nun im werbefreien Player von AdGuard geöffnet. +AdGuard wird seinen werbefreien Videoplayer öffnen. ## So blockieren Sie YouTube-Werbung in Safari @@ -31,4 +31,4 @@ Vergewissern Sie sich, dass Sie AdGuard Zugriff auf alle Websites gewährt haben 1. Wählen Sie ein Video aus und tippen Sie auf *Teilen*. 1. Tippen Sie auf *YouTube-Werbung blockieren (von AdGuard)*. -Das Video wird nun im werbefreien Player von AdGuard geöffnet. +AdGuard wird seinen werbefreien Videoplayer öffnen. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index bb18c8e40dd..267ccf3bd52 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ Um die *Low-Level-Einstellungen* aufzurufen, tippen Sie auf das Zahnradsymbol un Es gibt zwei Haupttypen von Tunneln: *Split-Tunnel* und *Full-Tunnel*. Der *Split-Tunnel*-Modus sorgt für Kompatibilität von AdGuard und sogenannten „Personal VPN” Apps. Im *Full-Tunnel*-Modus kann kein anderes VPN gleichzeitig mit AdGuard zusammenarbeiten. -Es gibt eine Besonderheit des *Split-Tunnel*-Modus: Bei schlechter DNS-Proxy-Leistung, zum Beispiel wenn die Antwort vom AdGuard-DNS-Server nicht rechtzeitig zurückkommt, leitet iOS den Datenverkehr stattdessen über den in den iOS-Einstellungen angegebenen DNS-Server um. Während dieser Zeit wird keine Werbung blockiert und der DNS-Verkehr nicht verschlüsselt. +Es gibt eine Besonderheit des *Split-Tunnel*-Modus: Wenn der DNS-Proxy nicht gut funktioniert, z. B. wenn die Antwort vom AdGuard-DNS-Server nicht rechtzeitig zurückkommt, wird iOS ihn „umgehen” und den Datenverkehr über den DNS-Server umleiten, der in den iOS-Einstellungen angegeben ist. Während dieser Zeit wird keine Werbung blockiert und der DNS-Verkehr nicht verschlüsselt. -Im *Full-Tunnel*-Modus wird nur der in den AdGuard-Einstellungen angegebene DNS-Server verwendet. Wenn der Server nicht reagiert, funktioniert das Internet einfach nicht. Der aktivierte *Full-Tunnel*-Modus kann die Leistung einiger Programme (z. B. FaceTime) beeinträchtigen und Probleme bei der Aktualisierung von Apps verursachen. +Im *Full-Tunnel*-Modus wird nur der in den AdGuard-Einstellungen angegebene DNS-Server verwendet. Wenn der Server nicht reagiert, funktioniert das Internet einfach nicht. Der aktivierte *Full-Tunnel*-Modus kann die Leistung einiger Programme (z. B. Facetime) beeinträchtigen und zu Problemen bei App-Updates führen. Standardmäßig verwendet AdGuard den Modus *Split-Tunnel* als stabilste Option. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md index 14117288616..8511eede3d0 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md @@ -99,7 +99,7 @@ Gehen Sie zum Abschnitt Anwendungen. Suchen Sie dort AdGuard, klicken Sie mit de ![Starten Sie die Anwendung „Activity Monitor“](https://cdn.adtidy.org/content/kb/ad_blocker/mac/22.jpg) -1. Stoppen Sie den Prozess, der unter dem Benutzer ausgeführt wird (nicht den, der unter Root ausgeführt wird). Klicken Sie dazu auf den Prozess und dann oben links auf X. Bestätigen Sie die Aktion im Dialogfenster. +1. Stoppen Sie den Prozess, der unter dem Benutzer ausgeführt wird (nicht den, der unter Root ausgeführt wird). Klicken Sie dazu auf den Prozess und dann oben links auf X. Confirm the action in the dialogue window. ![Bestätigen](https://cdn.adtidy.org/content/kb/ad_blocker/mac/33.jpg) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index e5823af1af4..cd88bd65235 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -13,27 +13,27 @@ Dieser Artikel behandelt AdGuard für Mac, einem multifunktionalen Werbeblocker, :::caution -Das Ändern der *Erweiterten Einstellungen* kann zu Problemen mit der Leistung von AdGuard führen, die Internetverbindung unterbrechen oder Ihre Sicherheit und Privatsphäre gefährden. Nehmen Sie Änderungen in diesem Bereich nur dann vor, wenn Sie sicher sind, was Sie tun, oder wenn unser Support-Team Sie darum gebeten hat. +Changing *Advanced Settings* may cause problems with AdGuard's performance, break the Internet connection, or compromise your security and privacy. Make changes to this section only if you are sure of what you are doing or our support team has asked you to do it. ::: -Um die *Erweiterte Einstellungen*zu finden, öffnen Sie AdGuard, klicken Sie auf das Zahnradsymbol, wählen Sie *Erweitert*und dann *Erweiterte Einstellungen*. +To find *Advanced Settings*, open AdGuard, click the gear icon, select *Advanced*, then select *Advanced Settings*. ## Erweiterte Einstellungen -### Netzwerkeinstellungen +### Network settings #### `network.extension.exclude.domains` -Die aufgelisteten Domains werden von der Filterung im Modus *Netzwerk-Erweiterung* ausgeschlossen. Verwenden Sie ein Komma oder einen Zeilenumbruch, um Werte zu trennen. +The listed domains will be excluded from filtering in the *Network Extension* mode. Verwenden Sie ein Komma oder einen Zeilenumbruch, um Werte zu trennen. #### `network.extension.exclude.ports` -Die aufgeführten Ports werden von der Filterung im Modus *Netzwerk-Erweiterung* ausgeschlossen. Verwenden Sie ein Komma oder einen Zeilenumbruch, um Werte zu trennen. +The listed ports will be excluded from filtering in the *Network Extension* mode. Verwenden Sie ein Komma oder einen Zeilenumbruch, um Werte zu trennen. #### `network.extension.route.exclude` -Die aufgelisteten Routen werden von der Filterung im Modus *Netzwerk-Erweiterung* ausgeschlossen. Legen Sie Routen mit einer IP-Adresse oder einem Ziel-CIDR fest. Trennen Sie die Werte durch Kommas oder Zeilenumbrüche. +The listed routes will be excluded from filtering in the *Network Extension* mode. Legen Sie Routen mit einer IP-Adresse oder einem Ziel-CIDR fest. Trennen Sie die Werte durch Kommas oder Zeilenumbrüche. #### `network.extension.http.downgrade.bundleids` @@ -41,7 +41,7 @@ Hier können Sie eine Liste von Anwendungen angeben, für die das HTTP/2-Protoko #### `network.extension.monterey.force.split.tunnel` -Hier können Sie AdGuard verbieten, die „Standardroute“ zu verwenden, die im Modus *Netzwerk-Erweiterung* unter macOS Monterey standardmäßig aktiviert ist. AdGuard verwendet die „Standardroute“, um iCloud Privat-Relay und E-Mail-Datenschutz zu deaktivieren, da sie nicht mit ihnen zusammenarbeiten können. +Here you can prohibit AdGuard from using the "default route" which is enabled by default in the *Network Extension* mode on macOS Monterey. AdGuard uses "default route" to disable iCloud Private Relay and Protect Mail Activity, as it cannot operate in unison with them. Weitere Informationen zum Problem finden Sie in [diesem Artikel](../icloud-private-relay). @@ -51,7 +51,7 @@ Hier können Sie eine Liste von Anwendungen angeben, die DNS-Abfragen direkt und #### `network.dns.filter.secure.request` -Leitet sichere DNS-Anfragen an einen lokalen DNS-Proxy um, sofern ein solcher vorhanden ist. +Redirects secure DNS requests to a local DNS proxy, if there is one available. #### `network.https.ocsp.check` @@ -59,19 +59,19 @@ Indem Sie `true` festlegen, aktivieren Sie die Sperrprüfung von HTTPS-Zertifika #### `network.tcp.keepalive.enabled` -Sendet in regelmäßigen Abständen TCP-Pakete über eine inaktive Verbindung, um sicherzustellen, dass diese aktiv bleibt und um NAT-Zeitüberschreitungen zu erneuern. +Periodically sends TCP packets over an idle connection to ensure that it remains active and to renew NAT timeouts. #### `network.tcp.keepalive.interval.seconds` -Leerlaufzeit (in Sekunden), bevor eine Keepalive-Anfrage gesendet wird. Wenn 0 (Null) angegeben wird, verwendet das System den Standardwert. +Idle time, in seconds, before sending a keepalive probe. If 0 is specified, the system will use the default value. #### `network.tcp.keepalive.timeout.seconds` -Zeit (in Sekunden), bevor eine weitere Keepalive-Anfrage an eine nicht reagierende Gegenstelle gesendet wird. Wird 0 (Null) angegeben, wird der vom System gewählte Wert verwendet. +Time, in seconds, before sending another keepalive probe to an unresponsive peer. Wird 0 (Null) angegeben, wird der vom System gewählte Wert verwendet. #### `network.https.ech.enabled` -Verwendet einen lokalen DNS-Proxy für die Suche nach Konfigurationen in den ECH-Konfigurationslisten. Falls gefunden, verschlüsselt Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` @@ -79,7 +79,7 @@ Verwendet einen lokalen DNS-Proxy für die Suche nach Konfigurationen in den ECH #### `network.https.filter.http3.enabled` -Mit der Einstellung `true` erlauben Sie AdGuard, Datenverkehr zu filtern, der über HTTP/3, die neueste Version des auf QUIC-basierenden HTTP-Protokolls, gesendet wird. +By setting `true`, you allow AdGuard to filter traffic sent over HTTP/3, the latest version of the HTTP protocol based on QUIC. #### `network.filtering.localnetwork` @@ -89,7 +89,7 @@ Indem Sie `true` setzen, aktivieren Sie die lokale Netzwerkfilterung. Wenn Sie `true` setzen, aktivieren Sie die LoopBack-Filterung. -### DNS-Einstellungen +### DNS settings #### `dns.proxy.bootstrap.ips` @@ -101,7 +101,7 @@ Hier können Sie eine Liste mit IP-Adressen von DNS-Servern angeben, die als Bac #### `dns.proxy.fallback.on.upstreams.failure.enabled` -Normale Abfragen werden an einen Fallback-Upstream weitergeleitet, wenn alle normalen Upstreams ausfallen. +Normal queries will be redirected to a fallback upstream if all normal upstreams fail. #### `dns.proxy.detect.search.domains` @@ -115,17 +115,17 @@ Hier können Sie Domains auflisten, für die der Fallback-DNS-Server anstelle de Hier können Sie die Art der Antwort des DNS-Servers auf blockierte Anfragen festlegen, die den Regeln im Stil von Werbeblockern entsprechen. -- 0 — mit REFUSED antworten -- 1 — mit NXDOMAIN antworten -- 2 — mit 0.0.0.0 oder den in `dns.proxy.blocking.response.IPv4.address` und/oder `dns.proxy.blocking.response.IPv6.address` angegebenen Adressen antworten +- 0 — respond with REFUSED +- 1 — respond with NXDOMAIN +- 2 — respond with 0.0.0.0 or the addresses specified in `dns.proxy.blocking.response.IPv4.address` and/or `dns.proxy.blocking.response.IPv6.address` #### `dns.proxy.hostrules.blocking.mode` Hier können Sie die Art der Antwort des DNS-Servers auf blockierte Anfragen entsprechend den Hosts-Regeln festlegen: -- 0 — mit REFUSED antworten -- 1 — mit NXDOMAIN antworten -- 2 — mit 0.0.0.0 oder den in `dns.proxy.blocking.response.IPv4.address` und/oder `dns.proxy.blocking.response.IPv6.address` angegebenen Adressen antworten +- 0 — respond with REFUSED +- 1 — respond with NXDOMAIN +- 2 — respond with 0.0.0.0 or the addresses specified in `dns.proxy.blocking.response.IPv4.address` and/or `dns.proxy.blocking.response.IPv6.address` #### `dns.proxy.blocking.response.IPv4.address` @@ -145,39 +145,39 @@ Hier können Sie den TTL-Wert (Time to Live) angeben, der als Antwort auf eine b #### `dns.proxy.parallel.upstream.queries.enabled` -Alle Upstreams werden gleichzeitig abgefragt. Die erste Antwort wird zurückgegeben. +All upstreams are queried simultaneously. The first response is returned. #### `dns.proxy.servfail.on.upstreams.failure.enabled` -Reagiert auf einen Upstream-Fehler mit einem SERVFAIL-Paket. +Responds to upstream failure with a SERVFAIL packet. #### `dns.proxy.http3.enabled` -Aktiviert HTTP/3 für DNS-over-HTTPS-Upstreams, um die Verbindung zu beschleunigen. +Enables HTTP/3 for DNS-over-HTTPS upstreams to accelerate connection. #### `dns.proxy.block.encrypted.client.hello.response` -Entfernt die „Encrypted Client Hello“-Parameter aus den Antworten. +Removes the Encrypted Client Hello parameters from responses. -### Privatsphäre-Einstellungen +### Stealth Mode settings #### `stealth.antidpi.http.split.fragment.size` -Passt die Größe der Fragmentierung der HTTP-Anfrage an. Gültige Werte: 1–1500. Wenn eine ungültige Größe angegeben wird, verwendet das System den Standardwert. +Passt die Größe der Fragmentierung der HTTP-Anfrage an. Valid values: 1–1500. If an invalid size is specified, the system will use the default value. #### `stealth.antidpi.clienthello.split.fragment.size` -Diese Option gibt die Größe der TCP-Paketfragmentierung an, die dazu beiträgt, Deep Packet Inspection zu vermeiden. Gültige Werte: 1–1500. Wenn eine ungültige Größe angegeben wird, verwendet das System den Standardwert. +This option specifies the size of TCP packet fragmentation, which helps avoid deep packet inspection. Valid values: 1–1500. If an invalid size is specified, the system will use the default value. #### `stealth.antidpi.http.space.juggling` -Fügt ein zusätzliches Leerzeichen zwischen der HTTP-Methode und der URL ein und entfernt das Leerzeichen nach dem Feld „Host:“. +Adds extra space between the HTTP method and the URL and removes space after the "Host:" field. #### `stealth.antidpi.split.delay.millisecond` -Hier können Sie die Verzögerung in Millisekunden angeben, nachdem das erste Fragment gesendet wurde, wenn eine Fragmentierung durchgeführt wird. +Here you can specify the delay, in milliseconds, after sending the first fragment, if fragmentation is performed. -### Einstellungen für das Abfangen von Abonnement-Links (Benutzerskripte und Filter) +### Subscription link interception settings (userscripts and filters) #### `subscription.link.interception.userscript` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index dfefbbd5860..a8bb66a4efe 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -11,15 +11,15 @@ Dieser Artikel behandelt AdGuard für Mac, einem multifunktionalen Werbeblocker, ## Aktuell bestehende Probleme -Jedes Jahr veröffentlicht Apple eine neue Version von macOS, die innovative Lösungen einführt und neue nützliche Funktionen hinzufügt. Einige von ihnen, wie Netzwerk-Erweiterungs API (Big Sur) oder iCloud Privat-Relay (Monterey), verursachen jedoch einige Probleme für viele Anwendungen, wobei AdGuard keine Ausnahme bildet. In diesem Artikel betrachten wir die bekannten Probleme, die für jede macOS-Version spezifisch sind, und auch die möglichen Lösungen. +Jedes Jahr veröffentlicht Apple eine neue Version von macOS, die innovative Lösungen einführt und neue nützliche Funktionen hinzufügt. Einige von ihnen, wie Netzwerk-Erweiterungs API (Big Sur) oder iCloud Private Relay (Monterey), verursachen jedoch einige Probleme für viele Anwendungen, wobei AdGuard keine Ausnahme bildet. In diesem Artikel betrachten wir die bekannten Probleme, die für jede macOS-Version spezifisch sind, und auch die möglichen Lösungen. ### Monterey 12: derzeit bestehende Probleme Diese Probleme wurden von Apple noch nicht oder nur teilweise behoben. -#### Kompatibilität mit iCloud Privat-Relay +#### Kompatibilität mit iCloud Private Relay -Derzeit können AdGuard und iCloud Privat-Relay nicht gleichzeitig funktionieren. AdGuard kann keine Werbung blockieren, da iCloud Privat-Relay den Datenverkehr verschlüsselt, bevor AdGuard Netzwerkverbindungen filtern kann. Wenn iCloud Privat-Relay aktiv ist, wird jegliche Filterung (einschließlich lokaler Filterung) unmöglich. Daher kann AdGuard in Safari keinen Datenverkehr filtern oder eine DNS-Filterung durchführen. Aus diesem Grund verwendet AdGuard standardmäßig die „Standardroute“, die iCloud Privat-Relay deaktiviert. +Derzeit können AdGuard und iCloud Private Relay nicht gleichzeitig funktionieren. AdGuard kann keine Werbung blockieren, da iCloud Private Relay den Datenverkehr verschlüsselt, bevor AdGuard Netzwerkverbindungen filtern kann. Wenn iCloud Private Relay aktiv ist, wird jegliche Filterung (einschließlich lokaler Filterung) unmöglich. Daher kann AdGuard in Safari keinen Datenverkehr filtern oder eine DNS-Filterung durchführen. Aus diesem Grund verwendet AdGuard standardmäßig die „Standardroute“, die iCloud Private Relay deaktiviert. Für ein tieferes Verständnis dieses Problems lesen Sie bitte [diesen Artikel](../icloud-private-relay). @@ -41,7 +41,7 @@ Für ein tieferes Verständnis dieses Problems lesen Sie bitte [diesen Artikel]( **Empfohlene Lösung** -An dieser Stelle empfehlen wir die Verwendung eines herkömmlichen VPN-Dienstes, wie [AdGuard VPN](https://adguard-vpn.com/), anstelle der neueren Apple-Datenschutzfunktionen. +At this point, we recommend using a more traditional VPN service, such as [AdGuard VPN](https://adguard-vpn.com/), instead of the newer Apple privacy features. ### Monterey 12, Big Sur 11.6 und höher: derzeit bestehende Probleme @@ -59,16 +59,16 @@ Wenn Sie Flutter zusammen mit AdGuard im Modus „Network Extension“ (oder ein 1. Verwenden Sie AdGuard im Modus [Automatischer Proxy](#automatic-proxy). -1. Deaktivieren Sie SIP und schalten Sie AdGuard in den Kernel-Erweiterungsmodus, wie [hier](#kernel-extension) erklärt. +1. Deaktivieren Sie SIP und schalten Sie AdGuard in den Kernel Extension Modus, wie [hier](#kernel-extension) erklärt. #### VPN-Apps mit Legacy-API -Obwohl AdGuard in den Systemeinstellungen als VPN angezeigt wird, sollte es keine Konflikte verursachen, wenn es mit anderen VPN-basierten Apps zusammenarbeitet. Wird jedoch eine VPN-basierte App verwendet, die außerhalb des App Stores heruntergeladen wurde, besteht das Risiko, dass sie die alte VPN-API verwendet und von der Filterung ausgeschlossen werden muss: +Obwohl AdGuard in den Systemeinstellungen als VPN angezeigt wird, sollte es keine Konflikte verursachen, wenn es mit anderen VPN-basierten Apps zusammenarbeitet. Wenn Sie jedoch eine VPN-basierte App verwenden, die von außerhalb des App Store heruntergeladen wurde, besteht die Möglichkeit, dass sie die alte VPN-API verwendet, und Sie müssen sie von der Filterung ausschließen: 1. Öffnen Sie das AdGuard-Menü. 1. Wählen Sie *Einstellungen…*. 1. Wechseln Sie zum Tab *Netzwerk*. -1. Klicken Sie auf die Schaltfläche *Anwendungen…* +1. Click the *Applications...* button. 1. Suchen Sie die App, die Sie ausschließen möchten, und deaktivieren Sie das Kontrollkästchen neben der App. ![Gefilterte Apps](https://cdn.adtidy.org/content/kb/ad_blocker/mac/legacy.jpg) @@ -79,9 +79,9 @@ Diese Probleme wurden inzwischen von Apple behoben, können aber noch in ältere ### Kompatibilität mit Little Snitch 5 -Derzeit ist der Modus Network Extension in AdGuard nicht mit [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html) kompatibel. Wenn beide ausgeführt werden, besteht die Gefahr, dass es zu Problemen mit dem Verhalten verschiedener Anwendungen kommt, selbst wenn diese nicht von AdGuard gefiltert werden. Dieses Problem wird direkt durch einen Fehler in Big Sur verursacht, und Apple wurde von uns bereits darüber informiert. Dies lässt vermuten, dass dieses Problem in einem der nächsten Aktualisierungen behoben werden wird. +Derzeit ist der Modus Network Extension in AdGuard nicht mit [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html) kompatibel. Wenn beide laufen, kann es zu Problemen mit dem Verhalten verschiedener Apps kommen, auch wenn sie nicht von AdGuard gefiltert werden. Dieses Problem wird direkt durch einen Fehler in Big Sur verursacht, und Apple wurde von uns bereits darüber informiert. Dies lässt vermuten, dass dieses Problem in einem der nächsten Aktualisierungen behoben werden wird. -Das Deaktivieren der Verbindungsüberwachung in Little Snitch löst das Problem jedoch nicht, da dadurch die Little Snitch-Erweiterung nicht aus dem Systemspeicher entfernt wird. Wir empfehlen, in den [**Automatischen Proxy**](#automatic-proxy)-Filtermodus zu wechseln, wenn Sie AdGuard zusammen mit Little Snitch auf Big Sur betreiben, zumindest bis Apple den Fehler behebt. +Es muss gesagt werden, dass dieses Problem nicht durch die Deaktivierung der Verbindungsüberwachung in Little Snitch gelöst werden kann, da diese Aktion die Erweiterung von Little Snitch nicht aus dem System entlädt. Wir empfehlen, in den [**Automatischen Proxy**](#automatic-proxy)-Filtermodus zu wechseln, wenn Sie AdGuard zusammen mit Little Snitch auf Big Sur betreiben, zumindest bis Apple den Fehler behebt. ### Kompatibilität mit lokalen Proxys @@ -93,7 +93,7 @@ Jetzt kann AdGuard lokale Proxys (meistens) problemlos filtern. Wenn Sie in den So konfigurieren Sie einen Upstream-Proxy in AdGuard für Mac in Big Sur: -1. Öffnen Sie *Einstellungen → Netzwerk → Ausgehender Proxy*. +1. Open AdGuard's settings *Preferences → Network → Outbound proxy*. 2. Wählen Sie HTTP, HTTPS, SOCKS4 oder SOCKS5, je nach Proxy-Typ. 3. Füllen Sie die Felder aus: - `host` ist die IP-Adresse Ihres Proxy-Servers, @@ -121,7 +121,7 @@ Zunächst benötigen Sie eine funktionierende Serverseite für Ihren Proxy. Höc :::tip -Weitere Informationen über den Einstieg finden Sie auf der [Shadowsocks-Website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +Weitere Informationen zu den ersten Schritten finden Sie auf der [Shadowsocks-Website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: @@ -139,7 +139,7 @@ In Big Sur v11.1+ gibt es keine bekannten Konflikte zwischen AdGuard und dem Sur ![Konfigurieren eines vorgelagerten Surge-Proxys *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/outbound-proxy.png) -Wechseln Sie nun zu *Einstellungen → Netzwerk → Ausgehender Proxy* und füllen Sie die Felder aus. Für SOCKS5-Proxy-Typ: +Now go to *Preferences → Network → Outbound proxy* and fill in the fields. Für SOCKS5-Proxy-Typ: - `host`: localhost - `port`: 6153 Für HTTP-Proxy-Typ: @@ -157,22 +157,22 @@ Wenn Sie in Big Sur oder Monterey auf Probleme stoßen, die mit keiner der oben 1. Öffnen Sie das AdGuard-Menü. 1. Wählen Sie *Einstellungen…*. 1. Wechseln Sie zum Tab *Netzwerk*. -1. Klicken Sie auf die Schaltfläche *Modus wechseln…*. -1. Wählen Sie *Automatischer Proxy* aus. +1. Click the *Select Mode...* button. +1. Select *Automatic Proxy*. ![AdGuard in den automatischen Proxy-Modus schalten](https://cdn.adtidy.org/content/kb/ad_blocker/mac/automatic-proxy_en.jpg) -Jetzt hat AdGuard automatisch eine **.pac** -Datei zu den Netzwerkeinstellungen Ihres Mac hinzugefügt, sodass das System AdGuard als Proxy betrachtet und versucht, den gesamten Datenverkehr über AdGuard zu senden. +Now AdGuard has automatically added a **.pac** file to your Mac's network settings, so that the system will consider AdGuard a proxy and try to send all traffic through AdGuard. :::note -Einige Apps können diese Systemeinstellung ignorieren und deren Datenverkehr wird nicht gefiltert. +Some apps may ignore this system setting and their traffic will not be filtered. ::: -### Aktivieren der Kernel-Erweiterung in Big Sur und Monterey {#kernel-extension} +### Aktivieren der Kernel Extension in Big Sur und Monterey {#kernel-extension} -Standardmäßig verwendet AdGuard das Network Extension-Framework in Big Sur und Monterey, da die alte Kernel-Erweiterung dort deaktiviert ist. Dies kann einige Kompatibilitätsprobleme verursachen, aber um die Kernel Extension wieder zu aktivieren, müssen Sie zuerst den Systemintegritätsschutz (SIP) deaktivieren. Um SIP zu deaktivieren, folgen Sie dieser Anleitung: +Standardmäßig verwendet AdGuard das Network Extension-Framework in Big Sur und Monterey, da die alte Kernel-Erweiterung dort deaktiviert ist. This can cause some compatibility problems, but to enable Kernel Extension back, you need to disable System Integrity Protection (SIP) first. Um SIP zu deaktivieren, folgen Sie dieser Anleitung: 1. Klicken Sie auf das *Apfelsymbol* in der Menüleiste. 1. Klicken Sie auf *Neustart…* @@ -186,14 +186,14 @@ Standardmäßig verwendet AdGuard das Network Extension-Framework in Big Sur und Nachdem SIP deaktiviert ist, aktivieren Sie die Kernel-Erweiterung folgendermaßen: -![Kernel-Erweiterung aktivieren](https://cdn.adtidy.org/content/kb/ad_blocker/mac/kernel_en.jpg) +![Kernel Extension aktivieren](https://cdn.adtidy.org/content/kb/ad_blocker/mac/kernel_en.jpg) 1. Öffnen Sie das AdGuard-Menü. 1. Wählen Sie *Einstellungen…*. 1. Wechseln Sie zum Tab *Netzwerk*. -1. Klicken Sie auf die Schaltfläche *Modus wechseln…*. -1. Wählen Sie *Kernel Extension* aus. -1. Bestätigen Sie, dass Sie zur Kernel-Erweiterung wechseln möchten. +1. Click the *Select Mode...* button. +1. Select *Kernel Extension*. +1. Confirm that you want to switch to Kernel Extension. :::caution diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index 1135a4573d7..e4cabeab86e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ Dieser Artikel behandelt AdGuard für Mac, einem multifunktionalen Werbeblocker, ::: -Bei der Installation von AdGuard unter macOS High Sierra (oder höher) kann es zu folgender Meldung kommen: „Systemerweiterung gesperrt“. Dies ist ein neuer Sicherheitsmechanismus, der in High Sierra aufgetaucht ist und erfordert, dass Sie die Installation einer Systemerweiterung eines Drittanbieters explizit zulassen. Um die Installation von AdGuard abzuschließen, müssen Sie das Laden der Erweiterung in *System Preferences* → *Security & Privacy* → *General* manuell zulassen. +Während der Installation von AdGuard auf macOS High Sierra (oder neueren Versionen) wird möglicherweise eine Meldung angezeigt: „System Extension Blocked“. Dies ist ein neuer Sicherheitsmechanismus, der in High Sierra aufgetaucht ist und erfordert, dass Sie die Installation einer Systemerweiterung eines Drittanbieters explizit zulassen. Um die Installation von AdGuard abzuschließen, müssen Sie das Laden der Erweiterung in *System Preferences* → *Security & Privacy* → *General* manuell zulassen. ![Erweiterungsinstallation in den Einstellungen zulassen](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md index 4344c533106..9d29b63dcff 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md @@ -1,5 +1,5 @@ --- -title: iCloud Privat-Relay und AdGuard +title: iCloud Private Relay und AdGuard sidebar_position: 7 --- @@ -11,11 +11,11 @@ Dieser Artikel behandelt AdGuard für Mac, einem multifunktionalen Werbeblocker, ## Problembeschreibung -Standardmäßig verwendet AdGuard die „Standardroute“, die iCloud Privat-Relay deaktiviert. +Standardmäßig verwendet AdGuard die „Standard-Route“, die iCloud Private Relay deaktiviert. -Derzeit können AdGuard und iCloud Privat-Relay nicht gleichzeitig funktionieren. AdGuard kann keine Anzeigen blockieren, da iCloud Privat-Relay den Datenverkehr verschlüsselt, bevor AdGuard Netzwerkverbindungen filtern kann. Wenn iCloud Privat-Relay aktiv ist, wird jegliche Filterung (einschließlich lokaler Filterung) unmöglich. Daher kann AdGuard in Safari keinen Datenverkehr filtern oder eine DNS-Filterung durchführen. Dennoch filtert AdGuard immer noch den Datenverkehr in anderen Browsern. Um iCloud Privat-Relay weiterhin zu verwenden, sollten Sie [AdGuard für Safari](https://adguard.com/adguard-safari/overview.html) installieren. +Derzeit können AdGuard und iCloud Private Relay nicht gleichzeitig funktionieren. AdGuard kann keine Anzeigen blockieren, da iCloud Private Relay den Datenverkehr verschlüsselt, bevor AdGuard Netzwerkverbindungen filtern kann. Wenn iCloud Private Relay aktiv ist, wird jegliche Filterung (einschließlich lokaler Filterung) unmöglich. Daher kann AdGuard in Safari keinen Datenverkehr filtern oder eine DNS-Filterung durchführen. Dennoch filtert AdGuard immer noch den Datenverkehr in anderen Browsern. Um iCloud Private Relay weiterhin zu verwenden, sollten Sie [AdGuard für Safari](https://adguard.com/adguard-safari/overview.html) installieren. -Das Gleiche gilt für die Verwendung von VPN-Apps auf dem Mac: Sie müssen sich entscheiden, ob Sie iCloud Privat-Relay oder einen VPN-Dienst verwenden. +Das Gleiche gilt für die Verwendung von VPN-Apps auf dem Mac: Sie müssen sich entscheiden, ob Sie iCloud Private Relay oder einen VPN-Dienst verwenden. ## Details @@ -23,15 +23,15 @@ AdGuard für Mac verwendet jetzt die in macOS integrierte Socket-Filterung basie Die Netzwerkerweiterungs-API hat eine VPN-ähnliche Konfiguration mit einer Liste routenähnlicher Einträge. Auf Big Sur hat AdGuard „Split-Tunnel“-Regeln entwickelt, um die Erstellung der „Default Route“-Regel zu vermeiden, da diese bei frühen Big Sur-Versionen Probleme verursacht. -Auf Monterey wurde iCloud Privat-Relay eingeführt. Datenschutzfunktionen der Mail-App verwenden auch Privat-Relay-Server. +Auf Monterey wurde iCloud Private Relay eingeführt. Datenschutzfunktionen der Mail-App verwenden auch private Relay-Server. -Infolgedessen kann AdGuard nicht mit iCloud Privat-Relay und den Datenschutzfunktionen der Mail-App zusammenarbeiten: +As a consequence, AdGuard can't work together with iCloud Private Relay and the Mail app privacy features: -1. iCloud Privat-Relay wird auf Verbindungen auf Bibliotheksebene angewendet – bevor sie die Socket-Ebene erreichen, auf der AdGuard arbeitet. -2. iCloud Privat-Relay verwendet QUIC, das AdGuard in gefilterten Apps nicht filtern kann, da die HTTP/3-Filterung noch nicht verfügbar ist. -3. Folglich sperrt AdGuard QUIC, einschließlich des iCloud Privat-Relay-Verkehrs — andernfalls ist das Sperren von Werbung unmöglich. -4. Wenn Sie iCloud Privat-Relay verwenden und AdGuard in den „Split-Tunnel“-Modus schalten, können Sie keine Websites in Safari öffnen. -5. Um dieses Problem für Monterey zu umgehen, wenden wir die Regel „Standard-Route“ an. Wenn Privat-Relay diese Regel sieht, deaktiviert es sich automatisch. AdGuard funktioniert also nahtlos auf Monterey, aber iCloud Privat-Relay wird deaktiviert. +1. iCloud Private Relay wird auf Verbindungen auf Bibliotheksebene angewendet – bevor sie die Socket-Ebene erreichen, auf der AdGuard arbeitet. +2. iCloud Private Relay verwendet QUIC, das AdGuard in gefilterten Apps nicht filtern kann, da die HTTP/3-Filterung noch nicht verfügbar ist. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic — otherwise, ad blocking is impossible. +4. Wenn Sie iCloud Private Relay verwenden und AdGuard in den „Split-Tunnel“-Modus schalten, können Sie keine Websites in Safari öffnen. +5. Um dieses Problem für Monterey zu umgehen, wenden wir die Regel „Standard-Route“ an. Wenn Private Relay diese Regel sieht, deaktiviert es sich automatisch. AdGuard funktioniert also nahtlos auf Monterey, aber iCloud Private Relay wird deaktiviert. `network.extension.monterey.force.split.tunnel` stellt das „Big Sur“-Verhalten wieder her, aber diese Option kann den Zugriff auf Websites aufgrund von (3) und (4) unterbrechen. Wir suchen weiter nach einer Lösung für dieses Problem. Eine der Optionen ist die Implementierung der HTTP/3-Filterung. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md index 36a1c493623..253d3e0f68a 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md @@ -13,16 +13,16 @@ AdGuard für Mac muss das Root-Zertifikat im Zertifikatspeicher installieren, um Um das Zertifikat manuell in einem Firefox-ähnlichen Browser zu installieren, machen Sie Folgendes: - 1. Öffnen Sie *Einstellungen* + 1. Open *Preferences* - 2. Wechseln Sie zu *Datenschutz und Sicherheit* ➜ *Zertifikate* + 2. Go to *Privacy & Security* → *Certificates* - 3. Klicken Sie auf *Zertifikate anzeigen* + 3. Click *View Certificates* - 4. Navigieren Sie zum Tab *Befugnisse* und klicken Sie auf die Schaltfläche *Importieren...* + 4. Navigate to the *Authorities* tab and click the *Import...* button 5. Wählen Sie die Datei `/Library/Application Support/AdGuard Software/com.adguard.mac.adguard/AdguardCore/Adguard Personal CA.cer` aus oder laden Sie sie einfach von http://local.adguard.org/cert mit einem Chromium-basierten Browser herunter (z. B. Google Chrome oder neu Edge) und mit einer in AdGuard laufenden HTTPS-Filterung Die genauen Aktionen, die für verschiedene Gecko-basierte Browser erforderlich sind, können variieren, aber die allgemeine Reihenfolge und der Pfad zur `Personal CA.cer` Datei sind gleich. -P.S.: Für Version [der Setapp-Anwendung](https://setapp.com/apps/adguard) lautet der Dateipfad wie folgt: `/Library/Application Support/com.adguard.mac.adguard-setapp/AdguardCore/Adguard Personal CA.cer` +P.S.: For [Setapp application version](https://setapp.com/apps/adguard) the file path is the following: `/Library/Application Support/com.adguard.mac.adguard-setapp/AdguardCore/Adguard Personal CA.cer` diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 7176ddaee14..cf150dc1504 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -25,18 +25,18 @@ AdGuard für Mac verwendet jetzt die in macOS integrierte Socket-Filterung basie Die Netzwerkerweiterungs-API hat eine VPN-ähnliche Konfiguration mit einer Liste routenähnlicher Einträge. Auf Big Sur verwendete AdGuard „Split-Tunnel“-Regeln, um die Erstellung der „Standard-Routen“-Regel zu vermeiden, da diese bei frühen Big Sur-Versionen Probleme verursacht. Diese Probleme wurden in Monterey gelöst, also hindert uns nichts daran, die „Standard-Routen“-Regel zu verwenden. -Auf Monterey wurde iCloud Privat-Relay eingeführt. Die Datenschutzfunktionen von Mail-App verwenden auch Privat-Relay-Server. +Auf Monterey wurde iCloud Private Relay eingeführt. Die Datenschutzfunktionen von Mail.app verwenden auch private Relay-Server. -Infolgedessen kann AdGuard nicht mit den Datenschutzfunktionen von iCloud Privat-Relay und der Mail-App zusammenarbeiten: +As a consequence, AdGuard can't work together with iCloud Private Relay and Mail app privacy features: -1. iCloud Privat-Relay wird auf Verbindungen auf Bibliotheksebene angewendet – bevor sie die Socket-Ebene erreichen, auf der AdGuard arbeitet. -2. iCloud Privat-Relay verwendet QUIC, das AdGuard nicht filtern kann, da HTTP/3-Filterung noch nicht verfügbar ist. -3. Folglich sperrt AdGuard QUIC, einschließlich des iCloud Privat-Relay-Verkehrs — andernfalls ist das Sperren von Werbung unmöglich. -4. Wenn Sie iCloud Privat-Relay verwenden und AdGuard in den „Split-Tunnel“-Modus schalten, können Sie keine Websites in Safari öffnen. -5. Um dieses Problem für Monterey zu umgehen, wenden wir die Regel „Standard-Route“ an. Wenn Privat-Relay diese Regel sieht, deaktiviert es sich automatisch. AdGuard funktioniert also nahtlos auf Monterey, aber iCloud Privat-Relay wird deaktiviert. +1. iCloud Private Relay wird auf Verbindungen auf Bibliotheksebene angewendet – bevor sie die Socket-Ebene erreichen, auf der AdGuard arbeitet. +2. iCloud Private Relay verwendet QUIC, das AdGuard nicht filtern kann, da HTTP/3-Filterung noch nicht verfügbar ist. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. +4. Wenn Sie iCloud Private Relay verwenden und AdGuard in den „Split-Tunnel“-Modus schalten, können Sie keine Websites in Safari öffnen. +5. Um dieses Problem für Monterey zu umgehen, wenden wir die Regel „Standard-Route“ an. Wenn Private Relay diese Regel sieht, deaktiviert es sich automatisch. AdGuard funktioniert also nahtlos auf Monterey, aber iCloud Private Relay wird deaktiviert. `network.extension.monterey.force.split.tunnel` stellt das „Big Sur“-Verhalten wieder her, aber diese Option kann den Zugriff auf Websites aufgrund von (3) und (4) unterbrechen. Wir suchen weiter nach einer Lösung für dieses Problem. Eine der Optionen ist die Implementierung der HTTP/3-Filterung. ## Empfohlene Lösung -An dieser Stelle empfehlen wir die Verwendung eines herkömmlichen VPN-Dienstes, wie [AdGuard VPN](https://adguard-vpn.com/), anstelle der neueren Apple-Datenschutzfunktionen. +At this point, we recommend using a more traditional VPN service, such as [AdGuard VPN](https://adguard-vpn.com/), instead of the newer Apple privacy features. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md index 2e6566900cc..2b5d1372360 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md @@ -11,7 +11,7 @@ Dieser Artikel behandelt AdGuard für Mac, einem multifunktionalen Werbeblocker, Wenn der AdGuard-Schutz aus irgendeinem Grund nicht aktiviert werden kann, führen Sie die folgenden Schritte aus: -1. Klicken Sie auf das AdGuard-Symbol in der Menüleiste und öffnen Sie *Erweitert* → *Einstellungen zurücksetzen...* → *AdGuard beenden...* +1. Click the AdGuard icon at the menu bar and go to *Advanced* → *Reset settings...* → *Quit AdGuard...* 2. Geben Sie in der Spotlight-Suche Terminal ein, geben Sie `sudo rm -R /Library/Application\ Support/com.adguard.adguard` ein und führen Sie es aus. @@ -19,4 +19,4 @@ Wenn der AdGuard-Schutz aus irgendeinem Grund nicht aktiviert werden kann, führ 4. Öffnen Sie das Terminal erneut, geben Sie `ls -al /Library/StagedExtensions/Library/Application\ Support/com.adguard.adguard/` ein und führen Sie es aus. Sie sollten Folgendes erhalten: `No such file or directory`. -5. Starten Sie AdGuard und geben Sie Ihre Anmeldedaten ein, wenn Sie dazu aufgefordert werden. +5. Start AdGuard and enter your login information when prompted. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md index ddd9a4f90b4..5b9c7c89e98 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md @@ -1,5 +1,5 @@ --- -title: Inkompatibilität mit der Bildschirmzeit +title: Incompatibility with Screen Time sidebar_position: 11 --- @@ -9,10 +9,10 @@ Dieser Artikel behandelt AdGuard für Mac, einem multifunktionalen Werbeblocker, ::: -Wenn Sie unter _Bildschirmzeit_ Inhaltsbeschränkungen aktiviert haben, während AdGuard aktiviert ist, können Probleme beim Laden von Webseiten auftreten. So prüfen Sie, ob Inhaltsbeschränkungen aktiv sind: +If you have Content Restrictions enabled in _Screen Time_ while AdGuard is on, you may experience problems loading web pages. To check if Content Restrictions are active: -1. Öffnen Sie Systemeinstellungen → Bildschirmzeit → Inhalt und Datenschutz → Inhaltsbeschränkungen +1. Go to System Settings → Screen Time → Content & Privacy → Content Restrictions -2. Prüfen Sie, ob die Einstellung für den Zugriff auf Webinhalte auf _Websites für Erwachsene beschränken_ gesetzt ist +2. Check if the setting for Access to Web Content is set to _Limit Adult Websites_ -Wenn diese Einstellung aktiviert ist, werden die Seiten nicht geladen. Wenn Sie AdGuard weiterhin verwenden möchten, deaktivieren Sie „Inhalt und Datenschutz“ in Bildschirmzeit und starten Sie das System neu. +If this setting is on, pages won’t load. To continue using AdGuard, disable Content & Privacy in Screen Time, and then restart the system. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 788f3ae85fe..ae1b4834c4f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ Im Tab „Über uns” finden Sie Informationen über die aktuelle Version Ihres :::note Erinnerung -AdGuard für Safari kann kostenlos [aus dem App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259) heruntergeladen werden. Eine ausführliche Installationsanleitung finden Sie in der [[Wissensdatenbank]](/adguard-for-safari/installation/). +AdGuard für Safari kann kostenlos [aus dem App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259) heruntergeladen werden. Eine ausführliche Installationsanleitung finden Sie in der [Wissensdatenbank](/adguard-for-safari/installation/). ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index af357a16e30..9cd40a3d16e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -11,7 +11,7 @@ In diesem Artikel geht es um AdGuard für Safari, der nur Ihren Safari-Browser s Zur Analyse und Diagnose verschiedener Probleme, die mit AdGuard für Safari auftreten können, benötigt der AdGuard-Support möglicherweise die Protokolldateien. Diese Dateien enthalten Aufzeichnungen über Fehler und andere Software-Ereignisse. Im Folgenden finden Sie eine kurze Anleitung, wie Sie Protokolle erstellen und bei Bedarf an den Support senden können. -### So erfassen Sie Protokolle +### So erstellen Sie Protokolle 1. Öffnen Sie AdGuard für Safari. 2. Blättern Sie nach unten und klicken Sie auf _Protokolle exportieren_. @@ -21,10 +21,10 @@ Jetzt können Sie diese Datei an support@adguard.com senden oder sie an Ihren Fe :::note -AdGuard ist dem Schutz Ihrer Privatsphäre verpflichtet. Wir halten uns strikt an unsere [Datenschutzerklärung](https://adguard.com/privacy/safari.html) und sammeln keine privaten Informationen über Nutzer:innen. Bevor Sie Ihre Protokolle an das Support-Team senden, überprüfen Sie bitte die Datei, da sie zusätzliche Informationen enthalten kann, die Sie vielleicht nicht freigeben möchten. Wenn sie solche persönlichen Informationen enthält, empfehlen wir Ihnen, sie zuerst zu löschen. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/safari.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -1. Öffnen Sie das [GitHub Repository von AdGuard for Safari](https://github.com/AdguardTeam/AdGuardForSafari/issues) und klicken Sie auf _New issue_. -2. Senden Sie die Protokolldatei an devteam@adguard.com. Geben Sie die Uhrzeit des Fehlers an und fügen Sie einen Link zu Ihrem Problem oder dessen Nummer hinzu (sie wird neben dem Titel als #Nummer angezeigt). - Alternativ können Sie die Protokolldatei auch auf Google Drive hochladen und an devteam@adguard.com senden. Fügen Sie den Dateilink zu Ihrem GitHub-Problem hinzu. +1. Open the [AdGuard for Safari GitHub repo](https://github.com/AdguardTeam/AdGuardForSafari/issues) and click _New issue_. +2. Send the log file to devteam@adguard.com. Geben Sie die Uhrzeit des Fehlers an und fügen Sie einen Link zu Ihrem Problem oder dessen Nummer hinzu (sie wird neben dem Titel als #Nummer angezeigt). + Alternativ können Sie die Protokolldatei auch auf Google Drive hochladen und an devteam@adguard.com senden. Add the file link to your GitHub issue. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index cc6dbc3c076..927fd042ed9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -1,5 +1,5 @@ --- -title: Dokumentation für Administratoren +title: Documentation for admins sidebar_position: 5 --- @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Testen Sie Ihre Installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 9346cc68086..af382575b75 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Hintergrundinformationen: In früheren Versionen der AdGuard-Browsererweiterung (vor v3.5) hat die Erweiterung, wenn sie zusammen mit AdGuard für Windows installiert wurde, die Funktionen des Assistenten übernommen, das Filtern selbst eingestellt und sich auf die App verlassen, die dies übernimmt. -Die Erweiterung und die App funktionierten zusammen, aber manchmal schlug die Integration fehl. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +Die Erweiterung und die App funktionierten zusammen, aber manchmal schlug die Integration fehl. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. Bei der Verwendung des Browser-Assistenten spielen all diese Probleme keine Rolle, da es im Grunde genommen keine Konflikte geben kann. Die Rolle des Browser-Assistenten ist klar definiert, und er kann die Funktion der App nicht beeinträchtigen, so dass es keinen Grund zur Sorge gibt. @@ -42,4 +42,4 @@ Legacy-Assistent ist die ältere Version des Assistenten, die nur ein Benutzersk Wenn Sie den Browser-Assistenten für Ihren Standardbrowser installieren möchten, können Sie dies direkt in den Einstellungen der App tun. Sie haben auch die Möglichkeit, ihn für andere Browser zu installieren. -Der AdGuard Browser-Assistent ist für alle gängigen Browser verfügbar: Chrome, Firefox, Edge, Opera und Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. Das war's! +Der AdGuard Browser-Assistent ist für alle gängigen Browser verfügbar: Chrome, Firefox, Edge, Opera und Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. Das war's! diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index a9b13d9f508..e1865e37811 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -21,7 +21,7 @@ Die folgenden Erweiterungen werden mit AdGuard installiert: ![Preinstalled userscripts \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/preinstalled-userscripts.png) -**AdGuard-Assistent** +**AdGuard Assistant** AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/adguard-for-windows/browser-assistant.md) is not available for your browser. Der Name dieser Erweiterung ist durchaus beabsichtigt: Sie unterstützt den Benutzer:innen bei der Änderung grundlegender AdGuard-Einstellungen direkt im Browser, ohne dass er die App selbst öffnen muss. Assistent funktioniert mit allen mit Microsoft Windows kompatiblen Browsern. Außerdem wird das AdGuard Assistent-Symbol nicht auf Websites angezeigt, die als Ausschlüsse aufgeführt sind, sowie auf bestimmten Seiten, bei denen die Gefahr besteht, dass falsche Inhalte angezeigt werden. @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a Dies ist eine benutzerdefinierte Erweiterung, die entwickelt wurde, um die Technik der Wiedereinführung blockierter Werbung zu bekämpfen — die so genannte Umgehung von Werbeblockern/Ad Reinjection. Beides sind fortschrittliche Anti-Werbeblocker-Methoden, die sich bei den Werbetreibenden immer größerer Beliebtheit erfreuen. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra ist im Wesentlichen ein Miniprogramm, das die Funktionsweise von Seiten so verändert, dass es für Websites sehr viel schwieriger wird, die oben genannten Methoden zur Umgehung von Blockern zu verwenden. **AdGuard Popup Blocker** -Diese Erweiterung verhindert das Öffnen von Pop-up-Fenstern, wenn Sie Webseiten aufrufen. Einige Pop-ups werden als nützlich erachtet — sie können Einstellungen für die Verwaltung der Website oder zusätzliche Referenzinformationen enthalten, die beim Anklicken eines Links angezeigt werden. Aus diesem Grund können Sie den Blocker bei Bedarf ausschalten. This extension doesn’t work on websites added to the AdGuard exceptions list either. Sie ist standardmäßig ausgeschaltet, kann aber in den Einstellungen aktiviert werden. You will find more detailed information about this extension in our Knowledge Base. +Diese Erweiterung verhindert das Öffnen von Pop-up-Fenstern, wenn Sie Webseiten aufrufen. Einige Pop-ups werden als nützlich erachtet — sie können Einstellungen für die Verwaltung der Website oder zusätzliche Referenzinformationen enthalten, die beim Anklicken eines Links angezeigt werden. Aus diesem Grund können Sie den Blocker bei Bedarf ausschalten. This extension doesn’t work on websites added to the AdGuard exceptions list either. Sie ist standardmäßig ausgeschaltet, kann aber in den Einstellungen aktiviert werden. Ausführlichere Informationen über diese Erweiterung finden Sie in unserer Wissensdatenbank. **Web of Trust** @@ -41,7 +41,7 @@ Mit Web of Trust können Sie den Ruf jeder Website auf der Grundlage von Nutzerm ### Netzwerk -Das vorletzte Modul ist der Netzwerkfilterung gewidmet, und hier finden Sie weitere netzwerkbezogene Optionen. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Dies sind wichtige zusätzliche Vorsichtsmaßnahmen, um Ihren Webspace besser zu filtern. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +Das vorletzte Modul ist der Netzwerkfilterung gewidmet, und hier finden Sie weitere netzwerkbezogene Optionen. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. Dies sind wichtige zusätzliche Vorsichtsmaßnahmen, um Ihren Webspace besser zu filtern. Most websites are now using HTTPS, and the same applies to advertising. Von vielen Websites, wie youtube.com, facebook.com und twitter.com, ist es unmöglich, Werbung ohne HTTPS-Filterung zu entfernen. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md index 6af21ea159a..4fd188b958f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md @@ -11,6 +11,6 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc AdGuard für Windows ist ein einfach zu bedienendes Tool, das lästige Banner, Pop-ups, Videoanzeigen und Tracker blockiert. Aber das ist noch nicht alles: Es hilft Ihnen, Datenverkehr zu sparen, Webseiten schneller zu laden und Ihren Computer vor unerwünschten und potenziell bösartigen Websites zu schützen. AdGuard schützt Sie auch vor Phishing-Websites und sorgt dafür, dass Ihre Kinder keinen Zugang zu ungeeigneten Inhalten haben. -![Hauptbildschirm \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/home-screen.png) +![Main screen \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/home-screen.png) Sobald Sie AdGuard für Windows starten, wird der Hauptbildschirm der App angezeigt. Its most noticeable detail is the _enable/disable protection_ button. Auf dieser Seite können Sie auch Statistiken über blockierte Werbung, Tracker und Bedrohungen einsehen, die aktuelle Version der App abrufen oder die App aktualisieren. Furthermore, there are four tabs in the upper right corner: _Settings_, _Support_, _License_, and _About_. Jeder dieser Punkte ist es wert, gesondert behandelt zu werden. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md index 7643ca57ff3..349db2e5219 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md @@ -19,7 +19,7 @@ Wenn Sie auf den Tab „Support“ klicken, öffnet sich ein Dialogfeld, in dem ### Lizenz -![Lizenz \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/license.png) +![License \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/license.png) Auf diesem Tab finden Sie Informationen zu Ihrer Lizenz. Hier können Sie: @@ -28,7 +28,7 @@ Auf diesem Tab finden Sie Informationen zu Ihrer Lizenz. Hier können Sie: ### Über uns -![Über \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/about.png) +![About \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/about.png) Zusätzlich zu den Informationen über die aktuelle Version des Programms bietet dieser Tab einige nützliche Links zu den Seiten Lizenzvereinbarung, Datenschutzerklärung, Danksagungen, Diskussionen und Versionsverlauf. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3522eb92417..591ca9afb3b 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -11,13 +11,13 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc _Settings_ is the section that requires the most attention. Hier können Sie die App so konfigurieren, dass sie genau Ihren Bedürfnissen entspricht: Sie blockiert nur das, was Sie stört, verwendet den DNS-Server des vertrauenswürdigen Anbieters, entfernt Cookies von Drittanbietern und so weiter. -![Einstellungen \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/settings.png) +![Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/settings.png) ### Allgemeine Einstellungen Hier können Sie die Sprache und das Design (dunkel oder hell) festlegen, den Start von AdGuard beim Systemstart und automatische Aktualisierungen im Hintergrund aktivieren, den Aktualisierungskanal auswählen und die Häufigkeit der Filteraktualisierungen festlegen. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). -![Erweiterte Einstellungen \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) +![Advanced Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) At the very bottom of the screen you will find _Advanced Settings_. Wenn Sie einige von ihnen unbedacht ändern, kann dies zu Problemen mit der Leistung führen, die Internetverbindung unterbrechen oder Ihre Sicherheit und Privatsphäre gefährden. Deshalb empfehlen wir Ihnen, diesen Bereich nur zu öffnen, wenn Sie sicher sind, was Sie tun, oder wenn unser Support-Team Sie danach gefragt hat. If you want to know what can be set up in _Advanced Setting_ read the [dedicated article](/adguard-for-windows/solving-problems/low-level-settings.md). @@ -25,7 +25,7 @@ At the very bottom of the screen you will find _Advanced Settings_. Wenn Sie ein Dies ist das Hauptmodul von AdGuard für Windows, das Werbung von den von Ihnen besuchten Websites und von den auf Ihrem Gerät installierten Apps entfernt. To filter out advertising and privacy-threatening content such as banners, pop-ups, or trackers AdGuard uses different filters: groups of rules with a similar purpose written with a [special syntax](/general/ad-filtering/create-own-filters). To understand what filters are and how they work read [this article](/general/ad-filtering/how-ad-blocking-works). -![Werbeblocker \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/settings_ad_blocker.png) +![Ad Blocker \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/settings_ad_blocker.png) Im Werbeblocker-Modul können Sie: @@ -40,11 +40,11 @@ Im Werbeblocker-Modul können Sie: Before you start manually writing your own rules read our detailed [syntax guide](/general/ad-filtering/create-own-filters). -### Privatsphäre +### Stealth Mode Viele Websites sammeln Informationen über Personen, die sie besuchen, z. B. ihre IP-Adressen, Informationen über den Browser und das installierte Betriebssystem, die Bildschirmauflösung und sogar darüber, von welcher Seite die Benutzer:innen kamen oder weitergeleitet wurden. Einige Webseiten verwenden Cookies, um den Browser zu kennzeichnen und Ihre persönlichen Einstellungen und Vorlieben zu speichern oder Sie bei Ihrem nächsten Besuch wiederzuerkennen. Das Privatsphäre-Modul schützt Ihre persönlichen Informationen vor solchen Daten- und Statistiksammelsystemen. -![Privatsphäre \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/stealth-mode.png) +![Stealth Mode \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/stealth-mode.png) Sie können die Funktionsweise dieses Moduls flexibel anpassen: Sie können z. B. verhindern, dass die Website die Suchanfrage erhält, mit der Sie sie im Internet gefunden haben, Sie können Cookies von Drittanbietern und der Website selbst automatisch löschen und Sie können die Standortfreigabe in Ihrem Browser deaktivieren, die dazu verwendet werden kann, Ihren Aufenthaltsort zu verfolgen. @@ -60,15 +60,15 @@ In diesem Modul können Sie: - akustische Benachrichtigungen aktivieren, - sich bereit erklären, anonyme sicherheitsrelevante Informationen an den AdGuard-Server zu übermitteln, damit wir die Datenbank mit bösartigen und Phishing-Websites auf dem neuesten Stand halten können. -![Internetsicherheit \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/browsing-security.png) +![Browsing security \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/browsing-security.png) -Wenn Sie mehr über Internetsicherheit erfahren möchten, lesen Sie [diesen Artikel](/general/browsing-security). +In case you want to learn more about Browsing security, read [this article](/general/browsing-security). ### DNS-Schutz -Es gibt drei wichtige Gründe, warum Sie die DNS-Schutzeinstellungen untersuchen sollten. Erstens, um zu vermeiden, dass Ihr ISP (Internetdiensteanbieter) Sie verfolgt. Jedes Mal, wenn Sie eine Website öffnen, zum Beispiel „google.com“, sendet Ihr Browser eine Anfrage an einen DNS-Server, um die IP-Adresse der Website zu erhalten. In der Regel gehört der DNS-Server zu Ihrem Internetanbieter, der damit Ihre Online-Aktivitäten verfolgen kann. Zweitens, um Ihren DNS-Verkehr zu verschlüsseln. And the third one is to [block content on DNS level](https://adguard-dns.io/kb/general/dns-filtering/). +Es gibt drei wichtige Gründe, warum Sie die DNS-Schutzeinstellungen untersuchen sollten. Erstens, um zu vermeiden, dass Ihr ISP (Internetdiensteanbieter) Sie verfolgt. Every time you open a website, for example `google.com`, your browser sends a request to a DNS server to get the IP address of the website in return. In der Regel gehört der DNS-Server zu Ihrem Internetanbieter, der damit Ihre Online-Aktivitäten verfolgen kann. Zweitens, um Ihren DNS-Verkehr zu verschlüsseln. And the third one is to [block content on DNS level](https://adguard-dns.io/kb/general/dns-filtering/). -![DNS-Schutz \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/dns-settings.png) +![DNS Protection \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/dns-settings.png) In the DNS protection module of AdGuard for Windows you can select the DNS servers from known DNS providers, including [AdGuard DNS](https://adguard-dns.io/kb/) that blocks ads and trackers, AdGuard DNS Family Protection that in addition blocks adult content, or AdGuard DNS Non-filtering that provides a secure and reliable connection, but doesn't filter anything. Sie können sogar eigene DNS-Server hinzufügen. Also there is an option to add custom rules using [DNS rule syntax](https://adguard-dns.io/kb/general/dns-filtering-syntax/). And if necessary, you can add [DNS filters of your choice](https://filterlists.com). @@ -76,16 +76,16 @@ In the DNS protection module of AdGuard for Windows you can select the DNS serve Es gibt eine Reihe von Websites, auf die der Zugriff von einem von Kindern benutzten PC aus beschränkt werden sollte. Diese Aufgabe wird von der Kindersicherung wahrgenommen. -![Kindersicherung \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) +![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) Das Modul prüft den Inhalt der im Browser geöffneten Webseiten und filtert diejenigen mit für Kinder unerwünschten Inhalten: Bilder und Texte für Erwachsene, Schimpfwörter, Gewalt, Drogenpropaganda usw. Die Einstellungen der Kindersicherung sind passwortgeschützt, so dass das Kind die Einschränkungen nicht umgehen kann. Dieses Modul blockiert nicht nur die Weiterleitung auf unerwünschte Seiten, sondern kann auch die für Kinder ungeeigneten Links aus den Suchergebnissen entfernen. -Im Modul _Kindersicherung_ können Sie die _Sichere Suche_ aktivieren und die _Sperrliste_ und die _Positivliste_ verwalten, um die Funktionsweise dieser Option anzupassen. Sie können auch das Kontrollkästchen _Herunterladen von ausführbaren Dateien sperren_ aktivieren, um zu verhindern, dass Ihr Kind Software auf den Computer herunterlädt und installiert. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. -![Kindersicherung \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) +![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) ### Browser-Assistent -![Browser-Assistent \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/browser-assistant.png) +![Browser Assistant \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/browser-assistant/browser-assistant.png) -Von diesem Tab aus können Sie ganz einfach den AdGuard Browser-Assistenten installieren, dessen Hauptfunktion darin besteht, das Filtern direkt über den Browser zu verwalten. Wie Sie damit arbeiten und was zu tun ist, wenn es für Ihren Browser keinen Browser-Assistenten gibt, wird in einem [separaten Artikel](/adguard-for-windows/browser-assistant.md) näher erläutert. +Von diesem Tab aus können Sie ganz einfach den AdGuard Browser-Assistenten installieren, dessen Hauptfunktion darin besteht, das Filtern direkt über den Browser zu verwalten. We explained more about how to work with it and what to do if there is no Browser Assistant for your browser in the [separate article](/adguard-for-windows/browser-assistant.md). diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index 13d920afeac..8cce023590e 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc Um AdGuard auf einem PC oder Tablet unter Microsoft Windows zu verwenden, müssen Sie das Installationspaket herunterladen und das Installationsprogramm starten. Führen Sie die folgenden Schritte aus: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![AdGuard herunterladen](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,9 +91,9 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. -![Erweiterte Deinstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) +![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) - Click *OK* once the warning window pops up: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index baa49e1c6fe..c026448f0cd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -1,5 +1,5 @@ --- -title: So erfassen Sie die AdGuard-Protokolle +title: So werden AdGuard-Protokolle erfasst sidebar_position: 3 --- @@ -15,17 +15,17 @@ Die in den Protokollen enthaltenen Daten und/oder Dateien werden in Übereinstim ::: -Zur Analyse und Diagnose verschiedener Probleme, die möglicherweise auftreten können, benötigt der AdGuard-Support möglicherweise AdGuard-Protokolldateien. Diese Dateien enthalten Aufzeichnungen über Fehler und andere Ereignisse, die im Zusammenhang mit der Software aufgetreten sind. Nachfolgend finden Sie eine kurze Anleitung, wie Sie die Protokolldateien abrufen und gegebenenfalls an den Support-Dienst senden können. +Zur Analyse und Diagnose verschiedener Probleme, die möglicherweise auftreten können, benötigt der AdGuard-Support möglicherweise AdGuard-Protokolldateien. These files contain records about errors and other events that occurr with the software. Nachfolgend finden Sie eine kurze Anleitung, wie Sie die Protokolldateien abrufen und gegebenenfalls an den Support-Dienst senden können. :::note -AdGuard ist dem Schutz Ihrer Privatsphäre verpflichtet. Wir halten uns konsequent an unsere [Datenschutzerklärung](https://adguard.com/privacy/windows.html) und sammeln keine privaten Informationen über Nutzer:innen. Bevor Sie Ihre Protokolle an das Support-Team senden, überprüfen Sie bitte die Datei, da sie zusätzliche Informationen enthalten kann, die Sie vielleicht nicht freigeben möchten. Wenn sie solche persönlichen Informationen enthält, empfehlen wir Ihnen, sie zuerst zu löschen. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: ### Debug logs {#debug-logs} -1. Öffnen Sie die AdGuard-Einstellungen. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Öffnen Sie die AdGuard-Einstellungen. Öffnen Sie den Abschnitt *Allgemeine Einstellungen*, blättern Sie bis zum Ende des Bildschirms und schalten Sie die *Protokollierungstiefe* auf *Zur Fehlersuche* um. ![Stufe der Fehlersuch-Protokollierung *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard ist dem Schutz Ihrer Privatsphäre verpflichtet. Wir halten uns konseque Wir empfehlen Ihnen dringend, sich den genauen Zeitpunkt zu notieren, zu dem Sie das Problem reproduziert haben: Das hilft unserem Support-Team, relevante Protokolleinträge zu finden und das Problem schneller zu lösen. -1. Export the collected logs using the *Export Logs* button. +1. Exportieren Sie die aufgezeichneten Protokolle über die Schaltfläche *Protokoll exportieren*. ![Protokoll exportieren *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Speichern Sie das Archiv in einem beliebigen Ordner. -1. **Important**: after exporting the logs, set the logging level back to *Default*. Die Protokollierungsstufe *Zur Fehlersuche* verlangsamt die Anwendung. +1. **Wichtig**: Setzen Sie nach dem Exportieren der Protokolle die Protokollierungsstiefe wieder auf *Standard*. Die Protokollierungsstufe *Zur Fehlersuche* verlangsamt die Anwendung. 1. Senden Sie das Archiv an den AdGuard-Support unter **support@adguard.com**, beschreiben Sie das Problem und vergessen Sie nicht, den Zeitpunkt anzugeben, zu dem Sie das Problem reproduziert haben. @@ -65,7 +65,7 @@ Wenn Sie eine ältere Version von AdGuard für Windows haben, führen Sie die An Wir empfehlen Ihnen dringend, sich den genauen Zeitpunkt zu notieren, zu dem Sie das Problem reproduziert haben: Das hilft unserem Support-Team, relevante Protokolleinträge zu finden und das Problem schneller zu lösen. -1. Export the collected logs using the *Export Logs* button. +1. Exportieren Sie die aufgezeichneten Protokolle über die Schaltfläche *Protokoll exportieren*. ![Protokoll exportieren *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 2020254f190..15ce1a57a97 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,27 +13,27 @@ In diesem Artikel finden Sie einige der häufigsten Fehler, die bei der Installa ### Fehler 5: Zugriff verweigert {#error-5} -This error message appears when required permissions haven't been granted. Es kann verschiedene Gründe geben, warum das AdGuard-Installationsprogramm nicht über die erforderlichen Berechtigungen verfügt, um den Installationsvorgang ordnungsgemäß abzuschließen. Sie können die folgenden Schritte versuchen: +This error occurs when there's something wrong with permissions. Es kann verschiedene Gründe geben, warum das AdGuard-Installationsprogramm nicht über die erforderlichen Berechtigungen verfügt, um den Installationsvorgang ordnungsgemäß abzuschließen. Sie können die folgenden Schritte versuchen: -- Temporarily disable your antivirus. Einige von ihnen können die Installation beeinträchtigen, je nachdem, wie stark sie eingestellt sind. +- Deaktivieren Sie vorübergehend Ihre Antivirenprogramme. Einige von ihnen können die Installation beeinträchtigen, je nachdem, wie stark sie eingestellt sind. - Wählen Sie einen anderen Installationsordner. Es ist möglich, dass der aktuelle Installationsordner Zugriffsbeschränkungen hat. Stellen Sie außerdem sicher, dass Sie kein externes oder virtuelles Laufwerk usw. auswählen. - Starten Sie Ihren Computer neu. Manchmal sind die Berechtigungsprobleme vorübergehend und können durch einen Neustart des PCs behoben werden. -### Fehler 112: Datenträger verfügt nicht mehr über genügend Speicherplatz, Fehler 1632: Temporärer Ordner voll oder unzugänglich {#error-112} +### Fehler 112: Datenträger ist voll, Fehler 1632: Temporärer Ordner voll oder unzugänglich {#error-112} -Es handelt sich um zwei verschiedene Fehler mit sehr ähnlichen Lösungen. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. Es gibt mehrere Möglichkeiten, das Problem zu beheben: +Es handelt sich um zwei verschiedene Fehler mit sehr ähnlichen Lösungen. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. Es gibt mehrere Möglichkeiten, das Problem zu beheben: - Deinstallieren Sie einige Programme oder löschen Sie unnötige Dateien von dem Laufwerk, auf dem Sie AdGuard installieren möchten. -- Laden Sie [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), eine kostenlose Software von Malwarebytes, herunter, installieren Sie sie und führen Sie sie aus. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. Das wird helfen, etwas Speicherplatz freizugeben. +- Laden Sie [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), eine kostenlose Software von Malwarebytes, herunter, installieren Sie sie und führen Sie sie aus. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. Das wird helfen, etwas Speicherplatz freizugeben. - Starten Sie Ihren Computer neu. Manchmal können temporäre Dateien eine beträchtliche Menge an Speicherplatz beanspruchen, und ein Neustart Ihres PCs ist die zuverlässigste Methode, sie loszuwerden. ### Fehler 1601: Auf Windows Installer kann nicht zugegriffen werden {#error-1601} -You could say this is a particular subcategory of Error 1603. Die möglichen Lösungen sind ähnlich: +You could say this is a particular sub-case of Error 1603. Die möglichen Lösungen sind ähnlich: - Starten und registrieren Sie den Microsoft Installer-Dienst erneut. Das erfordert etwas Arbeit. @@ -75,7 +75,7 @@ Dieser Fehler tritt auf, wenn mehrere Instanzen des AdGuard-Installationsprogram - Starten Sie Ihren PC neu und starten Sie das Installationsprogramm erneut. Wenn Sie den Computer neu starten, werden alle laufenden Prozesse angehalten, einschließlich aller Kopien des Installationsprogramms. -- Don't make multiple clicks on the installer even if it doesn't start right away. Manchmal kann es ein paar Sekunden dauern, bis die Benutzeroberfläche des Installationsprogramms angezeigt wird. +- Don't make multiple clicks on the installer even if doesn't start right away. Manchmal kann es ein paar Sekunden dauern, bis die Benutzeroberfläche des Installationsprogramms angezeigt wird. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Deinstallieren Sie AdGuard mit unserem speziellen [Deinstallationstool](../../installation#advanced) und wiederholen Sie dann die Installation. +- Maybe there's some leftover files from a previous AdGuard installation. Deinstallieren Sie AdGuard mit unserem speziellen [Deinstallationstool](../../installation#advanced) und wiederholen Sie dann die Installation. ### Andere Fehler {#other} -If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Bitte führen Sie dazu die folgenden Schritte aus: +If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md index 442ec280ed7..f3e5d1f7a24 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md @@ -1,5 +1,5 @@ --- -title: Zertifikatsbezogene Probleme +title: Certificate-related issues sidebar_position: 2 --- @@ -17,13 +17,13 @@ Normally browsers trust the AdGuard certificate once it's added to the system ce ![Security risk error](https://cdn.adtidy.org/public/Adguard/kb/en/certificate/cert_error_en.png) -Old FireFox versions, as well as browsers based on them, do not trust certificates from the system storage, but only those from their local storage. Seit Version 68 vertraut FireFox den Systemzertifikaten, aber Sie können immer noch die Fehlermeldung „Verbindung ist nicht vertrauenswürdig” erhalten. If something like this happens, first try to click the *Reinstall Certificate* button — you will find it in the *Network* tab. +Old FireFox versions, as well as browsers based on them, do not trust certificates from the system storage, but only those from their local storage. Since v68, FireFox trusts the system certificates, but you still can face the "Connection is untrusted" error. If something like this happens, first try to click the *Reinstall Certificate* button — you will find it in the *Network* tab. -![Zertifikat neu installieren](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/reinstall.jpg) +![Reinstall Certificate](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/reinstall.jpg) -Wenn das nicht hilft, folgen Sie den Anweisungen zum manuellen Hinzufügen des AdGuard-Zertifikats zum FireFox-Speicher. +If that doesn't help, follow the instructions for manually adding the AdGuard certificate to the FireFox storage. -> Diese Anleitung gilt für den Firefox-Browser. Die Namen der Schaltflächen und Menüpunkte können in anderen Firefox-basierten Browsern abweichen. +> This instruction is for Firefox browser. Names of buttons and menu items may differ in other Firefox-based browsers. 1. Run AdGuard. @@ -36,15 +36,15 @@ Wenn das nicht hilft, folgen Sie den Anweisungen zum manuellen Hinzufügen des A ::: - ![Zertifikat-Einstellungen](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/link.jpeg) + ![Certificate settings](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/link.jpeg) -1. Öffnen Sie Ihren Browser und dann die *Einstellungen*. +1. Open your browser and then open *Settings*. 1. Go to *Privacy & Security* tab. 1. Scroll down to *Certificates* and click the *View Certificates* button. - ![Fenster „Zertifikate” anzeigen](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import1.jpeg) + ![View certificates window](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import1.jpeg) 1. Select *Authorities* tab. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index 37fde6a538d..83d2e3d7249 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -1,5 +1,5 @@ --- -title: Mögliche DNS-Lecks +title: Possible DNS leaks sidebar_position: 9 --- @@ -11,7 +11,7 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,10 +21,10 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* -## Fallback-DNS-Server +## Fallback DNS server It could happen that AdGuard cannot reach the specified server because of a weak internet connection, an expiration of timeout set by default or some server related issues. In this case, it will connect to the fallback server, which is by default a system DNS server. This connection will also be considered by the check service as a leak. @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 8615e0eb222..20bba8cf696 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ Nachdem Sie die Dump-Datei erstellt haben, navigieren Sie bitte zum Speicherort :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard für Windows besteht aus zwei laufenden Prozessen (`Adguard.exe` und `AdguardSvc.exe`). Daher muss die Dump-Datei für jeden Prozess einzeln erstellt werden. ::: ![AdGuard-Prozesse](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -Wenn Sie die Dump-Dateien an das Support-Team senden, fügen Sie bitte auch die Protokolle der App an, damit wir eine bessere Chance haben, das Problem zu lösen. [Hier](../adguard-logs) finden Sie eine Anleitung, wie Sie die Protokolldatei erstellen können. +Wenn Sie die Dump-Dateien an das Support-Team senden, fügen Sie bitte auch die Protokolle der App an, damit wir eine bessere Chance haben, das Problem zu lösen. [Hier](../adguard-logs) können Sie die Anweisungen zum Zusammenstellen der Protokolldatei einsehen. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 309498661e1..2bb3ebcb70f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Daten und/oder Dateien, die in Systemprotokollen enthalten sind, werden gemäß If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index a432a4db892..89d20554e0f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Wenn Sie die erweiterten Einstellungen öffnen, werden Ihnen die folgenden Optio Wenn aktiviert, blockiert AdGuard TCP Fast Open im Edge-Browser. Um die Einstellungen zu übernehmen, müssen Sie den Browser neu starten. -### Encrypted Client Hello verwenden +### Encrypted ClientHello verwenden -Jede verschlüsselte Internetverbindung hat einen unverschlüsselten Teil. Dies ist das allererste Paket, das den Namen des Servers enthält, mit dem Sie sich verbinden. Die verschlüsselte Client-Hallo-Technologie soll dieses Problem lösen und das letzte bisschen an unverschlüsselter Information verschlüsseln. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Jede verschlüsselte Internetverbindung hat einen unverschlüsselten Teil. Dies ist das allererste Paket, das den Namen des Servers enthält, mit dem Sie sich verbinden. Die verschlüsselte Client-Hallo-Technologie soll dieses Problem lösen und das letzte bisschen an unverschlüsselter Information verschlüsseln. Um davon zu profitieren, aktivieren Sie die Option *Encrypted ClientHello verwenden*. It uses a local DNS proxy to look for the ECH configuration for the domain. Wenn es gefunden wird, wird das ClientHello-Paket verschlüsselt. ### Zertifikatstransparenz von Websites prüfen @@ -61,9 +61,9 @@ Aktivieren Sie diese Funktion, um Popup-Benachrichtigungen von AdGuard anzuzeige Aktivieren Sie diese Funktion, wenn Sie möchten, dass AdGuard automatisch Filter-URLs (z.B. `abp:subscribe` und ähnliche) abfängt und einen benutzerdefinierten Filter-Installationsdialog öffnet. -### HTTP/3 filtern +### Filter HTTP/3 -Ist diese Option aktiviert, filtert AdGuard zusätzlich zu den anderen Anfragetypen auch Anfragen, die über HTTP/3 gesendet werden. +If this option is enabled, AdGuard will filter requests sent over HTTP/3 in addition to other request types. ### Umleitungstreiber-Modus verwenden @@ -73,7 +73,7 @@ Andernfalls filtert AdGuard den gesamten Datenverkehr sofort und ohne Umleitung. ### Hauptfenster bei Systemstart öffnen -Aktivieren Sie diese Option, damit sich das Hauptfenster von AdGuard nach dem Laden des Systems öffnet. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Aktivieren Sie diese Option, damit sich das Hauptfenster von AdGuard nach dem Laden des Systems öffnet. Beachten Sie, dass es keinen Einfluss darauf hat, ob der eigentliche Filterdienst gestartet wird oder nicht. Diese Einstellung befindet sich in *Einstellungen → Allgemeine Einstellungen* ### Filterung beim Systemstart aktivieren @@ -95,7 +95,7 @@ Wenn Sie nicht möchten, dass AdGuard bestimmte Subnetze filtert, aktivieren Sie ### Das Schreiben im HAR-Format erlauben -Diese Option sollte **nur für die Fehlersuche** aktiviert werden. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. Diese Datei kann mit der App „Fiddler“ analysiert werden. Beachten Sie, dass sich Ihr Surfen im Internet dadurch erheblich verlangsamen kann. +Diese Option sollte **nur für die Fehlersuche** aktiviert werden. Wenn Sie das Häkchen setzen, erstellt AdGuard eine Datei, die Informationen über alle gefilterten HTTP-Anfragen im Format HAR 1.2 enthält. Diese Datei kann mit der App „Fiddler“ analysiert werden. Beachten Sie, dass sich Ihr Surfen im Internet dadurch erheblich verlangsamen kann. ### Zusätzliches Leerzeichen in die einfache HTTP-Anfrage einfügen @@ -115,15 +115,15 @@ Diese Option wird nur angewendet, wenn die Option *Schutz vor DPI* im Privatsph Gibt die Größe der TCP-Paketfragmentierung an, um eine Deep Packet Inspection zu vermeiden. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +Wenn diese Option aktiviert ist, teilt AdGuard das initiale TLS-Paket (das ClientHello-Paket) in zwei Teile auf: der erste hat die angegebene Länge und der zweite den Rest, bis zur Länge des gesamten initialen TLS-Pakets. -Gültige Werte: 1–1500. Wird eine ungültige Größe angegeben, wird der vom System ausgewählte Wert verwendet. Diese Option wird nur angewendet, wenn die Option *Schutz vor DPI* im Privatsphärenmodus aktiviert ist. +Valid values: 1–1500. Wird eine ungültige Größe angegeben, wird der vom System ausgewählte Wert verwendet. Diese Option wird nur angewendet, wenn die Option *Schutz vor DPI* im Privatsphärenmodus aktiviert ist. ### Fragmentgröße einer einfachen HTTP-Anfrage Passt die Größe der Fragmentierung der HTTP-Anfrage an. Diese Option betrifft nur den einfachen HTTP-Verkehr. Wenn diese Option aktiviert ist, teilt AdGuard das ursprüngliche Paket in zwei Teile auf: der erste hat die angegebene Länge und der zweite den Rest, bis zur Länge des gesamten ursprünglichen Pakets. -Gültige Werte: 1–1500. Wird eine ungültige Größe angegeben, wird der vom System ausgewählte Wert verwendet. Diese Option wird nur angewendet, wenn die Option *Schutz vor DPI* im Privatsphärenmodus aktiviert ist. +Valid values: 1–1500. Wird eine ungültige Größe angegeben, wird der vom System ausgewählte Wert verwendet. Diese Option wird nur angewendet, wenn die Option *Schutz vor DPI* im Privatsphärenmodus aktiviert ist. ### QUIC anzeigen diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 33f98d1ca7a..79c0481e176 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect Windows system logs +title: So erfassen Sie Windows-Systemprotokolle sidebar_position: 5 --- @@ -15,13 +15,13 @@ Daten und/oder Dateien, die in Systemprotokollen enthalten sind, werden gemäß ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Nachfolgend finden Sie eine kurze Anleitung, wie Sie die Protokolldateien abrufen und bei Bedarf an unseren Kundenservice senden können. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Nachfolgend finden Sie eine kurze Anleitung, wie Sie die Protokolldateien abrufen und bei Bedarf an unseren Kundenservice senden können. 1. Press *Win + R* 1. Geben Sie in dem sich öffnenden Fenster `eventvwr` ein und klicken Sie auf *OK*: - ![Ausführen-Fenster *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_1.png) + ![Run window *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_1.png) 1. Das Fenster der Ereignisanzeige erscheint wie in der Abbildung gezeigt. @@ -45,6 +45,6 @@ Bitte senden Sie die beiden Dateien, die Sie soeben gespeichert haben, an **supp :::note -AdGuard ist dem Schutz Ihrer Privatsphäre verpflichtet. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Bevor Sie Ihre Protokolle an das Support-Team senden, überprüfen Sie bitte die Datei, da sie zusätzliche Informationen enthalten kann, die Sie vielleicht nicht freigeben möchten. Wenn sie solche persönlichen Informationen enthält, empfehlen wir Ihnen, sie zuerst zu löschen. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index f673d121bf6..5e6c5ebfe3d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -1,5 +1,5 @@ --- -title: WFP-Treiber +title: WFP driver sidebar_position: 1 --- @@ -9,12 +9,12 @@ Dieser Artikel behandelt AdGuard für Windows, einem multifunktionalen Werbebloc ::: -Um den Netzwerkverkehr filtern zu können, verwendet AdGuard einen Netzwerktreiber. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. Um dies zu tun: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: -![WFP-Treiber *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) +![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/de/docusaurus-plugin-content-docs/current/general/account/features.md index 42f02784227..f102edeeda8 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ Im Abschnitt Kaufhistorie werden alle Lizenzen angezeigt, die Sie jemals über d ## Support kontaktieren -Der Tab „Support” enthält nützliche Links, die Ihnen helfen, Probleme zu lösen oder Antworten auf Ihre Fragen zu AdGuard-Produkten zu finden. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +Der Tab „Support” enthält nützliche Links, die Ihnen helfen, Probleme zu lösen oder Antworten auf Ihre Fragen zu AdGuard-Produkten zu finden. Sie sind in sechs Abschnitte unterteilt: FAQ, Senden Sie einen Fehlerbericht oder Anfrage zu einer gewünschten Funktion, Fehlerhaftes Sperren melden, Support kontaktieren, Wissensdatenbank und Diskutieren. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index c38fde7938d..5724c4bc00d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ In diesem Artikel geht es um die Filter, die wir für AdGuard und andere Werbebl - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index d3039e570c9..317bb3fcabc 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -143,7 +143,7 @@ Because of the limitations above AdGuard Content Blocker will not be mentioned i The most simple rules are so-called *Basic rules*. They are used to block requests to specific URLs. Or to unblock it, if there is a special marker "@@" at the beginning of the rule. The basic principle for this type of rules is quite simple: you have to specify the address and additional parameters that limit or expand the rule scope. -:::note Sub-Anfragen +:::note Sub-requests Basic rules for blocking requests are applied only to **sub-requests**. That means they will not block the loading of the page unless it is explicitly specified with a `$document` modifier. @@ -155,7 +155,7 @@ Browser detects a blocked request as completed with an error. ::: -:::note Länge der Regel +:::note Rule length Rules shorter than 4 characters are considered incorrect and will be ignored. @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:--------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — unterstützt, aber die Zuverlässigkeit kann variieren oder es können Einschränkungen auftreten; weitere Einzelheiten finden Sie in der Beschreibung des Modifikators -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Beschränkungen - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Kompatibilität -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -575,12 +567,11 @@ AdGuard will try to close the browser tab with any address that matches a blocki ##### `$popup` modifier limitations {#popup-modifier-limitations} -:::caution Beschränkungen +:::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Kompatibilität - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Kompatibilität - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Kompatibilität -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,27 +652,27 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:--------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:--------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — unterstützt, aber die Zuverlässigkeit kann variieren oder es können Einschränkungen auftreten; weitere Einzelheiten finden Sie in der Beschreibung des Modifikators +- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - ❌ — not supported - 🚫 — removed and no longer supported @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Beschränkungen +:::info Kompatibilität AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Kompatibilität - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Beschränkungen - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Kompatibilität +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Beschränkungen - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Kompatibilität -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,22 +831,22 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:--------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:--------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — unterstützt, aber die Zuverlässigkeit kann variieren oder es können Einschränkungen auftreten; weitere Einzelheiten finden Sie in der Beschreibung des Modifikators +- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - ❌ — not supported ::: @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Kompatibilität - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Kompatibilität - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Kompatibilität -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Beschränkungen +:::info Kompatibilität In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Kompatibilität - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Beschränkungen +:::info Kompatibilität In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Kompatibilität - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:--------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:--------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — unterstützt, aber die Zuverlässigkeit kann variieren oder es können Einschränkungen auftreten; weitere Einzelheiten finden Sie in der Beschreibung des Modifikators -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Beschränkungen - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Kompatibilität Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Beschränkungen - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Kompatibilität Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Beschränkungen - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Kompatibilität -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Kompatibilität -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Kompatibilität -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2093,7 +1971,7 @@ If there are multiple `$permissions` rules that match the same request, multiple ##### `$permissions` modifier limitations {#permissions-modifier-limitations} -:::caution Beschränkungen +:::caution Limitations Firefox ignores the `Permissions-Policy` header. For more information, see [this issue](https://bugzilla.mozilla.org/show_bug.cgi?id=1694922). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Kompatibilität -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Beschränkungen - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Kompatibilität -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Kompatibilität -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Kompatibilität -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Kompatibilität -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Beschränkungen - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Kompatibilität -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Kompatibilität -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Kompatibilität - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2738,15 +2535,15 @@ Rules with `$mp4` modifier are not supported by AdGuard Content Blocker, AdGuard Each rule has its own priority, which is necessary when several rules match the request and the filtering engine needs to select one of them. Priority is measured by a positive integer. -:::note Kollisionen +:::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:--------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:--------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Kompatibilität -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3854,7 +3649,7 @@ Following rule will delete all `script` elements with a `banner` substring in th $$script[tag-content="banner"] ``` -:::caution Beschränkungen +:::caution Limitations The `tag-content` special attribute must not appear in a selector to the left of a `>` combinator. @@ -3876,7 +3671,7 @@ For example: `$$script[wildcard="*banner*text*"]` It checks if the element code contains the two consecutive substrings `banner` and `text`. -:::caution Beschränkungen +:::caution Limitations The `wildcard` special attribute must not appear in a selector to the left of a `>` combinator. @@ -3904,7 +3699,7 @@ $$div[tag-content="banner"][max-length="400"] This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which does not exceed `400` characters. -:::caution Beschränkungen +:::caution Limitations The `max-length` special attribute must not appear in a selector to the left of a `>` combinator. @@ -3928,7 +3723,7 @@ $$div[tag-content="banner"][min-length="400"] This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which exceeds `400` characters. -:::caution Beschränkungen +:::caution Limitations The `min-length` special attribute must not appear in a selector to the left of a `>` combinator. @@ -3950,7 +3745,7 @@ or :contains(/reg(ular )?ex(pression)?/) ``` -:::note Kompatibilität +:::note Compatibility `:-abp-contains()` and `:has-text()` are synonyms for `:contains()`. @@ -3964,7 +3759,7 @@ The `:contains()` pseudo-class is supported by AdGuard for Windows, Mac, and And Requires that the inner HTML of the element contains the specified text or matches the specified regular expression. -:::caution Beschränkungen +:::caution Limitations A `:contains()` pseudo-class must not appear in a selector to the left of a `>` combinator. @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:--------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifikator \ Produkte | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard für iOS][ios-app] | [AdGuard für Safari][ext-saf] | [AdGuard-Inhaltsblocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:--------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — unterstützt, aber die Zuverlässigkeit kann variieren oder es können Einschränkungen auftreten; weitere Einzelheiten finden Sie in der Beschreibung des Modifikators +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Kompatibilität -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Beschränkungen - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Kompatibilität -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Beschränkungen +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Kompatibilität -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,47 +4470,34 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} :::note - ✅ — fully supported -- ✅ * — unterstützt, aber die Zuverlässigkeit kann variieren oder es können Einschränkungen auftreten; weitere Einzelheiten finden Sie in der Beschreibung des Modifikators +- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard für Safari" -[ext-saf]: #what-product "AdGuard for Safari" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index d27d3d0c6f8..c4e4da985dd 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard-Filter zum Blockieren von Werbung umfassen: - AdGuard Basisfilter - AdGuard-Filter gegen mobile Werbung - Regionale Filter nach Sprachprinzip — Chinesisch, Niederländisch, Französisch, Deutsch, Japanisch, Russisch, Spanisch/Portugiesisch, Türkisch, und Ukrainisch -- AdGuard Quick Fixes filter ### Der Zweck dieser Filter - **Der Basisfilter** blockiert Werbung auf englischsprachigen Websites und solchen, für die es keinen eigenen Filter gibt. Er enthält auch allgemeine Filterregeln, die für alle Websites unabhängig von der Sprache gelten - **Filter gegen mobile Werbung** blockiert Werbung auf mobilen Versionen von Websites und in mobilen Apps. Es gibt keine Unterteilung nach Sprachen - **Sprachspezifische Filter** folgen der gleichen Politik wie der **Basisfilter**, sind aber auf Websites in bestimmten Sprachen beschränkt -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. Das Ziel von Werbeblockern ist es, alle Arten von Werbung auf Websites, in Apps und auf bestimmten Geräten, die Werbung aus dem Internet laden können, zu blockieren: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index 0d421657b15..b4e77c7be48 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/de/docusaurus-plugin-content-docs/current/general/browsing-security.md index 755d6a900aa..db6e850386c 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. Wir tun unser Bestes, um den Prozentsatz der Falschmeldungen zu verringern, aber sie kommen trotzdem vor. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/de/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/de/docusaurus-plugin-content-docs/current/general/license/what-is.md index 6fb1cad57e8..dfd7eeb8a86 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ Auf der [Kaufseite](https://adguard.com/license.html) sind folgende Arten von Li - **1-Jahres-Abonnements** — diese Lizenzen werden automatisch jedes Jahr erneuert oder können manuell verlängert werden - Einzellizenz — schützt bis zu 3 Geräte - Familienlizenz — schützt bis zu 9 Geräte -- **Lifetime** — these licenses are perpetual +- **Lebenslang** — diese Lizenzen sind zeitlich nicht begrenzt - Einzellizenz — schützt bis zu 3 Geräte - Familienlizenz — schützt bis zu 9 Geräte diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/de/docusaurus-plugin-content-docs/current/general/stealth-mode.md index dad3db5dd9b..72ba72e5481 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Java sperren {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/de/docusaurus-plugin-content-docs/current/general/userscripts.md index e81ec1bc4d0..028e2527e31 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. Sie ändern oder erweitern die Funktionalität einer oder mehrerer Websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. Sie ändern oder erweitern die Funktionalität einer oder mehrerer Websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Unterstützte Apps @@ -134,7 +134,7 @@ Hier ist ein [Mailto-Link](mailto:devteam@adguard.com?Subject=Userscript%20autho ##### Nicht unterstützte Eigenschaften -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/de/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/de/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 9f9a4a15e41..4feefbc4e8f 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: So sammeln Sie eine HAR-Datei sidebar_position: 1 --- diff --git a/i18n/de/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/de/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 9596767a128..2451e4be768 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Prüfen Sie, ob Sie die aktuellste Version haben, und wenn nicht, aktualisieren ### Wie man ein Problem beschreibt -Versuchen Sie, so viele Details wie möglich anzugeben — das macht es für uns einfacher, den Fehler zu reproduzieren und herauszufinden, wie er behoben werden kann. Here’s what we expect a bug report to include: +Versuchen Sie, so viele Details wie möglich anzugeben — das macht es für uns einfacher, den Fehler zu reproduzieren und herauszufinden, wie er behoben werden kann. Das erwarten wir von einem Fehlerbericht: - Ihre App-Version - Ihre OS-Version @@ -26,9 +26,9 @@ Versuchen Sie, so viele Details wie möglich anzugeben — das macht es für uns - Ob es wieder auftritt und mit welcher Häufigkeit - Ob Sie ein VPN oder eine Antiviren-Software haben -### So erfassen Sie Protokolle +### So erstellen Sie Protokolle -Read about collecting logs in dedicated articles for each platform. +Lesen Sie über das Sammeln von Protokollen in speziellen Artikeln für jede Plattform. ## Wie man für Fehlerberichte oder Funktionswünsche abstimmt diff --git a/i18n/de/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/de/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index 9c985b92a2c..4955f3972b1 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ Auf manchen Laptops müssen Sie *Fn* gedrückt halten und dann *Druck* drücken. Windows erfasst den gesamten Bildschirm und kopiert ihn in die Zwischenablage. -To take a screenshot of an active window, use the following shortcut keys: +Um ein Bildschirmfoto von einem aktiven Fenster zu machen, verwenden Sie das folgende Tastaturkürzel: - **Halten Sie *Alt* gedrückt und drücken Sie *Druck* (oder *Fn + Alt + Druck* auf einigen Laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +Um ein Bildschirmfoto von einem bestimmten Bereich zu machen, verwenden Sie das folgende Tastaturkürzel: - ***Drücken Sie ***Win + Umschalt + S****** -Nachdem Sie ein Bildschirmfoto erstellt haben, wird es in der Zwischenablage gespeichert. In den meisten Fällen können Sie es mit dem Tastaturkürzel *Strg + V* in ein Dokument einfügen, das Sie gerade bearbeiten. Wenn Sie das Bildschirmfoto in einer Datei speichern möchten, sollten Sie alternativ das Standardprogramm **Paint** (oder eine andere Anwendung, die mit Bildern arbeiten kann) öffnen. Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +Nachdem Sie ein Bildschirmfoto erstellt haben, wird es in der Zwischenablage gespeichert. In den meisten Fällen können Sie es mit dem Tastaturkürzel *Strg + V* in ein Dokument einfügen, das Sie gerade bearbeiten. Wenn Sie das Bildschirmfoto in einer Datei speichern möchten, sollten Sie alternativ das Standardprogramm **Paint** (oder eine andere Anwendung, die mit Bildern arbeiten kann) öffnen. Fügen Sie Ihr Bildschirmfoto mit demselben Tastaturkürzel oder durch Klicken auf die Schaltfläche „Einfügen“ (in der Regel in der oberen linken Ecke des Bildschirms) ein und speichern Sie es dann. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. Sobald Sie diese Tasten drücken, wird das Bildschirmfoto automatisch als Datei in Ihrem Ordner *Bilder* → *Bildschirmfotos* gespeichert. +Unter Windows 8 und 10 können Sie mit dem Tastaturkürzel *Win + Druck* sehr schnell ein Bildschirmfoto aufnehmen. Sobald Sie diese Tasten drücken, wird das Bildschirmfoto automatisch als Datei in Ihrem Ordner *Bilder* → *Bildschirmfotos* gespeichert. Es gibt auch ein spezielles Programm zum Erstellen von Bildschirmfotos namens *Snipping Tool*. Sie finden es im Startmenü unter den Standardprogrammen Ihres Computers. Mit dem Snipping Tool können Sie einen beliebigen Bereich Ihres Desktops oder den gesamten Bildschirm erfassen. Nach der Aufnahme eines Bildschirmfotos mit diesem Programm können Sie das Bild bearbeiten und in einem beliebigen Ordner auf Ihrem Computer speichern. @@ -70,26 +70,26 @@ Außerdem können Sie auch versuchen, verschiedene Apps zum Aufnehmen von Bildsc ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Um ein Bildschirmfoto auf dem Mac zu erstellen, verwenden Sie das folgende Tastaturkürzel: - ***Drücken und halten Sie ***⌘ Cmd + Umschalt + 3****** Ihr Mac erfasst den gesamten Bildschirm und speichert ihn als Datei auf dem Desktop. -To take a screenshot of an active window, use the following shortcut keys: +Um ein Bildschirmfoto von einem aktiven Fenster zu machen, verwenden Sie das folgende Tastaturkürzel: - **Drücken und halten Sie *⌘ Cmd + Umschalt + 4 + Leertaste*. Der Zeiger verwandelt sich in ein Kamerasymbol. Klicken Sie auf das Fenster, um es zu erfassen. Drücken Sie die Esc-Taste, um die Aufnahme eines Bildschirmfotos abzubrechen** -To take a screenshot of a specific area, use the following shortcut keys: +Um ein Bildschirmfoto von einem bestimmten Bereich zu machen, verwenden Sie das folgende Tastaturkürzel: - ***Drücken Sie ***⌘ Cmd + Umschalt + 5******. Ziehen Sie das Fadenkreuz, um den gewünschten Bereich auszuwählen. Lassen Sie die Maus oder das Trackpad los, um ein Bildschirmfoto zu erstellen, und drücken Sie Esc, um den Vorgang abzubrechen. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +Um ein Bildschirmfoto von der *Touch Bar* (MacBook Pro) zu erstellen, verwenden Sie das folgende Tastaturkürzel: - ***Drücken Sie ***⌘ Cmd + Umschalt + 6****** Ihr Mac nimmt die gesamte *Touch Bar* auf und speichert sie als Datei auf dem Desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +Um ein Bildschirmfoto in die Zwischenablage zu kopieren, anstatt es zu speichern, halten Sie *Strg* zusammen mit einem der oben genannten Tastaturkürzel gedrückt. Dann können Sie das Bildschirmfoto (aus der Zwischenablage) mit der Tastenkombination *Cmd + V* in ein Dokument oder ein Bild einfügen, das Sie gerade bearbeiten. Sie können auch Bildschirmfotos erstellen, indem Sie die **Vorschau** verwenden und **Bildschirmfoto aufnehmen** (von dem ausgewählten Bereich, Fenster oder dem gesamten Bildschirm) wählen. Mit der **Vorschau** können Sie Ihre Bildschirmfotos in JPG, TIFF, PDF und anderen Dateiformaten speichern. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/intro.md b/i18n/de/docusaurus-plugin-content-docs/current/intro.md index 024794e7416..567ee17b577 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ Wir entwickeln und pflegen aber auch kostenlose Browsererweiterungen für alle g ## Nicht nur Werbeblocker -AdGuard Werbeblocker kann mehr als nur Werbung blockieren. Er schützt Sie vor Online-Tracking und verbessert Ihre Privatsphäre in vielerlei Hinsicht. Je nach Produkt bietet AdGuard auch Vorteile wie DNS-Filterung für einen umfassenderen Schutz, Kindersicherung, um Ihre Kinder vor ungeeigneten Inhalten zu schützen, Filterungsprotokolle für eine bessere Kontrolle Ihres Internetverkehrs und vieles mehr. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Werbeblocker kann mehr als nur Werbung blockieren. Er schützt Sie vor Online-Tracking und verbessert Ihre Privatsphäre in vielerlei Hinsicht. Je nach Produkt bietet AdGuard auch Vorteile wie DNS-Filterung für einen umfassenderen Schutz, Kindersicherung, um Ihre Kinder vor ungeeigneten Inhalten zu schützen, Filterungsprotokolle für eine bessere Kontrolle Ihres Internetverkehrs und vieles mehr. Diese Wissensdatenbank enthält detaillierte Informationen zu all diesen Themen — Sie können direkt auf die Artikel zugreifen, die Sie interessieren. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index 928780a1280..bb41da21177 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites ändern ständig die Art und Weise, wie sie Anzeigen einbetten, und wir Die Arbeit mit blockierenden Filtern erfordert jedoch spezifische Fähigkeiten. Wenn Sie diese haben und wissen, wie man Regeln erstellt, dann gehen Sie direkt zu unserem [AdGuard Filters Repository](https://github.com/AdguardTeam/AdguardFilters) auf GitHub. Dort finden Sie viele offene Probleme (issues), die jeweils auf ein Problem mit einer Website verweisen – eine verpasste Anzeige, ein falsch positives Ergebnis usw. Wählen Sie beliebige aus und schlagen Sie Ihre eigenen Regeln in den Kommentaren vor. AdGuard-Filteringenieure prüfen Ihre Vorschläge und wenn sie sie für angemessen halten, werden Ihre Regeln zu AdGuard-Filtern hinzugefügt. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +Wenn Sie mit der Syntax unserer Filterregeln noch nicht vertraut sind oder vielleicht eine Auffrischung benötigen, finden Sie die Grundlagen der Syntax [in unserer Wissensdatenbank](/general/ad-filtering/create-own-filters). ### Belohnung {#rewards} diff --git a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index 8a6d060e543..6a105ab77a6 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Übersetzer/Korrekturleser werden sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +Wenn Sie AdGuard-Produkte, -Websites und -Wissensdatenbanken übersetzen möchten, gehen Sie zu [Crowdin](https://crowdin.com/) und registrieren/melden Sie sich dort an. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index b1c41ca8c48..c62812fd598 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ Wenn Sie eine Phrase mit Pluralformen übersetzen, können Sie möglicherweise n Hier sind einige Informationsquellen, die Sie verwenden können. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) enthält eine umfangreiche Liste von Sprachen. Die Anzahl der Pluralformen für die verschiedenen Sprachen wird auf diese Weise dargestellt: `nplurals=2`, `nplurals=4` und so weiter. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) enthält eine umfangreiche Liste von Sprachen. Die Anzahl der Pluralformen für die verschiedenen Sprachen wird auf diese Weise dargestellt: `nplurals=2`, `nplurals=4` und so weiter. Die Zahl nach dem Gleichheitszeichen `=` gibt die Anzahl der Pluralformen der jeweiligen Sprache an. Informationen zu Pluralformen finden Sie auch im [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). Die CLDR-Pluralregeln geben eine zusätzliche Wortform für Dezimalzahlen an (1,5; 2,3; 100,1…), aber wir verwenden sie nicht in AdGuard-Übersetzungen. diff --git a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 477f3d27ed2..0226157e9a2 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: AdGuard übersetzen sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Haftungsausschluss:** Sie können uns Fragen zur Übersetzung von AdGuard stellen, indem Sie eine E-Mail an [translate@adguard.com](mailto:translate@adguard.com) senden oder unserem [Telegramm-Chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy) beitreten. -When it comes to translations, we at AdGuard always heavily rely on volunteers. +Wenn es um Übersetzungen geht, sind wir bei AdGuard immer stark auf Freiwillige angewiesen. -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +Wir verwenden jetzt die [Crowdin-Plattform](https://crowdin.com/), um die Übersetzungen unserer Produkte zu verwalten. Dies ist also der richtige Ort für alle, die zu AdGuard beitragen möchten, indem sie eines unserer Produkte übersetzen. -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +Wenn Sie uns bei der Übersetzung von AdGuard auch helfen möchten, lesen Sie bitte die Informationen darüber, [wie Sie unser:e Übersetzer:in werden können](../become-translator) und [wie wir mit ihnen zusammenarbeiten](../rewards). diff --git a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 48f18914e6e..f2e9d1e639d 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: Übersetzungspriorität der Crowdin-Dateien sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +Es gibt fünf große AdGuard-Projekte auf Crowdin – [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base) und [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). Wir haben keine klaren Richtlinien, mit welchen Dateien oder Produkten des Projekts *AdGuard Applications* Sie beginnen sollen. Wählen Sie einfach ein beliebiges Produkt aus. Es gibt nur ein paar Dinge, die wir erwähnen möchten: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- Sie können die App nur in den Sprachen sehen, für die alle Übersetzungen in Crowdin abgeschlossen sind; - Wir empfehlen, die Beschreibungen für App-Stores an zweiter Stelle zu übersetzen, da die Beschreibungen ohne die Übersetzung der Produkte selbst nicht benötigt werden. Anders verhält es sich bei dem Projekt *AdGuard Websites* . Sprachen können der Website auch dann hinzugefügt werden, wenn noch keine vollständigen Übersetzungen vorhanden sind. Dies hängt jedoch davon ab, welche Dateien bereits übersetzt wurden. Deshalb empfehlen wir Ihnen, mit den wichtigsten Dateien zu beginnen – sie sind unten aufgeführt: diff --git a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 6e0502dc132..183ea17cae9 100644 --- a/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/de/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Wissensdatenbanken aktualisieren sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. Aber die Dinge ändern sich ständig, und manchmal spiegelt ein Artikel nicht mehr den aktuellen Stand der Dinge wider. +Das Ziel der AdGuard-Werbeblocker-Wissensdatenbank ist es, jedem die aktuellsten Informationen zu allen Arten von AdGuard-bezogenen Themen zur Verfügung zu stellen. Aber die Dinge ändern sich ständig, und manchmal spiegelt ein Artikel nicht mehr den aktuellen Stand der Dinge wider. Aus diesem Grund haben wir alle Inhalte unserer Wissensdatenbank auf [GitHub](https://github.com/AdguardTeam/KnowledgeBase) eingestellt, und jetzt kann buchstäblich jeder dazu beitragen, indem er/sie Bearbeitungen und Übersetzungen zu bestehenden Artikeln vorschlägt, aber auch völlig neue Artikel erstellt. ## Änderungen vorschlagen / einen neuen Artikel schreiben {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. Wenn Sie mit den Prinzipien der Arbeit mit der Plattform nicht vertraut sind, lesen Sie zunächst [GitHub-Dokumentation](https://docs.github.com/en). +Sie können Änderungen an aktuellen Artikeln vorschlagen und neue zu unserer Wissensdatenbank hinzufügen, indem Sie die oben erwähnte Funktionalität von GitHub verwenden. Wenn Sie mit den Prinzipien der Arbeit mit der Plattform nicht vertraut sind, lesen Sie zunächst [GitHub-Dokumentation](https://docs.github.com/en). -Sobald Sie startbereit sind, arbeiten Sie im [KnowledgeBase-Repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Befolgen Sie die Markdown-Regeln, wenn Sie Artikel bearbeiten oder schreiben. Folgen Sie [diesem Link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax), um mehr über die Markdown-Syntax zu erfahren. +Sobald Sie startbereit sind, arbeiten Sie im [KnowledgeBase-Repository](https://github.com/AdguardTeam/KnowledgeBase). Alle Texte in unserer Wissensdatenbank sind in `Markdown` Auszeichnungssprache geschrieben. Befolgen Sie die Markdown-Regeln, wenn Sie Artikel bearbeiten oder schreiben. Folgen Sie [diesem Link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax), um mehr über die Markdown-Syntax zu erfahren. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. Wenn Sie Änderungen oder Ergänzungen vorschlagen, beachten Sie bitte, dass alle Dokumente den Grundsätzen der Plattform entsprechen müssen. Sie können über sie in [Docusaurus Guides](https://docusaurus.io/docs/category/guides) lesen. +Die Website der Wissensdatenbank wurde mit Docusaurus 2 erstellt, einem modernen Generator für statische Websites. Wenn Sie Änderungen oder Ergänzungen vorschlagen, beachten Sie bitte, dass alle Dokumente den Grundsätzen der Plattform entsprechen müssen. Sie können über sie in [Docusaurus Guides](https://docusaurus.io/docs/category/guides) lesen. -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +Sie können die Wissensdatenbank auch lokal auf Ihrem Computer bereitstellen, um eine Vorschau auf die von Ihnen vorgeschlagenen Änderungen zu erhalten. Detaillierte Anweisungen dazu finden Sie [in der README-Datei](https://github.com/AdguardTeam/KnowledgeBase#readme) auf der GitHub-Seite dieser Wissensdatenbank. ## Artikel übersetzen {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Die Übersetzung der bestehenden Artikel der Wissensdatenbank erfolgt auf [der Crowdin-Plattform](https://crowdin.com/profile/adguard). Alle Details zu Übersetzungen und zur Arbeit mit Crowdin finden Sie [im entsprechenden Artikel](../translate/guidelines) der Wissensdatenbank von AdGuard Werbeblocker. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In einem separaten Artikel](../translate/plural-forms) haben wir ausführlich die Schwierigkeiten beschrieben, die beim Übersetzen von Strings mit Pluralformen auftreten können, und eine ausführliche Anleitung gegeben, wie man damit auf der Crowdin-Plattform arbeiten kann. +Wenn Sie an Artikeln der AdGuard-Wissensdatenbank arbeiten, stoßen Sie möglicherweise auf Strings mit Pluralformen, die Sie mit besonderer Aufmerksamkeit übersetzen sollten. [In einem separaten Artikel](../translate/plural-forms) haben wir ausführlich die Schwierigkeiten beschrieben, die beim Übersetzen von Strings mit Pluralformen auftreten können, und eine ausführliche Anleitung gegeben, wie man damit auf der Crowdin-Plattform arbeiten kann. ## An Open Issues arbeiten -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Wählen Sie ein beliebiges Thema, das Sie ansprechend finden, und beginnen Sie, daran zu arbeiten. Wenn Sie Fragen haben, können Sie diese direkt in den Kommentaren zum Problem stellen. +Manchmal gibt es [offene Probleme (open issues) auf GitHub](https://github.com/AdguardTeam/KnowledgeBase/issues) im Zusammenhang mit der Aktualisierung der Wissensdatenbank. Sie können uns dabei helfen, die Fertigstellung zu beschleunigen [genauso wie](#suggest-change) Sie andere Änderungen an der Wissensdatenbank vorschlagen würden. Wählen Sie ein beliebiges Thema, das Sie ansprechend finden, und beginnen Sie, daran zu arbeiten. Wenn Sie Fragen haben, können Sie diese direkt in den Kommentaren zum Problem stellen. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md index 3e5ff9a9eb0..734f8249635 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md @@ -9,18 +9,18 @@ Este artículo trata sobre la extensión del navegador de AdGuard, que protege s ::: -[Extensión de navegador AdGuard] (https://adguard.com/adguard-browser-extension/overview.html) es una extensión gratuita que funciona en cinco navegadores populares: Chrome, Firefox, Edge, Opera y Yandex Browser. Puedes encontrarla fácilmente en la tienda en línea de tu navegador o en nuestro sitio web oficial. +[AdGuard Browser Extension](https://adguard.com/adguard-browser-extension/overview.html) is a free extension that works in five popular browsers: Chrome, Firefox, Edge, Opera, and Yandex Browser. Puedes encontrarla fácilmente en la tienda en línea de tu navegador o en nuestro sitio web oficial. -![Extensión de navegador AdGuard para Chrome \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) +![AdGuard Browser Extension for Chrome \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) -Las extensiones de navegador incluyen funciones básicas de bloqueo de anuncios, pero no pueden compararse con los programas de escritorio completos, como [AdGuard para Windows](/adguard-for-windows/features/home-screen) y [AdGuard para Mac](/adguard-for-mac/features/main). +Browser extensions include basic ad-blocking features but cannot be compared with full-featured desktop programs, such as [AdGuard for Windows](/adguard-for-windows/features/home-screen) and [AdGuard for Mac](/adguard-for-mac/features/main). -![Disponible para los navegadores más populares \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) +![Available for most popular browsers \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) :::note -Tenemos una extensión independiente para Safari. Desde el lanzamiento de [Safari 13](https://adguard.com/es/blog/adguard-safari-1-5.html), la mayoría de las extensiones de bloqueo de anuncios han experimentado enormes problemas y muchas de ellas dejaron de funcionar. Tuvimos que desarrollar una [extensión separada para Safari](/adguard-for-safari/features/general) que tiene algunas diferencias en comparación con la extensión descrita en este artículo. +Tenemos una extensión independiente para Safari. Since the release of [Safari 13](https://adguard.com/en/blog/adguard-safari-1-5.html), most of the ad-blocking extensions have experienced huge issues and many of them stopped functioning. We had to develop a [separate extension for Safari](/adguard-for-safari/features/general) that has some differences in comparison with the extension described in this article. ::: -**No olvides que la funcionalidad de cada extensión está estrictamente limitada por las capacidades del navegador**. Entonces, si deseas obtener una protección completa, considera instalar un programa independiente para tu computadora. Hay [una razón para ello](adguard-browser-extension/comparison-standalone). +**Do not forget that the functionality of each extension is strictly limited by the browser’s capabilities.** So if you want to get full-fledged protection, consider installing a standalone program for your computer. There's [a reason why](adguard-browser-extension/comparison-standalone). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 1978b43207f..09b0dc1e5e1 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -1,5 +1,5 @@ --- -title: Comparación con aplicaciones independientes +title: Comparison to standalone apps sidebar_position: 7 --- @@ -17,10 +17,10 @@ La segunda diferencia es que las posibilidades de los bloqueadores de anuncios b Mientras que la extensión de navegador AdGuard es gratuito y fácil de instalar, y tiene filtros para bloquear anuncios y combatir amenazas en línea, las aplicaciones completas son más potentes y tienen una lista de funciones avanzadas. Consulta todas las diferencias en el cuadro comparativo que figura a continuación. -![Extensión vs. aplicación \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) +![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — dentro de las restricciones del navegador y solo en el navegador donde está instalado; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — la extensión no puede detectar solicitudes de otras extensiones. Si una extensión maliciosa o de seguimiento envía una solicitud a tu servidor para mostrarte anuncios o realizar un seguimiento de tu actividad, la extensión de navegador AdGuard no podrá bloquear esa solicitud; +`2` – the extension is unable to detect requests from other extensions. Si una extensión maliciosa o de seguimiento envía una solicitud a tu servidor para mostrarte anuncios o realizar un seguimiento de tu actividad, la extensión de navegador AdGuard no podrá bloquear esa solicitud; -`3` — no todos los tipos de anuncios y amenazas pueden ser bloqueados por las extensiones de navegador debido a ciertas limitaciones del navegador. Algunos elementos pueden llegar a la página y ralentizar el proceso de carga. Además, a diferencia de los bloqueadores de anuncios para navegador, la aplicación AdGuard bloquea los anuncios antes de que se carguen en el navegador. Esto ahorra tráfico y acelera la carga de la página. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Algunos elementos pueden llegar a la página y ralentizar el proceso de carga. Además, a diferencia de los bloqueadores de anuncios para navegador, la aplicación AdGuard bloquea los anuncios antes de que se carguen en el navegador. Esto ahorra tráfico y acelera la carga de la página. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md index 156fb606b4a..3bc5404794b 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md @@ -1,5 +1,5 @@ --- -title: Compatibilidad con la aplicación independiente +title: Compatibility with the standalone app sidebar_position: 4 --- @@ -9,16 +9,16 @@ Este artículo trata sobre la extensión del navegador de AdGuard, que protege s ::: -Mientras que AdGuard Browser Extension puede bloquear anuncios en los navegadores, los [programas independientes de AdGuard](/adguard-browser-extension/comparison-standalone) filtran todo el tráfico de tu dispositivo, incluido el de navegadores y aplicaciones. +While AdGuard Browser Extension can block ads in browsers, [AdGuard standalone programs](/adguard-browser-extension/comparison-standalone) filter all the traffic on your device, including from browsers and apps. -Si decides instalar tanto la extensión como el programa independiente en tu PC, puedes encontrar algunos problemas de compatibilidad. El problema es que en algunos casos la aplicación y la extensión pueden interferir entre sí. Algunos sitios web ya no estarán protegidos por el programa de escritorio y solo estarán protegidos por la extensión, que tiene menos opciones. Además, el filtrado puede funcionar incorrectamente en algunos sitios web. Por lo tanto, no recomendamos utilizar la extensión junto con la aplicación. +If you decide to install both the extension and the standalone program on your PC, you may encounter some compatibility issues. The problem is that in some cases the application and the extension may interfere with each other. Some websites will no longer be protected by the desktop program and will only be protected by the extension, which has fewer options. Also, filtering may work incorrectly for some websites. Therefore, we don't recommend using the extension together with the application. -Si tienes la versión de escritorio de AdGuard instalada en su PC, es mejor utilizar AdGuard Browser Assistant en lugar de la extensión. +If you have the desktop version of AdGuard installed on your PC, it is better to use AdGuard Browser Assistant instead of the extension. ## AdGuard Browser Assistant -![Asistente de navegador AdGuard \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) +![AdGuard Browser Assistant \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) -AdGuard Browser Assistant es una extensión del navegador que funciona y se siente igual que AdGuard Browser Extension, pero es mucho más liviana y no interfiere con las aplicaciones de escritorio. Puedes [leer más sobre Browser Assistant para Windows](/adguard-for-windows/browser-assistant) o [Mac](/adguard-for-mac/features/browser-assistant), o [descargarlo de nuestro sitio web](https://adguard.com/adguard-assistant/overview.html). +AdGuard Browser Assistant is a browser extension that works and feels just like AdGuard Browser Extension, but it's much lighter and doesn't interfere with the desktop apps. You can [read more about Browser Assistant for Windows](/adguard-for-windows/browser-assistant) or [Mac](/adguard-for-mac/features/browser-assistant), or [download it from our website](https://adguard.com/adguard-assistant/overview.html). -El Asistente de Navegador AdGuard está disponible en todos los navegadores principales. +AdGuard Browser Assistant is available in all major browsers. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index 9f822d5ab27..95bfd068740 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ Todos los filtros se agrupan según tu función. Por ejemplo, existen categoría ## Filtros personalizados -Si bien las características de otros grupos de filtros son más o menos autoexplicativas, hay un grupo llamado _Personalizado_ que puede generar dudas adicionales. +Si bien las características de otros grupos de filtros son más o menos predecibles, hay un grupo llamado _Personalizado_ que puede generar dudas adicionales. ![Filtros personalizados \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 606de710329..308c637cea6 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -19,7 +19,7 @@ En la pestaña _General_, puedes permitir los anuncios de búsqueda y la [autopr Además, aquí puedes habilitar [_Protección contra phishing y malware_](/general/browsing-security). -Puedes guardar tu configuración haciendo clic en el botón _Exportar configuración_. La configuración se guardará como un archivo .json. Para importar la configuración guardada previamente, utiliza la función _Importar configuración_. Incluso puedes usarlo para cambiar rápidamente entre diferentes perfiles de configuración o incluso para transferir configuraciones entre diferentes navegadores. +Puedes guardar tu configuración haciendo clic en el botón _Exportar configuración_. La configuración se guardará como un archivo .json. Para subir la configuración previamente guardada, utiliza la función _Importar configuración_. Incluso puedes usarlo para cambiar rápidamente entre diferentes perfiles de configuración o incluso para transferir configuraciones entre diferentes navegadores. ## Configuraciones adicionales {#misc} diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md index baa35a9ca32..09c8f57b282 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md @@ -71,4 +71,4 @@ En la ventana de diálogo abierta, haz clic en *Agregar extensión* para instala ## Cómo instalar la extensión de navegador AdGuard para Safari -AdGuard para Safari no es una extensión de navegador común. Puedes leer más sobre esto en el [artículo](/adguard-for-safari/features/general). O puedes [descargar el archivo de instalación](https://agrd.io/safari_release) directamente desde esta página. +AdGuard para Safari no es una extensión de navegador común. You can read more about it in a [dedicated article](/adguard-for-safari/features/general). O puedes [descargar el archivo de instalación](https://agrd.io/safari_release) directamente desde esta página. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index 053d549c3a4..4b3bcaab272 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Páginas protegidas por el navegador -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md index 95f57fa1a43..4269d9e304c 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md @@ -53,11 +53,11 @@ sidebar_position: 1 :::note -AdGuard se compromete a proteger tu privacidad. Seguimos estrictamente nuestra [Política de Privacidad](https://adguard.com/privacy/browser-extension.html) y no recopilamos ninguna información privada sobre los usuarios. Antes de enviar tus registros al equipo de soporte, revisa el archivo, ya que puede contener información adicional que no deseas compartir. Si contiene información personal, te recomendamos que la elimines primero. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/browser-extension.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -Ahora que has recopilado los registros, sigue estos pasos para enviarlos a nuestro equipo de desarrollo: +Now that you have collected the logs, please follow these steps to submit them to our development team: -1. Informa el error en [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). -2. Envía tu archivo con los registros y el tiempo de reproducción a `devteam@adguard.com` y añade un enlace a tu GitHub issue. También puedes cargar el archivo en Google Drive y agregarle el enlace en lugar de adjuntar el archivo. +1. Report the bug on [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). +2. Send your archive with logs and playback time to `devteam@adguard.com` and add a link to your GitHub issue. You can also upload the archive to Google Drive and add the link to it instead of attaching the file. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index bb8d4112567..e5d954f0ae7 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ Desde el menú contextual, también puedes acceder a las estadísticas de la apl ### Aplicaciones “libres de problemas” y “problemáticas” -Most apps work correctly when filtered. Para dichas aplicaciones, su tráfico se dirige a través de AdGuard y se filtra de forma predeterminada. +La mayoría de las aplicaciones funcionan correctamente cuando el filtrado está habilitado. Para dichas aplicaciones, su tráfico se dirige a través de AdGuard y se filtra de forma predeterminada. Algunas aplicaciones, como el Administrador de descargas, la radio y las aplicaciones del sistema con UID 1000 y 1001 (por ejemplo, los servicios de Google Play), son "problemáticas" y pueden funcionar incorrectamente cuando se enrutan a través de AdGuard. Es por eso que es posible que veas la siguiente advertencia al intentar enrutar o filtrar todas las aplicaciones: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 5f2637fe448..1ca0aedf18c 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ Se puede acceder al módulo de protección DNS tocando la pestaña _Protección_ :::tip -La protección DNS funciona de manera diferente al bloqueo habitual de anuncios y rastreadores. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +La protección DNS funciona de manera diferente al bloqueo habitual de anuncios y rastreadores. Tu cámara [obtén más información sobre esto y cómo funciona en un artículo dedicado](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index bd2a3d1bde3..9c387ddac51 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ Para eliminar una regla o aplicación de _Reglas personalizadas_, deslízala hac ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index 5f7a819ef17..8d08ee3e635 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Estas son las características activas de los niveles preconfigurados: k. _Eliminar encabezado X-Client-Data_. Esta función evita que Google Chrome envíe información sobre su versión y modificaciones a los dominios de Google (incluidos DoubleClick y Google Analytics) -Puedes modificar configuraciones individuales en _Protección de seguimiento_ y crear una configuración personalizada. Cada configuración tiene una descripción que te ayudará a comprender su función. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +Puedes modificar configuraciones individuales en _Protección de seguimiento_ y crear una configuración personalizada. Cada configuración tiene una descripción que te ayudará a comprender su función. [Obtén más información sobre lo que hacen las distintas configuraciones de _Protección de seguimiento_](/general/stealth-mode) y utilízalas con precaución, ya que algunas pueden interferir con la funcionalidad de los sitios web y las extensiones del navegador. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 4193cc58492..0e13e44aa0b 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ Este artículo trata sobre AdGuard para Android, un bloqueador de anuncios multi Debido a las medidas de seguridad del sistema operativo Android, algunas funciones de AdGuard solo están disponibles en dispositivos rooteados. Aquí está la lista de ellos: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- El **filtrado HTTPS en la mayoría de las aplicaciones** requiere [instalar un certificado CA en el almacén del sistema](/adguard-for-android/features/settings#security-certificates), ya que la mayoría de las aplicaciones no confían en los certificados del almacén del usuario. La instalación de un certificado en el almacén del sistema solo es posible en dispositivos rooteados - El [**modo de enrutamiento proxy automático**](/adguard-for-android/features/settings#routing-mode) requiere acceso raíz debido a las restricciones de Android en el filtrado de tráfico en todo el sistema - El [**modo de enrutamiento proxy manual**](/adguard-for-android/features/settings#routing-mode) requiere acceso de root en Android 10 y versiones posteriores, ya que ya no es posible determinar el nombre de la aplicación asociada con un conexión filtrada por AdGuard diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 466413ebd7c..8ce1b695987 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -27,7 +27,7 @@ _Automatización_ te permite administrar AdGuard a través de aplicaciones de ta _Watchdog_ ayuda a proteger AdGuard para que no sea desactivado por el sistema ([leer más sobre el modo de ahorro de batería de Android](/adguard-for-android/solving-problems/background-work/)). El valor que ingreses será el intervalo en segundos entre verificaciones del watchdog. -_Nivel de registro_ define qué datos sobre el funcionamiento de la aplicación deben registrarse. De forma predeterminada, la aplicación recopila datos sobre sus eventos. El nivel _Debug_ registra más eventos; habilítalo si el equipo de AdGuard lo solicita para ayudarlos a comprender mejor el problema. [Read more about collecting and sending logs](/adguard-for-android/solving-problems/log/) +_Nivel de registro_ define qué datos sobre el funcionamiento de la aplicación deben registrarse. De forma predeterminada, la aplicación recopila datos sobre sus eventos. El nivel _Debug_ registra más eventos; habilítalo si el equipo de AdGuard lo solicita para ayudarlos a comprender mejor el problema. [Más información sobre la recopilación y el envío de registros](/adguard-for-android/solving-problems/log/) ![Avanzado \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) @@ -59,7 +59,7 @@ Si activas demasiados filtros, es posible que algunos sitios web funcionen incor ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. Para instalar scripts de usuario, necesitas un administrador de userscripts especial. AdGuard tiene una funcionalidad de este tipo y te permite añadir usercripts por URL o desde un archivo. +Los scripts de usuario son miniprogramas escritos en JavaScript que amplían la funcionalidad de uno o más sitios web. Para instalar scripts de usuario, necesitas un administrador de userscripts especial. AdGuard tiene una funcionalidad de este tipo y te permite añadir usercripts por URL o desde un archivo. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ En esta sección podrás encontrar información sobre tu licencia y gestionarla: - Compra una licencia de AdGuard para activar [las funciones de la versión completa](/adguard-for-android/features/free-vs-full) - Inicia sesión en tu cuenta AdGuard o ingresa la clave de licencia para activar tu licencia - Regístrate para activar tu período de prueba de 7 días si aún no lo has usado -- Refresh the license status from the three-dots menu (⋮) +- Actualiza el estado de la licencia desde el menú de tres puntos - Abre la cuenta AdGuard para administrar tu licencia allí - Restablece tu licencia. Por ejemplo, si has alcanzado el límite de dispositivos para esta licencia y deseas aplicar otra diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index f690d259b75..397721f4fc4 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Option 2 To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index eead7cda606..08d10ceb5b7 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -15,17 +15,17 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. +En este artículo, te guiaremos a través del proceso de recopilación de registros de depuración, un paso de solución de problemas esencial para resolver problemas complejos que puedan surgir. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. :::note -AdGuard se compromete a proteger tu privacidad. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Antes de enviar tus registros al equipo de soporte, revisa el archivo, ya que puede contener información adicional que no deseas compartir. Si contiene información personal, te recomendamos que la elimines primero. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index ae68e0f77a2..95e39b0e4ce 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -19,7 +19,7 @@ Sometimes a regular log may not be sufficient to identify the origin of the prob :::note -AdGuard se compromete a proteger tu privacidad. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Antes de enviar tus registros al equipo de soporte, revisa el archivo, ya que puede contener información adicional que no deseas compartir. Si contiene información personal, te recomendamos que la elimines primero. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index f3ca4ef8e81..2ae6fcb7293 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Toda conexión a Internet cifrada tiene una parte no cifrada. Este es el primer paquete que contiene el nombre del servidor al que te estás conectando. La tecnología Encrypted Client Hello resuelve este problema y cifra la última parte de la información no cifrada. To benefit from it, enable the *Encrypted Client Hello* option. Utiliza un proxy DNS local para buscar la configuración de ECH para el dominio. If it is found, Client Hello packet will be encrypted. +Toda conexión a Internet cifrada tiene una parte no cifrada. Este es el primer paquete que contiene el nombre del servidor al que te estás conectando. La tecnología Encrypted Client Hello resuelve este problema y cifra la última parte de la información no cifrada. To benefit from it, enable the *Encrypted Client Hello* option. Utiliza un proxy DNS local para buscar la configuración de ECH para el dominio. Si se encuentra, el paquete ClientHello se cifrará. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 106adb46393..00000000000 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Versión gratuita vs. versión completa -sidebar_position: 9 ---- - -:::info - -Este artículo trata sobre AdGuard para iOS, un bloqueador de anuncios multifuncional que protege tu dispositivo a nivel del sistema. Para ver cómo funciona, [descarga la app de AdGuard](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 6b22222807d..f208b659845 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -13,15 +13,15 @@ Este artículo trata sobre AdGuard para iOS, un bloqueador de anuncios multifunc ### iPhone -Requiere iOS 13 o posterior. +Requires iOS 13 or later. ### iPad -Requiere iPadOS 13 o posterior. +Requires iPadOS 13 or later. ### iPod touch -Requiere iOS 13 o posterior. +Requires iOS 13 or later. ## Instalación de AdGuard para iOS @@ -43,11 +43,11 @@ AdGuard Pro es una versión de pago de AdGuard para iOS, que ofrece un conjunto ![En la pantalla principal de App Store, toca Buscar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Escribe *adguard* en el formulario de búsqueda y luego toca la cadena *AdGuard Pro — adblock* que se mostrará entre los resultados de búsqueda. +Escribe *adguard* en el formulario de búsqueda y luego toca la cadena *AdGuard Pro - bloqueador de anuncios* que se mostrará entre los resultados de búsqueda. ![Escribe "AdGuard" en la barra de búsqueda *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -En la página abierta de la App Store, toca el botón con el costo de la licencia bajo la cadena *AdGuard Pro — adblock*, y luego toca *COMPRAR*. Es posible que se te pida que introduzcas tu nombre de usuario y contraseña de tu Apple ID. Escríbelo y espera a que se complete la instalación. +En la página abierta de la App Store, toca el botón con el costo de la licencia bajo la cadena *AdGuard Pro - adblock*, y luego toca *COMPRAR*. Es posible que se te pida que introduzcas tu nombre de usuario y contraseña de tu Apple ID. Escríbelo y espera a que se complete la instalación. ![Toca GET debajo de la aplicación AdGuard *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index 60dcfc93be1..8ba09f03a6b 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ Este artículo trata sobre AdGuard para iOS, un bloqueador de anuncios multifunc 1. Elige un vídeo y toca *Compartir*. 1. Toca *Más*, luego selecciona *Bloquear anuncios de YouTube (por AdGuard)*. -El vídeo ahora se abre en el reproductor sin anuncios de AdGuard. +AdGuard abrirá su reproductor de vídeo sin anuncios. ## Cómo bloquear anuncios en YouTube en Safari @@ -31,4 +31,4 @@ Asegúrate de haber dado acceso a AdGuard a todos los sitios web. Puedes comprob 1. Elige un vídeo y pulsa *Compartir*. 1. Toca *Bloquear anuncios de YouTube (por AdGuard)*. -El vídeo ahora se abre en el reproductor sin anuncios de AdGuard. +AdGuard abrirá su reproductor de vídeo sin anuncios. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index 59ea9011e9c..44aa04ccebc 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ Para ir a la *Configuración de bajo nivel*, toca el icono del engranaje en la p Hay dos modos principales de túnel: *Dividido* y *Completo*. El *modo de túnel dividido* proporciona compatibilidad de AdGuard y las aplicaciones llamadas "VPN personal". En *Túnel completo*, ninguna otra VPN puede funcionar simultáneamente con AdGuard. -Hay una característica específica del modo *Split-Tunnel*: en caso de un rendimiento deficiente del proxy DNS, por ejemplo, si la respuesta del servidor DNS de AdGuard no se devuelve a tiempo, iOS redirigirá el tráfico a través del servidor DNS especificado en la configuración de iOS. Por el momento, no se bloquea ningún anuncio y el tráfico DNS no está cifrado. +Hay una característica específica del modo *Túnel dividido*: si el proxy DNS no funciona bien, por ejemplo, si la respuesta del servidor de AdGuard DNS no se devolvió a tiempo, iOS la "comercializará" y redirigirá el tráfico a través del servidor DNS especificado en la configuración de iOS. Por el momento, no se bloquea ningún anuncio y el tráfico DNS no está cifrado. -En *Túnel completo*, solo se utiliza el servidor DNS especificado en la configuración de AdGuard. Si no responde, el Internet simplemente no funcionará. El modo *Full-Tunnel* activado puede afectar negativamente al rendimiento de algunos programas (por ejemplo, FaceTime) y causar problemas de actualización de aplicaciones. +En *Túnel completo*, solo se utiliza el servidor DNS especificado en la configuración de AdGuard. Si no responde, el Internet simplemente no funcionará. Activar el modo *Túnel completo* puede causar un funcionamiento incorrecto de algunos programas (por ejemplo, Facetime) y provocar problemas con las actualizaciones de las aplicaciones. De forma predeterminada, AdGuard utiliza *Túnel dividido* como la opción más estable. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 8b83cb0ae48..0f94077b281 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Tiempo, en segundos, antes de enviar otra sonda de mantenimiento de actividad a #### `network.https.ech.enabled` -Utiliza un proxy DNS local para buscar configuraciones en las listas de configuración de ECH. If found, encrypts Client Hellos. +Utiliza un proxy DNS local para buscar configuraciones en las listas de configuración de ECH. Si se encuentra, encripta ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 1607c9f41ef..2c0a0beea15 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ Si usas Flutter junto con AdGuard en el modo "Extensión de red" (o cualquier ot #### Aplicaciones VPN con API antigua -A pesar de que AdGuard se muestra como una VPN en la configuración del sistema, no debería causar ningún conflicto al trabajar junto con otras aplicaciones basadas en VPN. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +A pesar de que AdGuard se muestra como una VPN en la configuración del sistema, no debería causar ningún conflicto al trabajar junto con otras aplicaciones basadas en VPN. Sin embargo, si estás utilizando una aplicación basada en VPN que se descargó desde fuera de la App Store, existe la posibilidad de que utilice la antigua API de VPN y debas excluirla del filtrado: 1. Abre el menú de AdGuard. 1. Selecciona *Preferencias...*. @@ -79,9 +79,9 @@ Apple ya ha solucionado estos problemas, pero se pueden encontrar en las version ### Compatibilidad con Little Snitch 5 -En este momento, el modo de extensión de red en AdGuard no es compatible con [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. Este problema está causado directamente por un error en Big Sur y ya le hemos informado a Apple al respecto. Esto nos hace creer que este problema se resolverá en una de las próximas actualizaciones. +En este momento, el modo de extensión de red en AdGuard no es compatible con [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). Cuando ambos se están ejecutando, existe la posibilidad de encontrar problemas con el comportamiento de varias aplicaciones, incluso si AdGuard no las filtra. Este problema está causado directamente por un error en Big Sur y ya le hemos informado a Apple al respecto. Esto nos hace creer que este problema se resolverá en una de las próximas actualizaciones. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. Recomendamos cambiar al modo de filtrado [**Proxy automático**](#automatic-proxy) cuando se ejecuta AdGuard junto con Little Snitch en Big Sur, al menos hasta que Apple solucione el error. +Hay que decir que este problema no se puede solucionar deshabilitando el monitoreo de conexiones en Little Snitch, porque esta acción no descarga la extensión de Little Snitch del sistema. Recomendamos cambiar al modo de filtrado [**Proxy automático**](#automatic-proxy) cuando se ejecuta AdGuard junto con Little Snitch en Big Sur, al menos hasta que Apple solucione el error. ### Compatibilidad con proxies locales @@ -121,7 +121,7 @@ En primer lugar, necesitas un servidor que funcione para tu proxy. Lo más proba :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +Puedes encontrar más información sobre cómo comenzar en el [Sitio web de Shadowsocks](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index 49bf563c936..93620810e7c 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ Este artículo trata sobre AdGuard para Mac, un bloqueador de anuncios multifunc ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". Este es un nuevo mecanismo de seguridad que apareció en High Sierra y requiere que permitas explícitamente la instalación de una extensión del sistema de terceros. Para completar la instalación de AdGuard, tienes que permitir manualmente la carga de la extensión en *Preferencias del Sistema* → *Seguridad & Privacidad* → *General*. +Durante la instalación de AdGuard en macOS High Sierra (o versiones posteriores), es posible que veas un mensaje: "Extensión del sistema bloqueada". Este es un nuevo mecanismo de seguridad que apareció en High Sierra y requiere que permitas explícitamente la instalación de una extensión del sistema de terceros. Para completar la instalación de AdGuard, tienes que permitir manualmente la carga de la extensión en *Preferencias del Sistema* → *Seguridad & Privacidad* → *General*. ![Permitir la instalación de extensiones en la configuración](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index f0cbb81831d..02580830bde 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ Como consecuencia, AdGuard no puede funcionar junto con iCloud Private Relay y l 1. iCloud Private Relay se aplica a las conexiones a nivel de biblioteca, antes de que alcancen el nivel de socket, donde opera AdGuard. 2. iCloud Private Relay utiliza QUIC, que AdGuard no puede filtrar porque el filtrado HTTP/3 aún no está disponible. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. En consecuencia, AdGuard bloquea QUIC, incluido el tráfico de retransmisión privada de iCloud; de lo contrario, el bloqueo de anuncios es imposible. 4. Cuando usas iCloud Private Relay y cambias AdGuard al modo de "túnel dividido", no puedes abrir sitios web en Safari. 5. Para solucionar este problema en Monterey, aplicamos la regla de "ruta predeterminada". Cuando Private Relay ve esa regla, se desactiva automáticamente. Entonces, AdGuard funciona perfectamente en Monterey, pero iCloud Private Relay se desactiva. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 15f5b9d69bb..94c64fc07cb 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ En la pestaña Acerca de, verás información sobre la versión actual de tu pro :::note Importante -AdGuard para Safari se puede descargar de forma gratuita [desde App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). Encontrarás instrucciones detalladas de instalación en la [Base de conocimientos](/adguard-for-safari/installation/). +AdGuard para Safari se puede descargar de forma gratuita [desde App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). Hay instrucciones de configuración detalladas disponibles en la [Base de conocimientos](/adguard-for-safari/installation/). ::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index edc408c9a4c..a808b62afbe 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: Reglas de usuario sidebar_position: 4 --- -Las reglas de usuario se pueden utilizar para personalizar el bloqueo de anuncios. Pueden añadirse manualmente, importarse o crearse automáticamente al bloquear un elemento en la página. Para agregar tus propias reglas de filtrado, utiliza una [sintaxis especial](/general/ad-filtering/create-own-filters). +Las reglas de usuario se pueden utilizar para personalizar el bloqueo de anuncios. Pueden añadirse manualmente, importarse o crearse automáticamente al bloquear un elemento en la página. Para añadir tus propias reglas de filtrado, utiliza una [sintaxis especial](/general/ad-filtering/create-own-filters). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index af09fc2577b..c840a476d2a 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -21,10 +21,10 @@ Ahora puedes enviar este archivo a support@adguard.com o adjuntarlo a tu informe :::note -AdGuard se compromete a proteger tu privacidad. Seguimos estrictamente nuestra [Política de Privacidad](https://adguard.com/privacy/safari.html) y no recopilamos ninguna información privada sobre los usuarios. Antes de enviar tus registros al equipo de soporte, revisa el archivo, ya que puede contener información adicional que no deseas compartir. Si contiene información personal, te recomendamos que la elimines primero. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/safari.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -1. Abre el [repositorio GitHub de AdGuard para Safari](https://github.com/AdguardTeam/AdGuardForSafari/issues) y haz clic en _New issue_. -2. Envía el archivo de registro a devteam@adguard.com. Incluye la hora del error y adjunta un enlace a tu issue o su número (aparece como #número junto al título). - Alternativamente, puedes transferir el archivo de registro en Google Drive y enviarlo a devteam@adguard.com. Agrega el enlace del archivo a tu problema de GitHub. +1. Open the [AdGuard for Safari GitHub repo](https://github.com/AdguardTeam/AdGuardForSafari/issues) and click _New issue_. +2. Send the log file to devteam@adguard.com. Include the time of the bug and attach a link to your issue or its number (it appears as #number next to the title). + Alternatively, you can upload the log file to Google Drive and send it to devteam@adguard.com. Add the file link to your GitHub issue. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 67b5064687b..d68f8257ba3 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ El Asistente de AdGuard es un asistente antiguo que puede utilizar si el [nuevo Esta es una extensión personalizada diseñada para combatir la técnica de reinsertar anuncios bloqueados: la llamada elusión de bloqueadores de anuncios. Ambos son métodos avanzados de bloqueo de publicidad que siguen ganando popularidad entre los anunciantes. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra es esencialmente un miniprograma que cambia la forma en que funcionan las páginas de tal manera que a los sitios les resulta mucho más difícil utilizar los métodos mencionados anteriormente para evitar los bloqueadores. **AdGuard Popup Blocker** -Esta extensión evita que se abran ventanas emergentes cuando visualizas páginas web. Algunas ventanas emergentes se consideran útiles: pueden contener configuraciones para la administración del sitio o información de referencia adicional que se muestra al hacer clic en un enlace. Es por eso que puedes desactivar el bloqueador si es necesario. Esta extensión tampoco funciona en sitios web agregados a la lista de excepciones de AdGuard. Está desactivado de forma predeterminada, pero puedes activarlo en la configuración de la aplicación. You will find more detailed information about this extension in our Knowledge Base. +Esta extensión evita que se abran ventanas emergentes cuando visualizas páginas web. Algunas ventanas emergentes se consideran útiles: pueden contener configuraciones para la administración del sitio o información de referencia adicional que se muestra al hacer clic en un enlace. Es por eso que puedes desactivar el bloqueador si es necesario. Esta extensión tampoco funciona en sitios web agregados a la lista de excepciones de AdGuard. Está desactivado de forma predeterminada, pero puedes activarlo en la configuración de la aplicación. Encontrarás información más detallada sobre esta extensión en nuestra base de conocimiento. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust te permite ver la reputación de cada sitio web en función de las ### Red -El penúltimo módulo está dedicado al filtrado de redes y aquí encontrarás opciones adicionales relacionadas con la red. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Estas son precauciones adicionales importantes para filtrar mejor tu espacio web. La mayoría de los sitios web utilizan ahora HTTPS y lo mismo se aplica a la publicidad. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +El penúltimo módulo está dedicado al filtrado de redes y aquí encontrarás opciones adicionales relacionadas con la red. Dos de ellos están habilitados de forma predeterminada: _Habilitar filtrado de tráfico_ y _Filtrar protocolo HTTPS_. Estas son precauciones adicionales importantes para filtrar mejor tu espacio web. La mayoría de los sitios web utilizan ahora HTTPS y lo mismo se aplica a la publicidad. En muchos sitios, como youtube.com, facebook.com y twitter.com, es imposible eliminar anuncios sin el filtrado HTTPS. Así que mantén habilitada la función _Filtrar protocolo HTTPS_ a menos que tengas una buena razón para no hacerlo. ![Configuración de red \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index b0849aa3ec4..a0ecbd4651c 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ _Configuración_ es la sección que requiere mayor atención. Aquí es donde pod ### Configuración general -Aquí puedes configurar el idioma y el tema (Oscuro o Claro), habilitar el inicio de AdGuard al iniciar el sistema y las actualizaciones automáticas silenciosas, elegir el canal de actualización y filtrar el intervalo de verificación de actualización. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +Aquí puedes configurar el idioma y el tema (Oscuro o Claro), habilitar el inicio de AdGuard al iniciar el sistema y las actualizaciones automáticas silenciosas, elegir el canal de actualización y filtrar el intervalo de verificación de actualización. Además, Configuración es el lugar al que acudir si AdGuard para Windows no funciona correctamente y el equipo de soporte te pidió que [recopiles _Registros de depuración_](/adguard-for-windows/solving-problems/adguard-logs.md). ![Configuración avanzada \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ Existen varios sitios web a los que se debe restringir el acceso desde una PC ut El módulo verifica el contenido de las páginas web abiertas en el navegador y filtra aquellas con contenido no deseado para los niños: imágenes y textos para adultos, lenguaje grosero, violencia, propaganda de drogas, etc. La configuración del Control parental está protegida con contraseña para que el niño no pueda eludir las restricciones. Este módulo no sólo bloquea direcciones a sitios no deseados sino que también puede eliminar de los resultados de búsqueda los enlaces que no son apropiados para niños. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. También puedes marcar la casilla _Bloquear descarga de archivos ejecutables_ para evitar que tu hijo descargue e instale software en la computadora. Hay dos opciones más en el módulo _Control parental_: puedes seleccionar un usuario específico de Windows para que esté protegido por _Control parental_ y establecer una contraseña para proteger la configuración de AdGuard contra cambios. +En el módulo de Control parental puedes habilitar la _Búsqueda segura_ y administrar la _lista de bloqueo_ y la _lista de permitidos_ para personalizar cómo funciona esta opción. También puedes marcar la casilla _Bloquear descarga de archivos ejecutables_ para evitar que tu hijo descargue e instale software en la computadora. Hay dos opciones más en el módulo _Control parental_: puedes seleccionar un usuario específico de Windows para que esté protegido por _Control parental_ y establecer una contraseña para proteger la configuración de AdGuard contra cambios. ![Control parental \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index fefbc8ca9a0..824276109c6 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ Este artículo trata sobre AdGuard para Windows, un bloqueador de anuncios multi To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index d85b23ee348..5ec492ae9bc 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard logs +title: Cómo recopilar registros de AdGuard sidebar_position: 3 --- @@ -15,7 +15,7 @@ Los datos y/o archivos proporcionados en los registros se procesan de acuerdo co ::: -Para analizar y diagnosticar diferentes problemas que puedan surgir, el servicio de soporte de AdGuard puede necesitar archivos de registro. These files contain records about errors and other events that occur with the software. A continuación se muestran breves instrucciones que describen la forma de obtener los archivos de registro y enviarlos al servicio de soporte si es necesario. +Para analizar y diagnosticar diferentes problemas que puedan surgir, el servicio de soporte de AdGuard puede necesitar archivos de registro. Estos archivos contienen registros sobre errores y otros eventos que ocurren con el software. A continuación se muestran breves instrucciones que describen la forma de obtener los archivos de registro y enviarlos al servicio de soporte si es necesario. :::note @@ -25,7 +25,7 @@ AdGuard se compromete a proteger tu privacidad. Seguimos estrictamente nuestra [ ### Registros de depuración {#debug-logs} -1. Abre la configuración de AdGuard. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Abre la configuración de AdGuard. Ve a la sección *Configuración general*, desplázate hasta el final de la pantalla y cambia el *Nivel de registro* a *Depuración*. ![Nivel de registro de depuración *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard se compromete a proteger tu privacidad. Seguimos estrictamente nuestra [ Te recomendamos encarecidamente que tomes nota de la hora exacta en la que reprodujo el problema: ayudará a nuestro equipo de soporte a encontrar entradas de registro relevantes y resolver el problema más rápido. -1. Export the collected logs using the *Export Logs* button. +1. Exporta los registros grabados usando el botón *Exportar registros*. ![Exportar registros *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Guarda el archivo en cualquier carpeta. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Depurar* el nivel de registro ralentizará la aplicación. +1. **Importante**: después de exportar los registros, vuelve a establecer el nivel de registro en *Estándar*. *Depurar* el nivel de registro ralentizará la aplicación. 1. Envía el archivo al servicio de soporte de AdGuard a **support@adguard.com**, describe el problema y no olvides mencionar el momento en que reprodujo el problema. @@ -65,7 +65,7 @@ Si tienes una versión anterior de AdGuard para Windows, ejecuta la aplicación Te recomendamos encarecidamente que tomes nota de la hora exacta en la que reprodujo el problema: ayudará a nuestro equipo de soporte a encontrar entradas de registro relevantes y resolver el problema más rápido. -1. Export the collected logs using the *Export Logs* button. +1. Exporta los registros grabados usando el botón *Exportar registros*. ![Exportar registros *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index f1d36c7e234..1f03123c9fc 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ Este artículo contiene algunos de los errores más comunes que puedes encontrar ### Error 5: Acceso denegado {#error-5} -This error message appears when required permissions haven't been granted. Puede haber varias razones por las que el instalador de AdGuard no tenga los permisos necesarios para finalizar correctamente el proceso de instalación. Puedes intentar los siguientes pasos: +Este error ocurre cuando hay algún problema con los permisos. Puede haber varias razones por las que el instalador de AdGuard no tenga los permisos necesarios para finalizar correctamente el proceso de instalación. Puedes intentar los siguientes pasos: -- Temporarily disable your antivirus. Algunos de ellos pueden interferir con la instalación, dependiendo de su configuración. +- Desactiva temporalmente tu antivirus. Algunos de ellos pueden interferir con la instalación, dependiendo de su configuración. - Elige otra carpeta de instalación. Es posible que la carpeta de instalación actual tenga algunas restricciones de acceso. También asegúrate de no seleccionar una unidad externa, una unidad virtual, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. Puede ### Error 112: El disco está lleno, Error 1632: Carpeta temporal llena o inaccesible {#error-112} -Estos son dos errores diferentes con soluciones muy similares. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. Hay varias cosas que puedes intentar para solucionar el problema: +Estos son dos errores diferentes con soluciones muy similares. Como sugieren sus nombres, el instalador de AdGuard no encontró suficiente espacio en el disco para completar la instalación. Hay varias cosas que puedes intentar para solucionar el problema: - Desinstale algunos programas o elimina archivos innecesarios de la unidad en la que intentabas instalar AdGuard. -- Descarga, instala y ejecuta [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), un software gratuito de Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. Ayudará a limpiar algo de espacio en disco. +- Descarga, instala y ejecuta [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), un software gratuito de Malwarebytes. Entre otras cosas, limpiará tu sistema de todo tipo de archivos "sobrantes" que quedan después de desinstalar incorrectamente programas. Ayudará a limpiar algo de espacio en disco. - Reinicia tu computadora. A veces, los archivos temporales pueden ocupar una cantidad considerable de espacio en disco, y reiniciar tu PC es la forma más confiable de deshacerse de ellos. ### Error 1601: no se puede acceder al instalador de Windows {#error-1601} -You could say this is a particular subcategory of Error 1603. Las posibles soluciones son similares: +Se podría decir que este es un subcaso particular del Error 1603. Las posibles soluciones son similares: - Inicia y vuelve a registrar el servicio Microsoft Installer. Esto puede resultar laborioso. @@ -75,7 +75,7 @@ Este error ocurre cuando hay varias instancias del instalador de AdGuard iniciad - Reinicia tu PC y vuelve a iniciar el instalador. Al reiniciar el ordenador, se detendrán todos los procesos en curso, incluidas todas las copias del instalador. -- Don't make multiple clicks on the installer even if it doesn't start right away. A veces, la interfaz de usuario del instalador puede tardar unos segundos en mostrarse. +- No hagas varios clics en el instalador incluso si no se inicia de inmediato. A veces, la interfaz de usuario del instalador puede tardar unos segundos en mostrarse. ### Error 1638: Ya está instalada otra versión de este producto {#error-1638} @@ -83,14 +83,14 @@ Es muy probable que ya hayas instalado AdGuard. - Verifica si AdGuard ya está instalado en tu ordenador. Puedes hacerlo presionando la tecla *Win* y escribiendo ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Desinstala AdGuard usando nuestra herramienta especial de desinstalación [](../../installation#advanced) y luego repite la instalación. +- Tal vez haya algunos archivos sobrantes de una instalación anterior de AdGuard. Desinstala AdGuard usando nuestra herramienta especial de desinstalación [](../../installation#advanced) y luego repite la instalación. ### Otros errores {#other} Si has encontrado un error que no se encuentra en la lista anterior, es posible que podamos resolverlo nosotros mismos. Pero para hacerlo, necesitamos tus archivos de registro. Realiza los siguientes pasos: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Busca y archiva los **Registros de instalación de AdGuard** como se describe en [este artículo](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [Este artículo](../system-logs) explica cómo hacerlo. +- Busca y guarda en el disco los registros del **Event Viewer**. [Este artículo](../system-logs) explica cómo hacerlo. - Envía por correo electrónico todos estos archivos de los dos pasos anteriores al equipo de soporte vía **support@adguard.com** y describe el problema en el cuerpo del mensaje. Nuestro equipo de soporte técnico te responderá lo antes posible. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d57927162b7..58db562fe8b 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ Este artículo trata sobre AdGuard para Windows, un bloqueador de anuncios multi AdGuard para Windows permite a los usuarios especificar una dirección de servidor DNS para resolver consultas en lugar del servidor DNS del sistema, que proporciona tu ISP si no se anula en la configuración del sistema. El uso de un servidor DNS no predeterminado puede proteger tu tráfico DNS de la interceptación del ISP. Además, al elegir un servidor DNS cifrado y/o filtrado, obtienes otra capa de protección contra malos actores y anuncios molestos. -Muchos usuarios de AdGuard para Windows aprecian la función de protección DNS. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. En este artículo, te contamos por qué ocurre esto y cómo evitarlo. +Muchos usuarios de AdGuard para Windows aprecian la función de protección DNS. Pero algunos de ellos se encuentran con el siguiente problema: una comprobación en un sitio web como https://ipleak.net/ muestra que las solicitudes son gestionadas por el servidor DNS predeterminado en lugar del seleccionado. En este artículo, te contamos por qué ocurre esto y cómo evitarlo. ## Dirección DNS Bootstrap @@ -21,7 +21,7 @@ Las direcciones del servidor DNS pueden escribirse como IP o como nombres de dom - ve a *Configuración avanzada* - desplázate hacia abajo hasta la sección *Lista de direcciones de arranque personalizadas* -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- ingresa la dirección de arranque personalizada en formato de dirección IP (puedes usar [la lista de proveedores de DNS conocidos](https://adguard-dns.io/kb/general/dns-providers/)) - haz clic en *Guardar* ## Servidor DNS fallback @@ -33,7 +33,7 @@ Puede ocurrir que AdGuard no pueda llegar al servidor especificado debido a una - ve a *Configuración avanzada* - desplázate hacia abajo hasta la sección *Servidores fallback* - marca la opción *Usar servidores personalizados* -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- luego busca la sección *Lista de servidores fallback personalizados* e ingresa los servidores fallback personalizados, uno por línea o diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index d9f45bdd44a..6fb914fabc0 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ Una vez que hayas creado el archivo de volcado, navega hasta la ubicación del a :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard para Windows tiene dos procesos en ejecución (`Adguard.exe` y `AdguardSvc.exe`). Por lo tanto, debes crear el archivo dump por separado para cada proceso. ::: ![Procesos de AdGuard](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -Cuando envíes los archivos dump al equipo de soporte, adjunte también los registros de la aplicación AdGuard para que tengamos más posibilidades de resolver el problema. [Here](../adguard-logs) you can check the instructions on how to get the log file. +Cuando envíes los archivos dump al equipo de soporte, adjunte también los registros de la aplicación AdGuard para que tengamos más posibilidades de resolver el problema. [Aquí](../adguard-logs) puedes consultar las instrucciones sobre cómo recopilar el archivo de registro. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 76ac8ea5057..404cd220318 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard installation logs +title: Cómo recopilar registros de instalación de AdGuard sidebar_position: 4 --- @@ -17,7 +17,7 @@ Los datos y/o archivos proporcionados en los registros del sistema se procesan d Si ocurre algún problema durante la instalación de AdGuard, el equipo de soporte puede pedirte que recopiles y envíes registros de instalación de AdGuard. En este caso, es necesario: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Selecciona el comando *Ejecutar* en el menú Inicio o presiona *Win + R* en el teclado. 1. Escribe *%tmp%* y haz clic en *OK*. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 629e298e1f1..388007ef232 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Una vez que abras la Configuración avanzada, se te presentarán las siguientes Si está habilitada, AdGuard bloqueará TCP Fast Open en el navegador Edge. Para aplicar la configuración, debes reiniciar el navegador. -### Use Encrypted Client Hello +### Usar Encrypted ClientHello -Toda conexión a Internet cifrada tiene una parte no cifrada. Este es el primer paquete que contiene el nombre del servidor al que te estás conectando. La tecnología Encrypted Client Hello resuelve este problema y cifra la última parte de la información no cifrada. To benefit from it, enable the *Use Encrypted Client Hello* option. Utiliza un proxy DNS local para buscar la configuración de ECH para el dominio. If it is found, Client Hello packet will be encrypted. +Toda conexión a Internet cifrada tiene una parte no cifrada. Este es el primer paquete que contiene el nombre del servidor al que te estás conectando. La tecnología Encrypted Client Hello resuelve este problema y cifra la última parte de la información no cifrada. Para aprovecharla, activa la opción *Usar Encrypted ClientHello*. Utiliza un proxy DNS local para buscar la configuración de ECH para el dominio. Si se encuentra, el paquete ClientHello se cifrará. ### Verificar la transparencia de los certificados de los sitios web @@ -73,7 +73,7 @@ De lo contrario, AdGuard filtrará todo el tráfico, sin redirección. En este c ### Abrir la ventana principal al inicio del sistema -Activa esta opción para que la ventana principal de AdGuard se abra después de cargar el sistema. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Activa esta opción para que la ventana principal de AdGuard se abra después de cargar el sistema. Ten en cuenta que no afecta si el servicio de filtrado real se inicia o no, esta configuración se encuentra en *Configuración → Configuración general* ### Habilitar filtrado al iniciar el sistema @@ -95,7 +95,7 @@ Si no deseas que AdGuard filtre subredes particulares, habilita esta función y ### Habilitar escritura HAR -Esta opción debe habilitarse **solo con fines de debugging**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. Este archivo se puede analizar con la aplicación Fiddler. Ten en cuenta que esto puede ralentizar significativamente tu navegación web. +Esta opción debe habilitarse **solo con fines de debugging**. Si marcas la marca de verificación, AdGuard creará un archivo que contiene información sobre todas las solicitudes HTTP filtradas en formato HAR 1.2. Este archivo se puede analizar con la aplicación Fiddler. Ten en cuenta que esto puede ralentizar significativamente tu navegación web. ### Añadir un espacio adicional a la petición HTTP simple @@ -115,7 +115,7 @@ Esta opción solo se aplica cuando la opción *Proteger de DPI* en Modo Stealh e Especifica el tamaño de la fragmentación del paquete TCP, evitando la inspección profunda de paquetes. Esta opción solo afecta el tráfico seguro (HTTPS). -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +Si esta opción está habilitada, AdGuard divide el paquete TLS inicial (el paquete ClientHello) en dos partes: la primera tiene la longitud especificada y la segunda tiene el resto, hasta la longitud de todo el paquete TLS inicial. Valores válidos: 1–1500. Si se especifica un tamaño no válido, se utilizará el valor seleccionado por el sistema. Esta opción solo se aplica cuando la opción *Proteger de DPI* en Modo Stealh está habilitada. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 9ecb92e43b7..321f77cd180 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect Windows system logs +title: Cómo recopilar registros del sistema de Windows sidebar_position: 5 --- @@ -15,7 +15,7 @@ Los datos y/o archivos proporcionados en los registros del sistema se procesan d ::: -Para analizar y diagnosticar diferentes problemas que puedan surgir, el servicio de soporte de AdGuard puede necesitar archivos de registro del sistema de Windows. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. A continuación, se muestran breves instrucciones que describen la forma de obtener los archivos de registro y enviarlos a nuestro servicio de soporte si es necesario. +Para analizar y diagnosticar diferentes problemas que puedan surgir, el servicio de soporte de AdGuard puede necesitar archivos de registro del sistema de Windows. Los registros de eventos de Windows contienen registros sobre todos los errores que ocurren con el software instalado, incluido AdGuard. A continuación, se muestran breves instrucciones que describen la forma de obtener los archivos de registro y enviarlos a nuestro servicio de soporte si es necesario. 1. Presiona *Win + R* diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 399ffd48615..8c04ad76c83 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ Este artículo trata sobre AdGuard para Windows, un bloqueador de anuncios multi ::: -Para filtrar el tráfico de red, AdGuard utiliza un controlador de red. Hay dos opciones: controlador TDI y controlador WFP. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. Estos problemas y errores posteriores pueden ser muy diferentes en cada caso. +Para filtrar el tráfico de red, AdGuard utiliza un controlador de red. Hay dos opciones: controlador TDI y controlador WFP. Aunque el controlador PMA es generalmente preferible y está activado por defecto para todas las versiones más recientes del sistema operativo Windows (Windows 8 y posteriores), puede causar problemas de compatibilidad, especialmente con algunos antivirus. Estos problemas y errores posteriores pueden ser muy diferentes en cada caso. Si encuentras un problema que sospecha que puede deberse a esto, siempre puedes cambiar al controlador de red TDI más antiguo pero más estable. Para hacerlo: 1. Ve a *Ajustes → Red*. -2. Disable the WFP driver as it’s done in this picture: +2. Desactiva el driver WFP como se hace en esta imagen: ![Driver WFP *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/es/docusaurus-plugin-content-docs/current/general/account/features.md index 92eef8ae563..4030a89a749 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ La sección Historial de compras muestra todas las licencias que hayas comprado ## Contactar la asistencia técnica -La pestaña Soporte contiene enlaces útiles que te ayudarán a resolver problemas o encontrar respuestas a tus preguntas sobre los productos AdGuard. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +La pestaña Soporte contiene enlaces útiles que te ayudarán a resolver problemas o encontrar respuestas a tus preguntas sobre los productos AdGuard. Se dividen en seis secciones: Preguntas frecuentes, Enviar un informe de error/solicitud de función, Informar de un bloqueo incorrecto, Contactar con el soporte técnico, Base de conocimientos y Discusión. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index e87dc316263..33e1d343680 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ Este artículo trata sobre los filtros que creamos para usar en AdGuard y otros - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 8ce25d6f0c7..23706aa89d8 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-----------------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:-----------------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:-----------------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-----------------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:-----------------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-----------------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:---------------------------:|:------------------------------:|:-----------------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:---------------------------:|:------------------------------:|:-----------------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-----------------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-----------------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:---------------------------:|:------------------------------:|:-----------------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de contenido AdGuard][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:---------------------------:|:------------------------------:|:-----------------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,32 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard para Safari" -[ext-saf]: #what-product "AdGuard for Safari" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index e7d8ea551eb..6e16fdd4a6f 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ Los filtros de bloqueo de anuncios de AdGuard incluyen: - Filtro base AdGuard - Filtro de anuncios de AdGuard para dispositivos móviles - Filtros regionales divididos por idiomas: chino, holandés, francés, alemán, japonés, ruso, español, portugués, turco y ucraniano -- AdGuard Quick Fixes filter ### La finalidad de estos filtros - El **Filtro base** fue diseñado para bloquear anuncios en sitios en inglés y aquellos para los cuales no hay un filtro separado. También contiene reglas generales de filtrado que se aplican a todos los sitios, independientemente del idioma - El **Filtro de anuncios para dispositivos móviles** bloquea anuncios en versiones móviles de sitios y en teléfonos celulares y tabletas. No hay segmentación basada en el idioma - Los **Filtros regionales** siguen la misma política que el **Filtro base**, pero están limitados a sitios en determinados idiomas -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. El objetivo de los filtros de bloqueo de anuncios es bloquear todos los tipos de publicidad en sitios web, aplicaciones y dispositivos específicos que pueden cargar anuncios de Internet: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/es/docusaurus-plugin-content-docs/current/general/browsing-security.md index 0701fac8c8d..ae236437d93 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Ser víctima de phishing y malware sigue siendo un problema común. Para mejorar la seguridad digital, hemos incorporado filtros especiales en los productos AdGuard para protegerte de sitios web maliciosos y de phishing. Hasta hoy, hemos categorizado más de 15 millones de sitios y creado una base de datos de 1,5 millones de sitios web conocidos por phishing y malware. Al utilizar esta base de datos, AdGuard verifica los sitios web que visitas para protegerte de amenazas en línea. -:::note +::: note Estrictamente no recopilamos ni utilizamos ninguna información sobre los sitios web que visitas. ::: -## How does AdGuard check websites? +## ¿Cómo AdGuard verifica los sitios web? Cada vez que visitas un sitio web, tu cliente local intercambia información con nuestro servidor backend en forma de hash y prefijos hash. En base a este intercambio, el cliente local determina si el sitio web figura o no en la base de datos de sitios web potencialmente peligrosos. Hay una diferencia en el alcance de esta verificación para aplicaciones y extensiones. @@ -61,11 +61,11 @@ AdGuard mantiene una extensa base de datos de sitios web de phishing y malware, Analizamos automáticamente las quejas sobre sitios sospechosos y dedicamos mucho tiempo a mantener actualizada la base de datos, limpiando falsos positivos e implementando mecanismos para prevenirlos en el futuro. -### Want to help? +### ¿Quieres ayudar? ¡Toda ayuda es bienvenida! Si encuentras un sitio web de phishing o malware, infórmalo a . -### False-positive responses +### Falsos positivos​ Ocasionalmente, se agregan algunos sitios web no maliciosos a los filtros de AdGuard. Hacemos todo lo posible para reducir el porcentaje de falsos positivos, pero aún así ocurren. Si encuentras este comportamiento de AdGuard, por favor reporta el falso positivo a nuestro soporte técnico en . diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/es/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/es/docusaurus-plugin-content-docs/current/general/license/what-is.md index 737c331b882..b4d7f31f591 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ En la [ página de compra](https://adguard.com/license.html), puede ver los sigu - **Suscripciones de 1 año**: estas licencias se renuevan automáticamente cada año o se pueden extender manualmente - Personal: hasta 3 dispositivos - Familiar: hasta 9 dispositivos -- **Lifetime** — these licenses are perpetual +- **Vitalicia**: estas licencias no tienen límite de tiempo - Personal: hasta 3 dispositivos - Familiar: hasta 9 dispositivos diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/es/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 6082ddc18f6..f49000b52d2 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Habilitar esta opción evitará que el navegador envíe datos de GPS que podría ### Bloquear Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Al activar esta configuración, AdGuard bloquea la capacidad de los navegadores para detectar componentes (como complementos y objetos ActiveXObject) que permiten que Flash muestre contenido. En la práctica, esto significa que los navegadores no son compatibles con Flash. +El complemento Flash Player se ha vuelto cada vez más vulnerable a amenazas en línea como virus y hackers; También puede afectar significativamente el tiempo de carga del sitio web. Al activar esta configuración, AdGuard bloquea la capacidad de los navegadores para detectar componentes (como complementos y objetos ActiveXObject) que permiten que Flash muestre contenido. En la práctica, esto significa que los navegadores no son compatibles con Flash. ### Bloquear Java {#java} @@ -95,7 +95,7 @@ También puedes establecer un valor arbitrario para Referer ingresándolo en el Ten en cuenta que para poder filtrar el tráfico, las aplicaciones AdGuard "interceptan" las solicitudes del navegador al servidor. Las solicitudes a servidores de publicidad, seguimiento y phishing pueden modificarse antes de enviarlas al servidor o bloquearse por completo. Lo mismo ocurre con la opción *Ocultar Referer de terceros*: AdGuard intercepta solicitudes HTTP(S), en particular para eliminar o cambiar el encabezado Referer si esta opción está habilitada. Sin embargo, esto ocurre sólo después de que estas solicitudes “abandonan” el navegador. Esto significa que, si monitoreas el Referer dentro del navegador (por ejemplo, con la ayuda de las herramientas de desarrollo de Chrome), verás el Referer original porque la solicitud aún no ha llegado a AdGuard. Puedes utilizar software como [Fiddler](https://www.telerik.com/fiddler) para asegurarte de que Referer se modifique correctamente. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. Modificará el Referer en ese mismo momento, por lo que Developer Tools mostrará el Referer deseado para tus peticiones. +Por el contrario, debido a la naturaleza de todas las extensiones del navegador, la extensión de navegador AdGuard funciona "dentro" del navegador. Modificará el Referer en ese mismo momento, por lo que Developer Tools mostrará el Referer deseado para tus peticiones. ### Ocultar tu User-Agent {#useragent} @@ -120,9 +120,3 @@ Deep Packet Inspection es un sistema de análisis profundo y filtrado de tráfic AdGuard puede modificar los datos de los paquetes salientes para que el cliente no entre en los criterios de bloqueo de DPI. Esto significa que, al habilitar esta opción, los usuarios pueden acceder al contenido que desean. No todos los sistemas DPI se pueden omitir en este momento, pero trabajamos constantemente para mejorarlo. La función "Proteger de DPI" ya está implementada en AdGuard para Windows, AdGuard para Mac y AdGuard para Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/es/docusaurus-plugin-content-docs/current/general/userscripts.md index 4b9e38bd6e4..4a9f7201d92 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. Modifican o amplían la funcionalidad de uno o más sitios web. Es posible que muchos usuarios de AdGuard ya estén familiarizados con scripts de usuario como AdGuard Assistant, Popup Blocker y AdGuard Extra. +Los scripts de usuario (también los llamamos "extensiones") son, de hecho, miniprogramas escritos en JavaScript. Modifican o amplían la funcionalidad de uno o más sitios web. Es posible que muchos usuarios de AdGuard ya estén familiarizados con scripts de usuario como AdGuard Assistant, Popup Blocker y AdGuard Extra. :::note Aplicaciones compatibles @@ -134,7 +134,7 @@ Aquí hay un [enlace mailto](mailto:devteam@adguard.com?Subject=Userscript%20aut ##### Propiedades no compatibles -These properties will be simply ignored by AdGuard. +Adguard simplemente ignorará estas propiedades. ```text @unwrap diff --git a/i18n/es/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/es/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 7397d8ecff7..6df3fcd2f8b 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: Cómo recopilar un archivo HAR sidebar_position: 1 --- diff --git a/i18n/es/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/es/docusaurus-plugin-content-docs/current/guides/report-bugs.md index b703be44b57..0ec800ce5cf 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Verifica si el error no se ha informado antes. Aconsejamos prestar atención tan ### Cómo describir un problema -Intenta proporcionar tantos detalles como sea posible; eso nos facilitará la reproducción del error y descubriremos cómo solucionarlo. Here’s what we expect a bug report to include: +Intenta proporcionar tantos detalles como sea posible; eso nos facilitará la reproducción del error y descubriremos cómo solucionarlo. Esto es lo que esperamos ver en un informe de errores: - La versión de tu aplicación - La versión de tu sistema operativo @@ -28,7 +28,7 @@ Intenta proporcionar tantos detalles como sea posible; eso nos facilitará la re ### Cómo recopilar registros -Read about collecting logs in dedicated articles for each platform. +Lee sobre la recopilación de registros en los artículos dedicados a cada plataforma. ## Cómo votar por informes de errores o solicitudes de funciones diff --git a/i18n/es/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/es/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index 100bb8f08e6..ddc8b9a5b97 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ En algunos portátiles, tienes que mantener pulsada la tecla *Fn* y luego pulsar Windows captura toda la pantalla y la copia en el portapapeles. -To take a screenshot of an active window, use the following shortcut keys: +Para tomar una captura de pantalla de una ventana activa, utiliza el siguiente acceso directo: - **Manten presionado *Alt* y pulsa *PrtScn* (o *Fn + Alt + PrtScn* en algunos portátiles)** -To take a screenshot of a specific area, use the following shortcut keys: +Para tomar una captura de pantalla de un área específica, utiliza el siguiente acceso directo: - ***Presiona ***Win + Shift + S****** -Después de tomar una captura de pantalla, se guardará en el portapapeles. En la mayoría de los casos, podrás pegarlo en un documento que estés editando actualmente usando el atajo *Ctrl + V*. Alternativamente, si necesitas guardar la captura de pantalla en un archivo, debes abrir el programa estándar **Paint** (o cualquier otra aplicación que pueda trabajar con imágenes). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +Después de tomar una captura de pantalla, se guardará en el portapapeles. En la mayoría de los casos, podrás pegarlo en un documento que estés editando actualmente usando el atajo *Ctrl + V*. Alternativamente, si necesitas guardar la captura de pantalla en un archivo, debes abrir el programa estándar **Paint** (o cualquier otra aplicación que pueda trabajar con imágenes). Pega allí tu captura de pantalla utilizando el mismo atajo de teclado o haciendo clic en el botón Pegar (normalmente en la esquina superior izquierda de la pantalla) y luego guárdala. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. Tan pronto como presiones estas teclas, la captura de pantalla se guardará automáticamente como un archivo en tu carpeta de *Imágenes* → *Capturas de pantalla*. +Windows 8 y 10 te permiten tomar una captura de pantalla muy rápidamente con el atajo *Win + PrtScn*. Tan pronto como presiones estas teclas, la captura de pantalla se guardará automáticamente como un archivo en tu carpeta de *Imágenes* → *Capturas de pantalla*. También hay un programa dedicado a tomar capturas de pantalla llamado *Snipping Tool*, que se puede encontrar a través del menú de Inicio entre los programas estándar de tu ordenador. La Snipping Tool te permite capturar cualquier área de tu escritorio o toda la pantalla. Después de tomar una captura de pantalla con este programa, puedes editar la imagen y guardarla en cualquier carpeta de tu ordenador. @@ -70,26 +70,26 @@ Además, también puedes probar a utilizar diferentes aplicaciones para hacer ca ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Para tomar una captura de pantalla en Mac, usa el siguiente atajo: - ***Mantén pulsado ***⌘ Cmd + Shift + 3****** Tu Mac capturará toda la pantalla y la guardará como un archivo en el escritorio. -To take a screenshot of an active window, use the following shortcut keys: +Para tomar una captura de pantalla de una ventana activa, utiliza el siguiente acceso directo: - **Manten presionadas las teclas *⌘ Cmd + Shift + 4 + Barra espaciadora*. El puntero cambiará a un icono de cámara. Haz clic en la ventana para capturarla. Pulsa Esc para cancelar la captura de pantalla** -To take a screenshot of a specific area, use the following shortcut keys: +Para tomar una captura de pantalla de un área específica, utiliza el siguiente acceso directo: - ***Pulsa ***⌘ Cmd + Shift + 5******. Desliza para seleccionar el área necesaria. Suelta el ratón o el trackpad para hacer una captura de pantalla, pulsa Esc para cancelarla. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +Para tomar una captura de pantalla de la *Barra táctil* (MacBook Pro), utiliza el siguiente atajo: - ***Presiona ***⌘ Cmd + Shift + 6****** El Mac captura toda la *Touch Bar* y la guarda como un archivo en el escritorio. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +Para copiar una captura de pantalla al portapapeles en lugar de guardarla, mantén presionada la tecla *Ctrl* junto con cualquiera de los atajos anteriores. Luego puedes pegar la captura de pantalla (desde el portapapeles) en un documento o una imagen que estés editando actualmente usando el atajo *Cmd + V*. También puedes hacer capturas de pantalla utilizando la **Vista Previa** y eligiendo **Tomar captura de pantalla** (del área seleccionada, de la ventana o de toda la pantalla). Con la **Vista Previa** puedes guardar tus capturas de pantalla en JPG, TIFF, PDF y otros formatos de archivo. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/intro.md b/i18n/es/docusaurus-plugin-content-docs/current/intro.md index aff4b39da06..1ce805d783c 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index 99b633439cc..f543210f57e 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Los sitios web cambian constantemente la forma en que insertan los anuncios y ag Sin embargo, trabajar con filtros de bloqueo requiere habilidades específicas. Si las tienes y sabes cómo crear reglas, dirígete directamente a nuestro repositorio[de filtros AdGuard](https://github.com/AdguardTeam/AdguardFilters) en GitHub. Allí encontrará muchos problemas abiertos, cada uno de los cuales hace referencia a un problema del sitio web: un anuncio perdido, un falso positivo, etc. Elige cualquiera y sugiere tus propias reglas en los comentarios. Los ingenieros de filtros de AdGuard revisarán tus sugerencias y, si las encuentran apropiadas, tus reglas se agregarán a los filtros de AdGuard. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +Si aún no estás familiarizado con la sintaxis de nuestras reglas de filtrado, o tal vez necesites un repaso, encontrarás los conceptos básicos sobre la sintaxis [en nuestra Base de conocimientos](/general/ad-filtering/create-own-filters). ### Recompensas {#rewards} diff --git a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index 387b2cbea75..e1c796a2d3d 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Convertirte en traductor/revisor sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +Si deseas ayudar a traducir productos, sitios web y bases de conocimiento de AdGuard, ve a [Crowdin](https://crowdin.com/) y regístrate/inicia sesión allí. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index de947f278ca..0d0c838593d 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ Cuando se enfrenta a una traducción que requiere el uso de plurales, es posible Aquí hay algunas fuentes de información que puedes utilizar. -[La Guía de localización](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contiene una amplia lista de idiomas. El número de formas plurales para diferentes idiomas se muestra de esta manera: `nplurales=2`, `nplurales=4` y así sucesivamente. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[La Guía de localización](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contiene una amplia lista de idiomas. El número de formas plurales para diferentes idiomas se muestra de esta manera: `nplurales=2`, `nplurales=4` y así sucesivamente. El número después del signo igual `=` significa el número de formas plurales del idioma respectivo. Además, puedes obtener información sobre formas plurales en el [Repositorio de datos de configuración regional común](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR) de Unicode. Las reglas CLDR Plural indican una forma de palabra adicional para los números decimales (1,5; 2,3; 100,1…), pero no las usamos en las traducciones de AdGuard. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 00f1054e001..56277a6efcd 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: Programa de traducción AdGuard sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** puedes hacernos cualquier pregunta sobre la traducción de AdGuard enviándonos un correo electrónico a [translate@adguard.com](mailto:translate@adguard.com) o uniéndote a nuestro [chat de Telegram](https://t.me/joinchat/UVYTLcHbr8JmOGIy). -When it comes to translations, we at AdGuard always heavily rely on volunteers. +Cuando se trata de traducciones, en AdGuard siempre dependemos en gran medida de los voluntarios. -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +Ahora usamos la plataforma [Crowdin](https://crowdin.com/) para gestionar las traducciones de nuestros productos. Así que este es el lugar para cualquier persona que quiera contribuir con AdGuard traduciendo cualquiera de nuestros productos. -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +Si quieres estar entre los voluntarios que nos ayudan a traducir AdGuard, por favor lee la información en [Cómo convertirte en nuestro traductor](../become-translator) y [Cómo colaboramos con ellos](../rewards). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index a0f8f237bb7..50d754e835c 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: Cómo dar prioridad a las traducciones de archivos Crowdin sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +Hay cinco proyectos principales de AdGuard en Crowdin - [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), y [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). No tenemos pautas claras sobre con qué archivos o productos del proyecto *AdGuard Applications* comenzar. Simplemente elige cualquier producto que desees. Solo hay un par de cosas que queremos mencionar: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- Puedes ver la aplicación solo en aquellos idiomas para los que todas las traducciones se completan en Crowdin; - Recomendamos traducir las descripciones de las tiendas de aplicaciones en segundo lugar, porque sin la traducción de los productos en sí, las descripciones no serán necesarias. La situación es diferente en el proyecto *AdGuard Websites*. Se pueden agregar idiomas al sitio incluso si no está disponible un conjunto completo de traducciones. Sin embargo, esto depende de qué archivos ya se han traducido. Es por eso que te recomendamos que comiences con los archivos más importantes, que se enumeran a continuación: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index c082270511f..42b26d4992f 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Actualizando la Base de conocimientos sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. Pero las cosas cambian constantemente y, a veces, un artículo ya no refleja el estado actual de las cosas. +El objetivo de la base de conocimientos de AdGuard Ad Blocker es brindar a todos la información más actualizada sobre todo tipo de temas relacionados con AdGuard. Pero las cosas cambian constantemente y, a veces, un artículo ya no refleja el estado actual de las cosas. Por eso hemos colocado todo el contenido de nuestra base de conocimiento en [GitHub](https://github.com/AdguardTeam/KnowledgeBase), y ahora, literalmente, cualquiera puede contribuir a ella sugiriendo modificaciones y traducciones de los artículos existentes, así como otros totalmente nuevos. ## Cómo sugerir un cambio o redactar un nuevo artículo {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. Si no estás familiarizado con los principios de trabajo con la plataforma, comienza leyendo la documentación de [GitHub](https://docs.github.com/en). +Puedes sugerir cambios a los artículos actuales y agregar otros nuevos a nuestra base de conocimientos utilizando la funcionalidad de GitHub mencionada anteriormente. Si no estás familiarizado con los principios de trabajo con la plataforma, comienza leyendo la documentación de [GitHub](https://docs.github.com/en). -Una vez que estés listo para comenzar, trabaja en el repositorio [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Tenlo en cuenta cuando edites o escribas artículos. Sigue [este enlace](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) para aprender más sobre la sintaxis de Markdown. +Una vez que estés listo para comenzar, trabaja en el repositorio [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase). Todos los textos de nuestra Base de conocimientos están escritos en lenguaje de marcado `Markdown`. Tenlo en cuenta cuando edites o escribas artículos. Sigue [este enlace](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) para aprender más sobre la sintaxis de Markdown. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. Al sugerir cambios o adiciones, ten en cuenta que todos los documentos deben cumplir con los principios de la plataforma. Puedes leer sobre ellos en [Guías de Docusaurus](https://docusaurus.io/docs/category/guides). +El sitio web de Base de conocimiento se construye utilizando Docusaurus 2 - un moderno generador de sitios web estáticos. Al sugerir cambios o adiciones, ten en cuenta que todos los documentos deben cumplir con los principios de la plataforma. Puedes leer sobre ellos en [Guías de Docusaurus](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +Puedes implementar esta base de conocimiento localmente en tu computadora para obtener una vista previa de los cambios que sugiere. Puede encontrar instrucciones detalladas sobre cómo hacerlo [en el archivo README](https://github.com/AdguardTeam/KnowledgeBase#readme) de la página de GitHub de esta Base de conocimientos. ## Traducción de artículos {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +La traducción de los artículos existentes de la Base de conocimientos se realiza a través de la [ plataforma Crowdin](https://crowdin.com/profile/adguard). Todos los detalles sobre las traducciones y el trabajo con Crowdin se pueden consultar [en el artículo ](../translate/guidelines) dedicado de la Base de conocimientos del bloqueador de anuncios AdGuard. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [En un artículo separado](../translate/plural-forms), describimos en detalle las dificultades que pueden surgir al traducir cadenas con formas plurales, y dimos amplias instrucciones sobre cómo trabajar con ellas en la plataforma Crowdin. +Cuando se trabaja en los artículos de la Base de conocimientos de AdGuard, es posible que encuentres con cadenas que contienen formas plurales que debes traducir con especial atención. [En un artículo separado](../translate/plural-forms), describimos en detalle las dificultades que pueden surgir al traducir cadenas con formas plurales, y dimos amplias instrucciones sobre cómo trabajar con ellas en la plataforma Crowdin. ## Trabajar en los temas pendientes -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Elige cualquier tema que te parezca atractivo y empieza a trabajar en él. Si tienes alguna pregunta, puedes hacerla en los comentarios de ese tema. +A veces existen [tareas abiertas](https://github.com/AdguardTeam/KnowledgeBase/issues) en relación con la actualización de la Base de conocimientos. Puedes ayudarnos a acelerar su finalización [del mismo modo](#suggest-change) que sugerirías cualquier otro cambio en la Base de conocimientos. Elige cualquier tema que te parezca atractivo y empieza a trabajar en él. Si tienes alguna pregunta, puedes hacerla en los comentarios de ese tema. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/fa/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/fa/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/fa/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/fa/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/intro.md b/i18n/fa/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/fa/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/fi/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/fi/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/fi/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/fi/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/intro.md b/i18n/fi/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/fi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md index 37144474bc7..7260d5e770f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md @@ -9,18 +9,18 @@ Cet article concerne l'extension de navigateur AdGuard, qui protège uniquement ::: -[L'Extension de navigateur AdGuard] (https://adguard.com/adguard-browser-extension/overview.html) est une extension gratuite qui fonctionne dans cinq navigateurs populaires : Chrome, Firefox, Edge, Opera et Yandex Browser. Vous pouvez la trouver facilement dans la boutique en ligne de votre navigateur ou sur notre site officiel. +[AdGuard Browser Extension](https://adguard.com/adguard-browser-extension/overview.html) is a free extension that works in five popular browsers: Chrome, Firefox, Edge, Opera, and Yandex Browser. Vous pouvez la trouver facilement dans la boutique en ligne de votre navigateur ou sur notre site officiel. -! [Extension de navigateur AdGuard pour Chrome \*border] (https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) +![AdGuard Browser Extension for Chrome \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) -Les extensions de navigateur incluent des fonctionnalités de blocage des publicités de base, mais ne peuvent pas être comparées aux programmes de bureau complets, tels que [AdGuard pour Windows](/adguard-for-windows/features/home-screen) et [AdGuard pour Mac](/adguard-for-mac/features/main). +Browser extensions include basic ad-blocking features but cannot be compared with full-featured desktop programs, such as [AdGuard for Windows](/adguard-for-windows/features/home-screen) and [AdGuard for Mac](/adguard-for-mac/features/main). -![Disponible pour la plupart des navigateurs populaires \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) +![Available for most popular browsers \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) :::note -Nous avons une extension autonome pour Safari. Depuis la sortie de [Safari 13] (https://adguard.com/en/blog/adguard-safari-1-5.html), la plupart des extensions de blocage des publicités ont connu d'énormes problèmes et nombre d'entre elles ont cessé de fonctionner. Nous avons dû développer une [extension séparée pour Safari](/adguard-for-safari/features/general) qui présente quelques différences par rapport à l'extension décrite dans cet article. +Nous avons une extension autonome pour Safari. Since the release of [Safari 13](https://adguard.com/en/blog/adguard-safari-1-5.html), most of the ad-blocking extensions have experienced huge issues and many of them stopped functioning. We had to develop a [separate extension for Safari](/adguard-for-safari/features/general) that has some differences in comparison with the extension described in this article. ::: -**N'oubliez pas que la fonctionnalité de chaque extension est strictement limitée par les capacités du navigateur.** Donc, si vous souhaitez une protection complète, envisagez d'installer un programme autonome sur votre ordinateur. Il existe [une raison pourquoi](adguard-browser-extension/comparison-standalone). +**Do not forget that the functionality of each extension is strictly limited by the browser’s capabilities.** So if you want to get full-fledged protection, consider installing a standalone program for your computer. There's [a reason why](adguard-browser-extension/comparison-standalone). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index bf2dae89f15..dedfeb61b57 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -1,5 +1,5 @@ --- -title: Comparaison avec les applications autonomes +title: Comparison to standalone apps sidebar_position: 7 --- @@ -19,8 +19,8 @@ Alors que l'extension de navigateur AdGuard est gratuite et facile à installer, ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — dans les restrictions du navigateur et uniquement dans le navigateur où elle est installée; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — l'extension ne peut pas détecter les requêtes provenant d'autres extensions. Si une extension malveillante ou de suivi envoie une requête à son serveur pour vous montrer des publicités ou suivre votre activité, l'extension de navigateur AdGuard ne pourra pas bloquer cette requête ; +`2` – the extension is unable to detect requests from other extensions. Si une extension malveillante ou de suivi envoie une requête à son serveur pour vous montrer des publicités ou suivre votre activité, l'extension de navigateur AdGuard ne pourra pas bloquer cette requête ; -`3` - tous les types de publicités et de menaces ne peuvent pas être bloqués par les extensions de navigateur en raison de certaines limitations du navigateur. Certains éléments peuvent arriver sur la page et ralentir le processus de chargement. De plus, contrairement aux bloqueurs de publicités basés sur le navigateur, l'application AdGuard bloque les publicités avant qu'elles ne soient chargées dans le navigateur. Cela économise la bande passante et accélère le chargement des pages. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Certains éléments peuvent arriver sur la page et ralentir le processus de chargement. De plus, contrairement aux bloqueurs de publicités basés sur le navigateur, l'application AdGuard bloque les publicités avant qu'elles ne soient chargées dans le navigateur. Cela économise la bande passante et accélère le chargement des pages. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md index f999a36803d..6d4f926019f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md @@ -1,5 +1,5 @@ --- -title: Compatibilité avec l'application autonome +title: Compatibility with the standalone app sidebar_position: 4 --- @@ -9,16 +9,16 @@ Cet article concerne l'extension de navigateur AdGuard, qui protège uniquement ::: -Alors que l'extension de navigateur AdGuard peut bloquer les publicités dans les navigateurs, les [programmes autonomes AdGuard](/adguard-browser-extension/comparison-standalone) filtrent tout le trafic sur votre appareil, y compris celui des navigateurs et des applications. +While AdGuard Browser Extension can block ads in browsers, [AdGuard standalone programs](/adguard-browser-extension/comparison-standalone) filter all the traffic on your device, including from browsers and apps. -Si vous décidez d'installer à la fois l'extension et le programme autonome sur votre PC, vous risquez de rencontrer des problèmes de compatibilité. Le problème est que dans certains cas, l’application et l’extension peuvent interférer l’une avec l’autre. Certains sites web ne seront plus protégés par le programme de bureau et ne le seront plus que par l'extension, qui offre moins d'options. En outre, le filtrage peut ne pas fonctionner correctement pour certains sites web. Par conséquent, nous ne recommandons pas d'utiliser l'extension en même temps que l'application. +If you decide to install both the extension and the standalone program on your PC, you may encounter some compatibility issues. The problem is that in some cases the application and the extension may interfere with each other. Some websites will no longer be protected by the desktop program and will only be protected by the extension, which has fewer options. Also, filtering may work incorrectly for some websites. Therefore, we don't recommend using the extension together with the application. -Si vous avez la version de bureau d'AdGuard installée sur votre PC, il est préférable d'utiliser l'Assistant AdGuard de navigateur plutôt que l'extension. +If you have the desktop version of AdGuard installed on your PC, it is better to use AdGuard Browser Assistant instead of the extension. ## Assistant de navigateur AdGuard -! [Assistant AdGuard de navigateur \*mobile_border] (https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) +![AdGuard Browser Assistant \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) -L'Assistant de navigateur AdGuard Browser Assistant est une extension de navigateur qui fonctionne et se sent comme l'Extension de navigateur AdGuard, mais elle est beaucoup plus légère et n'interfère pas avec les applications de bureau. Vous pouvez [apprendre plus sur l'Assistant de navigateur pour Windows](/adguard-for-windows/browser-assistant) ou [Mac](/adguard-for-mac/features/browser-assistant), ou [le télécharger depuis notre site web](https://adguard.com/adguard-assistant/overview.html). +AdGuard Browser Assistant is a browser extension that works and feels just like AdGuard Browser Extension, but it's much lighter and doesn't interfere with the desktop apps. You can [read more about Browser Assistant for Windows](/adguard-for-windows/browser-assistant) or [Mac](/adguard-for-mac/features/browser-assistant), or [download it from our website](https://adguard.com/adguard-assistant/overview.html). -L'Assistant de navigateur AdGuard est disponible dans tous les navigateurs principaux. +AdGuard Browser Assistant is available in all major browsers. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index 03bf5a38615..8cd647bdade 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -15,25 +15,25 @@ Bloquer les publicités est la fonctionnalité clé de tout bloqueur de publicit Tous les filtres sont regroupés en fonction de leur rôle. Par exemple, il existe des catégories pour les filtres de blocage de publicités, les filtres de protection de la vie privée, les filtres liés aux médias sociaux, etc. Vous pouvez activer soit des filtres individuels, soit l'ensemble du groupe à la fois. -![Filtres anti-publicitaires \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters1.png) +![Ad blocking filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters1.png) ## Filtres personnalisés -Alors que les fonctionnalités des autres groupes de filtres sont plus ou moins explicites, il y existe un groupe appelé _Personnalisés_ qui peut soulever des questions supplémentaires. +Alors que les fonctionnalités des autres groupes de filtres sont plus ou moins prévisibles, il y existe un groupe appelé _Personnalisé_ qui peut soulever des questions supplémentaires. -![Filtres personnalisés \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) +![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) Dans cet onglet, vous pouvez ajouter des filtres qui ne sont pas présents par défaut dans l'extension. Il existe de nombreux [filtres disponibles publiquement sur Internet](https://filterlists.com). De plus, vous pouvez créer et ajouter vos propres filtres. En fait, vous pouvez construire n'importe quel ensemble de filtres et personnaliser le blocage des publicités selon vos préférences. Pour ajouter un filtre, cliquez simplement sur _Ajouter un filtre personnalisé_, saisissez l'URL ou le chemin du fichier du filtre que vous souhaitez ajouter, puis cliquez sur _Suivant_. -![Ajouter un filtre personnalisé \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters1.png) +![Add a custom filter \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters1.png) ## Règles utilisateur {#user-rules} Les _règles utilisateur_ sont un autre outil qui vous aide à personnaliser le blocage des publicités. -![Règles utilisateur \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_user_rules.png) +![User rules \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_user_rules.png) Il existe plusieurs façons d'ajouter de nouvelles règles. Le plus simple est de taper une règle, mais cela nécessite une certaine connaissance de la [syntaxe des règles](/general/ad-filtering/create-own-filters). @@ -47,10 +47,10 @@ Lorsque vous ajoutez un site à la liste autorisée (plus d'informations à ce s La _liste d'autorisation_ est utilisée pour exclure certains sites web du filtrage. Les règles de blocage ne s'appliquent pas aux sites web figurant sur la liste. -![Liste autorisée \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist.png) +![Allowlist \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist.png) La _liste d'autorisation_ peut également être inversée : vous pouvez débloquer les publicités partout, sauf sur les sites ajoutés à cette liste. Pour faire ça, activez l'option _Inverser la liste blanche_. -![Inverser la liste autorisée \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist1.png) +![Invert allowlist \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist1.png) Vous pouvez également importer et exporter des listes d'autorisation existantes. C'est utile, par exemple, si vous souhaitez appliquer les mêmes règles d'autorisation dans chacun de vos navigateurs. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 70f4e37b917..cb5b684e81e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -11,10 +11,10 @@ Cet article concerne l'extension de navigateur AdGuard, qui protège uniquement La page principale de l'extension peut être accédée en cliquant sur l'icône de l'extension dans la barre d'outils de votre navigateur. -![Menu Principal \*mobile\_border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_main.png) +![Main menu \*mobile\_border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_main.png) Sur la page principale, vous pouvez masquer manuellement n'importe quel élément sur n'importe quelle page (une règle correspondante sera ajoutée aux _Règles utilisateur_), ouvrir le _Journal de filtrage_ pour consulter des informations complètes sur le trafic de votre navigateur et bloquer les requêtes en cours, ou consulter le rapport de sécurité d'un site web. De plus, vous pouvez soumettre une plainte concernant n'importe quel site web (par exemple, s'il y a des publicités manquées sur la page, nos ingénieurs en filtrage examineront le rapport et résoudront le problème) et consulter les statistiques sur les règles de blocage appliquées. -Toutes les requêtes web effectuées par le navigateur sont affichées dans le _Journal de filtrage_, avec des informations détaillées sur chaque requête. Le _Journal de filtrage_ facilite, par exemple, le suivi des requêtes bloquées par l'extension de navigateur AdGuard. De plus, il vous permet de bloquer n'importe quelle requête ou d'ajouter une requête précédemment bloquée à la liste blanche en deux clics. Le _Journal de filtrage_ vous offre également une grande variété d'options pour trier les requêtes web, ce qui peut être utile lors de la création de vos propres règles de filtrage. Vous pouvez ouvrir le _Journal de filtrage_ en sélectionnant l'élément correspondant dans le menu principal, ou depuis la page des paramètres (dans l'onglet _Paramètres supplémentaires_). +Toutes les requêtes web effectuées par le navigateur sont affichées dans le _Journal de filtrage_, avec des informations détaillées sur chaque requête. Le _Journal de filtrage_ facilite, par exemple, le suivi des requêtes bloquées par l'extension de navigateur AdGuard. De plus, il vous permet de bloquer n'importe quelle requête ou d'ajouter une requête précédemment bloquée à la liste blanche en deux clics. Le _Journal de filtrage_ vous offre également une grande variété d'options pour trier les requêtes web, ce qui peut être utile lors de la création de vos propres règles de filtrage. Vous pouvez ouvrir le _Journal de filtrage_ en sélectionnant l'élément correspondant dans le menu principal, ou depuis la page des paramètres (dans l'onglet "Paramètres supplémentaires"). En cliquant sur les icônes dans le coin supérieur droit du menu principal de l'extension, vous pouvez ouvrir les paramètres de l'extension ou mettre la protection en pause. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 25aac8bf79f..3ec0e6bc40c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -19,13 +19,13 @@ Dans l'onglet _Général_, vous pouvez autoriser les publicités de recherche et De plus, ici vous pouvez activer la [_Protection contre l'hameçonnage et les logiciels malveillants_](/general/browsing-security). -Vous pouvez sauvegarder la configuration de vos paramètres en cliquant sur le bouton _Exporter les paramètres_. Les paramètres seront sauvegardés sous la forme d'un fichier .json. Pour importer la configuration de paramètres précédemment sauvegardée, utilisez la fonction _Importer les paramètres_. Vous pouvez même l'utiliser pour passer rapidement entre différents profils de paramètres ou même pour transférer des configurations de paramètres entre différents navigateurs. +Vous pouvez sauvegarder la configuration de vos paramètres en cliquant sur le bouton _Exporter les paramètres_. Les paramètres seront sauvegardés sous la forme d'un fichier .json. Pour charger la configuration de paramètres précédemment sauvegardée, utilisez la fonction _Importer les paramètres_. Vous pouvez même l'utiliser pour passer rapidement entre différents profils de paramètres ou même pour transférer des configurations de paramètres entre différents navigateurs. ## Paramètres supplémentaires {#misc} La section _Paramètres supplémentaires_ contient une gamme de paramètres variés liés au processus de blocage des publicités et à la convivialité de l'application. -![Paramètres additionnels \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_additional_settings.png) +![Additional settings \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_additional_settings.png) Depuis cet onglet, vous pouvez activer les filtres optimisés, activer les notifications concernant les mises à jour de l'extension, ouvrir le _Journal de filtrage_ ou effacer les statistiques des publicités et traceurs bloqués. @@ -35,4 +35,4 @@ De plus, vous pouvez choisir de nous aider dans le développement des filtres en Dans la section _À propos_, vous pouvez trouver des informations sur la version actuelle, des liens vers le CLUF et la Politique de confidentialité, ainsi que vers le dépôt de l'extension de navigateur sur GitHub. -![À propos \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) +![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md index efa94a944f3..d713fb1b850 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md @@ -71,4 +71,4 @@ Dans la fenêtre de dialogue ouverte, cliquez sur *Ajouter l'extension* pour ins ## Comment installer l'extension de navigateur AdGuard pour Safari -AdGuard pour Safari n'est pas une extension de navigateur au sens traditionnel. Vous pouvez en savoir plus à ce sujet dans un [article dédié](/adguard-for-safari/features/general). Ou vous pouvez [télécharger le fichier d'installation](https://agrd.io/safari_release) directement depuis cette page. +AdGuard pour Safari n'est pas une extension de navigateur au sens traditionnel. You can read more about it in a [dedicated article](/adguard-for-safari/features/general). Ou vous pouvez [télécharger le fichier d'installation](https://agrd.io/safari_release) directement depuis cette page. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index abc66257bae..6d60e956a86 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Pages protégées par le navigateur -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md index 5c5e95486c1..69a173319c9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md @@ -13,7 +13,7 @@ sidebar_position: 1 3. Activez le _Mode développeur_. - ![Mode développeur \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/developer_mode1.png) + ![Developer mode \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/developer_mode1.png) 4. Cliquez sur `background.html`. @@ -53,11 +53,11 @@ sidebar_position: 1 :::note -AdGuard s'engage à protéger votre vie privée. Nous suivons strictement notre [Politique de confidentialité](https://adguard.com/privacy/browser-extension.html) et ne collectons aucune information privée sur les utilisateurs. Avant d'envoyer vos journaux à l'équipe d'assistance, veuillez consulter le fichier car il peut contenir des informations supplémentaires que vous ne souhaitez pas partager. S'il contient de telles informations personnelles, nous vous recommandons de les supprimer au préalable. +AdGuard s'engage à protéger votre vie privée. We strictly follow our [Privacy Policy](https://adguard.com/privacy/browser-extension.html) and do not collect any private information about users. Avant d'envoyer vos journaux à l'équipe d'assistance, veuillez consulter le fichier car il peut contenir des informations supplémentaires que vous ne souhaitez pas partager. S'il contient de telles informations personnelles, nous vous recommandons de les supprimer au préalable. ::: -Maintenant que vous avez collecté les journaux, veuillez suivre ces étapes pour les soumettre à notre équipe de développement : +Now that you have collected the logs, please follow these steps to submit them to our development team: -1. Signalez le bug sur [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). -2. Envoyez votre archive avec les journaux et la durée de lecture à `devteam@adguard.com` et ajoutez un lien vers votre problème GitHub. Vous pouvez également télécharger l'archive sur Google Drive et y ajouter le lien au lieu de joindre le fichier. +1. Report the bug on [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). +2. Send your archive with logs and playback time to `devteam@adguard.com` and add a link to your GitHub issue. You can also upload the archive to Google Drive and add the link to it instead of attaching the file. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 9541b4b4db1..495a3830dcc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 1383ae20f3b..a8ec606192d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 154def8317f..fc3f8be0bce 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index 48512beccb5..aa53edbd68f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 73c5a762d61..1bc158a4532 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index c5fd9df2523..feb9485a1ab 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Scripts utilisateur -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index 5498745bf38..80885aedc84 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ C'est fait ! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index 561489f4a3c..120aa41c44c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. +Dans cet article, nous vous guiderons le long du processus de collecte des journaux de débogage, une étape de dépannage essentielle pour résoudre les problèmes complexes qui peuvent survenir. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. :::note @@ -23,9 +23,9 @@ AdGuard s'engage à protéger votre vie privée. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 05d58476391..94696a91c08 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index a7485f7661a..00000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -Cet article parle de AdGuard pour iOS, un bloqueur de contenus multifonctionnel qui protège votre appareil au niveau du système. Pour voir comment ça fonctionne, [téléchargez l'application AdGuard](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 6c20e908516..a0026fb635a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -13,15 +13,15 @@ Cet article parle de AdGuard pour iOS, un bloqueur de contenus multifonctionnel ### iPhone -Nécessite iOS 13 ou version ultérieure. +Requires iOS 13 or later. ### iPad -Nécessite iPadOS 13 ou version ultérieure. +Requires iPadOS 13 or later. ### iPod touch -Nécessite iOS 13 ou version ultérieure. +Requires iOS 13 or later. ## Installation de AdGuard pour iOS @@ -43,11 +43,11 @@ AdGuard Pro est une version payante d'AdGuard pour iOS, offrant un ensemble éla ![Sur l'écran principal de l'App Store, appuyez sur Rechercher *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Tapez *adguard* dans la barre de recherche, puis appuyez sur la chaîne *AdGuard Pro — adblock* qui s'affichera parmi les résultats de la recherche. +Tapez *adguard* dans la barre de recherche, puis appuyez sur la chaîne *adGuard pro - adblock* qui s'affichera parmi les résultats de la recherche. ![Tapez "AdGuard" dans la barre de recherche *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -Sur la page ouverte de l'App Store, appuyez sur le bouton avec le coût de la licence sous la chaîne *AdGuard Pro — adblock*, puis appuyez sur *ACHETER*. Vous pouvez être invité à saisir votre identifiant Apple et votre mot de passe. Saisissez-le et attendez que l'installation soit terminée. +Sur la page ouverte de l'App Store, appuyez sur le bouton avec le coût de la licence sous la chaîne *AdGuard Pro - adblock*, puis appuyez sur *ACHETER*. Vous pouvez être invité à saisir votre identifiant Apple et votre mot de passe. Saisissez-le et attendez que l'installation soit terminée. ![Appuyez sur OBTENIR sous l'application AdGuard *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index 90f6f09f9f7..85127140bd6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ Cet article parle de AdGuard pour iOS, un bloqueur de contenus multifonctionnel 1. Choisissez une vidéo et appuyez sur *Partager*. 1. Appuyez sur *Plus*, puis sélectionnez *Bloquer les publicités YouTube (par AdGuard)*. -La vidéo s'ouvre désormais dans le lecteur sans publicité d'AdGuard. +AdGuard ouvrira son lecteur vidéo sans publicité. ## Comment bloquer la pub sur YouTube dans Safari @@ -31,4 +31,4 @@ Assurez-vous d'avoir donné à AdGuard l'accès à tous les sites web. Vous pouv 1. Choisissez une vidéo et appuyez sur *Partager*. 1. Appuyez sur *Bloquer les publicités YouTube (par AdGuard)*. -La vidéo s'ouvre désormais dans le lecteur sans publicité d'AdGuard. +AdGuard ouvrira son lecteur vidéo sans publicité. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index 8d8af11b9ee..e8c696ab439 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ Pour accéder à *Paramètres de bas niveau*, appuyez sur l'icône d'engrenage e Il existe deux modes de tunnel principaux : *Split* et *Full*. Le mode *Split-Tunnel* assure la compatibilité d'AdGuard et des applications dites "VPN personnel". En mode *Full-Tunnel* aucun autre VPN ne peut fonctionner simultanément avec AdGuard. -Il existe une particularité du mode *Split-Tunnel* : En cas de mauvaise performance du proxy DNS, si, par exemple, la réponse du serveur DNS d'AdGuard n'est pas retournée à temps, iOS redirigera le trafic à travers le serveur DNS spécifié dans les paramètres iOS. Aucune publicité n'est bloquée pour le moment et le trafic DNS n'est pas crypté. +Il existe une particularité du mode *Split-Tunnel*  : si le proxy DNS ne fonctionne pas bien, par exemple si la réponse du serveur DNS AdGuard n'a pas été renvoyée à temps, iOS le "pénalise" et redirige le trafic via le serveur DNS, spécifié dans les paramètres iOS. Aucune publicité n'est bloquée pour le moment et le trafic DNS n'est pas crypté. -En mode *Full-Tunnel* , seul le serveur DNS spécifié dans les paramètres AdGuard est utilisé. S’il ne répond pas, Internet ne fonctionnera tout simplement pas. L'activation du mode *Full-Tunnel* peut avoir un impact négatif sur les performances de certains programmes (par exemple, FaceTime) et provoquer des problèmes de mise à jour des applications. +En mode *Full-Tunnel* , seul le serveur DNS spécifié dans les paramètres AdGuard est utilisé. S’il ne répond pas, Internet ne fonctionnera tout simplement pas. L'activation du mode *Full-Tunnel* peut entraîner des performances incorrectes de certains programmes (par exemple, FaceTime) et entraîner des problèmes avec les mises à jour des applications. Par défaut, AdGuard utilise le mode *Split-Tunnel* comme option la plus stable. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 690b9408d00..7bea6845791 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Temps, en secondes, avant d'envoyer une autre sonde keepalive à un homologue qu #### `network.https.ech.enabled` -Utilise un proxy DNS local pour rechercher des configurations dans les listes de configuration ECH. If found, encrypts Client Hellos. +Utilise un proxy DNS local pour rechercher des configurations dans les listes de configuration ECH. S'il est trouvé, il crypte ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 94ce8e6c123..6f48f554595 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ Si vous utilisez Flutter avec AdGuard en mode "Extension réseau" (ou toute autr #### Applications VPN avec API existante -Bien qu'AdGuard soit affiché comme VPN dans les paramètres système, il ne devrait provoquer aucun conflit lorsque vous travaillez avec d'autres applications basées sur VPN. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Bien qu'AdGuard soit affiché comme VPN dans les paramètres système, il ne devrait provoquer aucun conflit lorsque vous travaillez avec d'autres applications basées sur VPN. Cependant, si vous utilisez une application basée sur VPN téléchargée en dehors de l'App Store, il est possible qu'elle utilise l'ancienne API VPN et vous devez l'exclure du filtrage : 1. Ouvrez le menu AdGuard. 1. Sélectionnez *Préférences...*. @@ -79,9 +79,9 @@ Ces problèmes ont été résolus par Apple mais peuvent être rencontrés dans ### Compatibilité avec Little Snitch 5 -Pour le moment, le mode Extension réseau dans AdGuard n'est pas compatible avec [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. Ce problème est directement causé par un bug de Big Sur, et nous en avons déjà informé Apple. Cela nous fait penser que ce problème sera résolu dans l'une des prochaines mises à jour. +Pour le moment, le mode Extension réseau dans AdGuard n'est pas compatible avec [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). Lorsque les deux sont en cours d'exécution, il existe un risque de rencontrer des problèmes avec le comportement d'autres applications, même si elles ne sont pas filtrées par AdGuard. Ce problème est directement causé par un bug de Big Sur, et nous en avons déjà informé Apple. Cela nous fait penser que ce problème sera résolu dans l'une des prochaines mises à jour. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. Nous vous recommandons de passer au mode de filtrage Proxy automatique [****](#automatic-proxy) lors de l'exécution d'AdGuard avec Little Snitch sur Big Sur, au moins jusqu'à ce qu'Apple corrige le bogue. +Il faut dire que ce problème ne peut pas être résolu en désactivant la surveillance des connexions dans Little Snitch, car cette action ne décharge pas l'extension de Little Snitch du système. Nous vous recommandons de passer au mode de filtrage Proxy automatique [****](#automatic-proxy) lors de l'exécution d'AdGuard avec Little Snitch sur Big Sur, au moins jusqu'à ce qu'Apple corrige le bogue. ### Compatibilité avec les proxys locaux @@ -121,7 +121,7 @@ Tout d’abord, vous avez besoin d’un serveur fonctionnel pour votre proxy. Tr :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +Vous trouverez plus d'informations sur la façon de commencer sur le [site web de Shadowsocks](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index abaffb1bba7..379ca5883e2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ Cet article parle de AdGuard pour Mac, un bloqueur d'annonces multifonctionnel q ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". C'est un nouveau mécanisme de sécurité apparu dans High Sierra, il nécessite une autorisation explicite de votre part pour installer une extension système tierce. Pour terminer l'installation d'AdGuard, vous devez autoriser manuellement le chargement de l'extension dans *Préférences Système* → *Sécurité & Confidentialité* → *Général*. +Pendant l'installation d'AdGuard sur macOS High Sierra (ou versions ultérieures), vous pouvez voir un message : "Extension du système bloquée". C'est un nouveau mécanisme de sécurité apparu dans High Sierra, il nécessite une autorisation explicite de votre part pour installer une extension système tierce. Pour terminer l'installation d'AdGuard, vous devez autoriser manuellement le chargement de l'extension dans *Préférences Système* → *Sécurité & Confidentialité* → *Général*. ![Autoriser l'installation de l'extension dans les paramètres](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index d8f92d9c40e..d4b0ab40d93 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ Par conséquent, AdGuard ne peut pas fonctionner avec le Relais privé iCloud et 1. Le Relais privé iCloud est appliqué aux connexions au niveau de la bibliothèque, avant qu'elles n'atteignent le niveau du socket, où opère AdGuard. 2. Le Relais privé iCloud utilise QUIC, qu'AdGuard ne peut pas filtrer car le filtrage HTTP/3 n'est pas encore disponible. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Par conséquent, AdGuard bloque QUIC, y compris le trafic du Relais privé iCloud – sinon, le blocage des publicités est impossible. 4. Lorsque vous utilisez le Relais privé iCloud en mettant AdGuard en mode "split-tunnel", vous ne pouvez pas ouvrir de sites web dans Safari. 5. Pour contourner ce problème pour Monterey, nous appliquons la règle de la "route par défaut". Lorsque le Relais privé voit cette règle, il se désactive automatiquement. Ainsi, AdGuard fonctionne parfaitement sur Monterey, mais le Relais privé iCloud est désactivé. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index 7ee682a8747..0e32bc28117 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: Règles utilisateur sidebar_position: 4 --- -Les règles utilisateur peuvent être utilisées pour personnaliser le blocage des publicités. Elles peuvent être ajoutées manuellement, importées ou créées automatiquement lorsque vous bloquez un élément sur la page. Pour ajouter vos propres règles de filtrage, utilisez une [syntaxe spéciale](/general/ad-filtering/create-own-filters). +Les règles utilisateur peuvent être utilisées pour personnaliser le blocage des publicités. Elles peuvent être ajoutées manuellement, importées ou créées automatiquement lorsque vous bloquez un élément sur la page. Pour ajouter vos propres règles de classement, utilisez une [syntaxe spéciale](/general/ad-filtering/create-own-filters). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index f5357746b5d..9d55675d6d7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ L'Assistant AdGuard est un ancien assistant que vous pouvez utiliser si le [nouv C'est une extension personnalisée conçue pour lutter contre la technique de réinsertion des publicités bloquées — ce qu'on appelle le contournement des bloqueurs de publicités/réinjection de publicités. Les deux sont des méthodes anti-bloqueur de publicité avancées qui continuent de gagner en popularité parmi les annonceurs. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra est essentiellement un miniprogramme qui modifie le fonctionnement des pages de telle sorte qu'il devient beaucoup plus difficile pour les sites d'utiliser les méthodes susmentionnées pour contourner les bloqueurs. **Bloqueur AdGuard de fenêtres pop-up** -Cette extension empêche l'ouverture de fenêtres pop-up lorsque vous consultez des pages web. Certaines fenêtres pop-up sont considérées comme utiles — elles peuvent contenir des paramètres pour l'administration du site ou des informations de référence supplémentaires affichées lorsque l'on clique sur un lien. C'est pourquoi vous pouvez désactiver le Bloqueur si nécessaire. Cette extension ne fonctionne pas non plus sur les sites web ajoutés à la liste d'exceptions d'AdGuard. Elle est désactivée par défaut, mais vous pouvez l'activer dans les paramètres de l'application. You will find more detailed information about this extension in our Knowledge Base. +Cette extension empêche l'ouverture de fenêtres pop-up lorsque vous consultez des pages web. Certaines fenêtres pop-up sont considérées comme utiles — elles peuvent contenir des paramètres pour l'administration du site ou des informations de référence supplémentaires affichées lorsque l'on clique sur un lien. C'est pourquoi vous pouvez désactiver le Bloqueur si nécessaire. Cette extension ne fonctionne pas non plus sur les sites web ajoutés à la liste d'exceptions d'AdGuard. Elle est désactivée par défaut, mais vous pouvez l'activer dans les paramètres de l'application. Vous trouverez des informations plus détaillées sur cette extension dans notre Base de connaissances. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust vous permet de voir la réputation de chaque site web en fonction d ### Réseau -L'avant-dernier module est consacré au filtrage du réseau, et vous y trouverez des options supplémentaires liées au réseau. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Ce sont des précautions supplémentaires importantes pour mieux filtrer votre espace web. La plupart des sites web utilisent désormais HTTPS, et il en va de même pour la publicité. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +L'avant-dernier module est consacré au filtrage du réseau, et vous y trouverez des options supplémentaires liées au réseau. Deux d'entre eux sont activés par défaut : _Activer le filtrage du trafic_ et _Filtrer le protocole HTTPS_. Ce sont des précautions supplémentaires importantes pour mieux filtrer votre espace web. La plupart des sites web utilisent désormais HTTPS, et il en va de même pour la publicité. Sur de nombreux sites, comme youtube.com, facebook.com et twitter.com, c'est impossible de supprimer les publicités sans filtrage HTTPS. Gardez donc la fonctionnalité _Filtrer le protocole HTTPS_ activée, sauf si vous avez de bonnes raisons de ne pas le faire. ![Paramètres réseau \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3701beb0f..b864ef25ceb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ _Paramètres_ est la section qui nécessite un maximum d'attention. C'est ici qu ### Paramètres généraux -Ici, vous pouvez définir la langue et le thème (Sombre ou Clair), activer le lancement d'AdGuard au démarrage du système et les mises à jour automatiques silencieuses, choisir la chaîne de mise à jour et filtrer l'intervalle de vérification des mises à jour. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +Ici, vous pouvez définir la langue et le thème (Sombre ou Clair), activer le lancement d'AdGuard au démarrage du système et les mises à jour automatiques silencieuses, choisir la chaîne de mise à jour et filtrer l'intervalle de vérification des mises à jour. Les paramètres sont également l'endroit où aller si AdGuard pour Windows ne fonctionne pas correctement et si l'équipe d'assistance vous a demandé de [collecter les _journaux de débogage_](/adguard-for-windows/solving-problems/adguard-logs.md). ![Paramètres avancés \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ Il existe plusieurs sites web dont l'accès doit être restreint à partir d'un Le module vérifie le contenu des pages web ouvertes dans le navigateur et filtre celles dont le contenu est indésirable pour les enfants : images et textes pour adultes, langage grossier, violence, propagande de drogue, etc. Les paramètres du Contrôle Parental sont protégés par mot de passe pour que l'enfant ne puisse pas contourner les restrictions. Ce module bloque non seulement les directions vers des sites indésirables, mais peut également supprimer des résultats de recherche les liens inappropriés pour les enfants. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Vous pouvez également cocher la case _Bloquer le téléchargement des fichiers exécutables_ pour empêcher votre enfant de télécharger et d'installer des logiciels sur l'ordinateur. Il existe deux autres options dans le module _Contrôle parental_ : vous pouvez sélectionner un utilisateur Windows spécifique à protéger par le _Contrôle parental_ et définir un mot de passe pour protéger les paramètres AdGuard contre toute modification. +Dans le module Contrôle Parental, vous pouvez activer la _recherche sécurisée_ et gérer la _liste de blocage_ et la _liste d'autorisation_ pour personnaliser le fonctionnement de cette option. Vous pouvez également cocher la case _Bloquer le téléchargement des fichiers exécutables_ pour empêcher votre enfant de télécharger et d'installer des logiciels sur l'ordinateur. Il existe deux autres options dans le module _Contrôle parental_ : vous pouvez sélectionner un utilisateur Windows spécifique à protéger par le _Contrôle parental_ et définir un mot de passe pour protéger les paramètres AdGuard contre toute modification. ![Contrôle parental \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index f676a77123a..9db0d7d5f00 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ Cet article parle de AdGuard pour Windows, un bloqueur de contenus multifonction To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Allez sur le site [AdGuard](http://adguard.com) dans la barre d'adresse et cliquez *Télécharger* [sur la page qui s'ouvre](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 92fe6bbe2e5..9f52d8ee43a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard s'engage à protéger votre vie privée. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard s'engage à protéger votre vie privée. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 31f59529280..95e38b825b6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index 7a6b0e550de..34b17cae48a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ Cet article parle de AdGuard pour Windows, un bloqueur de contenus multifonction AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index c69c3700eb4..0ad77f2a065 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 22c8afa0d79..c4e506ae0b5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 6661a04b561..1db987717f8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index c32f96e7493..80a4897fdc8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 38c0d95af9a..05545421ae7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ Cet article parle de AdGuard pour Windows, un bloqueur de contenus multifonction ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/account/features.md index d4906e7968c..8476387ec46 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ La section Historique des achats affiche toutes les licences que vous avez déj ## Contacter l'assistance -L'onglet Assistance contient des liens utiles pour vous aider à résoudre des problèmes ou à trouver des réponses à vos questions sur les produits AdGuard. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +L'onglet Assistance contient des liens utiles pour vous aider à résoudre des problèmes ou à trouver des réponses à vos questions sur les produits AdGuard. Ils sont divisés en six sections : FAQ, Envoyer un rapport de bug/une demande de fonctionnalité, Signaler un blocage incorrect, Contacter le support, Base de connaissances et Discuter. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index aab2b965bbb..e7ef7fc7389 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ Cet article concerne les filtres que nous créons pour les utiliser dans AdGuard - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 95456b9621f..b16e46eab80 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-------------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:-------------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:-------------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:-------------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard pour iOS][ios-app] | [AdGuard pour Safari][ext-saf] | [Bloqueur de contenu AdGuard][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,32 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard pour Safari" -[ext-saf]: #what-product "AdGuard for Safari" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 93d732db931..0e2b56d8733 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ Les filtres de blocage publicitaire d'AdGuard sont les suivants : - Filtre de base AdGuard - Filtre de publicités mobiles AdGuard - Filtres régionaux divisés par principe linguistique : chinois, néerlandais, français, allemand, japonais, russe, espagnol/portugais, turc et ukrainien -- AdGuard Quick Fixes filter ### L'objectif de ces filtres - **Le filtre de base** est conçu pour bloquer les publicités sur les sites web en anglais et ceux pour lesquels il n'existe pas de filtre séparé. Il contient également des règles générales de filtrage qui s'appliquent à tous les sites web quelle que soit la langue - Le **Filtre de publicités mobiles** bloque les publicités sur les versions mobiles des sites web et dans les applications mobiles. Il n'y a pas de segmentation basée sur la langue - Les **Filtres régionaux** suivent la même politique que le **Filtre de base**, mais sont limités aux sites web dans certaines langues -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. L'objectif des filtres de blocage des publicités est de bloquer tous les types de publicité sur les sites web, les applications et certains appareils qui peuvent charger des publicités depuis Internet : diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/browsing-security.md index c658a519430..9b78b43899d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Les victimes d'hameçonnage et de logiciels malveillants restent un problème courant. Pour améliorer la sécurité numérique, nous avons incorporé des filtres spéciaux dans les produits AdGuard pour vous protéger contre les sites web malveillants et ceux de phishing. À ce jour, nous avons catégorisé plus de 15 millions de sites et construit une base de données de 1,5 million de sites web connus pour hameçonnage et maliciels. À l'aide de cette base de données, AdGuard vérifie les sites web que vous visitez pour vous protéger contre les menaces en ligne. -:::note +::: note Nous ne collectons ni n'utilisons aucune information sur les sites web que vous visitez. ::: -## How does AdGuard check websites? +## Comment AdGuard vérifie-t-il les sites web ?​ Chaque fois que vous visitez un site web, votre client local échange des informations avec notre serveur backend sous forme de hachages et de préfixes de hachage. Sur la base de cet échange, le client local détermine si le site web figure ou non dans la base de données des sites web potentiellement dangereux. Il existe une différence dans la portée de cette vérification pour les applications et les extensions. @@ -61,11 +61,11 @@ AdGuard gère une vaste base de données de sites web d'hameçonnage et de logic Nous analysons automatiquement les plaintes concernant les sites web suspects et passons beaucoup de temps à maintenir la base de données à jour, à nettoyer les faux positifs et à mettre en place des mécanismes pour les éviter à l'avenir. -### Want to help? +### Vous souhaitez nous aider ? Nous apprécions toute votre aide ! Si vous rencontrez un site d'hameçonnage ou de maliciels, veuillez le signaler à . -### False-positive responses +### Réponses faussement positives Il arrive que des sites web non malveillants soient ajoutés aux filtres d'AdGuard. Nous faisons de notre mieux pour réduire le pourcentage de faux positifs, mais il y en a toujours. Si vous rencontrez ce comportement de la part d'AdGuard, veuillez signaler le faux positif à notre assistance technique à . diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/license/what-is.md index f4ab0c6fd44..405a09f43b3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: Qu'est-ce qu'une licence AdGuard ? sidebar_position: 1 --- @@ -12,7 +12,7 @@ Sur la [page d'achat](https://adguard.com/license.html), vous pouvez voir les ty - **Les abonnements d'un an** — ces licences sont renouvelées automatiquement chaque année ou peuvent être prolongées manuellement - Personnelles — jusqu’à 3 appareils - Familiales — jusqu'à 9 appareils -- **Lifetime** — these licenses are perpetual +- **À vie** — ces licences ne sont pas limitées dans le temps - Personnelles — jusqu’à 3 appareils - Familiales — jusqu'à 9 appareils diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/stealth-mode.md index d9809a95b38..82bfe427080 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ L'activation de cette option empêchera le navigateur d'envoyer des données GPS ### Bloquer Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. L'activation de ce paramètre permet à AdGuard de bloquer la capacité des navigateurs à détecter les composants (tels que les plugins et les objets ActiveXObject) qui permettent à Flash d'afficher du contenu. Cela signifie que les navigateurs ne peuvent pas prendre en charge Flash. +Le plugin Flash Player est devenu de plus en plus vulnérable aux menaces en ligne telles que les virus et les pirates informatiques ; il peut également affecter de manière significative le temps de chargement des sites web. L'activation de ce paramètre permet à AdGuard de bloquer la capacité des navigateurs à détecter les composants (tels que les plugins et les objets ActiveXObject) qui permettent à Flash d'afficher du contenu. Cela signifie que les navigateurs ne peuvent pas prendre en charge Flash. ### Bloquer Java {#java} @@ -95,7 +95,7 @@ Vous pouvez également définir une valeur arbitraire pour le référent en la s Notez que pour pouvoir filtrer le trafic, les applications AdGuard "interceptent" les requêtes navigateur-serveur. Les requêtes adressées aux serveurs de publicité, de suivi et d'hameçonnage peuvent être modifiées avant d'être envoyées au serveur ou bloquées complètement. Idem pour l'option *Masquer le référent aux tiers* : AdGuard intercepte les requêtes HTTP(S), notamment pour supprimer ou modifier l'en-tête référent si cette option est activée. Toutefois, cela ne se produit qu'une fois que ces requêtes "quittent" le navigateur. Cela signifie que si vous surveillez le référent dans le navigateur (par exemple, avec l'aide des outils de développement de Chrome), vous verrez le référent d'origine car la requête n'a pas encore atteint AdGuard. Vous pouvez utiliser des logiciels tels que [Fiddler](https://www.telerik.com/fiddler) pour vous assurer que le référent est modifié correctement. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. Elle modifiera le référent à ce moment précis, de sorte que les outils de développeur afficheront le référent souhaité pour vos demandes. +En revanche, comme toutes les extensions de navigateur, l'Extension AdGuard fonctionne "à l'intérieur" du navigateur. Elle modifiera le référent à ce moment précis, de sorte que les outils de développeur afficheront le référent souhaité pour vos demandes. ### Masquer votre agent utilisateur {#useragent} @@ -120,9 +120,3 @@ L’inspection approfondie des paquets ou IPP est un système d’analyse et de AdGuard peut modifier les données des paquets sortants afin que le client ne relève pas des critères de blocage IPP. Cela signifie qu'en activant cette option, les utilisateurs peuvent accéder au contenu qu'ils souhaitent. Tous les systèmes IPP ne peuvent pas être contournés pour le moment, mais nous travaillons constamment à les améliorer. La fonction "Protection anti IPP" est déjà implémentée dans AdGuard pour Windows, AdGuard pour Mac et AdGuard pour Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/fr/docusaurus-plugin-content-docs/current/general/userscripts.md index 8360f7b6d5b..6c08f37d74e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. Ils modifient ou élargissent les fonctionnalités d'un ou plusieurs sites web. De nombreux utilisateurs d'AdGuard sont peut-être déjà familiers avec des scripts utilisateur tels que AdGuard Assistant, Popup Blocker et AdGuard Extra. +Les scripts utilisateurs ou userscripts (que nous appelons aussi "extensions") sont, en fait, des miniprogrammes écrits en JavaScript. Ils modifient ou élargissent les fonctionnalités d'un ou plusieurs sites web. De nombreux utilisateurs d'AdGuard sont peut-être déjà familiers avec des scripts utilisateur tels que AdGuard Assistant, Popup Blocker et AdGuard Extra. :::note Applications prises en charge @@ -134,7 +134,7 @@ Voici un [lien d'envoi d'email](mailto:devteam@adguard.com?Subject=Userscript%20 ##### Propriétés non prises en charge -These properties will be simply ignored by AdGuard. +Ces propriétés seront simplement ignorées par AdGuard. ```text @unwrap diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/fr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index ad50e5f629b..eff1d3e5cf2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: Comment collecter un fichier HAR sidebar_position: 1 --- diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/fr/docusaurus-plugin-content-docs/current/guides/report-bugs.md index eea15f2568c..dd13e791af0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Vérifier si le bogue n'a pas déjà été signalé. Nous vous conseillons de pr ### Comment décrire un problème -Essayez de fournir autant de détails que possible – cela nous permettra de reproduire plus facilement le bug et de trouver comment le corriger. Here’s what we expect a bug report to include: +Essayez de fournir autant de détails que possible – cela nous permettra de reproduire plus facilement le bug et de trouver comment le corriger. Voici ce que nous nous attendons à voir dans un rapport de bug : - La version de votre application - La version de votre système d’exploitation @@ -28,7 +28,7 @@ Essayez de fournir autant de détails que possible – cela nous permettra de re ### Comment collecter les journaux -Read about collecting logs in dedicated articles for each platform. +Découvrez comment collecter des journaux dans des articles dédiés à chaque plateforme. ## Comment voter pour les rapports de bogues ou les demandes de fonctionnalités diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/fr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index 3e4e3bbd78d..15fb1c3213e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ Sur certains ordinateurs portables, vous devrez maintenir *Fn* puis appuyer sur Windows capture tout l'écran et le copie dans le presse-papiers. -To take a screenshot of an active window, use the following shortcut keys: +Pour prendre une capture d'écran d'une fenêtre active, utilisez le raccourci suivant : - **Maintenez *Alt* enfoncé et appuyez sur *PrtScn* (ou *Fn + Alt + PrtScn* sur certains ordinateurs portables)** -To take a screenshot of a specific area, use the following shortcut keys: +Pour prendre une capture d'écran d'une zone spécifique, utilisez le raccourci suivant : - ***Appuyez sur ***Win + Shift + S****** -Une fois la capture d'écran prise, elle sera enregistrée dans le presse-papiers. Dans la plupart des cas, vous pourrez la coller dans un document que vous êtes en train de rédiger en utilisant le raccourci *Ctrl + V*. Alternativement, si vous devez enregistrer la capture d'écran dans un fichier, vous devez ouvrir le programme standard **Paint** (ou toute autre application pouvant travailler avec des images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +Une fois la capture d'écran prise, elle sera enregistrée dans le presse-papiers. Dans la plupart des cas, vous pourrez la coller dans un document que vous êtes en train de rédiger en utilisant le raccourci *Ctrl + V*. Alternativement, si vous devez enregistrer la capture d'écran dans un fichier, vous devez ouvrir le programme standard **Paint** (ou toute autre application pouvant travailler avec des images). Collez-y votre capture d'écran en utilisant le même raccourci ou en cliquant sur le bouton Coller (généralement dans le coin supérieur gauche de l'écran), puis enregistrez-la. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. Dès que vous appuyez sur ces touches, la capture d'écran sera automatiquement enregistrée sous forme de fichier dans votre dossier *Images* → *Dossier de captures d'écran*. +Windows 8 et 10 vous permettent de prendre une capture d'écran très rapidement avec le raccourci *Win + PrtScn*. Dès que vous appuyez sur ces touches, la capture d'écran sera automatiquement enregistrée sous forme de fichier dans votre dossier *Images* → *Dossier de captures d'écran*. Il existe également un programme dédié pour prendre des captures d'écran appelé *Snipping Tool* que vous pouvez trouver via le menu Démarrer parmi les programmes standard de votre ordinateur. Snipping Tool vous permet de capturer n'importe quelle zone de votre bureau ou de l'écran entier. Après avoir pris une capture d'écran à l'aide de ce programme, vous pouvez modifier l'image et l'enregistrer dans n'importe quel dossier de votre ordinateur. @@ -70,26 +70,26 @@ En outre, vous pouvez également essayer d'utiliser des applications différente ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Pour prendre une capture d'écran sur un appareil Mac, utilisez le raccourci suivant : - ***Appuyez et maintenez ***⌘ Cmd + Shift + 3****** Votre Mac capturera tout l'écran et l'enregistrera sous forme de fichier sur le bureau. -To take a screenshot of an active window, use the following shortcut keys: +Pour prendre une capture d'écran d'une fenêtre active, utilisez le raccourci suivant : - **Appuyez et maintenez *⌘ Cmd + Shift + 4 + barre d'espace*. Le pointeur se transforme en icône d'appareil photo. Cliquez sur la fenêtre pour la capturer. Appuyez sur Échap pour annuler la prise de capture d'écran** -To take a screenshot of a specific area, use the following shortcut keys: +Pour prendre une capture d'écran d'une zone spécifique, utilisez le raccourci suivant : - ***Appuyez sur ***⌘ Cmd + Shift + 5******. Faites glisser le pointeur pour sélectionner la zone requise. Relâchez votre souris ou votre trackpad pour prendre une capture d'écran, appuyez sur Echap pour l'annuler. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +Pour réaliser une capture d'écran de *la barre tactile* (MacBook Pro), utilisez le raccourci suivant : - ***Appuyez ***⌘ Cmd + Shift + 6****** Votre Mac capture l'intégralité de la *Barre tactile* et l'enregistre sous forme de fichier sur le bureau. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +Pour copier une capture d'écran dans le presse-papiers au lieu de l'enregistrer, maintenez la touche *Ctrl* enfoncée avec l'un des raccourcis ci-dessus. Vous pouvez ensuite coller la capture d'écran (depuis le presse-papiers) dans un document ou une image que vous êtes en train de modifier en utilisant le raccourci *Cmd + V* . Vous pouvez également faire des captures d'écran en utilisant l'**Aperçu** et en choisissant **Faire une capture d'écran** (de la zone, de la fenêtre ou de l'écran entier sélectionné). Avec **Aperçu** vous pouvez enregistrer vos captures d'écran au format JPG, TIFF, PDF et autres formats de fichiers. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/intro.md b/i18n/fr/docusaurus-plugin-content-docs/current/intro.md index ff77d436a24..9a75cc0921e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index e1c92200dca..28b6ff96a84 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Les sites web modifient constamment la manière dont ils intègrent les publicit Toutefois, l'utilisation de filtres de blocage nécessite des compétences spécifiques. Si vous les avez et si vous savez comment créer des règles, rendez-vous directement sur notre référentiel[répositoire des Filtres AdGuard](https://github.com/AdguardTeam/AdguardFilters) sur GitHub. Vous y trouverez de nombreux problèmes actifs, chacun faisant référence à un problème de site web - une annonce manquée, un faux positif, etc. Choisissez-en une et suggérez vos propres règles dans les commentaires. Les ingénieurs des filtres AdGuard examineront vos suggestions et, s'ils les jugent appropriées, vos règles seront ajoutées aux filtres AdGuard. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +Si vous n'êtes pas encore familiarisé avec la syntaxe de nos règles de filtrage, ou si vous avez besoin d'un rappel, vous trouverez les bases de la syntaxe [dans notre Base de connaissances](/general/ad-filtering/create-own-filters). ### Récompenses {#rewards} diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index 09c4222016e..9923d63cfc6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Devenir traducteur/réviseur sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +Si vous souhaitez aider à traduire les produits, les sites web et les Bases de connaissances AdGuard, accédez à [Crowdin](https://crowdin.com/) et inscrivez-vous/connectez-vous. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index 3871d5f9953..c14ce29997a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ Faisant face à une traduction qui nécessite l'utilisation de pluriels, vous ne Voici quelques sources d'informations que vous pouvez utiliser. -[Guide de localisation](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contient une large liste de langues. Le nombre de formes plurielles pour les langues différentes est indiqué de cette façon : `nplurals=2`, `nplurals=4` et ainsi de suite. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Guide de localisation](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contient une large liste de langues. Le nombre de formes plurielles pour les langues différentes est indiqué de cette façon : `nplurals=2`, `nplurals=4` et ainsi de suite. Le chiffre après le signe Égal `=` signifie le nombre de formes plurielles de la langue respective. En outre, vous pouvez obtenir des informations sur les formes plurielles dans le répertoire [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). Les règles plurielles CLDR indiquent une forme de mot supplémentaire pour les nombres décimaux (1.5 ; 2.3 ; 100.1…), mais nous ne les utilisons pas dans les traductions AdGuard. diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 2431225f540..bf195a0e855 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: Programme de traduction AdGuard sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Avis de non-responsabilité :** vous pouvez nous poser des questions sur la traduction d'AdGuard en envoyant un e-mail à [translate@adguard.com](mailto:translate@adguard.com) ou en rejoignant notre [chat sur Telegram](https://t.me/joinchat/UVYTLcHbr8JmOGIy). -When it comes to translations, we at AdGuard always heavily rely on volunteers. +En ce qui concerne les traductions, chez AdGuard, nous comptons toujours beaucoup sur les bénévoles. -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +Nous utilisons désormais la plateforme [Crowdin](https://crowdin.com/) pour gérer les traductions de nos produits. C'est donc l'endroit idéal pour tous ceux qui souhaitent contribuer à AdGuard en traduisant l'un de nos produits. -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +Si vous souhaitez faire partie des bénévoles qui nous aident à traduire AdGuard, veuillez lire les informations sur [comment devenir notre traducteur](../become-translator) et [comment nous collaborons avec eux](../rewards). diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 2ab5c9e6813..52647a0ecad 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: Comment hiérarchiser les traductions des fichiers Crowdin sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +Il existe cinq grands projets AdGuard sur Crowdin - [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), et [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). Nous n'avons pas de directives claires sur les fichiers ou les produits avec lesquels commencer travailler sur le projet *AdGuard Applications*. Choisissez simplement n'importe quel produit que vous préférez. Il y a juste deux ou trois choses que nous voulons mentionner : -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- Vous ne pouvez voir l'application que dans les langues pour lesquelles toutes les traductions sont effectuées dans Crowdin ; - Nous vous recommandons de traduire les descriptions des magasins d'applications en deuxième lieu, car sans la traduction des produits eux-mêmes, les descriptions ne seront pas nécessaires. La situation est différente dans le projet *AdGuard Websites*. Des langues peuvent être ajoutées au site même si un ensemble complet de traductions n'est pas disponible. Toutefois, cela dépend des fichiers qui ont déjà été traduits. C'est pourquoi nous vous recommandons de commencer par les fichiers les plus importants — ils sont répertoriés ci-dessous : diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 037397dcd22..893f0e152e3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/fr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Mise à jour de la Base de connaissances sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. Mais les choses évoluent constamment et il arrive qu'un article ne reflète plus l'état actuel des choses. +L'objectif de la Base de connaissances du Bloqueur des annonces AdGuard est de fournir à chacun les informations les plus récentes sur toutes sortes de sujets liés à AdGuard. Mais les choses évoluent constamment et il arrive qu'un article ne reflète plus l'état actuel des choses. C'est pourquoi nous avons placé l'ensemble du contenu de notre base de données sur [GitHub](https://github.com/AdguardTeam/KnowledgeBase). Désormais, tout le monde peut y contribuer en suggérant des modifications et des traductions pour les articles existants, ainsi que de nouveaux articles. ## Comment suggérer un changement ou écrire un nouvel article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. Si vous n'êtes pas familier avec les principes de travail avec la plate-forme, commencez par lire la [documentation GitHub](https://docs.github.com/en). +Vous pouvez suggérer des modifications aux articles actuels et en ajouter de nouveaux à la Base de connaissances en utilisant la fonctionnalité de GitHub mentionné ci-dessus. Si vous n'êtes pas familier avec les principes de travail avec la plate-forme, commencez par lire la [documentation GitHub](https://docs.github.com/en). -Une fois que vous êtes prêt à commencer, procédez dans [le référentiel KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Gardez cela à l'esprit lorsque vous modifiez ou rédigez des articles. Suivez [ce lien](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) pour apprendre plus sur la syntaxe Markdown. +Une fois que vous êtes prêt à commencer, procédez dans [le référentiel KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase). Tous les textes de notre Base de connaissances sont rédigés en langage de balisage `Markdown`. Gardez cela à l'esprit lorsque vous modifiez ou rédigez des articles. Suivez [ce lien](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) pour apprendre plus sur la syntaxe Markdown. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. Lorsque vous suggérez des modifications ou des ajouts d'infos, tenez compte du fait que tous les documents doivent respecter les principes de la plateforme. Vous pouvez en prendre connaissance dans les [Guides sur Docusaurus](https://docusaurus.io/docs/category/guides). +Le site web de la Base de connaissances est construit à l'aide de Docusaurus 2 - un générateur moderne de sites web statiques. Lorsque vous suggérez des modifications ou des ajouts d'infos, tenez compte du fait que tous les documents doivent respecter les principes de la plateforme. Vous pouvez en prendre connaissance dans les [Guides sur Docusaurus](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +Vous pouvez déployer cette Base de connaissances localement sur votre ordinateur pour prévisualiser les modifications que vous suggérez. Vous trouverez des instructions détaillées sur la façon de procéder à l'adresse [dans le fichier README.md](https://github.com/AdguardTeam/KnowledgeBase#readme) sur la page GitHub de cette Base de connaissances. ## La traduction des articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +La traduction des articles existants de la Base de connaissances est réalisée sur [la plateforme Crowdin](https://crowdin.com/profile/adguard). Tous les détails sur les traductions et le travail avec Crowdin peuvent être trouvés [dans l'article dédié](../translate/guidelines) de la Base de connaissances du Bloqueur AdGuard. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [Dans un article séparé](../translate/plural-forms), nous avons décrit en détail les difficultés qui peuvent survenir lors de la traduction de chaînes avec des formes plurielles, et avons donné des instructions détaillées sur la façon de les utiliser sur la plate-forme Crowdin. +Lorsque vous travaillez sur des articles de la Base de connaissances de AdGuard, vous pouvez rencontrer des chaînes contenant des formes plurielles que vous devrez traduire avec une attention particulière. [Dans un article séparé](../translate/plural-forms), nous avons décrit en détail les difficultés qui peuvent survenir lors de la traduction de chaînes avec des formes plurielles, et avons donné des instructions détaillées sur la façon de les utiliser sur la plate-forme Crowdin. ## Le travail sur les questions ouvertes -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choisissez un sujet qui vous intéresse et commencez à travailler dessus. Si vous avez des questions, vous pouvez les poser directement dans les commentaires de cette tâche. +Parfois, il y aura des [tâches ouvertes](https://github.com/AdguardTeam/KnowledgeBase/issues) liées à la mise à jour de la Base de connaissances. Vous pouvez nous aider à accélérer leur réalisation [de la même manière](#suggest-change) que vous suggéreriez toute autre modification à cette Base de connaissances. Choisissez un sujet qui vous intéresse et commencez à travailler dessus. Si vous avez des questions, vous pouvez les poser directement dans les commentaires de cette tâche. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/hr/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/hr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/hr/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/hr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/intro.md b/i18n/hr/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/hr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index f1a1bafde7f..6e7c76df742 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index b5cd7b222fd..65ba2274929 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index fcf01a5d5db..94d05e47222 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 74d88331007..f864ec68b35 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index d9bed22b318..03b410cdd3a 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index c20496553e4..f808f6d0e70 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Az az idő másodpercben, amíg újabb keepalive próbát küld egy nem reagál #### `network.https.ech.enabled` -Helyi DNS-proxyt használ a konfigurációk keresésére az ECH konfigurációs listákban. If found, encrypts Client Hellos. +Helyi DNS-proxyt használ a konfigurációk keresésére az ECH konfigurációs listákban. Ha megtalálja, titkosítja a ClientHellost. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 34a719794c9..a0a306bfde4 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index 90e4514b189..8af3934d6ca 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index f6e7208b541..5ca19a0ea97 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 7b0accbaae6..271e55685d7 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 2c9a5ecffca..cd84ac7fdd9 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ Az AdGuard hirdetésblokkoló szűrői a következők: - AdGuard Alap szűrő - AdGuard Mobile App Banners szűrő - Regionális szűrők nyelvi elvek szerint - kínai, holland, francia, német, japán, orosz, spanyol/portugál, török, német, ukrán és orosz -- AdGuard Quick Fixes filter ### Ezeknek a szűrőknek a célja - A **Az** alapszűrő célja, hogy blokkolja a hirdetéseket az angol nyelvű webhelyeken és azokon, amelyekhez nincs külön szűrő. Általános szűrési szabályokat is tartalmaz, amelyek nyelvtől függetlenül minden webhelyre vonatkoznak - A **mobilhirdetések szűrője** blokkolja a hirdetéseket a weboldalak mobilverzióiban és a mobilalkalmazásokban. Nincs nyelvi szegmentálás - **A** regionális szűrők ugyanazt az irányelvet követik, mint a **Alapszűrő**, de bizonyos nyelvű webhelyekre korlátozva -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. A hirdetésblokkoló szűrők célja, hogy blokkoljanak mindenféle hirdetést olyan webhelyeken, alkalmazásokban és bizonyos eszközökön, amelyek hirdetéseket tölthetnek be az internetről: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 0aebc8d7fd7..681a7364777 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::figyelem - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/hu/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/hu/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/hu/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/hu/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/intro.md b/i18n/hu/docusaurus-plugin-content-docs/current/intro.md index 0b50d7a9224..6b8edf1f801 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ De ingyenes böngészőbővítményeket is fejlesztünk és tartunk fenn minden ## Nem csak reklámblokkolás -Az AdGuard Ad Blocker nem csak a hirdetéseket blokkolja. Megvédi Önt az online nyomon követéstől, és számos módon javítja a magánéletét. Az adott terméktől függően az AdGuard olyan előnyöket is kínálhat, mint a DNS-szűrés a kerekebb védelem érdekében, a szülői felügyelet, amely megvédi a gyerekeket a nem megfelelő tartalomtól, a szűrési napló az internetes forgalom jobb ellenőrzése érdekében és még sok más. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +Az AdGuard Ad Blocker nem csak a hirdetéseket blokkolja. Megvédi Önt az online nyomon követéstől, és számos módon javítja a magánéletét. Az adott terméktől függően az AdGuard olyan előnyöket is kínálhat, mint a DNS-szűrés a kerekebb védelem érdekében, a szülői felügyelet, amely megvédi a gyerekeket a nem megfelelő tartalomtól, a szűrési napló az internetes forgalom jobb ellenőrzése érdekében és még sok más. Ez a tudásbázis részletes információkat tartalmaz mindegyikről - nyugodtan ugorjon bármelyik cikkre, amelyik érdekli. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/hu/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md index b4fa2433ec7..416251656d0 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md @@ -9,18 +9,18 @@ Questo articolo riguarda l'Estensione di browser AdGuard, che protegge solo il t ::: -[L'estensione del browser AdGuard](https://adguard.com/adguard-browser-extension/overview.html) è un'estensione gratuita che funziona su cinque browser popolari: Chrome, Firefox, Edge, Opera e Yandex Browser. Puoi trovarla facilmente sul negozio online del tuo browser o sul nostro sito web ufficiale. +[AdGuard Browser Extension](https://adguard.com/adguard-browser-extension/overview.html) is a free extension that works in five popular browsers: Chrome, Firefox, Edge, Opera, and Yandex Browser. Puoi trovarla facilmente sul negozio online del tuo browser o sul nostro sito web ufficiale. -![Estensione del browser AdGuard per Chrome \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) +![AdGuard Browser Extension for Chrome \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) -Le estensioni del browser includono funzionalità di base per il blocco degli annunci, ma non possono essere paragonate ai programmi desktop completi, come [AdGuard per Windows](/adguard-for-windows/features/home-screen) e [AdGuard per Mac](/adguard-for-mac/features/main). +Browser extensions include basic ad-blocking features but cannot be compared with full-featured desktop programs, such as [AdGuard for Windows](/adguard-for-windows/features/home-screen) and [AdGuard for Mac](/adguard-for-mac/features/main). -![Disponibile per i browser più diffusi \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) +![Available for most popular browsers \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) :::note -Per Safari, abbiamo un'estensione indipendente. Dal rilascio di [Safari 13](https://adguard.com/en/blog/adguard-safari-1-5.html), la maggior parte delle estensioni di blocco degli annunci ha riscontrato enormi problemi e molte di esse hanno smesso di funzionare. Abbiamo dovuto sviluppare una [estensione separata per Safari](/adguard-for-safari/features/general) che presenta alcune differenze rispetto all'estensione descritta in questo articolo. +Per Safari, abbiamo un'estensione indipendente. Since the release of [Safari 13](https://adguard.com/en/blog/adguard-safari-1-5.html), most of the ad-blocking extensions have experienced huge issues and many of them stopped functioning. We had to develop a [separate extension for Safari](/adguard-for-safari/features/general) that has some differences in comparison with the extension described in this article. ::: -**Non dimenticare che la funzionalità di ogni estensione è rigorosamente limitata dalle capacità del browser**. Quindi, se desideri ottenere una protezione completa, considera d'installare un programma indipendente per il tuo computer. There's [a reason why](adguard-browser-extension/comparison-standalone). +**Do not forget that the functionality of each extension is strictly limited by the browser’s capabilities.** So if you want to get full-fledged protection, consider installing a standalone program for your computer. There's [a reason why](adguard-browser-extension/comparison-standalone). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 6c6cf2536e2..121c1314f6e 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -1,5 +1,5 @@ --- -title: Comparazione con le app autonome +title: Comparison to standalone apps sidebar_position: 7 --- @@ -17,10 +17,10 @@ La seconda differenza è che le possibilità del blocco degli annunci basato sul Mentre l'estensione di browser AdGuard è gratuita e facile da installare e contiene filtri per bloccare annunci e combattere le minacce online, le app complete sono più potenti e includono un elenco di funzionalità avanzate. Visualizza tutte le differenze nella seguente tabella comparativa. -![Estensione vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) +![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — entro le limitazioni del browser ed esclusivamente sul browser in cui è installata; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — l'estensione non è in grado di rilevare le richieste da altre estensioni. Se un'estensione dannosa o di tracciamento invia una richiesta al proprio server per mostrarti annunci o tracciare la tua attività, l'estensione del browser AdGuard non sarà in grado di bloccare tale richiesta; +`2` – the extension is unable to detect requests from other extensions. Se un'estensione dannosa o di tracciamento invia una richiesta al proprio server per mostrarti annunci o tracciare la tua attività, l'estensione del browser AdGuard non sarà in grado di bloccare tale richiesta; -`3` — non tutti i tipi di annunci e minacce possono essere bloccati dalle estensioni del browser per via di alcune limitazioni dello stesso. Alcuni elementi potrebbero arrivare sulla pagina e rallentare il processo di caricamento. Inoltre, a differenza del blocco di annunci basato su browser, l'app di AdGuard blocca gli annunci prima che siano caricati sul browser. Ciò, risparmia traffico e velocizza il caricamento della pagina. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Alcuni elementi potrebbero arrivare sulla pagina e rallentare il processo di caricamento. Inoltre, a differenza del blocco di annunci basato su browser, l'app di AdGuard blocca gli annunci prima che siano caricati sul browser. Ciò, risparmia traffico e velocizza il caricamento della pagina. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md index 5dd3cccf19e..4bb1ba6a5cb 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md @@ -1,5 +1,5 @@ --- -title: Compatibilità con l'app autonoma +title: Compatibility with the standalone app sidebar_position: 4 --- @@ -9,16 +9,16 @@ Questo articolo riguarda l'Estensione di browser AdGuard, che protegge solo il t ::: -Mentre l'estensione del browser AdGuard può bloccare gli annunci nei browser, i [programmi autonomi AdGuard](/adguard-browser-extension/comparison-standalone) filtrano tutto il traffico sul tuo dispositivo, incluso quello proveniente da browser e app. +While AdGuard Browser Extension can block ads in browsers, [AdGuard standalone programs](/adguard-browser-extension/comparison-standalone) filter all the traffic on your device, including from browsers and apps. -Se decidi di installare sia l'estensione sia il programma autonomo sul tuo PC, potresti riscontrare alcuni problemi di compatibilità. Il problema è che in alcuni casi l'applicazione e l'estensione potrebbero interferire tra loro. Alcuni siti web non saranno più protetti dal programma desktop, ma solo dall'estensione, che offre meno opzioni. Inoltre, il filtraggio potrebbe non funzionare correttamente per alcuni siti web. Pertanto, sconsigliamo di utilizzare l'estensione insieme all'applicazione. +If you decide to install both the extension and the standalone program on your PC, you may encounter some compatibility issues. The problem is that in some cases the application and the extension may interfere with each other. Some websites will no longer be protected by the desktop program and will only be protected by the extension, which has fewer options. Also, filtering may work incorrectly for some websites. Therefore, we don't recommend using the extension together with the application. -Se hai installato la versione desktop di AdGuard sul tuo PC, è meglio utilizzare l'assistente AdGuard Browser Assistant invece dell'estensione. +If you have the desktop version of AdGuard installed on your PC, it is better to use AdGuard Browser Assistant instead of the extension. ## AdGuard Browser Assistant ![AdGuard Browser Assistant \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) -AdGuard Browser Assistant è un'estensione del browser che funziona e si presenta esattamente come l'Estensione del browser AdGuard, ma è molto più leggera e non interferisce con le app desktop. Puoi [leggere di più su Browser Assistant per Windows](/adguard-for-windows/browser-assistant) o [Mac](/adguard-for-mac/features/browser-assistant), oppure [scaricarlo dal nostro sito web](https://adguard.com/adguard-assistant/overview.html). +AdGuard Browser Assistant is a browser extension that works and feels just like AdGuard Browser Extension, but it's much lighter and doesn't interfere with the desktop apps. You can [read more about Browser Assistant for Windows](/adguard-for-windows/browser-assistant) or [Mac](/adguard-for-mac/features/browser-assistant), or [download it from our website](https://adguard.com/adguard-assistant/overview.html). -AdGuard Browser Assistant è disponibile su tutti i browser principali. +AdGuard Browser Assistant is available in all major browsers. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index da0dabc8c7d..291591b7ec4 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -11,29 +11,29 @@ Questo articolo riguarda l'Estensione di browser AdGuard, che protegge solo il t Il processo di blocco degli annunci è la funzionalità principale di qualsiasi app dedicata e l'Estensioni di browser AdGuard, non è un'eccezione. Il blocco degli annunci si basa su filtri: insiemi di regole scritte in un linguaggio speciale. Queste regole indicano quali elementi dovrebbero essere bloccati e quali no. AdGuard interpreta le regole e modifica le richieste web in base a esse. Di conseguenza, smetti di vedere annunci sulle pagine web. -![Filtri \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters.png) +![Filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters.png) Tutti i filtri sono raggruppati a seconda del loro ruolo. Ad esempio, esistono categorie per i filtri di blocco degli annunci, di protezione della privacy, correlati ai social, etc. Puoi abilitare singoli filtri o l'intero gruppo, in una volta sola. -![Filtri di blocco degli annunci \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters1.png) +![Ad blocking filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters1.png) ## Filtri personalizzati -Mentre le funzionalità degli altri gruppi di filtraggio sono più o meno autoesplicative, esiste un gruppo, detto _Personalizzati_, che potrebbe sollevare ulteriori dubbi. +Mentre le funzionalità degli altri gruppi di filtraggio sono più o meno prevedibili, esiste un gruppo, detto _Personalizzati_, che potrebbe sollevare ulteriori dubbi. -![Filtri personalizzati \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) +![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) In questa scheda, puoi aggiungere filtri non presenti nell'estensione di default. Esistono numerosi [filtri disponibili pubblicamente su Internet](https://filterlists.com). Inoltre, puoi creare e aggiungere i tuoi filtri. In effetti, puoi creare qualsiasi serie di filtri e personalizzare il blocco degli annunci come preferisci. Per aggiungere un filtro, basta cliccare _Aggiungi filtro personalizzato_, inserire l'URL o il percorso del file del filtro che desideri aggiungere e cliccare _Avanti_. -![Aggiungi un filtro personalizzato \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters1.png) +![Add a custom filter \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters1.png) ## Regole utente {#user-rules} _Le regole utente_ sono un altro strumento che ti aiuta a personalizzare il blocco degli annunci. -![Regole utente \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_user_rules.png) +![User rules \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_user_rules.png) Esistono diversi modi per aggiungere le nuove regole. La cosa più semplice è digitare una regola, ma richiede una certa conoscenza della [sintassi delle regole] (/general/ad-filtering/create-own-filters). @@ -51,6 +51,6 @@ La _lista consentita_ è utilizzata per escludere certi siti web dal filtraggio. Inoltre, la _lista consentita_ può essere invertita: puoi sbloccare gli annunci ovunque, tranne che sui siti web aggiunti a questo elenco. Per farlo, attiva l'opzione _Inverti lista consentita_. -! [Inverti allowlist \*border] (https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist1.png) +![Invert allowlist \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist1.png) Inoltre, puoi importare ed esportare le liste consentite esistenti. È utile, ad esempio, se desideri applicare le stesse regole d'autorizzazione, su ognuno dei tuoi browser. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 66e272003de..bf0c9e6e447 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -11,10 +11,10 @@ Questo articolo riguarda l'Estensione di browser AdGuard, che protegge solo il t La pagina principale dell'estensione è accessibile cliccando sull'icona dell'estensione, nella barra degli strumenti del tuo browser. -![Menu principale \*mobile\_border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_main.png) +![Main menu \*mobile\_border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_main.png) Sulla pagina principale, puoi nascondere qualsiasi elemento, su qualsiasi pagina, manualmente (sarà aggiunta una regola corrispondente alle _Regole utente_), aprire il _Registro di filtraggio_ per visualizzare al volo le informazioni complete sul traffico del tuo browser e le richieste di blocco, o visualizzare il rapporto di sicurezza di un sito web. Inoltre, puoi inviare un reclamo su qualsiasi sito web (ad esempio, se alcuni annunci sulla pagina non sono bloccati, i nostri ingegneri di filtraggio revisioneranno il rapporto e risolveranno il problema) e visualizzare le statistiche sulle regole di blocco applicate. -Tutte le richieste web effettuate dal browser sono registrate nel _Registro di filtraggio_, insieme a informazioni dettagliate su ogni richiesta. Il _Registro di filtraggio_ semplifica, ad esempio, il monitoraggio delle richieste bloccate dall'estensione di browser AdGuard. Inoltre, ti consente di bloccare qualsiasi richiesta o di aggiungere una richiesta bloccata in precedenza alla lista consentita, in due click. Inoltre, il _Registro di filtraggio_ ti offre numerose opzioni per ordinare le richieste web, il che può essere utile creando le tue regole di filtraggio. Puoi aprire il _Registro di filtraggio_ selezionando la voce corrispondente nel menu principale, o dalla pagina delle impostazioni (nella scheda _Impostazioni aggiuntive_). +Tutte le richieste web effettuate dal browser sono registrate nel _Registro di filtraggio_, insieme a informazioni dettagliate su ogni richiesta. Il _Registro di filtraggio_ semplifica, ad esempio, il monitoraggio delle richieste bloccate dall'estensione di browser AdGuard. Inoltre, ti consente di bloccare qualsiasi richiesta o di aggiungere una richiesta bloccata in precedenza alla lista consentita, in due click. Inoltre, il _Registro di filtraggio_ ti offre numerose opzioni per ordinare le richieste web, il che può essere utile creando le tue regole di filtraggio. Puoi aprire il _Registro di filtraggio_ selezionando la voce corrispondente nel menu principale, o dalla pagina delle impostazioni (nella scheda "Impostazioni aggiuntive"). Cliccando le icone in alto a destra sul menu principale dell'estensione, puoi aprire le impostazioni dell'estensione o interrompere la protezione. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index cf4184759ae..5935543cf89 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -15,17 +15,17 @@ Oltre ai grandi moduli chiave dell'estensione del browser AdGuard, ci sono molte Nella scheda _Generale_, puoi consentire la ricerca di annunci e [l'auto-promozione dei siti web](/general/ad-filtering/search-ads), abilitare l'attivazione automatica di filtri specifici per la lingua, indicare l'intervallo di aggiornamento dei filtri, etc. -! [Generale \*border] (https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) +![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Inoltre, qui puoi abilitare la [_Protezione da phishing e malware_](/general/browsing-security). -Puoi salvare la configurazione delle tue impostazioni cliccando il pulsante _Esporta impostazioni_. Le impostazioni saranno salvate come un file .json. Per importare la configurazione d'impostazioni precedentemente salvata, utilizza la funzionalità _Importa impostazioni_. Puoi anche utilizzarla per passare tra diversi profili di impostazioni, o persino per trasferire le configurazioni di impostazioni tra browser differenti. +Puoi salvare la configurazione delle tue impostazioni cliccando il pulsante _Esporta impostazioni_. Le impostazioni saranno salvate come un file .json. Per caricare la configurazione d'impostazioni precedentemente salvata, utilizza la funzionalità _Importa impostazioni_. Puoi anche utilizzarla per passare tra diversi profili di impostazioni, o persino per trasferire le configurazioni di impostazioni tra browser differenti. ## Impostazioni aggiuntive {#misc} La sezione delle _Impostazioni aggiuntive_ contiene una gamma di varie impostazioni, correlate al processo di blocco degli annunci e di utilizzabilità dell'applicazione. -![Impostazioni aggiuntive \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_additional_settings.png) +![Additional settings \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_additional_settings.png) Da questa scheda, puoi attivare i filtri ottimizzati, abilitare le notifiche sugli aggiornamenti dell'estensione, aprire il _Registro di filtraggio_ o cancellare le statistiche di annunci e tracciatori bloccati. @@ -33,6 +33,6 @@ Inoltre, puoi decidere di aiutarci con lo sviluppo dei filtri, inviandoci le sta ## Informazioni {#about} -Nella sezione _Informazioni_, puoi trovare le informazioni sulla versione corrente, collegamenti all'EULA e l'Informativa sulla Privacy e alla repository dell'estensione del Browser su GitHub. +Nella sezione _Informazioni_, puoi trovare le informazioni sulla versione corrente, collegamenti all'EULA e la Politica sulla Privacy e alla repository dell'estensione del Browser su GitHub. -![Informazioni \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) +![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md index d5026013769..f1e64a98dcb 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md @@ -11,7 +11,7 @@ Questo articolo riguarda l'Estensione di browser AdGuard, che protegge solo il t _La Modalità Invisibilità_ mira ad assicurare la protezione dei dati personali sensibili, da tracciatori e truffatori online. -![Modalità Invisibilità \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_stealth_mode.png) +![Stealth Mode \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_stealth_mode.png) In Modalità Invisibilità, puoi impedire a un sito web di visualizzare i tuoi quesiti di ricerca utilizzati per trovarlo su Internet, eliminare automaticamente i cookie di terze parti o del sito stesso, etc. A tutte queste caratteristiche è dedicato un [articolo separato](/general/stealth-mode). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md index aca5f488125..4ea799e035a 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md @@ -71,4 +71,4 @@ Nella finestra aperta, fai clic su *Aggiungi estensione* per installare l'estens ## Come installare l'estensione AdGuard per Safari -AdGuard per Safari non è un'estensione del browser nel senso comune. Puoi leggere di più a riguardo in un [articolo dedicato](/adguard-for-safari/features/general). Oppure, puoi [scaricare il file d'installazione](https://agrd.io/safari_release) direttamente da questa pagina. +AdGuard per Safari non è un'estensione del browser nel senso comune. You can read more about it in a [dedicated article](/adguard-for-safari/features/general). Oppure, puoi [scaricare il file d'installazione](https://agrd.io/safari_release) direttamente da questa pagina. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index 1500606159d..31de38d03bd 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Pagine protette dal browser -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md index b75ca5a7c1c..479eb4bac5f 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md @@ -53,11 +53,11 @@ sidebar_position: 1 :::note -AdGuard si impegna a proteggere la tua privacy. Seguiamo rigorosamente la nostra [Informativa sulla privacy](https://adguard.com/privacy/browser-extension.html) e non raccogliamo alcuna informazione privata sugli utenti. Prima di inviare i registri al team di supporto, esamina il file poiché potrebbe contenere informazioni aggiuntive che non desideri condividere. Se contiene tali informazioni personali, ti consigliamo di eliminarle prima. +AdGuard si impegna a proteggere la tua privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/browser-extension.html) and do not collect any private information about users. Prima di inviare i registri al team di supporto, esamina il file poiché potrebbe contenere informazioni aggiuntive che non desideri condividere. Se contiene tali informazioni personali, ti consigliamo di eliminarle prima. ::: -Ora che hai raccolto i registri, ti preghiamo di seguire questi passaggi per inviarli al nostro team di sviluppo: +Now that you have collected the logs, please follow these steps to submit them to our development team: -1. Segnala il bug su [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). -2. Invia il tuo archivio con i registri e l'orario di riproduzione a 'devteam@adguard.com' e aggiungi un collegamento al tuo ticket di GitHub. Puoi anche caricare l'archivio su Google Drive e aggiungere il collegamento a esso, invece di allegare il file. +1. Report the bug on [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). +2. Send your archive with logs and playback time to `devteam@adguard.com` and add a link to your GitHub issue. You can also upload the archive to Google Drive and add the link to it instead of attaching the file. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index e584e21c606..dedf1730d5a 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index aa36ef935aa..e9b7ab6ec63 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index fbdcdfd6b71..e7158995208 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index 3db3b503069..e204c77b6fd 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 079215356a6..15cb7c5b96f 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index a11d71fd6ef..8a73fb1b0fe 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Script utente -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index 595c1b87883..8a7054f314e 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Fatto! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 3573e6e31fb..7104c4c455d 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ Questo articolo riguarda AdGuard per Android, un blocco annunci multifunzionale ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 16d4b19dac1..5ecc5731591 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index 170397660c6..e28ccf5826f 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index 629a6efbd6c..65344c9b750 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index a848f184800..f325a99da69 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. +In questo articolo, ti guideremo attraverso il processo di raccolta dei registri di debug, un passaggio essenziale per la risoluzione dei problemi complessi che potrebbero potenzialmente sorgere. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. :::note @@ -23,9 +23,9 @@ AdGuard si impegna a proteggere la tua privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 9a2f0dff6a3..1c4684bc975 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. Utilizza un proxy DNS locale per cercare la configurazione ECH per il dominio. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. Utilizza un proxy DNS locale per cercare la configurazione ECH per il dominio. Se trovato, il pacchetto ClientHello sarà crittografato. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index aa66d8df4bf..1859f013c41 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index 79696704cec..8b8ba466eac 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index c770453a4bf..1b569165946 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index aaab2dd86c5..00000000000 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -Questo articolo riguarda AdGuard per iOS, un blocco annunci multifunzionale che protegge il tuo dispositivo a livello di sistema. Per vedere come funziona, [scarica l'app di AdGuard](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 72a22ebe656..594539ce4b8 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -13,15 +13,15 @@ Questo articolo tratta AdGuard per iOS, un blocco annunci multifunzionale che pr ### iPhone -Richiede iOS 13 o successive. +Requires iOS 13 or later. ### iPad -Richiede iPadOS 13 o successive. +Requires iPadOS 13 or later. ### iPod touch -Richiede iOS 13 o successive. +Requires iOS 13 or later. ## Installazione di AdGuard per iOS @@ -29,7 +29,7 @@ AdGuard per iOS è un'app presente sull'App Store. Per installarla sul tuo dispo ![Sulla schermata principale dell'App Store, tocca Cerca *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Digita *adguard* nella barra di ricerca e tocca sulla stringa *AdGuard* che apparirà tra i risultati di ricerca. +Digita *adguard* nella barra di ricerca e tocca sulla stringa *adguard* che apparirà tra i risultati di ricerca. ![Digita "AdGuard" nella barra di ricerca *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro è una versione a pagamento di AdGuard per iOS, che offre una serie ![Sulla schermata principale dell'App Store, tocca Cerca *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Digita *adguard* nella barra di ricerca e tocca sulla stringa *AdGuard pro — adblock* che apparirà tra i risultati di ricerca. +Digita *adguard* nella barra di ricerca e tocca sulla stringa *adguard pro - adblock* che apparirà tra i risultati di ricerca. ![Digita "AdGuard" nella barra di ricerca *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -Sulla pagina aperta dell'App Store tocca il pulsante con il costo della licenza, sotto la stringa *AdGuard Pro — adblock*, quindi su *ACQUISTA*. Ti potrebbe essere richiesto di inserire accesso e password del tuo Apple ID. Digitali e attendi il completamento dell'installazione. +Sulla pagina aperta dell'App Store tocca il pulsante con il costo della licenza, sotto la stringa *AdGuard Pro - blocco annunci*, quindi su *ACQUISTA*. Ti potrebbe essere richiesto di inserire accesso e password del tuo Apple ID. Digitali e attendi il completamento dell'installazione. ![Tocca OTTIENI sotto all'app di AdGuard *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index 4552f4bd522..9fd75a0515a 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ Questo articolo tratta AdGuard per iOS, un blocco annunci multifunzionale che pr 1. Scegli un video e tocca su *Condividi*. 1. Tocca su *Altre*, quindi seleziona *Blocca annunci di YouTube (AdGuard)*. -Ora il video si apre nel lettore senza pubblicità di AdGuard. +AdGuard aprirà il proprio lettore video senza pubblicità. ## Come bloccare gli annunci su YouTube su Safari @@ -31,4 +31,4 @@ Assicurati di aver dato ad AdGuard l'accesso a tutti i siti web. Puoi verificarl 1. Scegli un video e tocca su *Condividi*. 1. Tocca su *Blocca annunci di YouTube (AdGuard)*. -Ora il video si apre nel lettore senza pubblicità di AdGuard. +AdGuard aprirà il proprio lettore video senza pubblicità. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index df170d06d9d..3f8bb2d1404 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ Per andare alle *Impostazioni di basso livello*, tocca l'icona dell'ingranaggio Esistono due modalità tunnel principali: *Split* e *Full*. La modalità *Split-Tunnel* fornisce la compatibilità di AdGuard con le cosiddette app "VPN Personali". In modalità *Full-Tunnel*, nessun'altra VPN può operare simultaneamente con AdGuard. -Esiste una caratteristica specifica della modalità *Split-Tunnel*: in caso di scarse prestazioni del proxy DNS, ad esempio se la risposta dal server DNS di AdGuard non viene restituita in tempo, iOS reindirizzerà il traffico attraverso il server DNS specificato nelle impostazioni iOS. Nessun annuncio sarà bloccato e il traffico DNS non sarà crittografato. +Esiste una funzionalità specifica della modalità *Split-Tunnel*: se il proxy DNS non opera correttamente, ad esempio, se la risposta dal server DNS di AdGuard non è stata restituita in tempo, iOS la "punirà" e reindirizzerà il traffico tramite il server DNS specificato nelle impostazioni di iOS. Nessun annuncio sarà bloccato e il traffico DNS non sarà crittografato. -In modalità *Full-Tunnel*, soltanto il server DNS specificato sulle impostazioni di AdGuard è utilizzato. Se non risponde, Internet semplicemente non funzionerà. L'attivazione della modalità *Full-Tunnel* potrebbe avere un impatto negativo sulle prestazioni di alcuni programmi (ad esempio FaceTime) e causare problemi di aggiornamento delle app. +In modalità *Full-Tunnel*, soltanto il server DNS specificato sulle impostazioni di AdGuard è utilizzato. Se non risponde, Internet semplicemente non funzionerà. La modalità *Full-Tunnel* abilitata potrebbe causare prestazioni errate di certi programmi (ad esempio, Facetime) e condurre a problemi con gli aggiornamenti dell'app. Di default, AdGuard utilizza la modalità *Split-Tunnel* come l'opzione più stabile. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md index 8c6906f1789..28b314c5387 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md @@ -1,5 +1,5 @@ --- -title: 'Installazione/Disinstallazione' +title: 'Install/Uninstall' sidebar_position: 2 --- @@ -72,15 +72,15 @@ Go to the Applications section. Find AdGuard there, right-click it and choose ** **Use this instruction only if you know what you are doing or if our support service specifically recommended you the 'advanced uninstall'. Also, do all the steps from the "regular uninstall" first.** 1. After that, delete following AdGuard files: - - /Library/Application Support/AdGuard Software/com.adguard.mac.adguard (cartella) + - /Library/Application Support/AdGuard Software/com.adguard.mac.adguard (folder) - ~/Library/Preferences/com.adguard.mac.adguard.plist (file) - - ~/Library/Group\ Containers/TC3Q7MAJXF.com.adguard.mac (cartella) + - ~/Library/Group\ Containers/TC3Q7MAJXF.com.adguard.mac (folder) - /Library/LaunchDaemons/com.adguard.mac.adguard.adguard-pac.daemon.plist (file) - /Library/LaunchDaemons/com.adguard.mac.adguard.adguard-tun-helper.daemon.plist (file) - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-pac.daemon.log (file) - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-tun-helper.daemon.log (file) - Per farlo, apri l'app del Terminale, quindi, inserisci ed esegui i seguenti comandi: + To do so, open the Terminal app, then enter and execute the following commands: ```bash sudo rm -R "/Library/Application Support/AdGuard Software/com.adguard.mac.adguard" @@ -94,13 +94,13 @@ Go to the Applications section. Find AdGuard there, right-click it and choose ** sudo rm /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-tun-helper.daemon.log ``` -1. Avvia l'app **Monitoraggio Attività**. -1. Utilizzando lo strumento di ricerca, trova il processo **cfprefsd**. +1. Run the **Activity Monitor** app. +1. Using search tool, find the process **cfprefsd**. - ![Esegui Monitoraggio Attività](https://cdn.adtidy.org/content/kb/ad_blocker/mac/22.jpg) + ![Run Activity Monitor](https://cdn.adtidy.org/content/kb/ad_blocker/mac/22.jpg) -1. Arresta il processo in esecuzione sotto l'utente (non quello eseguito sotto root). Per farlo, clicca sul processo, quindi clicca sulla X in alto a sinistra. Conferma l'azione nella finestra. +1. Stop the process which is being run under the user (not the one run under root). To do so, click the process and then click X on the upper left. Confirm the action in the dialogue window. - ![Conferma](https://cdn.adtidy.org/content/kb/ad_blocker/mac/33.jpg) + ![Confirm](https://cdn.adtidy.org/content/kb/ad_blocker/mac/33.jpg) -AdGuard è ora rimosso dal tuo computer. +AdGuard is removed from your computer now. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 64f5d6f9b9b..1e9f306120b 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -21,7 +21,7 @@ Per trovare le *Impostazioni Avanzate*, apri AdGuard, clicca sull'icona dell'ing ## Impostazioni Avanzate -### Impostazioni di rete +### Network settings #### `network.extension.exclude.domains` @@ -71,7 +71,7 @@ Tempo, in secondi, prima dell'invio di un'altra richiesta keepalive verso un pee #### `network.https.ech.enabled` -Utilizza un proxy DNS locale per cercare le configurazioni nella lista di configurazioni ECH. Se trovata, cripta Client Hello. +Utilizza un proxy DNS locale per cercare le configurazioni nella lista di configurazioni ECH. Se trovata, cripta ClientHellos. #### `network.https.enforce.certificate.transparency` @@ -89,7 +89,7 @@ Impostando `true`, abiliti il filtraggio della rete locale. Impostando `true`, abiliti il filtraggio LoopBack. -### Impostazioni DNS +### DNS settings #### `dns.proxy.bootstrap.ips` diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 9229e683b6a..2603b56228f 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ Se utilizzi Flutter insieme ad AdGuard in modalità "Network Extension" (o quals #### App VPN con API ereditaria -Sebbene AdGuard sia visualizzato come una VPN nelle impostazioni di sistema, non dovrebbe causare alcun conflitto, lavorando insieme ad altre app basate sulla VPN. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Sebbene AdGuard sia visualizzato come una VPN nelle impostazioni di sistema, non dovrebbe causare alcun conflitto, lavorando insieme ad altre app basate sulla VPN. Tuttavia, se stai utilizzando un'app basata sulla VPN scaricata dall'esterno dell'App Store, è possibile che utilizzi un'API della VPN poco recente, e che tu debba escluderla dal filtraggio: 1. Apri il menu di AdGuard. 1. Seleziona *Preferenze...*. @@ -79,9 +79,9 @@ Questi problemi sono stati oramai risolti da Apple, ma possono esser riscontrati ### Compatibilità con Little Snitch 5 -Al momento, la modalità Estensione di Rete di AdGuard non è compatibile con [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. Questo problema è causato direttamente da un bug di Big Sur, e abbiamo già informato Apple a riguardo. Questo ci lascia credere che questo problema sarà risolto in uno dei prossimi aggiornamenti. +Al momento, la modalità Estensione di Rete di AdGuard non è compatibile con [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). Quando entrambe sono in esecuzione, è possibile riscontrare problemi con il comportamento di varie app, anche se non sono filtrate da AdGuard. Questo problema è causato direttamente da un bug di Big Sur, e abbiamo già informato Apple a riguardo. Questo ci lascia credere che questo problema sarà risolto in uno dei prossimi aggiornamenti. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. Consigliamo di passare alla modalità di filtraggio [**Proxy Automatico**](#automatic-proxy), eseguendo AdGuard insieme a Little Snitch su Big Sur, almeno fino alla risoluzione del bug da parte di Apple. +Va detto che questo problema non è risolvibile disabilitando il monitoraggio delle connessioni su Little Snitch, perché quest'azione non scarica l'estensione di Little Snitch dal sistema. Consigliamo di passare alla modalità di filtraggio [**Proxy Automatico**](#automatic-proxy), eseguendo AdGuard insieme a Little Snitch su Big Sur, almeno fino alla risoluzione del bug da parte di Apple. ### Compatibilità con i proxy locali @@ -121,7 +121,7 @@ Prima di tutto, necessiti di un lato server funzionante per il tuo proxy. Molto :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +Puoi trovare ulteriori informazioni su come iniziare sul [sito web di Shadowsocks](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index 21310e7cb6e..ccd451a73f3 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ Questo articolo riguarda AdGuard per Mac, un blocco annunci multifunzionale che ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". Questo è un nuovo meccanismo di sicurezza apparso in High Sierra che ti richiede di consentire esplicitamente l'installazione di un'estensione di sistema di terze parti. Per completare l'installazione di AdGuard devi consentire manualmente il caricamento dell'estensione in *Preferenze di Sistema* → *Sicurezza & Privacy* → *Generale*. +Durante l'installazione di AdGuard su macOS High Sierra (o versioni successive), potresti vedere il messaggio: "Estensione di Sistema Bloccata". Questo è un nuovo meccanismo di sicurezza apparso in High Sierra che ti richiede di consentire esplicitamente l'installazione di un'estensione di sistema di terze parti. Per completare l'installazione di AdGuard devi consentire manualmente il caricamento dell'estensione in *Preferenze di Sistema* → *Sicurezza & Privacy* → *Generale*. ![Consenti l'installazione dell'estensione nelle impostazioni](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 5b7d9bbc152..95468b691bf 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ Di conseguenza, AdGuard non può funzionare con il relay privato iCloud e con le 1. Il relay privato iCloud si applica alle connessioni a livello della libreria, prima che raggiungano il livello di socket, dove opera AdGuard. 2. Il relay privato iCloud utilizza QUIC, che AdGuard non può filtrare, poiché il filtraggio HTTP/3 non è ancora disponibile. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Di conseguenza, AdGuard blocca QUIC, incluso il traffico di relay privato iCloud; altrimenti, il blocco degli annunci è impossibile. 4. Quando utilizzi il relay privato iCloud e, in AdGuard, passi alla modalità "tunnel diviso", non puoi aprire i siti web su Safari. 5. Per risolvere questo problema per Monterey, applichiamo la regola "percorso predefinito". Quando Private Relay vede questa regola, si disabilita automaticamente. Quindi, AdGuard opera senza problemi su Monterey, ma il relay privato iCloud viene disabilitato. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 1c13c862fbb..90229c65492 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant è l'Assistente legacy che puoi utilizzare se il [nuovo Assist Questa è un'estensione personalizzata progettata per contrastare la tecnica di reinserimento degli annunci bloccati: la cosiddetta elusione dei blocchi di annunci o reiniezione degli annunci. Entrambi sono metodi anti blocco degli annunci avanzati, che continuano a crescere in popolarità tra gli inserzionisti. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra è, essenzialmente, un microprogramma che modifica il funzionamento delle pagine, così che diventi più difficile, per i siti, l'utilizzo dei suddetti metodi per aggirare i bloccatori. **AdGuard Popup Blocker** -Quest'estensione impedisce l'apertura delle finestre popup quando visualizzi le pagine web. Alcuni pop-up sono considerati utili: possono contenere impostazioni per l'amministrazione del sito o informazioni di riferimento aggiuntive mostrate facendo clic su un collegamento. Per questo, puoi disattivare il Blocco, se necessario. Quest'estensione non funziona neanche sui siti web aggiunti all'elenco di eccezioni di AdGuard. È disattivata di default, ma puoi attivarla nelle impostazioni dell'applicazione. You will find more detailed information about this extension in our Knowledge Base. +Quest'estensione impedisce l'apertura delle finestre popup quando visualizzi le pagine web. Alcuni pop-up sono considerati utili: possono contenere impostazioni per l'amministrazione del sito o informazioni di riferimento aggiuntive mostrate facendo clic su un collegamento. Per questo, puoi disattivare il Blocco, se necessario. Quest'estensione non funziona neanche sui siti web aggiunti all'elenco di eccezioni di AdGuard. È disattivata di default, ma puoi attivarla nelle impostazioni dell'applicazione. Troverai delle informazioni più dettagliate su quest'estensione nella nostra Base di conoscenza. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust ti consente di visualizzare la reputazione di ogni sito web, second ### Rete -Il penultimo modulo è dedicato al filtraggio di rete e, qui, troverai le opzioni aggiuntive correlate alla rete. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Queste sono importanti precauzioni aggiuntive, per meglio filtrare il tuo spazio web. Gran parte dei siti, a oggi, utilizzano HTTPS, il che si applica anche agli annunci. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +Il penultimo modulo è dedicato al filtraggio di rete e, qui, troverai le opzioni aggiuntive correlate alla rete. Due di esse sono abilitate di default: _Abilita il filtraggio del traffico_ e _Filtra protocollo HTTPS_. Queste sono importanti precauzioni aggiuntive, per meglio filtrare il tuo spazio web. Gran parte dei siti, a oggi, utilizzano HTTPS, il che si applica anche agli annunci. Da molti siti, come youtube.com, facebook.com e twitter.com, è impossibile rimuovere gli annunci senza il filtraggio HTTPS. Quindi, mantieni la funzionalità _Filtra protocollo HTTPS_ abiltata, a meno che tu non abbia una valida ragione per non farlo. ![Impostazioni di Rete \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 6c507dd8877..c9c5c938d1e 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ _Impostazioni_ è la sezione che richiede maggiore attenzione. Qui, puoi configu ### Impostazioni generali -Qui, puoi impostare la lingua e il tema (Scuro o Chiaro), abilitare l'avvio di AdGuard all'avvio del sistema e silenziare gli aggiornamenti automatici, scegliere il canale d'aggiornamento e filtrare l'intervallo di controllo per gli aggiornamenti. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +Qui, puoi impostare la lingua e il tema (Scuro o Chiaro), abilitare l'avvio di AdGuard all'avvio del sistema e silenziare gli aggiornamenti automatici, scegliere il canale d'aggiornamento e filtrare l'intervallo di controllo per gli aggiornamenti. Inoltre, Impostazioni è il posto in cui andare se AdGuard per Windows non funziona correttamente e se il team di supporto ti ha richiesto di [raccogliere i _Registri di debug_](/adguard-for-windows/solving-problems/adguard-logs.md). ![Impostazioni Avanzate \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ Esistono numerosi siti web a cui dovrebbe essere limitato l'accesso da un PC uti Il modulo controlla i contenuti delle pagine web aperte nel browser e filtra quelle con contenuti indesiderabili per i bambini: immagini e testi per adulti, linguaggio volgare, violenza, sostanze stupefacenti, etc. Le impostazioni del Controllo Genitori sono protette da password, così che i bambini non possano aggirare le limitazioni. Questo modulo non blocca soltanto le indicazioni ai siti indesiderati, ma può anche eliminare i collegamenti inappropriati per i bambini, dai risultati di ricerca. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Inoltre, puoi anche spuntare la casella _Blocca download file eseguibili_ per impedire ai tuoi figli di scaricare e installare software sul computer. Esistono ancora altre due opzioni nel modulo _Controllo Genitori_: puoi selezionare un utente di Windows specifico da proteggere con il _Controllo Genitori_ e impostare una password per proteggere le impostazioni di AdGuard dalla modifica. +Nel modulo Controllo Genitori, puoi abilitare la _Ricerca sicura_ e gestire l'_elenco di blocco_ e l'_elenco consentiti_ per personalizzare il funzionamento d quest'opzione. Inoltre, puoi anche spuntare la casella _Blocca download file eseguibili_ per impedire ai tuoi figli di scaricare e installare software sul computer. Esistono ancora altre due opzioni nel modulo _Controllo Genitori_: puoi selezionare un utente di Windows specifico da proteggere con il _Controllo Genitori_ e impostare una password per proteggere le impostazioni di AdGuard dalla modifica. ![Controllo Genitori \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cdb715bdb0c..d0d4ad9c13c 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ Questo articolo riguarda AdGuard per Windows, un blocco annunci multifunzionale To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Vai al [sito web di AdGuard](http://adguard.com) nella barra degli indirizzi e clicca su *Download* [nella pagina aperta](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 999080cf7ef..876a6154d27 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ I dati e/o i file forniti negli registri sono trattati in conformità con [l'Inf ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard si impegna a proteggere la tua privacy. Rispettiamo rigorosamente la nos ### Registri di debug {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard si impegna a proteggere la tua privacy. Rispettiamo rigorosamente la nos We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Esporta i registri *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 812c5d287d1..f8612da0d4b 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ Questo articolo contiene alcuni degli errori più comuni che puoi riscontrare du ### Errore 5: Accesso Negato {#error-5} -This error message appears when required permissions haven't been granted. Potrebbero esistere diversi motivi per cui il programma d'installazione di AdGuard non ha le autorizzazioni richieste per terminare correttamente il processo d'installazione. Puoi provare i seguenti passaggi: +Questo errore si verifica se c'è qualcosa che non va con le autorizzazioni. Potrebbero esistere diversi motivi per cui il programma d'installazione di AdGuard non ha le autorizzazioni richieste per terminare correttamente il processo d'installazione. Puoi provare i seguenti passaggi: -- Temporarily disable your antivirus. Alcuni di essi potrebbero interferire con l'installazione, a seconda della gravità delle loro impostazioni. +- Disabilita temporaneamente i tuoi antivirus. Alcuni di essi potrebbero interferire con l'installazione, a seconda della gravità delle loro impostazioni. - Scegli una cartella d'installazione differente. È possibile che la cartella d'installazione corrente preveda delle limitazioni d'accesso. Assicurati, inoltre, di non selezionare un'unità esterna, un'unità virtuale, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. Potre ### Errore 112: Il disco è pieno, Errore 1632: Cartella temporanea piena o inaccessibile {#error-112} -Esistono due errori differenti con soluzioni molto simili. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. Esistono diverse cose che puoi tentare per risolvere questo problema: +Esistono due errori differenti con soluzioni molto simili. Come suggerito dai loro nomi, il programma d'installazione di AdGuard non ha trovato abbastanza spazio per completare l'installazione. Esistono diverse cose che puoi tentare per risolvere questo problema: - Disinstalla alcuni programmi o elimina i file non necessari, dall'unità in cui stavi tentando d'installare AdGuard. -- Scarica, installa ed esegui [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), un software gratuito di Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Scarica, installa ed esegui [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), un software gratuito di Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Riavvia il tuo computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index f16e743129d..aa97acddb33 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ Questo articolo riguarda AdGuard per Windows, un blocco annunci multifunzionale AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 7cc67184f1c..c2efae168a9 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index aba3c7778c8..b249bee6ca4 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ I dati e/o i file forniti negli registri di sistema sono trattati in conformità If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 367243340e2..b11b4019e0b 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. Utilizza un proxy DNS locale per cercare la configurazione ECH per il dominio. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. Utilizza un proxy DNS locale per cercare la configurazione ECH per il dominio. Se trovato, il pacchetto ClientHello sarà crittografato. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Abilita quest'opzione per far aprire la finestra principale di AdGuard all'avvio del sistema. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Abilita quest'opzione per far aprire la finestra principale di AdGuard all'avvio del sistema. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ Se non desideri che AdGuard filtri determinate sottoreti, abilita questa funzion ### Abilita scrittura HAR -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valori validi: 1–1500. Se viene specificata una dimensione non valida, verrà utilizzato il valore selezionato dal sistema. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 22f71bc5206..49aaefc0183 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ I dati e/o i file forniti negli registri di sistema sono trattati in conformità ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 055ad24255a..7ddc1f5a5d1 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ Questo articolo riguarda AdGuard per Windows, un blocco annunci multifunzionale ::: -Per filtrare il traffico di rete, AdGuard utilizza un driver di rete. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +Per filtrare il traffico di rete, AdGuard utilizza un driver di rete. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. Per farlo: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/it/docusaurus-plugin-content-docs/current/general/account/features.md index db97e231263..1afe8fb379b 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ La sezione dello Storico degli acquisti mostra tutte le licenze mai acquistate u ## Contattare il supporto -La scheda del Supporto contiene i link utili per aiutarti a risolvere problemi e trovare risposte alle tue domande sui prodotti di AdGuard. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +La scheda del Supporto contiene i link utili per aiutarti a risolvere problemi e trovare risposte alle tue domande sui prodotti di AdGuard. Sono divisi in sei sezioni: FAQ, Invia una segnalazione di bug/richiesta di funzionalità, Segnala blocco errato, Contatta il supporto, Base di conoscenza e Discuti. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index b65758e1314..76dc4ffce66 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ Questo articolo riguarda i filtri che creiamo per l'utilizzo in AdGuard e altri - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index d25ecf7208d..4ae0fbcefef 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:----------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:----------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:----------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:----------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:----------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:----------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:----------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:----------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:----------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:----------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:----------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard per iOS][ios-app] | [AdGuard per Safari][ext-saf] | [Blocco contenuti AdGuard][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:----------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,32 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard per Safari" -[ext-saf]: #what-product "AdGuard for Safari" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 6f9743321a1..1ab9d483a49 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -36,19 +36,17 @@ Gli **anti-adblock** sono tecnologie utilizzate dai siti web o dalle applicazion ### Filtri -I filtri di blocco degli annunci di AdGuard includono: +I filtri di blocco degli annunci AdGuard includono: - Filtro di base di AdGuard - Filtro Inserzioni Mobili di AdGuard - Filtri regionali divisi per principio linguistico: cinese, olandese, francese, tedesco, giapponese, russo, spagnolo/portoghese, turco e ucraino -- AdGuard Quick Fixes filter ### Lo scopo di questi filtri - Il **filtro di base** è progettato per bloccare le inserzioni sui siti web in lingua inglese, nonché quelle per le quali non è presente alcun filtro separato. Inoltre, contiene le regole di filtraggio generali che si applicano a tutti i siti, indipendentemente dalla lingua - Il **filtro delle Inserzioni Mobili** blocca le inserzioni sulle versioni mobili dei siti web, e sulle app mobili. Non esiste alcuna segmentazione basata sulla lingua - I **filtri regionali** seguono la stessa politica del **filtro di base**, ma si limitano ai siti web in certe lingue -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. L'obiettivo dei filtri di blocco delle inserzioni è bloccare ogni tipo di inserzione sui siti web, le applicazioni, e certi dispositivi capaci di caricare inserzioni da Internet: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index b4272e780f8..3e796020aab 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/it/docusaurus-plugin-content-docs/current/general/browsing-security.md index e6c9027cd3d..443b23cf96b 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Cadere vittima di phishing e malware rimane un problema comune. Per migliorare la sicurezza digitale, abbiamo incorporato filtri speciali nei prodotti AdGuard per proteggerti da siti web dannosi e quelli di phishing. Ad oggi, abbiamo classificato oltre 15 milioni di siti e creato un database di 1,5 milioni di siti Web noti per phishing e malware. Utilizzando questo database, AdGuard controlla i siti web visitati per proteggerti dalle minacce online. -:::note +::: note Non raccogliamo né utilizziamo alcuna informazione sui siti web visitati. ::: -## How does AdGuard check websites? +## Come fa AdGuard a controllare i siti web?​ Ogni volta che visiti un sito web, il tuo client locale scambia informazioni con il nostro server di backend, nella forma di hash e prefissi di hash. A seconda di questo scambio, il client locale determina se il sito web è elencato nel database dei siti web potenzialmente pericolosi, oppure no. Esiste una differenza nell'ambito di questo controllo per app ed estensioni. @@ -61,11 +61,11 @@ AdGuard mantiene un ampio database di siti web di phishing e malware e viene agg Analizziamo automaticamente i reclami relativi ai siti sospetti e dedichiamo molto tempo a mantenere aggiornato il database, eliminando i falsi positivi e implementando meccanismi per prevenirli in futuro. -### Want to help? +### Vuoi aiutare?​ Ogni aiuto è ben accetto! Se incontri un sito web di phishing o malware, segnalalo a . -### False-positive responses +### Falsi positivi​ Occasionalmente, alcuni siti web non dannosi vengono aggiunti ai filtri di AdGuard. Facciamo del nostro meglio per ridurre la percentuale di falsi positivi, ma si verificano comunque. Se riscontri questo comportamento da AdGuard, segnala il falso positivo al nostro supporto tecnico all'indirizzo . diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/it/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 73264d390e4..7636a09c485 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Gran parte dei siti, a oggi, utilizzano HTTPS, il che si applica anche agli annunci. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Gran parte dei siti, a oggi, utilizzano HTTPS, il che si applica anche agli annunci. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/it/docusaurus-plugin-content-docs/current/general/license/what-is.md index 085f6e4c353..a1494316546 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: Cos'è una licenza di AdGuard? sidebar_position: 1 --- @@ -12,7 +12,7 @@ Nella pagina [di acquisto](https://adguard.com/license.html)è possibile visuali - **Abbonamenti di 1 anno**: queste licenze si rinnovano automaticamente ogni anno o possono essere estese manualmente - Personale — fino a 3 dispositivi - Famiglia — fino a 9 dispositivi -- **Lifetime** — these licenses are perpetual +- **A vita** — queste licenze non sono limitate nel tempo - Personale — fino a 3 dispositivi - Famiglia — fino a 9 dispositivi diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/it/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 6c164885f40..8ed3520baaa 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Abilitare quest'opzione impedirà al browser di inviare dati GPS utilizzabili pe ### Blocca Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Attivando quest'impostazione, AdGuard bloccherà l'abilità dei browser di rilevare componenti (quali plugin e oggetti ActiveXObject), che consentano a Flash di mostrare contenuti. Ciò significa effettivamente che i browser non saranno in grado di supportare Flash. +Il plugin Flash Player è diventato sempre più vulnerabile alle minacce online, quali virus e hacker; potrebbe inoltre influenzare significativamente i tempi di caricamento dei siti web. Attivando quest'impostazione, AdGuard bloccherà l'abilità dei browser di rilevare componenti (quali plugin e oggetti ActiveXObject), che consentano a Flash di mostrare contenuti. Ciò significa effettivamente che i browser non saranno in grado di supportare Flash. ### Blocca Java {#java} @@ -95,7 +95,7 @@ Inoltre, puoi impostare un valore arbitrario per il Referente, inserendolo nel c Tieni presente che per poter filtrare il traffico, le applicazioni AdGuard "intercettano" le richieste dal browser al server. Le richieste effettuate agli server di annunci, tracciamento e di phishing possono essere modificate prima dell'invio al server o bloccate completamente. Lo stesso valore per l'opzione *Nascondi Referente dalle terze parti*: AdGuard intercetta le richieste HTTP(S), in particolare per rimuovere o modificare l'intestazione del Referente, se quest'opzione è abilitata. Tuttavia, ciò accade solo dopo che queste richieste "lasciano" il browser. Ciò significa che se monitori il Referente nel browser (ad esempio, con l'aiuto degli Strumenti per Sviluppatori di Chrome), vedrai il Referente originale, poiché la richiesta non ha ancora raggiunto AdGuard. Puoi utilizzare software come [Fiddler](https://www.telerik.com/fiddler) per assicurarti che il Referente sia alterato correttamente. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. Altererà il Referente in quel momento, quindi, gli Strumenti per Sviluppatori mostreranno il Referente desiderato per le tue richieste. +Al contrario, a causa della natura stessa di tutte le estensioni del browser, l'Estensione di browser AdGuard funziona "all'interno" del browser. Altererà il Referente in quel momento, quindi, gli Strumenti per Sviluppatori mostreranno il Referente desiderato per le tue richieste. ### Nascondi il tuo User-Agent {#useragent} @@ -120,9 +120,3 @@ L'Ispezione Approfondita del Pacchetto è un sistema di analisi profonda e filtr AdGuard può modificare i dati del pacchetto in uscita, così che il client non rientri nei criteri di blocco IPP. Ciò significa che, abilitando quest'opzione, gli utenti possono accedere ai contenuti che desiderano. Non tutti i sistemi IPP sono aggirabili al momento, ma lavoriamo costantemente per migliorare questo aspetto. La funzionalità "Protezione da IPP" è già implementata su AdGuard per Windows, AdGuard per Mac e AdGuard per Android. - -:::attenzione - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/it/docusaurus-plugin-content-docs/current/general/userscripts.md index 9564b39902d..069103c4884 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. Essi, modificano o estendono la funzionalità di uno o più siti web. Molti utenti di AdGuard potrebbero già essere a conoscenza di certi userscript, come AdGuard Assistant, Popup Blocker e AdGuard Extra. +Gli userscript (li chiamiamo anche "estensioni") sono, di fatto, mini-programmi scritti in JavaScript. Essi, modificano o estendono la funzionalità di uno o più siti web. Molti utenti di AdGuard potrebbero già essere a conoscenza di certi userscript, come AdGuard Assistant, Popup Blocker e AdGuard Extra. :::note App supportate @@ -134,7 +134,7 @@ Ecco il [link per inviare la mail](mailto:devteam@adguard.com?Subject=Userscript ##### Proprietà non supportate -These properties will be simply ignored by AdGuard. +Queste proprietà saranno semplicemente ignorate da AdGuard. ```text @unwrap diff --git a/i18n/it/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/it/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 05573fa1958..78a47b41612 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: Come raccogliere un file HAR sidebar_position: 1 --- diff --git a/i18n/it/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/it/docusaurus-plugin-content-docs/current/guides/report-bugs.md index cb2af8094b1..d96a0ce01ab 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Verifica se il bug è già stato segnalato. Consigliamo di fare attenzione sia a ### Come descrivere un problema -Prova a fornire quanti più dettagli possibile: ci faciliteranno nel riprodurre il bug e scoprire come risolverlo. Here’s what we expect a bug report to include: +Prova a fornire quanti più dettagli possibile: ci faciliteranno nel riprodurre il bug e scoprire come risolverlo. Ecco cosa vorremmo vedere in una segnalazione di bug: - La versione della tua app - La versione del tuo OS @@ -28,7 +28,7 @@ Prova a fornire quanti più dettagli possibile: ci faciliteranno nel riprodurre ### Come raccogliere i registri -Read about collecting logs in dedicated articles for each platform. +Leggi sulla raccolta dei registri negli articoli dedicati per ogni piattaforma. ## Come votare le segnalazioni di bug o le richieste di funzionalità diff --git a/i18n/it/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/it/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index 00dc4dc7fd1..3567aa326a2 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ Su alcuni portatili, devi tenere premuti *Fn* e *PrtScn*. Windows cattura l'intera schermata e la copia negli appunti. -To take a screenshot of an active window, use the following shortcut keys: +Per scattare uno screenshot di una finestra attiva, utilizza la seguente scorciatoia: - **Tieni premuto *Alt* e *PrtScn* (o *Fn + Alt + PrtScn* su alcuni portatili)** -To take a screenshot of a specific area, use the following shortcut keys: +Per scattare lo screenshot di un'area specifica, utilizza la seguente scorciatoia: - ***Press ***Win + Shift + S****** -Dopo aver scattato uno screenshot, sarà salvato negli appunti. Nella maggior parte dei casi, potrai incollarlo in un documento che stai modificando utilizzando la scorciatoia *Ctrl + V*. Altrimenti, se necessiti di salvare lo screenshot in un file, dovresti aprire il programma standard **Paint** (o qualsiasi altra app che permetta di lavorare con le immagini). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +Dopo aver scattato uno screenshot, sarà salvato negli appunti. Nella maggior parte dei casi, potrai incollarlo in un documento che stai modificando utilizzando la scorciatoia *Ctrl + V*. Altrimenti, se necessiti di salvare lo screenshot in un file, dovresti aprire il programma standard **Paint** (o qualsiasi altra app che permetta di lavorare con le immagini). Incolla il tuo screenshot utilizzando la stessa scorciatoia, o utilizzando il tasto Incolla (solitamente, nell'angolo superiore sinistro della schermata), quindi salvalo. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. Appena premerai questi tasti, lo screenshot sarà automaticamente salvato come un file nella cartella *Immagini* → *Screenshot*. +Windows 8 e 10 ti consentono di scattare uno screenshot molto rapidamente, con la scorciatoia *Win + PrtScn*. Appena premerai questi tasti, lo screenshot sarà automaticamente salvato come un file nella cartella *Immagini* → *Screenshot*. Inoltre, esiste un programma dedicato per scattare screenshot, chiamato *Strumento di Cattura*, che puoi trovare nel menu Start, tra i programmi standard del tuo computer. Strumento di Cattura ti permette di catturare qualsiasi area del tuo desktop o l'intero schermo. Dopo aver scattato uno screenshot utilizzando questo programma, puoi modificare l'immagine e salvarla in qualsiasi cartella sul tuo computer. @@ -70,26 +70,26 @@ Puoi inoltre provare a utilizzare svariate app per scattare screenshot sul tuo c ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Per effettuare uno screenshot su Mac, utilizza la seguente scorciatoia: - ***Premi e tieni premuti ***⌘ Cmd + Shift + 3****** Il tuo Mac catturerà l'intera schermata e la salverà come un file sul desktop. -To take a screenshot of an active window, use the following shortcut keys: +Per scattare uno screenshot di una finestra attiva, utilizza la seguente scorciatoia: - **Premi e tieni premuti *⌘ Cmd + Shift + 4 + Barra spaziatrice*. Il puntatore si trasformerà nell'icona di una fotocamera. Clicca la finestra per catturarla. Premi Esc per annullare la creazione del screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +Per scattare lo screenshot di un'area specifica, utilizza la seguente scorciatoia: - ***Premi ***⌘ Cmd + Shift + 5******. Trascina il puntatore per selezionare l'area necessaria. Rilascia il tuo mouse o trackpad per scattare uno screenshot, premi Esc per annullarlo. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +Per scattare uno screenshot della *Barra Tattile* (MacBook Pro), utilizza la seguente scorciatoia: - ***Premi ***⌘ Cmd + Shift + 6****** Il tuo Mac cattura l'intera *Barra Tattile* e la salva come un file sul desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +Per copiare uno screenshot negli appunti, invece di salvarlo, tieni premuto *Ctrl* con una qualsiasi delle precedenti scorciatoie da tastiera. Così, potrai incollare lo screenshot (dagli appunti) in un documento o un'immagine che stai modificando, utilizzando la scorciatoia *Cmd + V*. Inoltre, puoi scattare gli screenshot utilizzando **Anteprima** e scegliendo **Scatta screenshot** (dell'area selezionata, della finestra o dell'intera schermata). Con **Anteprima**, puoi salvare i tuoi screenshot in JPG, TIFF, PDF e altri formati di file. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/intro.md b/i18n/it/docusaurus-plugin-content-docs/current/intro.md index 61aea159086..abddefc6af3 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index 500a30fcadd..b7cb28cd688 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ I siti web modificano costantemente come incorporano gli annunci e, noi, aggiung Tuttavia, lavorare con i filtri di blocco richiede delle competenze specifiche. Se le hai e sai come creare le regole, dirigiti direttamente alla nostra [repository dei Filtri di AdGuard](https://github.com/AdguardTeam/AdguardFilters) su Github. Lì, troverai molti ticket aperti, ognuno riferito a un problema con qualche sito web: un annuncio non bloccato, un falso positivo, etc. Scegline uno qualsiasi e suggerisci le tue regole nei commenti. Gli ingegneri di filtraggio di AdGuard revisioneranno i tuoi suggerimenti e, se li troveranno appropriati, le tue regole saranno aggiunte ai filtri di AdGuard. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +Se non sei ancora familiare con la sintassi delle nostre regole di filtraggio, o non ti ricordi come funziona, troverai i fondamenti sulla sintassi [nella nostra Knowledge base](/general/ad-filtering/create-own-filters). ### Ricompense {#rewards} diff --git a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index f50fd2e2af8..e2d08c1d2c0 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Diventare un traduttore/revisore sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +Se desideri aiutare a tradurre i prodotti, siti web e Basi di conoscenza di AdGuard, vai su [Crowdin](https://crowdin.com/) e registrati/accedi. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index 4f0d7abe1a2..71c2c7f2207 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ Quando ti trovi di fronte una traduzione che richiede l'uso dei plurali, potrest Ecco alcune fonti di informazioni che puoi utilizzare. -La [Guida di Localizzazione](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contiene un ampio elenco di lingue. La quantità di forme plurali per le diverse lingue è mostrato come segue: `nplurals=2`, `nplurals=4` e così via. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +La [Guida di Localizzazione](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contiene un ampio elenco di lingue. La quantità di forme plurali per le diverse lingue è mostrato come segue: `nplurals=2`, `nplurals=4` e così via. Il numero dopo il segno Uguale `=` indica il numero di forme plurali della lingua rispettiva. Inoltre, puoi ottenere le informazioni sulle forme plurali nella [Repository Locale di Dati Comuni Unicode](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). Le Regole Plurali CLDR indicano una forma aggiuntiva della parola per i numeri decimali (1,5; 2,3; 100,1…), ma non le utilizziamo nelle traduzioni di AdGuard. diff --git a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 908a411cefb..54954e0aa4d 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: Programma di traduzione di AdGuard sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Avvertenza:** puoi farci qualsiasi domanda sulla traduzione di AdGuard, inviando un'email a [translate@adguard.com](mailto:translate@adguard.com) o unendoti alla nostra [chat di Telegram](https://t.me/joinchat/UVYTLcHbr8JmOGIy). -When it comes to translations, we at AdGuard always heavily rely on volunteers. +Quando si tratta di traduzioni, noi di AdGuard facciamo sempre molto affidamento sui volontari. -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +Ora, utilizziamo la [piattaforma Crowdin](https://crowdin.com/) per gestire le traduzioni dei nostri prodotti. Quindi, questo è il posto giusto per chiunque voglia contribuire ad AdGuard traducendo uno qualsiasi dei nostri prodotti, o più. -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +Se desideri essere tra i volontari che ci aiutano a tradurre AdGuard, sei pregato di leggere le informazioni su [come diventare un nostro traduttore](../become-translator) e [come collaboriamo con loro](../rewards). diff --git a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 07a3e37a713..989e4c8103f 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: Come dare priorità alle traduzioni dei file di Crowdin sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +Esistono cinque progetti principali di AdGuard su Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base) e [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). Non abbiamo delle linee guida chiare su con quali file o prodotti del progetto *AdGuard Applications* iniziare. Basta scegliere qualsiasi prodotto tu preferisca. Ci sono soltanto un paio di cose che vogliamo menzionare: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- Puoi visualizzare l'app soltanto nelle lingue per cui tutte le traduzioni sono state completate su Crowdin; - Consigliamo di tradurre le descrizioni per i negozi di app in un secondo momento, poiché, senza la traduzione dei prodotti stessi, le descrizioni non saranno necessarie. La situazione è differente nel progetto *AdGuard Websites*. Le lingue possono essere aggiunte al sito anche se non è disponibile una serie completa di traduzioni. Tuttavia, ciò dipende da quali file sono già stati tradotti. Ecco perché ti consigliamo di iniziare con i file più importanti, elencati di seguito: diff --git a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 0405f7e5284..f4a296bb02c 100644 --- a/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/it/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Aggiornare la Base di conoscenza sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. Ma le cose cambiano continuamente e, talvolta, un articolo non riflette più lo stato corrente delle cose. +L'obiettivo della Base di conoscenza del Blocco AdGuard è quello di fornire a tutti le informazioni più aggiornate su ogni tipo di argomento correlato ad AdGuard. Ma le cose cambiano continuamente e, talvolta, un articolo non riflette più lo stato corrente delle cose. Per questo abbiamo inserito tutti i contenuti della nostra KB su [GitHub](https://github.com/AdguardTeam/KnowledgeBase) e, ora, letteralmente chiunque può contribuire a essa suggerendo modifiche e traduzioni agli articoli esistenti, nonché proporne di totalmente nuovi. ## Come suggerire una modifica o scrivere un nuovo articolo {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. Se non sei familiare con i principi di lavoro con la piattaforma, inizia leggendo la [documentazione di GitHub](https://docs.github.com/en). +Puoi suggerire modifiche agli articoli esistenti e aggiungerne di nuovi alla nostra Base di conoscenza, utilizzando la funzionalità di GitHub menzionata sopra. Se non sei familiare con i principi di lavoro con la piattaforma, inizia leggendo la [documentazione di GitHub](https://docs.github.com/en). -Una volta pronto a iniziare, lavora nella [repository "KnowledgeBase"](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Tienilo a mente quando modifichi o scrivi articoli. Segui [questo link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) per scoprire di più sulla sintassi di Markdown. +Una volta pronto a iniziare, lavora nella [repository "KnowledgeBase"](https://github.com/AdguardTeam/KnowledgeBase). Tutti i testi nella nostra Base di conoscenza sono scritti nel linguaggio di markup `Markdown`. Tienilo a mente quando modifichi o scrivi articoli. Segui [questo link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) per scoprire di più sulla sintassi di Markdown. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. Suggerendo modifiche o aggiunte, considera che tutti i documenti devono conformarsi ai principi della piattaforma. Puoi saperne di più nelle [Guide di Docusaurus](https://docusaurus.io/docs/category/guides). +Il sito web della Base di conoscenza è stato creato usando Docusaurus 2: un generatore di siti web statici moderno. Suggerendo modifiche o aggiunte, considera che tutti i documenti devono conformarsi ai principi della piattaforma. Puoi saperne di più nelle [Guide di Docusaurus](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +Puoi distribuire questa Base di conoscenza localmente sul tuo computer per visualizzare in anteprima le modifiche che suggerisci. Istruzioni dettagliate su come farlo si possono trovare [nel file README](https://github.com/AdguardTeam/KnowledgeBase#readme) su questa pagina di GitHub della Base di conoscenza. ## Traduzione degli articoli {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +La traduzione degli articoli esistenti della Base di conoscenza è svolta sulla [piattaforma Crowdin](https://crowdin.com/profile/adguard). Tutti i dettagli sulle traduzioni e sull'utilizzo di Crowdin si possono trovare [nell'articolo dedicato](../translate/guidelines) della Base di conoscenza del Blocco-annunci AdGuard. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In un articolo separato](../translate/plural-forms), abbiamo descritto nel dettaglio le difficoltà che possono sorgere traducendo stringhe contenenti le forme plurali e abbiamo fornito istruzioni approfondite su come lavorarci sulla piattaforma di Crowdin. +Lavorando con gli articoli della Base di conoscenza di AdGuard, potresti incontrare delle stringhe contenenti forme plurali, che dovresti tradurre con particolare attenzione. [In un articolo separato](../translate/plural-forms), abbiamo descritto nel dettaglio le difficoltà che possono sorgere traducendo stringhe contenenti le forme plurali e abbiamo fornito istruzioni approfondite su come lavorarci sulla piattaforma di Crowdin. ## Lavorare a problemi aperti -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Scegli qualsiasi problema tu trovi interessante e inizia a lavorarci. Se hai domande, puoi farle direttamente nei commenti di quel problema. +Talvolta, esistono delle [attività aperte](https://github.com/AdguardTeam/KnowledgeBase/issues) correlate all'aggiornamento della Base di conoscenza. Puoi aiutarci a velocizzarne il completamento, [allo stesso modo](#suggest-change) in cui suggeriresti qualsiasi altra modifica alla Base di conoscenza. Scegli qualsiasi problema tu trovi interessante e inizia a lavorarci. Se hai domande, puoi farle direttamente nei commenti di quel problema. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 1aa74e90184..06193b15a19 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index 3b26da73c68..cb113b9d2cf 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ sidebar_position: 1 ## カスタムフィルタ -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +ほとんどのフィルタグループの機能は大体その名称から想像がつきますが、「カスタム」というグループについては疑問に思うかもしれません。 ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 7005f07cbfe..af38d278ee9 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ sidebar_position: 4 メイン画面では、ページ上の任意の要素を手動で非表示にしたり（対応するルールは「ユーザールール」に追加されます）、「フィルタリングログ」を開いてブラウザのトラフィックやブロック要求の情報を随時確認したり、ウェブサイトの安全性の報告を確認したりできます。 さらに、現在閲覧中のウェブサイトについて苦情を提出することができ（例えば、ページ上に見逃された広告がある場合、当社のフィルターエンジニアがご報告を確認し、問題を修正します）、適用されたブロックルールに関する統計情報を見ることができます。 -ブラウザが行なったすべてのウェブリクエストは、各リクエストの詳細情報とともに、「フィルタリングログ」に表示されます。 また、「フィルタリングログ」では、たとえば、AdGuard ブラウザ拡張機能によってブロックされたリクエストを簡単に監視できます。 また、2回クリックするだけで、あらゆるリクエストをブロックしたり、以前にブロックしたリクエストをホワイトリストに追加することができます。 また、「フィルタリングログ」では、ウェブリクエストをソートするためのさまざまなオプションが用意されており、独自のフィルタリングルールを作成する際に役立ちます。 You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +ブラウザが行なったすべてのウェブリクエストは、各リクエストの詳細情報とともに、「フィルタリングログ」に表示されます。 また、「フィルタリングログ」では、たとえば、AdGuard ブラウザ拡張機能によってブロックされたリクエストを簡単に監視できます。 また、2回クリックするだけで、あらゆるリクエストをブロックしたり、以前にブロックしたリクエストをホワイトリストに追加することができます。 また、「フィルタリングログ」では、ウェブリクエストをソートするためのさまざまなオプションが用意されており、独自のフィルタリングルールを作成する際に役立ちます。 「フィルタリングログ」を開くには、メインメニューの対応する項目を選択するか、⚙設定→「追加設定」から開くことができます。 拡張機能のメインメニューの右上にあるアイコンを使って、拡張機能の設定を開いたり（⚙アイコン）、保護機能を一時停止したり（⏸アイコン）することができます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 62efaa96eb3..6ce29ba2b1c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ AdGuard ブラウザ拡張機能の主要なモジュールのほかに、拡張 ## 一般 {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +「一般」タブでは、検索連動型広告とウェブサイトの自己宣伝広告の許可、言語特化フィルタの自動有効化の設定、フィルタの更新間隔の指定、などができます。 ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) また、「[フィッシング詐欺とマルウェアからの保護](/general/browsing-security)」を有効にすることもできます。 -「設定をエクスポート」ボタンをクリックすることで、設定内容を保存することができます。 設定内容は .json ファイルとして保存されます。 To import the previously saved settings configuration, use the _Import settings_ function. この機能を使用して、簡単に異なる設定プロファイルに切り替えたり、設定内容を異なるブラウザ間で転送したりできます。 +「設定をエクスポート」ボタンをクリックすることで、設定内容を保存することができます。 設定内容は .json ファイルとして保存されます。 保存した設定内容をブラウザ拡張機能にアップロードするには、「設定をインポート」機能を使用してください。 この機能を使用して、簡単に異なる設定プロファイルに切り替えたり、設定内容を異なるブラウザ間で転送したりできます。 ## 追加設定 {#misc} @@ -33,6 +33,6 @@ In the _General_ tab, you can allow search ads and the [self-promotion of websit ## AdGuard について {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +「AdGuardについて」セクションには現在のバージョンに関する情報と、利用許諾契約(EULA)、プライバシーポリシー、Githubリポジトリへのリンクがあります。 ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index 7d0a29feaa7..9cf67d2471e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 698805bb61c..66be87de3e7 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ sidebar_position: 2 ### "問題のない"アプリと"問題あり"アプリ -Most apps work correctly when filtered. このような"問題なし"アプリのトラフィックは AdGuard を経由してルーティングされ、デフォルトでフィルタリングされます。 +フィルタリングを有効にすると、ほとんどのアプリは正常に動作します。 このような"問題なし"アプリのトラフィックは AdGuard を経由してルーティングされ、デフォルトでフィルタリングされます。 Download Manager、ラジオ、UIDが1000および1001のシステムアプリ（例：Google Playサービス）など、一部のアプリは"問題あり"で、AdGuardを経由すると正しく動作しない可能性があります。 そのため、すべてのアプリをルーティングまたはフィルタリングしようとすると、次のような警告が表示されることがあります: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3056956eea7..4a976694612 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ sidebar_position: 4 :::tip -「DNS通信を保護」は、通常の広告やトラッカーのブロック機能とは異なる動作をします。 You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +「DNS通信を保護」は、通常の広告やトラッカーのブロック機能とは異なる動作をします。 その仕組みについては[こちらの専用記事](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work)でご確認いただけます。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 7165c782c9c..d06fc9aaba3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ sidebar_position: 1 ### 通知 -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. すべてのアプリ、またはアプリごとに通知のオン／オフを切り替えることができます。 +この機能を有効にすると、アプリがそのアプリに対して設定されているファイアウォールルールのいずれかを破ろうとしたときに通知が表示されます（たとえば、モバイルデータ通信へのアクセスが制限されているアプリがモバイル通信しようとした時など）。 すべてのアプリ、またはアプリごとに通知のオン／オフを切り替えることができます。 通知をタップするとアプリに対するファイアウォール設定を開くことができます。また、通知内の対応するボタンをタップして、そのアプリに対するすべてのファイアウォールルールを一時的に無効にすることができます。 さらに、通知内の「ミュート」ボタンをタップすると、そのアプリに対するファイアウォール通知をすべてミュートできます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index 622ef61e060..c67cea4a2b4 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ sidebar_position: 2 ⑩ _X-Client-Dataヘッダーを削除する_ この機能により、Google Chromeのバージョンや変更に関する情報がGoogleドメイン（DoubleClickやGoogle Analyticsを含む）に送信されるのを防ぎます。 -「トラッキング防止」で個々の設定を微調整し、カスタム設定にしたりすることもできます。 各設定には、その役割を理解するのに役立つ説明がついています。 [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +「トラッキング防止」で個々の設定を微調整し、カスタム設定にしたりすることもできます。 各設定には、その役割を理解するのに役立つ説明がついています。 [さまざまな「トラッキング防止」設定の効果について詳しくはこちら](/general/stealth-mode)をご覧ください。※一部の設定はウェブサイトやブラウザ拡張機能の機能に干渉する可能性があるため、注意しながらご使用ください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index f8ac22fb39a..c3ccde74ff1 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ sidebar_position: 7 Android OSのセキュリティ対策により、AdGuardの一部の機能はroot化されたデバイスでのみ利用可能です。 そういった機能は以下の通りです: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **ほとんどのアプリでの HTTPS フィルタリング**には、[システム ストアに CA 証明書をインストールする](/adguard-for-android/features/settings#security-certificates) 必要があります。アプリの多くはユーザー ストアの証明書を信頼しないためです。 システムストアに証明書をインストールできるのは、ルート化されたデバイスのみです。 - Androidのシステム全体のトラフィックフィルタリングの制限により、[**自動プロキシ**ルーティングモード](/adguard-for-android/features/settings#routing-mode)にはルートアクセスが必要です。 - Android 10以降では、[**手動プロキシ**ルーティングモード](/adguard-for-android/features/settings#routing-mode)にルートアクセスが必要です。AdGuardによってフィルタリングされた接続に関連付けられたアプリの名前を特定できなくなったためです。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 520fc2ca0b0..a94f8da51dc 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -27,7 +27,7 @@ sidebar_position: 4 「ウォッチドッグ（Watchdog）」は、AdGuard がシステムによって無効化されるのを防ぎます ([Android のバッテリー節約モードについてもお読みください](/adguard-for-android/solving-problems/background-work/))。 入力した値は、ウォッチドッグチェック間の間隔 (秒単位) になります。 -「ログ・レベル」は、アプリの操作に関するどのデータをログに記録するかを定義します。 「デフォルト」レベルでは、アプリはイベントに関するデータを収集します。 「デバッグ」レベルでは、より多くのイベントがログに記録されます。AdGuard チームから問題をより深く理解するために有効にするよう依頼されましたら、これを有効にしてください。 [Read more about collecting and sending logs](/adguard-for-android/solving-problems/log/) +「ログ・レベル」は、アプリの操作に関するどのデータをログに記録するかを定義します。 「デフォルト」レベルでは、アプリはイベントに関するデータを収集します。 「デバッグ」レベルでは、より多くのイベントがログに記録されます。AdGuard チームから問題をより深く理解するために有効にするよう依頼されましたら、これを有効にしてください。 [ログの収集と送信について詳しくはこちら](/adguard-for-android/solving-problems/log/) ![Advanced \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) @@ -59,7 +59,7 @@ AdGuard は、フィルタのルールを適用することで、広告、トラ ### ユーザースクリプト -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. ユーザースクリプトをインストールするには、専用のユーザースクリプト・マネージャが必要です。 AdGuard にはこのようなマネージャー機能があるので、そのままURLまたはファイルからユーザースクリプトを追加することができます。 +ユーザースクリプトは、1 つ以上の Web サイトの機能を拡張するミニプログラムです。ユーザースクリプトは JavaScript で書かれています。 ユーザースクリプトをインストールするには、専用のユーザースクリプト・マネージャが必要です。 AdGuard にはこのようなマネージャー機能があるので、そのままURLまたはファイルからユーザースクリプトを追加することができます。 ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ AdGuardを、デバイスのすべてのトラフィックをプロキシサー - [フルバージョンの機能](/adguard-for-android/features/free-vs-full)を有効にするためのAdGuardライセンス購入 - AdGuard アカウントにログインするか、ライセンスキーを入力してライセンスを有効化 - 7日間の無料試用期間をまだ利用していない場合は、登録して試用期間を有効にする -- Refresh the license status from the three-dots menu (⋮) +- 右上の三点メニュー (⋮) からライセンスステータスを更新する - AdGuard アカウントを開いてライセンスを管理する - ライセンスをリセットする（たとえば、ライセンスの最大デバイス数上限に達し、別のライセンスを適用したい場合などです。） diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index f0739813230..d2495aa935e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Option 2 To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -199,7 +199,7 @@ On Android 11, Samsung will prevent apps (including AdGuard) from working in bac **Settings** → **Apps** → (⁝) menu → **Special Access** → **Optimize battery usage** → Find AdGuard on the list and uncheck it -1. Disable automatic optimization. その方法は以下の通りです: +1. Disable automatic optimization. To do so: Open **Battery** → (⁝) menu → Choose **Automation** → Toggle off all of the settings there @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 183b504b07e..42d9be175fe 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. そういった表示の原因、AdGuardがさまざまなアプリからのトラフィックをすべてカウントしていたためです。 その結果、総データ使用量とバッテリー使用量において、AdGuardの分は過大に表示され、他のアプリは過小に表示されていました。 +OS 6およびそれ以前のAndroidデバイスでは、内蔵の統計により、多くのデータおよびバッテリーの使用量がAdGuardに起因しているかのよう表示されることがよくありました。 そういった表示の原因、AdGuardがさまざまなアプリからのトラフィックをすべてカウントしていたためです。 その結果、総データ使用量とバッテリー使用量において、AdGuardの分は過大に表示され、他のアプリは過小に表示されていました。 しかし、Android 7では、この状況は改善しました。 現在、Android内蔵のデータ使用量統計に反映されるデータは、バッテリー使用量データに若干の不一致があるものの、現実に非常に近いものになっています。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..bed628c5524 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. +この記事では、複雑な問題を解決するために不可欠なトラブルシューティングのステップである、デバッグログというものの収集方法をご紹介しています。 Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. :::note @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index df40ba37f5d..f296d923945 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -41,7 +41,7 @@ If this setting is enabled, AdGuard will detect search domains and automatically Bootstrap DNS for DoH, DoT, and DoQ servers. The *Automatic DNS* — the system DNS or AdGuard DNS — is used by default. By selecting *Custom DNS*, you can list IPv4 and IPv6 server addresses to use as bootstrap upstreams. -#### adblock-styleルール用ブロックモード +#### Blocking mode for adblock-style rules Here you can specify the response type for domains blocked by DNS rules based on adblock rule syntax (for instance, `||example.org^`). @@ -49,7 +49,7 @@ Here you can specify the response type for domains blocked by DNS rules based on - Respond with NXDOMAIN - Respond with Custom IP address (IPv4 and IPv6 addresses can be specified here) -#### hostsルール用ブロックモード +#### Blocking mode for hosts rules Here you can specify the response type for domains blocked by DNS rules based on hosts rule syntax (for instance, ` 0.0.0.0 example.com`). @@ -59,7 +59,7 @@ Here you can specify the response type for domains blocked by DNS rules based on #### DNS request timeout -ここで、AdGuardがフォールバックに頼る前に、選択したDNSサーバーからの応答を待つ時間をミリ秒単位で指定できます。 このフィールドに何も入力しないか、無効な値を入力すると、5000という値が使用されます。 +Here you can specify the time in milliseconds that AdGuard will wait for the response from the selected DNS server before resorting to fallback. If you don’t fill in this field or enter an invalid value, the value of 5000 will be used. #### Blocked response TTL @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -暗号化されたインターネット接続には、暗号化されていない部分があります。 その部分とは、接続先のサーバー名を含む最初の通信パケットです。 Encrypted Client Hello 技術は、この問題を解決し、この暗号化されていない部分を暗号化してくれます。 To benefit from it, enable the *Encrypted Client Hello* option. このオプションは、ローカル DNS プロキシを使用して、ドメインの ECH 構成を検索します。 見つかった場合、ClientHello パケットは暗号化されます。 +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -121,13 +121,13 @@ If this setting is enabled, AdGuard will perform asynchronous OCSP checks to get If an OCSP check is completed within the required timeout, AdGuard will immediately block the connection if the certificate is revoked or establish the connection if the certificate is valid. -If the verification takes too long, AdGuard will allow the connection while continuing to check the certificate status in the background. 証明書が失効している場合は、そのドメインへの現在の接続および今後の接続はブロックされるようになります。 +If the verification takes too long, AdGuard will allow the connection while continuing to check the certificate status in the background. If the certificate is revoked, current and future connections to the domain will be blocked. #### Redirect DNS-over-HTTPS requests If this setting is enabled, AdGuard will redirect DNS-over-HTTPS requests to the local DNS proxy in addition to plain DNS requests. We recommend disabling fallback upstreams and using only encrypted DNS servers to maintain privacy. -#### HTTP/3 をフィルタリングする +#### Filter HTTP/3 If this setting is enabled, AdGuard will filter requests sent over HTTP/3 in addition to other request types. @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 7030474c979..3047ef1dcdb 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +[HTTPSトラフィック（通信）をフィルタリング](/general/https-filtering/what-is-https-filtering.md)できるようになるには、AdGuardはデバイスのユーザーストレージに証明書をインストールする必要があります。（※ほとんどの広告がHTTPSを使用しているため、HTTPSフィルタリングは広告ブロック性能にとって非常に重要です。） On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![証明書 *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +AdGuard証明書をインストールする方法は以下の通りです: 1. 「*HTTPS フィルタリングがオフになっています*」という通知が表示されたら、「*有効にする*」をタップします。 1. すると、3つの説明画面が順番に表示されます: - HTTPSトラフィックをフィルタリングする理由 - AdGuardによるHTTPSフィルタリングが安全である理由 - - The necessity of the AdGuard certificate + - AdGuard証明書の必要性 Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 35dd8a568a8..00000000000 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: 無料版 vs フルバージョン（有料版） -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. 実際どのように機能するのかを確認するには、[AdGuard アプリ](https://agrd.io/download-kb-adblock)をダウンロードしてください。 - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 5ec0a9a0b06..5076c1e9407 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ Requires iOS 13 or later. ![App Storeのメイン画面で、「検索」をタップします *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![検索バーに"AdGuard"と入力します。 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ Type *adguard* in the search bar and tap the string *AdGuard* which will be amon ![App Storeのメイン画面で、「検索」をタップします *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![検索バーに"AdGuard"と入力します。 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. 必要に応じてApple IDのパスワードを入力してください。 インストールが完了するのを待ちます。 +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. 必要に応じてApple IDのパスワードを入力してください。 インストールが完了するのを待ちます。 ![AdGuardアプリの下の「入手する」をタップします。 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index 156779c8ce3..163e14ae0d4 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ sidebar_position: 4 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## SafariでYouTube広告をブロックする方法 @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index 247c867a76d..cba8e9cdd31 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: AdGuard使用時FaceTime不具合の対処法 sidebar_position: 3 --- diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index e5e254451b4..b50b82b61c2 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/system-wide-filtering.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/system-wide-filtering.md index b96f21dfb3c..e40f752c652 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/system-wide-filtering.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/system-wide-filtering.md @@ -15,7 +15,7 @@ iOSでのシステムワイドブロックとは、Safariブラウザ以外、 On iOS, the only way to block ads and trackers system-wide is to use [DNS filtering](https://adguard-dns.io/kb/general/dns-filtering/). -First, you have to enable DNS protection. その方法は以下の通りです: +First, you have to enable DNS protection. To do so: 1. Open *AdGuard for iOS*. 2. Tap *Protection* icon (the second icon in the bottom menu bar). diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 9f61bd58f86..b58dcdfc263 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ sidebar_position: 9 #### `network.https.ech.enabled` -ECH Configs Lists内のconfigsを検索するために、ローカルDNSプロキシを使用します。 If found, encrypts Client Hellos. +ECH Configs Lists内のconfigsを検索するために、ローカルDNSプロキシを使用します。 見つかった場合、ClientHellosを暗号化します。 #### `network.https.enforce.certificate.transparency` diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index a3998273b62..6509040ba8c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ Monterey または Big Sur で、「ネットワーク拡張」モードのAdGua #### レガシーAPIを使用したVPNアプリ -AdGuard はシステム設定では VPN として表示されますが、他の VPN ベースのアプリと一緒に動作しても競合は発生しません。 However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +AdGuard はシステム設定では VPN として表示されますが、他の VPN ベースのアプリと一緒に動作しても競合は発生しません。 ただし、App Store 以外からダウンロードした VPN ベースのアプリを使用している場合は、古い VPN API を使用している可能性があるため、フィルタリングから除外しておく必要があります。 1. AdGuardのメニューを開きます。 1. *設定...* を選択します。 @@ -79,9 +79,9 @@ AdGuard はシステム設定では VPN として表示されますが、他の ### Little Snitch 5 との互換性 -現時点では、AdGuard のネットワーク拡張モードは [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html)と互換性がありません。 When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. この問題は Big Sur のバグによって引き起こされており、我々はすでに Apple にその旨を通知しています。 このため、この問題は今後のmacOSアップデートで解決されると思われます。 +現時点では、AdGuard のネットワーク拡張モードは [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html)と互換性がありません。 両方が実行されている場合、AdGuardによってフィルタリングされていなくても、さまざまなアプリの動作に問題が発生する可能性があります。 この問題は Big Sur のバグによって引き起こされており、我々はすでに Apple にその旨を通知しています。 このため、この問題は今後のmacOSアップデートで解決されると思われます。 -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. Apple がバグを修正するまでは、Big Sur で AdGuard を Little Snitch と併用する場合は、 [**自動プロキシ**](#automatic-proxy) フィルタリング モードに切り替えることをお勧めします。 +※この問題は、Little Snitch で接続監視を無効にするだけでは解決できません。このアクションでは、Little Snitch の拡張機能がシステムからアンロードされないためです。 Apple がバグを修正するまでは、Big Sur で AdGuard を Little Snitch と併用する場合は、 [**自動プロキシ**](#automatic-proxy) フィルタリング モードに切り替えることをお勧めします。 ### ローカルプロキシとの互換性問題 @@ -121,7 +121,7 @@ Big Surにおいて、AdGuard for Mac でアップストリームプロキシを :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +設定方法についてさらに詳しくは、 [Shadowsocks の Web サイト](https://shadowsocks.org/guide/what-is-shadowsocks.html)をご覧ください。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index 78a76998031..c9ba7207118 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ sidebar_position: 3 ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". これは High Sierra で登場した新しいセキュリティメカニズムであり、サードパーティのシステム拡張のインストールを明示的に許可する必要があります。 AdGuard のインストールを完了するには、 *システム環境設定* → *セキュリティ & プライバシー* → *一般* で拡張機能の読み込みを手動で許可する必要があります。 +macOS High Sierra (またはそれ以降のバージョン) に AdGuard をインストールしているときに、「システム拡張がブロックされました」というメッセージが表示される場合があります。 これは High Sierra で登場した新しいセキュリティメカニズムであり、サードパーティのシステム拡張のインストールを明示的に許可する必要があります。 AdGuard のインストールを完了するには、 *システム環境設定* → *セキュリティ & プライバシー* → *一般* で拡張機能の読み込みを手動で許可する必要があります。 ![設定で拡張機能のインストールを許可する](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 55ea51f3f8c..1145b4d68e1 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ Monterey では、iCloud プライベート リレーが登場しました。 Ma 1. iCloud プライベートリレーは、ライブラリレベル（AdGuard が動作するソケットレベルに到達する前）で接続に適用されます。 2. iCloud プライベートリレーは QUIC を使用しますが、HTTP/3 フィルタリングはまだ利用できないため、AdGuard はQUICをフィルタリングできません。 -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. その結果、AdGuard は iCloud プライベートリレー トラフィックを含む QUIC をブロックしてしまいます。そうしないと、広告をブロックすることは不可能になるからです。 4. iCloud プライベートリレーを使用し、AdGuard を「split-tunnel」モードに切り替えると、Safari で Web サイトを開くことができなくなります。 5. Monterey でこの問題を回避するには、「デフォルトルート」ルールを適用します。 プライベートリレーはそのルールを検出すると、自動的に無効になります。 つまり、AdGuard は Monterey 上でシームレスに動作しますが、その場合、iCloud プライベート リレーは無効になります。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1abaf8f36e8..f5cb777d34b 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ sidebar_position: 5 :::note リマインダー -AdGuard for Safari は無料で [App Store からダウンロード](https://apps.apple.com/app/adguard-for-safari/id1440147259)できます。 A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari は無料で [App Store からダウンロード](https://apps.apple.com/app/adguard-for-safari/id1440147259)できます。 詳しいセットアップ手順は、[こちらのナレッジベース記事](/adguard-for-safari/installation/)にあります。 ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index d8de647ee77..7c366181d49 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: ユーザールール sidebar_position: 4 --- -ユーザールールは、広告ブロックの効果をカスタマイズするために使用することができます。 ユーザールールは、手動で追加することも、インポートすることも、ページ上の要素をブロックしたときに自動的に作成することもできます。 To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +ユーザールールは、広告ブロックの効果をカスタマイズするために使用することができます。 ユーザールールは、手動で追加することも、インポートすることも、ページ上の要素をブロックしたときに自動的に作成することもできます。 独自のフィルタリングルールを追加するには、[専用の構文](/general/ad-filtering/create-own-filters)を使ってください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index 08d581bd52a..5216471a411 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -1,5 +1,5 @@ --- -title: How to collect logs in AdGuard for Safari +title: AdGuard for Safari のログを収集する方法 sidebar_position: 4 --- @@ -9,9 +9,9 @@ sidebar_position: 4 ::: -AdGuard for Safari で発生した問題を分析および診断するために、AdGuardのお客様サポートサービスはログファイルを必要とする場合があります。 このようなログファイルには、エラーやその他のソフトウェア・イベントの記録が含まれます。 Below are brief instructions on how to collect logs and send them to support if necessary. +AdGuard for Safari で発生した問題を分析および診断するために、AdGuardのお客様サポートサービスはログファイルを必要とする場合があります。 このようなログファイルには、エラーやその他のソフトウェア・イベントの記録が含まれます。 以下は、ログを収集し、必要に応じてAdGuardサポートに送信する方法についての簡単な説明です。 -### How to collect logs +### ログを収集する方法 1. AdGuard for Safari アプリを開きます。 2. 下にスクロールし、「_ログをエクスポートする_」をクリックします。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 3f1a71b6959..89bd0fe4370 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard アシスタントは、[新しいアシスタント](/adguard-for-windo これは、ブロックされた広告を再度挿入する手法（いわゆる広告ブロッカー回避や広告再投入という技術）への対処法として設計されたカスタム拡張機能です。 どちらも、広告主の間で人気が高まり続けている高度な広告ブロッカー対策手法です。 -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra は、基本的にミニプログラムで、サイトがブロッカーを回避するために上記の方法を使用することがより困難になるように、ページの動作方法を変更します。 **AdGuard ポップアップブロッカー** -この拡張機能は、ウェブページ閲覧時にポップアップウィンドウが開かないようにしてくれます。 ポップアップの中には、サイト管理のための設定や、リンクをクリックしたときに表示される追加参考情報が含まれているような、役に立つとされるポップアップもたまにあります。 そのため、必要に応じてAdGuard ポップアップブロッカーをオフにすることができます。 また、この拡張機能は、AdGuard の除外リストに追加されたウェブサイトでも機能しません。 デフォルトではオフになっていますが、アプリの設定でオンにすることができます。 You will find more detailed information about this extension in our Knowledge Base. +この拡張機能は、ウェブページ閲覧時にポップアップウィンドウが開かないようにしてくれます。 ポップアップの中には、サイト管理のための設定や、リンクをクリックしたときに表示される追加参考情報が含まれているような、役に立つとされるポップアップもたまにあります。 そのため、必要に応じてAdGuard ポップアップブロッカーをオフにすることができます。 また、この拡張機能は、AdGuard の除外リストに追加されたウェブサイトでも機能しません。 デフォルトではオフになっていますが、アプリの設定でオンにすることができます。 この拡張機能についての詳細情報はKnowledge Baseをご確認ください。 **Web of Trust** @@ -41,7 +41,7 @@ Web of Trustを使って、各ウェブサイトの、ユーザーの意見に ### ネットワーク -このモジュールはネットワークフィルタリング専用のもので、ネットワーク関連の追加オプションがあります。 Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. これらは、あなたのウェブスペースをより良くフィルタリングするための重要な追加予防措置です。 現在、ほとんどのウェブサイトがHTTPSを使用しており、広告も同様です。 From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +このモジュールはネットワークフィルタリング専用のもので、ネットワーク関連の追加オプションがあります。 このうち、「トラフィックフィルタリングを有効にする」と「HTTPS をフィルタリングする」は、デフォルトで有効になっています。 これらは、あなたのウェブスペースをより良くフィルタリングするための重要な追加予防措置です。 現在、ほとんどのウェブサイトがHTTPSを使用しており、広告も同様です。 youtube.com、facebook.com、twitter.comなど多くのサイトでは、HTTPSフィルタリングなしでは広告を削除することができません。 そのため、特別な理由がない限り、「HTTPSをフィルタリングする」機能は有効にしておいてください。 ![ネットワーク設定 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 44c504170ba..98474a308d1 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ sidebar_position: 2 ### 一般設定 -ここでは、言語とカラーテーマ（ダーク・ライト）の設定、システム起動時のAdGuardの起動と自動アップデートの有効化、アップデートチャネルの選択、フィルタ更新チェック間隔の指定などを行うことができます。 Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +ここでは、言語とカラーテーマ（ダーク・ライト）の設定、システム起動時のAdGuardの起動と自動アップデートの有効化、アップデートチャネルの選択、フィルタ更新チェック間隔の指定などを行うことができます。 また、AdGuard for Windows が正常に動作せず、サポートチームから[「デバッグログ」を収集する](/adguard-for-windows/solving-problems/adguard-logs.md)ように依頼された場合も、「設定」が役に立ちます。 ![高度な設定 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ AdGuard for Windows の「DNS通信を保護」モジュールでは、広告と このモジュールは、ブラウザで開かれたウェブページの内容をチェックし、子供にとって好ましくない内容（大人向けの画像やテキスト、下品な言葉、暴力、薬物の宣伝など）のものをフィルタリングします。 ペアレンタルコントロールの設定はパスワードで保護されているため、子供が自分で制限をオフにすることはできません。 このモジュールは、好ましくないサイトへの誘導をブロックするだけでなく、検索結果から子供に不適切なリンクを削除することもできます。 -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. 「実行形式ファイルのダウンロードをブロック」を有効にしますと、お子様のコンピュータへのソフトウェアのダウンロードとインストールを防ぎます。 _ペアレンタルコントロール_モジュールにはさらに 2 つのオプションがあります。_ペアレンタルコントロール_で保護対象の特定の Windows ユーザーを指定するオプションと、AdGuard 設定が変更されないようにパスワードを設定するオプションです。 +ペアレンタルコントロールモジュールでは、「_セーフサーチ_」を有効にし、「_ブラックリスト_」と「_ホワイトリスト_」を管理して、この機能の動作をカスタマイズすることができます。 「実行形式ファイルのダウンロードをブロック」を有効にしますと、お子様のコンピュータへのソフトウェアのダウンロードとインストールを防ぎます。 _ペアレンタルコントロール_モジュールにはさらに 2 つのオプションがあります。_ペアレンタルコントロール_で保護対象の特定の Windows ユーザーを指定するオプションと、AdGuard 設定が変更されないようにパスワードを設定するオプションです。 ![ペアレンタルコントロール \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index aca84f40f78..13a684c310e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ sidebar_position: 2 Microsoft Windowsを搭載したPCやタブレットでAdGuardを使用するには、インストールパッケージをダウンロードして、インストールプログラムを起動する必要があります。 以下の操作を行ってください: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 98718ae6723..72263058e56 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -1,72 +1,72 @@ --- -title: ログの収集・送信方法 +title: How to collect AdGuard logs sidebar_position: 3 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: :::note -※ログで提供されたデータおよびファイルは、[AdGuardのプライバシーポリシーに従って](https://adguard.com/en/privacy.html)処理されます。 +Data and/or files provided in logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -AdGuard for Windows で発生した問題を分析および診断するために、AdGuardのお客様サポートチームはログファイルを必要とする場合があります。 これらのファイルには、ソフトウェアで発生したエラーやその他のイベントに関する記録が含まれています。 以下は、ログファイルを取得し、必要に応じてAdGuardサポートに送信する方法についての簡単な説明です。 +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note -AdGuard は、お客様のプライバシーを保護することに強くコミットしています。 [プライバシーポリシー](https://adguard.com/privacy/windows.html)を厳守し、ユーザーの個人情報を収集することはありません。 サポートチームにログを送信する前に、機密情報や共有したくない情報が含まれていないかどうか、ログファイルを確認してください。 そのような個人情報が含まれている場合は、削除してからログを送信することをお勧めします。 +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -### デバッグログ {#debug-logs} +### Debug logs {#debug-logs} -1. AdGuardアプリ内で「設定」を開きます。 *一般設定* セクションに移動し、画面の一番下までスクロールして、「*ログレベル*」を「*デバッグ*」に切り替えます。 +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. - ![デバッグログレベル *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) + ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) -1. 問題を再現します。 +1. Reproduce the issue. - 問題が発生した正確な時刻をメモしておくことを強くお勧めします。そうすることで、サポートチームが問題に関連するログエントリーを見つけ、問題をより早く解決することができます。 + We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. 「*ログをエクスポートする*」ボタンを使用して、記録されたログをエクスポートします。 +1. Export the recorded logs using the *Export Logs* button. - ![ログをエクスポート *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) + ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) - アーカイブを任意のフォルダに保存します。 + Save the archive to any folder. -1. **重要**: ログをエクスポートした後、ログレベルを「*デフォルト*」に戻してください。 「*デバッグ*」ログレベルのまましてしまうと、アプリの動作が劇的に低速下します。 +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. -1. アーカイブを AdGuard サポートサービス (**support@adguard.com**) に送信し、問題を説明してください。また、問題が再現された時刻も必ず記入してください。 +1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. -### トレース（Trace）ログ {#trace-logs} +### Trace logs {#trace-logs} -サポートチームのメンバーから、 *トレース*ログの送信を依頼されることがあります。 Traceログの収集方法は以下の通りです: +Sometimes support team members may ask you to send *trace* logs. Then you will need to do the following: -1. トレイメニューのAdGuardアイコンを右クリックし、[ *AdGuardを終了*]を選択してAdGuardを停止します。 +1. Stop AdGuard by right-clicking the AdGuard icon in the tray menu and choosing *Exit AdGuard*: - ![AdGuardを終了する *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-3.png) + ![Exit AdGuard *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-3.png) - サービスを稼働させたままにしないでください: + Please don't leave the service running: - ![AdGuardサービスを停止する *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_logs_4.png) + ![Stop AdGuard Service *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_logs_4.png) -1. コンソールを開きます (スタートパネルに `cmd` と入力します)。 +1. Open the console (type `cmd` in the start panel). -1. AdGuard for Windows v7.16以降をインストールしている場合は、Windows のビット数に関係なく、コマンド `C:\"Program Files"\Adguard\Adguard.exe /trace` でAdGuardアプリを実行します。 +1. Run the application with the command `C:\"Program Files"\Adguard\Adguard.exe /trace` regardless of Windows bitness if you have installed AdGuard v7.16 for Windows or later. -Windows 用 AdGuard のより古いバージョンをお持ちの場合は、64 ビット Windows を使用している場合は C:\"Program Files (x86)"\Adguard\Adguard.exe /trace コマンドでAdGuardアプリを実行し、32 ビットを使用している場合は C:\"Program Files"\Adguard\Adguard.exe /trace コマンドでAdGuardアプリを実行します。 +If you have an older version of AdGuard for Windows, run the application with the command C:\"Program Files (x86)"\Adguard\Adguard.exe /trace if you are using 64-bit Windows, and C:\"Program Files"\Adguard\Adguard.exe /trace if you are using 32-bit. -1. 問題を再現します。 +1. Reproduce the issue. - 問題が発生した正確な時刻をメモしておくことを強くお勧めします。そうすることで、サポートチームが問題に関連するログエントリーを見つけ、問題をより早く解決することができます。 + We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. 「*ログをエクスポートする*」ボタンを使用して、記録されたログをエクスポートします。 +1. Export the recorded logs using the *Export Logs* button. - ![ログをエクスポート *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) + ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) - ログファイルが大きくても心配しないでください。 問題を解決するためには、できるだけ詳しい情報ほど、より早く解決策を見つけることができます。 + Don't worry if the log file is large. We need to know as much detail as possible to fix your problem. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 5cf682b9c41..1421de96bcf 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -1,96 +1,96 @@ --- -title: AdGuard インストール中の一般的なエラー +title: Common installer errors sidebar_position: 6 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -本記事には、AdGuard for Windows のインストール中に発生する可能性のある最も一般的なエラーと、その解決方法が記載されています。 +This article contains some of the most common errors that you can encounter during the AdGuard for Windows installation, and possible ways to solve them. -### エラー 5: アクセスが拒否されました {#error-5} +### Error 5: Access Denied {#error-5} -必要なアクセス権限が与えられていない場合に、このエラーメッセージが表示されます。 AdGuard インストーラー（インストール用プログラム）がインストールのプロセスを適切に完了するために必要な権限を持っていない理由はいくつか考えられます。 以下の手順を試してみてください: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- お使いのウイルス対策ソフト（アンチウイルス）を一時的に無効にしてください。 それらの設定の度合いによっては、AdGuard のインストールを妨害するものもあります。 +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. -- 別のインストールフォルダを選択してください。 現在のインストールフォルダに何らかのアクセス制限がある可能性があります。 また、外付けドライブや仮想ドライブなどを選択しないようにしてください。 +- Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. -- コンピュータを再起動してください。 場合によっては、アクセス権限関連問題は一時的なものであり、PC を再起動することで解決できたりすることがあります。 +- Reboot your computer. Sometimes the permission issues are temporary and can be solved by restarting the PC. -### エラー112: ディスクの空き容量が足りない　エラー1632: 一時フォルダがいっぱいもしくはアクセス不可能 {#error-112} +### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -これらは 2 つの異なるエラーですが、解決策は非常に似ています。 その名前が示すように、AdGuard インストーラーがインストールを完了するのに十分なディスク容量を見つけられなかった場合に表示されるエラーです。 問題を解決するにはいくつかの方法があります: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: -- AdGuard をインストールしようとしているドライブから、いくつかのプログラムをアンインストールするか、不要なファイルを削除してください。 +- Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Malwarebytes による無料ソフトウェア [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/) をダウンロード、インストールし、実行しください。 これは、特に、誤ってアンインストールしたプログラムなどの後に残る、あらゆる種類の余分な「残り物」ファイルからシステムをクリーンアップしてくれます。 ディスク領域を空けるのにも役立ちます。 +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. -- コンピュータを再起動してください。 一時ファイルがかなりのディスク容量を占めることがあり、PCを再起動することが、一時ファイルを取り除く最も確実な方法です。 +- Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. -### エラー 1601: Windowsインストーラーにアクセスできません {#error-1601} +### Error 1601: Windows Installer is not accessible {#error-1601} -これはエラー1603のサブカテゴリー的なものであると言えます。 考えられる解決策も似ています: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: -- Microsoftインストーラーサービスを開始して再登録してください。 これを行うには、多少のステップを踏む必要があります: +- Start and re-register Microsoft Installer service. It requires some work. - 1) *Win + R* を押して、 **services.msc** と入力します。 2) リストから *Windows インストーラー* を探し、ダブルクリックします。 3) *サービスステータス* の下の「*開始*」ボタンを押し、「*OK*」を押します。 サービスステータスが**実行中**の場合、まず「*停止*」をクリックし、次に「*開始*」をクリックします。 4) *Win + R* を押し、 ***msiexec /unregister*** と入力し、 *Enter*キーを押します。 5) *Win + R* をもう一度押し、 ***msiexec /regserver*** と入力し、 *Enter*キーを押します。 + 1) Press *Win + R* and enter **services.msc**. 2) Find in the list and double click *Windows Installer*. 3) Hit *Start* button under *Service status* and hit *OK*. If the service status is **running**, you should click *Stop* first and then hit *Start*. 4) Press *Win + R*, type and enter ***msiexec /unregister*** and hit *Enter*. 5) Press *Win + R* again, type and enter ***msiexec /regserver*** and hit *Enter* -- PC を再起動し、インストールを最初からやり直してください。 場合によっては、それだけで問題が解決する場合もあります。 +- Reboot the PC and start the installation all over again. Sometimes that's enough to fix the problem. -### エラー 1602: ユーザーによってインストールがキャンセルされた時 {#error-1602} +### Error 1602: Canceled by user {#error-1602} -このエラーコードが表示された場合は、何らかの方法でインストールプロセスを手動で中断した可能性があります。 できることは以下のとおりです: +If you got this error code, chances are you have interrupted the installation process manually in one way or another. What you can do is: -- インストール中、AdGuardインストーラーウィンドウを閉じないでください。 インストールが完了すると、ウィンドウは自動的に閉じます。 +- Don't close the installer window. When the installation is complete, it will close automatically. -- インストール中にダイアログウィンドウが表示された場合は、「はい」を押して、インストーラーに必要な権限を付与するようにしてください。 「いいえ」をクリックすると、インストールがキャンセルされます。 +- If a dialogue window pops up during the installation, hit "Yes" to grant the installer the required permissions. Clicking "No" will cancel the installation. -- インストール中は、他のプロセスを起動しないようにしてください。 +- Don't start other processes while the installation process is going on. -### エラー 1603: インストール中に致命的なエラーが発生しました {#error-1603} +### Error 1603: Fatal error during installation {#error-1603} -このエラーは怖く聞こえますが、実際のところ、 原因がさまざまの一般的なエラーであり、原因のいくつかは簡単に修正できます。 以下の解決策を試してみてください: +The error sounds scarier than it actually is. In reality, this is a rather generic error that can have many different causes, and some of them are easily fixed. Try the following solutions: -- *Win* キーを押し、「*コマンド プロンプト*」を検索して実行してください。 そこで、 `sfc /scannow` と入力し、 *Enter*キーを押してください。 +- Press the *Win* key, search for *Command Prompt* and run it. There, type in `sfc /scannow` and press *Enter*. -- 別のインストールフォルダを選択してください。 現在のインストールフォルダに何らかのアクセス制限がある可能性があります。 また、外付けドライブや仮想ドライブなどを選択しないようにしてください。 +- Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. -- [専用のアンインストールツール](../../installation#advanced)を使用して AdGuard をアンインストールし、その後にインストールを繰り返してください。 +- Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. -- Microsoftインストーラーサービスを開始して再登録してください。 これを行うには、多少のステップを踏む必要があります: +- Start and re-register Microsoft Installer service. It requires some work. - 1) *Win + R* を押して、 **services.msc** と入力します。 2) リストから *Windows インストーラー* を探し、ダブルクリックします。 3) *サービスステータス* の下の「*開始*」ボタンを押し、「*OK*」を押します。 サービスステータスが**実行中**の場合、まず「*停止*」をクリックし、次に「*開始*」をクリックします。 4) *Win + R* を押し、 ***msiexec /unregister*** と入力し、 *Enter*キーを押します。 5) *Win + R* をもう一度押し、 ***msiexec /regserver*** と入力し、 *Enter*キーを押します。 + 1) Press *Win + R* and enter ***services.msc***. 2) Find in the list and double click *Windows Installer*. 3) Hit *Start* button under *Service status* and hit *OK*. If the service status is **running**, you should click *Stop* first and then hit *Start*. 4) Press *Win + R*, type and enter ***msiexec /unregister*** and hit *Enter*. 5) Press *Win + R* again, type and enter ***msiexec /regserver*** and hit *Enter* -- インストールのためにドライブのフル権限を取得してください。 1603エラーが発生する原因は、ファイルの保存先に対してフルアクセス権限がないことの可能性があります。 結構手間かかりますが、手順は以下のとおりです: +- Acquire full permissions on the drive for installation. It is possible that the error 1603 occurs because you don’t have full permissions on the file location. It's also not as easy as some of the other solutions: - 1) *ファイルエクスプローラー*を開き、インストール先を含むドライブを右クリックして 「*プロパティ*」を選択します。 2) *セキュリティ*タブに移動して「*編集*」をクリックします。 3) *SYSTEM*（システム）を 1 回クリックし、「*SYSTEMのアクセス許可*」にあるすべての項目の *許可* ボックスがオンになっていることを確認します (チェック可能な場合)。 「*管理者*」に対しても同じチェックを入れます。 4) *OK* をクリックして *プロパティ* に戻ります。 次に「*詳細設定*」をクリックします。 5) 「*権限の変更*」をクリックします。 6) *権限* タブで、「*管理者*」をダブルクリックします。 7) *適用先* フィールドに対して「*このフォルダー、サブフォルダー、およびファイル*」を選択し、*基本権限*のすべてにチェックを入れます。 その後、 *OK* を押します。 8) *SYSTEM*に対してもステップ7と同じことをします。 9) *OK* を最後までクリックし続けます。 AdGuard を再度インストールしてみてください。 + 1) Open *File Explorer*, right-click the drive containing the installation location and select *Properties*. 2) Go to *Security* tab and click *Edit*. 3) Single-click *SYSTEM* and ensure that the *Allow* box of every item in *Permissions for SYSTEM* is checked (if it is checkable). Do the same check for *Administrators*. 4) Click *OK* to go back to *Properties* dialog. Then click *Advanced*. 5) Click *Change Permissions*. 6) On *Permissions* tab, double-click *Administrators*. 7) Select *This folder, subfolders and files* for *Applies to* field and check all the available *Basic permissions*. After that, hit *OK*. 8) Do the same operation above (from item 7) for *SYSTEM*. 9) Click *OK* all the way out. Try installing AdGuard again. -### エラー 1618: 他のインストールがすでに進行中です {#error-1618} +### Error 1618: Another installation is already in progress {#error-1618} -このエラーは、AdGuard インストーラーの複数のインスタンスが同時に起動された場合に発生します。 このエラーが表示された場合の対処方法は以下のとおりです: +This error occurs when there are several instances of AdGuard installer launched at the same time. What to do if you get this error: -- PC を再起動し、インストーラーを再び起動してください。 コンピュータを再起動すると、インストーラーのすべてのコピーを含め、進行中プロセスがすべて停止します。 +- Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- インストーラーがすぐに起動しなくても、何度もクリックしないようにしてください。 インストーラーのUIが表示されるまで数秒かかることがあります。 +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. -### エラー 1638: この製品の別バージョンがすでにインストールされています {#error-1638} +### Error 1638: Another version of this product is already installed {#error-1638} -おそらく、すでに AdGuard がインストールされているということです。 +It's very likely that you've already installed AdGuard before. -- お使いのコンピュータに AdGuard がすでにインストールされているかどうかを確認してください。 *Win*キーを押して「**AdGuard**」と入力すれば、コンピューター上に既存のAdGuardアプリがある場合は見つかります。 +- Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- 以前 AdGuard をインストールしたときのファイルが残っているのかもしれません。 [専用のアンインストールツール](../../installation#advanced)を使用して AdGuard をアンインストールし、その後にインストールを繰り返してください。 +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. -### その他のエラー {#other} +### Other errors {#other} -上記に記載されていないエラーが発生した場合、弊社で解決できる可能性があります。 ただし、そのためには、お客様からのログファイルが必要となります。 ログファイルの送信方法は以下のとおりです: +If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- **AdGuard インストールログ**を見つけてアーカイブします。その手順は、 [こちらの記事](../installation-logs)をご覧ください。 +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- **イベント ビューアー**のログを見つけてディスクに保存します。 手順は[こちらの記事](../system-logs)をご覧ください。 +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. -- 前述した2つのステップで作成したすべてのファイルを、AdGuardサポートチーム（**<0>support@adguard.com**）までメールでお送りください。 テクニカルサポート担当者ができるだけ早く返信いたします。 +- Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md index 3b68568f831..eed9e659003 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md @@ -1,79 +1,79 @@ --- -title: 証明書関連の問題 +title: Certificate-related issues sidebar_position: 2 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -HTTPSトラフィックをフィルタリングし、広告やトラッカーを効率的にブロックするために、AdGuardは特別でユニークなルート証明書を生成し、システムストレージにその証明書をインストールします。 （なぜ証明書が必要なのかについて詳しくは、[こちらの記事](/general/https-filtering/what-is-https-filtering)をご覧ください。） +To be able to filter HTTPS-traffic and efficiently block ads and trackers, AdGuard generates a special (and unique) root certificate and installs it into the system storage. You can learn more about why a certificate is required by reading [this article](/general/https-filtering/what-is-https-filtering). -AdGuard証明書がインストールプロセス中にシステム証明書ストレージに追加されると、ブラウザは通常、その証明書を信頼します。 しかし、場合によってはこれだけでは不十分で、警告やエラーに出くわすこともあります。 この現象は、Mozilla Firefox、PaleMoon、WaterfoxなどのFirefoxベースブラウザや、Yandex.Browserでよく起こります。 +Normally browsers trust the AdGuard certificate once it's added to the system certificate storage during the installation process. But in some cases this is not enough and you may come across warnings or errors. This happens most often in Firefox-based browsers like Mozilla Firefox, PaleMoon, Waterfox, etc., or in Yandex.Browser. -## Firefoxベースのブラウザにおける「*潜在的なセキュリティリスク*」エラー +## *Potential Security Risk* error in Firefox-based browsers -![セキュリティリスクエラー](https://cdn.adtidy.org/public/Adguard/kb/en/certificate/cert_error_en.png) +![Security risk error](https://cdn.adtidy.org/public/Adguard/kb/en/certificate/cert_error_en.png) -旧バージョンのFireFoxや、それをベースとしたブラウザは、システムストレージの証明書を信用せず、ローカルストレージの証明書のみを信用します。 バージョン 68 以降、FireFox はシステム証明書を信頼しますが、それでも「接続が信頼されていません」というエラーが発生する可能性があります。 このようなことが起こった場合は、まずはAdGuardの[*ネットワーク*]タブにある*[証明書を再インストールする*]ボタンをクリックしてみてください。 +Old FireFox versions, as well as browsers based on them, do not trust certificates from the system storage, but only those from their local storage. Since v68, FireFox trusts the system certificates, but you still can face the "Connection is untrusted" error. If something like this happens, first try to click the *Reinstall Certificate* button — you will find it in the *Network* tab. -![証明書を再インストール](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/reinstall.jpg) +![Reinstall Certificate](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/reinstall.jpg) -それでも解決しない場合は、AdGuard証明書をFireFoxのストレージに手動で追加する手順に従ってください。 +If that doesn't help, follow the instructions for manually adding the AdGuard certificate to the FireFox storage. -> ※以下の手順はFirefoxブラウザ用です。 他のFirefoxベースのブラウザでは、ボタンやメニューの名前が多少異なる場合があります。 +> This instruction is for Firefox browser. Names of buttons and menu items may differ in other Firefox-based browsers. -1. AdGuard を起動します。 +1. Run AdGuard. -1. [http://local.adguard.org/cert](http://local.adguard.org/cert) にアクセスし、 *ダウンロード* ボタンをクリックします。 ブラウザは **cert.cer** ファイルのダウンロードを開始するはずです。 +1. Go to [http://local.adguard.org/cert](http://local.adguard.org/cert) and click the *Download* button. The browser should start downloading **cert.cer** file. :::note - また、AdGuardアプリの*[設定]→[ネットワーク]→[HTTPSフィルタリング]*からリンクをクリックしてダウンロードページを開くこともできます。 + You can also open the download page by clicking the link via the AdGuard app at *Settings → Network → HTTPS filtering*. ::: - ![証明書の設定](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/link.jpeg) + ![Certificate settings](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/link.jpeg) -1. ブラウザを開き、 *設定*を開きます。 +1. Open your browser and then open *Settings*. -1. *プライバシーとセキュリティ* タブに移動します。 +1. Go to *Privacy & Security* tab. -1. *証明書* まで下にスクロールし、 *証明書を表示* ボタンをクリックします。 +1. Scroll down to *Certificates* and click the *View Certificates* button. - ![証明書ウィンドウを表示](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import1.jpeg) + ![View certificates window](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import1.jpeg) -1. *権限* タブを選択します。 +1. Select *Authorities* tab. -1. 「*インポート...*」をクリックします。 +1. Click *Import...*. - ![証明書設定 - インポート](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import2.jpeg) + ![Certificate settings — import](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import2.jpeg) -1. ダウンロードした **cert.cer** ファイルを参照して、 「*開く*」をクリックします。 +1. Browse the downloaded **cert.cer** file and click *Open*. -1. *[この認証局によるウェブサイトの識別を信頼する*] ボックスにチェックを入れ、 *[OK]*をクリックします。 +1. Check the *Trust this CA to identify websites* box and then click *OK*. - ![証明書設定 - チェックボックス](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/cert_checkbox.jpg) + ![Certificate settings — checkbox](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/cert_checkbox.jpg) -これで、AdGuard証明書のインストールは完了です。 ブラウザを再起動すればエラーは解消するはずです。 +You've successfully installed AdGuard certificate. Restart the browser and the error should go away. -## Yandex.Browser証明書の警告 +## Yandex.Browser certificate warning -AdGuard for Windows と Yandex.Browserの両方のユーザーであれば、この警告に出くわしたことがあるかもしれません: +If you are a user of both AdGuard for Windows and Yandex.Browser you may have come across this warning: -![Yandex 証明書の警告](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/yandex-cert.png) +![Yandex certificate warning](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/yandex-cert.png) -### なぜこのようなことが起こるのか +### Why is this happening -AdGuardとYandexの両社は、インターネット上のユーザーのセキュリティを非常に重視しています。 現在の Yandex のポリシーでは、ブラウザで認識されない証明書についてはユーザーに警告することになっています。 これは根拠のない話ではありません。悪意のあるアプリが独自の証明書を挿入し、それを使ってシステムに危害を加えたり、個人情報を盗んだりすることがあるからです。 +Both AdGuard and Yandex take users' security on the Internet very seriously. Current Yandex policy is to warn their users about any certificate that is not recognized by the browser. This is not unsubstantiated, because sometimes malicious apps can inject their own certificates and use this to harm the system and steal private data. -しかし、AdGuardもその証明書を信頼できるものに追加します。 これにより、例の警告メッセージが表示されます。 +However, AdGuard also adds its certificate to the trusted ones. This leads to the warning message you have encountered. -### この問題を解決する方法 +### How to solve the problem -最も簡単な方法は、「**サイトへ移動」**ボタンをクリックすることです。 これによりYandex.Browserは、しばらくの間はAdGuard証明書を信頼できるものとして記憶するようになります。 通常、例のメッセージを見ることはなくなりますが、何らかの理由で時折表示される可能性はゼロではありません。 このような場合は、同じボタンをもう一度押すだけで解決します *(※AdGuard 証明書に関する警告であることにご注意ください。)* +The easiest way is to click the **Go to site** button. This will tell Yandex.Browser to remember AdGuard certificate as a trusted one, at least for a while. Normally, you won't have to see this message anymore, but it is not beyond the realm of possibility for it to appear occasionally, for whatever reasons. In such cases, simply press the same button again *(make sure it is AdGuard's certificate!)*. -AdGuardのHTTPSフィルタリングを無効にした場合も、Yandex.Browserがこのメッセージを再び表示することはなくなりますが、それには大きな代償が伴います。HTTPSで読み込まれるすべての広告（**Yandex独自の広告**を含む）が、YouTube、Facebook、Instagramなどのウェブサイトで表示されるようになってしまいます。 広告ブロックの質を高く保ちたいのであれば、HTTPSフィルタリングをオフにする方法はお勧めできません。 +Disabling the HTTPS filtering in AdGuard will also prevent Yandex.Browser from showing this message again, but it comes with a big price: all ads that are loaded by HTTPS (including **Yandex's own ads**) will show up — on such websites as YouTube, Facebook, Instagram, and many more. We strongly advise against it if you want to keep the quality of ad blocking high. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index 3bc237fa72f..e5b7675a1f0 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -1,48 +1,48 @@ --- -title: DNSリークの可能性 +title: Possible DNS leaks sidebar_position: 9 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -AdGuard for Windowsでは、クエリを解決するために、システムDNSサーバーの代わりにDNSサーバーアドレスを指定することができます。（システムDNSサーバーは、システム設定で上書きされていない場合、インターネットプロバイダによって提供されます。） デフォルトでないDNSサーバーを使うことで、インターンシッププロバイダーの傍受からDNSトラフィックを守ることができます。 さらに、暗号化および/またはフィルタリングDNSサーバーを選択することで、悪質業者や迷惑な広告からの保護機能を得ることができます。 +AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -多くの AdGuard for Windows ユーザーは、DNS保護機能を高く評価してくれています。 しかし、次のような問題が発生していることもあります。https://ipleak.net/ のようなウェブサイトをチェックすると、リクエストは選択したDNSサーバーではなく、デフォルトのDNSサーバーによって処理されていることがわかります。 本記事では、なぜこのようなことが起こるのか、またそれを回避する方法を説明します。 +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. -## bootstrap DNSアドレス +## Bootstrap DNS address -DNS サーバーのアドレスは、IP またはドメイン名として記述できます。 IPアドレスの場合、AdGuardはDNS保護モジュールで指定されたサーバーにDNSリクエストを直接転送しますので、問題はありません。 しかし、DoTやDoHのような暗号化されたDNSサーバーアドレスは、ドメイン名として記述されることがほとんどです。 この場合、最初に暗号化されたDNSサーバーアドレスを解決するために、AdGuardはデフォルトでシステムDNSサーバーにDNSクエリを送信します。 この接続を、チェックサービスがリークと認識してしまうものです。 +The DNS server addresses could be written as IPs or as domain names. In the case of IP addresses there are no difficulties: AdGuard forwards the DNS request directly to the server specified in the DNS protection module. However, encrypted DNS server addresses, like DoT or DoH, are most often written as domain names. In this case, to first resolve the encrypted DNS server address, AdGuard sends a DNS query to the bootstrap address, which is by default a system DNS server. This connection is what check services perceive as a leak. -**このリークを解消する方法はこちら:** +**To eliminate this leak:** -- 「*詳細設定*」へ移動します。 -- 「*カスタムbootstrapアドレスの一覧*」セクションまでスクロールダウンします。 -- IPアドレス形式でカスタムブートストラップアドレスを入力してください（[こちらの既知のDNSプロバイダリスト](https://adguard-dns.io/kb/general/dns-providers/)を使用できます）。 -- 「*保存*」をクリックします。 +- go to the *Advanced settings* +- scroll down to the *List of custom bootstrap addresses* section +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- click *Save* -## フォールバックDNSサーバー +## Fallback DNS server -インターネット接続が弱い、デフォルトで設定されているタイムアウトの期限切れ、またはサーバー関連の問題のために、AdGuardが指定されたサーバーに到達できないことがあります。 この場合、デフォルトではシステムDNSサーバーであるフォールバックサーバーに、AdGuardは接続します。 この接続もチェックサービスによってリークとして認識されます。 +It could happen that AdGuard cannot reach the specified server because of a weak internet connection, an expiration of timeout set by default or some server related issues. In this case, it will connect to the fallback server, which is by default a system DNS server. This connection will also be considered by the check service as a leak. -**このリークを解消する方法はこちら:** +**To eliminate this leak:** -- 「*詳細設定*」へ移動します。 -- 「*フォールバックサーバー*」セクションまでスクロールします。 -- 「*カスタムサーバーを使用*」オプションをチェックします。 -- 次に、「*カスタムフォールバックサーバーのリスト*」セクションを見つけて、カスタムフォールバックサーバーを1行に1つずつ入力します。 +- go to the *Advanced settings* +- scroll down to the *Fallback servers* section +- check the *Use custom servers* option +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line -もしくは +or -- 「*詳細設定*」へ移動します。 -- 「*フォールバックサーバー*」セクションまでスクロールします。 -- 「*フォールバックサーバーを使用しない*」オプションをチェックします。 +- go to the *Advanced settings* +- scroll down to the *Fallback servers* section +- check the *Don’t use fallback servers* option -もしくは +or -- 「*詳細設定*」へ移動します。 -- 「*DNSサーバーのタイムアウト期間*」セクションまでスクロールします。 -- 任意の大きな数値を入力します。 +- go to the *Advanced settings* +- scroll down to the *DNS server timeout period* section +- enter an arbitrary large number diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 379e2aa6283..a27331d5f89 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -1,44 +1,44 @@ --- -title: ダンプファイルを作成する方法 +title: How to create a dump file sidebar_position: 8 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: :::note -※ダンプファイルで提供されたデータおよびファイルは、[AdGuardのプライバシーポリシーに従って](https://adguard.com/en/privacy.html)処理されます。 +Data and/or files provided in dump files are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -AdGuardの使用中にユーザーが遭遇する可能性のある問題の原因を診断するために、サポートチームはプロセスのダンプファイルを必要とする場合があります。 ダンプファイルは、開発者が特定の期間内に、アプリで実行されたプロセスを確認するのに役立ちます。 以下では、パソコンでダンプファイルの収集方法について説明します。 +To diagnose the reasons for potential problems that users might encounter while using AdGuard, the support team might need the process dump file. The dump file helps developers to see the processes that were executed in the application over a given period of time. Below you can check on the instructions of how to collect the dump file on your PC. -1. **Ctrl + Shift + Esc** キーを押し、**タスクマネージャー**をクリックします。 +1. Press **Ctrl + Shift + Esc** and click **Task Manager** -1. 上部メニューバーで「**詳細**」を選択します。 +1. In the upper menu bar select **Details** - ![タスクマネージャーの詳細](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/details_en.png) + ![Task Manager details](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/details_en.png) -1. ダンプファイル作成したいプロセスを右クリックします (たとえば、サポートチームから `Adguard.exe` のダンプを作成するように指示される場合があります)。 +1. Right-click the process that you want to create the dump file for (for example, the support team may ask you to create a dump for `Adguard.exe`) -1. ドロップダウンメニューで、 「**ダンプファイルの作成**」をクリックします。 +1. In the drop-down menu click **Create dump file** -1. ダンプファイルの作成完了です。 +1. The file was created successfully! - ![ダンプファイルの作成](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/create_dump_file_en.png) + ![Create dump file](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/create_dump_file_en.png) -ダンプファイルを作成したら、ファイルの場所に移動してください。 ダンプファイルを作成した直後に、そのファイルを含むフォルダを開くよう通知が表示されるはずです。 それ以外の場合は、 ファイルは **%tmp%** フォルダ内で見つけることができます。 作成されたダンプファイル（`.DMP`）は、前のステップで選択したプロセス名と同じ名前です。 ファイルはかなり大きいので、サポートに送る前にアーカイブに圧縮してください。 +After you’ve created the dump file, please navigate to the file location. You should be prompted to open the folder containing the dump file right after its creation. Otherwise, you will be able to find it inside the **%tmp%** folder. The created dump file (`.DMP`) has the same name as the name of the process you chose in the previous steps. The file is quite large, so please compress it into an archive before sending to support. :::note -AdGuard for Windows には、 `Adguard.exe` と `AdguardSvc.exe` の 2 つの実行プロセスがあります。 したがって、プロセスごとに個別のダンプファイルを作成する必要があります。 +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: -![AdGuardプロセス](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) +![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -ダンプファイルをサポートチームにお送りいただく際には、AdGuardアプリのログも添付してください。 ログファイルを取得する手順は[こちら](../adguard-logs)で確認できます。 +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 6d357b48069..aa0b9ca203e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -1,30 +1,30 @@ --- -title: AdGuard のインストールログを収集する方法 +title: How to collect AdGuard installation logs sidebar_position: 4 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: :::note -※システムログで提供されたデータおよびファイルは、[AdGuardのプライバシーポリシーに従って](https://adguard.com/en/privacy.html)処理されます。 +Data and/or files provided in system logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -AdGuard のインストール中に何らかの問題が発生した場合、サポートチームはAdGuardのインストールログを収集し、送信するよう求めることがあります。 その方法は以下の通りです: +If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. スタート メニューで *実行* コマンドを選択するか、キーボードで *Win + R* を押します。 +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. -1. *%tmp%* と入力し、 *OK* をクリックします。 +1. Type in *%tmp%* and click *OK*. - ![一時フォルダを開く *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/install-logs-1.png) + ![Open temp folder *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/install-logs-1.png) -1. 開いたフォルダで「`Adguard`」で始まるすべてのファイルを選択し、アーカイブに追加します（WinRARまたはその他のアーカイブソフトウェアを使用）。 +1. In the opened folder select all files starting with `Adguard` and add them to archive (using WinRAR or any other archiving software). - ![AdGuardインストールログファイル *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/install-logs-2.png) + ![AdGuard installation log files *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/install-logs-2.png) -1. このアーカイブをAdGuardテクニカルサポート（**support@adguard.com**）に送信してください。 +1. Send this archive to AdGuard tech support at **support@adguard.com**. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/known-issues.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/known-issues.md index 104a3e7e1bd..85da7706372 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/known-issues.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/known-issues.md @@ -1,20 +1,20 @@ --- -title: AdGuard for Windows の既知の問題 +title: Known issues of AdGuard for Windows sidebar_position: 10 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -## AdGuard for Windows と AdGuard VPN for Windows の互換性問題 +## AdGuard for Windows and AdGuard VPN for Windows compatibility issues -AdGuard for Windows と AdGuard VPN for Windows をインストールすると、何もしなくても連携して動作し始めます。 ただし、一部のデフォルト設定を変更すると、両アプリを同時に実行したときにアプリが正しく動作しなくなる可能性があります。 +Once you install AdGuard for Windows and AdGuard VPN for Windows, they just start working together without any effort on your part. However, changing some of their default settings may cause the apps to work incorrectly when they run at the same time. -AdGuard for Windows には、2 つの特殊設定があります: *リダイレクト・ドライバ・モードを使用する* 」と「*plocalhostをフィルタリングする*」です。 デフォルトでは、1つ目は無効、2つ目は有効になっています。 デバイスで AdGuard 広告ブロッカーと AdGuard VPN の両方が有効になっている場合、この二つの設定のいずれかを変更すると、必然的に AdGuard のフィルタリングが中断されてしまいます。 +There are two specific settings in AdGuard for Windows: *Use redirect driver mode* and *Filter localhost*. By default, the first is disabled, and the second is enabled. Changing any of these settings will inevitably disrupt AdGuard's filtering if both AdGuard Ad Blocker and AdGuard VPN are enabled on your device. -これらの設定を変更する必要があるのは、AdGuard 広告ブロッカーと、ウイルス対策、VPN、ネットワークフィルタなどのネットワークレベル系アプリの同時操作に関連する問題を解決する場合のみです。 上記の設定のデフォルト状態を変更する必要があり、AdGuard 広告ブロッカーと AdGuard VPN を同時に正しく動作させたい状況に遭遇した場合は、 [GitHub で問題を作成](https://github.com/AdguardTeam/AdguardForWindows/issues/new/choose)してください。専用的にサポートさせていただきます。 +Changing these settings is only necessary to resolve issues related to the simultaneous operation of AdGuard Ad Blocker and network-level apps such as antiviruses, VPNs, and network filters. If you come across a situation where you need to change the default state of the above settings and still want AdGuard Ad Blocker and AdGuard VPN to work simultaneously and correctly — [create an issue on GitHub](https://github.com/AdguardTeam/AdguardForWindows/issues/new/choose) so we can help you personally. -現在、アプリの併用に関する上記の制限を克服するために取り組んでおります。 +We are currently working on overcoming the above-listed limitations of the simultaneous work of our apps. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index b6d2fbf8606..3506bb29250 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -1,236 +1,236 @@ --- -title: 詳細設定（旧「ローレベル設定」）ガイド +title: Advanced (low-level) Settings guide sidebar_position: 7 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -（以前は旧名「ローレベル設定」として知られていた）詳細設定には、ほとんどの場合、一般ユーザーの知識を超え、日常的な使用では必要ないオプションが含まれています。 AdGuard for Windows は、これらの機能を変更することなく動作するように設計されていますが、一部のコーナーケースや一般的でない問題を解決する際に役立つ追加機能が詳細設定にあります。 +Previously known as low-level settings, Advanced Settings mostly contain options that go beyond the average user competence and aren't applied in everyday use. AdGuard for Windows is designed to work without ever having to change any of them, but they will provide additional features in some corner cases or when solving an uncommon problem. :::caution -*詳細設定*を考えずに変更することは AdGuard のパフォーマンスの悪化やインターネット接続の切断、もしくはあなたのセキュリティやプライバシーを侵害してしまう可能性があります。 このセクションで何かを変更するのは、あなたが何をしているのか自信がある場合、またはサポートチームから依頼された場合のみとすることをお勧めします。 +Mindlessly changing *Advanced Settings* can potentially cause problems with the performance of AdGuard, may break the Internet connection or compromise your security and privacy. You should only make changes to these settings if you are sure of what you are doing or if our support team has asked you to do so. ::: -## 詳細設定にアクセスする方法 +## How to reach Advanced Settings -*詳細設定*に移動するには、メインウィンドウで⚙️*「設定」→「一般設定」を*クリックし、「*詳細設定*」までスクロールダウンします。 または、トレイメニューで*「詳細設定」→「詳細設定...」* を選択します。 +To go to *Advanced settings*, in the main windows click *Settings → General Settings* and scroll down to *Advanced Settings*. Alternatively, select *Advanced → Advanced settings...* in the tray menu. -## 詳細設定 +## Advanced Settings -詳細設定を開くと、以下のオプションが表示されます: +Once you open Advanced Settings, you will be presented with the following options: -### TCP Fast Openをブロックする +### Block TCP Fast Open -有効にすると、AdGuardはEdgeブラウザのTCP Fast Openをブロックします。 この設定の変更を適用するには、ブラウザを再起動する必要があります。 +If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Encrypted Client Hello を使用する +### Use Encrypted ClientHello -暗号化されたインターネット接続には、暗号化されていない部分があります。 その部分とは、接続先のサーバー名を含む最初の通信パケットです。 Encrypted Client Hello 技術は、この問題を解決し、この暗号化されていない部分を暗号化してくれます。 この機能を利用するには、「*Encrypted Client Hello を使用する*」オプションを有効にします。 このオプションは、ローカル DNS プロキシを使用して、ドメインの ECH 構成を検索します。 見つかった場合、ClientHello パケットは暗号化されます。 +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. -### Webサイトの証明書の透明性を確認する +### Check websites' certificate transparency -Chrome Certificate Transparency Policy（証明書透過性ポリシー）に基づき、ドメインのすべての証明書の信頼性を検証します。 証明書が Chrome Certificate Transparency Policy（Chrome 証明書の透明性に関するポリシー）に準拠していない場合、AdGuard は Web サイトをフィルタリングしません。 そして Chrome はそれをブロックします。 +Chrome Certificate Transparency Policy（証明書透過性ポリシー）に基づき、ドメインのすべての証明書の信頼性を検証します。 If the certificate does not comply with the Chrome Certificate Transparency Policy, AdGuard will not filter the website. Chrome, in turn, will block it. -### SSL/TLS証明書の失効チェックを有効にする +### Enable SSL/TLS certificate revocation checks -このオプションを有効にすると、非同期OCSPチェックが実行され、ウェブサイトのSSL/TLS証明書が失効しているかどうかがチェックされます。 +Once enabled, this option runs asynchronous OCSP checks to check whether the website’s SSL/TLS certificate is revoked. -OCSP チェックが最小タイムアウト内に完了すると、AdGuard は結果を直ちに適用します（証明書が取り消されている場合は接続をブロックし、証明書が有効な場合は接続を確立します）。 +If the OCSP check completes within the minimum timeout, AdGuard will immediately apply the result: block the connection if the certificate is revoked or establish a connection if the certificate is valid. -検証に時間がかかりすぎる場合、AdGuardは接続を確立し、バックグラウンドでチェックを続けます。 証明書が失効している場合は、そのドメインへの現在の接続および今後の接続はブロックされるようになります。 +If the verification takes too long, AdGuard will establish a connection and continue checking in the background. If the certificate is revoked, current and future connections to the domain will be blocked. -### 設定で「AdGuard VPN」項目を表示する +### Show AdGuard VPN in Settings -このオプションを有効にすると、[設定] に [AdGuard VPN] タブが表示され、そのアプリやホームページを簡単に開くことができます。 +Enabling this option allows you to display the AdGuard VPN tab in Settings for easy opening of the app and the product's website. -### フルパスを入力してアプリをフィルタリングから除外する +### Exclude app from filtering by entering the full path -AdGuardが特定のアプリをフィルタリングしないようにしたい場合は、そのアプリへのフルパスを指定すると、そのアプリはフィルタリングから除外されます。 異なるパスはセミコロンで区切ります。 +If you want AdGuard not to filter any specific application, specify the full path to them and the apps will be excluded from filtering. Separate different paths by semicolons. -### AdGuardのポップアップ通知を有効にする +### Enable AdGuard pop-up notifications -この機能を有効にすると、AdGuardのポップアップ通知が表示されるようになります。 あまり頻繁には表示されず、重要な情報のみが含まれます。 トレイ メニューを使用して、最後のポップアップ通知を呼び出すこともできます。 +Enable this feature to see AdGuard pop-up notifications. They do not appear too often and contain only important information. You can also use the tray menu to recall the last pop-up notification. -### フィルタ・サブスクリプションURLを自動的に傍受する +### Automatically intercept filter subscription URLs -AdGuard に購読 URL (例: `abp:subscribe` など) を自動的に傍受させ、カスタムフィルタインストールウィンドウを開くようにさせたい場合は、この機能を有効にします。 +Enable this feature if you want AdGuard to automatically intercept filter subscription URLs (i.e. `abp:subscribe` and alike) and to open a custom filter installation dialog. -### HTTP/3 をフィルタリングする +### Filter HTTP/3 -このオプションを有効にすると、AdGuard は、他のリクエストタイプに加えて、HTTP/3 で送信されたリクエストもフィルタリングします。 +If this option is enabled, AdGuard will filter requests sent over HTTP/3 in addition to other request types. -### リダイレクト・ドライバ・モードを使用する +### Use redirect driver mode -このオプションを有効にすると、AdGuard はすべてのトラフィックを傍受し、さらにフィルタリングするためにローカルプロキシサーバーにリダイレクトします。 +If this option is enabled, AdGuard intercepts all the traffic and redirects it to the local proxy server for further filtering. -それ以外の場合、AdGuard はリダイレクトせずにすべてのトラフィックを即座にフィルタリングします。 この場合、システムは AdGuard をインターネットに接続する唯一のアプリと見なします (他のアプリケーションは AdGuard を経由してルーティングされます)。 欠点として、システムのファイアウォールの効果が低下することがあります。 利点は、このアプローチの方が少し速く動作することです。 +Otherwise, AdGuard will filter all the traffic on the fly, without redirection. In this case, the system will consider AdGuard to be the sole application that connects to the Internet (other applications are routed through it). The downside is that it will make the system Firewall less effective. The upside is that this approach works a little bit faster. -### システム起動時にメインウィンドウを開く +### Open main window at system start-up -このオプションを有効にすると、システムの起動後に AdGuard のメインウィンドウが開きます。 実際のフィルタリングサービスが起動するかどうかには影響しないことにご注意ください。その設定は*「設定」→「一般設定*」にあります。 +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* -### システム起動時にフィルタリングを有効にする +### Enable filtering at system start-up -v7.12以降、デフォルトでは、[システム起動時にAdGuardを起動]オプションが無効になっている場合、AdGuardのサービスはOS起動後にトラフィックをフィルタリングしません。 つまり、AdGuard のサービスは「アイドル」モードで開始されます。 このオプションを有効にすると、アプリが起動されていない場合でも AdGuard がトラフィックをフィルタリングします。 +Starting from v7.12, by default, AdGuard's service does not filter traffic after OS startup if the option Launch AdGuard at system start-up is disabled. In other words, the AdGuard's service is started in “idle” mode. Enable this option to make AdGuard filter traffic even if the app is not launched. :::note -v7.12 以前では、AdGuard サービスはデフォルトでフィルタリングモードで開始されていました ( *システム起動時に AdGuard を起動* が無効になっている場合でも)。 以前の動作に満足していた場合は、このオプションを有効にしてください。 +Before v7.12, the AdGuard service started in filtering mode by default (even if the *Launch AdGuard at system start-up* was disabled). If you were satisfied with the old behavior, enable this option. ::: -### localhostをフィルタリングする +### Filter localhost -AdGuard がループバック接続をフィルタリングするようにしたい場合は、チェックボックスをオンにします。 AdGuard VPN がインストールされている場合はこのオプションが常にオンになります。インストールされいない場合は機能しないからです。 +If you want AdGuard to filter loopback connections, check the box. This option will always be on if you have AdGuard VPN installed, because otherwise it won't be able to work. -### 指定のIP範囲をフィルタリングから除外する +### Exclude specified IP ranges from filtering -AdGuardに特定のサブネットをフィルタリングさせたくない場合は、この機能を有効にし、下の「**フィルタリングから除外するIP範囲**」セクションで、CIDR表記（例：98.51.100.14/24）でIP範囲を指定します。 +If you don't want AdGuard to filter particular subnets, enable this feature and specify the IP ranges in the CIDR notation (e.g. 98.51.100.14/24) in the **IP ranges excluded from filtering** section below. -### HAR writing を有効にする +### Enable HAR writing -このオプションは、**デバッグ目的でのみ**有効にしてください。 チェックボックスをオンにすると、AdGuard は、フィルタされたすべての HTTP リクエストに関する情報を含む HAR 1.2 形式のファイルを作成します。 このファイルは Fiddler アプリで分析できます。 ※このオプションがオンの時は、ウェブブラウジングの速度が著しく低下する可能性がありますのでご注意ください。 +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. -### プレーンHTTPリクエストに余分なスペースを追加する +### Add an extra space to the plain HTTP request -HTTPメソッドとURLの間に余分なスペースを追加し、「Host: 」欄の後のスペースを削除します。そうすることでdeep packet inspection（DPI）を回避します。 例えば、以下のリクエスト +Adds extra space between the HTTP method and the URL and removes space after the "Host:" field to avoid deep packet inspection. For instance, the request `GET /foo/bar/ HTTP/1.1 Host: example.org` -は、以下に変換されます: +will be converted to `GET /foo/bar/ HTTP/1.1 Host: example.org` -このオプションは、「*DPIから保護する*」というステルスモード機能が有効になっている場合にのみ適用されます。 +This option is only applied when the *Protect from DPI* Stealth mode option is enabled. -### 最初のTLSパケットのフラグメントサイズを調整する +### Adjust size of fragmentation of initial TLS packet -このオプションは、TCPパケットの断片化のサイズを指定し、ディープ・パケット・インスペクション（DPI）を回避するのに役立ちます。 このオプションは、保護された（HTTPS）トラフィックにのみ影響します。 +Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -このオプションを有効にすると、AdGuardは最初のTLSパケット(ClientHelloパケット)を2つの部分に分割います。最初の部分は指定された長さで、2番目の部分は最初のTLSパケット全体の長さまでの残りの内容です。 +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. -有効な値は 1～1500 です。 無効なサイズを指定すると、システムによって選択された値が使用されます。 このオプションは、「*DPIから保護する*」というステルスモード機能が有効になっている場合にのみ適用されます。 +Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. -### Plain HTTP request fragment size（プレーンHTTPリクエストフラグメントサイズ） +### Plain HTTP request fragment size -HTTPリクエストフラグメンテーションのサイズを調整します。 このオプションは、プレーンHTTPトラフィックにのみ影響します。 このオプションを有効にすると、AdGuardは最初のパケットを2つの部分に分割します。最初の部分は指定された長さで、2番目の部分は最初のパケット全体の長さまでの残りの内容です。 +HTTPリクエストフラグメンテーションのサイズを調整します。 This option only affects plain HTTP traffic. If this option is enabled, AdGuard splits the initial packet into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole original packet. -有効な値は 1～1500 です。 無効なサイズを指定すると、システムによって選択された値が使用されます。 このオプションは、「*DPIから保護する*」というステルスモード機能が有効になっている場合にのみ適用されます。 +Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. -### QUICを表示する +### Show QUIC -フィルタリングログにQUICプロトコルレコードの表示を許可します。 ブロックされたリクエストのみ対象。 +Allows displaying the QUIC protocol records in the filtering log. For blocked requests only. -### TCP keepalive を有効にする +### Enable TCP keepalive -コネクションがアクティブであることを確認するためとNATタイムアウトを更新するために、アイドル状態のコネクションに定期的にTCPパケットを送信します。 このオプションは、一部のISPが使用する厳格なネットワークアドレス変換（NAT）設定をバイパスするのに便利です。 +Periodically sends TCP packets over idle connection to ensure it is alive and to renew NAT timeouts. This option can be useful to bypass the strict network address translation (NAT) settings that some ISPs use. ### TCP keepalive interval -ここで、キープアライブ（keepalive）プローブを送信する前のアイドル時間を秒単位で指定できます。 「0」を指定すると、システムによって選択された値が使用されます。 +Here you can specify an idle time period, in seconds, before sending a keepalive probe. 「0」を指定すると、システムによって選択された値が使用されます。 :::note -※この設定は、「*TCP keepalive を有効にする*」オプションが有効になっている場合にのみ機能すします。 +This setting only works when the *Enable TCP keepalive* option is enabled. ::: ### TCP keepalive timeout -応答がないpeerに再度keepaliveプローブを送信するまでの時間 (秒単位)を指定できます。 「0」を指定すると、システムによって選択された値が使用されます。 +Here you can specify time in seconds before sending another keepalive probe to an unresponsive peer. 「0」を指定すると、システムによって選択された値が使用されます。 :::note -※この設定は、「*TCP keepalive を有効にする*」オプションが有効になっている場合にのみ機能すします。 +This setting only works when the *Enable TCP keepalive* option is enabled. ::: -### Javaをブロックする +### Block Java -一部のウェブサイトやウェブサービスは、現在もJavaプラグインをサポートしています。 Javaプラグインの基礎となるAPIには、深刻なセキュリティ上の脆弱性があります。 セキュリティのため、このようなプラグインを無効にすることができます。 ※「*Javaをブロックする*」オプションを使っても、JavaScriptは有効のままです。 +Some websites and web services still support Java Plug-Ins. The API that serves as the basis for Java plug-ins has serious security vulnerabilities. You can disable such plug-ins for security purposes. Nevertheless, even if you decide to use *Block Java* option, JavaScript will still be enabled. -### DNSサーバーのタイムアウト期間 +### DNS server timeout period -ここで、AdGuardがフォールバックに頼る前に、選択したDNSサーバーからの応答を待つ時間をミリ秒単位で指定できます。 このフィールドに何も入力しないか、無効な値を入力すると、5000という値が使用されます。 +Here you can specify the time in milliseconds that AdGuard will wait for the response from the selected DNS server before resorting to fallback. If you don’t fill in this field or enter an invalid value, the value of 5000 will be used. -### DNS-over-HTTPS に HTTP/3 を使用する +### Use HTTP/3 for DNS-over-HTTPS -選択したアップストリームがこのプロトコルをサポートしている場合、接続を高速化するためにDNS-over-HTTPSアップストリームでHTTP/3を有効にします。 つまり、このオプションを有効にしても、すべてのDNSリクエストがHTTP/3経由で送信されることが保証されるわけではありません。 +Enables HTTP/3 for DNS-over-HTTPS upstreams to accelerate connection if the selected upstream supports this protocol. This means that enabling this option does not guarantee that all DNS requests will be sent via HTTP/3. -### フォールバックDNSアップストリームを使用する +### Use fallback DNS upstreams -指定のアップストリームへのDNSリクエストがすべて失敗した場合、通常のクエリはフォールバックアップストリームにリダイレクトされます。 +Normal queries will be redirected to the fallback upstream if all DNS requests to the selected upstreams fail. -### DNSアップストリームを並列に問い合わせる +### Query DNS upstreams in parallel -すべてのアップストリームに並行して問い合わせが行われます。最初の応答が返されます。 DNSクエリは並行して行われるため、この機能を有効にするとインターネット速度が向上します。 +All upstreams will be queried in parallel and the first response is returned. Since DNS queries are made in parallel, enabling this feature increases the Internet speed. -### 失敗したDNSクエリにいつも応答する +### Always respond to failed DNS queries -転送(forward)された各アップストリームおよびフォールバックドメインで アドレス解決が失敗した場合、DNSリクエストに対する応答は`SERVFAIL`となります。 +If address resolving failed on each of the forwarded upstreams, as well as on the fallback domains, then the response to the DNS request will be `SERVFAIL`. -### セキュアなDNSリクエストのフィルタリングを有効にする +### Enable filtering of secure DNS requests -AdGuardは、プレーンDNSリクエストに加え、セキュアDNSリクエストもローカルDNSプロキシにリダイレクトします。 +AdGuard will redirect secure DNS requests to the local DNS proxy, in addition to plain DNS requests. -### hostsルール用ブロックモード +### Blocking mode for hosts rules -ここでは、[hosts ルールの構文に基づいて](https://adguard-dns.io/kb/general/dns-filtering-syntax/#etc-hosts-syntax)、AdGuard が DNS ルールでブロックされたドメインに応答する方法を選択できます。 +Here you can select the way AdGuard will respond to domains blocked by DNS rules based on [hosts rule syntax](https://adguard-dns.io/kb/general/dns-filtering-syntax/#etc-hosts-syntax). -- 「拒否されました」（Refused）エラーで返答する -- 「NxDomain」エラーで返答する -- カスタムIPアドレスで返答する +- Reply with “Refused” error +- Reply with “NxDomain” error +- Reply with a custom IP address -### adblock-styleルール用ブロックモード +### Blocking mode for adblock-style rules -ここでは、[adblock-styleの構文に基づいて](https://adguard-dns.io/kb/general/dns-filtering-syntax/#adblock-style-syntax)、AdGuard が DNS ルールでブロックされたドメインに応答する方法を選択できます。 +Here you can select the way AdGuard will respond to domains blocked by DNS rules based on [adblock-style syntax](https://adguard-dns.io/kb/general/dns-filtering-syntax/#adblock-style-syntax). -- 「拒否されました」（Refused）エラーで返答する -- 「NxDomain」エラーで返答する -- カスタムIPアドレスで返答する +- Reply with “Refused” error +- Reply with “NxDomain” error +- Reply with a custom IP address -### カスタムIPv4アドレス +### Custom IPv4 address -「adblock-styleルール用ブロックモード」や「hostsルール用ブロックモード」で「カスタムIPアドレス」オプションが選択されている場合、ブロックされた「A」リクエストに対して以下のIPアドレスが返されます。 何も指定しない場合、AdGuardはデフォルトのRefusedエラーで返信します。 +If Custom IP address is selected in Blocking mode for hosts rules or Blocking mode for adblock-style rules, this IP address will be returned in response to blocked A requests. If none are specified, AdGuard will reply with the default Refused error. -### カスタムIPv6アドレス +### Custom IPv6 address -「adblock-styleルール用ブロックモード」や「hostsルール用ブロックモード」で「カスタムIPアドレス」オプションが選択されている場合、ブロックされた「AAAA」リクエストに対して以下のIPアドレスが返されます。 何も指定しない場合、AdGuardはデフォルトの「Refused」エラーで返信します。 +If Custom IP address is selected in Blocking mode for hosts rules or Blocking mode for adblock-style rules, this IP address will be returned in response to blocked AAAA requests. If none are specified, AdGuard will reply with the default "Refused" error. -### フォールバックサーバー +### Fallback servers -ここでは、メインサーバーが次のセクションで指定されたタイムアウト期間内に応答しなかった場合に、DNSリクエストを再ルーティングする代替DNSサーバーを指定することができます。 選択できるオプションは 3 つあります: +Here you can specify an alternate DNS server to which a DNS request will be rerouted if the main server fails to respond within the timeout period specified in the next section. There are three options to choose from: -- フォールバックサーバーを使用しない -- システムデフォルトサーバーを使用する -- カスタムサーバーを使用する +- Don’t use fallback servers; +- Use system default servers; +- Use custom servers. -### ECHをブロックする +### Block ECH -この設定を有効にすると、AdGuardは応答からECH（Encrypted Client Hello）パラメータを削除します。 +If enabled, AdGuard strips Encrypted Client Hello parameters from responses. -### カスタムフォールバックサーバーのリスト +### List of custom fallback servers -AdGuardにカスタムフォールバックサーバーを使用させたい場合は、このセクションに1行に1つずつサーバーを列挙してください。 +If you want AdGuard to use custom fallback servers, list them in this section, one per line. -### カスタムbootstrapアドレスのリスト +### List of custom bootstrap addresses -bootstrap（ブートストラップ）とは、「*DNS通信を保護*」で選択しているセキュアDNSサーバーのIPアドレスを取得するために使用される中間DNSサーバーのことです。 このような「中間点」は、サーバー アドレスを文字で示すプロトコル (DNS-over-TLS など) を使用する場合に必要です。 この場合、ブートストラップは翻訳機として機能し、文字をシステムが理解できる数字に変換してくれます。 +A bootstrap is an intermediate DNS server used to get the IP address of the secure DNS server you chose earlier in *DNS protection*. Such a "middle ground" is needed when using protocols that denote the server address by letters (such as DNS-over-TLS, for example). In this case, the bootstrap acts as a translator, transforming the letters into numbers your system can understand. -デフォルトでは、システムDNSリゾルバが使用され、最初のブートストラップ要求はポート53を通して行われます。 これ以外が必要な場合、ここで、暗号化されたDNSサーバーのアドレスを決定するために使用されるDNSサーバーのIPアドレスを（上から下に）入力することができます。 指定されたIPアドレスは、リストされた順番で適用されます。 無効なアドレスを指定した場合、またはアドレスをまったく指定しなかった場合は、システムIPが使用されます。 +By default, the system DNS resolver is used, and the initial bootstrap request is made through port 53. If this does not suit you, list here the IP addresses of the DNS servers that will be used to determine the address of the encrypted DNS server in the top-to-bottom order. The specified IP addresses will be applied in the order listed. If you specify invalid addresses, or no addresses at all, the system IPs will be used. -### DNS除外リスト +### DNS exclusions -ここリストされているドメインへのすべてのDNSリクエストは、アプリの設定で指定されたDNSサーバーではなく、システムデフォルトDNSサーバーにリダイレクトされます。 また、このようなリクエストにDNSブロックルールは適用されません。 +All DNS requests to domains listed here will be redirected to the system default DNS server instead of the DNS server specified in the app’s settings. Also, DNS blocking rules will not be applied to such requests. -### 指定したWi-Fiネットワーク名（SSID）をDNSフィルタリングの対象から外す +### Exclude specified Wi-Fi networks names (SSIDs) from the DNS filtering -ここで入力されたWi-Fiネットワークに対し「DNS通信を保護」はオフになります。 Wi-Fiネットワーク名（SSID）を1行に1つずつ指定します。 これは、特定のWi-Fiネットワークがすでに AdGuard Home または他のDNS保護システムによって保護されている場合に便利です。 このような場合に、DNSリクエストの重複フィルタリングを避けることができます。 +DNS protection will not include Wi-Fi networks listed in this section. Specify Wi-Fi networks names (SSIDs) one per line. This can be useful if a particular Wi-Fi network is already protected by AdGuard Home or another DNS protection system. In this case, it is superfluous to filter DNS requests again. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index a28b57329e1..dbca398e36f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -1,50 +1,50 @@ --- -title: Windows システムログを収集する方法 +title: How to collect Windows system logs sidebar_position: 5 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: :::note -※システムログで提供されたデータおよびファイルは、[AdGuardのプライバシーポリシーに従って](https://adguard.com/en/privacy.html)処理されます。 +Data and/or files provided in system logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -AdGuard for Windows で発生した問題を分析および診断するために、AdGuardのお客様サポートチームはWindowsのシステムログファイルを必要とする場合があります。 Windows のイベントログには、AdGuard を含む、インストールされたソフトウェアで発生したすべてのエラーの記録が含まれています。 以下は、ログファイルを取得し、必要に応じてAdGuardサポートに送信する方法についての簡単な説明です。 +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. -1. *Win + R* を押します。 +1. Press *Win + R* -1. 表示されたウィンドウに「`eventvwr`」と入力し、「*OK*」をクリックします: +1. In the window that appears type in `eventvwr` and click *OK*: - ![実行ウィンドウ *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_1.png) + ![Run window *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_1.png) -1. イベント ビューアー ウィンドウが表示されます。 +1. Event Viewer window appears as shown in the picture. - ![イベントビューア *border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_2.png) + ![Event viewer *border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_2.png) - 必要なファイルを保存するには、以下の手順を実行します: + To save files that we need, do the following: - - *アプリケーション*を開きます: *イベント ビューアー (ローカル)* → *Windows ログ* → *アプリケーション* + - Open *Application*: *Event Viewer (Local)* → *Windows Logs* → *Application*. - - *アプリケーション* を右クリックし、ドロップダウンメニューで「*すべてのイベントを名前を付けて保存...*」を選択します。 + - Right-click *Application* and in the drop-down menu select *Save All Events As...* - - 保存する名前と保存場所を選択し、「*保存*」をクリックします。 「*以下の言語の情報を表示する*」を選択します。 *英語*の横にあるチェックボックスをオンにする必要があります。 「*OK*」をクリックします。 + - Select a name and where to save, click *Save*. Select *Display information for the following languages*. You need to check the checkbox next to *English*. Click *OK*. - - *システム*を開きます: *イベント ビューアー (ローカル)* → *Windows ログ* → *システム* + - Open *System*: *Event Viewer (Local)* → *Windows Logs* → *System*. - - *システム* を右クリックし、ドロップダウンメニューで「*すべてのイベントを名前を付けて保存...*」を選択します。 + - Right-click *System* and in the drop-down menu select *Save All Events As...* - - 保存先フォルダを選択し、名前を入力して「*保存*」をクリックします。 「*以下の言語の情報を表示する*」を選択します。 *英語*の横にあるチェックボックスにチェックを入れます。 「*OK*」をクリックします。 + - Choose a destination folder, enter the name, click *Save*. Select *Display information for the following languages*. You need to tick the box next to *English*. Click *OK*. -最近保存した 2 つのファイルを **support@adguard.com** まで送信してください。 +Please send the two files that you've recently saved to **support@adguard.com**. :::note -AdGuard は、お客様のプライバシーを保護することに強くコミットしています。 [プライバシーポリシー](https://adguard.com/privacy/windows.html)を厳守し、ユーザーの個人情報を収集することはありません。 サポートチームにログを送信する前に、機密情報や共有したくない情報が含まれていないかどうか、ログファイルを確認してください。 そのような個人情報が含まれている場合は、削除してからログを送信することをお勧めします。 +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index dc6d55056aa..0b36ab2494f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -1,20 +1,20 @@ --- -title: WFPドライバー +title: WFP driver sidebar_position: 1 --- :::info -この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 実際にどのように動作するかを確認するには、[AdGuard アプリをダウンロード](https://agrd.io/download-kb-adblock)してください。 +この記事では、システムレベルでお使いのデバイスを保護する多機能広告ブロッカー、「AdGuard for Windows」について書いています。 To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -ネットワークトラフィックをフィルタリングするために、AdGuardはネットワークドライバを使用します。 TDIドライバーとWFPドライバーという2つがあります。 WFPドライバは一般的に好ましく、すべての新しいWindows OSバージョン（Windows 8以降）でデフォルトで有効になっていますが、互換性問題（特に一部のウイルス対策ソフトとの互換性問題）を引き起こす可能性があります。 このような問題やその後のエラーは、それぞれのケースで大きく異なる可能性があります。 +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. -これが原因ではないかと思われる問題が発生した場合は、いつでも、より古いながらも安定しているTDIネットワークドライバーに切り替えることができます。 その方法は以下の通りです: +If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: -1. AdGuard の*「設定」→「ネットワーク」*に移動します。 +1. Go to *Settings → Network*. -2. 画像のように、WFPドライバーを無効にします: +2. Disable WFP driver as it’s done in this picture: -![WFPドライバー *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) +![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/account/features.md index 3a9c2f93747..658648841a2 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ AdGuard 広告ブロッカーライセンスにバインド（紐付け）され ## サポート・お問い合わせ -「サポート」タブには、AdGuard 製品に関する問題を解決したり、よくあるご質問への回答を見つけたりするのに役立つリンクが含まれています。 They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +「サポート」タブには、AdGuard 製品に関する問題を解決したり、よくあるご質問への回答を見つけたりするのに役立つリンクが含まれています。 6つのセクションがあります：「よくあるご質問（FAQ）、バグ報告・機能リクエストを送る、不適切なブロックを報告、サポート・お問い合わせ、ナレッジベース、意見交換 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 55eebf9eeab..ef22e8812b3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ sidebar_position: 2 - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 2a794e73957..23ceb2075fe 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3944,7 +3739,7 @@ The `min-length` special attribute must not appear in a selector to the left of :contains(unquoted text) ``` -もしくは +or ```text :contains(/reg(ular )?ex(pression)?/) @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuardコンテンツブロッカー][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4398,7 +4125,7 @@ rules_list !#endif ``` -もしくは +or ```adblock !#if (conditions) @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,30 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index a0907dc0245..e76b0ce2233 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuardの広告ブロックフィルタには以下が含まれます: - AdGuard ベースフィルタ - AdGuard モバイル広告フィルタ - 言語ごとに分けられた地域フィルタ：中国語、オランダ語、フランス語、ドイツ語、日本語、ロシア語、スペイン語/ポルトガル語、トルコ語、ウクライナ語。例「AdGuard 日本語フィルタ」 -- AdGuard Quick Fixes filter ### これらのフィルタの目的 - 「**AdGuard ベースフィルタ**」は、英語のウェブサイトや、専用フィルタがないウェブサイトの広告をブロックするように設計されています。 言語に関係なくすべてのサイトに適用される一般的なフィルタリングルールも含まれています。 - 「**AdGuard モバイル広告フィルタ**」はウェブサイトのモバイル版の広告とモバイルアプリ内の広告をブロックします。 言語によるセグメンテーション・差別化はありません。 - **地域別フィルタ**（言語特化フィルタ）は、 **AdGuard ベースフィルタ**と同じポリシーに従いますが、特定の言語のウェブサイトに限定されます。 -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. 広告ブロックフィルタの目的は、インターネットから広告を読み込むことができるウェブサイト、アプリケーション、特定のデバイス上であらゆる種類の広告をブロックすることです。ブロックする広告の種類: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/license/what-is.md index afbaeef5950..cb61bdc4400 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: AdGuard ライセンスとは? sidebar_position: 1 --- @@ -12,7 +12,7 @@ sidebar_position: 1 - **1年サブスクリプション** - これらのライセンスは毎年自動的に更新されますが、手動で延長することもできます。 - パーソナル（デバイス3台用） - ファミリー（デバイス9台用） -- **Lifetime** — these licenses are perpetual +- **永久** - これらのライセンスには有効期限はなく、ずっとご利用いただけます。 - パーソナル（デバイス3台用） - ファミリー（デバイス9台用） diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 90f8913b35c..f9993591e0f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/ja/docusaurus-plugin-content-docs/current/general/userscripts.md index 1bbaa624f45..40e307a564c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index d12b98e113d..72e2bbd29f1 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: HARファイルを収集する方法 sidebar_position: 1 --- diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 30d4f112ecf..4d3a351ef3d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ GitHubでバグが以前に報告されていないかどうかを確認して ### 問題を説明する方法 -できるだけ多くの詳細を記載するようにしてください。これにより、バグの再現と修正がより簡単になります。 Here’s what we expect a bug report to include: +できるだけ多くの詳細を記載するようにしてください。これにより、バグの再現と修正がより簡単になります。 バグ報告で歓迎される内容は以下のとおりです: - AdGuardアプリのバージョン - お使いのOSのバージョン @@ -26,9 +26,9 @@ GitHubでバグが以前に報告されていないかどうかを確認して - 問題が再発したかどうか、またその頻度はどれくらいか - VPNやウイルス対策ソフトを使用しているかどうか -### How to collect logs +### ログを収集する方法 -Read about collecting logs in dedicated articles for each platform. +ログの収集については、各プラットフォームの専用記事をお読みください。 ## バグレ報告や機能リクエストに投票する方法 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index 3e0b7dee63b..cf937707d70 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ iPhone/iPadでスクリーンショットを撮るには、次の組み合わせ Windowsは画面全体をキャプチャし、クリップボードにコピーします。 -To take a screenshot of an active window, use the following shortcut keys: +現在使用中ウィンドウのスクリーンショットを撮るには、次の組み合わせを使用します: - ***Alt* を押しながら、 *PrtScn* (機種によっては *Fn + Alt + PrtScn*) を押します。** -To take a screenshot of a specific area, use the following shortcut keys: +画面上の特定領域のスクリーンショットを撮るには、次の組み合わせを使用します: - ******Win + Shift + S****** -スクリーンショットを撮った後、クリップボードに保存されます。 ほとんどの場合、 *Ctrl + V* というショートカットキーで、現在編集中の文書にペーストすることができます。 また、スクリーンショットをファイルに保存する必要がある場合は、標準の「**ペイント**」プログラム（または画像を扱うことができるその他のアプリ）を開いてください。 Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +スクリーンショットを撮った後、クリップボードに保存されます。 ほとんどの場合、 *Ctrl + V* というショートカットキーで、現在編集中の文書にペーストすることができます。 また、スクリーンショットをファイルに保存する必要がある場合は、標準の「**ペイント**」プログラム（または画像を扱うことができるその他のアプリ）を開いてください。 Ctrl+V 、または貼り付けボタン（通常、画面の左上隅）をクリックしてスクリーンショットを貼り付け、保存してください。 -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. これらのキーを押すと同時に、スクリーンショットは自動的にファイルとして「*写真*」→「*スクリーンショット*」フォルダに保存されます。 +Windows 8 と 10 では、 *Win + PrtScn* というショートカットで、非常に素早くスクリーンショットを撮ることができます。 これらのキーを押すと同時に、スクリーンショットは自動的にファイルとして「*写真*」→「*スクリーンショット*」フォルダに保存されます。 また、スクリーンショットを撮るための専用プログラム「 *Snipping Tool* 」があり、コンピュータのスタートメニューにある標準プログラムの中から見つけることができます。 Snipping Tool を使用すると、デスクトップの任意の領域または画面全体をキャプチャできます。 このプログラムを使ってスクリーンショットを撮った後、画像を編集し、コンピュータの任意のフォルダに保存することができます。 @@ -70,26 +70,26 @@ Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* ### macOS の場合 {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Macでスクリーンショットを撮るには、以下のショートカットを使用します: - ******⌘ Cmd + Shift + 3*** を同時に押します。*** こうすることによって画面全体がキャプチャされ、ファイルとしてデスクトップに保存されます。 -To take a screenshot of an active window, use the following shortcut keys: +現在使用中ウィンドウのスクリーンショットを撮るには、次の組み合わせを使用します: - *****⌘ Cmd + Shift + 4 + Space*** を同時に長押しします。 ポインターがカメラアイコンに変わります。 撮りたいウィンドウをクリックすると、キャプチャします。 （スクリーンショットの撮影をキャンセルするには、Escボタンを押します。）** -To take a screenshot of a specific area, use the following shortcut keys: +画面上の特定領域のスクリーンショットを撮るには、次の組み合わせを使用します: - ******⌘ Cmd + Shift + 5*** を押します***。 十字をドラッグして必要な領域を選択します。 マウスまたはトラックパッドを離すとスクリーンショットが撮影されます（Escキーで撮影をキャンセルできます）。 -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +*タッチバー* (MacBook Pro)のスクリーンショットを撮るには、以下のショートカットを使用します: - ******⌘ Cmd + Shift + 6*** を同時に押します。*** こうすることによって*タッチバー*全体がキャプチャされ、ファイルとしてデスクトップに保存しされます。 -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +スクリーンショットを保存せずにクリップボードにコピーするには、 *Ctrl* を押しながら、上記のいずれかのショートカットを押してください。 その後、 *Cmd + V* で、（クリップボードから）スクリーンショットを現在編集中の文書、画像、アプリなどに貼り付けることができます。 また、 「**プレビュー**」アプリを使用して、 「**スクリーンショットを撮る**」 を選択することによって、スクリーンショットを撮る（選択した領域、ウィンドウ、または画面全体）ことができます。 「**プレビュー**」では、スクリーンショットを JPG、TIFF、PDF、その他のファイル形式で保存することができます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/intro.md b/i18n/ja/docusaurus-plugin-content-docs/current/intro.md index cc8e606461c..ddd60fd78de 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ AdGuard は、15 年以上の経験、さまざまなプラットフォーム向 ## 広告ブロック以外の機能もたくさんあります -AdGuard 広告ブロッカーは、広告をブロックするだけではありません。 トラッキングから守り、さまざまな方法であなたのオンラインプライバシーを強化してくれます。 各製品によって、保護層を増やしてくれる*DNSフィルタリング*、不適切なコンテンツから子供を守る*ペアレンタルコントロール*、インターネットトラフィックを制御するための*フィルタリングログ*などという機能も提供しています。 This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard 広告ブロッカーは、広告をブロックするだけではありません。 トラッキングから守り、さまざまな方法であなたのオンラインプライバシーを強化してくれます。 各製品によって、保護層を増やしてくれる*DNSフィルタリング*、不適切なコンテンツから子供を守る*ペアレンタルコントロール*、インターネットトラフィックを制御するための*フィルタリングログ*などという機能も提供しています。 本ナレッジベースには、各製品の機能に関する詳細な情報が含まれています。左側の目次（スマホの場合は左上の「≡」アイコン）から、興味のある記事にジャンプしてお読みください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index c4569fa7b31..058b5b4cb32 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ sidebar_position: 4 ブロックフィルターを扱うには、ある程度のスキルと知識が必要です。 もし、スキルをお持ちで、ルールの作り方をご存知でしたら、[GitHubの「AdGuard Filters」リポジトリ](https://github.com/AdguardTeam/AdguardFilters) に直接アクセスしてください。 そこには、広告の見逃しや誤検出など、それぞれのウェブサイトでの問題に対する多くのopen issueがあります。 好きなissueを選んで、コメントで独自のルールを提案してください。 AdGuardフィルターエンジニアがご提案を確認し、適切と判断した場合、ご指摘のルールはAdGuardのフィルターに追加されます。 -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### 報酬 {#rewards} diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index e66643a6a59..0efd3d1868e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: 翻訳者・校正者になるには sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +AdGuard製品、ウェブサイト、ナレッジベースの翻訳にご協力いただける方は、[Crowdin](https://crowdin.com/)にアクセスして、登録またはログインしてください。 ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index 5fc02da2d9d..26e8bbf5e5e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ Let’s take a look at this picture. ここでは、前に立つと語形が決 そういった情報を確認できるところをご紹介します。 -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) は、幅広い言語リストを含んでいます。 The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) は、幅広い言語リストを含んでいます。 The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. また、 [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR)で複数形に関する情報を入手することもできます。 CLDR Plural Rulesでは、10進数（1.5; 2.3; 100.1…）に対する追加の語形が示されていますが、AdGuardの翻訳ではそのような数字は使用していません。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 197b42f446f..2b22b885317 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: AdGuard翻訳プログラム sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **免責事項:** AdGuardの翻訳に関するご質問は、 [translate@adguard.com](mailto:translate@adguard.com) にメールを送るか、もしくは [Telegramチャット](https://t.me/joinchat/UVYTLcHbr8JmOGIy) に参加してください。 -When it comes to translations, we at AdGuard always heavily rely on volunteers. +翻訳に関しては、AdGuard は常にボランティアの方々に大変お世話になっております。 -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +現在、私たちの製品の翻訳管理には、[Crowdinプラットフォーム](https://crowdin.com/)を使用しています。 そこは、AdGuard製品の翻訳に貢献してくれる方々のための場でもあるのです。 -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +AdGuardの翻訳を手伝ってくれるボランティアの皆様の一員になりたい方は、 [翻訳者になる方法](../become-translator)と[ボランティアとの協力方法](../rewards)を読んでください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 9edc862af97..1f96dcc52b3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: Crowdinファイルの翻訳の優先順位 sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +Crowdinには、[AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases) という5つの主要なAdGuardプロジェクトがあります。 *AdGuard Applications*プロジェクトのどのファイルや製品から始めるべきか、明確なガイドラインはありません。 お好きな製品をお選びください。 ただ、いくつか触れておきたいことがあります: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- Crowdinで翻訳が完了した言語のみが、AdGuardアプリのUIで表示されます。 - 製品自体の翻訳がなければ説明文等は不要になるので、アプリストアの説明文などの翻訳は後回しにしたほうがお勧めです。 ただし、*AdGuard Websites*プロジェクトの場合は異なります。 翻訳が100％完了していなくても、言語をサイトに追加することは可能です。 これはどのファイルがすでに翻訳されているかによります。 そのため、最も重要なファイルから順に翻訳されることをお勧めします（以下に記載）: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 2336521f588..b18eed154fc 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: ナレッジベースの更新・変更 sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. しかし、情報は常に変化し、記事が現状を反映しきれなくなることがあります。 +AdGuardナレッジベース（知恵袋）の目的は、AdGuard関連のあらゆるトピックに関する最新情報・説明・使い方を皆様に提供することです。 しかし、情報は常に変化し、記事が現状を反映しきれなくなることがあります。 そのため、AdGuardナレッジベースコンテンツをすべて[GitHub](https://github.com/AdguardTeam/KnowledgeBase)に置き、既存の記事の編集や翻訳、まったく新しい記事の提案など、誰もが貢献できるようにしています。 ## 変更点を提案する・新しい記事を書く方法 {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. GitHubプラットフォームでの作業方法をあまりわからない場合は、[こちらのGitHubの使い方に関するドキュメント](https://docs.github.com/ja)を確認することから始めてください。 +上記のGitHubの機能を使って、既存記事への変更を提案したり、新しい記事をナレッジベースに追加することができます。 GitHubプラットフォームでの作業方法をあまりわからない場合は、[こちらのGitHubの使い方に関するドキュメント](https://docs.github.com/ja)を確認することから始めてください。 -準備ができましたら、[KnowledgeBaseリポジトリ](https://github.com/AdguardTeam/KnowledgeBase)で作業してください。 All texts in our Knowledge Base are written in `Markdown` markup language. 記事の編集や執筆の際には、このことを念頭に置いてください。 [こちら](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)で、Markdownの構文について詳しく知ることができます。 +準備ができましたら、[KnowledgeBaseリポジトリ](https://github.com/AdguardTeam/KnowledgeBase)で作業してください。 ナレッジベースにあるすべてのテキスト・文章は、 `Markdown`マークアップ言語を使って書かれています。 記事の編集や執筆の際には、このことを念頭に置いてください。 [こちら](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)で、Markdownの構文について詳しく知ることができます。 -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. 変更または追加を提案する場合、すべてのテキストがのDocusaurus 2に準拠している必要があります。 Docusaurus 2の原則は、 [このリンク先のDocusaurusガイド](https://docusaurus.io/docs/category/guides)で確認することができます。 +ナレッジベースのウェブサイトは、現代の静的ウェブサイトジェネレータである「Docusaurus 2」を使用して構築されています。 変更または追加を提案する場合、すべてのテキストがのDocusaurus 2に準拠している必要があります。 Docusaurus 2の原則は、 [このリンク先のDocusaurusガイド](https://docusaurus.io/docs/category/guides)で確認することができます。 -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +このナレッジベースは、お使いのコンピュータでローカルに展開することで、提案する変更をプレビューすることができます。 この方法は、本ナレッジベースの[GitHubページにあるREADME.mdファイル](https://github.com/AdguardTeam/KnowledgeBase#readme)に記載されています。 ## 記事を翻訳する方法 {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +ナレッジベースの既存記事の翻訳は、 [Crowdin platform](https://crowdin.com/profile/adguard)を使って行われています。 Crowdinの翻訳と作業に関するすべての詳細は、AdGuard広告ブロッカーのナレッジベースにある[専用記事](../translate/guidelines)に記載されています。 -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [別の記事](https://kb.adguard.com/ja/miscellaneous/plurals)で、複数形の文字列を翻訳する際に起こりうる困難について詳しく説明し、複数形に関するCrowdinプラットフォームでの作業方法について幅広く解説しています。 +AdGuardナレッジベースの記事を翻訳する際、複数形を含む文字列に遭遇することがありますが、複数形がいっぱいある言語の場合は特に注意して翻訳してください。 [別の記事](https://kb.adguard.com/ja/miscellaneous/plurals)で、複数形の文字列を翻訳する際に起こりうる困難について詳しく説明し、複数形に関するCrowdinプラットフォームでの作業方法について幅広く解説しています。 ## Open issue（GitHub）に対する作業・貢献 -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. お好みのissueを選んで、ぜひ作業を始めてください。 issueに関してご質問等があれば、お気軽にissueのコメント欄で直接メッセージしてください。 +ナレッジベースの更新に関連する[オープンタスク](https://github.com/AdguardTeam/KnowledgeBase/issues)が存在することがあります。 このナレッジベースに対する他の変更を提案するのと[同じ方法](#suggest-change)で、タスクの完了を高速化いただくことができます。 お好みのissueを選んで、ぜひ作業を始めてください。 issueに関してご質問等があれば、お気軽にissueのコメント欄で直接メッセージしてください。 diff --git a/i18n/ko/docusaurus-plugin-content-docs/current.json b/i18n/ko/docusaurus-plugin-content-docs/current.json index 79b6613c466..91998fbc1f5 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current.json +++ b/i18n/ko/docusaurus-plugin-content-docs/current.json @@ -28,7 +28,7 @@ "description": "The label for category AdGuard for Windows in sidebar tutorialSidebar" }, "sidebar.tutorialSidebar.category.AdGuard for Mac": { - "message": "Mac용 AdGuard", + "message": "AdGuard for Mac", "description": "The label for category AdGuard for Mac in sidebar tutorialSidebar" }, "sidebar.tutorialSidebar.category.Solving problems": { diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md index 89d62a74ae4..1ee3aca1a9d 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md @@ -9,18 +9,18 @@ sidebar_position: 2 ::: -[AdGuard 확장 프로그램](https://adguard.com/adguard-browser-extension/overview.html)은 5개의 인기 브라우저(Chrome, Firefox, Edge, Opera, Yandex 브라우저)에서 작동하는 무료 확장 프로그램입니다. 브라우저의 부가 기능 스토어나 공식 웹사이트에서 쉽게 찾을 수 있습니다. +[AdGuard Browser Extension](https://adguard.com/adguard-browser-extension/overview.html) is a free extension that works in five popular browsers: Chrome, Firefox, Edge, Opera, and Yandex Browser. 브라우저의 부가 기능 스토어나 공식 웹사이트에서 쉽게 찾을 수 있습니다. -![Chrome용 AdGuard 확장 프로그램 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) +![AdGuard Browser Extension for Chrome \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) -브라우저 확장 프로그램에는 기본 광고 차단 기능이 포함되어 있지만 [Windows용 AdGuard](/adguard-for-windows/features/home-screen) 및 [Mac용 AdGuard](/adguard-for-mac/features/main)와 같은 전체 기능을 갖춘 데스크톱 프로그램만큼 강력하지는 않습니다. +Browser extensions include basic ad-blocking features but cannot be compared with full-featured desktop programs, such as [AdGuard for Windows](/adguard-for-windows/features/home-screen) and [AdGuard for Mac](/adguard-for-mac/features/main). -![대부분의 인기 브라우저에서 사용 가능 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) +![Available for most popular browsers \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) :::note -Safari용 독립 실행형 확장 프로그램이 있습니다. [Safari 13](https://adguard.com/en/blog/adguard-safari-1-5.html)이 출시된 이후 대부분의 광고 차단 확장 프로그램에서 큰 문제가 발생하여 많은 확장 프로그램이 작동을 멈췄습니다. 이 문서에서 설명하는 확장 프로그램과는 다른 별도의 [Safari용 확장 프로그램](/adguard-for-safari/features/general)을 개발해야 했습니다. +Safari용 독립 실행형 확장 프로그램이 있습니다. Since the release of [Safari 13](https://adguard.com/en/blog/adguard-safari-1-5.html), most of the ad-blocking extensions have experienced huge issues and many of them stopped functioning. We had to develop a [separate extension for Safari](/adguard-for-safari/features/general) that has some differences in comparison with the extension described in this article. ::: -**각 확장 프로그램의 기능은 브라우저에 의해 엄격하게 제한된다는 것을 잊지 마세요**. 따라서 본격적인 보호를 받으려면 컴퓨터용 독립 실행형 프로그램을 설치하는 것이 좋습니다. [여기](adguard-browser-extension/comparison-standalone)에서 독립 실행형 프로그램을 설치해야 하는 이유를 확인할 수 있습니다. +**Do not forget that the functionality of each extension is strictly limited by the browser’s capabilities.** So if you want to get full-fledged protection, consider installing a standalone program for your computer. There's [a reason why](adguard-browser-extension/comparison-standalone). diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 4e20e0e6cc5..08fd707c27a 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -1,5 +1,5 @@ --- -title: 독립 실행형 앱과의 비교 +title: Comparison to standalone apps sidebar_position: 7 --- @@ -17,10 +17,10 @@ sidebar_position: 7 AdGuard 브라우저 확장 프로그램은 무료이며, 설치가 쉽고 광고를 차단하며 온라인 위협에 대응하는 필터가 있습니다. 정식 앱의 경우 확장 프로그램 대비 더 강력하고 고급 기능 목록을 제공합니다. 아래 비교 표에서 모든 차이점을 확인하세요. -![확장 프로그램 대 앱 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) +![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — 설치된 브라우저에서만 사용할 수 있으며 브라우저에 의해 제한을 받습니다. +`1` – within browser restrictions and only in the browser where it is installed; -`2` — 확장 프로그램이 다른 확장 프로그램의 요청을 감지할 수 없습니다. 만약 악성 또는 추적 확장 프로그램이 광고나 당신의 활동을 추적하기 위해 서버에 요청을 보내는 경우, AdGuard 브라우저 확장 프로그램은 해당 요청을 차단할 수 없습니다. +`2` – the extension is unable to detect requests from other extensions. 만약 악성 또는 추적 확장 프로그램이 광고나 당신의 활동을 추적하기 위해 서버에 요청을 보내는 경우, AdGuard 브라우저 확장 프로그램은 해당 요청을 차단할 수 없습니다. -`3` — 특정 브라우저 제한으로 인해 모든 유형의 광고 및 위협이 확장 프로그램으로 차단되는 것은 아닙니다. 일부 요소는 페이지로 이동하여 로딩 프로세스가 느려질 수 있습니다. 또한 브라우저 기반 광고 차단기와 달리 AdGuard 앱은 광고가 브라우저에 로드되기 전에 차단합니다. 이렇게 하면 트래픽이 절약되고 페이지 로딩 속도가 빨라집니다. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. 일부 요소는 페이지로 이동하여 로딩 프로세스가 느려질 수 있습니다. 또한 브라우저 기반 광고 차단기와 달리 AdGuard 앱은 광고가 브라우저에 로드되기 전에 차단합니다. 이렇게 하면 트래픽이 절약되고 페이지 로딩 속도가 빨라집니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md index 24318f6ae5c..cc063d2747e 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md @@ -1,5 +1,5 @@ --- -title: 독립형 앱과의 호환성 +title: Compatibility with the standalone app sidebar_position: 4 --- @@ -9,16 +9,16 @@ sidebar_position: 4 ::: -AdGuard 확장 프로그램은 브라우저에서 광고를 차단할 수 있지만, [AdGuard 독립 실행형 프로그램](/adguard-browser-extension/comparison-standalone)은 브라우저와 앱을 포함하여 기기의 모든 트래픽을 필터링합니다. +While AdGuard Browser Extension can block ads in browsers, [AdGuard standalone programs](/adguard-browser-extension/comparison-standalone) filter all the traffic on your device, including from browsers and apps. -확장 프로그램과 독립 실행형 프로그램을 모두 컴퓨터에 설치하는 경우 일부 호환성 문제가 발생할 수 있습니다. 문제는 경우에 따라 앱과 확장 프로그램이 서로 간섭할 수 있다는 것입니다. 일부 웹사이트는 더 이상 데스크톱 프로그램으로 보호되지 않으며 기능이 더 적은 확장 프로그램으로만 보호됩니다. 또한 일부 웹사이트에서는 필터링이 제대로 작동하지 않을 수 있습니다. 따라서 확장 프로그램을 앱과 함께 사용하지 않는 것이 좋습니다. +If you decide to install both the extension and the standalone program on your PC, you may encounter some compatibility issues. The problem is that in some cases the application and the extension may interfere with each other. Some websites will no longer be protected by the desktop program and will only be protected by the extension, which has fewer options. Also, filtering may work incorrectly for some websites. Therefore, we don't recommend using the extension together with the application. -컴퓨터에 AdGuard 데스크톱 버전이 설치되어 있는 경우 확장 프로그램 대신 AdGuard 브라우저 어시스턴트를 사용하는 것이 좋습니다. +If you have the desktop version of AdGuard installed on your PC, it is better to use AdGuard Browser Assistant instead of the extension. -## AdGuard 브라우저 어시스턴트 +## AdGuard Browser Assistant -![AdGuard 브라우저 어시스턴트 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) +![AdGuard Browser Assistant \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) -AdGuard 브라우저 어시스턴트는 AdGuard 브라우저 확장 프로그램처럼 작동하지만 훨씬 가볍고 데스크톱 앱과 간섭하지 않는 브라우저 확장 프로그램입니다. [Windows](/adguard-for-windows/browser-assistant) 또는 [Mac용 브라우저 어시스턴트](/adguard-for-mac/features/browser-assistant)에 대한 자세한 내용을 읽고 [웹사이트에서 다운로드](https://adguard.com/adguard-assistant/overview.html)할 수 있습니다. +AdGuard Browser Assistant is a browser extension that works and feels just like AdGuard Browser Extension, but it's much lighter and doesn't interfere with the desktop apps. You can [read more about Browser Assistant for Windows](/adguard-for-windows/browser-assistant) or [Mac](/adguard-for-mac/features/browser-assistant), or [download it from our website](https://adguard.com/adguard-assistant/overview.html). -AdGuard 브라우저 어시스턴트는 모든 주요 브라우저에서 사용할 수 있습니다. +AdGuard Browser Assistant is available in all major browsers. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index fd8829a7d9f..bd6a4454f60 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -11,29 +11,29 @@ sidebar_position: 1 광고 차단은 모든 광고 차단기의 핵심 기능이며 AdGuard 브라우저 확장 프로그램도 예외는 아닙니다. 광고 차단은 특수 언어로 작성된 규칙 집합인 필터를 기반으로 합니다. 이러한 규칙은 어떤 요소를 차단해야 하고 어떤 요소를 차단하지 말아야 하는지를 알려줍니다. AdGuard는 규칙을 해석하고 이를 기반으로 웹 요청을 수정합니다. 결과적으로 웹페이지에 광고가 표시되지 않습니다. -![필터 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters.png) +![Filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters.png) 모든 필터는 역할에 따라 분류됩니다. 예를 들어 광고 차단 필터, 프라이버시 보호 필터, 소셜 미디어 필터 등의 범주가 있습니다. 개별 필터 또는 전체 그룹을 한 번에 활성화할 수 있습니다. -![광고 차단 필터 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters1.png) +![Ad blocking filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters1.png) ## 사용자 정의 필터 -다른 필터 그룹의 기능은 설명이 필요 없을 것 같지만, **사용자 정의**이라는 필터 그룹은 설명이 좀 더 필요한 것 같습니다. +어느 정도 예측 가능한 기능을 가진 필터 그룹 외에 **사용자 정의** 필터가 있습니다. -![사용자 정의 필터 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) +![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) 이 탭에서는 기본적으로 확장 프로그램에 없는 필터를 추가할 수 있습니다. [인터넷에는 공개적으로 사용 가능한 필터](https://filterlists.com)가 많이 있습니다. 또한 자신만의 필터를 만들고 추가할 수 있습니다. 필터 세트를 만들고 원하는 방식으로 광고 차단을 맞춤 설정할 수 있습니다. 필터를 추가하려면 **사용자 정의 필터 추가**를 클릭하고 추가하려는 필터의 URL 또는 파일 경로를 입력한 후 **다음**을 클릭합니다. -![사용자 정의 필터 추가 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters1.png) +![Add a custom filter \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters1.png) ## 사용자 규칙 {#user-rules} **사용자 규칙**은 광고 차단을 맞춤 설정하는 데 도움이 되는 또 다른 도구입니다. -![사용자 규칙 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_user_rules.png) +![User rules \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_user_rules.png) 새 규칙을 추가하는 방법에는 여러 가지가 있습니다. 가장 간단한 방법은 규칙을 입력하는 것이지만, [규칙 구문](/general/ad-filtering/create-own-filters)에 대한 지식이 필요합니다. @@ -47,10 +47,10 @@ sidebar_position: 1 **허용 목록**은 특정 웹사이트를 필터링에서 제외하는 데 사용됩니다. 목록에 있는 웹사이트에는 차단 규칙이 적용되지 않습니다. -![허용 목록 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist.png) +![Allowlist \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist.png) **허용 목록**을 반대로 사용할 수도 있습니다. 이 목록에 추가된 웹사이트를 제외한 모든 곳에서 광고 차단을 해제할 수 있습니다. 이렇게 하려면 허용 목록 **반전 옵션**을 활성화합니다. -![허용 목록 반전 \*border] (https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist1.png) +![Invert allowlist \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist1.png) 허용 목록을 가져오거나 내보낼 수도 있습니다. 예를 들어 각 브라우저에 동일한 규칙을 적용하려는 경우 유용합니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 14c59e256aa..772d5f41e75 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -11,10 +11,10 @@ sidebar_position: 4 확장 프로그램의 메인 페이지는 브라우저의 도구 모음에서 확장 프로그램의 아이콘을 클릭하여 액세스할 수 있습니다. -![메인 메뉴 \*mobile\_border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_main.png) +![Main menu \*mobile\_border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_main.png) 기본 페이지에서 페이지의 모든 요소를 수동으로 숨기거나(**사용자 규칙**에 해당 규칙이 추가됨), **필터링 로그**를 열어 브라우저의 트래픽에 대한 전체 정보를 확인하고 이동 중에 요청을 차단하거나 웹사이트의 보안 보고서를 확인할 수 있습니다. 또한 모든 웹사이트에 대한 불만 사항을 제출하고 (예: 페이지에 누락된 광고가 있는 경우 필터 개발자가 신고를 검토하여 문제를 해결합니다) 적용된 차단 규칙에 대한 통계를 확인할 수 있습니다. -브라우저에서 이루어진 모든 웹 요청은 **필터링 로그**에 각 요청에 대한 자세한 정보와 함께 표시됩니다. 예를 들어, **필터링 로그**를 통해 AdGuard 확장 프로그램에서 차단한 요청들을 쉽게 모니터링할 수 있습니다. 또한 두 번의 클릭으로 모든 요청을 차단하거나 이전에 차단한 요청을 허용 목록에 추가할 수 있습니다. **필터링 로그**에서 웹 요청을 정렬할 수 있는 다양한 옵션도 제공하므로 사용자 정의 규칙을 만들 때 유용하게 사용할 수 있습니다. 기본 메뉴에서 해당 항목을 선택하거나 설정 페이지(**추가 설정** 탭)에서 **필터링 로그**를 열 수 있습니다. +브라우저에서 이루어진 모든 웹 요청은 **필터링 로그**에 각 요청에 대한 자세한 정보와 함께 표시됩니다. 예를 들어, **필터링 로그**를 통해 AdGuard 확장 프로그램에서 차단한 요청들을 쉽게 모니터링할 수 있습니다. 또한 두 번의 클릭으로 모든 요청을 차단하거나 이전에 차단한 요청을 허용 목록에 추가할 수 있습니다. **필터링 로그**에서 웹 요청을 정렬할 수 있는 다양한 옵션도 제공하므로 사용자 정의 규칙을 만들 때 유용하게 사용할 수 있습니다. 기본 메뉴에서 해당 항목을 선택하거나 설정 페이지(추가 설정 탭)에서 **필터링 로그**를 열 수 있습니다. 확장 프로그램의 주 메뉴 오른쪽 상단에 있는 아이콘을 클릭하면 콘텐츠 차단기 설정을 열거나 보호 기능을 일시 중지할 수 있습니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 48550876ed7..37c87434555 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -15,17 +15,17 @@ AdGuard 브라우저 확장 프로그램의 주요 모듈 외에도 확장 프 **일반 탭**에서 검색 광고 및 [웹사이트 자체 홍보](/general/ad-filtering/search-ads)를 허용하고 언어별 필터 자동 활성화나 필터 업데이트 주기 등을 지정할 수 있습니다. -![일반 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) +![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) 또한, 여기에서 [_피싱 및 멀웨어 보호_](/general/browsing-security)를 활성화할 수 있습니다. -**설정 내보내기** 버튼을 클릭하여 구성을 저장할 수 있습니다. 설정은 .json 파일로 저장됩니다. 이전에 저장한 설정 구성을 가져오려면 **설정 불러오기** 기능을 사용하세요. 다른 설정 프로필 간에 빠르게 전환하거나 다른 브라우저 간에 구성을 전송하는 데에도 사용할 수 있습니다. +**설정 내보내기** 버튼을 클릭하여 구성을 저장할 수 있습니다. 설정은 .json 파일로 저장됩니다. 이전에 만든 구성을 적용하려면 **설정 가져오기** 기능을 사용하세요. 다른 설정 프로필 간에 빠르게 전환하거나 다른 브라우저 간에 구성을 전송하는 데에도 사용할 수 있습니다. ## 추가 설정 {#misc} **추가 설정** 섹션에는 광고 차단 프로세스 및 앱 사용성과 관련된 다양한 설정이 포함되어 있습니다. -! [추가 설정 \*border] (https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_additional_settings.png) +![Additional settings \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_additional_settings.png) 이 탭에서 최적화된 필터를 활성화하고, 확장 프로그램 업데이트에 대한 알림을 사용 설정하고, **필터링 로그**를 열거나 차단된 광고 및 트래커의 통계를 지울 수 있습니다. @@ -33,6 +33,6 @@ AdGuard 브라우저 확장 프로그램의 주요 모듈 외에도 확장 프 ## 정보 {#about} -**정보 섹션**에는 현재 버전에 대한 정보, EULA 및 개인정보취급방침에 대한 링크, GitHub의 확장 프로그램 저장소를 확인할 수 있습니다. +**정보 섹션**에는 현재 버전에 대한 정보, EULA 및 개인정보취급방침에 대한 링크, GitHub의 브라우저 확장 프로그램 저장소를 확인할 수 있습니다. -![정보 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) +![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md index 598064968ae..72436e674df 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/stealth-mode.md @@ -11,7 +11,7 @@ sidebar_position: 2 **스텔스 모드**는 추적기 및 사기 사이트로부터 민감한 개인정보를 보호하는 것을 목표로 합니다. -![스텔스 모드 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_stealth_mode.png) +![Stealth Mode \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_stealth_mode.png) 스텔스 모드에서는 웹사이트가 인터넷에서 해당 웹사이트를 찾는 데 사용한 검색어를 볼 수 없도록 하고, 쿠키(제3자 쿠키 포함)를 자동으로 삭제하는 등의 기능을 사용할 수 있습니다. [별도의 문서](/general/stealth-mode)에서 이러한 모든 기능에 대해 확인할 수 있습니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md index 66bd868078d..52c458dc3f2 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md @@ -71,4 +71,4 @@ sidebar_position: 3 ## Safari용 AdGuard 확장 프로그램 설치 방법 -Safari용 AdGuard는 일반적으로 브라우저 확장 프로그램이 아닙니다. 자세한 내용은 [이 문서](/adguard-for-safari/features/general)에서 확인할 수 있습니다. 또는 [이 페이지](https://agrd.io/safari_release)에서 설치 파일을 다운로드할 수 있습니다. +Safari용 AdGuard는 일반적으로 브라우저 확장 프로그램이 아닙니다. You can read more about it in a [dedicated article](/adguard-for-safari/features/general). 또는 [이 페이지](https://agrd.io/safari_release)에서 설치 파일을 다운로드할 수 있습니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 332361fff58..00000000000 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## 제한 - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index 518dc0b6e8d..2f7333aed35 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: 브라우저에 의해 보호받는 페이지 -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md index 3cc95bdd961..fac4cfab793 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md @@ -13,7 +13,7 @@ sidebar_position: 1 3. _개발자 모드_를 활성화합니다. - ![개발자 모드 \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/developer_mode1.png) + ![Developer mode \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/developer_mode1.png) 4. `background.html`을 클릭합니다. @@ -53,11 +53,11 @@ sidebar_position: 1 :::note -AdGuard는 사용자의 개인정보를 보호하기 위해 최선을 다하고 있습니다. 당사는 [개인정보취급방침](https://adguard.com/privacy/browser-extension.html)을 준수하며 사용자에 대한 어떠한 개인정보도 수집하지 않습니다. 지원팀에 로그를 보내기 전에 파일에 전달하고 싶지 않은 추가 정보가 포함되어 있는지 확인하세요. 이러한 정보가 포함되어 있는 경우, 먼저 삭제하는 것이 좋습니다. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/browser-extension.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -로그를 저장했다면, 다음 단계에 따라 개발팀에 제출해 주세요. +Now that you have collected the logs, please follow these steps to submit them to our development team: -1. [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose)에 버그를 제보하세요. -2. 로그와 재생 시간이 포함된 ZIP 파일을 `devteam@adguard.com`로 보내고 GitHub 이슈에 링크를 추가합니다. 파일을 첨부하는 대신 Google 드라이브에 ZIP 파일을 업로드하고 링크를 추가할 수도 있습니다. +1. Report the bug on [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). +2. Send your archive with logs and playback time to `devteam@adguard.com` and add a link to your GitHub issue. You can also upload the archive to Google Drive and add the link to it instead of attaching the file. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 4760957e251..ce4196e202d 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ sidebar_position: 2 ### '문제가 없는' 앱과 '문제가 있는' 앱 -Most apps work correctly when filtered. 이러한 앱의 경우, 해당 앱의 트래픽은 AdGuard를 통해 라우팅되고 기본적으로 필터링됩니다. +필터링이 활성화되어 있으면 대부분의 앱이 제대로 작동합니다. 이러한 앱의 경우, 해당 앱의 트래픽은 AdGuard를 통해 라우팅되고 기본적으로 필터링됩니다. 다운로드 관리자, 라디오, UID 1000 및 1001이 있는 시스템 앱(예: Google Play 서비스)과 같은 일부 앱은 '문제가 있는' 앱으로 AdGuard를 통해 라우팅할 때 잘못 작동할 수 있습니다. 그렇기 때문에 모든 앱을 라우팅하거나 필터링하려고 할 때 다음과 같은 경고가 표시될 수 있습니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 6ee27b10c63..031b3c308f3 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ DNS 보호 모듈은 **보호** 탭(화면 하단의 왼쪽 두 번째 아이콘 :::tip -DNS 보호는 일반 광고 및 추적기 차단과는 다른 방식으로 작동합니다. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS 보호는 일반 광고 및 추적기 차단과는 다른 방식으로 작동합니다. [DNS 보호 및 작동 방식에 대한 자세한 내용은 전용 문서](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work)에서 확인할 수 있습니다. ::: diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index aefad067e83..dc5139b265f 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ sidebar_position: 1 ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index f9856a1973a..ad840151ef1 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ sidebar_position: 2 k. **X-Client-Data 헤더 제거** 이 기능은 Google Chrome이 버전 및 수정 사항에 대한 정보를 Google 도메인(DoubleClick 및 GoogleAnalytics 포함)으로 전송하는 것을 방지합니다. -**추적 보호**에서 개별 설정을 조정하고 사용자 지정 구성을 만들 수 있습니다. 모든 설정에는 해당 역할을 이해하는 데 도움이 되는 설명이 있습니다. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +**추적 보호**에서 개별 설정을 조정하고 사용자 지정 구성을 만들 수 있습니다. 모든 설정에는 해당 역할을 이해하는 데 도움이 되는 설명이 있습니다. [다양한 **추적 보호** 설정의 기능에 대해 자세히 알아보세요](/general/stealth-mode). 일부 설정은 웹사이트 및 브라우저 확장 프로그램의 기능을 방해할 수 있으므로 신중하게 접근하세요. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 69d6660c1a9..2b407369b9e 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ sidebar_position: 7 Android OS의 보안 조치로 인해 일부 AdGuard 기능은 루팅된 기기에서만 사용할 수 있습니다. 이 기능은 다음과 같습니다. -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- 대부분의 앱은 사용자 저장소의 인증서를 신뢰하지 않으므로 **대부분의 앱에서 HTTPS 필터링**을 사용하려면 [시스템 저장소에 CA 인증서를 설치](/adguard-for-android/features/settings#security-certificates)해야 합니다. 시스템 저장소에 인증서를 설치하는 것은 루팅된 기기에서만 가능합니다. - [**자동 프록시 라우팅 모드**](/adguard-for-android/features/settings#routing-mode)에서는 시스템 전체 트래픽 필터링에 대한 Android의 제한으로 인해 루트 액세스 권한이 필요합니다. - [**수동 프록시**](/adguard-for-android/features/settings#routing-mode) 라우팅 모드를 사용하려면 Android 10 이상에서 루트 액세스가 필요하며, AdGuard가 필터링한 연결과 관련된 앱의 이름을 더 이상 확인할 수 없기 때문입니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index dd5508d13d6..95b37f619df 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -27,7 +27,7 @@ sidebar_position: 4 **Watchdog**은 AdGuard가 시스템에 의해 비활성화되지 않도록 보호합니다 ([Android의 배터리 절약 모드에 대해 자세히 알아보기](/adguard-for-android/solving-problems/background-work/)). 입력하는 값은 감시 확인 사이의 간격(초)이 됩니다. -**로깅 수준**은 앱 성능에 대한 어떤 데이터를 기록할지 정의합니다. 기본적으로 앱은 이벤트에 대한 데이터를 수집합니다. **디버그 로깅 수준**은 더 많은 이벤트를 기록합니다. 문제가 있는 경우, 이 수준은 AdGuard 팀이 문제를 더 잘 이해하는 데 도움이 됩니다. 하지만 리소스를 더 많이 소모하므로 지원팀에서 요청하는 경우에만 활성화하는 것이 좋습니다. [Read more about collecting and sending logs](/adguard-for-android/solving-problems/log/) +**로깅 수준**은 앱 성능에 대한 어떤 데이터를 기록할지 정의합니다. 기본적으로 앱은 이벤트에 대한 데이터를 수집합니다. **디버그 로깅 수준**은 더 많은 이벤트를 기록합니다. 문제가 있는 경우, 이 수준은 AdGuard 팀이 문제를 더 잘 이해하는 데 도움이 됩니다. 하지만 리소스를 더 많이 소모하므로 지원팀에서 요청하는 경우에만 활성화하는 것이 좋습니다. [로그 수집 및 전송에 대해 자세히 알아보기](/adguard-for-android/solving-problems/log/) ![고급 \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) @@ -59,7 +59,7 @@ AdGuard는 필터의 규칙을 적용하여 광고, 추적기 및 성가신 광 ### 유저스크립트 -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. 유저스크립트를 설치하려면 특별한 유저스크립트 관리자가 필요합니다. AdGuard에는 이러한 기능이 있으며 URL 또는 파일에서 유저스크립트를 추가할 수 있습니다. +유저스크립트는 하나 이상의 웹사이트의 기능을 확장하는 자바스크립트로 작성된 미니 프로그램입니다. 유저스크립트를 설치하려면 특별한 유저스크립트 관리자가 필요합니다. AdGuard에는 이러한 기능이 있으며 URL 또는 파일에서 유저스크립트를 추가할 수 있습니다. ![유저스크립트 \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ HTTPS 필터링을 통해 AdGuard는 요청 및 응답의 콘텐츠를 필터링 - AdGuard 라이선스를 구매하여 [정식 버전의 기능](/adguard-for-android/features/free-vs-full)을 활성화하세요. - AdGuard 계정에 로그인하거나 라이선스 키를 입력하여 라이선스를 활성화하세요. - 아직 7일 체험판을 사용하지 않았다면 가입하여 활성화하세요. -- Refresh the license status from the three-dots menu (⋮) +- 점 3개 메뉴(:)에서 라이선스 상태를 새로 고칩니다. - AdGuard 계정을 열어 라이선스를 관리하세요. - 이 라이선스의 기기 제한에 도달하여 다른 라이선스를 적용하려면 라이선스를 초기화하세요. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index a7a0512ff80..ed25589d169 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Option 2 To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -199,7 +199,7 @@ On Android 11, Samsung will prevent apps (including AdGuard) from working in bac **Settings** → **Apps** → (⁝) menu → **Special Access** → **Optimize battery usage** → Find AdGuard on the list and uncheck it -1. Disable automatic optimization. 다음와 같이 설정합니다: +1. Disable automatic optimization. To do so: Open **Battery** → (⁝) menu → Choose **Automation** → Toggle off all of the settings there @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 31f2344efa0..596295e647c 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 41c20369ce9..f705bf41563 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index c3d4b4772b2..d046e29f8d4 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: HAR 파일 수집 방법 sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## HAR 파일이란 무엇인가요? -HAR(HTTP ARchive) 형식은 웹 브라우저와 사이트 간의 상호 작용을 로깅하기 위한 JSON 형식의 아카이브 파일로, The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. HAR 파일 형식에 대한 자세한 내용은 [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/)에서 확인하실 수 있습니다. +HAR(HTTP ARchive) 형식은 웹 브라우저와 사이트 간의 상호 작용을 로깅하기 위한 JSON 형식의 아카이브 파일로, 브라우저가 불러오는 웹 페이지에 대한 자세한 정보를 내보내는 데 이용되는 HTTP 트랜잭션에 대한 보관 데이터를 정의합니다. HAR 파일 형식에 대한 자세한 내용은 [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/)에서 확인하실 수 있습니다. -## How to generate HAR files +## HAR 파일 수집 방법 -간혹 재생산하기 어려운 특정 광고를 차단하기 위해 HAR 파일 분석이 필요합니다. To get HAR files, follow these steps: +간혹 재생산하기 어려운 특정 광고를 차단하기 위해 HAR 파일 분석이 필요합니다. HAR 파일을 수집하려면 다음 단계를 따르십시오. 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ HAR(HTTP ARchive) 형식은 웹 브라우저와 사이트 간의 상호 작용 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**.har 파일을 AdGuard 지원 팀에 보내 주세요.** :::note diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c95cc19334d..0e9a4c4a75a 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index 1f4ecaa87b4..e65a8f32938 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. +이 글에서는 디버그 로그를 수집하는 방법을 설명합니다. 디버그 로그는 잠재적으로 복잡한 문제를 해결하는 데 필요합니다. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. :::note @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +**디버그 로그**를 수집하여 저희에게 보내려면 다음 단계를 수행하십시오. 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index c42b3e36b55..868cab2cc0e 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -63,7 +63,7 @@ Here you can specify the response type for domains blocked by DNS rules based on #### 차단된 TTL 응답 -여기에서 차단된 요청에 대한 응답으로 반환할 TTL(유지시간) 값을 지정할 수 있습니다. +Here you can specify the TTL (time to live) value that will be returned in response to a blocked request. #### DNS cache size @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -모든 암호화된 인터넷 연결에는 암호화되지 않은 부분이 있습니다. 이것은 연결하려는 서버의 이름이 포함된 첫 번째 패킷입니다. Encrypted Client Hello 기술은 이 문제를 해결하고 암호화되지 않은 마지막 비트의 정보를 암호화합니다. To benefit from it, enable the *Encrypted Client Hello* option. 로컬 DNS 프록시를 사용하여 도메인에 대한 ECH 구성을 찾습니다. If it is found, Client Hello packet will be encrypted. +모든 암호화된 인터넷 연결에는 암호화되지 않은 부분이 있습니다. 이것은 연결하려는 서버의 이름이 포함된 첫 번째 패킷입니다. Encrypted Client Hello 기술은 이 문제를 해결하고 암호화되지 않은 마지막 비트의 정보를 암호화합니다. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. ECH 구성이 발견되면 ClientHello 패킷이 암호화됩니다. #### OCSP checking @@ -127,7 +127,7 @@ If the verification takes too long, AdGuard will allow the connection while cont If this setting is enabled, AdGuard will redirect DNS-over-HTTPS requests to the local DNS proxy in addition to plain DNS requests. We recommend disabling fallback upstreams and using only encrypted DNS servers to maintain privacy. -#### HTTP/3 필터링 +#### Filter HTTP/3 If this setting is enabled, AdGuard will filter requests sent over HTTP/3 in addition to other request types. @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 97759df30eb..3775ec6d532 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index 1d37f5add81..d25d1324528 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | 프록시 호스트 | *127.0.0.1* | | 프록시 포트 | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### PIA(Private Internet Access)와 함께 AdGuard를 사용하는 방법 @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## 제한 -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 0bfb919e726..f9b463cda8d 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 7dc93068cc5..00000000000 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: 무료 버전과 정식 버전 비교 -sidebar_position: 9 ---- - -:::info - -이 글은 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 iOS용 AdGuard에 관한 것입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 25a22728b4b..e6ff50880c2 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -13,15 +13,15 @@ sidebar_position: 2 ### iPhone -iOS 13 이상이 필요합니다. +Requires iOS 13 or later. ### iPad -iPadOS 13 이상이 필요합니다. +Requires iPadOS 13 or later. ### iPod touch -iOS 13 이상이 필요합니다. +Requires iOS 13 or later. ## iOS용 AdGuard 설치 방법 @@ -29,7 +29,7 @@ iOS용 AdGuard는 App Store에서 다운로드할 수 있는 무료 앱입니다 ![앱스토어 메인 화면에서 검색 누르기 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -검색창에 *adguard*를 입력하고 검색 결과 중 *AdGuard* 문자열을 탭합니다. +검색창에 *adguard*를 입력한 후 표시될 *adGuard*를 탭하세요. ![검색창에 "AdGuard" 입력 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro는 프리미엄 기능을 제공하는 iOS용 AdGuard의 유료 버 ![앱스토어 메인 화면에서 검색 누르기 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -검색 양식에 *adguard*를 입력한 다음 검색 결과 중에 표시되는 *AdGuard Pro — adblock* 문자열을 탭합니다. +검색창에 *adguard*를 입력한 후 표시될 *adGuard pro - adblock*를 탭하세요. ![검색창에 "AdGuard" 입력 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -App Store의 열린 페이지에서 *AdGuard Pro — adblock* 문자열 아래에 라이선스 비용이 표시된 버튼을 탭한 다음 *구매*를 탭합니다. 설치를 완료하려면 Apple ID 로그인 및 암호를 입력하고 설치가 완료될 때까지 기다리십시오. +App Store의 열린 페이지에서 *AdGuard Pro - adblock* 아래에 라이선스 가격이 있는 버튼을 탭한 후 *구매* 버튼을 누릅니다. 설치를 완료하려면 Apple ID 로그인 및 암호를 입력하고 설치가 완료될 때까지 기다리십시오. ![AdGuard 앱 아래에서 받기를 누르기 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index a33ff266853..170bbf41381 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ sidebar_position: 4 1. 동영상을 선택하고 *공유*를 누르세요. 1. *더보기*를 누르고 *YouTube 광고 차단(AdGuard 제공)*을 선택하세요. -이제 동영상은 AdGuard의 광고 없는 플레이어에서 열립니다. +AdGuard가 광고 없는 비디오 플레이어를 열게 됩니다. ## Safari에서 YouTube 광고를 차단하는 방법 @@ -31,4 +31,4 @@ AdGuard에 모든 웹사이트에 대한 접근 권한을 부여했는지 확인 1. 동영상을 선택하고 *공유*를 누르세요. 1. *YouTube 광고 차단(AdGuard 제공)*을 누르세세요. -이제 동영상은 AdGuard의 광고 없는 플레이어에서 열립니다. +AdGuard가 광고 없는 비디오 플레이어를 열게 됩니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index 3865026d657..aaac63c2ea7 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ sidebar_position: 5 두 가지 주요 터널링 모드는 *분할 터널링*과 *풀 터널링*입니다. *분할 터널링* 모드는 AdGuard와 소위 '개인 VPN' 앱의 호환성을 제공합니다. *풀 터널링* 모드에서는 다른 어떤 VPN도 AdGuard와 동시에 작동할 수 없습니다. -*분할 터널링 모드*에는 특정 기능이 있습니다. DNS 프록시 성능이 좋지 않은 경우(예: AdGuard DNS 서버의 응답이 제때에 반환되지 않는 경우) iOS는 대신 iOS 설정에 지정된 DNS 서버를 통해 트래픽을 재라우팅합니다. 현재 광고는 차단되지 않으며 DNS 트래픽은 암호화되지 않습니다. +*분할 터널링* 모드의 특정 기능이 있습니다. DNS 프록시가 제대로 작동하지 않는 경우(예: AdGuard DNS 서버의 응답이 제시간에 반환되지 않는 경우) iOS는 iOS 설정에 지정된 DNS 서버를 통해 트래픽을 리디렉션합니다. 현재 광고는 차단되지 않으며 DNS 트래픽은 암호화되지 않습니다. -*풀 터널링* 모드에서는 AdGuard 설정에 지정된 DNS 서버만 사용됩니다. 응답하지 않으면 인터넷이 작동하지 않는 것입니다. *풀 터널링* 모드를 활성화하면 일부 프로그램(예: FaceTime)의 성능에 부정적인 영향을 미치고 앱 업데이트 문제가 발생할 수 있습니다. +*풀 터널링* 모드에서는 AdGuard 설정에 지정된 DNS 서버만 사용됩니다. 응답하지 않으면 인터넷이 작동하지 않는 것입니다. *풀 터널링* 모드를 활성화하면 일부 프로그램(예: Facetime)의 성능이 저하되고 앱 업데이트에 문제가 발생할 수 있습니다. 기본적으로 AdGuard는 가장 안정적인 *분할 터널링* 모드를 사용합니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md index c2c2c3b2b8e..16fa61e8452 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 9dec4302d8b..93b022ed102 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -1,11 +1,11 @@ --- -title: 고급 설정 +title: Advanced Settings guide sidebar_position: 9 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -13,176 +13,176 @@ sidebar_position: 9 :::caution -*고급 설정*을 변경하면 AdGuard의 성능에 문제가 발생하고 인터넷 연결이 끊기며 보안 및 개인정보가 손상될 수 있습니다. 이러한 설정은 사용자가 무엇을 하고 있는지 확실하거나 지원팀에서 요청하는 경우에만 변경하세요. +Changing *Advanced Settings* may cause problems with AdGuard's performance, break the Internet connection, or compromise your security and privacy. Make changes to this section only if you are sure of what you are doing or our support team has asked you to do it. ::: -*고급 설정*을 찾으려면 AdGuard를 열고 톱니바퀴 아이콘을 클릭한 다음 *고급* → *고급 설정*을 선택합니다. +To find *Advanced Settings*, open AdGuard, click the gear icon, select *Advanced*, then select *Advanced Settings*. ## 고급 설정 -### 네트워크 설정 +### Network settings #### `network.extension.exclude.domains` -나열된 도메인은 *네트워크 확장* 모드에서 필터링에서 제외됩니다. 값을 구분하려면 쉼표나 줄 바꿈을 사용하세요. +The listed domains will be excluded from filtering in the *Network Extension* mode. Use a comma or line break to separate values. #### `network.extension.exclude.ports` -나열된 포트는 *네트워크 확장* 모드에서 필터링에서 제외됩니다. 값을 구분하려면 쉼표나 줄 바꿈을 사용하세요. +The listed ports will be excluded from filtering in the *Network Extension* mode. Use a comma or line break to separate values. #### `network.extension.route.exclude` -나열된 경로는 *네트워크 확장* 모드에서 필터링에서 제외됩니다. IP 주소 또는 대상 CIDR을 사용하여 경로를 설정합니다. 쉼표 또는 줄 바꿈으로 값을 구분합니다. +The listed routes will be excluded from filtering in the *Network Extension* mode. Set routes using an IP address or destination CIDR. Separate values with commas or line breaks. #### `network.extension.http.downgrade.bundleids` -여기에서 *네트워크 확장 필터링 모드*의 HTTP/2 프로토콜을 HTTP/1.1로 다운그레이드할 애플리케이션 목록을 지정할 수 있습니다. 번들 ID는 쉼표 또는 줄 바꿈으로 구분해야 합니다. +Here you can specify a list of applications for which the HTTP/2 protocol will be downgraded to HTTP/1.1 in the *Network Extension* filtering mode. The bundle ID should be separated by a comma or a line break. #### `network.extension.monterey.force.split.tunnel` -여기에서 macOS Monterey의 *네트워크 확장 모드*에서 활성화된 기본 경로를 AdGuard가 사용하지 못하도록 할 수 있습니다. AdGuard는 '기본 경로'를 사용하여 iCloud 비공개 릴레이 및 메일 활동 보호와 함께 작동할 수 없으므로 이를 비활성화합니다. +Here you can prohibit AdGuard from using the "default route" which is enabled by default in the *Network Extension* mode on macOS Monterey. AdGuard uses "default route" to disable iCloud Private Relay and Protect Mail Activity, as it cannot operate in unison with them. -이 문제에 대한 자세한 내용은 [이 문서](../icloud-private-relay)에서 확인할 수 있습니다. +You will find more information about the problem [in this article](../icloud-private-relay). #### `network.extension.dns.redirect.exclude.bundleids` -여기에서 시스템 DNS 리졸버를 거치지 않고 직접 DNS 쿼리를 수행하는 애플리케이션 목록(예: 일부 VPN 클라이언트 또는 DNS 필터링 애플리케이션)을 지정할 수 있습니다. *네트워크 확장 모드*에서는 DNS 필터링이 비활성화됩니다. 번들 ID는 쉼표 또는 줄 바꿈으로 구분해야 합니다. +Here you can specify a list of applications that make DNS queries directly not via system DNS resolver (for example, some VPN clients or DNS filtering applications). DNS filtering will be disabled for them in the *Network Extension mode*. The bundle IDs should be separated by a comma or line break. #### `network.dns.filter.secure.request` -보안 DNS 요청을 로컬 DNS 프록시로 리디렉션합니다(사용 가능한 프록시가 있는 경우). +Redirects secure DNS requests to a local DNS proxy, if there is one available. #### `network.https.ocsp.check` -`true로` 설정하면 HTTPS 인증서 해지 확인을 사용하도록 설정합니다. +By setting `true`, you enable HTTPS certificate revocation checking. #### `network.tcp.keepalive.enabled` -유휴 연결을 통해 주기적으로 TCP 패킷을 전송하여 연결이 활성 상태로 유지되도록 하고 NAT 시간 제한을 갱신합니다. +Periodically sends TCP packets over an idle connection to ensure that it remains active and to renew NAT timeouts. #### `network.tcp.keepalive.interval.seconds` -킵얼라이브 프로브를 보내기 전까지의 유휴 시간(초)입니다. 0이 지정되면 시스템은 기본값을 사용합니다. +Idle time, in seconds, before sending a keepalive probe. If 0 is specified, the system will use the default value. #### `network.tcp.keepalive.timeout.seconds` -응답이 없는 피어에게 다른 킵얼라이브 프로브를 보내기까지의 시간(초)입니다. 0을 지정하면 시스템에서 선택한 값이 사용됩니다. +Time, in seconds, before sending another keepalive probe to an unresponsive peer. If 0 is specified, the value selected by the system will be used. #### `network.https.ech.enabled` -로컬 DNS 프록시를 사용하여 ECH 구성 목록에서 구성을 찾습니다. 찾으면 ClientHello를 암호화합니다. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` -Chrome 인증서 투명성 정책에 따라 도메인의 모든 인증서를 확인합니다. +Verifies the authenticity of all certificates for the domain based on Chrome Certificate Transparency Policy. #### `network.https.filter.http3.enabled` -`true`로 설정하면 AdGuard가 QUIC 기반의 최신 버전의 HTTP 프로토콜인 HTTP/3을 통해 전송되는 트래픽을 필터링할 수 있습니다. +By setting `true`, you allow AdGuard to filter traffic sent over HTTP/3, the latest version of the HTTP protocol based on QUIC. #### `network.filtering.localnetwork` -`true`로 설정하면 로컬 네트워크 필터링이 활성화됩니다. +By setting `true`, you enable local network filtering. #### `network.filtering.localhost` -`true`로 설정하면 LoopBack 필터링이 활성화됩니다. +By setting `true`, you enable LoopBack filtering. -### DNS 설정 +### DNS settings #### `dns.proxy.bootstrap.ips` -여기에서 암호화된 DNS 서버의 주소를 확인하는 데 사용할 DNS 서버의 IP 주소를 입력할 수 있습니다. +Here you can enter the IP addresses of the DNS servers that will be used to determine the address of the encrypted DNS server. #### `dns.proxy.fallback.ips` -여기에서 암호화된 DNS 서버가 응답하지 않을 경우, 백업으로 사용할 DNS 서버의 IP 주소 목록을 지정할 수 있습니다. +Here you can specify a list of IP addresses of DNS servers that will be used as backups in case the encrypted DNS server fails to respond. #### `dns.proxy.fallback.on.upstreams.failure.enabled` -모든 일반 업스트림이 실패하면 일반 쿼리는 폴백 업스트림으로 리디렉션됩니다. +Normal queries will be redirected to a fallback upstream if all normal upstreams fail. #### `dns.proxy.detect.search.domains` -이 옵션을 사용하면 로컬 네트워크 도메인을 자동으로 감지하여 기본 DNS 서버 대신 폴백 DNS 서버로 자동 리디렉션할 수 있습니다. +This option enables automatic detection of the local network domain, which will be automatically redirected to the fallback DNS server instead of the main DNS server. #### `dns.proxy.fallback.domains` -여기에서 기본 DNS 서버 대신 폴백 DNS 서버를 사용할 도메인을 나열할 수 있습니다. +Here you can list domains for which the fallback DNS server will be used instead of the main DNS server. #### `dns.proxy.adblockrules.blocking.mode` -여기에서 광고 차단기 스타일 규칙에 해당하는 차단된 요청에 대한 DNS 서버 응답 유형을 지정할 수 있습니다. +Here you can specify the type of DNS server response to blocked requests, corresponding to ad-blocker-style rules. -- 0 — REFUSED로 응답 -- 1 — NXDOMAIN으로 응답 -- 2 - 0.0.0.0 또는 `dns.proxy.blocking.response.IPv4.address` 및/또는 `dns.proxy.blocking.response.IPv6.address`에 지정된 주소로 응답합니다. +- 0 — respond with REFUSED +- 1 — respond with NXDOMAIN +- 2 — respond with 0.0.0.0 or the addresses specified in `dns.proxy.blocking.response.IPv4.address` and/or `dns.proxy.blocking.response.IPv6.address` #### `dns.proxy.hostrules.blocking.mode` -여기에서 호스트 규칙에 해당하는 차단된 요청에 대한 DNS 서버 응답 유형을 지정할 수 있습니다. +Here you can specify the type of DNS server response to blocked requests, corresponding to hosts rules: -- 0 — REFUSED로 응답 -- 1 — NXDOMAIN으로 응답 -- 2 - 0.0.0.0 또는 `dns.proxy.blocking.response.IPv4.address` 및/또는 `dns.proxy.blocking.response.IPv6.address`에 지정된 주소로 응답합니다. +- 0 — respond with REFUSED +- 1 — respond with NXDOMAIN +- 2 — respond with 0.0.0.0 or the addresses specified in `dns.proxy.blocking.response.IPv4.address` and/or `dns.proxy.blocking.response.IPv6.address` #### `dns.proxy.blocking.response.IPv4.address` -여기에서 `dns.proxy.adblockrules.blocking.mode` 또는 `dns.proxy.hostrules.blocking.mode`가 응답 유형 'ADDRESS'로 설정된 경우 차단된 'A' 요청에 대한 응답으로 반환될 IPv4 주소를 지정할 수 있습니다. +Here you can specify the IPv4 address that will be returned in response to blocked "A" requests when `dns.proxy.adblockrules.blocking.mode` or `dns.proxy.hostrules.blocking.mode` is set to the response type "ADDRESS". #### `dns.proxy.blocking.response.IPv6.address` -여기에서 `dns.proxy.adblockrules.blocking.mode` 또는 `dns.proxy.hostrules.blocking.mode`가 응답 유형 'ADDRESS'로 설정된 경우 차단된 'AAAA' 요청에 대한 응답으로 반환될 IPv6 주소를 지정할 수 있습니다. +Here you can specify the IPv6 address that will be returned in response to blocked "AAAA" requests when `dns.proxy.adblockrules.blocking.mode` or `dns.proxy.hostrules.blocking.mode` is set to the response type "ADDRESS". #### `dns.proxy.block.AAAA.requests` -여기에서 IPv6 DNS 쿼리 차단을 활성화할 수 있습니다. +Here you can enable IPv6 DNS query blocking. #### `dns.proxy.blocked.response.TTL.in.seconds` -여기에서 차단된 요청에 대한 응답으로 반환할 TTL(유지시간) 값을 지정할 수 있습니다. +Here you can specify the TTL (time to live) value that will be returned in response to a blocked request. #### `dns.proxy.parallel.upstream.queries.enabled` -모든 업스트림이 동시에 쿼리됩니다. 첫 번째 응답이 반환됩니다. +All upstreams are queried simultaneously. The first response is returned. #### `dns.proxy.servfail.on.upstreams.failure.enabled` -SERVFAIL 패킷으로 업스트림 실패에 응답합니다. +Responds to upstream failure with a SERVFAIL packet. #### `dns.proxy.http3.enabled` -DNS-over-HTTPS 업스트림에 HTTP/3을 활성화하여 연결을 가속화합니다. +Enables HTTP/3 for DNS-over-HTTPS upstreams to accelerate connection. #### `dns.proxy.block.encrypted.client.hello.response` -응답에서 Encrypted Client Hello 매개 변수를 제거합니다. +Removes the Encrypted Client Hello parameters from responses. -### 스텔스 모드 설정 +### Stealth Mode settings #### `stealth.antidpi.http.split.fragment.size` -HTTP 요청 조각화의 크기를 조정합니다. 유효한 값은 1~1500입니다. 잘못된 크기를 지정하면 시스템에서 기본값을 사용합니다. +Adjusts the size of the HTTP request fragmentation. Valid values: 1–1500. If an invalid size is specified, the system will use the default value. #### `stealth.antidpi.clienthello.split.fragment.size` -이 옵션은 심층 패킷 검사를 피하는 데 도움이 되는 TCP 패킷 조각화 크기를 지정합니다. 유효한 값은 1~1500입니다. 잘못된 크기를 지정하면 시스템에서 기본값을 사용합니다. +This option specifies the size of TCP packet fragmentation, which helps avoid deep packet inspection. Valid values: 1–1500. If an invalid size is specified, the system will use the default value. #### `stealth.antidpi.http.space.juggling` -HTTP 메서드와 URL 사이에 공백을 추가하고 'Host:' 필드 뒤의 공백을 제거합니다. +Adds extra space between the HTTP method and the URL and removes space after the "Host:" field. #### `stealth.antidpi.split.delay.millisecond` -여기에서 조각화가 수행되는 경우, 첫 번째 조각을 전송한 후 지연 시간을 밀리초 단위로 지정할 수 있습니다. +Here you can specify the delay, in milliseconds, after sending the first fragment, if fragmentation is performed. -### 구독 링크 차단 설정(사용자 스크립트 및 필터) +### Subscription link interception settings (userscripts and filters) #### `subscription.link.interception.userscript` -AdGuard가 유저스크립트의 URL을 자동으로 가로채고 설치 창을 열도록 하려면 이 기능을 활성화하세요. +Activate this feature if you want AdGuard to automatically intercept the URLs of userscripts and open the installation window. #### `subscription.link.interception.filter` -AdGuard가 자동으로 구독 URL(예: abp:subscribe 등)을 가로채도록 하려면 이 기능을 활성화하고 사용자 정의 필터 설정 창을 엽니다. +Activate this feature if you want AdGuard to automatically intercept subscription URLs (for example, abp:subscribe, etc.) and open the custom filter setup window. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 0fd24f93662..ad9964caafc 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -1,112 +1,112 @@ --- -title: 다른 macOS 버전과의 호환성 문제 +title: Compatibility issues with different macOS versions sidebar_position: 4 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -## 현재 존재하는 문제 +## Currently existing problems -매년 Apple은 혁신적인 솔루션을 도입하고 새롭고 유용한 기능을 추가하는 새로운 버전의 macOS를 출시합니다. 그러나 네트워크 확장 API(Big Sur) 또는 iCloud 비공개 릴레이(Monterey)와 같은 일부는 많은 애플리케이션에 몇 가지 문제를 일으키며, AdGuard도 예외는 아닙니다. 이 도움말에서는 각 macOS 버전별로 알려진 문제와 이를 해결할 수 있는 방법을 살펴봅니다. +Every year Apple releases a new version of macOS, introducing innovative solutions and adding new useful features. But some of them, such as Network Extensions API (Big Sur) or iCloud Private Relay (Monterey), cause some problems to many applications, AdGuard not being an exception. In this article we go over the known issues specific to each macOS version and possible ways to solve them. -### Monterey 12: 현재 존재하는 문제 +### Monterey 12: currently existing problems -이러한 문제는 아직 Apple에서 해결되지 않았거나 부분적으로만 해결되었습니다. +These problems aren't fixed by Apple yet, or fixed only partially. -#### iCloud 비공개 릴레이와의 호환성 +#### Compatibility with iCloud Private Relay -현재 AdGuard와 iCloud 비공개 릴레이는 동시에 작동할 수 없습니다. AdGuard가 네트워크 연결을 필터링하기 전에 iCloud 비공개 릴레이가 트래픽을 암호화하기 때문에 광고를 차단할 수 없습니다. iCloud 비공개 릴레이가 활성화되면 모든 필터링(로컬 필터링 포함)이 불가능해집니다. 따라서 AdGard는 Safari에서 트래픽을 필터링하거나 DNS 필터링을 수행할 수 없습니다. 그렇기 때문에 AdGuard는 기본적으로 iCloud 비공개 릴레이를 비활성화하는 '기본 경로'를 사용합니다. +Currently, AdGuard and iCloud Private Relay cannot work at the same time. AdGuard has no ability to block ads because iCloud Private Relay encrypts traffic before AdGuard can filter network connections. When iCloud Private Relay is active, any filtering (including local filtering) becomes impossible. Thus, AdGuard can't filter traffic or perform DNS filtering in Safari. That's why by default, AdGuard uses the "default route" which disables iCloud Private Relay. -이 문제에 대해 자세히 알아보려면 [이 도움말 문서](../icloud-private-relay)를 참조하세요. +For a deeper understanding of this problem, read [this article](../icloud-private-relay). -**권장 솔루션** +**Recommended solution** -[AdGuard VPN](https://adguard-vpn.com/)과 같은 기존 VPN 서비스와 함께 사용하는 것을 권장합니다. +We recommend using AdGuard together with a more traditional VPN service such as [AdGuard VPN](https://adguard-vpn.com/). -**대안 솔루션** +**Alternative solution** -'기본 경로'를 비활성화하여 AdGuard가 '기본 경로'를 사용하지 못하도록 할 수 있습니다. 고급 설정 → `network.extension.monterey.force.split.tunnel`을 통해 이 작업을 수행할 수 있습니다. 이 설정을 활성화하면 위에서 설명한 문제가 발생할 수 있습니다. +You can prevent AdGuard from using the "default route" by disabling it. It can be done via Advanced Settings → `network.extension.monterey.force.split.tunnel`. Note that enabling this setting will cause the problems described above. -![고급 설정 *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_adguard_advanced_settings.jpg) +![Advanced Settings *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_adguard_advanced_settings.jpg) -#### 메일의 개인 정보 보호(Protect Mail Activity)와의 호환성 +#### Compatibility with Protect Mail Activity -이제 Apple의 메일 앱은 이메일에서 이미지를 다운로드할 때 프록시를 사용하여 사용자의 IP 주소를 숨깁니다. 하지만 활성 VPN 연결이 있는 경우에는 작동하지 않습니다. AdGuard를 VPN으로 취급하기 때문에 이미지를 자동으로 미리 로드하지 않습니다. +Apple's Mail app now uses a proxy to hide a user's IP address when downloading images from emails. However, it won't work if there's an active VPN connection. As it treats AdGuard as a VPN, it won't preload images automatically. -이 문제에 대해 자세히 알아보려면 [이 도움말 문서](../protect-mail-activity)를 참조하세요. +For a deeper understanding of this problem, read [this article](../protect-mail-activity). -**권장 솔루션** +**Recommended solution** -현재로서는 최신 Apple 개인정보 보호 기능 대신 [AdGuard VPN](https://adguard-vpn.com/)과 같은 일반적인 VPN 서비스를 사용하는 것을 권장합니다. +At this point, we recommend using a more traditional VPN service, such as [AdGuard VPN](https://adguard-vpn.com/), instead of the newer Apple privacy features. -### Monterey 12, Big Sur 11.6 이후 버전: 현재 존재하는 문제 +### Monterey 12, Big Sur 11.6 and later: currently existing problems -이러한 문제는 아직 Apple에서 해결되지 않았거나 부분적으로만 해결되었습니다. +These problems aren't fixed by Apple yet, or fixed only partially. -#### Cisco AnyConnect와의 호환성 +#### Compatibility with Cisco AnyConnect -AdGuard는 *네트워크 확장* 모드에서는 Cisco AnyConnect와 함께 작동하지 않습니다. AdGuard를 *자동 프록시* 모드로 전환해야 합니다. 이렇게 하려면 [다음 지침](#automatic-proxy)을 따르세요. +AdGuard will not work together with Cisco AnyConnect while in the *Network Extension* mode. You have to switch AdGuard to *Automatic Proxy* mode. To do so, follow [this instruction](#automatic-proxy). -#### Flutter와의 호환성 +#### Compatibility with Flutter -이 문제는 2021년 6월에 출시된 Flutter 2.2에서 해결되었습니다. 하지만 Flutter에서 개발된 애플리케이션에서 이 문제를 해결하려면 업데이트를 기다려야 합니다. +This problem is solved in Flutter 2.2, released in June 2021. But to fix it for applications developed in Flutter, you need to wait for updates. -Monterey 또는 Big Sur에서 '네트워크 확장' 모드(또는 기타 '투명 프록시' 유형 앱)에서 AdGuard와 함께 Flutter를 사용하는 경우, 프로젝트가 열리지 않고 Flutter가 사실상 중단되는 문제가 발생할 수 있습니다. 이미 이 버그를 Apple에 신고했습니다. 그동안 다음과 같은 임시 해결책을 사용할 수 있습니다. +If you use Flutter alongside AdGuard in "Network Extension" mode (or any other "Transparent Proxy"-type app) in Monterey or Big Sur, you will run into problems: projects won't open and Flutter will be effectively broken. We have already reported this bug to Apple. Meanwhile, you can use these temporary solutions: -1. [자동 프록시](#automatic-proxy) 모드에서 AdGuard를 사용하세요. +1. Use AdGuard in [Automatic Proxy](#automatic-proxy) mode. -1. [여기](#kernel-extension)에 설명된 대로 SIP를 비활성화하고 AdGuard를 커널 확장 모드로 전환합니다. +1. Disable SIP and switch AdGuard to Kernel Extension mode as explained [here](#kernel-extension). -#### 이전 API를 사용하는 VPN 앱 +#### VPN apps with legacy API -AdGuard는 시스템 설정에서 VPN으로 표시되지만, 다른 VPN 기반 앱과 함께 사용할 때 충돌을 일으키지 않습니다. 그러나 App Store 외부에서 다운로드한 VPN 기반 앱을 사용하는 경우, 이전 VPN API를 사용할 위험이 있으므로 필터링에서 제외해야 합니다. +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: -1. AdGuard의 메뉴를 엽니다. -1. *설정...*을 선택합니다. -1. *네트워크* 탭으로 전환합니다. -1. *애플리케이션...* 버튼을 클릭합니다. -1. 제외하려는 앱을 찾아 옆에 있는 확인란을 선택 취소합니다. +1. Open AdGuard's menu. +1. Select *Preferences...*. +1. Switch to the *Network* tab. +1. Click the *Applications...* button. +1. Find the app you want to exclude and uncheck the checkbox next to it. -![필터링된 애플리케이션](https://cdn.adtidy.org/content/kb/ad_blocker/mac/legacy.jpg) +![Filtered applications](https://cdn.adtidy.org/content/kb/ad_blocker/mac/legacy.jpg) -## 이미 해결된 문제 +## Already fixed problems -이러한 문제는 현재 Apple에서 수정되었지만 이전 버전의 macOS Big Sur에서 발생할 수 있습니다. +These problems have been fixed by Apple by now but can be encountered in the older versions of macOS Big Sur. -### Little Snitch 5와의 호환성 +### Compatibility with Little Snitch 5 -현재 AdGuard의 네트워크 확장 모드는 [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html)와 호환되지 않습니다. 두 가지를 모두 실행하면 AdGuard에서 필터링하지 않더라도 다양한 앱의 동작에 문제가 발생할 위험이 있습니다. 이 문제는 Big Sur의 버그로 인해 직접적으로 발생했으며, 이미 Apple에 이 사실을 알렸습니다. 따라서 다음 업데이트 중 하나에서 이 문제가 해결될 것으로 예상됩니다. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -하지만 Little Snitch에서 연결 모니터링을 비활성화해도 시스템 메모리에서 Little Snitch 확장 프로그램이 언로드되지 않으므로 문제가 해결되지는 않습니다. 최소한 Apple이 버그를 수정할 때까지는 Big Sur에서 Little Snitch와 함께 AdGuard를 실행할 때 [**자동 프록시**](#automatic-proxy) 필터링 모드로 전환할 것을 권장합니다. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. -### 로컬 프록시와의 호환성 +### Compatibility with local proxies :::note -이제 AdGuard는 문제 없이 로컬 프록시를 필터링할 수 있습니다. OS 버전 11.1 이상에서 문제가 발생하거나 Big Sur 11.0을 사용하는 경우, 시스템 설정에서 로컬 프록시를 제거하고 아래 지침에 따라 AdGuard에서 업스트림 프록시를 구성하세요. +Now AdGuard can filter local proxies (mostly) without any problems. If you encounter any issues in OS versions 11.1+, or if you're using Big Sur 11.0, remove the local proxy from System settings and configure an upstream proxy in AdGuard by following the instruction below. ::: -Big Sur의 Mac용 AdGuard에서 업스트림 프록시를 구성하려면 다음과 같이 하세요. +To configure an upstream proxy in AdGuard for Mac in Big Sur: -1. AdGuard의 설정 *설정 → 네트워크 → 아웃바운드 프록시*를 엽니다. -2. 프록시 유형에 따라 HTTP, HTTPS, SOCKS4 또는 SOCKS5를 선택합니다. -3. 다음 필드를 입력하세요. - - `host`는 프록시 서버의 IP 주소입니다. - - `port`는 프록시 서버에서 사용할 원하는 포트 번호입니다. - - `user`와 `password`는 프록시의 해당 사용자 아이디와 비밀번호(필요한 경우)입니다. 해당되지 않는 경우 둘 중 하나 또는 둘 다 무시합니다. +1. Open AdGuard's settings *Preferences → Network → Outbound proxy*. +2. Choose HTTP, HTTPS, SOCKS4 or SOCKS5, depending on your proxy type. +3. Fill in the fields: + - `host` is the IP address of your proxy server, + - `port` is the desired port number to be used by the proxy server, + - `user` and `password` are corresponding username and password of your proxy (if needed). Ignore either or both when not applicable. -문제가 발생하면 기술 지원팀(support@adguard.com)으로 문의하시기 바랍니다. +If you run into any problems, please contact our tech support at support@adguard.com. -#### 예제 1: 업스트림 Shadowsocks 프록시 구성 +#### Example 1: Configuring an upstream Shadowsocks proxy -다음은 [Shadowsocks](https://shadowsocks.org)에 대한 업스트림 프록시를 구성하는 방법의 예시입니다. +Here's an example of how to configure an upstream proxy for [Shadowsocks](https://shadowsocks.org). -우선, 프록시를 위한 서버 측이 작동해야 합니다. 대부분의 경우 다음과 같은 JSON 파일을 사용하여 설정합니다(`server` 및 `password` 값은 여기서 임의로 선택됨): +First of all, you need a working server side for your proxy. Most likely, to set it up, you would use a JSON file like this (`server` and `password` values were chosen randomly here): ```json { @@ -121,82 +121,82 @@ Big Sur의 Mac용 AdGuard에서 업스트림 프록시를 구성하려면 다음 :::tip -시작하는 방법에 대한 자세한 내용은 [Shadowsocks 웹사이트](https://shadowsocks.org/guide/what-is-shadowsocks.html)에서 확인할 수 있습니다. +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: -그런 다음 Mac에 Shadowsocks 클라이언트를 설치해야 합니다. 설정에서 '수동 모드' 또는 '자동 모드'를 선택했는지 확인하세요. 'Global Mode'(또는 11.1 이전 Big Sur 버전에서는 '자동 모드')를 선택하면 구성이 작동하지 않습니다. +Then you'd have to install Shadowsocks client on your Mac. Make sure that you select 'Manual Mode' or 'Auto Mode' in its settings! The configuration won't work if you select 'Global Mode' (or 'Auto Mode' in Big Sur versions prior to 11.1). -![설정에서 수동 모드 또는 자동 모드를 선택하세요 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/mac/shadowsocks.jpg) +![Select Manual Mode or Auto Mode in settings *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/mac/shadowsocks.jpg) -이제 *AdGuard 메뉴 → 고급 → 고급 설정...*으로 이동하여 `upstream.proxy` 설정의 *값* 영역을 `socks5://localhost:1080`으로 설정합니다. 여기서 JSON 파일의 'local_port' 값을 사용해야 한다는 점에 유의하세요. +Now go to *AdGuard menu → Advanced → Advanced Settings...* and set the *Value* area of the `upstream.proxy` setting to `socks5://localhost:1080`. Notice that you need to use "local_port" value from the JSON file here. -Shadowsocks는 SOCKS5를 사용하기 때문에 AdGuard 고급 설정에서 `upstream.proxy.socks5udp` 설정 값을 `true`로 설정해야 AdGuard가 UDP 트래픽을 프록시 서버로 라우팅할 수 있습니다. +Because Shadowsocks uses SOCKS5, you also need to set the value of the `upstream.proxy.socks5udp` setting in AdGuard Advanced Settings to `true` to make AdGuard route UDP traffic to the proxy server. -#### 예제 2: 업스트림 Surge 프록시 구성 +#### Example 2: Configuring an upstream Surge proxy -Big Sur v11.1+에서는 AdGuard와 Surge 프록시 간에 알려진 충돌이 없습니다. 이전 버전의 Big Sur(11.1 이전 버전)를 사용 중인 경우 오른쪽 하단의 **시스템 프록시**가 비활성화되어 있는지 확인하세요. 그렇지 않으면 Surge는 AdGuard와 함께 작동하지 않습니다. 반면에 **Enhanced Mode**는 모든 Big Sur 버전에서 충돌을 일으키지 않고 활성화할 수 있습니다. +In Big Sur v11.1+, there are no known conflicts between AdGuard and Surge proxy. If you are using an older version of Big Sur (prior to 11.1), check that **System Proxy** in the bottom right corner is disabled. Otherwise, Surge won't work with AdGuard. On the other hand, **Enhanced Mode** can be enabled without causing a conflict in any Big Sur version. -![업스트림 Surge 프록시 구성 *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/outbound-proxy.png) +![Configuring an upstream Surge proxy *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/outbound-proxy.png) -이제 *설정 → 네트워크 → 아웃바운드 프록시*로 이동하여 입력란을 채웁니다. SOCKS5 프록시 유형의 경우: +Now go to *Preferences → Network → Outbound proxy* and fill in the fields. For SOCKS5 proxy type: - `host`: localhost -- `포트`: 6153 HTTP 프록시 유형의 경우: +- `port`: 6153 For HTTP proxy type: - `host`: localhost - `port`: 6152 -## 네트워크 확장(Network Extension) 대신 사용할 수 있는 방법 +## Alternatives to using a Network Extension -Big Sur나 Monterey에서 발생할 수 있는 모든 문제를 예측하는 것은 불가능하며, 하드웨어/소프트웨어 및 설정 구성은 무수히 다양합니다. 호환성 문제가 발생하면 지원팀에 문의하시되, 먼저 이러한 해결 방법 중 하나를 시도해 보세요. +It's impossible to foresee each and every possible problem that can pop up in Big Sur or Monterey, there are countless various hardware/software and settings configurations. If you face any compatibility issues, please contact our support team, but feel free to try one of these workarounds first. -### '자동 프록시' 필터링 모드 사용 {#automatic-proxy} +### Using "Automatic proxy" filtering mode {#automatic-proxy} -위의 방법으로 해결할 수 없는 문제가 Big Sur 또는 Monterey에서 발생하는 경우, AdGuard를 *자동 프록시* 모드로 전환해 보세요. +If you face problems in Big Sur or Monterey which can't be resolved by any of the methods above, you can try switching AdGuard to *Automatic proxy* mode. -1. AdGuard의 메뉴를 엽니다. -1. *설정...*을 선택합니다. -1. *네트워크* 탭으로 전환합니다. -1. *모드 선택...* 버튼을 클릭합니다. -1. *자동 프록시*를 선택합니다. +1. Open AdGuard's menu. +1. Select *Preferences...*. +1. Switch to the *Network* tab. +1. Click the *Select Mode...* button. +1. Select *Automatic Proxy*. -![AdGuard를 자동 프록시 모드로 전환하기](https://cdn.adtidy.org/content/kb/ad_blocker/mac/automatic-proxy_en.jpg) +![Switch AdGuard to Automatic proxy mode](https://cdn.adtidy.org/content/kb/ad_blocker/mac/automatic-proxy_en.jpg) -이제 AdGuard가 Mac의 네트워크 설정에 **.pac** 파일을 자동으로 추가하여 시스템이 AdGuard를 프록시로 간주하고 모든 트래픽을 AdGuard를 통해 전송하려고 시도합니다. +Now AdGuard has automatically added a **.pac** file to your Mac's network settings, so that the system will consider AdGuard a proxy and try to send all traffic through AdGuard. :::note -일부 앱은 이 시스템 설정을 무시하고 트래픽이 필터링되지 않을 수 있습니다. +Some apps may ignore this system setting and their traffic will not be filtered. ::: -### Big Sur 및 Monterey에서 커널 확장 프로그램 활성화 {#kernel-extension} +### Enabling Kernel Extension in Big Sur and Monterey {#kernel-extension} -Big Sur 및 Monterey에서는 기존 커널 확장 프레임워크가 비활성화되어 있으므로 기본적으로 AdGuard는 네트워크 확장 프레임워크를 사용합니다. 이로 인해 일부 호환성 문제가 발생할 수 있지만 커널 확장 프로그램을 다시 사용하려면 먼저 SIP(System Integrity Protection, 시스템 무결성 보호)를 비활성화해야 합니다. SIP를 비활성화하려면 다음 지침을 따르세요. +By default AdGuard uses Network Extension framework in Big Sur and Monterey as the old Kernel Extension framework is disabled there. This can cause some compatibility problems, but to enable Kernel Extension back, you need to disable System Integrity Protection (SIP) first. To disable SIP, follow this instruction: -1. 메뉴 표시줄에서 *Apple 기호*를 클릭합니다. -1. *다시 시작...*을 클릭합니다. -1. *Command-R*을 길게 눌러 복구 모드로 재부팅합니다. -1. *유틸리티*를 클릭합니다. -1. *터미널*을 선택합니다. -1. `csrutil disable`을 입력합니다. -1. 키보드에서 *Return* 또는 *Enter* 키를 누릅니다. -1. 메뉴 표시줄에서 *Apple 기호*를 클릭합니다. -1. *다시 시작...*을 클릭합니다. +1. Click the *Apple symbol* in the Menu bar. +1. Click *Restart…* +1. Hold down *Command-R* to reboot into Recovery Mode. +1. Click *Utilities*. +1. Select *Terminal*. +1. Type `csrutil disable`. +1. Press *Return* or *Enter* on your keyboard. +1. Click the *Apple symbol* in the Menu bar. +1. Click *Restart…* -이제 SIP가 비활성화되었으므로 커널 확장 프로그램을 사용하도록 설정하는 방법은 다음과 같습니다. +Now that SIP is disabled, this is how you enable Kernel Extension: -![커널 확장 프로그램 활성화](https://cdn.adtidy.org/content/kb/ad_blocker/mac/kernel_en.jpg) +![Enable Kernel Extension](https://cdn.adtidy.org/content/kb/ad_blocker/mac/kernel_en.jpg) -1. AdGuard의 메뉴를 엽니다. -1. *설정...*을 선택합니다. -1. *네트워크* 탭으로 전환합니다. -1. *모드 선택...* 버튼을 클릭합니다. -1. *커널 확장 프로그램*을 선택합니다. -1. 커널 확장 프로그램으로 전환할 것인지 확인합니다. +1. Open AdGuard's menu. +1. Select *Preferences...*. +1. Switch to the *Network* tab. +1. Click the *Select Mode...* button. +1. Select *Kernel Extension*. +1. Confirm that you want to switch to Kernel Extension. :::caution -그러나 이 방법은 예기치 않은 문제가 발생할 수 있으므로 다른 모든 방법이 실패한 경우에만 사용하는 것이 좋습니다. +However, we only recommend using this method if everything else fails, as this may lead to unexpected issues. ::: diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index fe73f71617a..d0f07913de3 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -1,16 +1,16 @@ --- -title: macOS High Sierra 이상에 AdGuard를 설치하는 방법 +title: How to install AdGuard on macOS High Sierra and above sidebar_position: 3 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -macOS High Sierra(또는 그 이후 버전)에 AdGuard를 설치하는 동안 다음과 같은 메시지가 표시될 수 있습니다: '시스템 확장 차단됨'. 이것은 High Sierra에 등장한 새로운 보안 메커니즘으로, 타사 시스템 확장 프로그램의 설치를 명시적으로 허용해야 합니다. AdGuard 설치를 완료하려면 *시스템 환경설정* → *개인정보 보호와 보안* → *일반*에서 확장 프로그램 로드를 수동으로 허용해야 합니다. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. -![설정에서 확장 프로그램 설치 허용](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) +![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) -'허용' 버튼을 클릭하면 정상적으로 설치를 진행할 수 있습니다. +Click the "Allow" button, and after that you will be able to proceed with the installation as normal. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md index 5e484453828..f85bcabf451 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md @@ -1,48 +1,48 @@ --- -title: iCloud Private Relay 및 AdGuard +title: iCloud Private Relay and AdGuard sidebar_position: 7 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -## 문제 설명 +## Problem description in a nutshell -기본적으로 AdGuard는 iCloud 비공개 릴레이를 비활성화하는 '기본 경로'를 사용합니다. +By default, AdGuard uses the "default route" which disables iCloud Private Relay. -현재 AdGuard와 iCloud 비공개 릴레이는 동시에 작동할 수 없습니다. AdGuard가 네트워크 연결을 필터링하기 전에 iCloud 비공개 릴레이가 트래픽을 암호화하기 때문에 광고를 차단할 수 없습니다. iCloud 비공개 릴레이가 활성화되면 모든 필터링(로컬 필터링 포함)이 불가능해집니다. 따라서 AdGard는 Safari에서 트래픽을 필터링하거나 DNS 필터링을 수행할 수 없습니다. 하지만 AdGuard는 여전히 다른 브라우저의 트래픽을 필터링합니다. iCloud 비공개 릴레이를 계속 사용하려면 [Safari용 AdGuard](https://adguard.com/adguard-safari/overview.html)를 설치하는 것이 좋습니다. +Currently, AdGuard and iCloud Private Relay cannot work at the same time. AdGuard cannot block ads because iCloud Private Relay encrypts traffic before AdGuard can filter network connections. When iCloud Private Relay is active, any filtering (including local filtering) becomes impossible. Thus, AdGuard can't filter traffic or perform DNS filtering in Safari. Yet, AdGuard still filters traffic in other browsers. To keep using iCloud Private Relay, consider installing [AdGuard for Safari](https://adguard.com/adguard-safari/overview.html). -Mac에서 VPN 앱을 사용할 때도 마찬가지입니다. iCloud 비공개 릴레이 또는 VPN 서비스 중 하나를 선택해야 합니다. +The same applies to using any VPN apps on Mac: you have to choose between using iCloud Private Relay or a VPN service. -## 문제에 대한 자세한 설명 +## In detail -이제 Mac용 AdGuard는 네트워크 확장 API를 기반으로 하는 macOS 내장 소켓 필터링을 사용합니다. 이 새롭고 다소 버그가 많은 메커니즘은 기존의 커널 확장 프로그램을 대체했습니다. 지난 1.5년 동안 저희는 새로운 필터링 방식과 관련하여 20개(!) 이상의 버그를 Apple에 보고했습니다. +AdGuard for Mac now uses macOS built-in socket filtering based on the network extensions API. This new and rather buggy mechanism replaced good old Kernel extensions. Over the last 1.5 years, we've reported more than 20(!) bugs to Apple regarding their new filtering method. -네트워크 확장 API에는 경로와 유사한 항목 목록이 있는 VPN과 유사한 구성이 있습니다. Big Sur에서는 초기 Big Sur 릴리스에서 문제를 일으키는 '기본 경로' 규칙을 만들지 않기 위해 AdGuard는 '분할 터널링' 규칙을 개발했습니다. +The network extensions API has a VPN-like configuration with a list of route-like entries. On Big Sur, AdGuard developed "split-tunnel" rules to avoid creating the "default route" rule because it causes problems on early Big Sur releases. -Monterey에서 iCloud 비공개 릴레이가 도입되었습니다. 메일 앱의 개인정보 보호 기능도 iCloud 비공개 릴레이 서버를 사용합니다. +On Monterey, iCloud Private Relay got introduced. Privacy features of the Mail app also use Private Relay servers. -따라서 AdGuard는 iCloud 비공개 릴레이 및 메일 앱 개인정보 보호 기능과 함께 사용할 수 없습니다. +As a consequence, AdGuard can't work together with iCloud Private Relay and the Mail app privacy features: -1. iCloud 비공개 릴레이는 AdGuard가 작동하는 소켓 레벨에 도달하기 전에 라이브러리 레벨의 연결에 적용됩니다. -2. iCloud 비공개 릴레이는 아직 HTTP/3 필터링을 사용할 수 없기 때문에 AdGuard가 필터링된 앱에서 필터링할 수 없는 QUIC을 사용합니다. -3. 따라서 AdGuard는 iCloud 비공개 릴레이 트래픽을 포함한 QUIC을 차단합니다. 그렇지 않으면 광고 차단이 불가능합니다. -4. iCloud 비공개 릴레이를 사용하고 AdGuard를 '분할 터널링' 모드로 전환하면 Safari에서 웹사이트를 열 수 없습니다. -5. Monterey에서 이 문제를 해결하기 위해 '기본 경로' 규칙을 적용합니다. 비공개 릴레이가 해당 규칙을 발견하면 자동으로 비활성화됩니다. 따라서 AdGuard는 Monterey에서 원활하게 작동하지만 iCloud 비공개 릴레이는 비활성화됩니다. +1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. +2. iCloud Private Relay uses QUIC, which AdGuard can't filter in filtered apps because HTTP/3 filtering is not yet available. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic — otherwise, ad blocking is impossible. +4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. +5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. -`network.extension.monterey.force.split.tunnel`은 'Big Sur' 동작을 복원하지만 이 옵션은 (3) 및 (4)로 인해 웹사이트에 대한 액세스가 중단될 수 있습니다. 저희는 이 문제에 대한 해결책을 계속 찾고 있습니다. 옵션 중 하나는 HTTP/3 필터링을 구현하는 것입니다. +`network.extension.monterey.force.split.tunnel` restores the "Big Sur" behavior, but this option may break access to websites due to (3) and (4). We keep searching for a solution to this issue. One of the options is implementing HTTP/3 filtering. -## 권장 솔루션 +## Recommended solution -[AdGuard VPN](https://adguard-vpn.com/)과 같은 기존 VPN 서비스와 함께 사용하는 것을 권장합니다. +We recommend using AdGuard together with a more traditional VPN service such as [AdGuard VPN](https://adguard-vpn.com/). -## 대안 솔루션 +## Alternative solution -'기본 경로'를 비활성화하여 AdGuard가 '기본 경로'를 사용하지 못하도록 할 수 있습니다. 고급 설정 → `network.extension.monterey.force.split.tunnel`을 통해 이 작업을 수행할 수 있습니다. +You can prevent AdGuard from using the "default route" by disabling the "default route". It can be done via Advanced Settings → `network.extension.monterey.force.split.tunnel`. -![고급 설정에서 기본 경로 비활성화 *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_adguard_advanced_settings.jpg) +![Disable default route in advanced settings *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_adguard_advanced_settings.jpg) -이 경우 위에서 설명한 문제가 발생할 수 있다는 점에 유의하세요. +Bear in mind that, in this case, you'll face the issues described above. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/installation-issues.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/installation-issues.md index 3eababad473..4b64145dc28 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/installation-issues.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/installation-issues.md @@ -1,28 +1,28 @@ --- -title: 설치 문제 해결 +title: Installation problems solving sidebar_position: 5 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -## macOS Catalina에서 '설치 실패' 오류 +## "Installation failed" error in macOS Catalina -설치하는 동안 다음과 같은 오류가 발생할 수 있습니다. +During the installation you can face an error like this: -![설치 오류 화면](https://cdn.adtidy.org/content/kb/ad_blocker/mac/macerrorscreenEN.jpg) +![Installation error screen](https://cdn.adtidy.org/content/kb/ad_blocker/mac/macerrorscreenEN.jpg) -문제를 해결하려면 다음 지침을 따르세요. +Follow this instruction to solve the problem: -1. Mac을 재시동합니다. -2. Mac이 재시동될 때 시작 신호음이 들리면 바로 *Command(⌘) + R* 키를 길게 누릅니다. Apple 로고가 나타날 때까지 키를 누르고 있으면 컴퓨터가 복구 모드로 전환됩니다. -3. 상단 표시줄에서 *유틸리티* → *터미널*을 선택하고 다음 명령을 실행합니다: `csrutil disable`. -4. Mac을 재시동하고 관리자 프로필에 로그인합니다. -5. Finder 창을 열고 상단 바에서 *이동* → *폴더로 이동*을 선택한 다음 `~/private/`를 입력합니다. -6. *tmp*라는 폴더를 만들고 비밀번호를 입력합니다. -7. AdGuard 설치를 시작합니다. +1. Restart your Mac +2. As your Mac restarts, press and hold down the *Command(⌘) + R* keys immediately upon hearing the startup chime. Hold the keys until the Apple logo appears to get the computer into Recovery mode. +3. From the top bar select *Utilities* → *Terminal*, and execute this command: `csrutil disable` +4. Restart the Mac and log into Administrator's profile +5. Open the Finder window and select from the top bar *Go* → *Go to Folder* and type `~/private/` +6. Create a folder named *tmp* and type in your password +7. Launch AdGuard installation -설치가 완료되면 위의 지침에 따라 복구 모드에서 Mac을 재시동하고 터미널에서 `csrutil enable` 명령을 실행하여 시스템 보호를 활성화합니다. +As the installation is completed, restart your Mac in Recovery mode using the instruction above and execute `csrutil enable` command in Terminal to enable system protection. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/launch-issues.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/launch-issues.md index 6f31d8505dd..68590236b75 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/launch-issues.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/launch-issues.md @@ -1,40 +1,40 @@ --- -title: macOS에서 실행 문제 +title: Launch issues on macOS sidebar_position: 6 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -때때로 macOS로 인해 AdGuard의 네트워크 확장 모듈이 손상되어 앱을 사용할 수 없는 경우가 있습니다. 이 경우 사용 중인 OS 버전에 따라 다음 지침 중 하나를 따라야 합니다. +Occasionally macOS may cause the corruption of AdGuard's Network Extension module, making it unable to use the app. In this case you should follow one of these instructions, based on your OS version. -## macOS 11 이상에서 실행 문제 +## Launch issues on macOS 11 and higher -Big Sur 및 Monterey 운영 체제에서 Mac용 AdGuard를 실행하는 데 문제가 있는 경우 이 지침을 사용하세요. +If you have problems launching AdGuard for Mac on Big Sur and Monterey operating systems, please use this instruction: -1. Mac을 재부팅하고 [복구 모드](https://support.apple.com/en-us/HT201255)로 들어갑니다. -1. SIP를 비활성화합니다(**유틸리티** 메뉴에서 **터미널**을 실행하고 `csrutil disable`을 입력합니다). -1. Mac을 재부팅합니다. -1. AdGuard 앱을 닫고 **터미널**을 연 다음 `systemextensionsctl 재설정`을 입력합니다. -1. Mac을 재부팅하고 복구 모드로 들어갑니다. -1. SIP를 활성화합니다(**유틸리티** 메뉴에서 **터미널**을 실행하고 `csrutil enable`을 입력합니다). -1. AdGuard 앱을 실행하고 보호 기능을 활성화합니다. +1. Reboot Mac and enter [recovery mode](https://support.apple.com/en-us/HT201255). +1. Disable SIP (Launch **Terminal** from the **Utilities** menu and type `csrutil disable`). +1. Reboot Mac. +1. Close the AdGuard app, open **Terminal** and type `systemextensionsctl reset`. +1. Reboot Mac and enter recovery mode. +1. Enable SIP (Launch **Terminal** from the **Utilities** menu and type `csrutil enable`). +1. Launch the AdGuard app and enable protection. -## macOS 10에서 실행 문제 +## Launch issues on macOS 10 -Sierra, Mojave 및 Catalina 운영 체제에서 Mac용 AdGuard를 실행하는 데 문제가 있는 경우 이 지침을 따르세요. +If you have problems launching AdGuard for Mac on Sierra, Mojave and Catalina operating systems, please use this instruction: -1. **터미널**을 열고 `ls -@lOae /private/var/db/KernelExtensionManagement` 명령을 입력합니다. -1. 스크린샷과 같이 `restricted` 플래그가 없는지 확인합니다. ![명령어 예시 *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/restricted-flag.jpg) -1. 복구 모드에서 Mac을 재부팅합니다. -1. **유틸리티** → **터미널**을 엽니다. -1. `csrutil disable`를 입력합니다. -1. 관리자 비밀번호를 입력합니다. -1. Mac을 재부팅합니다. -1. **터미널**을 열고 다음 명령을 입력합니다: `sudo chflags restricted /private/var/db/KernelExtensionManagement`. -1. 복구 모드에서 Mac을 재부팅합니다. -1. **유틸리티** → **터미널**을 열고 `csrutil enable`를 입력한 후 관리자 비밀번호를 입력합니다. 그 다음 Mac을 재부팅합니다. -1. AdGuard 보호를 활성화합니다. +1. Open **Terminal** and enter command `ls -@lOae /private/var/db/KernelExtensionManagement`. +1. Check that the `restricted` flag is not present (like on the screenshot). ![Command example *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/restricted-flag.jpg) +1. Reboot your Mac in recovery mode. +1. Open **Utilities** → **Terminal**. +1. Enter `csrutil disable`. +1. Enter administrator password. +1. Reboot your Mac. +1. Open **Terminal** and enter the following command: `sudo chflags restricted /private/var/db/KernelExtensionManagement`. +1. Reboot your Mac in recovery mode. +1. Open **Utilities** → **Terminal** → Enter `csrutil enable` → Enter administrator password → Reboot your Mac. +1. Enable AdGuard protection. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md index b8a6facbead..23da64ea063 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md @@ -1,28 +1,28 @@ --- -title: 수동 인증서 설치 +title: Manual certificate installation sidebar_position: 1 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -Mac용 AdGuard는 루트 인증서를 인증서 저장소에 설치해야 [HTTPS 트래픽을 필터링](/general/https-filtering/what-is-https-filtering)할 수 있습니다. 대부분의 경우 이 작업은 애플리케이션을 처음 시작할 때 자동으로 수행되지만 브라우저에 마스터 비밀번호를 설치한 Gecko 기반 브라우저(Firefox, Waterfox 등) 사용자는 이러한 브라우저가 시스템 인증서 대신 자체 인증서 저장소를 사용하므로 추가 단계를 수행해야 할 수 있습니다. 메시지가 표시되면 마스터 비밀번호를 입력하거나(인증서 저장소에 대한 AdGuard 액세스 권한을 부여하기 위해) 인증서를 수동으로 설치해야 합니다. +AdGuard for Mac needs to install the root certificate into certificate storage to be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering). This action is performed automatically in most cases as you run the app for the first time, but users of Gecko-based browsers (Firefox, Waterfox etc.) who have a master password set up for their browser may be required to take additional steps (because these browsers use their own certificate storage instead of the system one). They need to either enter the master password when prompted (to grant AdGuard access to the certificate storage) or manually install the certificate. -Firefox와 같은 브라우저에 인증서를 수동으로 설치하려면 다음 단계를 따르세요. +To manually install the certificate into Firefox-like browser: - 1. *설정*을 엽니다. + 1. Open *Preferences* - 2. *개인정보 보호와 보안* → *인증서*로 이동합니다. + 2. Go to *Privacy & Security* → *Certificates* - 3. *인증서 보기*를 클릭합니다. + 3. Click *View Certificates* - 4. *인증* 탭으로 이동하여 *가져오기...* 버튼을 클릭합니다. + 4. Navigate to the *Authorities* tab and click the *Import...* button - 5. `Library/Application Support/AdGuard Software/com.adguard.mac.adguard/AdguardCore/Adguard Personal CA.cer` 파일을 선택하거나 http://local.adguard.org/cert 에서 Chromium 기반 브라우저(예: Google Chrome 또는 새로운 Edge)를 사용하여 AdGard에서 HTTPS 필터링이 실행되는 상태에서 다운로드합니다. + 5. Select file `/Library/Application Support/AdGuard Software/com.adguard.mac.adguard/AdguardCore/Adguard Personal CA.cer` or just download it from http://local.adguard.org/cert using a Chromium-based browser (e.g Google Chrome or new Edge) and with a HTTPS-filtering running in AdGuard -Gecko 기반 브라우저마다 필요한 정확한 작업은 다를 수 있지만 일반적인 순서와 `AdGuard Personal CA.cer` 파일의 경로는 동일합니다. +Exact actions required for different Gecko-based browsers may vary, but the general sequence and the path to `AdGuard Personal CA.cer` file will be the same. -참고: [Setapp 애플리케이션 버전의](https://setapp.com/apps/adguard) 경우 파일 경로는 다음과 같습니다: `/Library/Application Support/com.adguard.mac.adguard-setapp/AdguardCore/Adguard Personal CA.cer`. +P.S.: For [Setapp application version](https://setapp.com/apps/adguard) the file path is the following: `/Library/Application Support/com.adguard.mac.adguard-setapp/AdguardCore/Adguard Personal CA.cer` diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 65a33db0536..e867a29311d 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -1,42 +1,42 @@ --- -title: 메일 활동 및 AdGuard 보호 +title: Protect Mail Activity and AdGuard sidebar_position: 8 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -## 요약 +## In a nutshell -이제 Apple의 메일 앱은 이메일에서 이미지를 다운로드할 때 프록시를 사용하여 사용자의 IP 주소를 숨깁니다. +Apple's Mail app now uses a proxy to hide a user's IP address when downloading images from emails. -![메일 개인 정보 보호](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_protectMailActivity.jpg) +![Mail privacy protection](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_protectMailActivity.jpg) -하지만 활성 VPN 연결이 있는 경우에는 작동하지 않습니다. AdGuard를 VPN으로 취급하기 때문에 이미지를 자동으로 미리 로드하지 않습니다. +However, it won't work if there's an active VPN connection. As it treats AdGuard as a VPN, it won't preload images automatically. -Apple은 이 문제에 대해 [여기](https://support.apple.com/HT212797)에서 설명합니다. +Apple explains this issue [here](https://support.apple.com/HT212797). -## 문제에 대한 자세한 설명 +## In detail -이제 Mac용 AdGuard는 네트워크 확장 API를 기반으로 하는 macOS 내장 소켓 필터링을 사용합니다. 이 새롭고 다소 버그가 많은 메커니즘은 기존의 커널 확장 프로그램을 대체했습니다. 지난 1.5년 동안 저희는 새로운 필터링 방식과 관련하여 20개(!) 이상의 버그를 Apple에 보고했습니다. +AdGuard for Mac now uses macOS built-in socket filtering based on the network extensions API. This new and rather buggy mechanism replaced good old Kernel extensions. Over the last 1.5 years, we've reported more than 20(!) bugs to Apple regarding their new filtering method. -네트워크 확장 API에는 경로와 유사한 항목 목록이 있는 VPN과 유사한 구성이 있습니다. Big Sur에서는 초기 Big Sur 릴리스에서 문제를 일으킬 수 있는 '기본 경로' 규칙을 만들지 않기 위해 AdGuard는 '분할 터널링' 규칙을 사용했습니다. 이러한 문제는 몬터레이에서 해결되었으므로 '기본 경로' 규칙을 사용하는 데 아무런 지장이 없습니다. +The network extensions API has a VPN-like configuration with a list of route-like entries. On Big Sur, AdGuard used "split-tunnel" rules to avoid creating the "default route" rule because it causes problems on early Big Sur releases. These problems were solved in Monterey so nothing prevents us from using the "default route" rule. -Monterey에서 iCloud 비공개 릴레이가 도입되었습니다. Mail.app의 개인정보 보호 기능도 비공개 릴레이 서버를 사용합니다. +On Monterey, iCloud Private Relay got introduced. Privacy features of Mail.app also use Private Relay servers. -따라서 AdGuard는 iCloud 비공개 릴레이 및 메일 앱 개인정보 보호 기능과 함께 사용할 수 없습니다: +As a consequence, AdGuard can't work together with iCloud Private Relay and Mail app privacy features: -1. iCloud 비공개 릴레이는 AdGuard가 작동하는 소켓 레벨에 도달하기 전에 라이브러리 레벨의 연결에 적용됩니다. -2. iCloud 비공개 릴레이는 아직 HTTP/3 필터링을 사용할 수 없기 때문에 AdGuard가 필터링할 수 없는 QUIC을 사용합니다. -3. 따라서 AdGuard는 iCloud 비공개 릴레이 트래픽을 포함한 QUIC을 차단합니다. 그렇지 않으면 광고 차단이 불가능합니다. -4. iCloud 비공개 릴레이를 사용하고 AdGuard를 '분할 터널링' 모드로 전환하면 Safari에서 웹사이트를 열 수 없습니다. -5. Monterey에서 이 문제를 해결하기 위해 '기본 경로' 규칙을 적용합니다. 비공개 릴레이가 해당 규칙을 발견하면 자동으로 비활성화됩니다. 따라서 AdGuard는 Monterey에서 원활하게 작동하지만 iCloud 비공개 릴레이는 비활성화됩니다. +1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. +2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. +4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. +5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. -`network.extension.monterey.force.split.tunnel`은 'Big Sur' 동작을 복원하지만 이 옵션은 (3) 및 (4)로 인해 웹사이트에 대한 액세스가 중단될 수 있습니다. 저희는 이 문제에 대한 해결책을 계속 찾고 있습니다. 옵션 중 하나는 HTTP/3 필터링을 구현하는 것입니다. +`network.extension.monterey.force.split.tunnel` restores the "Big Sur" behavior, but this option may break access to websites due to (3) and (4). We keep searching for a solution to this issue. One of the options is implementing HTTP/3 filtering. -## 권장 솔루션 +## Recommended solution -현재로서는 최신 Apple 개인정보 보호 기능 대신 [AdGuard VPN](https://adguard-vpn.com/)과 같은 일반적인 VPN 서비스를 사용하는 것을 권장합니다. +At this point, we recommend using a more traditional VPN service, such as [AdGuard VPN](https://adguard-vpn.com/), instead of the newer Apple privacy features. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md index c9a8b02527c..f2a515791c7 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md @@ -1,22 +1,22 @@ --- -title: 보호 기능을 활성화할 수 없는 문제 +title: Protection cannot be enabled sidebar_position: 2 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -어떤 이유로 AdGuard 보호를 활성화할 수 없는 경우 다음 단계를 수행하세요. +If AdGuard Protection cannot be enabled for some reason, perform the following steps: -1. 메뉴 표시줄에서 AdGuard 아이콘을 클릭하고 *고급* → *설정 재설정...* → *AdGuard 종료...*로 이동합니다. +1. Click the AdGuard icon at the menu bar and go to *Advanced* → *Reset settings...* → *Quit AdGuard...* -2. Spotlight 검색에서 터미널을 입력하고 `sudo rm -R /Library/Application\ Support/com.adguard.adguard`를 입력한 후 실행합니다. +2. In the Spotlight Search, type Terminal, enter `sudo rm -R /Library/Application\ Support/com.adguard.adguard` and execute. -3. 컴퓨터를 다시 시작합니다. +3. Restart your computer. -4. 터미널을 다시 열고 `ls -al /Library/StagedExtensions/Library/Application\ Support/com.adguard.adguard/`를 입력한 후 실행합니다. 다음과 같은 메시지가 표시됩니다: `해당 파일 또는 디렉터리가 없습니다`. +4. Open the Terminal again, type `ls -al /Library/StagedExtensions/Library/Application\ Support/com.adguard.adguard/` and execute. You should receive the following: `No such file or directory`. -5. AdGuard를 시작하고 메시지가 표시되면 로그인 정보를 입력합니다. +5. Start AdGuard and enter your login information when prompted. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md index a338e7c959e..c30431695be 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md @@ -1,18 +1,18 @@ --- -title: 스크린 타임과의 비호환성 +title: Incompatibility with Screen Time sidebar_position: 11 --- :::info -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. ::: -AdGuard가 켜져 있는 동안 **스크린 타임**에서 콘텐츠 제한을 사용 설정한 경우 웹 페이지를 로드하는 데 문제가 발생할 수 있습니다. 콘텐츠 제한이 활성화되어 있는지 확인합니다. +If you have Content Restrictions enabled in _Screen Time_ while AdGuard is on, you may experience problems loading web pages. To check if Content Restrictions are active: -1. 시스템 설정 → 스크린 타임 → 콘텐츠 및 개인정보 보호 → 콘텐츠 제한으로 이동합니다. +1. Go to System Settings → Screen Time → Content & Privacy → Content Restrictions -2. 웹 콘텐츠 액세스 설정이 **성인용 웹사이트 제한**으로 설정되어 있는지 확인합니다. +2. Check if the setting for Access to Web Content is set to _Limit Adult Websites_ -이 설정이 켜져 있으면 페이지가 로드되지 않습니다. AdGuard를 계속 사용하려면 스크린 타임에서 콘텐츠 및 개인정보 보호를 비활성화한 다음 시스템을 다시 시작하세요. +If this setting is on, pages won’t load. To continue using AdGuard, disable Content & Privacy in Screen Time, and then restart the system. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/tor-filtering.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/tor-filtering.md index bcb59e79069..23fa17b34e6 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/tor-filtering.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/tor-filtering.md @@ -1,30 +1,30 @@ --- -title: Tor Browser에서 필터링 설정 +title: Setting up filtering in Tor Browser sidebar_position: 10 --- :::정보 -이 글은 시스템 수준에서 기기를 보호하는 광고 차단기인 Mac용 AdGuard에 관한 내용입니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +This article is about AdGuard for Mac, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -기본적으로 Tor 브라우저는 AdGuard의 필터링된 애플리케이션 목록에 추가됩니다. 하지만 이를 필터링하기 위해서는 AdGuard가 Tor의 보안 설정을 변경해야 합니다. 이렇게 하면 Tor가 AdGuard의 CA 인증서를 신뢰하게 됩니다. +By default, Tor Browser is added to AdGuard’s list of filtered applications. However, to filter it, AdGuard needs to change Tor's security settings. This will make Tor trust AdGuard's CA certificate. -Tor를 필터링하고 *설정* → *네트워크* → *애플리케이션*에서 선택하면 AdGuard에 이 대화 상자가 표시됩니다. +If you decide to filter Tor and check it in *Preferences* → *Network* → *Applications*, AdGuard will show you this dialog box: -![AdGuard 대화 상자](https://cdn.adtidy.org/content/kb/ad_blocker/mac/tor-setup.png) +![AdGuard dialog box](https://cdn.adtidy.org/content/kb/ad_blocker/mac/tor-setup.png) -Tor 설정을 업데이트하면 AdGuard는 다음을 설정합니다. +By updating Tor settings, AdGuard will set the following: `security.enterprise_roots.enabled`: true -이 설정은 Tor가 루트 인증서를 신뢰하도록 합니다. [자세히 알아보기](https://support.mozilla.org/en-US/kb/setting-certificate-authorities-firefox) +This setting will cause Tor to trust root certificates. [Learn more](https://support.mozilla.org/en-US/kb/setting-certificate-authorities-firefox) `security.cert_pinning.enforcement_level`: 1 -공개 키 고정(Public Key Pinning)은 웹사이트가 사이트와 사용자 간의 연결의 신뢰성을 보장할 수 있도록 하는 보안 조치입니다. 여기에는 웹사이트가 신뢰하는 공개 키 또는 핀 목록을 게시하는 것이 포함됩니다. 적용 수준을 1로 설정하면 사용자 정의 CA에 대해 고정이 적용되지 않습니다. [자세히 알아보기](https://wiki.mozilla.org/SecurityEngineering/Public_Key_Pinning) +Public Key Pinning is a security measure that allows websites to ensure that the connection between a website and a user is authentic. This involves the website publishing a list of public keys, or pins, that it trusts. With the enforcement level set to 1, pinning is not enforced for custom CAs. [Learn more](https://wiki.mozilla.org/SecurityEngineering/Public_Key_Pinning) -변경 사항을 적용하려면, Tor 브라우저를 재시작해야 합니다. +To apply the changes, you’ll need to restart Tor Browser. -이러한 설정을 수동으로 변경하면 Tor 필터링이 중지됩니다. +If you manually change these settings, Tor filtering will be stopped. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index d1d1e20da57..eb9b20a3fc8 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ sidebar_position: 5 :::note 알림 -Safari용 AdGuard는 [App Store에서](https://apps.apple.com/app/adguard-for-safari/id1440147259) 무료로 다운로드할 수 있습니다. A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +Safari용 AdGuard는 [App Store에서](https://apps.apple.com/app/adguard-for-safari/id1440147259) 무료로 다운로드할 수 있습니다. 자세한 설정 방법은 [지식 창고](/adguard-for-safari/installation/)에서 확인할 수 있습니다. ::: diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index 817b8c2c4fc..ed402277762 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: 사용자 규칙 sidebar_position: 4 --- -사용자 규칙을 사용하여 광고 차단을 맞춤 설정할 수 있습니다. 수동으로 추가하거나 가져올 수 있습니다. 페이지에서 항목을 차단하면 사용자 정의 규칙이 자동으로 만들어집니다. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +사용자 규칙을 사용하여 광고 차단을 맞춤 설정할 수 있습니다. 수동으로 추가하거나 가져올 수 있습니다. 페이지에서 항목을 차단하면 사용자 정의 규칙이 자동으로 만들어집니다. 자신만의 파일링 규칙을 추가하려면 [특수 구문](/general/ad-filtering/create-own-filters)을 사용하세요. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index 9b8c4687615..f3a33fb9f77 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -1,5 +1,5 @@ --- -title: How to collect logs in AdGuard for Safari +title: Safari용 AdGuard에서 로그를 수집하는 방법 sidebar_position: 4 --- @@ -9,9 +9,9 @@ Safari 브라우저만 보호하는 Safari용 AdGuard에 관한 문서입니다. ::: -Safari용 AdGuard에서 발생할 수 있는 문제를 분석하고 진단하기 위해 AdGuard 고객지원 서비스에서 로그 파일이 필요할 수 있습니다. 이러한 파일에는 오류 및 기타 소프트웨어 이벤트에 대한 기록이 포함되어 있습니다. Below are brief instructions on how to collect logs and send them to support if necessary. +Safari용 AdGuard에서 발생할 수 있는 문제를 분석하고 진단하기 위해 AdGuard 고객지원 서비스에서 로그 파일이 필요할 수 있습니다. 이러한 파일에는 오류 및 기타 소프트웨어 이벤트에 대한 기록이 포함되어 있습니다. 다음은 로그를 수집하여 지원팀에 보내는 방법에 대한 간단한 지침입니다. -### How to collect logs +### 로그 수집 방법 1. Safari용 AdGuard 앱을 엽니다. 2. 아래로 스크롤하여 **로그 내보내기**를 클릭합니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 9b410d85697..b15e4dcb43a 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard 어시스턴트는 브라우저에서 [새 어시스턴트](/adguard-for 이 확장 프로그램은 차단된 광고를 다시 삽입하는 기술(소위 광고 차단기 우회/광고 재삽입)에 대응하기 위해 설계된 맞춤형 확장 프로그램입니다. 이 두 가지 방법 모두 광고주들 사이에서 지속적으로 인기를 얻고 있는 고급 광고 차단 방어 방법입니다. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra는 기본적으로 사이트가 위에서 언급한 방법을 사용하여 차단기를 우회하는 것을 훨씬 더 어렵게 만드는 방식으로 페이지 작동 방식을 변경하는 미니 프로그램입니다. **AdGuard 팝업 차단기** -이 확장 프로그램은 웹페이지를 볼 때 팝업 창이 열리지 않도록 합니다. 일부 팝업에는 사이트 관리를 위한 설정이나 링크 클릭 시 표시되는 추가 참조 정보가 포함될 수 있으므로 유용한 것으로 간주됩니다. 그렇기 때문에 필요한 경우 차단기를 끌 수 있습니다. 이 확장 프로그램은 AdGuard 예외 목록에 추가된 웹사이트에서도 작동하지 않습니다. 기본적으로 꺼져 있지만 애플리케이션 설정에서 켤 수 있습니다. You will find more detailed information about this extension in our Knowledge Base. +이 확장 프로그램은 웹페이지를 볼 때 팝업 창이 열리지 않도록 합니다. 일부 팝업에는 사이트 관리를 위한 설정이나 링크 클릭 시 표시되는 추가 참조 정보가 포함될 수 있으므로 유용한 것으로 간주됩니다. 그렇기 때문에 필요한 경우 차단기를 끌 수 있습니다. 이 확장 프로그램은 AdGuard 예외 목록에 추가된 웹사이트에서도 작동하지 않습니다. 기본적으로 꺼져 있지만 애플리케이션 설정에서 켤 수 있습니다. 이 확장 프로그램에 대한 자세한 내용은 지식 창고에서 확인할 수 있습니다. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust를 사용하면 사용자 의견을 기반으로 각 웹사이트 ### 네트워크 -이 모듈은 네트워크 필터링 전용 모듈입니다. 여기에서 네트워크 관련 추가 옵션을 찾을 수 있습니다. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. 이는 웹 공간을 더 잘 필터링하기 위한 중요한 추가 예방 조치입니다. 대부분의 웹 사이트와 광고 네트워크는 현재 HTTPS를 사용하고 있습니다. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +이 모듈은 네트워크 필터링 전용 모듈입니다. 여기에서 네트워크 관련 추가 옵션을 찾을 수 있습니다. 이 중 두 가지(**트래픽 필터링 활성화** 및 **HTTPS 프로토콜 필터링**)는 기본적으로 활성화되어 있습니다. 이는 웹 공간을 더 잘 필터링하기 위한 중요한 추가 예방 조치입니다. 대부분의 웹 사이트와 광고 네트워크는 현재 HTTPS를 사용하고 있습니다. youtube.com, facebook.com, twitter.com과 같은 많은 사이트에서 HTTPS 필터링 없이는 광고를 제거하는 것이 불가능합니다. 따라서 **HTTPS 프로토콜 필터링** 기능을 사용하도록 설정하는 것이 좋습니다. ![네트워크 설정 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 14f21059454..376cd830885 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ sidebar_position: 2 ### 일반 설정 -여기에서 언어와 테마(다크 테마 또는 라이트 테마)를 설정하고, 시스템 시작 시 AdGuard를 실행하고 자동 업데이트를 무음으로 설정할 수 있습니다. 업데이트 채널과 업데이트 확인 간격 필터를 선택할 수도 있습니다. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +여기에서 언어와 테마(다크 테마 또는 라이트 테마)를 설정하고, 시스템 시작 시 AdGuard를 실행하고 자동 업데이트를 무음으로 설정할 수 있습니다. 업데이트 채널과 업데이트 확인 간격 필터를 선택할 수도 있습니다. 또한 Windows용 AdGuard가 제대로 작동하지 않아 지원팀에서 [**디버그 로그 수집**](/adguard-for-windows/solving-problems/adguard-logs.md)을 요청하는 경우 설정으로 이동합니다. ![고급 설정 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ Windows용 AdGuard의 DNS 보호 모듈에서 광고 및 추적기를 차단하 이 모듈은 브라우저에서 열린 웹 페이지의 콘텐츠를 확인하고 성인용 이미지 및 텍스트, 거친 언어, 폭력, 마약 선전 등 어린이에게 바람직하지 않은 콘텐츠가 포함된 웹 페이지를 필터링합니다. 자녀 보호 설정은 자녀가 제한을 우회할 수 없도록 비밀번호로 보호됩니다. 이 모듈은 원치 않는 사이트로 연결되는 경로를 차단할 뿐만 아니라 검색 결과에서 어린이에게 부적절한 링크를 삭제할 수도 있습니다. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. 자녀가 컴퓨터에 소프트웨어를 다운로드하고 설치하지 못하도록 **실행 파일 다운로드 차단** 확인란을 선택할 수도 있습니다. **자녀보호** 모듈에는 두 가지 옵션이 더 있습니다: **자녀보호**로 보호할 특정 Windows 사용자를 선택하고, 비밀번호를 설정하여 AdGuard 설정이 변경되지 않도록 보호할 수 있습니다. +자녀 보호 모듈에서 **안전 검색**을 활성화하고 **차단 목록** 및 **허용 목록**을 관리하여 이 옵션의 작동 방식을 사용자 지정할 수 있습니다. 자녀가 컴퓨터에 소프트웨어를 다운로드하고 설치하지 못하도록 **실행 파일 다운로드 차단** 확인란을 선택할 수도 있습니다. **자녀보호** 모듈에는 두 가지 옵션이 더 있습니다: **자녀보호**로 보호할 특정 Windows 사용자를 선택하고, 비밀번호를 설정하여 AdGuard 설정이 변경되지 않도록 보호할 수 있습니다. ![자녀 보호 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index 6778003748b..fa109c50fdd 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ sidebar_position: 2 Microsoft Windows의 PC 또는 태블릿에서 AdGuard를 사용하려면 설치 패키지를 다운로드하고 설치하면 됩니다. 다음 단계를 따라와 보세요. -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. [AdGuard 웹사이트](http://adguard.com)로 이동하여 [열린 페이지](https://adguard.com/download.html?auto=1)에서 *다운로드*를 클릭합니다. ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index e6c06f3fe6b..38389f3eb93 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -1,72 +1,72 @@ --- -title: How to collect AdGuard logs +title: AdGuard 로그 수집하는 방법 sidebar_position: 3 --- :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 작동 방식을 확인하려면 [AdGuard 앱을 다운로드하세요](https://agrd.io/download-kb-adblock). +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: :::note -로그에 제공된 데이터 및/또는 파일은 [AdGuard 개인정보취급방침에](https://adguard.com/en/privacy.html) 따라 처리됩니다. +Data and/or files provided in logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -잠재적으로 발생할 수 있는 다양한 문제를 분석하고 진단하기 위해 AdGuard 지원 서비스에는 AdGuard 로그 파일이 필요할 수 있습니다. These files contain records about errors and other events that occur with the software. AdGuard 로그를 수집하여 지원 팀에 보내는 방법을 살펴보겠습니다. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. 이 파일에는 소프트웨어에서 발생한 모든 오류에 대한 기록이 있습니다. AdGuard 로그를 수집하여 지원 팀에 보내는 방법을 살펴보겠습니다. :::note -AdGuard는 사용자의 개인정보를 보호하기 위해 최선을 다하고 있습니다. 당사는 [개인정보취급방침을](https://adguard.com/privacy/windows.html) 엄격하게 준수하며 사용자에 대한 어떠한 개인 정보도 수집하지 않습니다. 지원팀에 로그를 보내기 전에 파일에 전달하고 싶지 않은 추가 정보가 포함되어 있는지 확인하세요. 이러한 정보가 포함되어 있는 경우, 먼저 삭제하는 것이 좋습니다. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -### 디버그 로그 {#debug-logs} +### Debug logs {#debug-logs} -1. AdGuard 설정을 엽니다. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. - ![디버그 로깅 레벨 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) + ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) -1. 문제를 재현합니다. +1. Reproduce the issue. - 지원 팀이 빨리 문제를 해결할 수 있도록 문제 재현 시간을 지정해 주십시오. + We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. - ![로그 내보내기 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) + ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) - 어느 폴더에서나 압축된 로그파일을 저장합니다. + Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *디버그* 로깅 레벨이 켜져 있으면 프로그램이 느려집니다. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. -1. 문제를 재현한 시간을 알려 주고 자세히 설명하여 AdGuard 지원 팀에 **support@adguard.com**으로 압축된 로그파일을 보내 주세요. +1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. ### 추적 로그 {#trace-logs} -가끔 지원 팀은 *추적 로그*를 보내달라고 요청할 수 있습니다. 추적 로그를 수집하는 방법은 다음과 같습니다. +Sometimes support team members may ask you to send *trace* logs. Then you will need to do the following: -1. 트레이 메뉴에서 AdGuard 아이콘을 마우스 오른쪽 버튼으로 클릭하고 *AdGuard 종료를* 선택하여 AdGuard를 종료합니다. +1. Stop AdGuard by right-clicking the AdGuard icon in the tray menu and choosing *Exit AdGuard*: - ![AdGuard 종료 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-3.png) + ![Exit AdGuard *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-3.png) - 서비스를 실행 상태로 두지 마십시오. + Please don't leave the service running: - ![AdGuard 서비스 중지 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_logs_4.png) + ![Stop AdGuard Service *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_logs_4.png) -1. 콘솔을 엽니다(시작 패널에 `cmd` 입력). +1. Open the console (type `cmd` in the start panel). -1. Windows용 AdGuard v7.16 이상을 설치한 경우 Windows 버전에 관계없이 `C:\"Program Files"\Adguard\Adguard.exe /trace` 명령으로 애플리케이션을 실행합니다. +1. Run the application with the command `C:\"Program Files"\Adguard\Adguard.exe /trace` regardless of Windows bitness if you have installed AdGuard v7.16 for Windows or later. -Windows용 AdGuard의 이전 버전을 사용하는 경우 64비트 Windows를 사용하는 경우 C:\"Program Files (x86)"\Adguard\Adguard.exe /trace 명령으로 애플리케이션을 실행하고, 32비트를 사용하는 경우 C:\"Program Files"\Adguard\Adguard.exe /trace 명령으로 애플리케이션을 실행합니다. +If you have an older version of AdGuard for Windows, run the application with the command C:\"Program Files (x86)"\Adguard\Adguard.exe /trace if you are using 64-bit Windows, and C:\"Program Files"\Adguard\Adguard.exe /trace if you are using 32-bit. -1. 문제를 재현합니다. +1. Reproduce the issue. - 지원 팀이 빨리 문제를 해결할 수 있도록 문제 재현 시간을 지정해 주십시오. + We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. - ![로그 내보내기 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) + ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) - 로그파일은 커도 문제가 없습니다. 문제를 해결하기 위해 정보가 많을수록 좋습니다. + Don't worry if the log file is large. We need to know as much detail as possible to fix your problem. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index c874400daec..abbfd429cc0 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -1,96 +1,96 @@ --- -title: 일반적인 설치 프로그램 오류 +title: Common installer errors sidebar_position: 6 --- :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 이용하고자 한다면 [AdGuard 앱을 다운로드](https://agrd.io/download-kb-adblock)해 보세요. +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -이 문서에는 Windows용 AdGuard 설치 중 발생할 수 있는 가장 일반적인 오류와 이를 해결하는 방법이 포함되어 있습니다. +This article contains some of the most common errors that you can encounter during the AdGuard for Windows installation, and possible ways to solve them. -### 오류 5: 액세스 거부 {#error-5} +### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. AdGuard VPN 설치 프로그램에 설치 프로세스를 제대로 완료하는 데 필요한 권한이 없는 데는 여러 가지 이유가 있을 수 있습니다. 다음 단계를 시도해 보세요. +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. 일부 바이러스 백신은 설치를 방해할 수 있습니다. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. -- 다른 설치 폴더를 선택하세요. 현재 설치 폴더에 일부 액세스 제한이 있을 수 있습니다. 또한 외장 드라이브, 가상 드라이브 등을 선택하지 않았는지 확인하세요. +- Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. -- 컴퓨터를 재부팅합니다. 때때로 권한 문제는 일시적이며 PC를 다시 시작하여 해결할 수 있습니다. +- Reboot your computer. Sometimes the permission issues are temporary and can be solved by restarting the PC. -### 오류 112: 디스크가 꽉 찼습니다. 오류 1632: 임시 폴더가 꽉 찼거나 액세스할 수 없습니다. {#error-112} +### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -이 두 가지 오류는 매우 유사한 해결책을 가진 서로 다른 두 가지 오류입니다. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. 문제를 해결하기 위해 시도할 수 있는 몇 가지 방법이 있습니다: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: -- AdGuard를 설치하려고 했던 드라이브에서 일부 프로그램을 제거하거나 불필요한 파일을 삭제하세요. +- Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Malwarebytes의 무료 소프트웨어인 [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/)를 다운로드, 설치 및 실행하세요. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. 디스크 공간을 정리하는 데 도움이 됩니다. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. -- 컴퓨터를 재부팅합니다. 임시 파일은 디스크 공간을 상당히 많이 차지할 수 있으므로 PC를 재시작하는 것이 가장 안정적인 방법으로 임시 파일을 제거할 수 있습니다. +- Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. -### 오류 1601: Windows 설치 프로그램에 액세스할 수 없습니다. {#error-1601} +### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. 가능한 해결책은 비슷합니다: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: -- Microsoft 설치 관리자 서비스를 시작하고 다시 등록합니다. 약간의 작업이 필요합니다. +- Start and re-register Microsoft Installer service. It requires some work. - 1) *Win + R* 를 누르고 **services.msc**를 입력합니다. 2) 목록에서 *Windows Installer*를 찾아 두 번 클릭합니다. 3) *서비스 상태* 아래에 있는 *시작* 버튼을 누르고 *확인*을 누릅니다. 서비스 상태가 **실행 중**이면 먼저 *중지* 를 클릭한 다음 *시작*을 클릭해야 합니다. 4) *Win + R*를 누르고 ***msiexec /unregister*** 를 입력하고 Enter를 누른 다음 *를 누르고*를 Enter를 누릅니다. 5) *Win + R* 를 다시 누르고 ***msiexec /regserver*** 를 입력하고 Enter를 누릅니다. *Enter* + 1) Press *Win + R* and enter **services.msc**. 2) Find in the list and double click *Windows Installer*. 3) Hit *Start* button under *Service status* and hit *OK*. If the service status is **running**, you should click *Stop* first and then hit *Start*. 4) Press *Win + R*, type and enter ***msiexec /unregister*** and hit *Enter*. 5) Press *Win + R* again, type and enter ***msiexec /regserver*** and hit *Enter* -- PC를 재부팅하고 설치를 처음부터 다시 시작하세요. 때로는 그것만으로도 문제를 해결할 수 있습니다. +- Reboot the PC and start the installation all over again. Sometimes that's enough to fix the problem. -### 오류 1602: 사용자에 의해 취소됨 {#error-1602} +### Error 1602: Canceled by user {#error-1602} -이 오류 코드가 표시되었다면 어떤 식으로든 설치 프로세스를 수동으로 중단했을 가능성이 있습니다. 할 수 있는 일은 +If you got this error code, chances are you have interrupted the installation process manually in one way or another. What you can do is: -- 설치 프로그램 창을 닫지 마세요. 설치가 완료되면 자동으로 닫힙니다. +- Don't close the installer window. When the installation is complete, it will close automatically. -- 설치 중에 대화창이 나타나면 '예'를 눌러 설치 프로그램에 필요한 권한을 부여합니다. '아니요'를 클릭하면 설치가 취소됩니다. +- If a dialogue window pops up during the installation, hit "Yes" to grant the installer the required permissions. Clicking "No" will cancel the installation. -- 설치 프로세스가 진행되는 동안에는 다른 프로세스를 시작하지 마세요. +- Don't start other processes while the installation process is going on. -### 오류 1603: 설치 중 치명적인 오류 {#error-1603} +### Error 1603: Fatal error during installation {#error-1603} -이 오류는 실제보다 더 무섭게 들립니다. 실제로 이것은 여러 가지 원인이 있을 수 있는 다소 일반적인 오류이며 일부는 쉽게 수정할 수 있습니다. 다음 해결 방법을 시도해 보세요: +The error sounds scarier than it actually is. In reality, this is a rather generic error that can have many different causes, and some of them are easily fixed. Try the following solutions: -- *Win* 키를 누르고 *명령 프롬프트* 를 검색하여 실행합니다. 거기에서 `sfc /scannow를` 입력하고 *Enter* 키를 누릅니다. +- Press the *Win* key, search for *Command Prompt* and run it. There, type in `sfc /scannow` and press *Enter*. -- 다른 설치 폴더를 선택하세요. 현재 설치 폴더에 일부 액세스 제한이 있을 수 있습니다. 또한 외장 드라이브, 가상 드라이브 등을 선택하지 않았는지 확인하세요. +- Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. -- 전용 [제거 도구를](../../installation#advanced) 사용하여 AdGuard를 제거한 다음 설치를 반복하세요. +- Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. -- Microsoft 설치 관리자 서비스를 시작하고 다시 등록합니다. 약간의 작업이 필요합니다. +- Start and re-register Microsoft Installer service. It requires some work. - 1) *Win + R을* 누르고 ***services.msc***. 2) 목록에서 *Windows Installer*를 찾아 두 번 클릭합니다. 3) *서비스 상태* 아래에 있는 *시작* 버튼을 누르고 *확인*을 누릅니다. 서비스 상태가 **실행 중**이면 먼저 *중지* 를 클릭한 다음 *시작*을 클릭해야 합니다. 4) *Win + R*를 누르고 ***msiexec /unregister*** 를 입력하고 Enter를 누른 다음 *를 누르고*를 Enter를 누릅니다. 5) *Win + R* 를 다시 누르고 ***msiexec /regserver*** 를 입력하고 Enter를 누릅니다. *Enter* + 1) Press *Win + R* and enter ***services.msc***. 2) Find in the list and double click *Windows Installer*. 3) Hit *Start* button under *Service status* and hit *OK*. If the service status is **running**, you should click *Stop* first and then hit *Start*. 4) Press *Win + R*, type and enter ***msiexec /unregister*** and hit *Enter*. 5) Press *Win + R* again, type and enter ***msiexec /regserver*** and hit *Enter* -- 설치를 위해 드라이브에 대한 전체 권한을 획득합니다. 파일 위치에 대한 전체 권한이 없기 때문에 오류 1603이 발생할 수 있습니다. 또한 다른 솔루션만큼 쉽지 않습니다: +- Acquire full permissions on the drive for installation. It is possible that the error 1603 occurs because you don’t have full permissions on the file location. It's also not as easy as some of the other solutions: - 1) *파일 탐색기를* 열고 설치 위치가 포함된 드라이브를 마우스 오른쪽 버튼으로 클릭한 다음 *속성을* 선택합니다. 2) *보안* 탭으로 이동하여 *편집을* 클릭합니다. 3) *시스템을* 한 번 클릭하고 *시스템에 대한 권한의* 모든 항목의 *허용* 상자가 선택되어 있는지 확인합니다(선택 가능한 경우). *관리자에* 대해서도 동일한 확인을 수행합니다. 4) *확인을* 클릭하여 *속성* 대화 상자로 돌아갑니다. 그런 다음 *고급을* 클릭합니다. 5) *권한 변경을* 클릭합니다. 6) *권한* 탭에서 *관리자를* 두 번 클릭합니다. 7) *적용 대상* 필드에서 *이 폴더, 하위 폴더 및 파일을* 선택하고 사용 가능한 모든 *기본 권한을* 확인합니다. 그런 다음 *확인을* 누릅니다. 8) *시스템에서* 위와 동일한 작업(7번 항목부터)을 수행합니다. 9) *확인을* 끝까지 클릭합니다. AdGuard를 다시 설치해 보세요. + 1) Open *File Explorer*, right-click the drive containing the installation location and select *Properties*. 2) Go to *Security* tab and click *Edit*. 3) Single-click *SYSTEM* and ensure that the *Allow* box of every item in *Permissions for SYSTEM* is checked (if it is checkable). Do the same check for *Administrators*. 4) Click *OK* to go back to *Properties* dialog. Then click *Advanced*. 5) Click *Change Permissions*. 6) On *Permissions* tab, double-click *Administrators*. 7) Select *This folder, subfolders and files* for *Applies to* field and check all the available *Basic permissions*. After that, hit *OK*. 8) Do the same operation above (from item 7) for *SYSTEM*. 9) Click *OK* all the way out. Try installing AdGuard again. -### 오류 1618: 다른 설치가 이미 진행 중입니다. {#error-1618} +### Error 1618: Another installation is already in progress {#error-1618} -이 오류는 여러 개의 AdGuard 설치 관리자가 동시에 실행될 때 발생합니다. 이 오류가 발생하면 어떻게 해야 하나요? +This error occurs when there are several instances of AdGuard installer launched at the same time. What to do if you get this error: -- PC를 재부팅하고 설치 프로그램을 다시 시작합니다. 컴퓨터를 다시 시작하면 설치 프로그램의 모든 복사본을 포함하여 진행 중인 모든 프로세스가 중지됩니다. +- Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. 설치 프로그램 UI를 표시하는 데 몇 초가 걸릴 수 있습니다. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. -### 오류 1638: 이 제품의 다른 버전이 이미 설치되어 있습니다. {#error-1638} +### Error 1638: Another version of this product is already installed {#error-1638} -이전에 이미 AdGuard를 설치하셨을 가능성이 높습니다. +It's very likely that you've already installed AdGuard before. -- 컴퓨터에 AdGuard가 이미 설치되어 있는지 확인하세요. *Win* 키를 누르고 다음을 입력하면 됩니다. ***AdGuard***. +- Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. 전용 [제거 도구를](../../installation#advanced) 사용하여 AdGuard를 제거한 다음 설치를 반복하세요. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. -### 기타 오류 {#other} +### Other errors {#other} -위에 나열되지 않은 오류가 발생한 경우 저희가 직접 해결할 수 있을 수도 있습니다. 하지만 이를 위해서는 사용자의 로그 파일이 필요합니다. 다음 단계를 수행하세요: +If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [이 문서에서는](../system-logs) 이를 수행하는 방법을 설명합니다. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. -- 이전 두 단계의 모든 파일을 지원팀 이메일( **support@adguard.com** )로 보내주시고 메시지 본문에 문제를 설명해 주세요. 기술 지원 담당자가 최대한 빨리 답변해 드립니다. +- Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md index 15b410d44f4..3f112a6c6c8 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/connection-not-trusted.md @@ -1,79 +1,79 @@ --- -title: 인증서 관련 문제 +title: Certificate-related issues sidebar_position: 2 --- :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 작동 방식을 확인하려면 [AdGuard 앱을 다운로드하세요](https://agrd.io/download-kb-adblock). +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -HTTPS 트래픽을 필터링하고 광고 및 추적기를 효율적으로 차단할 수 있도록 AdGuard는 특수한 (고유한) 루트 인증서를 생성하여 시스템 저장소에 설치합니다. 인증서가 필요한 이유에 대한 자세한 내용은 [이 도움말 문서를](/general/https-filtering/what-is-https-filtering) 참조하세요. +To be able to filter HTTPS-traffic and efficiently block ads and trackers, AdGuard generates a special (and unique) root certificate and installs it into the system storage. You can learn more about why a certificate is required by reading [this article](/general/https-filtering/what-is-https-filtering). -일반적으로 브라우저는 설치 프로세스 중에 시스템 인증서 저장소에 추가되면 AdGuard 인증서를 신뢰합니다. 그러나 경우에 따라서는 이것만으로는 충분하지 않고 경고나 오류가 발생할 수 있습니다. 이는 Mozilla Firefox, PaleMoon, Waterfox 등과 같은 Firefox 기반 브라우저 또는 Yandex.Browser에서 가장 자주 발생합니다. +Normally browsers trust the AdGuard certificate once it's added to the system certificate storage during the installation process. But in some cases this is not enough and you may come across warnings or errors. This happens most often in Firefox-based browsers like Mozilla Firefox, PaleMoon, Waterfox, etc., or in Yandex.Browser. -## Firefox 기반 브라우저의 *잠재적 보안 위험* 오류 +## *Potential Security Risk* error in Firefox-based browsers -![보안 위험 오류](https://cdn.adtidy.org/public/Adguard/kb/en/certificate/cert_error_en.png) +![Security risk error](https://cdn.adtidy.org/public/Adguard/kb/en/certificate/cert_error_en.png) -이전 FireFox 버전과 이를 기반으로 하는 브라우저는 시스템 저장소의 인증서를 신뢰하지 않고 로컬 저장소에 있는 인증서만 신뢰합니다. v68부터 FireFox는 시스템 인증서를 신뢰하지만 여전히 '연결이 신뢰할 수 없음' 오류가 발생할 수 있습니다. 이런 일이 발생하면 먼저 *인증서 재설치* 버튼을 클릭해 보세요. *네트워크* 탭에서 찾을 수 있습니다. +Old FireFox versions, as well as browsers based on them, do not trust certificates from the system storage, but only those from their local storage. Since v68, FireFox trusts the system certificates, but you still can face the "Connection is untrusted" error. If something like this happens, first try to click the *Reinstall Certificate* button — you will find it in the *Network* tab. -![인증서 다시 설치](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/reinstall.jpg) +![Reinstall Certificate](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/reinstall.jpg) -그래도 문제가 해결되지 않는 경우, 수동으로 AdGuard 인증서를 FireFox 저장소에 추가하는 지침을 따르세요. +If that doesn't help, follow the instructions for manually adding the AdGuard certificate to the FireFox storage. -> 이 지침은 Firefox 브라우저용입니다. 버튼 및 메뉴 항목의 이름은 다른 Firefox 기반 브라우저에서 다를 수 있습니다. +> This instruction is for Firefox browser. Names of buttons and menu items may differ in other Firefox-based browsers. -1. AdGuard를 실행합니다. +1. Run AdGuard. -1. [http://local.adguard.org/cert](http://local.adguard.org/cert)으로 이동하여 *다운로드* 버튼을 클릭합니다. 브라우저에서 **cert.cer** 파일 다운로드가 시작됩니다. +1. Go to [http://local.adguard.org/cert](http://local.adguard.org/cert) and click the *Download* button. The browser should start downloading **cert.cer** file. :::note - AdGuard 앱의 *설정 → 네트워크 → HTTPS 필터링에서* 링크를 클릭하여 다운로드 페이지를 열 수도 있습니다. + You can also open the download page by clicking the link via the AdGuard app at *Settings → Network → HTTPS filtering*. ::: - ![인증서 설정](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/link.jpeg) + ![Certificate settings](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/link.jpeg) -1. 브라우저를 연 다음 *설정을* 엽니다. +1. Open your browser and then open *Settings*. -1. *개인정보 & 보안* 탭으로 이동합니다. +1. Go to *Privacy & Security* tab. -1. *인증서까지* 아래로 스크롤하여 *인증서 보기* 버튼을 클릭합니다. +1. Scroll down to *Certificates* and click the *View Certificates* button. - ![인증서 보기 창](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import1.jpeg) + ![View certificates window](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import1.jpeg) -1. *권한* 탭을 선택합니다. +1. Select *Authorities* tab. -1. *가져오기...*를 클릭합니다. +1. Click *Import...*. - ![인증서 설정 - 가져오기](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import2.jpeg) + ![Certificate settings — import](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/import2.jpeg) -1. 다운로드한 **cert.cer** 파일을 찾아서 *열기를* 클릭합니다. +1. Browse the downloaded **cert.cer** file and click *Open*. -1. *이 CA를 신뢰하여 웹사이트 식별 확인란을* 선택한 다음 *확인을* 클릭합니다. +1. Check the *Trust this CA to identify websites* box and then click *OK*. - ![인증서 설정 - 확인란](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/cert_checkbox.jpg) + ![Certificate settings — checkbox](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/cert_checkbox.jpg) -AdGuard 인증서를 성공적으로 설치했습니다. 브라우저를 다시 시작하면 오류가 사라집니다. +You've successfully installed AdGuard certificate. Restart the browser and the error should go away. -## Yandex.Browser 인증서 경고 +## Yandex.Browser certificate warning -Windows용 AdGuard와 Yandex.Browser를 모두 사용하는 경우 이 경고가 표시될 수 있습니다: +If you are a user of both AdGuard for Windows and Yandex.Browser you may have come across this warning: -![Yandex 인증서 경고](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/yandex-cert.png) +![Yandex certificate warning](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/yandex-cert.png) -### 이런 일이 발생하는 이유 +### Why is this happening -AdGuard와 Yandex는 모두 인터넷에서 사용자의 보안을 매우 중요하게 생각합니다. 현재 Yandex 정책은 브라우저에서 인식하지 못하는 인증서에 대해 사용자에게 경고하는 것입니다. 때로는 악성 앱이 자체 인증서를 삽입하고 이를 사용하여 시스템을 손상시키고 개인 데이터를 훔칠 수 있기 때문에 이는 근거가 없는 것은 아닙니다. +Both AdGuard and Yandex take users' security on the Internet very seriously. Current Yandex policy is to warn their users about any certificate that is not recognized by the browser. This is not unsubstantiated, because sometimes malicious apps can inject their own certificates and use this to harm the system and steal private data. -그러나 AdGuard는 신뢰할 수 있는 인증서에 인증서를 추가합니다. 이렇게 하면 경고 메시지가 표시됩니다. +However, AdGuard also adds its certificate to the trusted ones. This leads to the warning message you have encountered. -### 문제 해결 방법 +### How to solve the problem -가장 쉬운 방법은 **사이트로 이동** 버튼을 클릭하는 것입니다. 이렇게 하면 Yandex.Browser가 적어도 한동안은 AdGuard 인증서를 신뢰할 수 있는 인증서로 기억하도록 지시합니다. 일반적으로 이 메시지는 더 이상 표시되지 않지만, 어떤 이유로든 가끔씩 표시될 가능성이 전혀 없는 것은 아닙니다. 이러한 경우 동일한 버튼을 다시 누르기만 하면 * 됩니다(AdGuard 인증서인지 확인하세요!)*. +The easiest way is to click the **Go to site** button. This will tell Yandex.Browser to remember AdGuard certificate as a trusted one, at least for a while. Normally, you won't have to see this message anymore, but it is not beyond the realm of possibility for it to appear occasionally, for whatever reasons. In such cases, simply press the same button again *(make sure it is AdGuard's certificate!)*. -AdGuard에서 HTTPS 필터링을 비활성화하면 Yandex.Browser에서 이 메시지가 다시 표시되지 않지만 큰 비용이 발생합니다. HTTPS로 로드된 모든 광고( **Yandex 자체 광고**포함)가 YouTube, Facebook, Instagram 등의 웹사이트에 표시됩니다. 광고 차단 품질을 높게 유지하려면 이 기능을 사용하지 않는 것이 좋습니다. +Disabling the HTTPS filtering in AdGuard will also prevent Yandex.Browser from showing this message again, but it comes with a big price: all ads that are loaded by HTTPS (including **Yandex's own ads**) will show up — on such websites as YouTube, Facebook, Instagram, and many more. We strongly advise against it if you want to keep the quality of ad blocking high. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index 07a68459987..b1ca95c4a2b 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -1,48 +1,48 @@ --- -title: DNS 유출 가능성 +title: Possible DNS leaks sidebar_position: 9 --- :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 작동 방식을 확인하려면 [AdGuard 앱을 다운로드하세요](https://agrd.io/download-kb-adblock) +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -Windows용 AdGuard를 사용하면 사용자는 시스템 설정에서 설정하지 않은 경우 ISP에서 제공하는 시스템 DNS 서버 대신 쿼리를 해결하기 위한 DNS 서버 주소를 지정할 수 있습니다. 기본값이 아닌 DNS 서버를 사용하면 ISP의 감시로부터 DNS 트래픽을 보호할 수 있습니다. 또한 암호화 및 필터링 DNS 서버, 혹은 둘 다를 선택하면 악의적인 행위자 및 성가신 광고로부터 또 다른 보호 단계를 얻을 수 있습니다. +AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -많은 Windows용 AdGuard 사용자는 DNS 보호 기능을 높이 평가합니다. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. 이번 문서에서는 이런 일이 발생하는 이유와 이를 방지하는 방법에 대해 설명하겠습니다. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. -## 부트스트랩 DNS 주소 +## Bootstrap DNS address -DNS 서버 주소는 IP 또는 도메인 이름으로 작성할 수 있습니다. IP 주소의 경우 어렵지않게, AdGuard는 DNS 요청을 DNS 보호 모듈에 지정된 서버로 직접 전달합니다. 그러나 DoT 또는 DoH와 같은 암호화된 DNS 서버 주소는 대부분 도메인 이름으로 작성됩니다. 이 경우 암호화된 DNS 서버 주소를 먼저 확인하기 위해 AdGuard는 기본적으로 시스템 DNS 서버인 부트스트랩 주소로 DNS 쿼리를 보냅니다. 이러한 연결이 바로 수표 서비스에서 유출로 인식하는 것입니다. +The DNS server addresses could be written as IPs or as domain names. In the case of IP addresses there are no difficulties: AdGuard forwards the DNS request directly to the server specified in the DNS protection module. However, encrypted DNS server addresses, like DoT or DoH, are most often written as domain names. In this case, to first resolve the encrypted DNS server address, AdGuard sends a DNS query to the bootstrap address, which is by default a system DNS server. This connection is what check services perceive as a leak. -**이 누수를 제거합니다:** +**To eliminate this leak:** -- *고급 설정*으로 이동합니다. -- 아래로 스크롤하여 *사용자 지정 부트스트랩 주소 목록* 섹션으로 이동합니다. -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) -- *저장을* 클릭합니다. +- go to the *Advanced settings* +- scroll down to the *List of custom bootstrap addresses* section +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- click *Save* -## 대체 DNS 서버 +## Fallback DNS server -인터넷 연결 상태가 좋지 않거나 기본적으로 설정된 시간 제한이 만료되었거나 일부 서버 관련 문제로 인해 AdGuard가 지정된 서버에 연결할 수 없는 경우가 발생할 수 있습니다. 이 경우 기본적으로 시스템 DNS 서버인 대체 서버에 연결됩니다. 이 연결도 점검 서비스에서 유출로 간주합니다. +It could happen that AdGuard cannot reach the specified server because of a weak internet connection, an expiration of timeout set by default or some server related issues. In this case, it will connect to the fallback server, which is by default a system DNS server. This connection will also be considered by the check service as a leak. -**이 누수를 제거합니다:** +**To eliminate this leak:** -- *고급 설정*으로 이동합니다. -- *대체 서버* 항목까지 아래로 스크롤합니다. -- *사용자 지정 서버 사용* 옵션을 선택합니다. -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- go to the *Advanced settings* +- scroll down to the *Fallback servers* section +- check the *Use custom servers* option +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line -또는 +or -- *고급 설정*으로 이동합니다. -- *대체 서버* 항목까지 아래로 스크롤합니다. -- *대체 서버 사용 안 함* 옵션을 체크하세요. +- go to the *Advanced settings* +- scroll down to the *Fallback servers* section +- check the *Don’t use fallback servers* option -또는 +or -- *고급 설정*으로 이동합니다. -- *DNS 서버 시간 초과 기간* 항목까지 아래로 스크롤합니다. -- 임의의 큰 숫자를 입력합니다. +- go to the *Advanced settings* +- scroll down to the *DNS server timeout period* section +- enter an arbitrary large number diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 565285dbb72..2a5f7534168 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -1,44 +1,44 @@ --- -title: 덤프 파일을 만드는 방법 +title: How to create a dump file sidebar_position: 8 --- :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 작동 방식을 확인하려면 [AdGuard 앱을 다운로드하세요](https://agrd.io/download-kb-adblock). +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: :::note -덤프 파일에 제공된 데이터 및/또는 파일은 [AdGuard 개인정보 보호정책에](https://adguard.com/en/privacy.html) 따라 처리됩니다. +Data and/or files provided in dump files are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -사용자가 AdGuard를 사용하는 동안 발생할 수 있는 잠재적인 문제의 원인을 진단하려면 지원팀에서 프로세스 덤프 파일이 필요할 수 있습니다. 덤프 파일은 개발자가 특정 기간 동안 애플리케이션에서 실행된 프로세스를 확인할 수 있도록 도와줍니다. 아래에서 PC에서 덤프 파일을 수집하는 방법에 대한 지침을 확인할 수 있습니다. +To diagnose the reasons for potential problems that users might encounter while using AdGuard, the support team might need the process dump file. The dump file helps developers to see the processes that were executed in the application over a given period of time. Below you can check on the instructions of how to collect the dump file on your PC. -1. **Ctrl + Shift + Esc를** 누르고 **작업 관리자를** 클릭합니다. +1. Press **Ctrl + Shift + Esc** and click **Task Manager** -1. 상단 메뉴 표시줄에서 **세부 정보를** 선택합니다. +1. In the upper menu bar select **Details** - ![작업 관리자 세부 정보](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/details_en.png) + ![Task Manager details](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/details_en.png) -1. 덤프 파일을 만들려는 프로세스를 마우스 오른쪽 버튼으로 클릭합니다(예: 지원팀에서 `Adguard.exe에` 대한 덤프를 만들라고 요청할 수 있음). +1. Right-click the process that you want to create the dump file for (for example, the support team may ask you to create a dump for `Adguard.exe`) -1. 드롭다운 메뉴에서 **덤프 파일 생성을** 클릭합니다. +1. In the drop-down menu click **Create dump file** -1. 파일이 성공적으로 생성되었습니다! +1. The file was created successfully! - ![덤프 파일 만들기](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/create_dump_file_en.png) + ![Create dump file](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/create_dump_file_en.png) -덤프 파일을 생성한 후 파일 위치로 이동합니다. 덤프 파일이 생성된 직후 덤프 파일이 들어 있는 폴더를 열라는 메시지가 표시됩니다. 그렇지 않으면 다음 폴더에서 찾을 수 있습니다. **%tmp%** 폴더에서 찾을 수 있습니다. 생성된 덤프 파일(`.DMP`)의 이름은 이전 단계에서 선택한 프로세스의 이름과 동일합니다. 파일이 상당히 크므로 지원팀에 보내기 전에 압축하여 아카이브 파일로 만들어 주세요. +After you’ve created the dump file, please navigate to the file location. You should be prompted to open the folder containing the dump file right after its creation. Otherwise, you will be able to find it inside the **%tmp%** folder. The created dump file (`.DMP`) has the same name as the name of the process you chose in the previous steps. The file is quite large, so please compress it into an archive before sending to support. :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: -![AdGuard 프로세스](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) +![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -지원팀에 덤프 파일을 보내실 때 AdGuard 애플리케이션 로그도 첨부해 주시면 문제를 더 잘 해결할 수 있습니다. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index f1aef4eaf83..cea063cc776 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -1,30 +1,30 @@ --- -title: How to collect AdGuard installation logs +title: AdGuard 설치 로그를 수집하는 방법 sidebar_position: 4 --- :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 작동 방식을 확인하려면 [AdGuard 앱을 다운로드하세요](https://agrd.io/download-kb-adblock). +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: :::note -시스템 로그에 제공된 데이터 및/또는 파일은 [AdGuard 개인정보취급방침에](https://adguard.com/en/privacy.html) 따라 처리됩니다. +Data and/or files provided in system logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: AdGuard 설치 중 문제가 발생하면 지원 팀에서 AdGuard 설치 로그를 수집하여 보내달라고 요청할 수 있습니다. AdGuard 설치 로그 수집 및 전송 방법은 다음과 같습니다. -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. -1. *%tmp%*를 입력하고 *확인*을 클릭합니다. +1. Type in *%tmp%* and click *OK*. - ![임시 폴더 열기 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/install-logs-1.png) + ![Open temp folder *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/install-logs-1.png) -1. 열린 폴더에서 `Adguard`로 시작하는 모든 파일을 선택하고 ZIP 파일에 추가합니다 (예: WinRAR 사용). +1. In the opened folder select all files starting with `Adguard` and add them to archive (using WinRAR or any other archiving software). - ![AdGuard 설치 로그 파일 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/install-logs-2.png) + ![AdGuard installation log files *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/install-logs-2.png) -1. 이 ZIP 파일을 AdGuard 지원 팀에 **support@adguard.com**으로 보냅니다. +1. Send this archive to AdGuard tech support at **support@adguard.com**. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/known-issues.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/known-issues.md index 910363e23d6..407d033914d 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/known-issues.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/known-issues.md @@ -1,20 +1,20 @@ --- -title: Windows용 AdGuard의 알려진 문제 +title: Known issues of AdGuard for Windows sidebar_position: 10 --- :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 작동 방식을 확인하려면 [AdGuard 앱을 다운로드하세요](https://agrd.io/download-kb-adblock). +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -## Windows용 AdGuard 및 Windows용 AdGuard VPN 호환성 문제 +## AdGuard for Windows and AdGuard VPN for Windows compatibility issues -Windows용 AdGuard와 Windows용 AdGuard VPN을 설치하면 사용자의 노력 없이도 함께 작동하기 시작합니다. 그러나 기본 설정 중 일부를 변경하면 앱이 동시에 실행될 때 앱이 제대로 작동하지 않을 수 있습니다. +Once you install AdGuard for Windows and AdGuard VPN for Windows, they just start working together without any effort on your part. However, changing some of their default settings may cause the apps to work incorrectly when they run at the same time. -Windows용 AdGuard에는 두 가지 특정 설정이 있습니다: *리디렉션 드라이버 모드 사용* 및 *로컬 호스트 필터링*. 기본적으로 첫 번째는 비활성화되어 있고 두 번째는 활성화되어 있습니다. 기기에서 AdGuard 광고 차단기와 AdGuard VPN이 모두 활성화된 경우 이러한 설정을 변경하면 AdGuard의 필터링이 불가피하게 중단됩니다. +There are two specific settings in AdGuard for Windows: *Use redirect driver mode* and *Filter localhost*. By default, the first is disabled, and the second is enabled. Changing any of these settings will inevitably disrupt AdGuard's filtering if both AdGuard Ad Blocker and AdGuard VPN are enabled on your device. -이러한 설정을 변경하는 것은 AdGuard 광고 차단기와 안티바이러스, VPN, 네트워크 필터와 같은 네트워크 수준 앱의 동시 작동과 관련된 문제를 해결하기 위해서만 필요합니다. 위 설정의 기본 상태를 변경해야 하지만 여전히 AdGuard Ad Blocker와 AdGuard VPN이 동시에 올바르게 작동하길 원하는 상황이 발생하면 [GitHub에서 이슈를 생성하세요](https://github.com/AdguardTeam/AdguardForWindows/issues/new/choose) 그러면 저희가 직접 도와드리겠습니다. +Changing these settings is only necessary to resolve issues related to the simultaneous operation of AdGuard Ad Blocker and network-level apps such as antiviruses, VPNs, and network filters. If you come across a situation where you need to change the default state of the above settings and still want AdGuard Ad Blocker and AdGuard VPN to work simultaneously and correctly — [create an issue on GitHub](https://github.com/AdguardTeam/AdguardForWindows/issues/new/choose) so we can help you personally. -현재 위에 나열된 앱 동시 작업의 한계를 극복하기 위해 노력하고 있습니다. +We are currently working on overcoming the above-listed limitations of the simultaneous work of our apps. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 7ebd3fc88d9..63e9ea099c4 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -5,7 +5,7 @@ sidebar_position: 7 :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 작동 방식을 확인하려면 [AdGuard 앱을 다운로드하세요](https://agrd.io/download-kb-adblock). +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -29,13 +29,13 @@ sidebar_position: 7 이 기능을 활성화하면 AdGuard가 Edge 브라우저에서 TCP 빠른 열기를 차단합니다. 설정을 적용하려면 브라우저를 다시 시작해야 합니다. -### Use Encrypted Client Hello +### Encrypted ClientHello 사용 -모든 암호화된 인터넷 연결에는 암호화되지 않은 부분이 있습니다. 이것은 연결하려는 서버의 이름이 포함된 첫 번째 패킷입니다. Encrypted Client Hello 기술은 이 문제를 해결하고 암호화되지 않은 마지막 비트의 정보를 암호화합니다. To benefit from it, enable the *Use Encrypted Client Hello* option. 로컬 DNS 프록시를 사용하여 도메인에 대한 ECH 구성을 찾습니다. If it is found, Client Hello packet will be encrypted. +모든 암호화된 인터넷 연결에는 암호화되지 않은 부분이 있습니다. 이것은 연결하려는 서버의 이름이 포함된 첫 번째 패킷입니다. Encrypted Client Hello 기술은 이 문제를 해결하고 암호화되지 않은 마지막 비트의 정보를 암호화합니다. 이 기능을 사용하려면 *Encrypted ClientHello 사용* 옵션을 활성화하세요. It uses a local DNS proxy to look for the ECH configuration for the domain. ECH 구성이 발견되면 ClientHello 패킷이 암호화됩니다. ### 웹사이트의 인증서 투명성 확인 -Chrome 인증서 투명성 정책에 따라 도메인의 모든 인증서를 확인합니다. 인증서가 Chrome 인증서 투명성 정책을 준수하지 않는 경우 AdGuard는 웹사이트를 필터링하지 않습니다. 반면에 Chrome은 이 사이트를 차단합니다. +Chrome 인증서 투명성 정책에 따라 도메인의 모든 인증서를 확인합니다. If the certificate does not comply with the Chrome Certificate Transparency Policy, AdGuard will not filter the website. 반면에 Chrome은 이 사이트를 차단합니다. ### SSL/TLS 인증서 해지 확인 활성화 @@ -61,9 +61,9 @@ Chrome 인증서 투명성 정책에 따라 도메인의 모든 인증서를 확 AdGuard가 필터 구독 URL(예: `abp:subscribe` 등)을 자동으로 가로채고 사용자 정의 필터 설치 대화 상자를 열도록 하려면 이 기능을 활성화합니다. -### HTTP/3 필터링 +### Filter HTTP/3 -이 옵션을 활성화하면 AdGuard는 다른 요청 유형과 함께 HTTP/3을 통해 전송된 요청을 필터링합니다. +If this option is enabled, AdGuard will filter requests sent over HTTP/3 in addition to other request types. ### 리디렉션 드라이버 모드 사용 @@ -73,7 +73,7 @@ AdGuard가 필터 구독 URL(예: `abp:subscribe` 등)을 자동으로 가로채 ### 시스템 시작 시 메인 창 열기 -이 옵션을 활성화하면 시스템이 로드된 후 기본 AdGuard 창이 열립니다. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +이 옵션을 활성화하면 시스템이 로드된 후 기본 AdGuard 창이 열립니다. 이 설정은 *설정 → 일반 설정*에 있으며 실제 필터링 서비스가 실행되는지 여부에는 영향을 미치지 않습니다. ### 시스템 시작 시 필터링 활성화 @@ -81,7 +81,7 @@ AdGuard가 필터 구독 URL(예: `abp:subscribe` 등)을 자동으로 가로채 :::note -v7.12 이전에는 *시스템 시작 시 AdGard 실행이* 비활성화되어 있어도 기본적으로 필터링 모드에서 AdGard 서비스가 시작되었습니다. 애플리케이션의 이전 동작에 만족했다면 이 옵션을 활성화하세요. +Before v7.12, the AdGuard service started in filtering mode by default (even if the *Launch AdGuard at system start-up* was disabled). If you were satisfied with the old behavior, enable this option. ::: @@ -95,7 +95,7 @@ AdGuard가 특정 서브넷을 필터링하지 않도록 설정하려면 이 기 ### HAR 기록 사용 -이 옵션은 **디버깅 목적**으로만 활성화해야 합니다. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. 이 파일은 Fiddler 앱으로 분석할 수 있습니다. 웹 브라우징 속도가 상당히 느려질 수 있습니다. +이 옵션은 **디버깅 목적**으로만 활성화해야 합니다. 확인 표시를 선택하면 AdGuard가 필터링된 모든 HTTP 요청에 대한 정보가 포함된 HAR 1.2 형식의 파일을 생성합니다. 이 파일은 Fiddler 앱으로 분석할 수 있습니다. 웹 브라우징 속도가 상당히 느려질 수 있습니다. ### 일반 HTTP 요청에 추가 공백 추가 @@ -113,17 +113,17 @@ Host: example.org 요청은` ### 초기 TLS 패킷의 조각화 크기 조정 -심층 패킷 검사를 피하기 위해 TCP 패킷 조각화의 크기를 지정합니다. 이 옵션은 보안(HTTPS) 트래픽에만 영향을 줍니다. +심층 패킷 검사를 피하기 위해 TCP 패킷 조각화의 크기를 지정합니다. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +이 옵션을 활성화하면 AdGuard는 초기 TLS 패킷(ClientHello 패킷)을 두 부분으로 분할합니다. 첫 번째 부분은 지정된 길이를 가지며 두 번째 부분은 나머지 길이(전체 초기 TLS 패킷의 길이까지)를 가집니다. -유효한 값은 1~1500입니다. 잘못된 크기를 지정하면 시스템에서 선택한 값이 사용됩니다. 이 설정은 스텔스 모드에서 *DP로부터 보호* 옵션이 활성화된 경우에만 적용됩니다. +Valid values: 1–1500. 잘못된 크기를 지정하면 시스템에서 선택한 값이 사용됩니다. 이 설정은 스텔스 모드에서 *DP로부터 보호* 옵션이 활성화된 경우에만 적용됩니다. ### 일반 HTTP 조각 크기 HTTP 요청 조각화의 크기를 조정합니다. 이 옵션은 일반 HTTP 트래픽에만 영향을 줍니다. 이 옵션을 활성화하면 AdGuard는 초기 패킷을 두 부분으로 분할하여 첫 번째 패킷은 지정된 길이로, 두 번째 패킷은 전체 원본 패킷의 길이까지 나머지 부분을 차지합니다. -유효한 값은 1~1500입니다. 잘못된 크기를 지정하면 시스템에서 선택한 값이 사용됩니다. 이 설정은 스텔스 모드에서 *DP로부터 보호* 옵션이 활성화된 경우에만 적용됩니다. +Valid values: 1–1500. 잘못된 크기를 지정하면 시스템에서 선택한 값이 사용됩니다. 이 설정은 스텔스 모드에서 *DP로부터 보호* 옵션이 활성화된 경우에만 적용됩니다. ### QUIC 보기 @@ -135,21 +135,21 @@ HTTP 요청 조각화의 크기를 조정합니다. 이 옵션은 일반 HTTP ### TCP 연결 유지 간격 -킵얼라이브 프로브를 보내기 전에 유휴 기간을 초 단위로 지정할 수 있습니다. 0을 지정하면 시스템에서 선택한 값이 사용됩니다. +킵얼라이브 프로브를 보내기 전에 유휴 기간을 초 단위로 지정할 수 있습니다. If 0 is specified, the value selected by the system will be used. :::note -이 설정은 *TCP 킵얼라이브 활성화* 옵션이 활성화된 경우에만 작동합니다. +This setting only works when the *Enable TCP keepalive* option is enabled. ::: ### TCP 연결 유지 시간 초과 -여기에서 응답이 없는 피어에게 다른 킵얼라이브 프로브를 보내기 전에 시간을 초 단위로 지정할 수 있습니다. 0을 지정하면 시스템에서 선택한 값이 사용됩니다. +Here you can specify time in seconds before sending another keepalive probe to an unresponsive peer. 0을 지정하면 시스템에서 선택한 값이 사용됩니다. :::note -이 설정은 *TCP 킵얼라이브 활성화* 옵션이 활성화된 경우에만 작동합니다. +This setting only works when the *Enable TCP keepalive* option is enabled. ::: @@ -167,11 +167,11 @@ HTTP 요청 조각화의 크기를 조정합니다. 이 옵션은 일반 HTTP ### 폴백 DNS 업스트림 사용 -선택한 업스트림에 대한 모든 DNS 요청이 실패하면 일반 쿼리는 폴백 업스트림으로 리디렉션됩니다. +Normal queries will be redirected to the fallback upstream if all DNS requests to the selected upstreams fail. ### DNS 업스트림 쿼리를 병렬로 수행 -모든 업스트림이 병렬로 쿼리되고 첫 번째 응답이 반환됩니다. DNS 쿼리는 병렬로 이루어지므로 이 기능을 활성화하면 인터넷 속도가 빨라집니다. +All upstreams will be queried in parallel and the first response is returned. DNS 쿼리는 병렬로 이루어지므로 이 기능을 활성화하면 인터넷 속도가 빨라집니다. ### 실패한 DNS 쿼리에 항상 응답 @@ -179,7 +179,7 @@ HTTP 요청 조각화의 크기를 조정합니다. 이 옵션은 일반 HTTP ### 보안 DNS 요청 필터링 사용 -AdGuard는 일반 DNS 요청뿐만 아니라 보안 DNS 요청을 로컬 DNS 프록시로 리디렉션합니다. +AdGuard will redirect secure DNS requests to the local DNS proxy, in addition to plain DNS requests. ### 호스트 규칙에 대한 차단 모드 @@ -233,4 +233,4 @@ AdGuard가 사용자 정의 폴백 서버를 사용하도록 하려면 이 섹 ### 지정된 Wi-Fi 네트워크 이름(SSID)을 DNS 필터링하지 않기 -DNS 보호에는 이 섹션에 나열된 Wi-Fi 네트워크가 포함되지 않습니다. Wi-Fi 네트워크 이름(SSID)을 한 줄에 하나씩 지정합니다. 특정 Wi-Fi 네트워크가 이미 AdGuard Home 또는 다른 DNS 보호 시스템에 의해 보호되고 있는 경우 유용할 수 있습니다. 이 경우 DNS 요청을 다시 필터링할 필요가 없습니다. +DNS protection will not include Wi-Fi networks listed in this section. Wi-Fi 네트워크 이름(SSID)을 한 줄에 하나씩 지정합니다. 특정 Wi-Fi 네트워크가 이미 AdGuard Home 또는 다른 DNS 보호 시스템에 의해 보호되고 있는 경우 유용할 수 있습니다. 이 경우 DNS 요청을 다시 필터링할 필요가 없습니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index df9c381f2f8..66261b626ed 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -1,50 +1,50 @@ --- -title: How to collect Windows system logs +title: Windows 로그 수집하는 방법 sidebar_position: 5 --- :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 작동 방식을 확인하려면 [AdGuard 앱을 다운로드하세요](https://agrd.io/download-kb-adblock). +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: :::note -시스템 로그에 제공된 데이터 및/또는 파일은 [AdGuard 개인정보취급방침에](https://adguard.com/en/privacy.html) 따라 처리됩니다. +Data and/or files provided in system logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -잠재적으로 발생할 수 있는 다양한 문제를 분석하고 진단하기 위해 AdGuard 지원 서비스에는 Windows 시스템 로그 파일이 필요할 수 있습니다. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Windows 로그를 수집하여 지원 팀에 보내는 방법을 살펴보겠습니다. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. 이 파일에는 소프트웨어에서 발생한 모든 오류에 대한 기록이 있습니다. Windows 로그를 수집하여 지원 팀에 보내는 방법을 살펴보겠습니다. -1. *Win+R*을 함께 누릅니다. +1. Press *Win + R* -1. 열린 창에 `eventvwr`을 입력하고 *확인*을 클릭합니다. +1. In the window that appears type in `eventvwr` and click *OK*: - ![실행창 *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_1.png) + ![Run window *mobile](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_1.png) -1. 그다음에는 이벤트 뷰어 창이 나타납니다. +1. Event Viewer window appears as shown in the picture. - ![이벤트 뷰어 *border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_2.png) + ![Event viewer *border](https://cdn.adtidy.org/public/Adguard/kb/newscreenshots/En/eng_event_logs_2.png) - 필요한 파일을 저장하려면 다음 지침을 따르세요. + To save files that we need, do the following: - - *애플리케이션* 열기: *이벤트 뷰어(로컬)* → * Windows 로그* → *애플리케이션*. + - Open *Application*: *Event Viewer (Local)* → *Windows Logs* → *Application*. - - *애플리케이션*을 우클릭하고 드롭다운 메뉴에서 *다른 이름으로 모든 이벤트 저장…*을 선택합니다. + - Right-click *Application* and in the drop-down menu select *Save All Events As...* - - 이름과 저장할 위치를 선택하고 *저장*을 클릭합니다. 그다음에는 *언어 설정에 대한 정보 표시*를 선택합니다. *영어* 옆에 있는 확인란을 선택해야 합니다. *확인*을 클릭합니다. + - 이름과 저장할 위치를 선택하고 *저장*을 클릭합니다. 그다음에는 *언어 설정에 대한 정보 표시*를 선택합니다. You need to check the checkbox next to *English*. *확인*을 클릭합니다. - - *시스템* 열기: *이벤트 뷰어(로컬)* → * Windows 로그* → *시스템*. + - Open *System*: *Event Viewer (Local)* → *Windows Logs* → *System*. - - *시스템*을 우클릭하고 드롭다운 메뉴에서 *다른 이름으로 모든 이벤트 저장…*을 선택합니다. + - Right-click *System* and in the drop-down menu select *Save All Events As...* - 저장할 위치를 선택하고 이름을 입력한 후 *저장*을 클릭합니다. 그다음에는 *언어 설정에 대한 정보 표시*를 선택합니다. *한국어* 옆의 확인란을 선택하고 *확인*을 클릭합니다. -**support@adguard.com**으로 두 개의 파일을 보내 주십시오. +Please send the two files that you've recently saved to **support@adguard.com**. :::note -AdGuard는 사용자의 개인정보를 보호하기 위해 최선을 다하고 있습니다. 당사는 [개인정보취급방침을](https://adguard.com/privacy/windows.html) 엄격하게 준수하며 사용자에 대한 어떠한 개인 정보도 수집하지 않습니다. 지원팀에 로그를 보내기 전에 파일에 전달하고 싶지 않은 추가 정보가 포함되어 있는지 확인하세요. 이러한 정보가 포함되어 있는 경우, 먼저 삭제하는 것이 좋습니다. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/windows.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 0cc5fcba750..4b4d0c92e11 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -1,20 +1,20 @@ --- -title: WFP 드라이버 +title: WFP driver sidebar_position: 1 --- :::정보 -본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. 작동 방식을 확인하려면 [AdGuard 앱을 다운로드하세요](https://agrd.io/download-kb-adblock). +본 문서는 시스템 수준에서 기기를 보호하는 다기능 광고 차단기인 Windows용 AdGuard에 대해 다룹니다. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -네트워크 트래픽을 필터링하기 위해 AdGuard는 네트워크 드라이버를 사용합니다. TDI 드라이버와 WFP 드라이버 옵션이 있습니다. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. 이러한 문제와 그에 따른 오류는 각 경우에 따라 매우 다를 수 있습니다. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. -이로 인해 발생한 것으로 의심되는 문제가 발생하면 언제든지 이전 버전이지만 더 안정적인 TDI 네트워크 드라이버로 전환할 수 있습니다. 다음와 같이 설정합니다: +If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: -1. *설정 → 네트워크로* 이동합니다. +1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: -![WFP 드라이버 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) +![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/account/features.md index 3b2fd3662db..abc4a4e9025 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ AdGuard 광고 차단 라이선스에 연결된 기기의 연결을 해제하거 ## 고객지원 문의 -지원 탭에는 문제를 해결하거나 AdGuard 제품에 대한 정보를 찾는 데 도움이 되는 유용한 링크가 포함되어 있습니다. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +지원 탭에는 문제를 해결하거나 AdGuard 제품에 대한 정보를 찾는 데 도움이 되는 유용한 링크가 포함되어 있습니다. 6개의 섹션으로 나뉘어 있습니다: 자주 묻는 질문, 버그 제보/기능 요청 보내기, 잘못된 차단 신고, 지원팀에 문의, 지식 창고, 토론장입니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 184c3796296..bbe0745016d 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ sidebar_position: 2 - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index f5d102c24ba..176a42a6c87 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:-------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::정보 -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:-------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:-----------------------:|:--------------------------:|:-------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:-------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:-----------------------:|:--------------------------:|:-------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:-----------------------:|:--------------------------:|:-------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------:|:--------------------------:|:-------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::정보 -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------:|:--------------------------:|:-------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:-----------------------:|:--------------------------:|:-------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **제한** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3944,7 +3739,7 @@ The `min-length` special attribute must not appear in a selector to the left of :contains(unquoted text) ``` -또는 +or ```text :contains(/reg(ular )?ex(pression)?/) @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:-----------------------:|:--------------------------:|:-------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS용 AdGuard][ios-app] | [Safari용 AdGuard][ext-saf] | [AdGuard 콘텐츠 차단기][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:-----------------------:|:--------------------------:|:-------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4398,7 +4125,7 @@ rules_list !#endif ``` -또는 +or ```adblock !#if (conditions) @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,32 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "Safari용 AdGuard" -[ext-saf]: #what-product "AdGuard for Safari" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index c3006f9c45a..741fec174d6 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard 광고 차단 필터에는 다음이 포함됩니다. - AdGuard 베이스 필터 - AdGuard 모바일 광고 필터 - 언어 원칙에 따라 구분된 지역 필터: 중국어, 네덜란드어, 프랑스어, 독일어, 일본어, 러시아어, 스페인어/포르투갈어, 터키어, 우크라이나어 -- AdGuard Quick Fixes filter ### 이러한 필터의 목적 - **베이스 필터**는 영어 웹사이트 및 별도의 필터가 없는 웹사이트의 광고를 차단하도록 설계되었습니다. 또한 언어에 관계없이 모든 사이트에 적용되는 일반 필터링 규칙이 포함되어 있습니다. - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. 언어에 따른 세분화가 없습니다. - **지역 필터**는 **베이스 필터**와 동일한 정책을 따르지만 특정 언어의 웹사이트로 제한됩니다. -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. 광고 차단 필터의 목표는 인터넷에서 광고를 로드할 수 있는 웹사이트, 애플리케이션 및 특정 디바이스에서 모든 유형의 광고를 차단하는 것입니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index 16cb592afed..751fab53a76 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/browsing-security.md index 6f1fb95e132..a62d04ff815 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 피싱과 멀웨어는 여전히 흔한 문제입니다. 디지털 보안을 강화하기 위해 AdGuard 제품에 특수 필터를 통합하여 악성 및 피싱 웹사이트로부터 사용자를 보호합니다. 현재까지 1,500만 개 이상의 사이트를 분류하고 피싱 및 멀웨어로 알려진 150만 개 웹사이트의 데이터베이스를 구축했습니다. AdGuard는 이 데이터베이스를 사용하여 사용자가 방문하는 웹사이트를 확인하여 온라인 위협으로부터 사용자를 보호합니다. -:::note +::: note 당사는 사용자가 방문하는 웹사이트에 대한 정보를 엄격하게 수집하거나 사용하지 않습니다. ::: -## How does AdGuard check websites? +## AdGuard는 웹사이트를 어떻게 검사하나요? 사용자가 웹사이트를 방문할 때마다 로컬 클라이언트는 해시 및 해시 접두사 형태로 AdGuard 백엔드 서버와 정보를 교환합니다. 이 교환을 기반으로 로컬 클라이언트는 잠재적으로 위험한 웹사이트 데이터베이스에 해당 웹사이트가 등재되어 있는지 여부를 결정합니다. 하지만 앱과 확장 프로그램은 조금 다르게 검사됩니다. @@ -61,11 +61,11 @@ AdGuard는 피싱 및 멀웨어 웹사이트에 대한 광범위한 데이터베 의심스러운 사이트에 대한 불만을 자동으로 분석하고 데이터베이스를 최신 상태로 유지하며 오탐을 정리하고 향후 이를 방지하기 위한 메커니즘을 구현하는 데 많은 시간을 할애합니다. -### Want to help? +### 돕고 싶으신가요? 피싱 또는 멀웨어 웹사이트를 발견하면 으로 신고해 주세요. -### False-positive responses +### 오탐 응답 때때로 일부 비악성 웹사이트가 AdGuard의 필터에 추가되는 경우가 있습니다. 오탐 비율을 줄이기 위해 최선을 다하고 있지만 여전히 오탐이 발생하고 있습니다. AdGuard에서 이러한 동작이 발생하면 지원팀( )으로 오탐을 신고해 주세요. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/how-to-install.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/how-to-install.md index b842f3b982c..db343acde02 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/how-to-install.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/how-to-install.md @@ -11,7 +11,7 @@ sidebar_position: 8 [Windows용 AdGuard](/adguard-for-windows/installation) -[Mac용 AdGuard](/adguard-for-mac/installation) +[AdGuard for Mac](/adguard-for-mac/installation) [AdGuard 확장 프로그램](/adguard-browser-extension/installation) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 574ba06971e..129555003e6 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS(HyperText Transfer Protocol Secure)는 보안을 강화하기 위해 암호화를 지원하는 HTTP 프로토콜의 확장입니다. 이 프로토콜은 개인 데이터, 신용 카드 정보 등과 같은 중요한 지정보를 안전하게 전송하는 데 사용됩니다. -암호화된 트래픽이 제3자에 의해 ‘엿들어지지 않도록’ 보호되므로 HTTPS를 사용하는 것이 좋습니다. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +암호화된 트래픽이 제3자에 의해 ‘엿들어지지 않도록’ 보호되므로 HTTPS를 사용하는 것이 좋습니다. 최근 HTTPS는 [Google 권장을 받고](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) 있다는 점과 무료 인증 센터 [Let ’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt)의 등장으로 인해 확산되고 있습니다. 아래의 그림은일반 HTTP 프로토콜과 보안 HTTPS 프로토콜의 차이점을 보여줍니다. @@ -15,17 +15,17 @@ HTTPS(HyperText Transfer Protocol Secure)는 보안을 강화하기 위해 암 ### 보안 인증서란 무엇인가요? -간단히 말하면 HTTPS는 데이터 암호화를 의미합니다. 그러나 원하시는 웹 사이트와 암호화된 연결을 했는지 어떻게 확인을 할 수 있을까요? 웹 사이트가 보안 인증서가 있으면 연결이 암호화됩니다. A certificate serves as proof that the website is really who or what it claims to be. 브라우저에서 보안 연결이 될 수 없습니다. 웹 사이트에서 사용하는 인증서를 브라우저에서 신뢰하는 CA(인증 기관)에서 발급받는 것이 중요합니다. 인증 기관은 SSL 인증서가 웹 사이트 소유자에게 발급되는 것을 보장합니다. +간단히 말하면 HTTPS는 데이터 암호화를 의미합니다. 그러나 원하시는 웹 사이트와 암호화된 연결을 했는지 어떻게 확인을 할 수 있을까요? 웹 사이트가 보안 인증서가 있으면 연결이 암호화됩니다. 웹 사이트가 보안 인증서가 없거나 인증서에 잘못된 정보가 포함된 경우, 브라우저에서 보안 연결이 될 수 없습니다. 웹 사이트에서 사용하는 인증서를 브라우저에서 신뢰하는 CA(인증 기관)에서 발급받는 것이 중요합니다. 인증 기관은 SSL 인증서가 웹 사이트 소유자에게 발급되는 것을 보장합니다. ### AdGuard가 HTTPS를 필터링해야 하는 이유는 무엇인가요? -대부분의 웹 사이트와 광고 네트워크는 현재 HTTPS를 사용하고 있습니다. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +대부분의 웹 사이트와 광고 네트워크는 현재 HTTPS를 사용하고 있습니다. YouTube와 Facebook, Twitter가 HTTPS를 필터링하지 않고는 광고를 삭제할 수 없는 대표적인 예시입니다. ### HTTPS 필터링은 어떻게 작동하나요? -HTTPS 필터링 작업 방식이 쉬웠다면 HTTPS는 그렇게 안전하지 않을 것입니다. 브라우저가 서버에 연결하려고 하면 AdGuard는 두 개의 보안 연결을 설정하는데, 각각 브라우저나 다른 앱, 그리고 서버와 설정하는 것이 그것입니다. 브라우저는 AdGuard와 AdGuard가 생성하는 연결을 신뢰해야 합니다. 이를 위해 AdGuard는 특수 루트 인증서를 생성하여 시스템에 설치하고 필요한 경우, Firefox와 같은 일부 브라우저에도 설치합니다. AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +HTTPS 필터링 작업 방식이 쉬웠다면 HTTPS는 그렇게 안전하지 않을 것입니다. 브라우저가 서버에 연결하려고 하면 AdGuard는 두 개의 보안 연결을 설정하는데, 각각 브라우저나 다른 앱, 그리고 서버와 설정하는 것이 그것입니다. 브라우저는 AdGuard와 AdGuard가 생성하는 연결을 신뢰해야 합니다. 이를 위해 AdGuard는 특수 루트 인증서를 생성하여 시스템에 설치하고 필요한 경우, Firefox와 같은 일부 브라우저에도 설치합니다. 따라서 AdGuard는 보안 연결 상황을 확인하고 광고 및 추적을 차단할 수 있습니다. -For better understanding, we have depicted this process: +아래의 그림은 이러한 과정을 알기 쉽게 보여줍니다. ![HTTPS 필터링은 어떻게 작동하나요](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/license/what-is.md index ee78165415e..b5936c1ce14 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: AdGuard 라이선스란 무엇인가요? sidebar_position: 1 --- @@ -12,7 +12,7 @@ sidebar_position: 1 - **연간 구독** — 이 라이선스는 매년 자동으로 갱신되거나 수동으로 연장할 수 있습니다. - 개인용 — 최대 3개의 기기 - 가족용 — 최대 9개의 기기 -- **Lifetime** — these licenses are perpetual +- **평생** — 이 라이선스는 기간 제한이 없습니다. - 개인용 — 최대 3개의 기기 - 가족용 — 최대 9개의 기기 diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 0687cc47064..e9744ea8ead 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ WebRTC(웹 실시간 통신)는 브라우저와 앱 간에 데이터를 직접 ### Flash 차단 {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. 이 설정을 켜면 AdGuard가 브라우저에서 Flash의 콘텐츠 표시를 허용하는 구성 요소(예: 플러그인 및 ActiveXObject 개체)를 감지하는 기능을 차단합니다. 이는 사실상 브라우저가 Flash를 지원할 수 없음을 의미합니다. +Flash Player 플러그인은 바이러스 및 해커와 같은 온라인 위협에 점점 더 취약해지고 있습니다. 또한 웹사이트 로딩 시간에 큰 영향을 미칠 수도 있습니다. 이 설정을 켜면 AdGuard가 브라우저에서 Flash의 콘텐츠 표시를 허용하는 구성 요소(예: 플러그인 및 ActiveXObject 개체)를 감지하는 기능을 차단합니다. 이는 사실상 브라우저가 Flash를 지원할 수 없음을 의미합니다. ### Java 차단 {#java} @@ -95,7 +95,7 @@ The Flash Player plugin has become increasingly vulnerable to such online threat 트래픽을 필터링하기 위해 AdGuard 애플리케이션은 브라우저-서버 간 요청을 '가로채기'합니다. 광고, 추적 및 피싱 서버에 대한 요청은 서버로 전송되기 전에 변경되거나 완전히 차단될 수 있습니다. *타사 리퍼러 숨기기* 옵션도 마찬가지입니다: 이 옵션이 활성화된 경우 AdGuard는 HTTP(S) 요청, 특히 리퍼러 헤더를 제거하거나 변경하기 위해 요청을 가로챕니다. 그러나 이러한 요청은 브라우저에서 '종료'된 후에만 발생합니다. 즉, 브라우저 내부에서 리퍼러를 모니터링하는 경우(예: Chrome의 개발자 도구 사용) 요청이 아직 AdGuard에 도달하지 않았기 때문에 원래 리퍼러가 표시됩니다. [Fiddler](https://www.telerik.com/fiddler)와 같은 소프트웨어를 사용하여 Referer가 올바르게 변경되었는지 확인할 수 있습니다. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. 그러면 바로 그 자리에서 Referer가 변경되므로 개발자 도구는 귀하의 요청에 대해 원하는 Referer를 표시합니다. +반대로, 모든 브라우저 확장 프로그램의 특성상 AdGuard 브라우저 확장 프로그램은 브라우저 '내부'에서 작동합니다. 그러면 바로 그 자리에서 Referer가 변경되므로 개발자 도구는 귀하의 요청에 대해 원하는 Referer를 표시합니다. ### User Agent 숨기기 {#useragent} @@ -120,9 +120,3 @@ Custom User Agent 필드에 User Agent 값을 입력하여 임의의 값을 설 AdGuard는 클라이언트가 DPI 차단 기준에 해당하지 않도록 발신 패킷 데이터를 수정할 수 있습니다. 즉, 이 옵션을 활성화하면 사용자가 원하는 콘텐츠에 액세스할 수 있습니다. 현재 모든 DPI 시스템을 우회할 수 있는 것은 아니지만 이를 개선하기 위해 지속적으로 노력하고 있습니다. 'DPI로부터 보호' 기능은 Windows용 AdGuard, Mac용 AdGuard 및 Android용 AdGuard에 이미 구현되어 있습니다. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/ko/docusaurus-plugin-content-docs/current/general/userscripts.md index 1613d1c4479..f9172f7eb79 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. 하나 이상의 웹사이트의 기능을 수정하거나 확장합니다. 많은 AdGuard 사용자는 이미 AdGuard 어시스턴트, 팝업 차단기 및 AdGuard Extra와 같은 유저스크립트에 익숙할 것입니다. +유저스크립트('확장 프로그램'이라고도 함)는 사실상 자바스크립트로 작성된 미니 프로그램입니다. 하나 이상의 웹사이트의 기능을 수정하거나 확장합니다. 많은 AdGuard 사용자는 이미 AdGuard 어시스턴트, 팝업 차단기 및 AdGuard Extra와 같은 유저스크립트에 익숙할 것입니다. :::note 지원되는 앱 @@ -134,7 +134,7 @@ Android용 AdGuard에만 사전 설치된 스크립트입니다. Google 검색 ##### 지원되지 않는 속성 -These properties will be simply ignored by AdGuard. +이러한 속성은 Adguard에서 무시됩니다. ```text @unwrap diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/ko/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index b4b4db26111..246a5f78aef 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: HAR 파일을 수집하는 방법 sidebar_position: 1 --- diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/ko/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 050f72da679..3af37b0f537 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ AdGuard 제품을 사용하는 동안 버그를 발견하면 문제를 해결하 ### 문제를 설명하는 방법 -가능한 한 많은 세부 정보를 제공해 주시면 버그를 재현하고 수정 방법을 쉽게 파악할 수 있습니다. Here’s what we expect a bug report to include: +가능한 한 많은 세부 정보를 제공해 주시면 버그를 재현하고 수정 방법을 쉽게 파악할 수 있습니다. 버그 보고서에서 예상되는 내용은 다음과 같습니다: - 앱 버전 - OS 버전 @@ -26,9 +26,9 @@ AdGuard 제품을 사용하는 동안 버그를 발견하면 문제를 해결하 - 반복 여부 및 빈도 - VPN 또는 바이러스 백신 소프트웨어 사용 여부 -### How to collect logs +### 로그 수집 방법 -Read about collecting logs in dedicated articles for each platform. +각 플랫폼별 전용 문서에서 로그 수집에 대해 알아보세요. ## 버그 신고 또는 기능 요청에 투표하는 방법 diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/ko/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index 64f1a76a276..c88a7cff98e 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ iOS 기기는 전체 화면을 캡처하여 사진으로 저장합니다. 기본 Windows는 전체 화면을 캡처하여 클립보드에 복사합니다. -To take a screenshot of an active window, use the following shortcut keys: +활성 창의 스크린샷을 찍으려면 다음 단축키를 사용하세요. - ***Alt* 을 누른 상태에서 *PrtScn* (또는 일부 노트북에서는 *Fn + Alt + PrtScn*)을 누릅니다.** -To take a screenshot of a specific area, use the following shortcut keys: +특정 영역의 스크린샷을 찍으려면 다음 단축키를 사용하세요. - ******Win + Shift + S를*** 누릅니다.*** -스크린샷을 찍으면 클립보드에 저장됩니다. 대부분의 경우, *Ctrl + V* 단축키를 사용하여 현재 편집 중인 문서에 붙여넣을 수 있습니다. 또는 스크린샷을 파일로 저장해야 하는 경우 기본 **Paint** 프로그램(또는 이미지로 작업할 수 있는 다른 앱)을 열어야 합니다. Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +스크린샷을 찍으면 클립보드에 저장됩니다. 대부분의 경우, *Ctrl + V* 단축키를 사용하여 현재 편집 중인 문서에 붙여넣을 수 있습니다. 또는 스크린샷을 파일로 저장해야 하는 경우 기본 **Paint** 프로그램(또는 이미지로 작업할 수 있는 다른 앱)을 열어야 합니다. 동일한 단축키를 사용하거나 붙여넣기 버튼(일반적으로 화면 왼쪽 상단에 있음)을 클릭하여 스크린샷을 붙여넣은 다음 저장합니다. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. 이 버튼을 누르는 즉시 스크린샷이 *사진* → *스크린샷 폴더*에 파일로 자동 저장됩니다. +Windows 8 및 10에서는 *Win + PrtScn* 단축키를 사용하여 매우 빠르게 스크린샷을 찍을 수 있습니다. 이 버튼을 누르는 즉시 스크린샷이 *사진* → *스크린샷 폴더*에 파일로 자동 저장됩니다. 컴퓨터의 표준 프로그램 중 시작 메뉴를 통해 찾을 수 있는 *Snipping Tool* 이라는 스크린샷 전용 프로그램도 있습니다. 캡처 도구를 사용하면 바탕화면의 모든 영역이나 전체화면을 캡처할 수 있습니다. 이 프로그램을 사용하여 스크린샷을 찍은 후 사진을 편집하고 컴퓨터의 모든 폴더에 저장할 수 있습니다. @@ -70,26 +70,26 @@ Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Mac에서 스크린샷을 찍으려면 다음 단축키를 사용하세요. - ******Cmd + Shift + 3***을 길게 누릅니다.*** Mac은 전체 화면을 캡처하여 바탕 화면에 파일로 저장됩니다. -To take a screenshot of an active window, use the following shortcut keys: +활성 창의 스크린샷을 찍으려면 다음 단축키를 사용하세요. - ***⌘ Cmd + Shift + 4 + 스페이스바*를 길게 누릅니다. 포인터가 카메라 아이콘으로 변경됩니다. 창을 클릭하여 캡처합니다. 스크린샷 촬영을 취소하려면 Esc 키를 누릅니다.** -To take a screenshot of a specific area, use the following shortcut keys: +특정 영역의 스크린샷을 찍으려면 다음 단축키를 사용하세요. - *** ***⌘ Cmd + Shift + 5******를 누릅니다. 십자선을 드래그하여 필요한 영역을 선택합니다. 마우스 또는 트랙패드에서 손을 떼어 스크린샷을 찍고 Esc를 눌러 취소합니다. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +*Touch Bar* (MacBook Pro)의 스크린샷을 찍으려면 다음 단축키를 사용하세요. - ******⌘ Cmd + Shift + 6***를 누릅니다.*** Mac은 전체 *Touch Bar*를 캡처하여 바탕화면에 파일로 저장합니다. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +스크린샷을 저장하는 대신 클립보드에 복사하려면 위의 단축키 중 하나를 누른 상태에서 *Ctrl* 키를 함께 누르세요. 그런 다음 클립보드에 있는 스크린샷을 *Cmd + V* 단축키를 사용하여 현재 편집 중인 문서나 이미지에 붙여넣을 수 있습니다. **미리보기**를 사용하고 **스크린샷 찍기** (선택한 영역, 창 또는 전체 화면)를 선택하여 스크린샷을 찍을 수도 있습니다. **미리보기**를 사용하면 스크린샷을 JPG, TIFF, PDF 및 기타 파일 형식으로 저장할 수 있습니다. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/intro.md b/i18n/ko/docusaurus-plugin-content-docs/current/intro.md index d90f0f6468e..c91c5d7ac32 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/intro.md @@ -9,7 +9,7 @@ slug: / AdGuard is one of the leaders on the market of ad-blocking software with 15+ years of experience, almost a dozen products for various platforms, and over 375 million user installs. Unlike other ad-blocking solutions, most of which are browser-based, we offer standalone apps for all major platforms, both desktop and mobile. AdGuard apps are more powerful than browser extensions, can block more and do it more efficiently: - [Windows용 AdGuard](/adguard-for-windows/features/home-screen) -- [Mac용 AdGuard](/adguard-for-mac/features/main) +- [AdGuard for Mac](/adguard-for-mac/features/main) - [Android용 AdGuard](/adguard-for-android/features/protection/ad-blocking) - [iOS용 AdGuard](/adguard-for-ios/features/safari-protection) @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/acknowledgements.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/acknowledgements.md index 73ffb271c73..9cca7409681 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/acknowledgements.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/acknowledgements.md @@ -1,48 +1,48 @@ --- -title: 감사의 말 +title: Credits & Acknowledgements sidebar_position: 2 --- -우리 개발진은 서드파티 개발자, 베타 테스터 및 AdGuard의 개선과 성장에 도움을 주신 사용자들에게 감사의 뜻을 전합니다. +Our dev team would like to thank the developers of this third-party software, our beta testers and other interested users who helped AdGuard improve and grow. -## 타사 소프트웨어 {#software} +## Third-party software {#software} -다음은 AdGuard 소프트웨어 개발 과정에 도움이 된 라이브러리 및 기타 리소스 목록입니다. +This is the list of libraries and other resources that really helped us with AdGuard software development process. ## Windows용 AdGuard {#win} -- SQLLite 데이터베이스 엔진: [sqlite.org](https://sqlite.org) -- SQLite용 ADO.NET 공급자: [system.data.sqlite.org/index.html/doc/trunk/www/index.wiki](https://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki) -- Json.NET — .NET용 고성능 JSON 프레임워크: [www.newtonsoft.com/json](https://www.newtonsoft.com/json) -- AvalonEdit — WPF 기반 텍스트 편집기: [avalonedit.net](https://avalonedit.net) - -## Mac용 AdGuard {#mac} - -- Red Sweater Software, RSVerticallyCenteredTextFieldCell의 개발사: [http://www.red-sweater.com/blog/148/what-a-difference-a-cell-makes](http://www.red-sweater.com/blog/148/what-a-difference-a-cell-makes) -- ITProgressIndicator 컴포넌트용 Ilija Tovilo: [github.com/iluuu1994/ITProgressIndicator](https://github.com/iluuu1994/ITProgressIndicator) -- Sparkle.framework 컴포넌트용 Sparkle 프로젝트: [http://sparkle-project.org](http://sparkle-project.org) -- GCDAsyncSocket 컴포넌트의 Robbie Hanson: [github.com/robbiehanson/CocoaAsyncSocket](https://github.com/robbiehanson/CocoaAsyncSocket) -- Reachability 컴포넌트의 Tony Million: [github.com/tonymillion/Reachability](https://github.com/tonymillion/Reachability) -- Fmdb 컴포넌트용 August “Gus” Mueller: [github.com/ccgus/fmdb](https://github.com/ccgus/fmdb) -- SFBCrashReporter 프로젝트의 Stephen F. Booth: [github.com/sbooth/SFBCrashReporter](https://github.com/sbooth/SFBCrashReporter) -- Acextract 컴포넌트용 Bartosz Janda: [github.com/bartoszj/acextract](https://github.com/bartoszj/acextract) +- SQLLite database engine: [sqlite.org](https://sqlite.org) +- ADO.NET provider for SQLite: [system.data.sqlite.org/index.html/doc/trunk/www/index.wiki](https://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki) +- Json.NET — high-performance JSON framework for .NET: [www.newtonsoft.com/json](https://www.newtonsoft.com/json) +- AvalonEdit — WPF-based text editor component: [avalonedit.net](https://avalonedit.net) + +## AdGuard for Mac {#mac} + +- Red Sweater Software, LLC for RSVerticallyCenteredTextFieldCell component: [http://www.red-sweater.com/blog/148/what-a-difference-a-cell-makes](http://www.red-sweater.com/blog/148/what-a-difference-a-cell-makes) +- Ilija Tovilo for ITProgressIndicator component: [github.com/iluuu1994/ITProgressIndicator](https://github.com/iluuu1994/ITProgressIndicator) +- Sparkle Project for Sparkle.framework component: [http://sparkle-project.org](http://sparkle-project.org) +- Robbie Hanson for GCDAsyncSocket component: [github.com/robbiehanson/CocoaAsyncSocket](https://github.com/robbiehanson/CocoaAsyncSocket) +- Tony Million for Reachability component: [github.com/tonymillion/Reachability](https://github.com/tonymillion/Reachability) +- August «Gus» Mueller for Fmdb component: [github.com/ccgus/fmdb](https://github.com/ccgus/fmdb) +- Stephen F. Booth for SFBCrashReporter project: [github.com/sbooth/SFBCrashReporter](https://github.com/sbooth/SFBCrashReporter) +- Bartosz Janda for Acextract component: [github.com/bartoszj/acextract](https://github.com/bartoszj/acextract) - FLOPageViewController: [github.com/floschliep/FLOPageViewController](https://github.com/floschliep/FLOPageViewController) ## Android용 AdGuard {#android} -- Tony19의 Logback-android: [tony19.github.io/logback-android](https://tony19.github.io/logback-android) -- Square의 Otto: [http://square.github.io/otto](http://square.github.io/otto) -- Stericson의 RootTools 라이브러리: [github.com/Stericson/RootTools](https://github.com/Stericson/RootTools) -- Supratim Chakraborty의 MaterialDateRangePicker: [github.com/borax12/MaterialDateRangePicker](https://github.com/borax12/MaterialDateRangePicker) -- Leszek Wach의 HelloCharts: [github.com/lecho/hellocharts-android](https://github.com/lecho/hellocharts-android) +- Logback-android by Tony19: [tony19.github.io/logback-android](https://tony19.github.io/logback-android) +- Otto by Square: [http://square.github.io/otto](http://square.github.io/otto) +- RootTools Library by Stericson: [github.com/Stericson/RootTools](https://github.com/Stericson/RootTools) +- MaterialDateRangePicker by Supratim Chakraborty: [github.com/borax12/MaterialDateRangePicker](https://github.com/borax12/MaterialDateRangePicker) +- HelloCharts by Leszek Wach: [github.com/lecho/hellocharts-android](https://github.com/lecho/hellocharts-android) ## iOS용 AdGuard {#ios} -- Tony Million의 도달 가능성 컴포넌트: [github.com/tonymillion/Rachability](https://github.com/tonymillion/Reachability) -- August «Gus» Mueller의 Fmdb 컴포넌트: [github.com/ccgus/fmdb](https://github.com/ccgus/fmdb) -- Nate Weaver의 NSStringPunycodeAdditions 컴포넌트: [github.com/Wevah/Punycode-Cocoa](https://github.com/Wevah/Punycode-Cocoa) -- Nathan Moinvaziri의 Minizip-ng 라이브러리: [github.com/zlib-ng/minizip-ng](https://github.com/zlib-ng/minizip-ng) -- Brandon Withrow의 iOS용 Lottie 라이브러리: [github.com/airbnb/lottie-ios](https://github.com/airbnb/lottie-ios) +- Reachability component by Tony Million: [github.com/tonymillion/Reachability](https://github.com/tonymillion/Reachability) +- Fmdb component by August «Gus» Mueller: [github.com/ccgus/fmdb](https://github.com/ccgus/fmdb) +- NSStringPunycodeAdditions component by Nate Weaver: [github.com/Wevah/Punycode-Cocoa](https://github.com/Wevah/Punycode-Cocoa) +- Minizip-ng library by Nathan Moinvaziri: [github.com/zlib-ng/minizip-ng](https://github.com/zlib-ng/minizip-ng) +- Lottie for iOS library by Brandon Withrow: [github.com/airbnb/lottie-ios](https://github.com/airbnb/lottie-ios) ## AdGuard 확장 프로그램 {#extension} @@ -86,7 +86,7 @@ sidebar_position: 2 - request: [github.com/request/request](https://github.com/request/request) - require-dir: [github.com/aseemk/requireDir](https://github.com/aseemk/requireDir) -## AdGuard 브라우저 어시스턴트 {#assistant} +## AdGuard Browser Assistant {#assistant} - React: [github.com/facebook/react](https://github.com/facebook/react) - webextension-polyfill: [github.com/mozilla/webextension-polyfill](https://github.com/mozilla/webextension-polyfill) @@ -113,7 +113,7 @@ sidebar_position: 2 - Chromium: [github.com/chromium/chromium/blob/master/LICENSE](https://github.com/chromium/chromium/blob/master/LICENSE) - Detours: [github.com/microsoft/Detours/blob/main/LICENSE.md](https://github.com/microsoft/Detours/blob/main/LICENSE.md) - eDistantObject: [github.com/google/eDistantObject/blob/master/LICENSE](https://github.com/google/eDistantObject/blob/master/LICENSE) -- Simon Zolin의 FF/FFOS 라이브러리: [github.com/stsaz/ffbase/blob/master/README.md](https://github.com/stsaz/ffbase/blob/master/README.md) +- FF/FFOS libs by Simon Zolin: [github.com/stsaz/ffbase/blob/master/README.md](https://github.com/stsaz/ffbase/blob/master/README.md) - Google test: [github.com/google/googletest/blob/master/LICENSE](https://github.com/google/googletest/blob/master/LICENSE) - http-parser: [github.com/nodejs/http-parser/blob/master/LICENSE-MIT](https://github.com/nodejs/http-parser/blob/master/LICENSE-MIT) - jsmn: [github.com/zserge/jsmn/blob/master/LICENSE](https://github.com/zserge/jsmn/blob/master/LICENSE) @@ -127,58 +127,58 @@ sidebar_position: 2 - SQLite: [www.sqlite.org/copyright.html](https://www.sqlite.org/copyright.html) - zlib: [zlib.net/zlib_license.html](https://zlib.net/zlib_license.html) -## 특별한 감사의 말 {#testers} - -더불어 모든 베타 테스터들과, 버그를 찾거나 제거하고 AdGuard를 번역하며 커뮤니티를 조정할 수 있도록 귀중한 도움을 주신 것에 큰 감사를 표합니다. 특별 기여자 명단: - -- ag_bug_finder — Windows용 AdGuard의 베타 테스터 -- Aikatsui — AdGuard Home의 적극적인 기여자 -- Andy Kleinert (AndyKl) — Crowdin의 독일어 번역자 및 교정자 -- BigDargon - AdGuard DNS 목록에 hostsVN 프로젝트를 소스로 제공했습니다. -- Blaz — 필터 기여자로 시작하여 현재 AdGuard에서 근무 -- Boo Berry — Telegram 그룹 중재자 -- buuuuuuu190 — 베타 테스터 -- clarke — 베타 테스터 -- [dartrax](https://github.com/dartrax) — 베타 테스터 -- dja2k — 베타 테스터 -- Eduardo Addad de Oliveira (eduardoaddad) — Crowdin의 포르투갈어와 브라질어 번역자 및 교정자 -- fabjazz — 베타 테스터 -- Görkem Emrah Güler (gork7777) — Crowdin의 튀르키예어 번역가 및 교정자 -- hanschke — 베타 테스터 -- iDjay — iOS용 AdGuard의 뛰어난 베타 테스터 -- Imre Kristoffer Eilertsen (DandelionSprout) — 모든 AdGuard 도구에 포함된 "Dandelion Sprout’s Nordic Filters" 유지 관리자 -- IONIL — Crowdin의 히브리어 번역가 및 교정자 -- itabmedia — 베타 테스터 -- kirasam — 베타 테스터 -- krystian3w — 매우 적극적인 필터 기여자 -- lancelot.moon — Crowdin의 중국어 번체 번역가 및 교정자, 베타 테스터 -- Lord Ami — 베타 테스터 -- Lukas Novotny (novas78) — Crowdin의 체코어 번역가 및 교정자 -- malware1 — 베타 테스터 -- milder — 베타 테스터 -- Nicos18 — 베타 테스터 -- Oizaro — Crowdin의 이탈리아어 번역가 및 교정자 -- Oleg Chashko — 매우 적극적인 Safari용 AdGuard 베타 테스터 -- Oskari Lavinto (olavinto) — Crowdin의 핀란드어 번역가 및 교정자 -- ouzbed — 베타 테스터 -- PentagramTr — 필터 기여자, 즉, 튀르키예어 필터에 많은 새로운 것을 제공 -- Peter Hubinsky (hubak) — Crowdin의 슬로바키아어 번역가 및 교정자 -- PiQuark6046 — 필터 기여자 -- rickyoh — 베타 테스터 -- Ronin427 — 베타 테스터 -- Sanjay Nand — 베타 테스터 -- saturnotaku — 베타 테스터 -- steve1209 — 베타 테스터 -- streetwolf — 베타 테스터 -- superlex — scriptlets, 필터, Safari용 AdGuard에 도움 -- TayTayTheKiller — 베타 테스터 -- [TPS](https://github.com/TPS) — 버그 수색자, 필터 기여자 -- Yuki2718 — AdGuard 필터의 적극적인 기여자 -- zznosar — iOS용 AdGuard 중심의 적극적 베타 테스터 -- Sergey Zozulya(sviperz) — 우리 Telegram 그룹의 적극적인 멤버, 베타 테스터 +## Special thanks {#testers} + +Also a huge thanks and gratitude to all beta testers and other engaged users, whose help in finding/eliminating all the bugs, translating AdGuard and moderating our communities was priceless. Special thanks to: + +- ag_bug_finder — beta tester of AdGuard for Windows +- Aikatsui — active contributor to AdGuard Home +- Andy Kleinert (AndyKl) — translator and proofreader to German in Crowdin +- BigDargon — contributed the hostsVN project as a source to the list of AdGuard DNS +- Blaz — started as a filter contributor and now working at AdGuard +- Boo Berry — Telegram group moderator +- buuuuuuu190 — beta tester +- clarke — beta tester +- [dartrax](https://github.com/dartrax) — beta tester +- dja2k — beta tester +- Eduardo Addad de Oliveira (eduardoaddad) — translator and proofreader to Portuguese and Portuguese, Brazilian in Crowdin +- fabjazz — beta tester +- Görkem Emrah Güler (gork7777) — translator and proofreader to Turkish in Crowdin +- hanschke — beta tester +- iDjay — outstanding beta tester of AdGuard for iOS +- Imre Kristoffer Eilertsen (DandelionSprout) — maintainer of "Dandelion Sprout’s Nordic Filters" that are included in all AdGuard tools +- IONIL — translator and proofreader to Hebrew in Crowdin +- itabmedia — beta tester +- kirasam — beta tester +- krystian3w — very active filter contributor +- lancelot.moon — translator and proofreader to Chinese Traditional in Crowdin, beta tester +- Lord Ami — beta tester +- Lukas Novotny (novas78) — translator and proofreader to Czech in Crowdin +- malware1 — beta tester +- milder — beta tester +- Nicos18 — beta tester +- Oizaro — translator and proofreader to Italian in Crowdin +- Oleg Chashko — very active beta tester of AdGuard for Safari +- Oskari Lavinto (olavinto) — translator and proofreader to Finnish in Crowdin +- ouzbed — beta tester +- PentagramTr — filter contributor, namely, he has brought a lot of new things to the Turkish filter +- Peter Hubinsky (hubak) — translator and proofreader to Slovak in Crowdin +- PiQuark6046 — filter contributor +- rickyoh — beta tester +- Ronin427 — beta tester +- Sanjay Nand — beta tester +- saturnotaku — beta tester +- steve1209 — beta tester +- streetwolf — beta tester +- superlex — helps us with scriptlets, filters, and AdGuard for Safari +- TayTayTheKiller — beta tester +- [TPS](https://github.com/TPS) — bug finder, filter contributor +- Yuki2718 — actively contributes to AdGuard filters +- zznosar — active beta tester focused on AdGuard for iOS +- Sergey Zozulya (sviperz) — active member of our Telegram group, beta tester --- -우리는 또한 [xda-developers 이용자들](https://forum.xda-developers.com/t/app-android-5-0-3-4-120-21-05-2020-adguard-no-root-ad-blocker.2958895/)에게 감사드립니다. 유용한 피드백을 보내 주셔서 감사합니다! +We also want to thank the [xda-developers users](https://forum.xda-developers.com/t/app-android-5-0-3-4-120-21-05-2020-adguard-no-root-ad-blocker.2958895/). Thank you for your helpful feedback! -우리는 언제나 우리 소프트웨어의 사용자들, 특히 열성적인 사용자들의 의견에 감사드립니다. 언제든지 우리에게 연락하여 AdGuard에 대한 의견을 공유하고, 새로운 기능을 요청하고, 버그를 제출할 수 있습니다. [AdGuard 서브레딧](https://reddit.com/r/adguard), [Xda-developers 포럼](https://forum.xda-developers.com/t/app-android-5-0-3-4-120-21-05-2020-adguard-no-root-ad-blocker.2958895/)에 가입하거나 [GitHub](https://github.com/AdguardTeam)에서 우리의 페이지를 방문하세요. +We always appreciate comments from our users, especially constructive ones. You can always contact us to share your thoughts about AdGuard, request new features, and submit bugs. Join the [AdGuard Subreddit](https://reddit.com/r/adguard), [Xda-developers Forum](https://forum.xda-developers.com/t/app-android-5-0-3-4-120-21-05-2020-adguard-no-root-ad-blocker.2958895/) or visit our page on [GitHub](https://github.com/AdguardTeam). diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/beta-testing.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/beta-testing.md index 3d5da96692e..c0a361c8894 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/beta-testing.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/beta-testing.md @@ -1,34 +1,34 @@ --- -title: AdGuard 베타 테스트 +title: AdGuard beta testing sidebar_position: 1 --- -거의 모든 주요 플랫폼을 위한 AdGuard 앱이 있으며, 모든 플랫폼에 대한 업데이트를 정기적으로 출시합니다. 이는 베타 테스트, 더 중요한 것은 베타 테스터 없이는 불가능합니다. 베타 테스터가 되고 싶다면 아래 방법을 확인하세요. +There is an AdGuard app for virtually every major platform out there, and we regularly release updates for all of them. This would not be possible without beta testing and, more importantly, beta testers. Want to become one? Here's how you can do it. -## 베타 테스터가 되는 방법 {#intro} +## How to become a beta tester {#intro} -AdGuard를 사용하고, 베타 버전이 출시되면 베타 버전으로 업그레이드하고, 발견되는 버그를 신고하세요. 하지만 베타 테스터가 되려면 [GitHub](https://github.com/) 계정이 필요하므로 먼저 계정을 만드는 것이 좋습니다. +Our requirements are easy: use AdGuard, upgrade to the beta version when it becomes available, and report any bugs you notice. However, you will need a [GitHub](https://github.com/) account to become our beta tester, so you may want to get that out of the way first. -어떤 경우든 알아야 할 모든 정보가 [전용 페이지](https://adguard.com/beta.html)에 모여 있습니다. +In any case, every single thing you need to know is gathered on a [dedicated page](https://adguard.com/beta.html). -설명 부분을 건너뛰고 바로 실행에 옮기고 싶다면 [여기](https://surveys.adguard.com/beta_testing_program/form.html)에서 신청할 수 있습니다. 신청서는 영업일 기준 1~3일 이내에 검토되며 이메일을 통해 회신해 드립니다. +If you want to skip the description part and get straight to the action, you can apply [here](https://surveys.adguard.com/beta_testing_program/form.html). Your application will be reviewed within 1-3 working days, and you'll get a reply via email. -## 버그를 신고하는 방법 {#report-a-bug} +## How to report a bug {#report-a-bug} -버그를 발견했거나 제안을 공유하고 싶으시면 [GitHub](https://github.com/AdguardTeam/)로 이동하여 적합한 리포지토리를 찾은 후 새 이슈를 생성하고 버그/기능 요청을 자세히 설명해 주세요. +If you spotted a bug or just want to share your suggestion, let us know: go to [GitHub](https://github.com/AdguardTeam/), find a suitable repository, create a new issue there, and describe the bug/feature request in detail. -이상의 방법이 가장 선호되지만, 만약 필요하다면 다른 방법을 사용할 수도 있습니다: +The above method is the most preferred, but you can use others if necessary: -- [Facebook](https://www.facebook.com/AdguardEn/), [Reddit](https://www.reddit.com/r/Adguard/) 등 다양한 소셜 미디어 플랫폼에서 저희를 만나보세요. 하지만 이는 기술적인 문제를 논의하는 데 가장 편리한 방법은 아닙니다. +- Find us on various social media platforms, like [Facebook](https://www.facebook.com/AdguardEn/), [Reddit](https://www.reddit.com/r/Adguard/), etc. However, this is not the most convenient way to discuss technical matters. -- 앱의 지원 탭에서 저희의 지원 팀에게 이메일을 보내거나, [support@adguard.com](mailto:support@adguard.com)으로 직접 보내주세요. +- Email our support team from the Support tab in the app or write directly to [support@adguard.com](mailto:support@adguard.com). -## iOS 앱에서 베타 키를 활성화하는 방법 {#ios} +## How to activate the beta key in the iOS application {#ios} -이미 베타 키를 받았고 `adguard.com` 계정에 베타 키가 등록되어 있는 경우 앱으로 이동하여 라이선스 섹션(프리미엄 받기)을 엽니다. AdGuard 계정의 자격 증명을 입력하세요. 그 후에는 프리미엄 기능을 자동으로 사용할 수 있게 됩니다. +If you have already received a beta key and it is listed in your `adguard.com` account, go to the app and open the license section (Get Premium). Once there, enter the credentials from your AdGuard account. After that, the premium features will become available automatically. -### 기타 +### What else? -더 이상 추가할 내용이 많지 않습니다. 버그를 찾기 위해 직접 찾아다니지 않아도 됩니다. 평소와 같이 AdGuard를 계속 사용할 수 있습니다. 하지만 버그가 발견되면 신고해 주세요. 물론 추가적인 노력에 감사드립니다. +There is not much more to add. You don't have to go out of your way to find bugs. You can continue using AdGuard as usual. However, if you encounter a bug, please report it. Of course, we appreciate any additional effort. -가끔씩 뉴스레터를 통해 베타의 최신 변경 사항(놓친 경우) 및 기타 중요한 소식을 알려드립니다. 언제든 구독을 취소할 수 있습니다. +Occasionally, you will receive our newsletters, keeping you informed of the latest changes in the beta (in case you missed them) and other important news. You can unsubscribe from it at any time. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index db637fc3042..963fdf6dfae 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -1,20 +1,20 @@ --- -title: AdGuard 필터에 기여하기 +title: Contribute to AdGuard filters sidebar_position: 4 --- -### 필터링 규칙 {#filtering-rules} +### Filtering rules {#filtering-rules} -아시다시피 AdGuard는 필터링 규칙을 사용하여 광고를 차단하며, 이러한 규칙은 AdGuard 기본 필터, 모바일 광고 필터 등과 같은 주제별 [차단 필터](/general/ad-filtering/adguard-filters)로 결합됩니다. [광고 차단 작동 방식에 대해 자세히 읽어보세요](/general/ad-filtering/how-ad-blocking-works). +As you probably know, AdGuard uses filtering rules to block ads, and these rules are combined into thematic [blocking filters](/general/ad-filtering/adguard-filters), like AdGuard Base filter, Mobile ads filter, etc. [Read more about how ad blocking works](/general/ad-filtering/how-ad-blocking-works). -웹사이트는 광고 삽입 방식을 지속적으로 변경하고 있으며, 저희는 필터에 새로운 규칙을 추가해서 대응합니다. 필터 개발자들은 새로운 규칙을 만들기 위해 노력하고 있지만, 우리는 언제나 자원봉사자들의 도움과 지원을 환영합니다. +Websites constantly change the way they embed ads, and we add new rules to our filters to keep them effective. Filter engineers are working on creating new rules, but we always welcome the help and support of volunteers. -### 시작하는 법 {#how-to-start} +### How to start {#how-to-start} -하지만, 차단 필터를 다루기 위해서는 특정한 기술들이 필요합니다. 그 기술들과 규칙을 만드는 법을 알고 있다면 [GitHub의 AdGuard 필터 저장소로](https://github.com/AdguardTeam/AdguardFilters) 오세요. 이곳에는 놓친 광고, 잘못된 판단 등 웹사이트 문제와 관련된 여러 가지 미해결 문제들이 있습니다. 자유롭게 골라서 댓글로 당신만의 규칙을 제안해보세요. AdGuard 필터 개발자가 귀하의 제안을 검토하고 적절하다고 판단하면 당신의 규칙이 AdGuard 필터에 추가됩니다. +However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -필터링 규칙 구문에 아직 익숙하지 않거나 복습이 필요한 경우 [저희의 지식 창고에서](/general/ad-filtering/create-own-filters) 구문의 기본에 대해 알아볼 수 있습니다. +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). -### 보상 {#rewards} +### Rewards {#rewards} -당신이 여러 필터링 규칙을 제안하고 그 중 일부가 승인되었다면 이제 보상을 받을 차례입니다. GitHub 계정 이름과 함께 [st@adguard.com](mailto:st@adguard.com) 로 메일을 보내주시면 무료 AdGuard 라이선스 키를 받으실 수 있습니다. 자격을 얻기 위해 승인을 받아야 하는 규칙의 정확한 갯수에 대해서는 엄격한 규칙이 없습니다. 이 작업은 쉽지 않죠. 그러니 5개 이상이면 충분합니다. +If you have suggested several filtering rules and some of them were approved, then it's time for you to get a reward. Send us a message at [st@adguard.com](mailto:st@adguard.com) with your GitHub account name, and you'll get a free AdGuard license key. As for the exact number of rules you need to get approved to become eligible, there are no hard rules. This task is not easy, so anything north of 5 should be enough. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index bda92ebceb4..5bdb5650dad 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -35,7 +35,7 @@ Crowdin에 가입·로그인한 후, [AdGuard 페이지](https://crowdin.com/pro ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/mode.png) -[이 글에서 AdGuard 번역에 대한 몇 가지 유용한 팁](../guidelines)을 확인할 수 있습니다. 한번 살펴보시기 바랍니다. +[이 글에서 AdGuard 번역에 대한 몇 가지 유용한 팁](../guidelines)을 확인할 수 있습니다. Please take a look at it. ### 교정자가 되는 방법 {#proofreaders} @@ -51,4 +51,4 @@ AdGuard에는 각 언어별로 프루프리더(이전에는 모더레이터라 - 해당 언어로 번역과 관련된 댓글에 응답합니다. -AdGuard는 매년 최고의 교정자에게 선물을 증정합니다. 물론, 활동적인 번역가들에게도 보상이 제공됩니다. AdGuard의 [보상 시스템](../rewards)에 대해 자세히 알아보세요. +Every year, the best proofreaders receive gifts from AdGuard. 물론, 활동적인 번역가들에게도 보상이 제공됩니다. AdGuard의 [보상 시스템](../rewards)에 대해 자세히 알아보세요. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/guidelines.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/guidelines.md index 20c934e20f9..16b0513f607 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/guidelines.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/guidelines.md @@ -1,87 +1,87 @@ --- -title: 지침 및 권장 사항 +title: Guidelines and recommendations sidebar_position: 3 --- -번역을 시작하기 전에 몇 가지 사항을 알아두어야 합니다. 이는 시간과 노력을 아낄 수 있을 뿐만 아니라, 번역되는 문구의 의미에 대해 통일성을 키워줄 것입니다. +There are several things we'd like you to know before you start translating. It will not only save your time and effort, but also ensure that we are on the same page in terms of the meaning of phrases being translated. -저희의 [Crowdin 페이지](https://crowdin.com/profile/adguard/)를 연 다음, 원하는 프로젝트와 언어를 선택하세요. +Once you open [our page on Crowdin](https://crowdin.com/profile/adguard/), choose any project you need and select your language. -![언어 *border](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/language.png) +![Language *border](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/language.png) -특정 제품의 폴더를 연 후에도 언어 간 전환이 가능합니다. +You'll also be able to switch between languages even after opening certain product folders. -![언어1 *border](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/language1.png) +![Language1 *border](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/language1.png) -사용 가능한 제품 폴더 중 하나를 선택하고 파일을 선택하면 이제 번역을 시작할 수 있습니다. +Choose any of available product folders and select a file — now you can start translating. -![파일 *border](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/files.png) +![Files *border](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/files.png) :::note -또한 페이지 오른쪽 상단에 있는 *설정* 아이콘을 클릭하여 Crowdin 인터페이스 언어를 변경할 수 있습니다. 열린 창에서 *UI language* 탭까지 아래로 스크롤하세요. 열어서 언어를 선택하고 **Change**를 클릭하세요. +You can also change the Crowdin interface language by clicking the *Settings* icon in the top right corner of the page. In the opened window scroll down to the *UI language* tab. Open it, choose a language and click **Change**. ::: -![언어1 *border](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/settings_en.png) +![Language1 *border](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/settings_en.png) -**다음 지침은 이 과정을 진행하는 데 도움이 될 것입니다.** +**The following guidelines will help you through the process.** -1. 이 버튼을 클릭하고 제공되는 옵션을 선택하여 번역을 필터링할 수 있습니다. +1. You can filter translations by clicking this button and selecting any offered option. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/filter.png) -1. 프로젝트의 파일 사이를 쉽게 이동하세요. +1. Easily move between the files of the project. ![crowdin *border](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/filter_files.png) -1. 출처 문구에서 점선으로 강조된 용어집 용어에 주의하세요. 일반적으로 번역해서는 안 되는 특수 단어(예: 브랜드 이름)입니다. +1. Pay attention to the glossary terms highlighted with a dotted line in a source phrase. Usually, they are special words (like brand names) that should not be translated. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/terms.png) - [AdGuard Glossary](https://crowdin.com/project/adguard-glossary) 프로젝트에서 번역 가능한 용어에 대한 번역을 제안할 수 있습니다. + You can suggest your translation for translatable terms in the [AdGuard Glossary](https://crowdin.com/project/adguard-glossary) project. -1. Crowdin에서 문자열에는 문구를 더 쉽게 이해하고 번역할 수 있는 메모가 있습니다. 소스 문자열의 'Context' 필드에서 해당 문자열을 찾습니다. +1. In Crowdin, strings can have notes that make it easier to understand and translate phrases. Look for them in the "Context" field of the source string. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/context-note.png) -1. 소스 문자열은 Context 섹션에 스크린샷이 있을 수도 있습니다. 문맥을 이해하고 정확한 의미를 전달하는 데 도움이 됩니다. +1. Note that source strings may also have screenshots in the Context section. They help to understand the context and convey the exact meaning. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/screenshot.png) :::tip - 'REQUEST' 버튼을 클릭하여 컨텍스트를 요청할 수 있습니다. + You can request context by clicking the "REQUEST" button. ::: ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/request.png) -1. 새 번역을 제안하는 것 외에도 문자열에 댓글을 남길 수도 있습니다. 댓글을 사용하여 소스 텍스트 또는 기존 번역의 오류를 알려주거나 메모를 남기거나 질문을 할 수 있습니다. 번역에 댓글이 남아있는 경우 댓글에 응답해 보세요. +1. In addition to suggesting new translations, you can also leave comments on strings. Use comments to let us know about mistakes in the source text or existing translations, make notes, or ask questions. If you see a comment left on your translation — try to respond to it. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/comments.png) - 또한 메인 프로젝트 페이지에 **토론** 탭이 있어 이 프로젝트의 특정 언어에 대한 모든 댓글을 편리하게 볼 수 있습니다. + There's also a **Discussions** tab on the main project page that conveniently allows you to see all the comments for the specific language in this project. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/discussions.png) -1. Crowdin은 *번역 메모리*라는 매우 유용하고 편리한 도구를 제공합니다. 이 기능을 사용하면 동일한 단어와 구문에 대해 이전에 만든 번역을 찾아 번역에 재사용할 수 있습니다. +1. Crowdin provides a very useful and convenient tool called *Translation Memory*. With its help, you can find the previously made translations of the same words and phrases and reuse them in your translations. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/tm.png) -1. '참여' 버튼을 클릭하여 프로젝트에 참여하면 프로젝트 페이지에 **Tasks** 탭이 표시되며, 여기서 특정 프로젝트 파일에 대한 작업이 만들어집니다. *일반적으로 우선 순위가 더 높으니 주의하세요.* +1. Once you join a project by clicking the "Join" button, you will see the **Tasks** tab on the project page, where the tasks for specific project files get created. *Please pay attention to them: they usually have a higher priority.* ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/tasks.png) -1. 때로는 복수형이 포함된 문구가 있을 수 있습니다. 이러한 문구를 번역할 때는 특히 주의하시기 바랍니다. [여기](../plural-forms)에서 복수형을 번역하는 방법에 대해 읽어보세요. +1. Sometimes you can find phrases with plural forms. Please be especially attentive when translating such phrases. You can read how to translate plural forms [here](../plural-forms). ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/plurals.png) - 적절한 복수형을 사용하는 것은 매우 중요합니다. 불분명한 점이 있으면 댓글로 문의해 주세요. + Using proper plural forms is extremely important: please ask us in the comments if anything is unclear. -1. **프로젝트 정보에 나열된 프로젝트 관리자 및 교정자에게 직접 메세지를 보내지 마십시오.** +1. **Please do not write directly to the project managers and proofreaders listed in the Project info.** - 번역에 대해 궁금한 점이 있으면 언제든지 댓글을 통해 교정자나 관리자에게 문의할 수 있습니다. + If you have questions about translations, you can always ask our proofreaders or admins through comments. - 또는 [translate@adguard.com](mailto:translate@adguard.com)으로 이메일을 보내거나 [Telegram 채팅](https://t.me/joinchat/UVYTLcHbr8JmOGIy)에서 질문할 수도 있습니다. 관리자가 최대한 빠르게 답변해드리겠습니다. + Also, you can send an email to [translate@adguard.com](mailto:translate@adguard.com) or ask a question in the [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). The Admins will answer you as soon as possible. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index 80043ed5f39..b8e95e7faf9 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -1,156 +1,156 @@ --- -title: 복수형 +title: Plural forms sidebar_position: 4 --- -전 세계 언어에는 많은 차이가 있습니다. 이러한 차이점 중 하나는 현지화 문제와 관련하여 큰 어려움을 야기할 수 있는 복수형 사용입니다. +There are a lot of differences between the world’s languages. One of these differences is the use of plural forms that can cause huge difficulties when it comes to localization issue. 복수형에 대한 자세한 내용과 AdGuard 번역에서 복수형이 어떻게 사용되는지 알아보려면 이 글을 읽어보세요. -## 복수형은 무엇을 의미하나요? {#plurals} +## What do plural forms mean? {#plurals} -어떤 언어의 명사는 여러 복수형 단어 형태를 가질 수 있습니다. 사용법은 대화하는 대상의 수에 따라 다릅니다. +Nouns in different languages can have several plural word forms. Their usage depends on the number of things you are talking about. -예를 들어, 영어 단어는 단수형으로 무언가를 말할 때 두 가지 단어 형태를 갖습니다. 예를 들어 *'one star'*와 같고, 복수형으로는 *'two stars'*와 같습니다. 별 5개, 26개, 또는 532개라고 말하더라도 마지막 글자 's'는 동일하게 유지됩니다. 그러나 일부 언어에는 복수형이 하나 또는 여러 개가 포함될 수 있습니다. 별 5개, 26개, 또는 532개라고 말하더라도 마지막 글자 's'는 동일하게 유지됩니다. 그러나 일부 언어에는 복수형이 하나 또는 여러 개만 포함될 수 있습니다. +For instance, English words have two word forms when speaking about something in the singular, like *'one star'*, and in the plural — *'two stars'*. It doesn’t matter if you say five, twenty six or even five hundred thirty two stars — the ending 's' will remain the same. But some languages can contain only one or many plural forms. -영어와 달리 폴란드어에는 세 가지 복수형 명사가 있습니다. 그 중 하나는 단수로 무언가를 말할 때 사용되고, 다른 형태는 복수형으로 사용되지만 12~14를 제외하고 2~4로 끝나는 숫자가 사용되며, 세 번째 형태는 앞에 다른 숫자가 붙은 단어에 사용됩니다. +In contrast to English, the Polish language has three plural forms of nouns. One of them is used when speaking about something in the singular, another form is used in the plural but with numbers ending in 2–4, excluding 12–14, and the third form — for words with other numbers in front of them. -이 사진을 살펴보겠습니다. 여기에서 단어 앞에 있을 때 단어의 형태를 결정하는 숫자 그룹을 볼 수 있습니다. +Let’s take a look at this picture. Here you can see the groups of numerals which determine a word form when standing in front of it. -![폴란드어](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/polish.png) +![Polish](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/polish.png) -이해를 돕기 위해 영어와 폴란드어를 조금 비유해 보겠습니다. +Let’s draw a small parallel between English and Polish for better understanding: - 영어： 폴란드어： + The English version: The Polish equivalents: - 1. 형식 — It takes one hour. 1. 형식 — Zajmuje to godzinę. - 2. 형식 — It takes two hours. 2. 형식 — Zajmuje to dwie godziny. - 3. 형식 — It takes five hours. 3. 형식 — Zajmuje to pięć godzin. + 1. form — It takes one hour. 1. form — Zajmuje to godzinę. + 2. form — It takes two hours. 2. form — Zajmuje to dwie godziny. + 3. form — It takes five hours. 3. form — Zajmuje to pięć godzin. -폴란드어 *'godzinę'*(시간)은 세 가지 형태가 있는 반면 영어 단어는 주어진 숫자에 따라 형태가 두 번만 바뀝니다. +Now it is clear that the Polish *'godzinę'* (hour) has three different forms, whereas the English word changes its form with given numbers only twice. -폴란드어 외에도 러시아어, 세르비아어, 슬로바키아어, 체코어 등 3개 이상의 복수형이 있는 언어가 많이 있습니다. 하지만 모두 같은 규칙을 따르는 것은 아닙니다. 그렇기 때문에 언어에 복수형이 몇 개나 있는지, 그리고 복수형을 올바르게 사용하는 방법을 아는 것이 매우 중요합니다. +Except for Polish, there are a lot of other languages that have three plural forms and more, such as Russian, Serbian, Slovak, Czech etc. But not all of them obey the same rule. That's why it's so important to know how many plurals your language has, and how to use them correctly. -## 복수형 수에 대한 정보는 어디에서 확인할 수 있나요? {#where-to-learn} +## Where can you learn about the number of plural forms? {#where-to-learn} -복수형을 사용해야 하는 번역에 직면했을 때 해당 언어에 얼마나 많은 단어 형태가 포함되어 있는지 바로 알아차리지 못할 수 있습니다. +When you are faced with a translation that requires the use of plurals, you may not be able to realize right away how many word forms your language contains. -다음은 사용할 수 있는 몇 가지 정보 출처입니다. +Here are some sources of information you can use. -[현지화 가이드](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html)에는 다양한 언어 목록이 포함되어 있습니다. 다른 언어의 복수형 수는 `nplurals=2`, `nplurals=4` 등과 같은 방식으로 표시됩니다. 등호 기호 `=` 뒤의 숫자는 해당 언어의 복수형 개수를 나타냅니다. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. -또한 [Unicode Common Locale Data Repository(CLDR)](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules)에서 복수형에 대한 정보를 확인할 수 있습니다. CLDR 복수형 규칙은 10진수(1.5, 2.3, 100.1…)에 대한 추가 단어 형식을 나타내지만 AdGuard 번역에는 사용하지 않습니다. +Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. -## AdGuard 번역의 복수형 {#translations} +## Plurals in AdGuard translations {#translations} -우선, 모든 AdGuard 번역에 복수형을 사용해야 하는 것은 아닙니다. +First of all, we want to mention that not every AdGuard translation requires the use of plural forms. -현재 Crowdin에는 복수형을 사용하는 4가지 유형의 문자열이 있습니다. +Currently, we have 4 types of strings on Crowdin that involve the use of plurals. -자세히 살펴보겠습니다. +Let's take a closer look at them. -### 1. `.singular`, `.dual`, `.plural`로 끝나는 문자열 키가 있는 구문이 있습니다. {#1type} +### 1. Phrases with string keys ending in `.singular`, `.dual`, `.plural` {#1type} ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/plurals/dual_it.png) -대부분은 `AdGuard for Windows` 프로젝트에 표시되며 한두 개의 단어로만 구성됩니다. +Most of them are represented in the `AdGuard for Windows` project and consist of only one or two words: -- `days` -- `extensions` +- `days;` +- `extensions;` - `hours` -이러한 구문의 문자열 키와 복수형에 대한 몇 가지 중요한 메모를 볼 수 있는 'Context' 필드에 주의하세요. 문자열 키에는 `Singular`, `Dual`, `Plural`의 단어가 포함될 수 있습니다(예: `FormatDayDeclensionDual`). 이 경우에는 키에 지정된 대로 적절한 복수형을 그대로 두어야 합니다. +Please pay attention to the string keys of such phrases and to the "Context" field where you can see some important notes about plurals. The string keys may contain `Singular`, `Dual`, `Plural` words (ex.`FormatDayDeclensionDual`). In this case, you should leave the appropriate plural form as it is specified in the key. -### 2. 단수 및 복수 명사가 쉼표로 구분된 문자열 {#2type} +### 2. Strings with singular and plural nouns separated by commas {#2type} -이러한 종류의 문자열은 대부분 `AdGuard for Android` 프로젝트에 집중되어 있습니다. +This kind of strings is mostly concentrated in the `AdGuard for Android` project. -다음 예를 살펴보세요. +Please look at the example: ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/plurals/android_fr.png) -폴란드어와 같이 사용 중인 언어에 복수형 명사가 3개가 있는 경우, 모든 복수형을 쉼표로 구분하여 작성하세요. +If there are 3 plural forms of nouns in your language (like in Polish), please write all plural forms separated by commas. `hour, hours — godzinę, godziny, godzin` -명사의 형식이 2개만 있는 경우 같은 형식을 두 번 쓸 필요가 없습니다. *이 규칙은 복수가 포함된 문자열에만 적용됩니다.* 하지만 형식을 두 번 반복해도 괜찮습니다. +In case a noun has only 2 forms, there is no need to write the same form twice (*typically only for this type of strings with plurals!*). However, it won't be a mistake if you repeat the form twice. -### 3. Crowdin이 개발한 패턴을 사용하는 문자열 {#3type} +### 3. Strings that use the Crowdin-developed pattern {#3type} -이것은 복수형이 포함된 문자열을 번역하는 가장 사용자 친화적인 방식입니다. +This is the most user-friendly scheme of translating strings with plurals. -Crowdin은 사용자에게 다양한 복수형을 가진 특정 양의 문구를 번역할 것을 제안합니다. +Crowdin suggests to users that they translate the certain amount of phrases with different plural forms. -언어가 복수형 하나만 제공하는 경우, 번역할 구문은 하나만 표시됩니다. 형식이 3개 이상인 경우, Crowdin은 번역할 문자열을 다른 2개 또는 3개의 문자열로 나누어 제공합니다. +If your language provides only one plural form, then you will see only one phrase to translate. If three or more forms, Crowdin will provide you with the string divided into other two or three strings to translate. -예를 들어 +For example: ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/plurals/crowdin_scheme.png) -이러한 문자열을 번역하고 승인할 때는 세심한 주의를 기울여 주세요. 'Other' 필드의 의미를 모른다면 'Many' 필드에 있는 것과 동일한 형식을 붙여넣기만 하면 됩니다. 'Many' 및 'Other' 필드의 번역은 동일할 수 있습니다. +Please be attentive when translating these strings and approving them. If you have no idea what the "Other" field means, then just paste the same form as it is in the "Many" field. The translations of "Many" and "Other" fields can be the same. -### 4. 세로 막대 기호로 구분된 템플릿이 있는 문자열 {#4type} +### 4. Strings with templates separated by the vertical bar sign {#4type} -이는 `AdGuard Websites` 프로젝트에서 주로 사용되는 가장 복잡한 유형의 AdGuard 문자열입니다. +This is the most complicated type of AdGuard strings which is mostly used in the `AdGuard Websites` project. -문장 사이의 세로 막대 기호에 주의하세요. **%count%** 플레이스홀더에 주목하세요. 이렇게 하면 번역에서 복수형을 사용해야 하는 구문을 식별하는 데 도움이 됩니다. +Pay close attention to a vertical bar sign between the sentences and **%count%** placeholders in original phrases — this will help you identify phrases where translations require the use of plural forms. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/plurals/plurals_site.png) -이제 “`%count%대의 컴퓨터용 일반 라이선스 | %count%대의 컴퓨터용 일반 라이선스`”라는 문자열이 표시된다고 가정해 보겠습니다. +Now, let’s imagine — you are faced with such a string: `Standard license for %count% computer | Standard license for %count% computers`. -올바르게 번역하려면 무엇을 알아야 하나요? +What should you know to translate it correctly? -세로 막대 기호로 구분된 문장을 **'템플릿'**이라고 부릅시다. 실제로는 숫자가 다른 문구의 템플릿 역할을 하기 때문입니다. +Let's call the sentences which are divided by a vertical bar sign **"templates"**, because actually they serve as templates for phrases with different numbers. -다시 예시로 돌아와서 영어에는 두 가지 형식만 포함되어 있으므로 각각 두 개의 템플릿이 있어야 합니다. +Coming back to the example, as the English language includes only two forms, there should be two templates respectively: -`컴퓨터**%count%**대의 기기에서 사용 가능한 일반 라이선스 | 컴퓨터** %count%*대의 기기에서 사용 가능한 일반 라이선스` +`Standard license for *%count%* computer | Standard license for *%count%* computers` -**템플릿 1**은 *%count%*컴퓨터용 일반 라이선스입니다. +where **template 1** is Standard license for *%count%* computer, -**템플릿 2**은 *%count%*컴퓨터용 일반 라이선스입니다. +and **template 2** is Standard license for *%count%* computers -주의해야 할 또 다른 중요한 사항은 다음과 같습니다. **%count%** 플레이스홀더는 평소와 같이 정의하는 단어 앞에 위치합니다. 대신 **%count%** 대신 선택되는 템플릿에 따라 다른 숫자가 표시됩니다. +Another important thing you should pay your attention to is **%count%** placeholders that, as usual, take place before the words they define. Instead of **%count%** here will appear different numbers depending on which templates are being chosen. -예를 들어, 복수형이 3개인 다른 언어가 있는 상황에서는 그 사이에 세로 막대 기호 2개가 있는 템플릿 3개가 있어야 합니다. +In a situation with another language that has, let’s say, three plural forms, there should be three templates with two vertical bar signs between them. -예를 들어, 위에 언급된 문구를 슬로바키아어로 번역하면, [현지화 가이드](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) 규칙에 따라 세 가지 단어 형태가 있는데, 올바른 번역은 다음과 같습니다. +For example, when we translate the above mentioned phrase into Slovak, that according to the rule of [Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) has three word forms, the correct translation will look so: -`Štandartná licencia pre %count% počítač | Štandartná licencia pre %count% počítače | Štandartná licencia pre %count% počítačov` +`**Štandartná licencia pre *%count%* počítač | Štandartná licencia pre *%count%* počítače | Štandartná licencia pre *%count%* počítačov**` -![슬로바키아어](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/slovak.png) +![Slovak](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/slovak.png) -이 경우 슬로바키아어로 ‘počítač’(컴퓨터)라는 단어의 세 가지 형식이 포함된 세 가지 템플릿이 표시됩니다. +In this case, we see three templates which contain three forms of the word *"počítač"* (computer) in Slovak. -*형식 중 하나를 무시하고 슬로바키아어에 3개가 아닌 2개의 템플릿만 사용하면 시스템이 특정 숫자에 적합한 템플릿을 사용할 수 없어* 결과적으로 영어와 같이 문장에 문법 오류가 발생하게 됩니다: *컴퓨터 5대용 일반 라이선스입니다*. -> **단어 자체의 단어 형식이 적은 경우에도 항상 해당 언어의 단어 수만큼의 형식을 사용하세요.** +*If we ignore one of the forms and use only two templates for Slovak instead of three, the system won’t be able to take an appropriate template for certain numbers* and, as a result, we will have grammar mistakes in sentences, like in English: *Standard license for 5 computer*. +> **Always use as many forms as there are in your language, even when the word itself has fewer word forms.** -예를 들어, 세르비아어 단어 *'računar'*(컴퓨터)에는 두 가지 형식이 있습니다. 하지만 세르비아어에는 3가지 복수형이 있습니다. +For example, the Serbian word *'računar'* (computer) has only two forms. But there are 3 plural forms in Serbian. -![세르비아어](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/serbian.png) +![Serbian](https://cdn.adtidy.org/content/Kb/ad_blocker/miscellaneous/adguard_translations/serbian.png) -따라서 영어에서 세르비아어로 번역해야 합니다. +Thus, the translation from English into Serbian should be: -`Standardna licenca za %count% računar|Standardna licenca za %count% računara | Standardna licenca za %count% računara` +`**Standardna licenca za *%count%* računar | Standardna licenca za *%count%* računara | Standardna licenca za *%count%* računara**` -마지막 두 템플릿에는 차이가 없는 것은 분명하지만 규칙을 지키는 것이 매우 중요합니다: **템플릿의 수는 해당 언어의 복수형 수를 반영해야 합니다!**(일반적으로 복수형이 포함된 문자열의 경우). +Although it is obvious that the last two templates have no differences, it is very important to keep the rule: **The number of templates should reflect the number of plural forms of the respective language!**(typically for this type of strings with plurals). -### 간단한 요약 {#summury} +### Short summary {#summury} -AdGuard 프로젝트를 번역할 때는 복수형을 사용해야 하는 문구에 세심한 주의를 기울이세요. +When translating AdGuard projects pay your close attention to phrases which require the use of plural forms. -처음 세 가지 유형의 문자열은 어느 정도 수행하기 쉽지만 네 번째 유형은 더 많은 주의가 필요합니다. +While first three types of such strings are more or less easy to perform, the fourth type demands more vigilance. -다시 한 번 강조하지만, **세로 막대 기호** 및 **%count%** 자리 표시자를 발견하면 다음을 수행하세요. +And again: if you come across an original phrase with two important elements: **the vertical bar sign** and **%count%** placeholders, please do the following: -- 번역하는 언어의 복수형 규칙을 참조하세요. +- Refer to the plural rule of a language you translate into; -템플릿의 수는 언어에 포함된 복수형 수와 일치해야 하며, 일부 단어의 경우 그 자체의 형식이 더 적은 경우에도 마찬가지입니다. 복수형 2개 — 번역 템플릿 2개, 복수형 5개 — 템플릿 5개 등입니다. +The number of your templates should be consistent with the number of plural forms your language includes, even in cases some words have fewer forms themselves. Two plural forms — two templates in translations; five plural forms — five templates, etc. -- 템플릿은 원래 문자열로 표시되므로 템플릿 사이에 세로 막대 기호를 사용하는 것을 잊지 마세요. +- Do not forget to use a vertical bar sign between templates as it is represented in original strings; -- **%count%** 플레이스홀더를 번역, 입력 또는 삭제하지 마세요. +- Do not translate, fill in or delete **%count%** placeholders. -이러한 간단한 규칙을 따르면 AdGuard 개발자가 현지화 과정에서 불필요한 복황한 상황을 피할 수 있습니다. +By following these simple rules you will help AdGuard developers avoid a lot of unnecessary complications during the localization process. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 98906ea888f..4eed3126873 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -1,12 +1,12 @@ --- -title: AdGuard 번역 프로그램 +title: AdGuard translation program sidebar_position: 1 --- -AdGuard 번역에 대한 질문은 [translate@adguard.com](mailto:translate@adguard.com)으로 이메일을 보내거나 [Telegram 채팅](https://t.me/joinchat/UVYTLcHbr8JmOGIy)에 참여하여 문의할 수 있습니다. +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). -번역과 관련하여 AdGuard는 항상 자원봉사자들의 도움을 많이 받고 있습니다. +When it comes to translations, we at AdGuard always heavily rely on volunteers. -현재 저희는 [Crowdin 플랫폼](https://crowdin.com/)을 통해 제품 번역을 관리하고 있습니다. 이곳은 저희의 제품을 번역하여 AdGuard에 기여하고 싶은 모든 이들을 위한 곳입니다. +We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. -AdGuard 번역을 돕는 자원봉사자가 되고 싶다면 [번역가가 되는 방법](../become-translator) 및 [그들과 협력하는 방법](../rewards)에 대한 정보를 읽어보세요. +If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/rewards.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/rewards.md index b202b1ad65e..f6c52d896cb 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/rewards.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/rewards.md @@ -1,28 +1,28 @@ --- -title: 보상 시스템 +title: Reward system sidebar_position: 6 --- -정직하고 성실한 노력에는 보상이 주어져야 하므로, Crowdin에서 활동 중인 번역가는 무료 AdGuard 라이선스 키와 VPN 구독을 요청할 수 있습니다. +As any honest and well-performed effort should be rewarded, active translators on Crowdin can request a free AdGuard license key and a VPN subscription. -**1년 AdGuard 라이선스 키** 또는 **1년 AdGuard VPN 구독**을 요청하려면 각각 최소 **500단어**와 **2,500단어**를 번역해야 합니다. +To request a **one-year AdGuard license key** or a **one-year AdGuard VPN subscription**, you must translate at least **500** and **2,500** words respectively. -번역 진행 상황을 확인하려면 작업한 프로젝트를 열고 *Reports* 탭을 클릭한 다음 *My Contribution*를 선택하세요. 여러 프로젝트에서 번역한 단어 수를 합산하여 라이선스를 받을 수 있습니다. +To check your translation progress, open a project you have worked on, click the *Reports* tab and select *My Contribution*. You can sum up the number of words translated in different projects to get a license. -## 보상 시스템의 작동 방식은 다음과 같습니다. +## Here’s how our reward system works ```text -첫 1년 AdGuard 라이선스의 경우 500단어를 번역해야 합니다. -두 번째 라이선스의 경우 1,000단어, 즉 총 1,500단어가 필요합니다. -이후 모든 라이선스에는 라이선스당 1,500단어를 추가로 입력해야 합니다. +For the first one-year AdGuard license, you need to translate 500 words. +For the second license, you need 1,000 words, i.e. 1,500 words altogether. +All subsequent licenses require an additional 1,500 words per license. -AdGuard VPN을 처음 1년 구독하는 경우, 2,500개의 단어를 번역해야 합니다. -이후 모든 구독 또는 갱신에는 구독당 2,500단어가 추가로 필요합니다. +For the first one-year AdGuard VPN subscription, you need to translate 2,500 words. +All subsequent subscriptions or renewals require an additional 2,500 words per subscription. ``` -[translate@adguard.com](mailto:translate@adguard.com)으로 요청을 보내주시면 감사의 표시로 라이선스를 보내드립니다. +Just send us a request to [translate@adguard.com](mailto:translate@adguard.com) and you’ll get the license as a token of our gratitude. -또한 가장 활발하게 활동하는 번역가에게 향후 교정자 자격을 부여할 수 있으며, 그러한 의사를 표명하면 더 많은 좋은 콘텐츠를 제공할 수 있습니다. +Besides, the most active translators may receive proofreader status in the future, should they express such an intention, and that promises even more good stuff. -매년 AdGuard는 현역 교정자에게 AdGuard 로고가 새겨진 선물을 증정합니다. 교정자가 되고 싶다면 [translate@adguard.com](mailto:translate@adguard.com)으로 이메일을 보내주세요. +Every year we present gifts with the AdGuard logo to our active proofreaders. If you want to become one of them, please write to [translate@adguard.com](mailto:translate@adguard.com). diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 06dd985ba16..4c15594b389 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -1,35 +1,35 @@ --- -title: Crowdin 파일 번역의 우선순위를 정하는 방법 +title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -Crowdin에는 다음과 같이 5개의 주요 AdGuard 프로젝트가 있습니다. [AdGuard Application](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases)입니다. +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). -*AdGuard Applications* 프로젝트의 어떤 파일 또는 제품부터 시작해야 하는지에 대한 명확한 가이드라인이 없습니다. 원하는 제품을 선택하시면 됩니다. +We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. -몇 가지 언급하고 싶은 것이 있습니다. +There are just a couple of things we want to mention: -- 이 앱은 Crowdin에서 모든 번역이 완료된 언어를 사용하는 사용자에게만 제공됩니다. -- 제품 자체의 번역이 없으면 설명이 필요하지 않으므로 앱 스토어용 설명은 두 번째로 번역하는 것이 좋습니다. +- You can see the app only in those languages for which all translations are completed in Crowdin; +- We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. -*AdGuard Websites* 프로젝트는 상황이 다릅니다. 전체 번역 세트를 사용할 수 없더라도 사이트에 언어를 추가할 수 있습니다. 그러나 이는 이미 번역된 파일에 따라 다릅니다. 따라서 아래에 나열된 가장 중요한 파일부터 시작하는 것이 좋습니다. +The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: -[AdGuard 광고 차단기 웹사이트](https://crowdin.com/project/adguard-websites/en#/adguard.com) +[AdGuard Ad Blocker website](https://crowdin.com/project/adguard-websites/en#/adguard.com) - `critical.resx` - `auth.resx` - `welcome.resx` -[AdGuard VPN 웹사이트](https://crowdin.com/project/adguard-websites/en#/adguard-vpn.com) +[AdGuard VPN website](https://crowdin.com/project/adguard-websites/en#/adguard-vpn.com) - `critical.resx` - `auth.resx` -[AdGuard DNS 웹사이트](https://crowdin.com/project/adguard-websites/en#/adguard-dns.com) +[AdGuard DNS website](https://crowdin.com/project/adguard-websites/en#/adguard-dns.com) - `critical.resx` - `auth.resx` -이러한 파일에 새 문자열을 추가하고 기존 문자열을 업데이트하려면 프로젝트 번역가와 교정자의 특별한 주의가 필요합니다. +Adding new strings as well as updating existing ones in these files requires special attention from the project translators and proofreaders. -웹사이트 외에도 AdGuard 웹사이트 프로젝트에는 [트랜잭션 이메일](https://crowdin.com/project/adguard-websites/en#/emails) 번역을 위한 파일이 있습니다. 이 파일에 새로 추가된 문자열도 번역 우선 순위가 높습니다. +In addition to websites, there is a file for translating [transactional emails](https://crowdin.com/project/adguard-websites/en#/emails) in the AdGuard Websites project. Newly added strings in this file also have a high translation priority. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 86ba0e853a1..b0978dc0171 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: 지식 창고 업데이트 +title: Updating the Knowledge base sidebar_position: 2 --- -이 기술 자료의 목표는 모든 종류의 AdGuard 광고 차단기 관련 주제에 대한 최신 정보를 모든 사용자에게 제공하는 것입니다. 하지만 상황은 끊임없이 변하고, 때로는 기사가 더 이상 현재 상황을 반영하지 못할 때도 있습니다. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. -그래서 우리가 모든 지식 창고 콘텐츠를 [GitHub](https://github.com/AdguardTeam/KnowledgeBase)에 배치했습니다. 이제 누구나 기존 및 새 기사에 대한 편집 및 번역을 제안할 수 있습니다. +This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. -## 변경 사항을 제안하거나 새 문서를 작성하는 방법 {#suggest-change} +## How to suggest a change or write a new article {#suggest-change} -위에서 언급한 GitHub의 기능을 사용하여 현재 기사에 대한 변경 내용을 제안하고 기술 자료에 새 기사를 추가할 수 있습니다. 플랫폼에 익숙하지 않은 경우, [GitHub 문서](https://docs.github.com/en)를 참조하세요. +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -시작할 준비가 되면 [KnowledgeBase 레포지터리](https://github.com/AdguardTeam/KnowledgeBase)에서 작업하세요. 기술 창고의 모든 글은 `Markdown` 마크업 언어로 작성되었습니다. 기사를 편집하거나 작성할 때 이것을 명심하십시오. Markdown 구문에 대해 자세히 알아보려면 [이 링크](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)를 클릭하세요. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -지식 창고 웹사이트는 최신 웹사이트 생성기인 Docusaurus 2를 사용하여 제작되었습니다. 텍스트를 변경하거나 추가할 때 모든 기사가 플랫폼의 원칙을 준수해야 한다는 점을 고려하십시오. [Docusaurus 가이드](https://docusaurus.io/docs/category/guides)에서 자세한 내용을 확인할 수 있습니다. +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -이 지식 창고를 컴퓨터에 배포하여 제안한 변경 사항을 미리 볼 수 있습니다. 이 작업을 수행하는 방법에 대한 자세한 지침은 이 지식창고의 GitHub 페이지에 있는 [README 파일](https://github.com/AdguardTeam/KnowledgeBase#readme)에서 확인할 수 있습니다. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. -## 문서 번역하기 {#translate-adguard} +## Translating articles {#translate-adguard} -지식 창고의 기존 문서 번역은 [Crowdin 플랫폼](https://crowdin.com/profile/adguard)에서 수행됩니다. 번역과 Crowdin 사용 방법에 대한 자세한 내용은 [AdGuard 광고 차단기의 지식 창고 문서](../translate/guidelines)에서 확인할 수 있습니다. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -AdGuard 지식 창고에서 기사를 번역하는 동안 번역에 특별한 주의를 기울여야 하는 복수형이 포함된 문자열을 보게 될 것입니다. [별도의 기사](../translate/plural-forms)에서 복수형 문자열을 번역할 때 발생할 수 있는 어려움에 대해 자세히 설명하고 Crowdin 플랫폼에서 작업하는 방법에 대한 광범위한 지침을 제공했습니다. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. -## 미해결 이슈 작업하기 +## Working on open issues -지식 창고 업데이트와 관련된 [열린 태스크](https://github.com/AdguardTeam/KnowledgeBase/issues)가 있을 수 있습니다. 이 지식 창고에 대한 다른 변경 사항을 제안하는 것과 [동일한 방식](#suggest-change)으로 이러한 태스크를 해결하는 데 도움을 줄 수 있습니다. 원하는 태스크를 선택하고, 작업을 시작하세요. 질문이 있는 경우, 해당 태스크에 대한 댓글에서 바로 질문할 수 있습니다. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/writing-about-adguard.md b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/writing-about-adguard.md index 9596e59432f..3443b61ccc3 100644 --- a/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/writing-about-adguard.md +++ b/i18n/ko/docusaurus-plugin-content-docs/current/miscellaneous/contribute/writing-about-adguard.md @@ -1,10 +1,10 @@ --- -title: AdGuard에 대한 글쓰기 +title: Writing about AdGuard sidebar_position: 3 --- -AdGuard가 마음에 들고 소셜 미디어나 개인 블로그, 웹사이트에서 관련된 생각을 널리 알리고 공유하고 싶다면 이 문서에 흥미가 있을지도 모릅니다. +If you like AdGuard and want to spread the word and share your thoughts about it on social media or on a personal blog or website, this article may interest you. -당신의 경험을 공유한 후, [pr@adguard.com](mailto:pr@adguard.com)으로 게시물 주소를 포함한 이메일을 보내주세요. 가장 잘 작성된 리뷰의 작성자들은 무료 AdGuard 라이선스 키를 받게 됩니다. 웹사이트의 방문자 수가 적든 많든 상관 없이, 우리는 모든 노력을 소중히 여깁니다. 리뷰는 300자에서 500자 내외로 작성해야 한다는 것을 기억해 주세요. +After sharing your experience, email [pr@adguard.com](mailto:pr@adguard.com) and include a link to your post. The authors of the most well-written reviews will receive a free AdGuard license key. It doesn't matter if your website's audience is small or large; we value every effort. Please note that your review should be around 300 to 500 words. -AdGuard에 대한 동영상을 제작하거나, 다른 색다른 무언가를 계획하고 있다면 오해의 소지가 없도록 우리에게 미리 알려주시기 바랍니다. AdGuard 로고, 배너 및 기타 시각적 요소를 사용할 계획일 경우에도 마찬가지입니다. 연락할 수 있는 이메일 주소는 동일합니다: [pr@adguard.com](mailto:pr@adguard.com). +If you are planning to make a video about AdGuard or do anything else offbeat, please let us know in advance to avoid any possible misunderstandings. The same applies if your plan includes the use of the AdGuard logo, banners, or other visual elements. The contact email address remains the same: [pr@adguard.com](mailto:pr@adguard.com). diff --git a/i18n/ko/docusaurus-theme-classic/footer.json b/i18n/ko/docusaurus-theme-classic/footer.json index 4d8e959b53a..c0315425c38 100644 --- a/i18n/ko/docusaurus-theme-classic/footer.json +++ b/i18n/ko/docusaurus-theme-classic/footer.json @@ -44,7 +44,7 @@ "description": "The label of footer link with label=adguard_for_android linking to https://adguard.com/adguard-android/overview.html" }, "link.item.label.adguard_for_mac": { - "message": "Mac용 AdGuard", + "message": "AdGuard for Mac", "description": "The label of footer link with label=adguard_for_mac linking to https://adguard.com/adguard-mac/overview.html" }, "link.item.label.adguard_for_ios": { diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/nl/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/nl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/nl/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/nl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/intro.md b/i18n/nl/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/nl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/no/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/no/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/no/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/no/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/no/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/no/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/no/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/no/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/no/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/no/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/no/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/no/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/intro.md b/i18n/no/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/no/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/pl/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/pl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/pl/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/pl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/intro.md b/i18n/pl/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/pl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md index fd7f1ed7b2f..77d2104e8e3 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/availability.md @@ -9,18 +9,18 @@ Este artigo é sobre a extensão de navegador AdGuard, que protege apenas o seu ::: -A extensão de navegador [AdGuard](https://adguard.com/adguard-browser-extension/overview.html) é uma extensão gratuita que funciona em cinco navegadores populares: Chrome, Firefox, Edge, Opera e Vivaldi. Você pode encontrá-lo facilmente na loja online do seu navegador ou em nosso site oficial. +[AdGuard Browser Extension](https://adguard.com/adguard-browser-extension/overview.html) is a free extension that works in five popular browsers: Chrome, Firefox, Edge, Opera, and Yandex Browser. Você pode encontrá-lo facilmente na loja online do seu navegador ou em nosso site oficial. -![Extensão de navegador AdGuard para Chrome](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) +![AdGuard Browser Extension for Chrome \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_overview.png) -Extensões de navegador incluem funções básicas de bloqueio de anúncios, mas não podem ser comparadas com programas completos para desktop, como [AdGuard para Windows](/adguard-for-windows/features/home-screen) e [AdGuard para Mac](/adguard-for-mac/features/main). +Browser extensions include basic ad-blocking features but cannot be compared with full-featured desktop programs, such as [AdGuard for Windows](/adguard-for-windows/features/home-screen) and [AdGuard for Mac](/adguard-for-mac/features/main). -![Disponível na maioria dos navegadores](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) +![Available for most popular browsers \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_availability.png) :::note -Temos uma extensão independente para Safari. Desde o lançamento do [Safari 13](https://adguard.com/en/blog/adguard-safari-1-5.html), várias das extensões bloqueadoras de anúncios encontraram problemas e pararam de funcionar. Nós tivemos que desenvolver [uma extensão separada para Safari](/adguard-for-safari/features/general) que tem algumas diferenças em relação à extensão descrita neste artigo. +Temos uma extensão independente para Safari. Since the release of [Safari 13](https://adguard.com/en/blog/adguard-safari-1-5.html), most of the ad-blocking extensions have experienced huge issues and many of them stopped functioning. We had to develop a [separate extension for Safari](/adguard-for-safari/features/general) that has some differences in comparison with the extension described in this article. ::: -**Não esqueça que a funcionalidade de cada extensão é estritamente limitada pelas capacidades do navegador.** Então, se você deseja uma proteção completa, considere instalar a versão de desktop para seu computador. Existe um [motivo](adguard-browser-extension/comparison-standalone) para isso. +**Do not forget that the functionality of each extension is strictly limited by the browser’s capabilities.** So if you want to get full-fledged protection, consider installing a standalone program for your computer. There's [a reason why](adguard-browser-extension/comparison-standalone). diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 362872f0102..e791aa6fa5f 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -1,5 +1,5 @@ --- -title: Comparação com apps para desktop +title: Comparison to standalone apps sidebar_position: 7 --- @@ -17,10 +17,10 @@ A segunda diferença é que as possibilidades dos bloqueadores de anúncios base Embora a extensão do navegador AdGuard seja gratuita, fácil de instalar e tenha filtros para bloquear anúncios e combater ameaças online, os aplicativos completos são mais poderosos e possuem vários recursos avançados. Veja todas as diferenças na tabela comparativa abaixo. -![Extensão vs. App](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) +![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — dentro das restrições do navegador e somente no navegador onde está instalado; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — a extensão não consegue detectar solicitações de outras extensões. Se uma extensão maliciosa ou de rastreamento enviar uma solicitação ao seu servidor para mostrar anúncios ou rastrear sua atividade, a extensão de navegador AdGuard não poderá bloquear essa solicitação; +`2` – the extension is unable to detect requests from other extensions. Se uma extensão maliciosa ou de rastreamento enviar uma solicitação ao seu servidor para mostrar anúncios ou rastrear sua atividade, a extensão de navegador AdGuard não poderá bloquear essa solicitação; -`3` — nem todos os tipos de anúncios e ameaças podem ser bloqueados por extensões de navegador devido a certas limitações do navegador. Alguns elementos podem chegar à página e retardar o processo de carregamento. Além disso, ao contrário dos bloqueadores de anúncios de extensões, o aplicativo AdGuard bloqueia anúncios antes que eles sejam carregados no navegador. Isso economiza tráfego e acelera o carregamento da página. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Alguns elementos podem chegar à página e retardar o processo de carregamento. Além disso, ao contrário dos bloqueadores de anúncios de extensões, o aplicativo AdGuard bloqueia anúncios antes que eles sejam carregados no navegador. Isso economiza tráfego e acelera o carregamento da página. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md index 40d786742b5..fae5c46c500 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md @@ -1,5 +1,5 @@ --- -title: Compatibilidade com o aplicativo independente +title: Compatibility with the standalone app sidebar_position: 4 --- @@ -9,16 +9,16 @@ Este artigo é sobre a extensão de navegador AdGuard, que protege apenas o seu ::: -Embora a extensão de navegador AdGuard possa bloquear anúncios em navegadores, os [programas autônomos do AdGuard](/adguard-browser-extension/comparison-standalone) filtram todo o tráfego no seu dispositivo, incluindo navegadores e aplicativos. +While AdGuard Browser Extension can block ads in browsers, [AdGuard standalone programs](/adguard-browser-extension/comparison-standalone) filter all the traffic on your device, including from browsers and apps. -Se você decidir instalar a extensão e o programa autônomo no seu PC, poderá encontrar alguns problemas de compatibilidade. O problema é que, em alguns casos, o aplicativo e a extensão podem interferir um no outro. Alguns sites não serão mais protegidos pelo programa de desktop e serão protegidos apenas pela extensão, que tem menos opções. Além disso, a filtragem pode funcionar incorretamente em alguns sites. Portanto, não recomendamos usar a extensão junto com o aplicativo. +If you decide to install both the extension and the standalone program on your PC, you may encounter some compatibility issues. The problem is that in some cases the application and the extension may interfere with each other. Some websites will no longer be protected by the desktop program and will only be protected by the extension, which has fewer options. Also, filtering may work incorrectly for some websites. Therefore, we don't recommend using the extension together with the application. -Se você tiver a versão desktop do AdGuard instalada em seu PC, é melhor usar o Assistente do Navegador AdGuard em vez da extensão. +If you have the desktop version of AdGuard installed on your PC, it is better to use AdGuard Browser Assistant instead of the extension. ## Assistente de navegador AdGuard -![Assistente de navegador AdGuard \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) +![AdGuard Browser Assistant \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) -O Assistente de navegador AdGuard é uma extensão de navegador que funciona e se sente exatamente como a Extensão do AdGuard para navegador, mas é muito mais leve e não interfere nos aplicativos de desktop. Você pode [ler mais sobre o Assistente do navegador para Windows](/adguard-for-windows/browser-assistant) ou [Mac](/adguard-for-mac/features/browser-assistant), ou [baixá-lo em nosso site](https://adguard.com/adguard-assistant/overview.html). +AdGuard Browser Assistant is a browser extension that works and feels just like AdGuard Browser Extension, but it's much lighter and doesn't interfere with the desktop apps. You can [read more about Browser Assistant for Windows](/adguard-for-windows/browser-assistant) or [Mac](/adguard-for-mac/features/browser-assistant), or [download it from our website](https://adguard.com/adguard-assistant/overview.html). -O Assistente de Navegador AdGuard está disponível em todos os principais navegadores. +AdGuard Browser Assistant is available in all major browsers. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index de77fd1d08a..26d3fbdd178 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ Todos os filtros são agrupados de acordo com sua função. Por exemplo, existem ## Filtros personalizados -Embora os recursos de outros grupos de filtros sejam mais ou menos autoexplicativos, há um grupo chamado _Personalizado_ que pode levantar questões adicionais. +Embora os recursos de outros grupos de filtros sejam mais ou menos previsíveis, existe um grupo chamado _Personalizado_ que pode gerar dúvidas. ![Filtros personalizados \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index bedca05c006..66d6f3efcbf 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ A página principal da extensão pode ser acessada clicando no ícone da extens Na página principal, você pode ocultar qualquer elemento em qualquer página manualmente (uma regra correspondente será adicionada às _Regras do usuário_), abrir o _Registro de filtragem_ para visualizar as informações completas sobre o tráfego do seu navegador e bloquear solicitações em movimento ou consultar o relatório de segurança de um site. Além disso, você pode enviar uma reclamação sobre qualquer site (por exemplo, se houver anúncios perdidos na página, nossos engenheiros de filtros analisarão o relatório e corrigirão o problema) e ver as estatísticas sobre as regras de bloqueio aplicadas. -Todas as solicitações web feitas pelo navegador são exibidas no _Registro de filtragem_, junto com informações detalhadas sobre cada solicitação. O _Registro de filtragem_ facilita, por exemplo, o monitoramento de solicitações bloqueadas pela extensão de navegador AdGuard. Além disso, isso permite bloquear qualquer solicitação ou adicionar uma solicitação previamente bloqueada à lista de permissões em dois cliques. O _Registro de filtragem_ também oferece uma ampla variedade de opções para classificar solicitações da web, o que pode ser útil ao criar suas próprias regras de filtragem. Você pode abrir o _Registro de filtragem_ selecionando o item correspondente no menu principal ou na página de configurações (na guia _Configurações adicionais_). +Todas as solicitações web feitas pelo navegador são exibidas no _Registro de filtragem_, junto com informações detalhadas sobre cada solicitação. O _Registro de filtragem_ facilita, por exemplo, o monitoramento de solicitações bloqueadas pela extensão de navegador AdGuard. Além disso, isso permite bloquear qualquer solicitação ou adicionar uma solicitação previamente bloqueada à lista de permissões em dois cliques. O _Registro de filtragem_ também oferece uma ampla variedade de opções para classificar solicitações da web, o que pode ser útil ao criar suas próprias regras de filtragem. Você pode abrir o _Registro de filtragem_ selecionando o item correspondente no menu principal ou na página de configurações (na guia "Configurações adicionais"). Ao clicar nos ícones no canto superior direito do menu principal da extensão, você pode abrir as configurações da extensão ou pausar a proteção. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 48204e75011..8389e7a9e57 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -19,7 +19,7 @@ Na aba _Geral_, você pode permitir anúncios de pesquisa e a [autopromoção de Além disso, aqui você pode ativar a [_Proteção contra phishing e malware_](/general/browsing-security). -Você pode salvar suas configurações clicando no botão _Exportar configurações_. As configurações serão salvas como um arquivo .json. Para importar as configurações salvas anteriormente, use a função _Importar configurações_. Você pode até usá-lo para alternar rapidamente entre diferentes perfis de configurações ou até mesmo para transferir configurações entre diferentes navegadores. +Você pode salvar suas configurações clicando no botão _Exportar configurações_. As configurações serão salvas como um arquivo .json. Para carregar as configurações salvas anteriormente, use a função _Importar configurações_. Você pode até usá-lo para alternar rapidamente entre diferentes perfis de configurações ou até mesmo para transferir configurações entre diferentes navegadores. ## Configurações adicionais {#misc} diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md index 39dfde438ec..920474ffe5d 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/installation.md @@ -71,4 +71,4 @@ Na janela de diálogo aberta, clique em *Adicionar extensão* para instalar a ex ## Como instalar a extensão de navegador AdGuard para Safari -O AdGuard para Safari não é uma extensão de navegador comum. Pode ler mais sobre este assunto [neste artigo](/adguard-for-safari/features/general). Ou você pode [baixar o ficheiro de instalação](https://agrd.io/safari_release) diretamente desta página. +O AdGuard para Safari não é uma extensão de navegador comum. You can read more about it in a [dedicated article](/adguard-for-safari/features/general). Ou você pode [baixar o ficheiro de instalação](https://agrd.io/safari_release) diretamente desta página. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index 00ee824378e..71439eadb17 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Páginas protegidas pelo navegador -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md index 673605a0b98..748e7dd860f 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md @@ -53,11 +53,11 @@ sidebar_position: 1 :::note -O AdGuard tem o compromisso de proteger sua privacidade. Seguimos rigorosamente nossa [Política de Privacidade](https://adguard.com/privacy/browser-extension.html) e não coletamos nenhuma informação privada sobre os usuários. Antes de enviar seus registros para a equipe de suporte, revise o arquivo, pois ele pode conter informações adicionais que você não deseja compartilhar. Se contiver tais informações pessoais, recomendamos que você as exclua primeiro. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/browser-extension.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -Agora que você coletou os logs, siga estas etapas para enviá-los à nossa equipe de desenvolvimento: +Now that you have collected the logs, please follow these steps to submit them to our development team: -1. Relate o bug no [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). -2. Envie o arquivo com os registros e o tempo de reprodução para `devteam@adguard.com` e anexe um link para seu issue no GitHub. Você também pode fazer upload do arquivo para o Google Drive e adicionar o link a ele em vez de anexar o arquivo. +1. Report the bug on [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). +2. Send your archive with logs and playback time to `devteam@adguard.com` and add a link to your GitHub issue. You can also upload the archive to Google Drive and add the link to it instead of attaching the file. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 6adc04f6053..08d187868ec 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ No menu de contexto, você também pode acessar as estatísticas do aplicativo. ### Aplicativos “sem problemas” e “problemáticos” -Most apps work correctly when filtered. Para esses aplicativos, o tráfego é roteado pelo AdGuard e filtrado por padrão. +A maioria dos aplicativos funciona corretamente quando a filtragem está ativada. Para esses aplicativos, o tráfego é roteado pelo AdGuard e filtrado por padrão. Alguns aplicativos, como Download Manager, rádio, aplicativos de sistema com UID 1000 e 1001 (por exemplo, Google Play Services), são “problemáticos” e podem funcionar incorretamente quando roteados pelo AdGuard. É por isso que você poderá ver o seguinte aviso ao tentar rotear ou filtrar todos os aplicativos: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 66233a50b34..1833e0604a1 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ O módulo de proteção DNS pode ser acessado tocando na guia _Proteção_ (segu :::tip -A proteção DNS funciona de maneira diferente do bloqueio normal de anúncios e rastreadores. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +A proteção DNS funciona de maneira diferente do bloqueio normal de anúncios e rastreadores. [Aprenda mais sobre o assunto e sobre como ela funciona em um artigo dedicado](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 93263cc5b7d..6f76ffb2e95 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ Para excluir uma regra ou aplicativo de _Regras personalizadas_, deslize-o para ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index 84175d6b460..4489c04ea9d 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Aqui estão os recursos ativos dos níveis pré-configurados: k. _Remover cabeçalho X-Client-Data_. Este recurso impede que o Google Chrome envie informações sobre sua versão e modificações para domínios do Google (incluindo DoubleClick e Google Analytics) -Você pode ajustar configurações individuais em _Proteção contra rastreamento_ e criar uma configuração personalizada. Cada configuração possui uma descrição que o ajudará a entender sua função. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +Você pode ajustar configurações individuais em _Proteção contra rastreamento_ e criar uma configuração personalizada. Cada configuração possui uma descrição que o ajudará a entender sua função. [Saiba mais sobre o que várias configurações de _Proteção contra rastreamento_ fazem](/general/stealth-mode) e aborde-as com cautela, pois algumas podem interferir na funcionalidade de sites e extensões de navegador. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 4da63e79a2b..68fb92ccc1f 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ Este artigo aborda o AdGuard para Android, um bloqueador de anúncios multifunci Devido às medidas de segurança do sistema operacional Android, alguns recursos do AdGuard estão disponíveis apenas em dispositivos com acesso root. Aqui está a lista deles: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **A filtragem HTTPS na maioria dos aplicativos** requer [instalar um certificado CA no armazenamento do sistema](/adguard-for-android/features/settings#security-certificates), já que a maioria dos aplicativos não confia em certificados no armazenamento do usuário. A instalação de um certificado no armazenamento do sistema só é possível em dispositivos com acesso root - O [**modo de roteamento proxy automático**](/adguard-for-android/features/settings#routing-mode) requer acesso root devido às restrições do Android na filtragem de tráfego em todo o sistema - O [**modo de roteamento proxy manual**](/adguard-for-android/features/settings#routing-mode) requer acesso root no Android 10 e superior, pois não é mais possível determinar o nome do aplicativo associado a um conexão filtrada pelo AdGuard diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index cdb521668af..7f17898abb5 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -27,7 +27,7 @@ _Automação_ permite que você gerencie o AdGuard por meio de aplicativos de ta _Watchdog_ ajuda a proteger o AdGuard contra desativação do sistema ([leia mais sobre o modo de economia de bateria do Android](/adguard-for-android/solving-problems/background-work/)). O valor inserido será o intervalo em segundos entre as verificações de watchdog. -_Nível de registro_ define quais dados sobre a operação do aplicativo devem ser registrados. Por padrão, o aplicativo coleta dados sobre seus próprios eventos. O nível _Debug_ registra mais eventos. Ative-o se solicitado pela equipe do AdGuard para ajudá-los a entender melhor o problema. [Read more about collecting and sending logs](/adguard-for-android/solving-problems/log/) +_Nível de registro_ define quais dados sobre a operação do aplicativo devem ser registrados. Por padrão, o aplicativo coleta dados sobre seus próprios eventos. O nível _Debug_ registra mais eventos. Ative-o se solicitado pela equipe do AdGuard para ajudá-los a entender melhor o problema. [Leia mais sobre como coletar e enviar registros](/adguard-for-android/solving-problems/log/) ![Avançado \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) @@ -59,7 +59,7 @@ Se você ativar muitos filtros, alguns sites poderão funcionar incorretamente. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. Para instalar userscripts, você precisa de um gerenciador de userscript especial. O AdGuard tem essa funcionalidade e permite que você adicione scripts de usuário por URL ou a partir de um arquivo. +Userscripts são miniprogramas escritos em JavaScript que ampliam a funcionalidade de um ou mais sites. Para instalar userscripts, você precisa de um gerenciador de userscript especial. O AdGuard tem essa funcionalidade e permite que você adicione scripts de usuário por URL ou a partir de um arquivo. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ Nesta seção você pode encontrar informações sobre sua licença e gerenciá- - Compre uma licença do AdGuard para ativar [os recursos da versão completa](/adguard-for-android/features/free-vs-full) - Faça login em sua conta AdGuard ou insira a chave de licença para ativar sua licença - Inscreva-se para ativar seu período de teste de 7 dias, caso ainda não o tenha usado -- Refresh the license status from the three-dots menu (⋮) +- Atualize o status da licença no menu de três pontos (:) - Abra a conta AdGuard para gerenciar sua licença lá - Redefina sua licença. Por exemplo, se você atingiu o limite de dispositivos para esta licença e deseja aplicar outra diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index 9fdaa18280d..b86c96be964 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Pronto! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 492ad68039e..ccd419f6e97 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 0fda955d4ab..dc3caa1d4b4 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md index a3c9025edff..d19cba0e27e 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/firefox-certificates.md @@ -1,11 +1,11 @@ --- -title: Instalação manual do certificado de segurança no navegador Firefox +title: Manual installation of the security certificate into the Firefox browser sidebar_position: 11 --- :::info -Este artigo é sobre o AdGuard para Android, um bloqueador de anúncios multifuncional que protege seu dispositivo a nível de sistema. Veja como funciona ao [baixar o AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Veja como funciona ao [baixar o AdGuard](https://agrd.io/download-kb-adblock) ::: @@ -43,12 +43,12 @@ This method will only work on **rooted** devices. ::: -1. [Instale e configure](https://www.xda-developers.com/install-adb-windows-macos-linux/) o ADB; Na plataforma Windows, os usuários da **Samsung** talvez precisem instalar [esse utilitário](https://developer.samsung.com/mobile/android-usb-driver.html). +1. [Install and configure](https://www.xda-developers.com/install-adb-windows-macos-linux/) ADB; On the Windows platform, **Samsung** owners may need to install [this utility](https://developer.samsung.com/mobile/android-usb-driver.html). -1. Ative o **modo de desenvolvedor** e ative a **depuração USB**: +1. Activate the **developer mode** and enable **USB debugging**: - - Abra as **Configurações** em seu telefone; - - Vá para a seção **Sistema** (último item no menu de configurações). In this section, find the sub-item **About phone**; + - Open the **Settings** app on your phone; + - Go to **System** section (last item in the settings menu). In this section, find the sub-item **About phone**; - Tap the **Build number** line 7 times. After that, you will receive a notification that **You are now a developer** (If necessary, enter an unlock code for the device); - Open **System Settings** → **Developer Options** → Scroll down and enable **USB debugging** → Confirm debugging is enabled in the window **Allow USB debugging** after reading the warning carefully. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index 7ef50af4f8b..979912e211d 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index e0e9195ff52..32812cb7382 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index df96f2b9157..22361cd0812 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -15,17 +15,17 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. +Neste artigo, vamos guiá-lo pelo processo de coleta de logs de depuração, uma etapa de solução de problemas essencial para solucionar problemas complexos que podem surgir. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. :::note -O AdGuard tem o compromisso de proteger sua privacidade. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Antes de enviar seus registros para a equipe de suporte, revise o arquivo, pois ele pode conter informações adicionais que você não deseja compartilhar. Se contiver tais informações pessoais, recomendamos que você as exclua primeiro. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index 7b2d53b8130..567e511e967 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -19,7 +19,7 @@ Sometimes a regular log may not be sufficient to identify the origin of the prob :::note -O AdGuard tem o compromisso de proteger sua privacidade. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Antes de enviar seus registros para a equipe de suporte, revise o arquivo, pois ele pode conter informações adicionais que você não deseja compartilhar. Se contiver tais informações pessoais, recomendamos que você as exclua primeiro. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 81f69768ff6..2a60b7b572f 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Cada conexão de Internet criptografada tem uma parte não criptografada. Estamos falando do primeiro pacote, que contém o nome do servidor ao qual você está se conectando. A tecnologia Encrypted ClientHello deve resolver esse problema e criptografar esta última parte de informação não criptografada. To benefit from it, enable the *Encrypted Client Hello* option. Ela utiliza um proxy DNS local para procurar a configuração ECH para o domínio. If it is found, Client Hello packet will be encrypted. +Cada conexão de Internet criptografada tem uma parte não criptografada. Estamos falando do primeiro pacote, que contém o nome do servidor ao qual você está se conectando. A tecnologia Encrypted ClientHello deve resolver esse problema e criptografar esta última parte de informação não criptografada. To benefit from it, enable the *Encrypted Client Hello* option. Ela utiliza um proxy DNS local para procurar a configuração ECH para o domínio. Se encontrado, o pacote ClientHello será criptografado. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index ebee9cd8390..beedc325eba 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md index 5ca73a44695..a6528a29249 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md @@ -1,5 +1,5 @@ --- -title: Problemas causados por múltiplos perfis de usuário +title: Problems caused by multiple user profiles sidebar_position: 10 --- @@ -11,13 +11,13 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro In this article you will find the methods on how to solve problems with AdGuard when you set up *multiple accounts* or *Restricted Profiles* on your Android devices. -## Problemas causados por múltiplos perfis de usuário +## Problems caused by multiple user profiles -No Android 9 e versões posteriores, se o AdGuard estiver instalado em mais de um perfil de usuário no seu dispositivo, você poderá encontrar problemas ao desinstalar o aplicativo. Ao desinstalar o AdGuard de um perfil de usuário, o aplicativo ainda aparecerá na lista de aplicativos, mas você não poderá desinstalá-lo ou reinstalá-lo. This happens because AdGuard is installed for a different user profile on the device. +On Android 9 and later, if AdGuard is installed for more than one user profile on your device, you may encounter problems when uninstalling the app. When you uninstall AdGuard from one user profile, the app will still appear on the app list, but you won't be able to uninstall or reinstall it. This happens because AdGuard is installed for a different user profile on the device. If you try to reinstall AdGuard after an unsuccessful removal attempt, you will see the error message “You can't install the app on your device”. -Para resolver esse problema, você precisa desinstalar o aplicativo para todos os usuários: vá para Configurações → Todos os aplicativos → AdGuard. Tap the three-dot menu in the top right corner and select *Uninstall for all users*. +To solve this problem, you need to uninstall the application for all users: go to Settings → All apps → AdGuard. Tap the three-dot menu in the top right corner and select *Uninstall for all users*. ![Uninstall *mobile border](https://cdn.adtidy.org/blog/new/tu49hmultiple_users.png) @@ -37,10 +37,10 @@ This approach is available starting from **AdGuard v3.5 nightly 6**. If you're u ::: -1. Ative o **modo de desenvolvedor** e ative a **depuração USB**: +1. Activate the **developer mode** and enable **USB debugging**: - Open the **Settings** app phone; - - Vá para a seção **Sistema** (último item no menu de configurações). In this section, find the sub-item **About phone**; + - Go to **System** section (last item in the settings menu). In this section, find the sub-item **About phone**; - Tap the **Build number** line 7 times. After that, you will receive a notification that **You are now a developer** (If necessary, enter an unlock code for the device); - Open **System Settings** → **Developer Options** → Scroll down and enable **USB debugging** → Confirm debugging is enabled in the window **Allow USB debugging** after reading the warning carefully. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index e5b4dc21c43..2f707b24808 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 4d228b9a5ff..9e859cce014 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 00edfef1a80..00000000000 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Versão gratuita vs. versão completa -sidebar_position: 9 ---- - -:::info - -Este artigo é sobre o AdGuard para iOS, um bloqueador de anúncios multifuncional que protege seu dispositivo no nível do sistema. Para ver como funciona, [baixe o aplicativo AdGuard](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 349dc3a2b16..14262545473 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -13,15 +13,15 @@ Este artigo aborda o AdGuard para iOS, um bloqueador de anúncios multifuncional ### iPhone -Requer iOS 13 ou superior. +Requires iOS 13 or later. ### iPad -Requer iPadOS 13 ou superior. +Requires iPadOS 13 or later. ### iPod touch -Requer iOS 13 ou superior. +Requires iOS 13 or later. ## Instalação do AdGuard para iOS @@ -29,7 +29,7 @@ AdGuard para iOS é um aplicativo apresentado na App Store. Para instalá-lo em ![Na tela principal da App Store, toque em Pesquisar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Digite *adguard* na barra de pesquisa e toque na string *AdGuard* que estará entre os resultados da pesquisa. +Digite *AdGuard* na barra de pesquisa e toque na string *AdGuard* que estará entre os resultados da pesquisa. ![Digite "AdGuard" na barra de pesquisa *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ O AdGuard Pro é uma versão paga do AdGuard para iOS, oferecendo um conjunto ex ![Na tela principal da App Store, toque em Pesquisar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Digite *adguard* no formulário de pesquisa e toque na sequência *AdGuard Pro — adblock* que será exibida entre os resultados da pesquisa. +Digite *AdGuard* na barra de pesquisa e toque na string *AdGuard pro - Bloqueador de anúncios* que será mostrada entre os resultados da pesquisa. ![Digite "AdGuard" na barra de pesquisa *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -Na página aberta da App Store, toque no botão com o custo da licença na string *AdGuard Pro — Bloqueador de anúncios* e, em seguida, toque em *COMPRAR*. Pode ser solicitado que você insira seu login e senha do Apple ID. Digite-a e aguarde a conclusão da instalação. +Na página aberta da App Store, toque no botão com o custo da licença na string *AdGuard Pro - Bloqueador de anúncios* e, em seguida, toque em *COMPRAR*. Pode ser solicitado que você insira seu login e senha do Apple ID. Digite-a e aguarde a conclusão da instalação. ![Toque em OBTER abaixo do aplicativo AdGuard *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index d79e3be3b22..556d0ab47b9 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ Este artigo aborda o AdGuard para iOS, um bloqueador de anúncios multifuncional 1. Escolha um vídeo e toque em *Compartilhar*. 1. Toque em *Mais*e selecione *Bloquear anúncios do YouTube (por AdGuard)*. -O vídeo agora abre no player sem anúncios do AdGuard. +O AdGuard abrirá seu player de vídeo sem anúncios. ## Como bloquear anúncios no YouTube no Safari @@ -31,4 +31,4 @@ Certifique-se de ter concedido ao AdGuard acesso a todos os sites. Você pode ve 1. Escolha um vídeo e toque em *Compartilhar*. 1. Toque em *Bloquear anúncios do YouTube (por AdGuard)*. -O vídeo agora abre no player sem anúncios do AdGuard. +O AdGuard abrirá seu player de vídeo sem anúncios. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index bf57be16da6..9bc41a0be79 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ Para ir para *Configurações de baixo nível*, toque no ícone de engrenagem no Existem dois modos de túnel principais: *Split* e *Full*. O modo *Split-Tunnel* fornece compatibilidade entre o AdGuard e os chamados aplicativos "VPN pessoal". No modo *Full-Tunnel*, nenhuma outra VPN pode funcionar simultaneamente com o AdGuard. -Há um recurso específico do modo *Split-Tunnel*: em caso de baixo desempenho do proxy DNS, por exemplo, se a resposta do servidor DNS do AdGuard não for retornada em tempo hábil, o iOS redirecionará o tráfego por meio do servidor DNS especificado nas configurações do iOS. Nenhum anúncio está bloqueado neste momento e o tráfego DNS não é criptografado. +Há um recurso específico do modo *Split-Tunnel*: se o proxy DNS não funcionar bem, o iOS irá redirecionar o tráfego através do servidor DNS especificado nas configurações do iOS. Nenhum anúncio está bloqueado neste momento e o tráfego DNS não é criptografado. -No modo *Full-Tunnel*, apenas o servidor DNS especificado nas configurações do AdGuard é usado. Se não responder, a Internet simplesmente não funcionará. O modo *Full-Tunnel* ativado pode afetar negativamente o desempenho de alguns programas (por exemplo, FaceTime) e causar problemas de atualização de aplicativos. +No modo *Full-Tunnel*, apenas o servidor DNS especificado nas configurações do AdGuard é usado. Se não responder, a Internet simplesmente não funcionará. O modo *Full-Tunnel* ativado pode causar o desempenho incorreto de alguns programas (por exemplo, Facetime) e causar problemas com atualizações de aplicativos. Por padrão, o AdGuard usa o modo *Split-Tunnel* como a opção mais estável. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index c3580fd79eb..8dcfcfa49ab 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Tempo, em segundos, antes de enviar outra sonda de manutenção de atividade par #### `network.https.ech.enabled` -Usa um proxy DNS local para procurar configurações nas listas de configurações ECH. If found, encrypts Client Hellos. +Usa um proxy DNS local para procurar configurações nas listas de configurações ECH. Se encontrado, criptografa ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index ab60bc20efd..1f001ff96fb 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ Se você usar o Flutter junto com o AdGuard no modo "Extensão de rede" (ou qual #### Aplicativos VPN com API antiga -Apesar do AdGuard ser exibido como VPN nas configurações do sistema, ele não deve causar conflitos ao trabalhar com outros aplicativos baseados em VPN. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Apesar do AdGuard ser exibido como VPN nas configurações do sistema, ele não deve causar conflitos ao trabalhar com outros aplicativos baseados em VPN. No entanto, se você estiver usando um aplicativo baseado em VPN que foi baixado de fora da App Store, é possível que ele use a API VPN antiga e você precise excluí-lo da filtragem: 1. Abra o menu do AdGuard. 1. Selecione *Preferências...*. @@ -79,9 +79,9 @@ Esses problemas já foram corrigidos pela Apple, mas podem ser encontrados nas v ### Compatibilidade com o Little Snitch 5 -No momento, o modo de extensão de rede no AdGuard não é compatível com o [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. Esse problema é causado diretamente por um bug no Big Sur, e já informamos a Apple sobre isso. Isso nos leva a acreditar que esse problema será resolvido em uma das próximas atualizações. +No momento, o modo de extensão de rede no AdGuard não é compatível com o [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). Quando ambos estão em execução, é possível encontrar problemas com o comportamento de vários aplicativos, mesmo que não sejam filtrados pelo AdGuard. Esse problema é causado diretamente por um bug no Big Sur, e já informamos a Apple sobre isso. Isso nos leva a acreditar que esse problema será resolvido em uma das próximas atualizações. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. Recomendamos mudar para o modo de filtragem [**Automatic Proxy**](#automatic-proxy) ao executar o AdGuard junto com Little Snitch no Big Sur, pelo menos até que a Apple corrija o bug. +É preciso dizer que este problema não pode ser resolvido desativando o monitoramento de conexões no Little Snitch, pois esta ação não descarrega a extensão do Little Snitch do sistema. Recomendamos mudar para o modo de filtragem [**Automatic Proxy**](#automatic-proxy) ao executar o AdGuard junto com Little Snitch no Big Sur, pelo menos até que a Apple corrija o bug. ### Compatibilidade com proxies locais @@ -121,7 +121,7 @@ Em primeiro lugar, você precisa de um servidor funcional para o seu proxy. Prov :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +Você pode encontrar mais informações sobre como começar no site [Shadowsocks](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index 0a25e2d062b..6033cbe8470 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ Este artigo é sobre o AdGuard para Mac, um bloqueador de anúncios multifuncion ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". Este é um novo mecanismo de segurança que apareceu no High Sierra e exige que você permita explicitamente a instalação de uma extensão de sistema de terceiros. Para concluir a instalação do AdGuard, é necessário permitir o carregamento da extensão manualmente em *Preferências do sistema* → *Segurança & Privacidade* → *Geral*. +Durante a instalação do AdGuard no macOS High Sierra (ou versões posteriores), você poderá ver a mensagem: "Extensão do sistema bloqueada". Este é um novo mecanismo de segurança que apareceu no High Sierra e exige que você permita explicitamente a instalação de uma extensão de sistema de terceiros. Para concluir a instalação do AdGuard, é necessário permitir o carregamento da extensão manualmente em *Preferências do sistema* → *Segurança & Privacidade* → *Geral*. ![Dê permissão para a instalação de extensão nas configurações](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index e5eda7ffbb4..543b2180b8d 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ Como consequência, o AdGuard não pode funcionar em conjunto com os recursos de 1. O iCloud Private Relay é aplicado às conexões no nível da biblioteca antes que elas atinjam o nível do soquete, onde o AdGuard opera. 2. O iCloud Private Relay usa QUIC, que o AdGuard não pode filtrar porque a filtragem HTTP/3 ainda não está disponível. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequentemente, o AdGuard bloqueia o QUIC, incluindo o tráfego do iCloud Private Relay. Caso contrário, o bloqueio de anúncios é impossível. 4. Ao usar o iCloud Private Relay e alternar o AdGuard para o modo "túnel dividido", você não poderá abrir sites no Safari. 5. Para contornar esse problema em Monterey, aplicamos a regra da "rota padrão". Quando o Private Relay vê essa regra, ele se desativa automaticamente. Portanto, o AdGuard funciona perfeitamente em Monterey, mas o iCloud Private Relay é desativado. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index fcd5c24e070..cf88b37a28d 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ Na aba Sobre, é possível ver informações sobre a versão atual do seu produt :::note Lembrete -O AdGuard para Safari pode ser baixado gratuitamente [na App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). Uma instrução de configuração detalhada está disponível na [Base de conhecimento](/adguard-for-safari/installation/). +O AdGuard para Safari pode ser baixado gratuitamente [na App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). Uma instrução de configuração detalhada está disponível na [base de conhecimento](/adguard-for-safari/installation/). ::: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index 403789afd47..e167ea70c6d 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -21,10 +21,10 @@ Agora você pode enviar este arquivo para support@adguard.com ou anexá-lo ao se :::note -O AdGuard tem o compromisso de proteger sua privacidade. Seguimos rigorosamente nossa [Política de Privacidade](https://adguard.com/privacy/safari.html) e não coletamos nenhuma informação privada sobre os usuários. Antes de enviar seus registros para a equipe de suporte, revise o arquivo, pois ele pode conter informações adicionais que você não deseja compartilhar. Se contiver tais informações pessoais, recomendamos que você as exclua primeiro. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/safari.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -1. Abra o [repositório GitHub do AdGuard for Safari](https://github.com/AdguardTeam/AdGuardForSafari/issues) e clique em _Novo problema_. -2. Envie o arquivo de registro para devteam@adguard.com. Inclua a hora do bug e anexe um link para o seu problema ou seu número (aparece como #number próximo ao título). - Alternativamente, você pode fazer upload do arquivo de registro para o Google Drive e enviá-lo para devteam@adguard.com. Adicione o link do arquivo ao seu problema do GitHub. +1. Open the [AdGuard for Safari GitHub repo](https://github.com/AdguardTeam/AdGuardForSafari/issues) and click _New issue_. +2. Send the log file to devteam@adguard.com. Include the time of the bug and attach a link to your issue or its number (it appears as #number next to the title). + Alternatively, you can upload the log file to Google Drive and send it to devteam@adguard.com. Add the file link to your GitHub issue. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 16d965d8bbf..df3ad6efc63 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ O Assistente AdGuard é um assistente antigo que você pode usar se o [novo assi Esta é uma extensão personalizada projetada para combater a técnica de reinserção de anúncios bloqueados, conhecida com evasão/reinjeção de anúncios do bloqueador de anúncios. Ambos são métodos avançados de bloqueio de anúncios que continuam a crescer em popularidade entre os anunciantes. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +O AdGuard Extra é basicamente um miniprograma que altera a forma como as páginas funcionam, de modo que se torna muito mais difícil para os sites usarem os métodos mencionados acima para contornar os bloqueadores. **Bloqueador de pop-ups do AdGuard** -Esta extensão evita que janelas popup sejam abertas quando você visualiza páginas da web. Algumas popups são consideradas úteis: elas podem conter configurações para administração do site ou informações de referência adicionais demonstradas ao clicar em um link. É por isso que você pode desligar o bloqueador, se necessário. Esta extensão também não funciona em sites adicionados à lista de exceções do AdGuard. Ele está desativado por padrão, mas você pode ativá-lo nas configurações do aplicativo. You will find more detailed information about this extension in our Knowledge Base. +Esta extensão evita que janelas popup sejam abertas quando você visualiza páginas da web. Algumas popups são consideradas úteis: elas podem conter configurações para administração do site ou informações de referência adicionais demonstradas ao clicar em um link. É por isso que você pode desligar o bloqueador, se necessário. Esta extensão também não funciona em sites adicionados à lista de exceções do AdGuard. Ele está desativado por padrão, mas você pode ativá-lo nas configurações do aplicativo. Você encontrará informações mais detalhadas sobre esta extensão em nossa base de conhecimento. **Web of Trust** @@ -41,7 +41,7 @@ O Web of Trust permite que você veja a reputação de cada site com base nas op ### Rede -O penúltimo módulo é dedicado à filtragem de rede e aqui você encontrará opções adicionais relacionadas à rede. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Estas são precauções extras importantes para filtrar melhor o seu espaço web. A maioria dos sites agora usa HTTPS, e o mesmo se aplica à publicidade. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +O penúltimo módulo é dedicado à filtragem de rede e aqui você encontrará opções adicionais relacionadas à rede. Dois deles estão habilitados por padrão: _Habilitar filtragem de tráfego_ e _Filtrar protocolo HTTPS_. Estas são precauções extras importantes para filtrar melhor o seu espaço web. A maioria dos sites agora usa HTTPS, e o mesmo se aplica à publicidade. Em muitos sites, como youtube.com, facebook.com e twitter.com, é impossível remover anúncios sem filtragem HTTPS. Portanto, mantenha o recurso _Filtrar protocolo HTTPS_ ativado, a menos que você tenha um forte motivo para não fazê-lo. ![Configurações de rede \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 59d977d45d1..507614c80e7 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ _Configurações_ é a seção que requer mais atenção. É aqui que você pode ### Configurações gerais -Aqui você pode definir o idioma e o tema (escuro ou claro), ativar o lançamento do AdGuard na inicialização do sistema e atualizações automáticas silenciosas, escolher o canal de atualização e filtrar o intervalo de verificação de atualização. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +Aqui você pode definir o idioma e o tema (escuro ou claro), ativar o lançamento do AdGuard na inicialização do sistema e atualizações automáticas silenciosas, escolher o canal de atualização e filtrar o intervalo de verificação de atualização. Além disso, você pode recorrer às Configurações se o AdGuard para Windows não estiver funcionando corretamente e a equipe de suporte solicitar que você [colete _logs de depuração_](/adguard-for-windows/solving-problems/adguard-logs.md). ![Configurações avançadas \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ Existem vários websites aos quais o acesso deve ser restringido a partir de um O módulo verifica o conteúdo das páginas web abertas no navegador e filtra aquelas com conteúdo indesejável para crianças: imagens e textos para adultos, linguagem grosseira, violência, propaganda de drogas, etc. As configurações do Controle Parental são protegidas por senha para que a criança não consiga contornar as restrições. Este módulo não apenas bloqueia direções para sites indesejáveis, mas também pode excluir links inadequados para crianças dos resultados da pesquisa. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Você também pode marcar a caixa _Bloquear download de arquivos executáveis_ para evitar que seu filho baixe e instale software no computador. Existem mais duas opções no módulo _Controle Parental_: você pode selecionar um usuário específico do Windows para ser protegido pelo _Controle Parental_ e definir uma senha para proteger as configurações do AdGuard contra alterações. +No módulo Controle Parental você pode ativar a _Pesquisa segura_ e gerenciar a _lista de bloqueios_ e a _lista de permissões_ para personalizar o funcionamento desta opção. Você também pode marcar a caixa _Bloquear download de arquivos executáveis_ para evitar que seu filho baixe e instale software no computador. Existem mais duas opções no módulo _Controle Parental_: você pode selecionar um usuário específico do Windows para ser protegido pelo _Controle Parental_ e definir uma senha para proteger as configurações do AdGuard contra alterações. ![Controle parental \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index 751d54baf49..3d448f7c993 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ Este artigo aborda o AdGuard para Windows, um bloqueador de anúncios multifunci To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index e050c0742c1..83e572edff8 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard logs +title: Como coletar logs do AdGuard sidebar_position: 3 --- @@ -15,7 +15,7 @@ Os dados e/ou arquivos fornecidos nos logs são processados de acordo com [a Pol ::: -Para analisar e diagnosticar diferentes problemas que possam surgir, o serviço de suporte AdGuard pode precisar de arquivos de log. These files contain records about errors and other events that occur with the software. Há uma breve instrução abaixo que descreve a forma de obter os arquivos de log e enviá-los ao serviço de suporte, se necessário. +Para analisar e diagnosticar diferentes problemas que possam surgir, o serviço de suporte AdGuard pode precisar de arquivos de log. Esses arquivos contêm registros sobre erros e outros eventos que ocorrem com o software. Há uma breve instrução abaixo que descreve a forma de obter os arquivos de log e enviá-los ao serviço de suporte, se necessário. :::note @@ -25,7 +25,7 @@ O AdGuard tem o compromisso de proteger sua privacidade. Seguimos rigorosamente ### Registros de depuração {#debug-logs} -1. Abra as configurações do AdGuard. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Abra as configurações do AdGuard. Vá para a seção *Configurações gerais*, role para baixo até o final da tela e alterne o *Nível de registro* para *Depuração*. ![Nível de registro de depuração *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ O AdGuard tem o compromisso de proteger sua privacidade. Seguimos rigorosamente Aconselhamos fortemente que você anote o momento exato em que você reproduziu o problema: isso ajudará nossa equipe de suporte a encontrar entradas de log relevantes e resolver o problema mais rapidamente. -1. Export the collected logs using the *Export Logs* button. +1. Exporte os registros gravados usando o botão *Exportar Logs*. ![Exportar logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Salve o arquivo em qualquer pasta. -1. **Important**: after exporting the logs, set the logging level back to *Default*. O nível de registro *Depuração* deixará o aplicativo lento. +1. **Importante**: após exportar os logs, defina o nível de registro de volta para *Padrão*. O nível de registro *Depuração* deixará o aplicativo lento. 1. Envie o arquivo para o serviço de suporte do AdGuard em **support@adguard.com**, descreva o problema e não se esqueça de mencionar o horário em que você reproduziu o problema. @@ -65,7 +65,7 @@ Se você tiver uma versão mais antiga do AdGuard para Windows, execute o aplica Aconselhamos fortemente que você anote o momento exato em que você reproduziu o problema: isso ajudará nossa equipe de suporte a encontrar entradas de log relevantes e resolver o problema mais rapidamente. -1. Export the collected logs using the *Export Logs* button. +1. Exporte os registros gravados usando o botão *Exportar Logs*. ![Exportar logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 9bbb96baf9f..05d83877999 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ Este artigo contém alguns dos erros mais comuns que você pode encontrar durant ### Erro 5: Acesso negado {#error-5} -This error message appears when required permissions haven't been granted. Pode haver vários motivos diferentes pelos quais o instalador do AdGuard não tem as permissões necessárias para concluir corretamente o processo de instalação. Você pode tentar as seguintes etapas: +Esse erro ocorre quando há algo errado com as permissões. Pode haver vários motivos diferentes pelos quais o instalador do AdGuard não tem as permissões necessárias para concluir corretamente o processo de instalação. Você pode tentar as seguintes etapas: -- Temporarily disable your antivirus. Alguns deles podem interferir na instalação, dependendo de suas configurações. +- Desative temporariamente seus antivírus. Alguns deles podem interferir na instalação, dependendo de suas configurações. - Escolha uma pasta de instalação diferente. É possível que a pasta de instalação atual tenha algumas restrições de acesso. Certifique-se também de não selecionar uma unidade externa, uma unidade virtual, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. Pode ### Erro 112: O disco está cheio, Erro 1632: Pasta temporária cheia ou inacessível {#error-112} -Estes são dois erros diferentes com soluções muito semelhantes. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. Há várias coisas que você pode fazer para tentar corrigir o problema: +Estes são dois erros diferentes com soluções muito semelhantes. Como seus nomes sugerem, o instalador AdGuard não encontrou espaço em disco suficiente para concluir a instalação. Há várias coisas que você pode fazer para tentar corrigir o problema: - Desinstale alguns programas ou exclua arquivos desnecessários da unidade em que você estava tentando instalar o AdGuard. -- Baixe, instale e execute o [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), um software gratuito da Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. Isso ajudará a liberar espaço em disco. +- Baixe, instale e execute o [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), um software gratuito da Malwarebytes. Ele irá, entre outras coisas, limpar seu sistema de todos os tipos de arquivos extras “sobras” que permanecem após a desinstalação incorreta de programas e similares. Isso ajudará a liberar espaço em disco. - Reinicie o computador. Às vezes, os arquivos temporários podem ocupar uma quantidade considerável de espaço em disco e reiniciar o PC é a maneira mais simples de se livrar deles. ### Erro 1601: o instalador do Windows não está acessível {#error-1601} -You could say this is a particular subcategory of Error 1603. As soluções possíveis são semelhantes: +Pode-se dizer que esse é um subcaso específico do Erro 1603. As soluções possíveis são semelhantes: - Inicie e registre novamente o serviço Instalador Microsoft. Isso dá um pouco de trabalho. @@ -75,7 +75,7 @@ Este erro ocorre quando várias instâncias do instalador do AdGuard são inicia - Reinicie o computador e inicie o instalador novamente. Quando você reiniciar o computador, todos os processos em andamento serão interrompidos, incluindo todas as cópias do instalador. -- Don't make multiple clicks on the installer even if it doesn't start right away. Às vezes, pode levar alguns segundos para exibir a interface do usuário do instalador. +- Não faça vários cliques no instalador, mesmo que ele não inicie imediatamente. Às vezes, pode levar alguns segundos para exibir a interface do usuário do instalador. ### Erro 1638: outra versão deste produto já está instalada {#error-1638} @@ -83,14 +83,14 @@ Este erro ocorre quando várias instâncias do instalador do AdGuard são inicia - Verifique se o AdGuard já está instalado no seu computador. Você pode fazer isso pressionando a tecla *Win* e digitando ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Desinstale o AdGuard usando nossa [ferramenta de desinstalação](../../installation#advanced) e repita a instalação. +- Pode ser que haja alguns arquivos restantes de uma instalação anterior do AdGuard. Desinstale o AdGuard usando nossa [ferramenta de desinstalação](../../installation#advanced) e repita a instalação. ### Outros erros {#other} Se você encontrou um erro que não está listado acima, é possível que possamos resolvê-lo sozinhos. Mas, para isso, precisamos de seus arquivos de log. Por favor, execute as seguintes etapas: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Encontre e arquive **AdGuard installation logs** conforme descrito em [neste artigo](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [Este artigo](../system-logs) explica como fazer isso. +- Localize e salve no disco **Event Viewer** logs. [Este artigo](../system-logs) explica como fazer isso. - Por favor, envie todos esses arquivos das duas etapas anteriores para a equipe de suporte em **support@adguard.com** e descreva o problema no corpo da mensagem. Nossa equipe de suporte responderá o mais rápido possível. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index 1840d605579..bd0e538adcb 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ Este artigo aborda o AdGuard para Windows, um bloqueador de anúncios multifunci O AdGuard para Windows permite que os usuários especifiquem um endereço de servidor DNS para resolver consultas em vez do servidor DNS do sistema, que é fornecido pelo seu ISP se não for substituído nas configurações do sistema. Usar um servidor DNS não padrão pode proteger seu tráfego DNS contra interceptação do ISP. Além disso, ao escolher um servidor DNS criptografado e/ou filtrante, você obtém outra camada de proteção contra ameaças e anúncios irritantes. -Muitos usuários do AdGuard para Windows gostam do recurso de proteção DNS. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. Neste artigo, explicaremos por que isso acontece e como evitá-lo. +Muitos usuários do AdGuard para Windows gostam do recurso de proteção DNS. Mas alguns deles encontram o seguinte problema: uma verificação em um site como https://ipleak.net/ mostra que as solicitações são tratadas pelo servidor DNS padrão em vez do servidor selecionado. Neste artigo, explicaremos por que isso acontece e como evitá-lo. ## Endereço DNS de bootstrap @@ -21,7 +21,7 @@ Os endereços dos servidores DNS podem ser escritos como IPs ou nomes de domíni - vá para *Configurações avançadas* - role para baixo até a seção *Lista de endereços de bootstrap personalizados* -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- insira o endereço de inicialização personalizado no formato de endereço IP (você pode usar [a lista de provedores de DNS conhecidos](https://adguard-dns.io/kb/general/dns-providers/)) - clique em *Salvar* ## Servidor DNS fallback @@ -33,7 +33,7 @@ Pode ser que o AdGuard não consiga acessar o servidor especificado devido a uma - vá para *Configurações avançadas* - role para baixo até a seção *Servidores de fallback* - marque a opção *Usar servidores personalizados* -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- em seguida, encontre a seção *Lista de servidores fallback personalizados* e insira servidores fallback personalizados, um por linha ou diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 21c83176e8a..9086142add7 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ Depois de criar o arquivo dump, navegue até o local do arquivo. Será pedido qu :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +O AdGuard para Windows tem dois processos em execução (`Adguard.exe` e `AdguardSvc.exe`). Portanto, você precisa criar o arquivo dump separadamente para cada processo. ::: ![Processos do AdGuard](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -Ao enviar os arquivos dump para a equipe de suporte, anexe também os logs do aplicativo AdGuard para que tenhamos mais chances de resolver o problema. [Here](../adguard-logs) you can check the instructions on how to get the log file. +Ao enviar os arquivos dump para a equipe de suporte, anexe também os logs do aplicativo AdGuard para que tenhamos mais chances de resolver o problema. [Aqui](../adguard-logs) você pode verificar as instruções sobre como coletar o arquivo de log. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 96942e54b09..d170a6daaa6 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard installation logs +title: Como coletar logs de instalação do AdGuard sidebar_position: 4 --- @@ -17,7 +17,7 @@ Os dados e/ou arquivos fornecidos nos registros do sistema são processados de a Caso ocorra algum problema durante a instalação do AdGuard, a equipe de suporte poderá solicitar que você colete e envie os logs de instalação do AdGuard. Neste caso você precisa: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Selecione o comando *Executar* no menu Iniciar ou pressione *Win + R* no teclado. 1. Digite *%tmp%* e clique em *OK*. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4308742f4ff..c0176f3be26 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Depois de abrir as Configurações avançadas, você verá as seguintes opções Se ativado, o AdGuard bloqueará o TCP Fast Open no navegador Edge. Para aplicar as configurações, você precisa reiniciar o navegador. -### Use Encrypted Client Hello +### Usar Encrypted ClientHello -Cada conexão de Internet criptografada tem uma parte não criptografada. Estamos falando do primeiro pacote, que contém o nome do servidor ao qual você está se conectando. A tecnologia Encrypted ClientHello deve resolver esse problema e criptografar esta última parte de informação não criptografada. To benefit from it, enable the *Use Encrypted Client Hello* option. Ela utiliza um proxy DNS local para procurar a configuração ECH para o domínio. If it is found, Client Hello packet will be encrypted. +Cada conexão de Internet criptografada tem uma parte não criptografada. Estamos falando do primeiro pacote, que contém o nome do servidor ao qual você está se conectando. A tecnologia Encrypted ClientHello deve resolver esse problema e criptografar esta última parte de informação não criptografada. Para utilizá-la, habilite a opção *Usar Encrypted ClientHello*. Ela utiliza um proxy DNS local para procurar a configuração ECH para o domínio. Se encontrado, o pacote ClientHello será criptografado. ### Verificar a transparência do certificado dos sites @@ -73,7 +73,7 @@ Caso contrário, o AdGuard filtrará todo o tráfego em tempo real, sem redireci ### Abrir a janela principal na inicialização do sistema -Ative esta opção para abrir a janela principal do AdGuard depois que o sistema for carregado. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Ative esta opção para abrir a janela principal do AdGuard depois que o sistema for carregado. Observe que isso não afeta se o serviço de filtragem real será iniciado ou não. Esta configuração está localizada em *Configurações → Configurações Gerais* ### Ativar filtragem na inicialização do sistema @@ -95,7 +95,7 @@ Se você não deseja que o AdGuard filtre sub-redes específicas, ative esse rec ### Habilitar escrita HAR -Esta opção deve ser habilitada **apenas para fins de debugging**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. Este arquivo pode ser analisado com o aplicativo Fiddler. Observe que isso pode tornar sua navegação na web significativamente mais lenta. +Esta opção deve ser habilitada **apenas para fins de debugging**. Se você marcar esta opção, o AdGuard criará um arquivo que contém informações sobre todas as solicitações HTTP filtradas no formato HAR 1.2. Este arquivo pode ser analisado com o aplicativo Fiddler. Observe que isso pode tornar sua navegação na web significativamente mais lenta. ### Adicionar um espaço extra à solicitação HTTP simples @@ -115,7 +115,7 @@ Esta opção só é aplicada quando a opção do modo Stealth *Proteger de DPI* Especifica o tamanho da fragmentação do pacote TCP, evitando a inspeção profunda do pacote. Esta opção afeta apenas o tráfego seguro (HTTPS). -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +Se esta opção estiver ativada, o AdGuard divide o pacote TLS inicial (o pacote ClientHello) em duas partes: a primeira tem o comprimento especificado e a segunda tem o restante, até o comprimento de todo o pacote TLS inicial. Valores válidos: 1–1500. Se for especificado um tamanho inválido, o valor selecionado pelo sistema será utilizado. Esta opção só é aplicada quando a opção do modo Stealth *Proteger de DPI* está habilitada. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 836bbbb0752..138276b5cd1 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect Windows system logs +title: Como coletar logs do sistema Windows sidebar_position: 5 --- @@ -15,7 +15,7 @@ Os dados e/ou arquivos fornecidos nos registros do sistema são processados de a ::: -Para analisar e diagnosticar diferentes problemas que possam surgir, o serviço de suporte AdGuard pode precisar de arquivos de log do sistema Windows. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Há uma breve instrução abaixo que descreve a forma de obter os arquivos de log e enviá-los ao nosso serviço de suporte, se necessário. +Para analisar e diagnosticar diferentes problemas que possam surgir, o serviço de suporte AdGuard pode precisar de arquivos de log do sistema Windows. Os logs de eventos do Windows contêm registros sobre todos os erros que ocorrem com o software instalado, incluindo o AdGuard. Há uma breve instrução abaixo que descreve a forma de obter os arquivos de log e enviá-los ao nosso serviço de suporte, se necessário. 1. Pressiona *Win + R* diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 22408438d29..dc7ba38add7 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ Este artigo aborda o AdGuard para Windows, um bloqueador de anúncios multifunci ::: -Para filtrar o tráfego de rede, o AdGuard usa um driver de rede. Existem duas opções: driver TDI e driver WFP. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. Esses problemas e erros subsequentes podem ser muito diferentes em cada caso. +Para filtrar o tráfego de rede, o AdGuard usa um driver de rede. Existem duas opções: driver TDI e driver WFP. Embora o driver WFP seja geralmente preferível e esteja ativado por padrão para todas as versões mais recentes do sistema operacional Windows (Windows 8 e mais recentes), ele pode causar problemas de compatibilidade, especialmente com alguns antivírus. Esses problemas e erros subsequentes podem ser muito diferentes em cada caso. Se você encontrar um problema que suspeita ser causado por isso, você sempre pode mudar para o driver de rede TDI mais antigo, porém mais estável. Para isso: 1. Vá para *Configurações → Rede*. -2. Disable the WFP driver as it’s done in this picture: +2. Desative o driver WFP como é feito nesta imagem: ![Driver WFP *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/account/features.md index 95b20a6805a..2f1f2863657 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ A seção Histórico de compras exibe todas as licenças que você já comprou u ## Entrar em contato com o suporte -A guia Suporte contém links úteis para ajudá-lo a resolver problemas ou encontrar respostas para suas perguntas sobre os produtos AdGuard. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +A guia Suporte contém links úteis para ajudá-lo a resolver problemas ou encontrar respostas para suas perguntas sobre os produtos AdGuard. Eles são divididos em seis seções: FAQ, Enviar um relatório de bug/sugestão de funcionalidade, Denunciar bloqueio incorreto, Suporte, Base de conhecimento e Discussão. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 55c450cf5f7..40ed6e8a612 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ Este artigo é sobre os filtros que criamos para usar no AdGuard e outros softwa - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index ed482b81404..99885e0d073 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-------------------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:-------------------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:-------------------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:-------------------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard para iOS][ios-app] | [AdGuard para Safari][ext-saf] | [Bloqueador de conteúdo do AdGuard][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:---------------------------:|:------------------------------:|:-------------------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,32 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard para Safari" -[ext-saf]: #what-product "AdGuard for Safari" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index d25ee414d41..6db7dc1d57d 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ Os filtros de bloqueio de anúncios AdGuard incluem: - Filtro base do AdGuard - Filtro de anúncios para dispositivos móveis do AdGuard - Filtros regionais divididos por idiomas: chinês, holandês, francês, alemão, japonês, russo, espanhol, português, turco e ucraniano -- AdGuard Quick Fixes filter ### O propósito desses filtros - O **Filtro base** foi projetado para bloquear anúncios em sites em inglês e aqueles para os quais não há filtro separado. Ele também contém regras gerais de filtragem que se aplicam a todos os sites, independentemente do idioma - O **Filtro de anúncios para dispositivos móveis** bloqueia anúncios em versões móveis de sites e em celulares e tablets. Não há segmentação com base no idioma - Os **Filtros regionais** seguem a mesma política do **Filtro base**, mas são limitados a sites em determinados idiomas -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. O objetivo dos filtros de bloqueio de anúncios é bloquear todos os tipos de publicidade em sites, aplicativos e determinados dispositivos que podem carregar anúncios da Internet: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/browsing-security.md index d9b8d12b980..d4123cd4e51 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. Fazemos o possível para reduzir a porcentagem de falsos positivos, mas eles ainda assim podem ocorrer. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/license/what-is.md index fad8c16cb3a..479a8243ae7 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ Na página de compra [](https://adguard.com/license.html), você verá os seguin - **Assinaturas de 1 ano**: essas licenças são renovadas automaticamente todos os anos ou podem ser estendidas manualmente - Individual: até 3 dispositivos - Familiar: até 9 dispositivos -- **Lifetime** — these licenses are perpetual +- **Vitalícia**: essas licenças não têm limitadas de tempo - Individual: até 3 dispositivos - Familiar: até 9 dispositivos diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 95c1dfe57a2..b7c075b1981 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Ativar esta opção impedirá que o navegador envie dados de GPS que possam ser ### Bloquear Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Ativar essa configuração faz com que o AdGuard bloqueie a capacidade dos navegadores de detectar componentes (como plug-ins e objetos ActiveXObject) que permitem que o Flash exiba conteúdo. Na prática, isso implica que os navegadores não suportem Flash. +O plugin Flash Player tornou-se cada vez mais vulnerável a ameaças online como vírus e hackers; também pode afetar significativamente o tempo de carregamento do site. Ativar essa configuração faz com que o AdGuard bloqueie a capacidade dos navegadores de detectar componentes (como plug-ins e objetos ActiveXObject) que permitem que o Flash exiba conteúdo. Na prática, isso implica que os navegadores não suportem Flash. ### Bloquear Java {#java} @@ -95,7 +95,7 @@ Você também pode definir um valor arbitrário para o Referer inserindo-o no ca Observe que, para poder filtrar o tráfego, os aplicativos AdGuard "interceptam" as solicitações do navegador para o servidor. As solicitações para servidores de anúncios, rastreamento e phishing podem ser alteradas antes de serem enviadas ao servidor ou bloqueadas completamente. O mesmo vale para a opção *Ocultar referenciador de terceiros*: o AdGuard intercepta solicitações HTTP(S), em particular para remover ou alterar o cabeçalho do referenciador se esta opção estiver habilitada. No entanto, isso só acontece depois que essas solicitações "saem" do navegador. Isso significa que, se você monitorar o Referer dentro do navegador (por exemplo, com a ajuda das Ferramentas de Desenvolvedor do Chrome), você verá o Referer original porque a solicitação ainda não chegou ao AdGuard. Você pode usar software como [Fiddler](https://www.telerik.com/fiddler) para garantir que o Referer seja alterado corretamente. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. Ela alterará o Referer ali mesmo, então as Ferramentas do Desenvolvedor mostrarão o Referer desejado para suas solicitações. +Pelo contrário, devido à natureza de todas as extensões do navegador, a extensão de navegador AdGuard funciona “dentro” do navegador. Ela alterará o Referer ali mesmo, então as Ferramentas do Desenvolvedor mostrarão o Referer desejado para suas solicitações. ### Ocultar seu agente de usuário {#useragent} @@ -120,9 +120,3 @@ O Deep Packet Inspection é um sistema de análise profunda e filtragem de tráf O AdGuard pode modificar os dados do pacote de saída para que o cliente não se enquadre nos critérios de bloqueio de DPI. Isso significa que, ao habilitar esta opção, os usuários podem ter acesso ao conteúdo que desejam. Nem todos os sistemas DPI podem ser ignorados neste momento, mas estamos trabalhando constantemente para melhorar isso. O recurso "Proteger contra DPI" já está implementado no AdGuard para Windows, AdGuard para Mac e AdGuard para Android. - -:::cuidado - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/userscripts.md index 219aa3b54bb..e673123b215 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. Eles modificam ou ampliam a funcionalidade de um ou mais websites. Muitos usuários do AdGuard já podem estar familiarizados com scripts de usuário como o Assistente AdGuard, o Bloqueador de pop-ups e o AdGuard Extra. +Userscripts (também chamados de "extensões") são, na verdade, miniprogramas escritos em JavaScript. Eles modificam ou ampliam a funcionalidade de um ou mais websites. Muitos usuários do AdGuard já podem estar familiarizados com scripts de usuário como o Assistente AdGuard, o Bloqueador de pop-ups e o AdGuard Extra. :::note Aplicativos compatíveis @@ -134,7 +134,7 @@ Aqui está um [link mailto](mailto:devteam@adguard.com?Subject=Userscript%20auth ##### Propriedades não compatíveis -These properties will be simply ignored by AdGuard. +Essas propriedades serão simplesmente ignoradas pelo Adguard. ```text @unwrap diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index c2ab4ae23f1..41ca00ee7ba 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: Como coletar um arquivo HAR sidebar_position: 1 --- diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/report-bugs.md index bda385f1767..b489444fc02 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Verificar se o bug não foi reportado antes. Aconselhamos prestar atenção a qu ### Como descrever um problema -Tente fornecer o máximo de detalhes possível, isso facilitará a reprodução do bug e a descoberta de como corrigi-lo. Here’s what we expect a bug report to include: +Tente fornecer o máximo de detalhes possível, isso facilitará a reprodução do bug e a descoberta de como corrigi-lo. Aqui está o que esperamos ver em um relatório de bug: - A versão do seu aplicativo - A sua versão do SO @@ -28,7 +28,7 @@ Tente fornecer o máximo de detalhes possível, isso facilitará a reprodução ### Como coletar registros -Read about collecting logs in dedicated articles for each platform. +Leia sobre a coleta de logs em artigos dedicados para cada plataforma. ## Como votar em relatórios de bugs ou solicitações de recursos diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index a2e475c75a6..facde26b57a 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ Em alguns notebooks, você deve segurar *Fn*, e então pressionar *PrtScn*. O Windows captura a tela inteira e copia para a área de transferência. -To take a screenshot of an active window, use the following shortcut keys: +Para tirar uma captura de tela de uma janela ativa, use o seguinte atalho: - **Segure *Alt* e pressione *PrtScn* (ou *Fn + Alt + PrtScn* em alguns laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +Para fazer uma captura de tela de uma área específica, use o seguinte atalho: - ***Pressione ***Win + Shift + S****** -Depois de tirar uma captura de tela, ela será salva na área de transferência. Na maioria dos casos, você poderá colá-lo em um documento que esteja editando no momento usando o atalho *Ctrl + V*. Como alternativa, se você precisar salvar a captura de tela em um arquivo, abra o programa padrão **Paint** (ou qualquer outro aplicativo que possa trabalhar com imagens). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +Depois de tirar uma captura de tela, ela será salva na área de transferência. Na maioria dos casos, você poderá colá-lo em um documento que esteja editando no momento usando o atalho *Ctrl + V*. Como alternativa, se você precisar salvar a captura de tela em um arquivo, abra o programa padrão **Paint** (ou qualquer outro aplicativo que possa trabalhar com imagens). Cole sua captura de tela lá usando o mesmo atalho ou clicando no botão Colar (geralmente no canto superior esquerdo da tela) e depois salve-a. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. Assim que você pressionar essas teclas, a captura de tela será salva automaticamente como um arquivo em *Imagens* → *Pasta de Capturas de Tela*. +Os Windows 8 e 10 permitem que você faça uma captura de tela muito rapidamente com o atalho *Win + PrtScn*. Assim que você pressionar essas teclas, a captura de tela será salva automaticamente como um arquivo em *Imagens* → *Pasta de Capturas de Tela*. Há também um programa dedicado para tirar screenshots chamado *Snipping Tool* que você pode encontrar através do menu Iniciar entre os programas padrão do seu computador. A ferramenta de recorte permite capturar qualquer área da área de trabalho ou a tela inteira. Depois de fazer uma captura de tela usando este programa, você pode editar a imagem e salvá-la em qualquer pasta do seu computador. @@ -70,26 +70,26 @@ Além disso, você também pode tentar usar diferentes aplicativos para tirar sc ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Para fazer uma captura de tela no Mac, use o seguinte atalho: - ***Pressione e segure ***⌘ Cmd + Shift + 3****** Seu Mac irá capturar a tela inteira e salvá-la como um arquivo na área de trabalho. -To take a screenshot of an active window, use the following shortcut keys: +Para tirar uma captura de tela de uma janela ativa, use o seguinte atalho: - **Pressione e segure *⌘ Cmd + Shift + 4 + Barra de espaço*. O ponteiro mudará para um ícone de câmera. Clique na janela para capturar. Pressione Esc para cancelar a captura de tela** -To take a screenshot of a specific area, use the following shortcut keys: +Para fazer uma captura de tela de uma área específica, use o seguinte atalho: - ***Pressione ***⌘ Cmd + Shift + 5******. Arraste a mira para selecionar a área necessária. Solte o mouse ou o trackpad para fazer uma captura de tela, pressione Esc para cancelá-la. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +Para fazer uma captura de tela da *Touch Bar* (MacBook Pro), use o seguinte atalho: - ***Pressione ***⌘ Cmd + Shift + 6****** Seu Mac captura toda a *Touch Bar* e a salva como um arquivo na área de trabalho. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +Para copiar uma captura de tela para a área de transferência em vez de salvá-la, mantenha pressionado *Ctrl* junto com qualquer um dos atalhos acima. Em seguida, você pode colar a captura de tela (da área de transferência) em um documento ou imagem que está editando no momento usando o atalho *Cmd + V*. Você também pode fazer capturas de tela usando **Visualização** e escolhendo **Tirar captura de tela** (da área selecionada, janela ou tela inteira). Com **Preview** você pode salvar suas capturas de tela em JPG, TIFF, PDF e outros formatos de arquivo. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/intro.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/intro.md index 6a67eff5ce8..fbd50c7fbfa 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index c81620e764a..6a1daf63dac 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Os sites mudam constantemente a maneira como incorporam anúncios, e adicionamos No entanto, trabalhar com filtros de bloqueio requer habilidades específicas. Se você as possui e sabe como criar regras, vá direto para o nosso repositório[AdGuard Filters](https://github.com/AdguardTeam/AdguardFilters) no GitHub. Lá você encontrará muitas questões em aberto, cada uma referindo-se a um problema do site: um anúncio perdido, um falso positivo etc. Escolha qualquer um e sugira suas próprias regras nos comentários. Os engenheiros de filtro do AdGuard revisarão suas sugestões e, se acharem apropriado, suas regras serão adicionadas aos filtros do AdGuard. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +Se você ainda não está familiarizado com nossa sintaxe de regras de filtragem, ou talvez precise de uma atualização, você encontrará o básico sobre a sintaxe [em nossa Base de conhecimento](/general/ad-filtering/create-own-filters). ### Recompensas {#rewards} diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index 00f618e1c80..c7a8652328b 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Tornando-se um tradutor/revisor sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +Se você quiser ajudar a traduzir produtos AdGuard, sites e bases de conhecimento, vá para [Crowdin](https://crowdin.com/) e inscreva-se/faça login. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index 3bb5acbd3c4..d0ee34739cd 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ Quando você se depara com uma tradução que exige o uso de plurais, talvez nã Aqui estão algumas fontes de informação que você pode usar. -[O Guia de Localização](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contém uma ampla lista de idiomas. O número de formas plurais para diferentes idiomas é mostrado desta forma: `nplurals=2`, `nplurals=4` e assim por diante. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[O Guia de Localização](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contém uma ampla lista de idiomas. O número de formas plurais para diferentes idiomas é mostrado desta forma: `nplurals=2`, `nplurals=4` e assim por diante. O numeral após o sinal de igual `=` significa o número de formas plurais do respectivo idioma. Além disso, você pode obter informações sobre formas plurais no [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). As regras do plural CLDR indicam uma forma de palavra adicional para números decimais (1,5; 2,3; 100,1…), mas não as usamos nas traduções do AdGuard. diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 0ca696b849a..75ec7507cc3 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: Programa de tradução do AdGuard sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Aviso:** pode fazer-nos quaisquer perguntas sobre a tradução do AdGuard enviando um e-mail para [translate@adguard.com](mailto:translate@adguard.com) ou juntando-se ao nosso [chat no Telegram](https://t.me/joinchat/UVYTLcHbr8JmOGIy). -When it comes to translations, we at AdGuard always heavily rely on volunteers. +Quando se trata de traduções, nós do AdGuard sempre dependemos fortemente de voluntários. -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +Agora usamos a plataforma [Crowdin](https://crowdin.com/) para gerenciar traduções de nossos produtos. Portanto, este é o lugar para quem deseja contribuir com o AdGuard traduzindo qualquer um de nossos produtos. -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +Se você deseja estar entre os voluntários que nos ajudam a traduzir o AdGuard, leia as informações sobre [como se tornar nosso tradutor](../become-translator) e [como colaboramos com eles](../rewards). diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 7b12ab68411..d4099b4fc5c 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: Como priorizar as traduções dos arquivos do Crowdin sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +Existem cinco projetos principais do AdGuard no Crowdin: [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), e [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). Não temos uma sugestão clara sobre com quais arquivos ou produtos do projeto *AdGuard Applications* começar. Basta escolher qualquer produto de que goste. Há apenas algumas coisas que queremos mencionar: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- Você pode ver o aplicativo apenas nos idiomas para os quais todas as traduções forem completadas no Crowdin; - Recomendamos traduzir as descrições para lojas de aplicativos em segundo lugar, porque sem a tradução dos próprios produtos, estas descrições não serão necessárias. A situação é diferente no projeto *AdGuard Websites*. Os idiomas podem ser adicionados ao site mesmo que um conjunto completo de traduções não esteja disponível. No entanto, isso depende de quais arquivos já foram traduzidos. É por isso que recomendamos que você comece com os arquivos mais importantes, listados abaixo: diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index fe7c6484f7c..c9f9b4884f7 100644 --- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Atualizando a Base de conhecimento sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. Mas as coisas mudam constantemente e, às vezes, um artigo não reflete mais o estado atual das coisas. +O objetivo da base de conhecimento do Bloqueador de anúncios AdGuard é fornecer a todos as informações mais atualizadas sobre todos os tipos de tópicos relacionados ao AdGuard. Mas as coisas mudam constantemente e, às vezes, um artigo não reflete mais o estado atual das coisas. É por isso que colocamos todo o nosso conteúdo KB no [GitHub](https://github.com/AdguardTeam/KnowledgeBase), e agora literalmente qualquer pessoa pode contribuir sugerindo edições e traduções de artigos existentes, bem como de artigos totalmente novos. ## Como sugerir uma mudança ou escrever um novo artigo {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. Se você não estiver familiarizado com os princípios de trabalho com a plataforma, comece lendo a [Documentação do GitHub](https://docs.github.com/en). +Você pode sugerir alterações nos artigos atuais e adicionar novos à nossa base de conhecimento usando a funcionalidade do GitHub mencionada acima. Se você não estiver familiarizado com os princípios de trabalho com a plataforma, comece lendo a [Documentação do GitHub](https://docs.github.com/en). -Quando estiver pronto para começar, trabalhe no repositório [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Tenha isso em mente ao editar ou escrever artigos. Siga [este link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) para saber mais sobre a sintaxe do Markdown. +Quando estiver pronto para começar, trabalhe no repositório [KnowledgeBase](https://github.com/AdguardTeam/KnowledgeBase). Todos os textos em nossa Base de conhecimento são escritos em linguagem de marcação `Markdown`. Tenha isso em mente ao editar ou escrever artigos. Siga [este link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) para saber mais sobre a sintaxe do Markdown. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. Ao sugerir alterações ou acréscimos, leve em consideração que todos os documentos devem obedecer aos princípios da plataforma. Você pode ler sobre eles em [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +O site da base de Conhecimento é construído usando o Docusaurus 2 — um moderno gerador de sites estáticos. Ao sugerir alterações ou acréscimos, leve em consideração que todos os documentos devem obedecer aos princípios da plataforma. Você pode ler sobre eles em [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +Você pode implantar esta Base de conhecimento localmente em seu computador para visualizar as alterações sugeridas. Instruções detalhadas sobre como fazer isso podem ser encontradas [no arquivo README](https://github.com/AdguardTeam/KnowledgeBase#readme) na página GitHub desta Base de conhecimento. ## Traduzindo artigos {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +A tradução dos artigos existentes da Base de conhecimento é realizada [na plataforma Crowdin](https://crowdin.com/profile/adguard). Todos os detalhes sobre traduções e como trabalhar com o Crowdin podem ser encontrados [no artigo dedicado](../translate/guidelines) da Base de conhecimento do bloqueador de anúncios do AdGuard. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [Em um artigo separado](../translate/plural-forms), descrevemos em detalhes as dificuldades que podem surgir ao traduzir strings com formas plurais e fornecemos instruções extensas sobre como trabalhar com elas na plataforma Crowdin. +Ao trabalhar em artigos da base de conhecimento do AdGuard, você pode encontrar strings contendo formas plurais que devem ser traduzidas com atenção extra. [Em um artigo separado](../translate/plural-forms), descrevemos em detalhes as dificuldades que podem surgir ao traduzir strings com formas plurais e fornecemos instruções extensas sobre como trabalhar com elas na plataforma Crowdin. ## Trabalhando em problemas abertos -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Escolha qualquer problema que você ache interessante e comece a trabalhar nele. Se tiver alguma dúvida, você pode perguntar diretamente nos comentários dessa edição. +Às vezes, existem [tarefas abertas](https://github.com/AdguardTeam/KnowledgeBase/issues) relacionadas à atualização da Base de conhecimento. Você pode nos ajudar a acelerar sua conclusão [da mesma forma](#suggest-change) que sugeriria qualquer outra alteração na Base de conhecimento. Escolha qualquer problema que você ache interessante e comece a trabalhar nele. Se tiver alguma dúvida, você pode perguntar diretamente nos comentários dessa edição. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 3af29562434..ea8d2bb8594 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index 1599f079fab..761fe1e699a 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 09859a87b2a..994c0c47f30 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 27a78f641f9..e16747f7cc8 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index c73790d180e..5c9d7407aed 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..121b4bb053c 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. +Neste artigo, vamos guiá-lo através do processo de recolha de registos de depuração, um passo de resolução de problemas essencial para resolver problemas complexos que possam surgir. Debug logs provide detailed insight into the inner workings of AdGuard for Android. If the AdGuard support team asks you to provide debug logs, simply follow these instructions. :::note @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index afcdf78d16d..757c2629c7f 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index e2f42e9fc9b..74ebe485538 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ Este artigo aborda o AdGuard para iOS, um bloqueador de anúncios multifuncional 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index 5283e1a5df0..7a5d428bc41 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index 01f53c4c1e3..86992f99d6c 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index af305b67447..ea5377be3f0 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 1a8f5cc4ce3..4420f677249 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index 372022c498c..7ae1aa42a57 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ Este artigo aborda o AdGuard para Windows, um bloqueador de anúncios multifunci To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 9f8142fbe5c..af8225e68c4 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 1dd6999fbf3..62ca056d607 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index ae21cfa3913..6f57b58d83b 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ Este artigo aborda o AdGuard para Windows, um bloqueador de anúncios multifunci AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 5db6a59ae46..bef91ffd5f4 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 90acaab434c..97b308f95dd 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index d44bce84515..3057c07034c 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 9c8548548cc..bf443dc87ef 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index cac4b264b0c..f4f0926000b 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ Este artigo aborda o AdGuard para Windows, um bloqueador de anúncios multifunci ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 4dcb7bf9838..972ff2ea031 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ Este artigo é sobre os filtros que criamos para usar no AdGuard e em outros sof - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 931c28c5ae2..22fc571659f 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/pt/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/pt/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/pt/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/pt/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/intro.md b/i18n/pt/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/pt/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/ro/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/ro/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/ro/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/ro/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/intro.md b/i18n/ro/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/ro/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 73da41858ea..fc9f14af3c4 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ sidebar_position: 7 ![Расширение vs. приложение \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` — в пределах ограничений браузера и только в том браузере, где расширение установлено; -`2` — the extension is unable to detect requests from other extensions. Если вредоносное или трекинговое расширение отправляет запрос на свой сервер, чтобы показать вам рекламу или отследить вашу активность, браузерное расширение AdGuard не сможет заблокировать этот запрос; +`2` — расширение не может обнаруживать запросы от других расширений. Если вредоносное или трекинговое расширение отправляет запрос на свой сервер, чтобы показать вам рекламу или отследить вашу активность, браузерное расширение AdGuard не сможет заблокировать этот запрос; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Некоторые элементы могут попасть на страницу и замедлить процесс загрузки. Приложение же, в отличие от расширения, блокирует рекламу ещё до того, как она загрузится в браузер. Это экономит трафик и ускоряет загрузку страниц. +`3` — из-за ограничений браузера расширения могут блокировать не все виды рекламы и угроз. Некоторые элементы могут попасть на страницу и замедлить процесс загрузки. Приложение же, в отличие от расширения, блокирует рекламу ещё до того, как она загрузится в браузер. Это экономит трафик и ускоряет загрузку страниц. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index f7394708b44..d4e2387f561 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ sidebar_position: 1 ## Собственные фильтры -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +По названию чаще всего можно понять, для чего нужен фильтр. Вопросы может вызвать группа _Собственные фильтры_. ![Пользовательские фильтры \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index eb03a6ec8de..00efff5dc5b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ sidebar_position: 4 На главном экране можно скрыть любой элемент на сайте вручную (это добавит новое пользовательское правило) или открыть _Журнал фильтрации_, чтобы посмотреть информацию о трафике вашего браузера. Там же можно заблокировать запросы на ходу и просмотреть отчёт о безопасности сайта. Если вы заметили пропущенную рекламу, вы можете пожаловаться на некорректную блокировку. Наши разработчики фильтров рассмотрят жалобу и исправят проблему. Там же можно посмотреть статистику по применённым правилам фильтрации. -Все запросы, сделанные браузером, отображаются в _Журнале фильтрации_ вместе с подробной информацией о каждом запросе. _Журнал фильтрации_ позволяет, например, отследить, какие запросы заблокировало расширение. В Журнале также можно заблокировать или разблокировать любой запрос в два клика. Там же можно отсортировать запросы, что может помочь, если вы создаёте свои правила фильтрации. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +Все запросы, сделанные браузером, отображаются в _Журнале фильтрации_ вместе с подробной информацией о каждом запросе. _Журнал фильтрации_ позволяет, например, отследить, какие запросы заблокировало расширение. В Журнале также можно заблокировать или разблокировать любой запрос в два клика. Там же можно отсортировать запросы, что может помочь, если вы создаёте свои правила фильтрации. _Журнал фильтрации_ можно открыть из главного меню или настроек (во вкладке «Дополнительные настройки»). Значки в правом верхнем углу главного меню отвечают за настройки расширения и приостановку защиты. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index ac5466c0ebd..ffe11cf0e30 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ sidebar_position: 3 ## Основные {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +Во вкладке _Основные_ можно разрешить поисковую рекламу их [саморекламу сайтов](/general/ad-filtering/search-ads), включить автоматическую активацию языковых фильтров, указать интервал обновления фильтров и т. д. ![Основные \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Кроме того, здесь вы можете включить [_Защиту от фишинга и вредоносных программ_](/general/browsing-security). -Вы можете сохранить конфигурацию настроек, нажав кнопку _Экспорт настроек_. Настройки будут сохранены в виде файла .json. To import the previously saved settings configuration, use the _Import settings_ function. Вы можете использовать эту функцию, чтобы быстро переключаться между различными профилями настроек или перенести конфигурацию настроек в другой браузер. +Вы можете сохранить конфигурацию настроек, нажав кнопку _Экспорт настроек_. Настройки будут сохранены в виде файла .json. Чтобы загрузить ранее сохранённую конфигурацию настроек, воспользуйтесь функцией _Импорт настроек_. Вы можете использовать эту функцию, чтобы быстро переключаться между различными профилями настроек или перенести конфигурацию настроек в другой браузер. ## Дополнительные настройки {#misc} @@ -33,6 +33,6 @@ In the _General_ tab, you can allow search ads and the [self-promotion of websit ## О программе {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +В разделе _О программе_ можно найти информацию о текущей версии, ссылки на Лицензионное соглашение и Политику конфиденциальности, а также на репозиторий браузерного расширения на GitHub. ![О программе \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 91e923e5158..00000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Ограничения - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index ffad71d2a7e..1fecaa74ec7 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Страницы, защищённые браузером -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index 44530321797..00000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -Вот и всё! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md index 04e17ad0b40..e919365705b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md @@ -53,11 +53,11 @@ sidebar_position: 1 :::note -AdGuard стремится защищать вашу конфиденциальность. Мы строго соблюдаем нашу [Политику конфиденциальности](https://adguard.com/privacy/browser-extension.html) и не собираем никакой личной информации о пользователях. Перед отправкой логов в поддержку проверьте, не содержит ли файл дополнительную информацию, которую вы не хотите передавать. Если в файле осталась личная информация, рекомендуем удалить её. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/browser-extension.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -Теперь, когда вы собрали логи, выполните следующие действия, чтобы отправить их нашей команде разработчиков: +Now that you have collected the logs, please follow these steps to submit them to our development team: -1. Сообщите об ошибке [на GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). -2. Отправьте архив с логами и временем воспроизведения на адрес `devteam@adguard.com` и прикрепите ссылку на свою задачу на GitHub. Вы также можете загрузить архив на Google Диск и добавить на него ссылку вместо прикрепления файла. +1. Report the bug on [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). +2. Send your archive with logs and playback time to `devteam@adguard.com` and add a link to your GitHub issue. You can also upload the archive to Google Drive and add the link to it instead of attaching the file. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index f7b2c15e85c..4ceb2836117 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -5,22 +5,22 @@ sidebar_position: 2 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -Модуль _Управление приложениями_ можно открыть, нажав на вкладку _Управление приложениями_ (третий значок слева в нижней части экрана). В этом разделе вы можете управлять разрешениями и настройками фильтрации для всех приложений, установленных на вашем устройстве. +The _App management_ module can be accessed by tapping the _App management_ tab (third icon from the left at the bottom of the screen). В этом разделе вы можете управлять разрешениями и настройками фильтрации для всех приложений, установленных на вашем устройстве. -![Управление приложениями \*mobile\_border](https://cdn.adtidy.org/blog/new/9sakapp_management.png) +![App management \*mobile\_border](https://cdn.adtidy.org/blog/new/9sakapp_management.png) -Нажав на приложение, вы можете управлять его настройками: +By tapping an app, you can manage its settings: - Направлять трафик через AdGuard -- Блокировать рекламу и трекеры в этом приложении (_Фильтровать трафик_) -- Фильтрация HTTPS-трафика (для приложений, не являющихся браузерами, требуется [установка сертификата CA AdGuard в системное хранилище](/adguard-for-android/solving-problems/https-certificate-for-rooted/), доступного на устройствах с root-доступом) +- Block ads and trackers in this app (_Filter app content_) +- Filter its HTTPS traffic (for non-browser apps, it requires [installing AdGuard's CA certificate into the system store](/adguard-for-android/solving-problems/https-certificate-for-rooted/), available on rooted devices) - Направлять его трафик через указанный прокси-сервер или AdGuard VPN в Режиме интеграции -![Управление приложениями в Chrome \*mobile\_border](https://cdn.adtidy.org/blog/new/nvvgochrome_management.png) +![App management in Chrome \*mobile\_border](https://cdn.adtidy.org/blog/new/nvvgochrome_management.png) Из контекстного меню вы также можете попасть в статистику приложения. @@ -28,10 +28,10 @@ sidebar_position: 2 ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. Трафик таких приложений по умолчанию направляется через AdGuard и фильтруется. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. -Некоторые приложения, такие как менеджер загрузок, радио, системные приложения с UID 1000 и 1001 (например, сервисы Google Play), являются «проблемными» и могут работать некорректно при маршрутизации через AdGuard. Поэтому вы можете увидеть следующее предупреждение при попытке перенаправить или отфильтровать все приложения: +Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. Поэтому вы можете увидеть следующее предупреждение при попытке перенаправить или отфильтровать все приложения: -![Диалоговое окно фильтрации всех приложений \*mobile\_border](https://cdn.adtidy.org/blog/new/6du8jiroute_all.png) +![Route all apps dialog \*mobile\_border](https://cdn.adtidy.org/blog/new/6du8jiroute_all.png) -Чтобы все приложения работали правильно, настоятельно рекомендуем направлять через AdGuard только непроблемные. Полный список приложений, которые не рекомендуется фильтровать, можно посмотреть в разделе _Настройки_ → _Основные_ → _Расширенные_ → _Низкоуровневые настройки_ → _Защита_ → _Исключённые приложения_. +Чтобы все приложения работали правильно, настоятельно рекомендуем направлять через AdGuard только непроблемные. You can see the full list of apps not recommended for filtering in _Settings_ → _General_ → _Advanced_ → _Low-level settings_ → _Protection_ → _Excluded apps_. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/assistant.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/assistant.md index 37f576f36da..e9897e726a1 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/assistant.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/assistant.md @@ -5,18 +5,18 @@ sidebar_position: 5 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -Помощник — удобный инструмент для быстрого изменения настроек приложения или сайта и просмотра статистики без запуска приложения AdGuard. +Assistant is a handy tool to quickly change app or website settings and view statistics without opening the AdGuard UI. ### Как получить доступ к Помощнику 1. Проведите пальцем вниз от верхней части экрана, чтобы открыть шторку уведомлений. -2. Найдите и **разверните** уведомление AdGuard. +2. Find and **expand** the AdGuard notification. -![Развернуть уведомление AdGuard в панели уведомлений \*mobile](https://cdn.adtidy.org/blog/new/jkksbhassistant-shade.png) +![Expand AdGuard notification in the notification shade \*mobile](https://cdn.adtidy.org/blog/new/jkksbhassistant-shade.png) 1. Tap _Assistant_. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/free-vs-full.mdx b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/free-vs-full.mdx index 4667873d370..8d53a98482f 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/free-vs-full.mdx +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/free-vs-full.mdx @@ -5,7 +5,7 @@ sidebar_position: 6 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/integration-with-vpn.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/integration-with-vpn.md index 675fdc953e6..d8eb522f58d 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/integration-with-vpn.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/integration-with-vpn.md @@ -5,14 +5,14 @@ sidebar_position: 8 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: AdGuard для Android создает локальный VPN для фильтрации трафика. Получается, другие VPN-приложения нельзя использовать, пока работает AdGuard для Android. However, both AdGuard and [AdGuard VPN](https://adguard-vpn.com/) apps have Integrated modes that let you use them together. -В этом режиме AdGuard VPN выступает в роли исходящего прокси-сервера, через который AdGuard направляет свой трафик. Это позволяет AdGuard создавать VPN-интерфейс и блокировать рекламу и трекеры локально, а AdGuard VPN направляет весь трафик через удалённый сервер. +In this mode, AdGuard VPN acts as an outbound proxy server through which AdGuard Ad Blocker routes its traffic. Это позволяет AdGuard создавать VPN-интерфейс и блокировать рекламу и трекеры локально, а AdGuard VPN направляет весь трафик через удалённый сервер. Если вы отключите AdGuard VPN, AdGuard перестанет использовать его в качестве исходящего прокси. Если вы отключите AdGuard, AdGuard VPN будет маршрутизировать трафик через собственный VPN-интерфейс. -If you have AdGuard Ad Blocker and install AdGuard VPN, the Ad Blocker app will detect it and enable _Integration with AdGuard VPN_ automatically. Это работает и наоборот. Обратите внимание, что при включённой интеграции вы не сможете управлять исключениями приложений и подключаться к DNS-серверам из приложения AdGuard VPN. Вы можете указать приложения, которые будут маршрутизироваться через VPN-туннель, через _Настройки_ → _Фильтрация_ → _Сеть_ → _Прокси_ → _Приложения, работающие через прокси_. Чтобы выбрать DNS-сервер, откройте AdGuard → _Защита_ → _DNS-защита_ → _DNS-сервер_. +If you have AdGuard Ad Blocker and install AdGuard VPN, the Ad Blocker app will detect it and enable _Integration with AdGuard VPN_ automatically. Это работает и наоборот. Обратите внимание, что при включённой интеграции вы не сможете управлять исключениями приложений и подключаться к DNS-серверам из приложения AdGuard VPN. You can specify apps to be routed through your VPN tunnel via _Settings_ → _Filtering_ → _Network_ → _Proxy_ → _Apps operating through proxy_. To select a DNS server, open AdGuard → _Protection_ → _DNS protection_ → _DNS server_. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/ad-blocking.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/ad-blocking.md index a3198a9b907..c5dc3a2affa 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/ad-blocking.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/ad-blocking.md @@ -5,7 +5,7 @@ sidebar_position: 1 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/annoyance-blocking.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/annoyance-blocking.md index 47ad68d96ae..f4cef61069b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/annoyance-blocking.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/annoyance-blocking.md @@ -5,12 +5,12 @@ sidebar_position: 3 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -Модуль защиты от слежения можно открыть, нажав вкладку _Защита_ (второй слева значок в нижней части экрана), а затем выбрав пункт _Блокировка раздражителей_. +The Tracking protection module can be accessed by tapping the _Protection_ tab (second-left icon at the bottom of the screen) and then selecting _Annoyance blocking_. -This feature is based on AdGuard's annoyance filters and allows you to block popups, online assistant windows, cookie notifications, prompts to download mobile apps, and similar annoyances that aren't ads but still detract from your online experience. [Узнайте больше о фильтрах раздражителей](/general/ad-filtering/adguard-filters/#adguard-filters) +This feature is based on AdGuard's annoyance filters and allows you to block popups, online assistant windows, cookie notifications, prompts to download mobile apps, and similar annoyances that aren't ads but still detract from your online experience. [Learn more about annoyance filters](/general/ad-filtering/adguard-filters/#adguard-filters) -![Блокировка раздражителей \*mobile\_border](https://cdn.adtidy.org/blog/new/lwujvannoyance.png) +![Annoyance blocking \*mobile\_border](https://cdn.adtidy.org/blog/new/lwujvannoyance.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/browsing-security.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/browsing-security.md index 27336946b81..4b250dab5fa 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/browsing-security.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/browsing-security.md @@ -1,11 +1,11 @@ --- -title: Защита от фишинга +title: Browsing security sidebar_position: 6 --- :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index ffecb69f11c..697702f6fdb 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -5,7 +5,7 @@ sidebar_position: 4 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 1af67f823ee..b79c3abd569 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -5,48 +5,48 @@ sidebar_position: 1 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -В модуле «Фаервол» можно попасть, нажав на вкладку _Защита_ (второй слева значок в нижней части экрана) и выбрав _Фаервол_. +The Firewall module can be accessed by tapping the _Protection_ tab (second-left icon at the bottom of the screen) and then selecting _Firewall_. Эта функция помогает управлять доступом в интернет для определённых приложений, установленных на вашем устройстве, и для устройства в целом. -![Фаервол \*mobile\_border](https://cdn.adtidy.org/blog/new/gdn94firewall.png) +![Firewall \*mobile\_border](https://cdn.adtidy.org/blog/new/gdn94firewall.png) ### Глобальные правила Фаервола Этот раздел позволяет контролировать доступ в интернет для всего устройства. -![Глобальные правила фаервола \*mobile\_border](https://cdn.adtidy.org/blog/new/4zx2nhglobal_rules.png) +![Global firewall rules \*mobile\_border](https://cdn.adtidy.org/blog/new/4zx2nhglobal_rules.png) Эти правила применяются ко всем приложениям на устройстве, если для них не установлены собственные правила. ### Пользовательские правила Фаервола -В этом разделе вы можете контролировать доступ в интернет для конкретных приложений — ограничить те, которые вы не считаете надёжными, или, наоборот, разблокировать те, для которых вы хотите обойти глобальные правила Фаервола. +In this section, you can control Internet access for specific apps — restrict permissions for those that you don’t find trustworthy, or, on the contrary, unblock the ones you want to circumvent the global firewall rules. -1. Откройте _Пользовательские правила Фаервола_. В разделе _Приложения с пользовательскими правилами_ нажмите _Добавить приложение_. +1. Open _Custom firewall rules_. Under _Apps with custom rules_, tap _Add app_. - ![Пользовательские правила фаервола \*mobile\_border](https://cdn.adtidy.org/blog/new/qkxpecustom_rules.png) + ![Custom firewall rules \*mobile\_border](https://cdn.adtidy.org/blog/new/qkxpecustom_rules.png) 2. Выберите приложение, для которого вы хотите установить индивидуальные правила. - ![Добавление приложения в пользовательские правила фаервола \*mobile\_border](https://cdn.adtidy.org/blog/new/2db47fadding_app.png) + ![Adding an app to Custom firewall rules \*mobile\_border](https://cdn.adtidy.org/blog/new/2db47fadding_app.png) -3. В _Доступных правилах_ выберите те, которые хотите добавить, и нажмите «+». Эти правила появятся в разделе _Применённые правила_. +3. In _Available custom rules_, select the ones you want to configure and tap the “+” icon. The rules will now appear in _Applied custom rules_. - ![Добавленное правило \*mobile\_border](https://cdn.adtidy.org/blog/new/6fzjladded_rule.png) + ![Added rule \*mobile\_border](https://cdn.adtidy.org/blog/new/6fzjladded_rule.png) -4. Если вам нужно заблокировать определённый тип соединения, переведите переключатель влево. Если вы хотите разрешить его, оставьте переключатель включённым. _Пользовательские правила_ имеют приоритет над глобальными: любые изменения в Глобальных правилах Фаервола не повлияют на это приложение. +4. Если вам нужно заблокировать определённый тип соединения, переведите переключатель влево. Если вы хотите разрешить его, оставьте переключатель включённым. **Custom rules override global ones**: any changes you make in _Global firewall rules_ will not affect this app. -Чтобы удалить правило или приложение из _Пользовательских правил_, проведите по нему влево. +To delete a rule or app from _Custom rules_, swipe it to the left. -### Уведомления +### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. Вы можете включать и выключать уведомления для всех приложений или для каждого приложения отдельно. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. -Нажмите на уведомление, чтобы получить доступ к настройкам фаераола приложения, или временно отключите все правила фаервола для этого приложения, нажав соответствующую кнопку в уведомлении. Вы также можете отключить все уведомления Фаервола для приложения, нажав кнопку _Не уведомлять_ в уведомлении для этого приложения. +Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. -Обратите внимание, что если уведомления для нескольких приложений будут отображаться, они будут объединены в одно уведомление. +Note that if notifications for multiple apps would be displayed, they will be bundled into a single notification instead. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/quick-actions.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/quick-actions.md index 5eff80c8151..c669d6000b1 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/quick-actions.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/quick-actions.md @@ -5,14 +5,14 @@ sidebar_position: 2 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -Быстрые действия можно найти в модуле _Фаервол_, доступ к которому можно получить, нажав на вкладку _Защита_ (второй слева значок в нижней части экрана), а затем выбрав _Фаервол_. +Quick actions can be found inside the _Firewall_ module, which can be accessed by tapping the _Protection_ tab (second-left icon at the bottom of the screen) and then selecting _Firewall_. -_Быстрые действия_ основаны на запросах из _Недавней активности_, которую можно найти [в _Статистике_](/adguard-for-android/features/statistics). В этом разделе показано, какие приложения недавно подключались к интернету. +_Quick actions_ are based on the requests from _Recent activity_ (which can be found in [_Statistics_](/adguard-for-android/features/statistics)). В этом разделе показано, какие приложения недавно подключались к интернету. -![Быстрые действия \*mobile\_border](https://cdn.adtidy.org/blog/new/yigrfquick_actions.png) +![Quick actions \*mobile\_border](https://cdn.adtidy.org/blog/new/yigrfquick_actions.png) -Если вы видите приложение, которое вообще не должно использовать интернет, или приложение, которое вы в последнее время не использовали, вы можете заблокировать ему доступ одной кнопкой. Это будет невозможно, если не включён модуль _Фаервол_. +Если вы видите приложение, которое вообще не должно использовать интернет, или приложение, которое вы в последнее время не использовали, вы можете заблокировать ему доступ одной кнопкой. This will not be possible unless the _Firewall_ module is turned on. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index 5e83cc4daf9..c745a990e42 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -21,60 +21,60 @@ Here are the active features of the pre-configured levels: 1. **Standard** - a. _Блокировать трекеры_. Эта функция использует фильтр «Защита от трекинга» AdGuard для защиты от онлайн-счётчиков и инструментов веб-аналитики + a. _Block trackers_. This feature uses _AdGuard Tracking Protection filter_ to protect you from online counters and web analytics tools - b. _Просить сайты не отслеживать вас_. Эта функция отправляет сигналы [Global Privacy Control](https://globalprivacycontrol.org/) и [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) на посещаемые вами сайты, запрашивая веб-приложения отключить отслеживание вашей активности + b. _Ask websites not to track you_. This feature sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity - c. _Удалять заголовок X-Client-Data_. Эта функция не даёт отправлять информацию о версии и модификации Google Chrome на домены Google (включая DoubleClick и Google Analytics) + c. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending information about its version and modifications to Google domains (including DoubleClick and Google Analytics) -2. **Высокий** +2. **High** - a. _Блокировать трекеры_. Эта функция использует фильтр «Защита от трекинга» AdGuard для защиты от онлайн-счётчиков и инструментов веб-аналитики + a. _Block trackers_. This feature uses _AdGuard Tracking Protection filter_ to protect you from online counters and web analytics tools - b. _Удалять параметры отслеживания из URL-адресов_. Эта функция использует _Фильтр отслеживания по URL_ для удаления параметров отслеживания, таких как `utm_*` и `fb_ref`, из URL-адресов страниц + b. _Remove tracking parameters from URLs_. This feature uses _AdGuard URL Tracking filter_ to remove tracking parameters, such as `utm_*` and `fb_ref`, from page URLs - c. _Скрывать поисковые запросы_. Эта функция скрывает запросы к сайтам, на которые вы пришли из поисковой системы + c. _Hide your search queries_. This feature hides queries for websites visited from a search engine - d. _Просить сайты не отслеживать вас_. Эта функция отправляет сигналы [Global Privacy Control](https://globalprivacycontrol.org/) и [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) на посещаемые вами сайты, запрашивая веб-приложения отключить отслеживание вашей активности + d. _Ask websites not to track you_. This feature sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity - е. _Самоуничтожение сторонних куки_. Эта функция ограничивает время жизни сторонних куки до 180 минут + е. _Self-destruction of third-party cookies_. This feature limits the lifetime of third-party cookies to 180 minutes :::caution - Эта функция удаляет все сторонние файлы куки после принудительного истечения их срока действия. Сюда входят ваши логины в социальных сетях или других сторонних сервисах. Возможно, вам придётся периодически повторно входить на некоторые сайты или столкнуться с другими проблемами, связанными с файлами куки. Чтобы блокировать только отслеживающие куки, используйте _Стандартный уровень защиты_. + This feature deletes all third-party cookies after their forced expiration. This includes your logins through social networks or other third-party services. You may need to re-log in to some websites periodically or experience other cookie-related issues. To block only tracking cookies, use the _Standard_ protection level. ::: - f. _Удалять заголовок X-Client-Data_. Эта функция не даёт отправлять информацию о версии и модификации Google Chrome на домены Google (включая DoubleClick и Google Analytics) + f. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) 3. **Extreme** (formerly known as _Ultimate_) - a. _Блокировать трекеры_. Эта функция использует _Фильтр счётчиков и систем аналитики_, чтобы защитить вас от онлайн-счётчиков и инструментов веб-аналитики + a. _Block trackers_. This feature uses _AdGuard Tracking Protection filter_ to protect you from online counters and web analytics tools - b. _Удалять параметры отслеживания из URL-адресов_. Эта функция использует _Фильтр отслеживания по URL_ для удаления параметров отслеживания, таких как `utm_*` и `fb_ref`, из URL-адресов страниц + b. _Remove tracking parameters from URLs_. This feature uses _AdGuard URL Tracking filter_ to remove tracking parameters, such as `utm_*` and `fb_ref`, from page URLs - c. _Скрывать поисковые запросы_. Эта функция скрывает запросы к сайтам, на которые вы пришли из поисковой системы + c. _Hide your search queries_. This feature hides queries for websites visited from a search engine - d. _Просить сайты не отслеживать вас_. Эта функция отправляет сигналы [Global Privacy Control](https://globalprivacycontrol.org/) и [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) на посещаемые вами сайты, запрашивая веб-приложения отключить отслеживание вашей активности + d. _Ask websites not to track you_. This feature sends the [Global Privacy Control](https://globalprivacycontrol.org/) and [Do Not Track](https://en.wikipedia.org/wiki/Do_Not_Track) signals to the websites you visit, asking web apps to disable tracking of your activity - е. _Самоуничтожение сторонних куки_. Эта функция ограничивает время жизни сторонних куки до 180 минут + е. _Self-destruction of third-party cookies_. This feature limits the lifetime of third-party cookies to 180 minutes :::caution - Эта функция удаляет все сторонние файлы куки после принудительного истечения их срока действия. Сюда входят ваши логины в социальных сетях или других сторонних сервисах. Возможно, вам придётся периодически повторно входить на некоторые сайты или испытывать другие проблемы, связанные с файлами куки. Чтобы блокировать только отслеживающие куки, используйте _Стандартный уровень защиты_. + This feature deletes all third-party cookies after their forced expiration. This includes your logins through social networks or other third-party services. You may need to re-log in to some websites periodically or experience other cookie-related issues. To block only tracking cookies, use the _Standard_ protection level. ::: - f. _Блокировать WebRTC_. Эта функция блокирует WebRTC — уязвимость, которая может привести к утечке вашего IP-адреса, даже если вы используете прокси или VPN + f. _Block WebRTC_. This feature blocks WebRTC, a known vulnerability that can leak your real IP address even if you use a proxy or VPN - g. _Блокировать Push API_. Эта функция не позволяет вашим браузерам получать push-сообщения от серверов + g. _Block Push API_. This feature prevents your browsers from receiving push messages from servers - h. _Блокировать Location API_. Эта функция не позволяет браузерам получать доступ к вашим данным GPS и определять ваше местоположение + h. _Block Location API_. This feature prevents browsers from accessing your GPS data and determining your location - i. _Скрывать Referer от третьих лиц_. Эта функция не позволяет третьим лицам узнать, какие сайты вы посещаете. Она скрывает HTTP-заголовок, содержащий URL-адрес начальной страницы, и заменяет его на стандартный или пользовательский, который вы можете задать + i. _Hide Referer from third parties_. This feature prevents third parties from knowing which websites you visit. It hides the HTTP header that contains the URL of the initial page and replaces it with a default or custom one that you can set - j. _Скрыть User-Agent_. Эта функция удаляет из заголовка User-Agent идентифицирующую информацию, которая обычно включает название и версию браузера, операционную систему и языковые настройки + j. _Hide your User-Agent_. This feature removes identifying information from the User-Agent header, which typically includes the name and version of the browser, the operating system, and language settings - k. _Удалять заголовок X-Client-Data_. Эта функция не даёт отправлять информацию о версии и модификации Google Chrome на домены Google (включая DoubleClick и Google Analytics) + k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -Вы можете изменить отдельные параметры в разделе _Антитрекинг_ и создать индивидуальную конфигурацию. У каждой настройки есть описание, которое поможет вам понять её роль. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 6bdfbc33ebd..0b225aaa965 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -5,12 +5,12 @@ sidebar_position: 7 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: Из-за мер безопасности ОС Android некоторые функции AdGuard доступны только на устройствах с root-доступом. Вот их список: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store -- Режим маршрутизации [**Автоматический прокси**](/adguard-for-android/features/settings#routing-mode) требует root-доступа из-за ограничений Android на фильтрацию трафика в масштабах всей системы +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Установка сертификата в системное хранилище возможна только на рутованных устройствах +- The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 4ea8bca7f04..45bd159b62b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -5,49 +5,49 @@ sidebar_position: 4 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -Вкладку _Настройки_ можно открыть, нажав на самую правую иконку в нижней части экрана. Этот раздел содержит различные настройки, информацию о приложении, лицензиях и подписках, а также о поддержке. +The _Settings_ tab can be accessed by tapping the right-most icon at the bottom of the screen. This section contains various settings, information about your app, license & subscription, and various support resources. ## Основное -Этот раздел помогает управлять внешним видом и поведением приложения: вы можете установить цветовую тему и язык, управлять уведомлениями и многое другое. Если вы хотите помочь команде AdGuard развивать приложение, можете включить опцию _Отправлять отчёты о сбоях_ и _Отправлять данные об использовании приложения_. +Этот раздел помогает управлять внешним видом и поведением приложения: вы можете установить цветовую тему и язык, управлять уведомлениями и многое другое. If you want to help the AdGuard team detect app crashes and research usability, you can enable _Auto-report crashes_ and _Send technical and interaction data_. -![Основные \*mobile\_border](https://cdn.adtidy.org/blog/new/my5quggeneral.png) +![General \*mobile\_border](https://cdn.adtidy.org/blog/new/my5quggeneral.png) -В разделе _Обновления приложения и фильтров_ вы можете настроить автоматическое обновление фильтров и выбрать канал обновления приложения. Выберите _Релиз_ для большей стабильности и _Бета_ или _Nightly_ для раннего доступа к новым функциям. +Under _App and filter updates_, you can configure automatic filter updates and select an app update channel. Choose _Release_ for more stability and _Beta_ or _Nightly_ for early access to new features. -![Обновления \*mobile\_border](https://cdn.adtidy.org/blog/new/hqm8kupdates.png) +![Updates \*mobile\_border](https://cdn.adtidy.org/blog/new/hqm8kupdates.png) ### Расширенные настройки -_Автоматизация_ позволяет управлять AdGuard через приложения-таскеры. +_Automation_ allows you to manage AdGuard via tasker apps. -_Watchdog_ помогает защитить AdGuard от отключения системой ([подробнее о режиме экономии заряда батареи Android](/adguard-for-android/solving-problems/background-work/)). Введённое значение будет интервалом в секундах между проверками Watchdog. +_Watchdog_ helps protect AdGuard from being disabled by the system ([read more about Android's battery save mode](/adguard-for-android/solving-problems/background-work/)). Введённое значение будет интервалом в секундах между проверками Watchdog. -_Уровень логирования_ определяет, какие данные о работе приложения должны записываться. По умолчанию приложение собирает данные о своих событиях. _Подробный_ уровень фиксирует больше событий. Если возникнет проблема, этот уровень поможет команде AdGuard лучше понять проблему. Но он потребляет больше ресурсов — советуем включать его только по запросу команды поддержки. [Подробнее о сборе и отправке логов](/adguard-for-android/solving-problems/log/) +_Logging level_ defines what data about the app's operation should be logged. По умолчанию приложение собирает данные о своих событиях. The _Debug_ level logs more events — enable it if asked by the AdGuard team to help them get a better understanding of the problem. [Read more about collecting and sending logs](/adguard-for-android/solving-problems/log/) -![Расширенные \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) +![Advanced \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) -Раздел _Низкоуровневые настройки_ предназначен для продвинутых пользователей. [Подробнее о низкоуровневых настройках](/adguard-for-android/solving-problems/low-level-settings/) +The _Low-level settings_ section is for expert users. [Read more about low-level settings](/adguard-for-android/solving-problems/low-level-settings/) -![Низкоуровневые настройки \*mobile\_border](https://cdn.adtidy.org/blog/new/n9ztplow_level.png) +![Low-level settings \*mobile\_border](https://cdn.adtidy.org/blog/new/n9ztplow_level.png) ## Фильтрация В этом разделе можно управлять настройками HTTPS-фильтрации, фильтрами и пользовательскими скриптами, а также настраивать прокси-сервер. -![Фильтрация \*mobile\_border](https://cdn.adtidy.org/blog/new/7v5c6filtering.png) +![Filtering \*mobile\_border](https://cdn.adtidy.org/blog/new/7v5c6filtering.png) ### Фильтры -AdGuard блокирует рекламу, трекеры и раздражители, применяя правила из своих фильтров. Большинство функций из раздела _Защита_ работают на основе [фильтров AdGuard] (/general/ad-filtering/adguard-filters/#adguard-filters). Если вы включите _Базовую защиту_, автоматически включится Базовый фильтр AdGuard и Фильтр мобильной рекламы AdGuard. И наоборот: если отключить оба фильтра, _Базовая защита_ тоже будет отключена. +AdGuard блокирует рекламу, трекеры и раздражители, применяя правила из своих фильтров. Most features from the _Protection_ section are powered by [AdGuard filters](/general/ad-filtering/adguard-filters/#adguard-filters). If you enable _Basic protection_, it will automatically turn on the AdGuard Base filter and AdGuard Mobile Ads filter. And vice versa: if you turn off both filters, _Basic protection_ will also be disabled. -![Фильтры \*mobile\_border](https://cdn.adtidy.org/blog/new/7osjdfilters.png) +![Filters \*mobile\_border](https://cdn.adtidy.org/blog/new/7osjdfilters.png) -Для нормальной работы AdGuard достаточно фильтров, включённых по умолчанию. Но если вы хотите настроить блокировку рекламы под себя, вы можете использовать другие фильтры AdGuard или сторонние фильтры. Для этого выберите категорию и включите нужные фильтры. Чтобы добавить пользовательский фильтр, нажмите _Собственные фильтры_ → _Добавить свой фильтр_ и введите его URL-адрес или путь к файлу. +Для нормальной работы AdGuard достаточно фильтров, включённых по умолчанию. Но если вы хотите настроить блокировку рекламы под себя, вы можете использовать другие фильтры AdGuard или сторонние фильтры. Для этого выберите категорию и включите нужные фильтры. To add a custom filter, tap _Custom filters_ → _Add custom filter_ and enter its URL or file path. :::note @@ -55,13 +55,13 @@ AdGuard блокирует рекламу, трекеры и раздражит ::: -[Подробнее о фильтрах](https://adguard.com/ru/blog/what-are-filters.html) +[Read more about filters](https://adguard.com/en/blog/what-are-filters.html) ### Пользовательские скрипты Пользовательские скрипты — это мини-программы, написанные на JavaScript и меняющие поведение одного или нескольких сайтов. Для установки пользовательских скриптов нужна специальная программа — менеджер скриптов. AdGuard может играть эту роль и позволяет устанавливать пользовательские скрипты по URL или из файла. -![Пользовательские скрипты \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) +![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) #### AdGuard Extra @@ -69,21 +69,21 @@ AdGuard Extra — это специальный пользовательский #### Отключить AMP -Отключить AMP — это пользовательский скрипт, который отключает [Accelerated mobile pages](https://ru.wikipedia.org/wiki/Accelerated_mobile_pages) на странице результатов поиска Google. +Disable AMP is a userscript that disables [Accelerated mobile pages](https://en.wikipedia.org/wiki/Accelerated_Mobile_Pages) on the Google search results page. ### Сеть #### HTTPS-фильтрация -Чтобы блокировать рекламу и трекеры на большинстве сайтов и в большинстве приложений, AdGuard нужно фильтровать HTTPS-трафик. [Подробнее об HTTPS-фильтрации](/general/https-filtering/what-is-https-filtering) +Чтобы блокировать рекламу и трекеры на большинстве сайтов и в большинстве приложений, AdGuard нужно фильтровать HTTPS-трафик. [Read more about HTTPS filtering](/general/https-filtering/what-is-https-filtering) ##### Сертификат безопасности Чтобы управлять зашифрованным трафиком, AdGuard устанавливает на устройство сертификат ЦС. Это безопасно: трафик фильтруется локально, а AdGuard проверяет безопасность соединения. -В старых версиях Android сертификат устанавливается автоматически. На Android 11 и выше сертификат нужно устанавливать вручную. [Инструкция по установке](/adguard-for-android/solving-problems/manual-certificate/) +В старых версиях Android сертификат устанавливается автоматически. На Android 11 и выше сертификат нужно устанавливать вручную. [Installation instructions](/adguard-for-android/solving-problems/manual-certificate/) -Сертификата в пользовательском хранилище достаточно для фильтрации HTTPS-трафика в браузерах и некоторых приложениях. Однако есть приложения, которые доверяют только сертификатам из системного хранилища. Чтобы фильтровать HTTPS-трафик подобных приложений, вам понадобится установить сертификат AdGuard в системное хранилище. [Инструкция](/adguard-for-android/solving-problems/https-certificate-for-rooted/) +Сертификата в пользовательском хранилище достаточно для фильтрации HTTPS-трафика в браузерах и некоторых приложениях. Однако есть приложения, которые доверяют только сертификатам из системного хранилища. Чтобы фильтровать HTTPS-трафик подобных приложений, вам понадобится установить сертификат AdGuard в системное хранилище. [Instructions](/adguard-for-android/solving-problems/https-certificate-for-rooted/) ##### Приложения с HTTPS-фильтрацией @@ -93,66 +93,66 @@ AdGuard Extra — это специальный пользовательский Эта настройка позволяет вам управлять сайтами, для которых AdGuard должен фильтровать HTTPS-трафик. -HTTPS-фильтрация позволяет AdGuard фильтровать содержимое запросов и ответов, но мы никогда не собираем и не храним эти данные. Однако для повышения безопасности мы [исключаем из HTTPS-фильтрации сайты, содержащие потенциально конфиденциальную информацию](/general/https-filtering/what-is-https-filtering/#financial-websites-and-websites-with-sensitive-personal-data). +HTTPS-фильтрация позволяет AdGuard фильтровать содержимое запросов и ответов, но мы никогда не собираем и не храним эти данные. However, to increase security, we [exclude websites that contain potentially sensitive information from HTTPS filtering](/general/https-filtering/what-is-https-filtering/#financial-websites-and-websites-with-sensitive-personal-data). Вы также можете добавить в исключения сайты, которые считаете необходимыми, выбрав один из режимов: - Исключить определённые сайты из HTTPS-фильтрации - Фильтровать HTTPS-трафик только на сайтах, добавленных в исключения -По умолчанию мы также не фильтруем сайты с сертификатами Extended Validation (EV), например, сайты финансовых организаций. При необходимости вы можете включить опцию _Фильтровать сайты с EV-сертификатами_. +По умолчанию мы также не фильтруем сайты с сертификатами Extended Validation (EV), например, сайты финансовых организаций. If needed, you can enable the _Filter websites with EV certificates_ option. #### Прокси -Вы можете настроить AdGuard так, чтобы он пропускал весь трафик устройства через прокси-сервер. [Как настроить исходящий прокси](/adguard-for-android/solving-problems/outbound-proxy) +Вы можете настроить AdGuard так, чтобы он пропускал весь трафик устройства через прокси-сервер. [How to set up an outbound proxy](/adguard-for-android/solving-problems/outbound-proxy) В этом разделе вы также можете настроить сторонний VPN для работы с AdGuard, ваш VPN-провайдер это позволяет. -Во вкладке _Приложения, работающие через прокси_ можно выбрать приложения, которые будут направлять свой трафик через указанный вами прокси-сервер. Если у вас включена _Интеграция с AdGuard VPN_, эта настройка заменяет функцию исключений приложений в AdGuard VPN: в Приложениях, работающих через прокси, можно указать приложения, которые будут направляться через туннель AdGuard VPN. +Under _Apps operating through proxy_, you can select apps that will route their traffic through your specified proxy. If you have _Integration with AdGuard VPN_ enabled, this setting plays the role of AdGuard VPN's app exclusions: it allows you to specify apps to be routed through the AdGuard VPN tunnel. #### Режим маршрутизации Здесь вы можете выбрать метод фильтрации трафика. -- _Локальный VPN_ фильтрует трафик через локально созданный VPN. Это самый надёжный режим. Из-за ограничений Android это также единственный способ фильтрации трафика на системном уровне, доступный на нерутованных устройствах. +- _Local VPN_ filters traffic through a locally created VPN. Это самый надёжный режим. Из-за ограничений Android это также единственный способ фильтрации трафика на системном уровне, доступный на нерутованных устройствах. :::note -Режим _Локальный VPN_ не позволяет использовать AdGuard одновременно с другими VPN. Чтобы использовать другой VPN с AdGuard, вам необходимо перенастроить его для работы в режиме прокси и настроить исходящий прокси в AdGuard. Для AdGuard VPN это делается автоматически с помощью [_Режима интегрирации_](/adguard-for-android/features/integration-with-vpn). +The _Local VPN_ mode doesn't allow AdGuard to be used simultaneously with other VPNs. Чтобы использовать другой VPN с AdGuard, вам необходимо перенастроить его для работы в режиме прокси и настроить исходящий прокси в AdGuard. For AdGuard VPN, this is done automatically with the help of the [_Integrated mode_](/adguard-for-android/features/integration-with-vpn). ::: -- _Автоматический прокси_ — альтернативный метод маршрутизации трафика, не требующий использования VPN. Одним из его существенных преимуществ является то, что его можно запускать параллельно с VPN. Этот режим требует root-доступа. +- _Automatic proxy_ is an alternative traffic routing method that does not require the use of a VPN. Одним из его существенных преимуществ является то, что его можно запускать параллельно с VPN. Этот режим требует root-доступа. -- В режиме _Ручной прокси_ настраивается порт для прокси, который затем нужно указать в настройках Wi-Fi. Для этого режима требуется root-доступ на Android 10 и выше. +- _Manual proxy_ involves setting up a proxy server on a specific port, which can then be configured in Wi-Fi settings. Для этого режима требуется root-доступ на Android 10 и выше. ## Лицензия В этом разделе вы можете узнать больше о лицензии и управлять ей: -- Купите лицензию AdGuard, чтобы активировать [функции полной версии](/adguard-for-android/features/free-vs-full) +- Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Войти в аккаунт AdGuard или ввести лицензионный ключ для активации лицензии - Зарегистрироваться для активации 7-дневного пробного периода, если вы ещё не воспользовались им -- Обновите статус лицензии в меню с тремя точками (⋮) +- Refresh the license status from the three-dots menu (:) - Открыть личный кабинет AdGuard, чтобы продлить или улучшить лицензию -- Сбросить лицензию — например, если вы достигли лимита устройств для неё и хотите применить другую +- Reset your license — for example, if you've reached device limit for this license and want to apply another one -![Экран лицензии \*mobile\_border](https://cdn.adtidy.org/blog/new/3wyh5hlicense.png) +![License screen \*mobile\_border](https://cdn.adtidy.org/blog/new/3wyh5hlicense.png) ## Поддержка -Этот раздел поможет, если у вас есть вопросы или предложения по улучшению AdGuard для Android. Мы рекомендуем ознакомиться с _[FAQ](https://adguard.com/support/adguard_for_android.html)_ или этой базой знаний, прежде чем обращаться в поддержку. +Этот раздел поможет, если у вас есть вопросы или предложения по улучшению AdGuard для Android. We recommend consulting _[FAQ](https://adguard.com/support/adguard_for_android.html)_ or this knowledge base before contacting support. -![Поддержка \*mobile\_border](https://cdn.adtidy.org/blog/new/cz55usupport.png) +![Support \*mobile\_border](https://cdn.adtidy.org/blog/new/cz55usupport.png) -Если вы заметили пропущенную рекламу, сообщите об этом в разделе _Сообщить о некорректной блокировке_. +If you notice a missed ad, please report it via _Report incorrect blocking_. -Если приложение работает некорректно, выберите _Сообщить об ошибке_. По возможности опишите проблему подробно и прикрепите логи приложения. [Как описать проблему](/guides/report-bugs/#how-to-describe-a-problem) +For unexpected app behavior, select _Report a bug_. По возможности опишите проблему подробно и прикрепите логи приложения. [How to describe an issue](/guides/report-bugs/#how-to-describe-a-problem) -Предложить улучшение можно в разделе _Предложить функцию_. +For your suggestions, use _Request a feature_. :::note -GitHub — ещё один способ сообщать об ошибках и предлагать новые функции. [Инструкции и ссылки на репозитории](/guides/report-bugs/#adguard-for-android) +GitHub — ещё один способ сообщать об ошибках и предлагать новые функции. [Instructions and repository links](/guides/report-bugs/#adguard-for-android) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/statistics.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/statistics.md index 044419a8d68..77fa0c38066 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/statistics.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/features/statistics.md @@ -5,11 +5,11 @@ sidebar_position: 3 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -Модуль _Статистика_ можно открыть, нажав на вкладку _Статистика_ (четвёртая иконка слева в нижней части экрана). Статистика помогает увидеть полную картину того, что происходит с трафиком на вашем устройстве: сколько запросов отправляется и в какие компании, сколько данных загружается и скачивается, какие запросы блокируются и многое другое. Вы можете выбрать отображение статистики за период времени: 24 часа, 7 дней, 30 дней или за всё время. +The _Statistics_ module can be accessed by tapping the _Statistics_ tab (fourth icon from the left at the bottom of the screen). Статистика помогает увидеть полную картину того, что происходит с трафиком на вашем устройстве: сколько запросов отправляется и в какие компании, сколько данных загружается и скачивается, какие запросы блокируются и многое другое. You can choose to display the statistics for the selected time period: 24 hours, 7 days, 30 days, or all time. ![Statistics \*mobile\_border](https://cdn.adtidy.org/blog/new/czy5rStatistics.jpeg?mw=1360) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md index 6867c859250..c906f40a4d1 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/installation.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: @@ -43,9 +43,9 @@ AdGuard для Android не представлен на Google Play: Google за ![Установка приложений из неизвестных источников *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/inst_4.png) - Затем вам будет предложено ознакомиться с *Лицензионным соглашением AdGuard* и *Политикой конфиденциальности*. Вы также можете помочь в разработке продукта. Для этого отметьте галочкой *Отправлять автоматические отчёты об ошибках* и *Отправлять технические данные и информацию о взаимодействиях*. Затем нажмите *Продолжить*. + You will then be asked to read AdGuard's *License agreement* and *Privacy policy*. Вы также можете помочь в разработке продукта. Для этого отметьте галочкой *Отправлять автоматические отчёты об ошибках* и *Отправлять технические данные и информацию о взаимодействиях*. Затем нажмите *Продолжить*. - ![Политика конфиденциальности *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/fl_3.png) + ![Privacy policy *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/installation/fl_3.png) 1. **Создайте локальный VPN**. Чтобы фильтровать весь трафик непосредственно на вашем устройстве, а не направлять его через удалённый сервер, AdGuard необходимо установить VPN-соединение. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index c922d2e0503..7054d47684c 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -5,11 +5,11 @@ sidebar_position: 17 :::info -В этой статье рассказывается об AdGuard для Android TV — блокировщике рекламы, который защищает ваш телевизор на системном уровне. [Скачайте приложение AdGuard для Android TV] (https://agrd.io/tvapk), чтобы увидеть, как оно работает +This article is about AdGuard for Android TV, an ad blocker that protects your TV at the system level. [Скачайте приложение AdGuard для Android TV] (https://agrd.io/tvapk), чтобы увидеть, как оно работает ::: -В большинстве случаев браузеры не могут установить файл на телевизор. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. Или использовать приложение [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader). +В большинстве случаев браузеры не могут установить файл на телевизор. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. Или использовать приложение [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader). ## Установка AdGuard для Android TV через браузер diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index e5b13fe96b9..488f129eed8 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -27,31 +27,31 @@ sidebar_position: 9 Устройства Xiaomi (и особенно MIUI) — одни из самых проблемных, когда речь идёт о фоновой работе. Известно, что они ограничивают фоновые процессы и имеют нестандартные разрешения с отсутствием надлежащей документации. Иногда приложения просто не работают на телефонах Xiaomi, и с этим мало что можно сделать. Ниже приведены некоторые действия, которые вы можете выполнить, если столкнётесь с проблемами, связанными с фоновой работой AdGuard на различных устройствах Xiaomi. -### MIUI 13+ и HyperOS +### MIUI 13+ and HyperOS -В зависимости от версий MIUI и HyperOS существует два способа изменить настройки оптимизации заряда батареи на телефоне и блокировать рекламу более эффективно. +Depending on the MIUI and HyperOS versions, there are two ways to change the battery optimization settings on your phone and block ads more efficiently. -Опция 1 +Option 1 -1. Перейдите в **Настройки** → **Приложения** → **Разрешения** → **Автозапуск в фоновом режиме** и разрешите AdGuard работать в фоновом режиме +1. Go to **Settings** → **Apps** → **Permissions** → **Background autostart** and allow AdGuard to run in the background 1. Return to **Settings** → **Apps** → **Manage apps** → **AdGuard** and uncheck **Pause app activity if unused** -1. Перейдите в раздел **Экономия заряда батареи** и нажмите **Без ограничений** +1. Go to **Battery saver** and tap **No restrictions** -Опция 2 +Option 2 1. Go to **Settings** → **Apps** → **Manage apps** → **AdGuard** and enable **Autostart** -1. Перейдите в раздел **Экономия заряда батареи** и нажмите **Без ограничений** +1. Go to **Battery saver** and tap **No restrictions** -Готово! Вы успешно настроили AdGuard для работы в фоновом режиме. +Готово! You have successfully set up AdGuard to work in the background. ### MIUI 12.0.8 Чтобы приложение AdGuard успешно работало в фоновом режиме, сделайте следующее: -В разделе **Настройки** → **Приложения** → **Управление приложениями**, прокрутите вниз до **AdGuard** и включите **Автозапуск**. +В разделе **"Настройки"** → **"Приложения"** → " **Управление приложениями** " → прокрутите вниз до **AdGuard** и включите **Автозапуск"**. ![Настройки Xiaomi *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ Huawei чрезвычайно изобретательны в оптимизац Вам также необходимо обозначить AdGuard как Исключенный из функции Энергосбережения: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**Системные настройки** → **Приложения и уведомления** → **Расширенные** → **Доступ к специальным приложениям** → **Энергосбережение** → переключите бегунок напротив AdGuard на **Исключено** ## Wiko diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 2ba22a6dffa..f10faa037a0 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -5,11 +5,11 @@ sidebar_position: 1 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. Это происходило потому, что AdGuard учитывал весь отфильтрованный трафик из разных приложений. В результате доля AdGuard в общем объёме данных и расходе батареи была завышена, а доля других приложений — занижена. +На устройствах Android с ОС 6 и более ранних встроенная статистика часто связывала высокое использование трафика и/или батареи с AdGuard. Это происходило потому, что AdGuard учитывал весь отфильтрованный трафик из разных приложений. В результате доля AdGuard в общем объёме данных и расходе батареи была завышена, а доля других приложений — занижена. Однако в Android 7 это было исправлено. Теперь информация во встроенной статистике использования данных Android очень близка к реальности, хотя в данных об использовании батареи есть небольшие расхождения. @@ -37,13 +37,13 @@ Due to built-in statistics processes, high data and/or battery consumption was o *radio.active=* 100–300мА дополнительное потребление в мАч, вызванное передачей данных по мобильной сети. - *cpu.active=* 100–200мА дополнительное потребление в мАч, вызванное н-загрузкой процессора. + *cpu.active=* 100-200mA additional consumption in mAh caused by CPU load. -1. AdGuard самостоятельно почти не потребляет трафика, так что для оценки энергопотребления отбросим значения Mobile/Wi-Fi packets и остановимся на подсчёте CPU. +1. AdGuard by itself almost doesn't consume any traffic, so for the sake of evaluating power consumption let's get rid of 'Mobile/Wi-Fi packets' and stick to 'CPU'. Формула для вычисления потребления: - > “CPU TIME (мс)" x "cpu.active" / (60 *60* 1000) = "POWER USE мАч” + > “CPU TIME (ms)” X “cpu.active” / (60 *60* 1000) = “POWER USE mAh” Подставим в эту формулу реальные значения. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 351e922f769..6964fee70a8 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -5,7 +5,7 @@ sidebar_position: 16 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: @@ -36,7 +36,7 @@ sidebar_position: 16 ### UC браузеры: UC Browser, UC Browser для x86, UC Mini, UC Browser HD -Чтобы фильтровать HTTPS-трафик, AdGuard добавляет свой сертификат в пользовательское хранилище. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +Чтобы фильтровать HTTPS-трафик, AdGuard добавляет свой сертификат в пользовательское хранилище. К сожалению, браузеры UC не доверяют пользовательским сертификатам, поэтому AdGuard не может фильтровать их HTTPS-трафик. - Чтобы решить эту проблему, переместите сертификат [в системное хранилище сертификатов](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/extending-restricted-settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/extending-restricted-settings.md index c1394249945..d98274a0489 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/extending-restricted-settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/extending-restricted-settings.md @@ -5,7 +5,7 @@ sidebar_position: 18 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index cb4f828e3e1..4aa2cbe05f9 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,11 +1,11 @@ --- -title: How to generate HAR files +title: Как получить файлы HAR sidebar_position: 5 --- :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## Что такое файлы HAR? -Формат HAR (HTTP ARchive) представляет собой файл архива в формате JSON для протоколирования взаимодействия браузера с сайтом. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. Более подробное описание формата файла HAR и его характеристик вы можете найти на сайте [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/). +Формат HAR (HTTP ARchive) представляет собой файл архива в формате JSON для протоколирования взаимодействия браузера с сайтом. Технические характеристики формата HAR определяют архивные данные для транзакций HTTP, которые используются браузером для экспорта подробной информации о загружаемых веб-страницах. Более подробное описание формата файла HAR и его характеристик вы можете найти на сайте [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/). -## How to generate HAR files +## Как получить файлы HAR -Иногда нам нужно проанализировать данные файлы, чтобы заблокировать определённые объявления, которые по какой-то причине трудно воспроизвести. To get HAR files, follow these steps: +Иногда нам нужно проанализировать данные файлы, чтобы заблокировать определённые объявления, которые по какой-то причине трудно воспроизвести. Чтобы получить файлы HAR, выполните следующие действия: 1. Откройте AdGuard и перейдите в **Настройки** (значок ⚙ в правом нижнем углу). 2. Нажмите **Общие** →**Дополнительные** → **Низкоуровневые настройки**. @@ -31,7 +31,7 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// 6. Вернитесь в раздел **Расширенные**. 7. Нажмите **Экспортировать логи и информацию о системе** → **Разрешить** (при необходимости) → **Сохранить**. -**Send the generated file with the logs to the AdGuard support service.** +**Пожалуйста, пришлите файл с логами (полученный в результате) в службу поддержки AdGuard.** :::note diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index bc67ee00872..abe7a600c99 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -5,7 +5,7 @@ sidebar_position: 14 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: @@ -29,7 +29,7 @@ AdGuard для Android может [фильтровать зашифрованн 1. Установите [последнюю версию **модуля adguardcert**](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Откройте *Magisk → Модули → Установить из хранилища* и выберите загруженный файл **adguardcert**. The AdGuard Personal CA certificate will be copied to the system store. +1. Откройте *Magisk → Модули → Установить из хранилища* и выберите загруженный файл **adguardcert**. AdGuard Personal CA будет перемещён из пользовательского хранилища в системное. ![Откройте модули Magisk *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index 215926ad7a9..b56d4553a46 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -1,31 +1,31 @@ --- -title: How to collect debug logs +title: Как получить отладочные логи AdGuard sidebar_position: 2 --- :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: :::note -Данные и/или файлы в логах обрабатываются в соответствии с [Политикой конфиденциальности AdGuard](https://adguard.com/en/privacy.html). +Data and/or files provided in logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -In this article, we'll guide you through the process of collecting debug logs, an essential troubleshooting step for solving complex issues that may potentially arise. Отладочные логи позволяют получить подробное представление о внутреннем устройстве AdGuard для Android. Если команда поддержки AdGuard попросит вас предоставить отладочные логи, просто следуйте этим инструкциям. +В этой статье мы расскажем вам о том, как собирать отладочные логи — важном этапе поиска неисправностей для решения сложных проблем, которые могут потенциально возникнуть. Отладочные логи позволяют получить подробное представление о внутреннем устройстве AdGuard для Android. Если команда поддержки AdGuard попросит вас предоставить отладочные логи, просто следуйте этим инструкциям. :::note -AdGuard стремится защищать вашу конфиденциальность. Мы строго следуем нашей [Политике конфиденциальности](https://adguard.com/privacy/android.html) и не собираем никакой личной информации о пользователях. Перед отправкой логов в поддержку проверьте, не содержит ли файл дополнительную информацию, которую вы не хотите передавать. Если в файле осталась личная информация, рекомендуем удалить её. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -### Запись отладочных логов +### Сбор отладочных логов -To collect **debug** log and send it to us, you need to perform following steps: +Чтобы собрать **отладочные** логи и отправить их нам, сделайте следующее: 1. Перейдите на страницу *Настройки* → *Основные* → *Расширенные*. 1. Выберите пункт *Уровень логирования* и установите его на *Записывать всё*. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index ecd29de3166..818691edf07 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -5,21 +5,21 @@ sidebar_position: 4 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: :::note -Данные и/или файлы в логах обрабатываются в соответствии с [Политикой конфиденциальности AdGuard](https://adguard.com/ru/privacy.html). +Data and/or files provided in logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -Иногда обычных логов может быть недостаточно, чтобы определить источник проблемы. В таких случаях необходимы системные логи. Below are instructions on how to collect and get it: via Developer options and Logcat. +Иногда обычных логов может быть недостаточно, чтобы определить источник проблемы. В таких случаях необходимы системные логи. Их можно собрать через настройки разработчика и Logcat, ниже — подробные инструкции. :::note -AdGuard стремится защищать вашу конфиденциальность. Мы строго следуем нашей [Политике конфиденциальности](https://adguard.com/ru/privacy/windows.html) и не собираем никакой личной информации о пользователях. Перед отправкой логов в поддержку проверьте, не содержит ли файл дополнительную информацию, которую вы не хотите передавать. Если в файле осталась личная информация, рекомендуем удалить её. +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 23437546f37..a431f58ec0f 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -5,7 +5,7 @@ sidebar_position: 6 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: @@ -13,7 +13,7 @@ sidebar_position: 6 :::caution -Изменение *Низкоуровневых настроек* может вызвать проблемы с производительностью AdGuard, нарушить подключение к интернету или поставить под угрозу вашу безопасность и конфиденциальность. Открывайте этот раздел, только если вы знаете, что делаете, или если вас попросила об этом наша команда поддержки. +Изменение *Низкоуровневых настроек* может вызвать проблемы с производительностью AdGuard, нарушить подключение к интернету или поставить под угрозу вашу безопасность и конфиденциальность. This section should only be opened if you know what you are doing, or you were asked to do so by our support team. ::: @@ -39,7 +39,7 @@ sidebar_position: 6 #### Bootstrap DNS-серверы -Загрузочный DNS для серверов DoH, DoT и DoQ. По умолчанию используется *Автоматический DNS* — системный DNS-сервер или AdGuard DNS. Выбирая *Пользовательский DNS*, вы можете использовать IPv4- и IPv6-адреса в качестве upstream-серверов. +Загрузочный DNS для серверов DoH, DoT и DoQ. The *Automatic DNS* — the system DNS or AdGuard DNS — is used by default. Выбирая *Пользовательский DNS*, вы можете использовать IPv4- и IPv6-адреса в качестве upstream-серверов. #### Режим блокировки для правил adblock @@ -93,19 +93,19 @@ sidebar_position: 6 Если этот параметр включён, AdGuard будет проверять upstrem-серверы DNS перед добавлением или обновлением пользовательских DNS-серверов. -#### Фильтровать зашифрованные DNS-запросы +#### Filter secure DNS -Если эта настройка включена, AdGuard применит все включённые фильтры DNS и пользовательские правила DNS к зашифрованному трафику DNS-over-HTTPS (DoH), а не только к обычному DNS. Трафик DoH в основном поступает из Chrome и других браузеров, у которых есть настройка *Secure DNS* (или аналогичная). Вы можете использовать настройку *Фильтровать безопасный DNS* в двух разных режимах: +If this setting is on, AdGuard will apply all enabled DNS filters and DNS user rules to encrypted DNS-over-HTTPS (DoH) traffic and not only to plain DNS. DoH traffic mostly comes from Chrome and other browsers that have a *Secure DNS* (or similar) setting. You can use *Filter secure DNS* in two different modes: -- **Фильтровать на лету**. В этом режиме AdGuard применяет все включённые DNS-фильтры и пользовательские правила DNS к трафику DoH, но не перенаправляет его на локальный DNS-прокси. Если в настройках браузера указан DNS-сервер, он будет обрабатывать трафик DoH для этого браузера +- **Filter on the fly**. In this mode, AdGuard applies all enabled DNS filters and DNS user rules to DoH traffic but doesn’t redirect it to the local DNS proxy. If a DNS server is specified in the browser’s settings, this server will handle the DoH traffic for this browser -- **Перенаправлять на DNS-прокси**. В этом режиме AdGuard применяет все включённые DNS-фильтры и пользовательские правила DNS к трафику DoH, перенаправляя его на локальный DNS-прокси. DNS-сервер, указанный в настройках AdGuard DNS, будет обрабатывать весь трафик DoH +- **Redirect to DNS proxy**. In this mode, AdGuard applies all enabled DNS filters and DNS user rules to DoH traffic by redirecting it to the local DNS proxy. The DNS server specified in the AdGuard’s DNS settings will handle all DoH traffic ### Фильтрация #### Записывать HAR -Если эта настройка включена, AdGuard будет перехватывать HAR-файлы. Он создаст директорию «har» в кеш-директории программы. Она будет содержать все отфильтрованные запросы в формате HAR 1.2, который может быть проанализирован программой Fiddler. +Если эта настройка включена, AdGuard будет перехватывать HAR-файлы. It will create a directory named “har” inside the app cache directory and add there information about all filtered HTTP requests in HAR 1.2 format that can be analyzed with the Fiddler program. Используйте его только для целей отладки! @@ -113,7 +113,7 @@ sidebar_position: 6 #### Encrypted Client Hello -У каждого зашифрованного интернет-соединения есть незашифрованная часть. Это самый первый пакет, который содержит имя сервера, к которому вы подключаетесь. Технология Encrypted Client Hello должна решить эту проблему и зашифровать последний бит незашифрованной информации. Чтобы воспользоваться ей, включите опцию *Использовать Encrypted Client Hello*. Она использует локальный DNS-прокси для поиска ECH-конфигурации для домена. If it is found, Client Hello packet will be encrypted. +У каждого зашифрованного интернет-соединения есть незашифрованная часть. Это самый первый пакет, который содержит имя сервера, к которому вы подключаетесь. Технология Encrypted Client Hello должна решить эту проблему и зашифровать последний бит незашифрованной информации. Чтобы воспользоваться ей, включите опцию *Использовать Encrypted Client Hello*. Она использует локальный DNS-прокси для поиска ECH-конфигурации для домена. Если она найдена, пакет ClientHello будет зашифрован. #### Проверка OCSP @@ -205,7 +205,7 @@ sidebar_position: 6 #### Включить шлюз Wi-Fi в маршруты VPN -Если этот параметр включён, IP-адреса шлюзов будут добавляться в VPN-маршруты при работе с Wi-Fi. +If this setting is enabled, the gateway IP addresses will be added to VPN routes when on Wi-Fi. #### IPv4-адрес diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index e746372f8db..edf511b4f93 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -5,22 +5,22 @@ sidebar_position: 12 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. На старых версиях Android это происходило автоматически, но на Android 11 и выше приходится устанавливать его вручную. +Чтобы [фильтровать HTTPS-трафик](/general/https-filtering/what-is-https-filtering.md) (что крайне важно, поскольку большая часть рекламы передаётся по протоколу HTTPS), AdGuard необходимо установить сертификат в пользовательское хранилище устройства. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Сертификат *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Как установить сертификат AdGuard: 1. В уведомлении *«HTTPS-фильтрация отключена»* нажмите *Включить*. 1. Появятся три экрана с объяснениями: - Зачем фильтровать HTTPS-трафик - Почему эта фильтрация безопасна - - The necessity of the AdGuard certificate + - Почему сертификат AdGuard необходим Нажмите *Далее* → *Далее* → *Сохранить сертификат*. @@ -36,7 +36,7 @@ Follow these steps to install the AdGuard certificate: Всё готово! Когда сертификат будет установлен, HTTPS-фильтрация включится автоматически. -Обратите внимание, что эти шаги описаны на основе навигации смартфона Google Pixel 7. В других устройствах Android названия настроек могут отличаться. Возможно, вам поможет ввести слово «сертификат» или «сертификат Ca» в строке поиска по настройкам. +Обратите внимание, что эти шаги описаны на основе навигации смартфона Google Pixel 7. В других устройствах Android названия настроек могут отличаться. For easier navigation consider searching for a certificate by entering “certificate” or “credentials” in the settings search bar. Если у вас возникли проблемы при ручной установке сертификата (например, вы установили сертификат, но приложение продолжает его игнорировать), вы можете воспользоваться одним из решений ниже. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md index 61ee5e4482f..56c42c8d954 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/multiple-user-profiles.md @@ -5,7 +5,7 @@ sidebar_position: 10 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: @@ -85,7 +85,7 @@ If you try to reinstall AdGuard after an unsuccessful removal attempt, you will - Откройте **Настройки**; - Нажмите **Расширенные**; - Прокрутите вниз и нажмите **Dual Messenger**; -- Отключите **Dual Messenger** для всех приложений; +- Disable the **Dual messenger** for all apps; - Заблокируйте устройство на 5 минут; - Разблокируйте экран и повторите попытку создания VPN-профиля. @@ -94,5 +94,5 @@ If you try to reinstall AdGuard after an unsuccessful removal attempt, you will - Откройте **Настройки**; - Выберите вкладку **Основные**; - Прокрутите вниз и нажмите **Dual App**; -- Удалите все приложения из списка; +- Remove all apps from the list; - Перезагрузите устройство. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index c70a5c53733..beb222556d1 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -5,11 +5,11 @@ sidebar_position: 8 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Здесь приведён список известных приложений, которые можно настроить для работы в качестве прокси-серверов в AdGuard. :::note @@ -41,11 +41,11 @@ AdGuard позволяет направлять трафик устройств | Прокси-хост | *127.0.0.1* | | Порт прокси | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Вы также можете нажать на **Прокси** → **Добавить прокси-сервер**, ввести эти значения вручную и установить Orbot в качестве прокси-сервера по умолчанию. 1. Включите основной переключатель Прокси и защиту AdGuard, чтобы направить трафик вашего устройства через прокси. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Теперь AdGuard будет перенаправлять весь трафик через Orbot. Если вы отключите Orbot, подключение к интернету будет недоступно до тех пор, пока вы не отключите настройки исходящего прокси в AdGuard. ### Как использовать AdGuard с PIA (Private Internet Access) @@ -157,4 +157,4 @@ AdGuard позволяет направлять трафик устройств ## Ограничения -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. Чтобы это исправить, откройте **Управление приложениями**, выберите нужное приложение и включите настройку **Направлять трафик через AdGuard**. +Бывает, что трафик приложения не маршрутизируется через прокси-сервер, даже если он верно настроен в AdGuard. Такое может случиться, если не настроить маршрутизацию этого приложения через AdGuard. Чтобы это исправить, откройте **Управление приложениями**, выберите нужное приложение и включите настройку **Направлять трафик через AdGuard**. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea.md index 0a7b242e295..2809e38213e 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea.md @@ -5,7 +5,7 @@ sidebar_position: 17 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/secure-folder.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/secure-folder.md index 43e1c7e845f..b8ba4565152 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/secure-folder.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/secure-folder.md @@ -5,7 +5,7 @@ sidebar_position: 13 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 0597ab8ca0b..64d3c45b904 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -41,13 +41,13 @@ sidebar_position: 3 `enable:true` или `enable:false` соответственно включает или выключает DNS-фильтрацию. -`fake_dns` allows resolving DNS requests on the specified proxy server. В поле Extra нужно добавить информацию: +`fake_dns` allows resolving DNS requests on the specified proxy server. This requires an extra flag: `enable:true` or `enable:false` enables or disables the *Use FakeDNS* setting, respectively. :::note -When the *Use FakeDNS* setting is enabled, *DNS Protection* will be automatically disabled. DNS-запросы не будут фильтроваться локально. +When the *Use FakeDNS* setting is enabled, *DNS Protection* will be automatically disabled. DNS requests won't be filtered locally. ::: @@ -65,7 +65,7 @@ When the *Use FakeDNS* setting is enabled, *DNS Protection* will be automaticall `server:custom` переключается на ранее добавленный сервер с именем `custom`; - `server:tls://dns.adguard.com` создаёт новый сервер и переключается на него, если среди ранее добавленных серверов и провайдеров нет сервера с таким же адресом. В противном случае он переключается на соответствующий сервер. Адреса серверов можно добавлять в виде IP (обычный DNS), `sdns://…` (DNSCrypt или DNS-over-HTTPS), `https://…` (DNS-over-HTTPS) или `tls://...` (DNS-over-TLS); + `server:tls://dns.adguard.com` создаёт новый сервер и переключается на него, если среди ранее добавленных серверов и провайдеров нет сервера с таким же адресом. В противном случае он переключается на соответствующий сервер. You can add server addresses as IP ( regular DNS), `sdns://…` (DNSCrypt or DNS-over-HTTPS), `https://…` (DNS-over-HTTPS) or `tls://...` (DNS-over-TLS); `server:1.1.1.1, tls://1.1.1.1` создаёт сервер с адресами через запятую и переключается на него. При добавлении сервера через `server:1.1.1.1, tls://1.1.1.1` ранее добавленный сервер удаляется. @@ -126,7 +126,7 @@ When the *Use FakeDNS* setting is enabled, *DNS Protection* will be automaticall ::: -**Don't forget to include the password, package name, and class. Это нужно делать для каждого интента.** +**Не забудьте дополнительно указать пароль, имя приложения (package) и класс. Это нужно делать для каждого интента.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -До версии 4.0 класс назывался `com.adguard.android.receivers.AutomationReceiver`, но затем мы изменили его название на `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +До версии 4.0 класс назывался `com.adguard.android.receivers.AutomationReceiver`, но затем мы изменили его название на `com.adguard.android.receiver.AutomationReceiver`. Если вы пользовались этой функцией, пожалуйста, используйте новое название. ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/youtube-ads.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/youtube-ads.md index daa2088b184..d2051987904 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/youtube-ads.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/youtube-ads.md @@ -5,7 +5,7 @@ sidebar_position: 7 :::info -В этой статье рассказывается об AdGuard для Android — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) +This article is about AdGuard for Android, a multifunctional ad blocker that protects your device at the system level. Чтобы увидеть, как он работает, [скачайте приложение AdGuard](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/adguard-and-adguard-pro.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/adguard-and-adguard-pro.md index 46de8d1ff11..d4bb6906543 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/adguard-and-adguard-pro.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/adguard-and-adguard-pro.md @@ -5,7 +5,7 @@ sidebar_position: 5 :::info -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/activity.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/activity.md index f191c3b7c9d..9dda9d378e4 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/activity.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/activity.md @@ -5,7 +5,7 @@ sidebar_position: 4 :::info -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -15,7 +15,7 @@ _Activity_ screen is the 'information hub' of AdGuard's DNS protection suite. Yo Здесь AdGuard отображает статистику DNS-запросов вашего устройства, такую как их общее количество, количество зашифрованных запросов и среднее время обработки. AdGuard может отображать статистику за день, неделю, месяц или за всё время. -Ниже есть лента _Недавняя активность_. AdGuard хранит последние 1500 DNS-запросов с вашего устройства и показывает информацию о них: например, тип протокола и домен. +Below is the _Recent activity_ feed. AdGuard хранит последние 1500 DNS-запросов с вашего устройства и показывает информацию о них: например, тип протокола и домен. :::note @@ -25,10 +25,10 @@ AdGuard никуда не отправляет эту информацию. Он Нажмите на любой запрос, чтобы просмотреть подробную информацию о нём. Внизу также будут кнопки, предлагающие добавить запрос в Белый/Чёрный список. -![Детали запроса \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/request_info_en.jpeg) +![Request details \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/request_info_en.jpeg) -Над лентой активности расположены _Наиболее активные_ и _Наиболее блокируемые_ компании. Нажмите на каждый, чтобы увидеть данные по последним 1500 запросам. +Above the activity feed, there are _Most active_ and _Most blocked_ companies. Нажмите на каждый, чтобы увидеть данные по последним 1500 запросам. -### Статистика {#statistics} +### Statistics {#statistics} -Помимо экрана _Активность_, глобальную статистику можно найти на главном экране и в виджетах. +Aside from the _Activity_ screen, you can find global statistics on the home screen and in widgets. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/advanced-protection.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/advanced-protection.md index 9b987d450d9..0abb362a7b3 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/advanced-protection.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/advanced-protection.md @@ -5,15 +5,15 @@ sidebar_position: 3 :::info -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -В iOS 15 Apple добавила поддержку веб-расширений для Safari, а мы, в свою очередь, добавили в AdGuard для iOS новый модуль _Расширенная защита_. Благодаря ему AdGuard может применять расширенные правила фильтрации, такие как CSS-правила, CSS-селекторы и скриптлеты, и тем самым способен бороться со сложной рекламой, такой как реклама на YouTube. +In iOS 15 Apple has added the support for Safari Web Extensions, and we in turn added a new _Advanced protection_ module to AdGuard for iOS. Благодаря ему AdGuard может применять расширенные правила фильтрации, такие как CSS-правила, CSS-селекторы и скриптлеты, и тем самым способен бороться со сложной рекламой, такой как реклама на YouTube. -![Экран расширенной защиты \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/protection_screen_15_en.jpeg) +![Advanced protection screen \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/protection_screen_15_en.jpeg) -### Как включить +### How to enable To enable _Advanced protection_, open the _Protection_ tab by tapping the second left icon at the bottom of the screen, select the _Advanced protection_ module, activate the feature by toggling the switch slider, and follow the on-screen instructions. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/assistant.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/assistant.md index 03643e72130..1ade2b2daa0 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/assistant.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/assistant.md @@ -5,7 +5,7 @@ sidebar_position: 5 :::info -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/compatibility-with-adguard-vpn.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/compatibility-with-adguard-vpn.md index 577e9026703..c59def9203b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/compatibility-with-adguard-vpn.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/compatibility-with-adguard-vpn.md @@ -5,28 +5,28 @@ sidebar_position: 8 :::info -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -В большинстве случаев блокировщик рекламы и VPN-приложение не могут работать вместе, просто потому что существуют определённые системные ограничения. +In most cases, an ad blocker app and a VPN app cannot work together, due to certain system limitations. -Несмотря на это, нам удалось найти решение, как «подружить» [AdGuard VPN](https://adguard-vpn.com/) и Блокировщик рекламы AdGuard. +Nevertheless, we've managed to find a solution to befriend [AdGuard VPN](https://adguard-vpn.com/) and AdGuard Ad Blocker. -В разделе _Защита_ вы можете легко переключаться между двумя приложениями. +On the _Protection_ section, you can easily switch between two apps. -### Как включить режим совместимости +### How to enable compatibility mode -**Если вы уже используете Блокировщик рекламы AdGuard и решили установить AdGuard VPN, режим совместимости включится автоматически и позволит вам одновременно использовать оба приложения AdGuard.** +**If you already have AdGuard Ad Blocker when installing AdGuard VPN, integrated (compatibility) mode will turn on automatically, allowing you to use our apps at the same time.** -Если же сначала вы установили AdGuard VPN, а уже потом решили попробовать Блокировщик AdGuard, то, чтобы пользоваться ими совместно, выполните следующие действия: +If you have installed AdGuard VPN first and only then decided to try AdGuard Ad Blocker, follow these steps to use the two apps together: -1. Откройте приложение AdGuard VPN для iOS и выберите ⚙ _Настройки_ в правом нижнем углу экрана. -2. Перейдите в _Настройки приложений_ и выберите _Режим работы_. -3. Измените режим с VPN на Интегрированный. +1. Open AdGuard VPN for iOS app and select ⚙ _Settings_ in the lower right corner of the screen. +2. Go to _App settings_ and select _Operating mode_. +3. Switch the mode from VPN to Integrated. :::note -В _Интегрированном режиме_ функции _Исключения_ и _DNS-сервер_ AdGuard VPN недоступны. +In _Integrated mode_, AdGuard VPN's _Exclusions_ and _DNS server_ features are not available. ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/dns-protection.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/dns-protection.md index a485b7f4bdc..b00a210887d 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/dns-protection.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/dns-protection.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::info -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -17,25 +17,25 @@ sidebar_position: 2 ::: -### Реализация DNS {#dns-implementation} +### DNS implementation {#dns-implementation} -![Экран реализации DNS \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/implementation_en.jpeg) +![DNS implementation screen \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/implementation_en.jpeg) В этом разделе есть две опции на выбор: AdGuard и Нативная. По сути, это два метода настройки DNS. -При выборе режима Нативной реализации DNS-запросы обрабатываются системой, а не приложением. Это означает, что AdGuard не нужно создавать локальный VPN. К сожалению, это не поможет вам обойти системные ограничения и использовать AdGuard вместе с другими приложениями на основе VPN: если включено любое VPN-приложение, нативный DNS игнорируется. Следовательно, вы не сможете фильтровать трафик локально или использовать наш новый протокол [DNS-over-QUIC (DoQ)](https://adguard.com/en/blog/dns-over-quic.html). +При выборе режима Нативной реализации DNS-запросы обрабатываются системой, а не приложением. Это означает, что AdGuard не нужно создавать локальный VPN. К сожалению, это не поможет вам обойти системные ограничения и использовать AdGuard вместе с другими приложениями на основе VPN: если включено любое VPN-приложение, нативный DNS игнорируется. Consequently, you won't be able to filter traffic locally or to use our brand new [DNS-over-QUIC protocol (DoQ)](https://adguard.com/en/blog/dns-over-quic.html). -### DNS-серверы {#dns-servers} +### DNS servers {#dns-servers} -Следующий раздел, который вы увидите на экране DNS-защиты, — это DNS-сервер. В ней показаны выбранные в данный момент DNS-сервер и тип шифрования. Нажмите на кнопку «DNS-сервер», если хотите изменить один из этих параметров (или оба). +The next section you'll see on the DNS Protection screen is DNS server. В ней показаны выбранные в данный момент DNS-сервер и тип шифрования. Нажмите на кнопку «DNS-сервер», если хотите изменить один из этих параметров (или оба). -![DNS-серверы \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/dns_server_en.jpeg) +![DNS servers \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/dns_server_en.jpeg) -Серверы отличаются скоростью, используемым протоколом, надёжностью, политикой логирования и т. д. По умолчанию AdGuard предложит несколько DNS-серверов из числа наиболее популярных (включая AdGuard DNS). Нажмите на любой из них, чтобы изменить тип шифрования (если такая опция предусмотрена владельцем сервера) или перейти на домашнюю страницу сервера. Мы добавили такие ярлыки, как `Политика «Без логов»`, `Блокировка рекламы`, `Безопасность`, чтобы помочь вам сделать выбор. +Серверы отличаются скоростью, используемым протоколом, надёжностью, политикой логирования и т. д. По умолчанию AdGuard предложит несколько DNS-серверов из числа наиболее популярных (включая AdGuard DNS). Нажмите на любой из них, чтобы изменить тип шифрования (если такая опция предусмотрена владельцем сервера) или перейти на домашнюю страницу сервера. We added labels such as `No logging policy`, `Ad blocking`, `Security` to help you make a choice. Помимо этого, в нижней части экрана есть возможность добавить пользовательский DNS-сервер. Он поддерживает обычные серверы, DNSCrypt, DNS-over-HTTPS, DNS-over-TLS и DNS-over-QUIC. -#### Базовая HTTP-аутентификация для DNS-over-HTTPS +#### HTTP basic authentication for DNS-over-HTTPS This feature brings the authentication capabilities of the HTTP protocol to DNS, which does not have built-in authentication. Authentication in DNS is useful if you want to restrict access to your custom DNS server to specific users. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 474d64ca502..00000000000 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/low-level-settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/low-level-settings.md index 2e7c0409057..7438c1940ce 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/low-level-settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/low-level-settings.md @@ -5,21 +5,21 @@ sidebar_position: 6 :::info -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -![Низкоуровневые настройки \*mobile\_border](https://cdn.adtidy.org/public/Adguard/Blog/ios_lowlevel.PNG) +![Low-level settings \*mobile\_border](https://cdn.adtidy.org/public/Adguard/Blog/ios_lowlevel.PNG) -Чтобы открыть _Низкоуровневые настройки_, перейдите в _Настройки_ → _Общие_ → (включите _Расширенный режим_, если он выключен) → _Расширенные настройки_ → _Низкоуровневые настройки_. +To open the _Low-level settings_, go to _Settings_ → _General_ → (Enable _Advanced mode_ if it's off) → _Advanced settings_ → _Low-level settings_. В основном, настройки этого раздела лучше не трогать: используйте их, только если уверены в том, что делаете, или если об этом попросила команда поддержки. Однако некоторые настройки можно изменять самостоятельно. -### Блокировать IPv6 {#blockipv6} +### Block IPv6 {#blockipv6} На любой запрос к DNS-серверу на получение IPv6-адреса наше приложение возвращает пустой ответ, как будто этого адреса не существует. Новая функция позволяет не возвращать IPv6-адреса. Её дальнейшее описание получится слишком техническим: всё-таки настройка или отключение IPv6 — это исключительная прерогатива продвинутых пользователей. Если вы один из них, то наверняка и так знаете, что это за функция, если нет — то и нет необходимости погружаться в эти детали. -### Серверы Bootstrap и Fallback {#bootstrap-fallback} +### Bootstrap and Fallback servers {#bootstrap-fallback} Fallback — это резервный DNS-сервер. Если вы выбрали DNS-сервер и с ним что-то случилось, необходим такой запасной вариант, который будет использоваться, пока не отвечает основной. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/other-features.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/other-features.md index 225d04ff83c..6c579b54aca 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/other-features.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/other-features.md @@ -5,7 +5,7 @@ sidebar_position: 7 :::info -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -37,18 +37,18 @@ AdGuard поддерживает виджеты, которые обеспечи **Advanced mode** unlocks **Advanced settings**. Мы не рекомендуем возиться с ними, если вы не уверены в том, что делаете, или не проконсультировались сначала с технической поддержкой. -### **Сбросить статистику** +### **Reset statistics** Очистит все данные статистики, такие как количество запросов и другие. -### **Сбросить настройки** +### **Reset settings** Эта опция меню сбросит все настройки. -### **Поддержка** +### **Support** Используйте эту опцию, чтобы связаться с командой поддержки, сообщить о пропущенной рекламе (хотя для вашего удобства мы рекомендуем использовать Помощник или веб-расширение AdGuard для Safari), экспортировать логи или отправить запрос на добавление функции. -### **О программе** +### **About** Содержит текущую версию приложения и набор редко используемых опций и ссылок. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/safari-protection.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/safari-protection.md index e9e94a45ba7..e5ef74f8f9f 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/safari-protection.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/features/safari-protection.md @@ -1,21 +1,21 @@ --- -title: Защита Safari +title: Safari protection sidebar_position: 1 --- :::info -В этой статье рассказывается об AdGuard для iOS — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -### Блокировщики контента {#content-blockers} +### Content blockers {#content-blockers} Блокировщики контента служат «контейнерами» для хранения правил фильтрации, которые и выполняют основную работу: блокируют рекламу и трекинг. В AdGuard для iOS шесть блокировщиков контента: General, Privacy, Social, Security, Custom и Other. До недавнего времени Apple разрешал использовать только 50 000 правил фильтрации на один блокировщик контента, а в iOS 15 верхняя граница ограничения отодвинулась на отметку 150 000 правил. -Все блокировщики контента, их статусы, используемые на данный момент фильтры и общее количество правил фильтрации можно найти на соответствующем экране в _Расширенных настройках_ (нажмите на иконку шестерёнки в правом нижнем углу → _Общие_ → _Расширенные настройки_ → _Блокировщики контента_). +All content blockers, their statuses, which thematic filters they currently include, and a total number of used filtering rules can be found on the respective screen in _Advanced settings_ (tap the gear icon at the bottom right → _General_ → _Advanced settings_ → _Content blockers_). -![Блокировщики контента \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/content_blockers_en.jpeg) +![Content blockers \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/content_blockers_en.jpeg) :::tip @@ -23,15 +23,15 @@ sidebar_position: 1 ::: -### Фильтры {#filters} +### Filters {#filters} Работа блокировщиков рекламы основана на фильтрах. Каждый фильтр — это список правил фильтрации. Когда вы пользуетесь интернетом со включённым блокировщиком рекламы, то последний постоянно проверяет посещаемые страницы и элементы на них. Всё, что соответствует каким-либо правилам фильтрации, он блокирует. Правила построены таким образом, чтобы блокировать трекеры, рекламу и многое другое. -Фильтры сгруппированы в тематические категории. Чтобы увидеть полный список категорий (не путать с блокировщиками контента), откройте раздел _Защита_, нажав на изображение щита внизу экрана, затем выберите _Защита Safari_ → _Фильтры_. +Фильтры сгруппированы в тематические категории. To see the full list of these categories (not to be confused with content blockers), open the _Protection_ section by tapping the shield icon, then go to _Safari protection_ → _Filters_. -![Группы фильтров \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/filters_group_en.jpeg) +![Filter groups \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/filters_group_en.jpeg) -Всего категорий восемь, каждая объединяет несколько фильтров, служащих общей цели. Например, они блокируют рекламу, виджеты социальных сетей, уведомления о cookie или защищают пользователя от мошенников. Чтобы вам было легче решить, какие фильтры вам подходят, читайте их описания и ориентируйтесь по меткам (`ads`, `privacy`, `recommended` и т. д.). +Всего категорий восемь, каждая объединяет несколько фильтров, служащих общей цели. Например, они блокируют рекламу, виджеты социальных сетей, уведомления о cookie или защищают пользователя от мошенников. To decide which filters suit your needs, read their descriptions and navigate by the labels (`ads`, `privacy`, `recommended`, etc.). :::note @@ -39,16 +39,16 @@ sidebar_position: 1 ::: -Категория пользовательских фильтров пуста по умолчанию, чтобы пользователи могли добавлять туда свои фильтры по URL. Вы можете найти фильтры в интернете или даже попробовать [создать свой собственный](/general/ad-filtering/create-own-filters). +Категория пользовательских фильтров пуста по умолчанию, чтобы пользователи могли добавлять туда свои фильтры по URL. You can find filters on the Internet or even try to [create one by yourself](/general/ad-filtering/create-own-filters). -### Пользовательские правила {#user-rules} +### User rules {#user-rules} -В этом разделе вы можете добавлять новые правила — либо введя их вручную, либо используя [инструмент ручной блокировки AdGuard в Safari](#assistant). Используйте пользовательские правила, чтобы настроить фильтрацию Safari без добавления целого списка фильтров. +Here you can add new rules — either by entering them manually, or by using [the AdGuard manual blocking tool in Safari](#assistant). Используйте пользовательские правила, чтобы настроить фильтрацию Safari без добавления целого списка фильтров. -Узнайте, как создавать пользовательские фильтры рекламы](/general/ad-filtering/create-own-filters). Но обратите внимание, что не все они будут работать в Safari на iOS. +Learn [how to create your own ad filters](/general/ad-filtering/create-own-filters). Но обратите внимание, что не все они будут работать в Safari на iOS. -![Экран пользовательских правил \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/user_rules_en.jpeg) +![User rules screen \*mobile\_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/features/user_rules_en.jpeg) -### Белый список {#allowlist} +### Allowlist {#allowlist} -Третий раздел на экране _Защита Safari_. Если вы хотите отключить блокировку рекламы на определённом сайте, Белый список поможет это сделать. Он позволяет добавлять домены и поддомены в список исключений. В AdGuard для iOS есть функция экспорта/импорта, благодаря которой можно переносить Белый список с одного устройства на другое. +The third section of the _Safari protection_ screen. Если вы хотите отключить блокировку рекламы на определённом сайте, Белый список поможет это сделать. It allows you to add domains and subdomains to exclusions. В AdGuard для iOS есть функция экспорта/импорта, благодаря которой можно переносить Белый список с одного устройства на другое. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 68518d099ea..a12e9d13eae 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ Requires iOS 13 or later. ![На главном экране App Store нажмите «Поиск» *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Введите *adguard* в строке поиска и нажмите на строку *adGuard*, которая будет среди результатов поиска. ![Введите "AdGuard" в строке поиска *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ Type *adguard* in the search bar and tap the string *AdGuard* which will be amon ![На главном экране App Store нажмите «Поиск» *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Введите *adguard* в строке поиска и нажмите на строку *adGuard pro - блокировщик рекламы*, которая будет среди результатов поиска. ![Введите "AdGuard" в строке поиска *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. Вам может потребоваться ввести логин и пароль Apple ID. Введите его и дождитесь завершения установки. +На открывшейся странице App Store нажмите на кнопку со стоимостью лицензии под строкой *AdGuard Pro - блокировщик рекламы*, а затем нажмите *КУПИТЬ*. Вам может потребоваться ввести логин и пароль Apple ID. Введите его и дождитесь завершения установки. ![Нажмите СКАЧАТЬ под приложением AdGuard *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index 3a3fef73b28..41dcd5d373e 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ sidebar_position: 4 1. Выберите видеоролик и нажмите *Поделиться*. 1. Нажмите *Подробнее*, затем выберите *Блокировать рекламу на YouTube (с помощью AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard откроет свой видеоплеер без рекламы. ## Как заблокировать рекламу на YouTube в Safari @@ -31,4 +31,4 @@ The video now opens in AdGuard's ad-free player. 1. Выберите видеоролик и нажмите *Поделиться*. 1. Нажмите *Блокировать рекламу на YouTube (от AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard откроет свой видеоплеер без рекламы. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index 1245f77282e..99fff955ae5 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: Как избежать проблем совместимости с FaceTime sidebar_position: 3 --- diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index e97402f29a4..991df66e403 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -13,7 +13,7 @@ sidebar_position: 5 :::caution -Изменение *Низкоуровневых настроек* может вызвать проблемы с производительностью AdGuard, нарушить подключение к интернету или поставить под угрозу вашу безопасность и конфиденциальность. Открывайте этот раздел, только если вы знаете, что делаете, или если вас попросила об этом наша команда поддержки. +Изменение *Низкоуровневых настроек* может вызвать проблемы с производительностью AdGuard, нарушить подключение к интернету или поставить под угрозу вашу безопасность и конфиденциальность. This section should only be opened if you know what you are doing, or you were asked to do so by our support team. ::: @@ -25,9 +25,9 @@ sidebar_position: 5 Существует два основных режима работы туннеля: *Split* и *Full*. *Режим Split-Tunnel* обеспечивает совместимость AdGuard c так называемыми персональными VPN-приложениями. В режиме *Full-Tunnel* никакие другие VPN не могут работать одновременно с AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. Реклама не блокируется, а трафик DNS не шифруется. +Есть особенность режима *Split-Tunnel*: если DNS-прокси работает плохо, например, когда ответ от DNS-сервера AdGuard не возвращается вовремя, iOS перенаправляет трафик через DNS-сервер, указанный в настройках iOS. Реклама не блокируется, а трафик DNS не шифруется. -В режиме *Full-Tunnel* используется только DNS-сервер, указанный в настройках AdGuard. Если он не будет отвечать, интернет просто не будет работать. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +В режиме *Full-Tunnel* используется только DNS-сервер, указанный в настройках AdGuard. Если он не будет отвечать, интернет просто не будет работать. Включенный режим *Full-Tunnel* может приводить к некорректной работе некоторых программ (например, Facetime) и вызывать проблемы с обновлением приложений. По умолчанию AdGuard использует режим *Split-Tunnel* как наиболее стабильный вариант. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/web-extension.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/web-extension.md index cfb40ba17ff..afcc1bf74f2 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/web-extension.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-ios/web-extension.md @@ -50,9 +50,9 @@ sidebar_position: 3 ![Выберите "AdGuard" в разделе РАЗРЕШИТЬ ЭТИ РАСШИРЕНИЯ *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/webext/settings3_en.png) -Tap it, then toggle the switch. На том же экране установите разрешение *Все сайты* для AdGuard на *Разрешить* или *Спрашивать*. Если вы выберете *Разрешить*, вам не придётся давать разрешение каждый раз, когда вы посещаете новый сайт. Если вы не уверены, выберите *Спрашивать*, чтобы выдавать разрешения для каждого сайта. +Tap it, then toggle the switch. On the same screen, set the *All Websites* permission for AdGuard to either *Allow* or *Ask*. If you choose *Allow*, you won't have to give permission every time you visit a new website. If you are unsure, choose *Ask* to grant permissions on a per-site basis. -![Настройки расширения *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/webext/settings4_en.png) +![Extension settings *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/iOS/webext/settings4_en.png) ### В Safari diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/browser-assistant.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/browser-assistant.md index 808394ec33f..38e296cf1eb 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/browser-assistant.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/browser-assistant.md @@ -5,37 +5,37 @@ sidebar_position: 8 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -Браузерный помощник AdGuard позволяет управлять защитой AdGuard прямо из браузера. +AdGuard Browser Assistant allows you to manage AdGuard protection directly from your browser. ![The Assistant window \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/mac/assistant_window.png) ## Как это работает -Браузерный помощник AdGuard — это расширение для браузера. Позволяет быстро управлять приложением AdGuard: +AdGuard Browser Assistant is a browser extension. It allows you to quickly manage the AdGuard app: -- Включить или отключить защиту для определённого сайта (переключатель под его названием) -- Приостановить защиту на 30 секунд -- Отключить защиту (значок паузы в правом верхнем углу) -- Блокировка рекламы вручную -- Открыть журнал фильтрации -- Сообщить о неправильной блокировке -- Открыть настройки AdGuard +- Enable or disable protection for a specific website (a toggle under the website name) +- Pause protection for 30 seconds +- Disable protection (the pause icon in the upper right corner) +- Manually block an ad +- Open the filtering log +- Report incorrect blocking +- Open AdGuard settings - View website certificate and manage HTTPS filtering (the lock icon next to the website name) ## Как установить -При установке AdGuard для Mac вам будет предложено установить Помощник для вашего браузера по умолчанию. Если вы пропустите этот шаг, вы сможете установить его позже. +When you install AdGuard for Mac, you will be prompted to install Browser Assistant for your default browser. If you skip this step, you can install it later. -**Из настроек**: +**From settings**: -1. Откройте меню AdGuard. -2. Нажмите на значок шестерёнки и выберите _Настройки_. -3. Перейдите на вкладку _Помощник_. -4. Нажмите _Добавить расширение_ рядом с вашим браузером по умолчанию. +1. Open the AdGuard menu. +2. Click the gear icon and select _Preferences_. +3. Switch to the _Assistant_ tab. +4. Click _Get the Extension_ next to your default browser. 5. Install Assistant from your browser’s extension store. ![The Assistant tab](https://cdn.adtidy.org/content/kb/ad_blocker/mac/assistant.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/dns.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/dns.md index c397f3ef2fa..8f2579dd9f8 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/dns.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/dns.md @@ -5,7 +5,7 @@ sidebar_position: 4 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/extensions.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/extensions.md index cac70b75e38..1d9abbc8e54 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/extensions.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/extensions.md @@ -5,7 +5,7 @@ sidebar_position: 8 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -20,9 +20,9 @@ Some userscripts are pre-installed, others can be installed manually. This userscript allows you to manage AdGuard protection directly from your browser. While the [new Assistant](/adguard-for-mac/features/browser-assistant) is a browser extension that can be installed from your browser’s store, the legacy Assistant is a userscript that doesn’t require additional installation. Some features are common to both assistants: - Enable or disable protection for a specific website -- Приостановить защиту на 30 секунд -- Блокировка рекламы вручную -- Сообщить о неправильной блокировке +- Pause protection for 30 seconds +- Manually block an ad +- Report incorrect blocking However, the new Assistant is more advanced. It also allows you to manage AdGuard protection for all websites, check the website’s certificate, manage HTTPS filtering, and open the filtering log or the app’s settings. We recommend that you use the legacy Assistant only if the new Assistant is not available. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/filters.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/filters.md index 4a7c2be0849..8b09c3b66f7 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/filters.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/filters.md @@ -5,7 +5,7 @@ sidebar_position: 3 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md index 440a6188f07..7c93df242d2 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -25,15 +25,15 @@ This feature prevents AdGuard from blocking [search ads and self-promotions on w ### Activate language-specific filters automatically -Эта функция определяет язык посещаемого вами сайта и автоматически активирует соответствующие фильтры для более точной блокировки рекламы. This is especially helpful if you change languages frequently. +This feature detects the language of the website you’re visiting and automatically activates appropriate filters for more accurate ad blocking. This is especially helpful if you change languages frequently. ### Launch AdGuard at login This feature automatically launches AdGuard automatically after you restart your computer. This helps keep AdGuard protection active without having to manually open the app. -### Скрыть иконку меню +### Hide menu bar icon -This feature hides AdGuard’s icon from the menu bar but keeps AdGuard running in the background. Если вы хотите полностью отключить AdGuard, нажмите _Выйти из AdGuard_ в меню главного окна. +This feature hides AdGuard’s icon from the menu bar but keeps AdGuard running in the background. If you want to disable AdGuard completely, click _Quit AdGuard_ in the main window menu. ### Белый список diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/main.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/main.md index 7d9a82409e5..cad67be1fb4 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/main.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/main.md @@ -5,7 +5,7 @@ sidebar_position: 1 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/network.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/network.md index ccd78d31fe7..f9ce26664d4 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/network.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/network.md @@ -5,32 +5,32 @@ sidebar_position: 9 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: ## Основное -![Сеть](https://cdn.adtidy.org/content/kb/ad_blocker/mac/network.png) +![Network](https://cdn.adtidy.org/content/kb/ad_blocker/mac/network.png) -### Автоматически фильтровать трафик приложений +### Automatically filter applications -By default, AdGuard blocks ads and trackers in most browsers ([Tor Browser is an exception](/adguard-for-mac/solving-problems/tor-filtering)). Эта настройка позволяет AdGuard блокировать рекламу и в приложениях. +By default, AdGuard blocks ads and trackers in most browsers ([Tor Browser is an exception](/adguard-for-mac/solving-problems/tor-filtering)). This setting allows AdGuard to block ads in apps as well. -Чтобы управлять отфильтрованными приложениями, нажмите _Приложения_. +To manage filtered apps, click _Applications_. -### Фильтровать HTTPS-протокол +### Filter HTTPS protocol -This setting allows AdGuard to filter the secure HTTPS protocol, which is currently used by most websites and apps. By default, websites with potentially sensitive information, such as banking services, are not filtered. Чтобы управлять исключениями HTTPS, нажмите _Исключения_. +This setting allows AdGuard to filter the secure HTTPS protocol, which is currently used by most websites and apps. By default, websites with potentially sensitive information, such as banking services, are not filtered. To manage HTTPS exclusions, click _Exclusions_. -По умолчанию AdGuard не фильтрует сайты с сертификатами Extended Validation (EV). При необходимости вы можете включить опцию _Фильтровать сайты с EV-сертификатами_. +By default, AdGuard doesn’t filter websites with Extended Validation (EV) certificates. If needed, you can enable the _Filter websites with EV certificates_ option. ## Исходящий прокси -Вы можете настроить AdGuard так, чтобы он пропускал весь трафик устройства через прокси-сервер. +You can set up AdGuard to route all your device’s traffic through your proxy server. -## HTTP-прокси +## HTTP proxy -Вы можете использовать AdGuard в качестве HTTP-прокси-сервера. Это позволит вам фильтровать трафик на других устройствах, подключенных к прокси-серверу. +You can use AdGuard as an HTTP proxy server. This will allow you to filter traffic on other devices connected to the proxy. -Убедитесь, что ваш Mac и другое устройство подключены к одной сети, и введите порт прокси-сервера на устройстве, которое вы хотите направить через прокси-сервер (обычно в настройках сети). Чтобы фильтровать и HTTPS-трафик, [перенесите сертификат прокси-сервера AdGuard](http://local.adguard.org/cert) на это устройство. [Узнайте больше об установке прокси-сертификата](/guides/proxy-certificate) +Make sure your Mac and your other device are connected to the same network and enter the proxy port on the device you want to route through your proxy server (usually in the network settings). To filter HTTPS traffic as well, [transfer AdGuard’s proxy certificate](http://local.adguard.org/cert) to this device. [Learn more about installing a proxy certificate](/guides/proxy-certificate) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/security.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/security.md index ea381bf43d9..6eba83ea762 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/security.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/security.md @@ -5,20 +5,20 @@ sidebar_position: 6 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: -## Защита от фишинга и вредоносных программ +## Phishing and malware protection -![Безопасность](https://cdn.adtidy.org/content/kb/ad_blocker/mac/security.png) +![Security](https://cdn.adtidy.org/content/kb/ad_blocker/mac/security.png) -У AdGuard есть база мошеннических, фишинговых и вредоносных доменов. Если вы включите функцию _Защита от фишинга и вредоносных программ_, AdGuard будет предупреждать вас каждый раз, когда вы собираетесь посетить опасный сайт. Даже если опасными являются только некоторые части сайта, AdGuard проверит их и выдаст предупреждение. +AdGuard has a database of fraudulent, phishing, and malicious domains. If you enable _Phishing and malware protection_, AdGuard will warn you every time you’re about to visit a dangerous website. Even if only some parts of the website are dangerous, AdGuard will check it and display a warning. -Это безопасно. As AdGuard checks hash prefixes, not URLs, it doesn’t know what websites you visit. [Узнайте больше о проверках безопасности AdGuard](/general/browsing-security) +This is safe. As AdGuard checks hash prefixes, not URLs, it doesn’t know what websites you visit. [Learn more about AdGuard’s security checks](/general/browsing-security) :::note -AdGuard не антивирус. Он не может предотвратить загрузку подозрительных файлов или удалить существующие вирусы. +AdGuard is not an antivirus software. It can’t stop you from downloading suspicious files or delete existing viruses. ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md index ad7a4244131..0fde0f33136 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/features/stealth.md @@ -5,12 +5,12 @@ sidebar_position: 5 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: ## Advanced privacy protection -![Защита от трекинга](https://cdn.adtidy.org/content/kb/ad_blocker/mac/stealth.png) +![Stealth Mode](https://cdn.adtidy.org/content/kb/ad_blocker/mac/stealth.png) -_Расширенная защита конфиденциальности_ защищает вас, удаляя файлы cookie, UTM-метки, онлайн-счётчики и системы аналитики. Она не позволяет сайтам собирать ваш IP-адрес, параметры устройства и браузера, поисковые запросы и личную информацию. [Узнайте больше о настройках Защиты от трекинга](/general/stealth-mode) +_Advanced privacy protection_ protects your privacy by deleting cookies, UTM tags, online counters, and analytics systems. It doesn’t let websites collect your IP address, device and browser parameters, search queries, and personal information. [Learn more about Stealth Mode settings](/general/stealth-mode) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md index 230ad3ef840..2864d1f7176 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md @@ -80,7 +80,7 @@ sidebar_position: 2 - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-pac.daemon.log (файл) - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-tun-helper.daemon.log (файл) - Для этого введите и выполните следующие команды через Терминал: + To do so, open the Terminal app, then enter and execute the following commands: ```bash sudo rm -R "/Library/Application Support/AdGuard Software/com.adguard.mac.adguard" @@ -99,7 +99,7 @@ sidebar_position: 2 ![Запустите приложение «Мониторинг системы»](https://cdn.adtidy.org/content/kb/ad_blocker/mac/22.jpg) -1. Остановите процесс, запущенный от имени пользователя. Для этого нажмите на него, а после нажмите на X в левом верхнем углу. Подтвердите действие в диалоговом окне. +1. Остановите процесс, запущенный от имени пользователя. Для этого нажмите на него, а после нажмите на X в левом верхнем углу. Confirm the action in the dialogue window. ![Подтвердите](https://cdn.adtidy.org/content/kb/ad_blocker/mac/33.jpg) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index b24240c9ef5..f99183b0a17 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -21,7 +21,7 @@ sidebar_position: 9 ## Расширенные настройки -### Настройки сети +### Network settings #### `network.extension.exclude.domains` @@ -71,7 +71,7 @@ sidebar_position: 9 #### `network.https.ech.enabled` -Использует локальный DNS-прокси для поиска конфигураций в списках конфигураций ECH. If found, encrypts Client Hellos. +Использует локальный DNS-прокси для поиска конфигураций в списках конфигураций ECH. Если такие найдены, шифрует ClientHellos. #### `network.https.enforce.certificate.transparency` @@ -89,7 +89,7 @@ sidebar_position: 9 Установив значение `true`, вы включите фильтрацию loopback-соединений. -### Настройки DNS +### DNS settings #### `dns.proxy.bootstrap.ips` @@ -159,7 +159,7 @@ sidebar_position: 9 Удаляет параметры Encrypted Client Hello из ответов. -### Настройки Защиты от трекинга +### Stealth Mode settings #### `stealth.antidpi.http.split.fragment.size` @@ -177,7 +177,7 @@ sidebar_position: 9 Здесь можно указать задержку (в миллисекундах) после отправки первого фрагмента, если выполняется фрагментация. -### Настройки перехвата ссылок на подписку (пользовательские скрипты и фильтры) +### Subscription link interception settings (userscripts and filters) #### `subscription.link.interception.userscript` diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 3a33de1bc6b..344b0700af4 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ AdGuard не будет работать вместе с Cisco AnyConnect, ес #### VPN-приложения со старым API -Несмотря на то, что AdGuard отображается в системных настройках как VPN, конфликтов с другими приложениями на основе VPN возникнуть не должно. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Несмотря на то, что AdGuard отображается в системных настройках как VPN, конфликтов с другими приложениями на основе VPN возникнуть не должно. Но если вы используете VPN-приложение, скачанное не из App Store, есть шанс, что оно использует старое VPN API. В таком случае необходимо исключить его из фильтрации: 1. Откройте меню AdGuard. 1. Выберите *Настройки...*. @@ -79,9 +79,9 @@ AdGuard не будет работать вместе с Cisco AnyConnect, ес ### Совместимость с Little Snitch 5 -На момент написания статьи режим фильтрации «Сетевое расширение» в AdGuard не совместим с [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. Эта проблема вызвана багом в Big Sur, о котором мы уже проинформировали Apple. Это позволяет надеяться, что в ближайших обновлениях он будет исправлен. +На момент написания статьи режим фильтрации «Сетевое расширение» в AdGuard не совместим с [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). Когда они оба запущены, существует вероятность столкнуться с проблемами в поведении различных приложений, даже если они исключены из фильтрации в AdGuard. Эта проблема вызвана багом в Big Sur, о котором мы уже проинформировали Apple. Это позволяет надеяться, что в ближайших обновлениях он будет исправлен. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. Мы рекомендуем использовать режим фильтрации [**Автоматический прокси**](#automatic-proxy), если вы запускаете AdGuard на одном устройстве с Little Snitch под Big Sur, во всяком случае до тех пор, пока Apple не исправит данную проблему совместимости. +Проблему нельзя решить отключением мониторинга соединений в Little Snitch, поскольку это не выгружает его расширение из системы. Мы рекомендуем использовать режим фильтрации [**Автоматический прокси**](#automatic-proxy), если вы запускаете AdGuard на одном устройстве с Little Snitch под Big Sur, во всяком случае до тех пор, пока Apple не исправит данную проблему совместимости. ### Совместимость с локальными прокси @@ -93,7 +93,7 @@ However, disabling connection monitoring in Little Snitch doesn't solve the issu Чтобы настроить восходящий прокси-сервер в AdGuard for Mac в Big Sur: -1. Откройте настройки AdGuard *Настройки → Сеть → Исходящий прокси*. +1. Open AdGuard's settings *Preferences → Network → Outbound proxy*. 2. Выберите HTTP, HTTPS, SOCKS4 или SOCKS5 в зависимости от типа прокси-сервера. 3. Заполните поля: - `host` — IP-адрес вашего прокси-сервера, @@ -121,7 +121,7 @@ However, disabling connection monitoring in Little Snitch doesn't solve the issu :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +Подробнее почитать о том, как начать работать с Shadowsocks, можно [на их сайте](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index 6ced212ec4b..a714301c720 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ sidebar_position: 3 ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". Это новый механизм защиты, появившийся в High Sierra, он требует от вас явно разрешить установку сторонних расширений. Чтобы завершить установку AdGuard, вам нужно вручную разрешить установку расширений: перейдите в *Системные настройки* → *Защита и безопасность* → *Основные*. +Во время установки AdGuard на macOS High Sierra (или более поздние версии) вы можете увидеть такое сообщение: «Системное расширение заблокировано». Это новый механизм защиты, появившийся в High Sierra, он требует от вас явно разрешить установку сторонних расширений. Чтобы завершить установку AdGuard, вам нужно вручную разрешить установку расширений: перейдите в *Системные настройки* → *Защита и безопасность* → *Основные*. ![Разрешить установку расширений в настройках](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md index 81db5073a9e..c46edcd7c96 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md @@ -13,16 +13,16 @@ AdGuard для Mac должен установить корневой серти Чтобы установить сертификат вручную: - 1. Откройте *Настройки* + 1. Open *Preferences* - 2. Перейдите в *Приватность и Защита* — *Просмотр сертификатов* + 2. Go to *Privacy & Security* → *Certificates* - 3. Кликните по *Просмотр сертификатов* + 3. Click *View Certificates* - 4. Перейдите во вкладку *Центры сертификации* и кликните по кнопке *Импортировать...* + 4. Navigate to the *Authorities* tab and click the *Import...* button 5. Выберите файл `/Library/Application Support/com.adguard.mac.adguard/AdguardCore/Adguard Personal CA.cer` или скачайте его c http://local.adguard.org/cert через любой браузер на основе Chromium (например, Google Chrome или Edge) с запущенной HTTPS-фильтрацией в AdGuard Точные действия могут различаться для разных браузеров, но общая последовательность и путь к файлу `AdGuard Personal CA.cer` остаются теми же. -P.S.: Для [версии приложении в Setapp](https://setapp.com/apps/adguard) путь файла будет такой: `/Library/Application Support/com.adguard.mac.adguard-setapp/AdguardCore/Adguard Personal CA.cer` +P.S.: For [Setapp application version](https://setapp.com/apps/adguard) the file path is the following: `/Library/Application Support/com.adguard.mac.adguard-setapp/AdguardCore/Adguard Personal CA.cer` diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md index 97a03c70bbd..9f2e188a94f 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md @@ -11,7 +11,7 @@ sidebar_position: 2 Если по каким-либо причинам не удаётся включить защиту AdGuard, выполните следующие действия: -1. Нажмите на иконку AdGuard в строке меню, откройте настройки → *Дополнительно* → *Сбросить настройки...* → *Завершить AdGuard...* +1. Click the AdGuard icon at the menu bar and go to *Advanced* → *Reset settings...* → *Quit AdGuard...* 2. В поиске Spotlight введите Терминал, введите `sudo rm -R /Library/Application\ Support/com.adguard.adguard` и выполните команду. @@ -19,4 +19,4 @@ sidebar_position: 2 4. В Терминале проверьте, что папка стёрлась, выполнив команду: `ls -al /Library/StagedExtensions/Library/Application\ Support/com.adguard.Adguard/`. Вы должны увидеть следующее сообщение: `No such file or directory`. -5. Запустите AdGuard и введите данные для входа. +5. Start AdGuard and enter your login information when prompted. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md index 5a91fce3407..cbcc712027a 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md @@ -5,7 +5,7 @@ sidebar_position: 11 :::info -В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Mac — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 548c2ae3c5e..3969b5436f7 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ sidebar_position: 5 :::note Напоминание -AdGuard для Safari можно бесплатно загрузить [из App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard для Safari можно бесплатно загрузить [из App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). Подробная инструкция по установке — в нашей [Базе знаний](/adguard-for-safari/installation/). ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index 6affc6e7053..e3ddd03f9d9 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: Пользовательские правила sidebar_position: 4 --- -Пользовательские правила можно использовать, чтобы настроить блокировку под себя. Их можно добавить вручную или импортировать. Когда вы блокируете элемент на странице, они создаются автоматически. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +Пользовательские правила можно использовать, чтобы настроить блокировку под себя. Их можно добавить вручную или импортировать. Когда вы блокируете элемент на странице, они создаются автоматически. Чтобы добавить собственные правила фильтрации, используйте [специальный синтаксис](/general/ad-filtering/create-own-filters). diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index 9c8cad7a6e3..58b05f557a8 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -1,5 +1,5 @@ --- -title: How to collect logs in AdGuard for Safari +title: Как собирать логи в AdGuard для Safari sidebar_position: 4 --- @@ -9,9 +9,9 @@ sidebar_position: 4 ::: -Для анализа и диагностики различных проблем, которые могут возникнуть с AdGuard для Safari, команде поддержки AdGuard могут понадобиться лог-файлы. В этих файлах содержатся записи об ошибках и других программных событиях. Below are brief instructions on how to collect logs and send them to support if necessary. +Для анализа и диагностики различных проблем, которые могут возникнуть с AdGuard для Safari, команде поддержки AdGuard могут понадобиться лог-файлы. В этих файлах содержатся записи об ошибках и других программных событиях. Ниже приведена краткая инструкция о том, как собирать логи и отправлять их в поддержку. -### How to collect logs +### Как собирать логи 1. Откройте приложение AdGuard для Safari. 2. Прокрутите вниз и нажмите _Экспортировать логи_. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 7639e81f27c..5a8cb33245c 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -39,7 +39,7 @@ AdGuard подключается к двум хостам: `api.adguard.org` и :::note -If you have installed AdGuard for Windows from an MSI file, AdGuard will not be updated automatically. Чтобы разрешить обновления вручную: +If you have installed AdGuard for Windows from an MSI file, AdGuard will not be updated automatically. To allow manual updates: - In versions released after v7.16, delete the `ForbidCheckUpdates` parameter or set its value to `NO` (case-insensitive) in the registry under `HKEY_LOCAL_MACHINE\SOFTWARE\Adguard`. @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Протестируйте установку {#installation-test} -Запустите AdGuard на целевой машине. Open the license screen to check that it is using the specified license. Возможно, вам придётся кликнуть по кнопке «Обновить статус», чтобы AdGuard проверил лицензионный ключ. +Запустите AdGuard на целевой машине. Откройте экран лицензии, чтобы проверить, что используется установленная вами лицензия. Возможно, вам придётся кликнуть по кнопке «Обновить статус», чтобы AdGuard проверил лицензионный ключ. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 3842090c004..63253002ee8 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ sidebar_position: 3 В предыдущих версиях Браузерного расширения AdGuard (до версии 3.5), если оно было установлено вместе с AdGuard для Windows, расширение брало на себя функции Помощника, прекращало фильтровать самостоятельно и полагалось на приложение. -Расширение и приложение работали вместе, но иногда интеграция давала сбой. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +Расширение и приложение работали вместе, но иногда интеграция давала сбой. Приложение прекращало фильтровать некоторые сайты, вместо него это делало расширение, обладающее заметно меньшими возможностями. При использовании Браузерного помощника все эти проблемы не имеют значения, поскольку конфликтов по сути быть не может. Роль Браузерного помощника чётко определена, и он не может помешать работе основного приложения, так что не о чем беспокоиться. @@ -42,4 +42,4 @@ The new Browser Assistant has its own tab in AdGuard for Windows settings, along Если вы хотите установить Браузерный Помощник для своего браузера по умолчанию, вы можете сделать это прямо из настроек приложения. Однако у вас также есть возможность установить его для других браузеров. -Браузерный помощник AdGuard доступен для всех популярных браузеров: Chrome, Firefox, Edge, Opera и Яндекс. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. Вот и всё! +Браузерный помощник AdGuard доступен для всех популярных браузеров: Chrome, Firefox, Edge, Opera и Яндекс. Чтобы установить Помощник для нужного браузера (или несколько, это не запрещено, а даже приветствуется), перейдите на [наш сайт](https://adguard.com/adguard-assistant/overview.html), кликните на иконку браузера и нажмите кнопку *Скачать*. Вот и всё! diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index aa19b37b276..e01e42e4975 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -5,7 +5,7 @@ sidebar_position: 3 :::info -В этой статье рассказывается об AdGuard для Windows — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Windows — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a Это пользовательское расширение, предназначенное для борьбы с повторной вставкой заблокированной рекламы — так называемым обходом блокировщика рекламы. Это передовые методы защиты от блокировки рекламы, которые пользуются популярностью среди рекламодателей. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -Это расширение блокирует всплывающие окна при просмотре веб-страниц. Некоторые всплывающие окна считаются полезными — они могут содержать настройки для администрирования сайта или справочную информацию, отображаемую при переходе по ссылке. Вот почему вы можете отключить Блокировщик, если это необходимо. Это расширение также не работает на сайтах, добавленных в список исключений AdGuard. По умолчанию это расширение отключено, но вы можете включить его в настройках приложения. You will find more detailed information about this extension in our Knowledge Base. +Это расширение блокирует всплывающие окна при просмотре веб-страниц. Некоторые всплывающие окна считаются полезными — они могут содержать настройки для администрирования сайта или справочную информацию, отображаемую при переходе по ссылке. Вот почему вы можете отключить Блокировщик, если это необходимо. Это расширение также не работает на сайтах, добавленных в список исключений AdGuard. По умолчанию это расширение отключено, но вы можете включить его в настройках приложения. Вы найдёте более подробную информацию об этом расширении в нашей Базе знаний. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust показывает вам репутацию каждого са ### Сеть -Предпоследний модуль посвящён сетевой фильтрации, и здесь вы найдёте дополнительные параметры, связанные с сетью. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Это важная дополнительная мера предосторожности для лучшей фильтрации веб-пространства. Большинство сайтов теперь используют HTTPS, то же самое относится и к рекламным сетям. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +Предпоследний модуль посвящён сетевой фильтрации, и здесь вы найдёте дополнительные параметры, связанные с сетью. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. Это важная дополнительная мера предосторожности для лучшей фильтрации веб-пространства. Большинство сайтов теперь используют HTTPS, то же самое относится и к рекламным сетям. Со многих сайтов, таких как youtube.com, facebook.com и twitter.com, невозможно удалить рекламу без HTTPS-фильтрации. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md index 2a663824c7f..3e85f90b8ae 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/home-screen.md @@ -5,7 +5,7 @@ sidebar_position: 1 :::info -В этой статье рассказывается об AdGuard для Windows — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Windows — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md index 51c8a9cb017..1a5f3521524 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/others.md @@ -5,7 +5,7 @@ sidebar_position: 4 :::info -В этой статье рассказывается об AdGuard для Windows — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Windows — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -13,13 +13,13 @@ sidebar_position: 4 ### Поддержка -![Поддержка \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/support.png) +![Support \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/support.png) Нажав на вкладку «Поддержка», вы откроете диалоговое окно, в котором можете сообщить об ошибке, отправить запрос на добавление функции или просто поделиться своим мнением о продукте. ### Лицензия -![Лицензия \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/license.png) +![License \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/license.png) Эта вкладка содержит информацию о лицензии. Здесь вы можете: @@ -28,13 +28,13 @@ sidebar_position: 4 ### О компании -![О программе \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/about.png) +![About \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/about.png) In addition to information about the current version of the program, this tab provides some useful links to Licese agreement, Privacy policy, Acknowledgements, Discussions, and Version history pages. ### Проверить обновления -![Проверка обновлений \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/check-updates.png) +![Check for updates \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/check-updates.png) Чтобы проверить наличие обновлений фильтров и пользовательских скриптов, нажмите на значок вращающихся стрелок в правом верхнем углу главного экрана приложения. @@ -45,7 +45,7 @@ In addition to information about the current version of the program, this tab pr - включить защиту - отключить защиту: полностью или на 30 секунд - go to _Settings_ -- откройте меню _Инструменты_ и _Дополнительно_ +- open the _Tools_ and _Advanced_ menus - проверить обновления фильтров - проверить обновления приложения - вспомнить последнее всплывающее сообщение diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 5ccfb54f296..9edc8a98ae5 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -5,7 +5,7 @@ sidebar_position: 2 :::info -В этой статье рассказывается об AdGuard для Windows — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. [Скачайте приложение AdGuard](https://agrd.io/download-kb-adblock), чтобы увидеть, как оно работает +В этой статье рассказывается об AdGuard для Windows — многофункциональном блокировщике рекламы, который защищает ваше устройство на системном уровне. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) ::: @@ -50,7 +50,7 @@ Before you start manually writing your own rules read our detailed [syntax guide To learn everything about Stealth Mode and its many options, [read this article](/general/stealth-mode). -### Защита от фишинга +### Browsing security Browsing security gives strong protection against malicious and phishing websites. Нет, AdGuard для Windows — это не антивирус. Он не остановит загрузку вируса, если она уже началась, и не удалит уже существующие вирусы. Но он предупредит вас, если вы собираетесь перейти на сайт, домен которого был добавлен в нашу базу «ненадёжных сайтов», или загрузить файл с такого сайта. You can find more information about how this module works in the [dedicated article](/general/browsing-security). @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b Модуль проверяет содержимое веб-страниц, открытых в браузере, и отфильтровывает страницы с нежелательным для детей контентом: изображения и тексты для взрослых, ненормативная лексика, насилие, пропаганда наркотиков и т. д. Настройки Родительского контроля защищены паролем, чтобы ребёнок не смог обойти ограничения. Этот модуль не только блокирует доступ к нежелательным сайтам, но и удаляет неподходящие для детей ссылки из результатов поиска. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index 1d9a16a1efe..54aa3e534d7 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ sidebar_position: 2 Чтобы использовать программу AdGuard на компьютере или планшете под управлением Microsoft Windows, загрузите установочный пакет этого приложения и запустите программу установки. Для этого выполните перечисленные ниже действия: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Перейдите на [сайт AdGuard](http://adguard.com) и нажмите *Скачать* [на открывшейся странице](https://adguard.com/download.html?auto=1). ![Скачайте AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ sidebar_position: 2 ::: -- Выберите *Блокировщик рекламы AdGuard* и *Расширенный* тип удаления, затем нажмите *Удалить*. В появившемся окне нажмите *Да, продолжить*. +- Выберите *Блокировщик рекламы AdGuard* и *Расширенный* тип удаления, затем нажмите *Удалить*. Clcik *Yes, continue* in the window prompt. ![Расширенное удаление *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 15d8e61b990..5d1306f7a91 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard logs +title: Как получить логи AdGuard sidebar_position: 3 --- @@ -11,11 +11,11 @@ sidebar_position: 3 :::note -Данные и/или файлы в логах обрабатываются в соответствии с [Политикой конфиденциальности AdGuard](https://adguard.com/en/privacy.html). +Data and/or files provided in logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: -Для анализа и диагностики различных проблем службе поддержки могут понадобиться файлы журнала AdGuard. These files contain records about errors and other events that occur with the software. Ниже представлена краткая инструкция, описывающая как получить и отправить в службу поддержки файлы журнала. +Для анализа и диагностики различных проблем службе поддержки могут понадобиться файлы журнала AdGuard. Эти файлы содержат записи обо всех ошибках, которые произошли с программой за последнее время. Ниже представлена краткая инструкция, описывающая как получить и отправить в службу поддержки файлы журнала. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Откройте настройки AdGuard. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Откройте настройки AdGuard. Перейдите в раздел *Общие настройки*, прокрутите вниз до конца экрана и выберите *Уровень логирования* *Подробный*. ![Подробный уровень логирования *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Мы настоятельно рекомендуем записывать точное время, когда вы воспроизвели проблему: это поможет нашей команде поддержки найти соответствующие логи и решить проблему быстрее. -1. Export the collected logs using the *Export Logs* button. +1. Экспортируйте полученные логи при помощи кнопки *Экспортировать логи*. ![Экспортировать логи *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Сохраните архив в любую папку. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Подробный* уровень логирования может значительно замедлить работу приложения. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Подробный* уровень логирования может значительно замедлить работу приложения. 1. Отправьте сохранённый архив в службу поддержки AdGuard по адресу **support@adguard.com**, опишите проблему и не забудьте указать время, когда вы воспроизвели проблему. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th Мы настоятельно рекомендуем записывать точное время, когда вы воспроизвели проблему: это поможет нашей команде поддержки найти соответствующие логи и решить проблему быстрее. -1. Export the collected logs using the *Export Logs* button. +1. Экспортируйте полученные логи при помощи кнопки *Экспортировать логи*. ![Экспортировать логи *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 55801212d7d..7a20413d7e5 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ sidebar_position: 6 ### Ошибка 5: Отказано в доступе {#error-5} -This error message appears when required permissions haven't been granted. Почему у установщика AdGuard нет разрешения, которое требуется для завершения установки, может объясняться рядом причин. Выполните следующие действия: +Эта ошибка возникает, когда что-то не в порядке с разрешением на доступ. Почему у установщика AdGuard нет разрешения, которое требуется для завершения установки, может объясняться рядом причин. Выполните следующие действия: -- Temporarily disable your antivirus. Некоторые из них могут мешать установке, это зависит от степени жёсткости ваших настроек. +- Временно отключите антивирусы. Некоторые из них могут мешать установке, это зависит от степени жёсткости ваших настроек. - Выберите другую папку установки. Возможно, что у текущей папки есть ограничения доступа. Также удостоверьтесь, что не выбрали внешний или виртуальный жёсткий диск. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. По ### Ошибка 112: Недостаточно места на диске, Ошибка 1632: Временная папка переполнена или к ней нет доступа {#error-112} -Две разные ошибки с очень похожими решениями. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. Вот что вы можете попробовать, чтобы устранить проблему: +Две разные ошибки с очень похожими решениями. Как видно из названия, в обоих случаях установщик AdGuard не нашёл достаточно места, чтобы завершить процесс. Вот что вы можете попробовать, чтобы устранить проблему: - Удалите некоторые программы или ненужные файлы с вашего диска, на который вы пытались установить AdGuard. -- Загрузите, установите и запустите [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), бесплатный инструмент от Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. Это освободит место на диске. +- Загрузите, установите и запустите [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), бесплатный инструмент от Malwarebytes. Помимо прочего, он очистит вашу систему от файлов, оставшихся после неправильно удалённых программ. Это освободит место на диске. - Перезагрузите компьютер. Иногда временные файлы могут занимать много места на диске, и перезагрузка компьютера — самый надёжный способ избавиться от них. ### Ошибка 1601: Нет доступа к службе установки Windows {#error-1601} -You could say this is a particular subcategory of Error 1603. Возможные решения аналогичны: +Можно сказать, что это частный случай Ошибки 1603. Возможные решения аналогичны: - Запустите и пройдите перерегистрацию службы установщика Microsoft. На это потребуется некоторое время. @@ -67,7 +67,7 @@ You could say this is a particular subcategory of Error 1603. Возможные - Получите полный доступ к диску для установки. Возможно, что ошибка 1603 возникает, если у вас нет полного доступа к местоположению файла. Это решение также требует некоторой работы: - 1) Откройте *Проводник*, щёлкните правой кнопкой мыши диск, содержащий место установки, и выберите *Свойства*. 2) Перейдите на вкладку *Безопасность* и нажмите на *Редактировать*. 3) Один раз щёлкните по разделу *СИСТЕМА* и убедитесь, что для каждого элемента в *Разрешения для СИСТЕМЫ* установлен флажок *Разрешить* (если он есть). Проверьте то же самое для вкладки *Администраторы*. 4) Нажмите на *OK*, чтобы вернуться к окну *Свойства*. Затем нажмите *Расширенные*. 5) Выберите *Изменить разрешения*. 6) Во вкладке *Разрешения* дважды щёлкните *Администраторы*. 7) Выберите *Эта папка, подпапки и файлы* для поля *Применяется к* и отметьте все доступные *Основные разрешения*. After that, hit *OK*. 8) Повторите операцию из пункта 7 для *СИСТЕМА*. 9) Нажимайте *OK* до конца. Попробуйте установить AdGuard заново. + 1) Откройте *Проводник*, щёлкните правой кнопкой мыши диск, содержащий место установки, и выберите *Свойства*. 2) Перейдите на вкладку *Безопасность* и нажмите на *Редактировать*. 3) Один раз щёлкните по разделу *СИСТЕМА* и убедитесь, что для каждого элемента в *Разрешения для СИСТЕМЫ* установлен флажок *Разрешить* (если он есть). Проверьте то же самое для вкладки *Администраторы*. 4) Нажмите на *OK*, чтобы вернуться к окну *Свойства*. Затем нажмите *Расширенные*. 5) Выберите *Изменить разрешения*. 6) Во вкладке *Разрешения* дважды щёлкните *Администраторы*. 7) Select *This folder, subfolders and files* for *Applies to* field and check all the available *Basic permissions*. After that, hit *OK*. 8) Повторите операцию из пункта 7 для *СИСТЕМА*. 9) Нажимайте *OK* до конца. Попробуйте установить AdGuard заново. ### Ошибка 1618: Уже выполняется другая установка {#error-1618} @@ -75,7 +75,7 @@ You could say this is a particular subcategory of Error 1603. Возможные - Перезагрузите компьютер и запустите установщик заново. Когда вы сделаете это, все текущие процессы будут остановлены, включая копии установщика. -- Don't make multiple clicks on the installer even if it doesn't start right away. Иногда отображение интерфейса может занять несколько секунд. +- Не нажимайте на установщик несколько раз, если он не запускается сразу. Иногда отображение интерфейса может занять несколько секунд. ### Ошибка 1638: Другая версия этой программы уже установлена {#error-1638} @@ -83,14 +83,14 @@ You could say this is a particular subcategory of Error 1603. Возможные - Проверьте, установлен ли AdGuard на вашем компьютере. Вы можете сделать это, нажав клавишу *Win* и введя ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Удалите AdGuard с помощью нашего специального [инструмента удаления](../../installation#advanced), а затем повторите установку. +- Может быть, у вас остались файлы от предыдущей установки AdGuard. Удалите AdGuard с помощью нашего специального [инструмента удаления](../../installation#advanced), а затем повторите установку. ### Другие ошибки {#other} Если вы столкнулись с ошибкой, не указанной выше, возможно, мы сможем её решить. Но чтобы это сделать, нам нужны ваши логи. Пожалуйста, выполните следующие шаги: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Найдите и архивируйте **файлы журнала установки AdGuard**, как описано в [этой статье](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [Наша статья](../system-logs) объясняет, как это сделать. +- Найдите и сохраните на диск логи **Просмотра событий**. [Наша статья](../system-logs) объясняет, как это сделать. - Пожалуйста, отправьте файлы из двух предыдущих шагов команде поддержки по адресу **support@adguard.com** и опишите проблему. Наши специалисты технической поддержки ответят вам в кратчайшее время. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index 9f634eaf764..a6d4ef94d23 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ sidebar_position: 9 В AdGuard для Windows можно указать адрес DNS-сервера, который будет обрабатывать запросы вместо системного DNS-сервера, обычно предоставляемого провайдером (если это не отменено в настройках системы). Замена DNS-сервера, может защитить ваш DNS-трафик от прослушивания провайдером. Более того, выбрав зашифрованный и/или фильтрующий DNS-сервер, вы получите дополнительную защиту от киберпреступников и назойливой рекламы. -Многие пользователи AdGuard для Windows ценят функцию защиты DNS. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. В этой статье мы расскажем, почему это происходит и как этого избежать. +Многие пользователи AdGuard для Windows ценят функцию защиты DNS. Но некоторые из них сталкиваются со следующей проблемой: проверка на сайте типа https://ipleak.net/ показывает, что запросы обрабатываются системным DNS-сервером, а не выбранным. В этой статье мы расскажем, почему это происходит и как этого избежать. ## Bootstrap DNS-адрес @@ -21,7 +21,7 @@ sidebar_position: 9 - перейдите в *Расширенные настройки* - прокрутите вниз до раздела *Список пользовательских bootstrap-адресов* -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- введите bootsrap-адрес в формате IP-адреса (вы можете найти нужный в [списке известных DNS-провайдеров](https://adguard-dns.io/kb/general/dns-providers/)) - нажмите *Сохранить* ## Резервный (fallback) DNS-сервер @@ -33,7 +33,7 @@ sidebar_position: 9 - перейдите в *Расширенные настройки* - прокрутите вниз до раздела *Резервные (fallback) серверы* - отметьте опцию *Использовать пользовательские серверы* -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- затем найдите раздел *Список пользовательских резервных (fallback) серверов* и укажите серверы по одному в строке или diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 35a8d9c325e..b4b9c1c5a8b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ Data and/or files provided in dump files are processed in accordance with [the A :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard для Windows имеет два запущенных процесса (`Adguard.exe` и `AdguardSvc.exe`). Поэтому вам нужно создать файл дампа отдельно для каждого процесса. ::: ![Процессы AdGuard](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -Когда вы отправляете файлы дампа команде поддержки, пожалуйста, отправьте их вместе с логами, чтобы мы могли решить проблему как можно быстрее. [Here](../adguard-logs) you can check the instructions on how to get the log file. +Когда вы отправляете файлы дампа команде поддержки, пожалуйста, отправьте их вместе с логами, чтобы мы могли решить проблему как можно быстрее. [Здесь](../adguard-logs) вы можете ознакомиться с инструкцией по сбору логов AdGuard. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index a171011ad8d..ffa32e2b16c 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard installation logs +title: Как собирать логи установки AdGuard sidebar_position: 4 --- @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the Если во время установки AdGuard возникнут какие-либо проблемы, служба поддержки может попросить вас собрать и отправить им журналы установки AdGuard. В этом случае вам необходимо: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Выберите команду *Выполнить* в меню «Пуск» или нажмите *Win + R* на клавиатуре. 1. Введите *%tmp%* и нажмите *OK*. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index c98be24404a..eabd7e05782 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ sidebar_position: 7 Если эта функция включена, AdGuard будет блокировать TCP Fast Open в браузере Edge. Чтобы применить настройки, необходимо перезапустить браузер. -### Use Encrypted Client Hello +### Использовать Encrypted ClientHello -У каждого зашифрованного интернет-соединения есть незашифрованная часть. Это самый первый пакет, который содержит имя сервера, к которому вы подключаетесь. Технология Encrypted Client Hello должна решить эту проблему и зашифровать последний бит незашифрованной информации. To benefit from it, enable the *Use Encrypted Client Hello* option. Она использует локальный DNS-прокси для поиска ECH-конфигурации для домена. If it is found, Client Hello packet will be encrypted. +У каждого зашифрованного интернет-соединения есть незашифрованная часть. Это самый первый пакет, который содержит имя сервера, к которому вы подключаетесь. Технология Encrypted Client Hello должна решить эту проблему и зашифровать последний бит незашифрованной информации. Чтобы воспользоваться ей, включите опцию *Использовать Encrypted ClientHello*. Она использует локальный DNS-прокси для поиска ECH-конфигурации для домена. Если она найдена, пакет ClientHello будет зашифрован. ### Проверять прозрачность сертификатов сайтов @@ -73,7 +73,7 @@ sidebar_position: 7 ### Открывать главное окно при запуске системы -Включите эту опцию, чтобы главное окно AdGuard открывалось при каждом запуске системы. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Включите эту опцию, чтобы главное окно AdGuard открывалось при каждом запуске системы. Обратите внимание, что эта настройка не влияет на то, запущена ли реальная фильтрация или нет. Она находится в разделе *Настройки → Общие настройки* ### Включать фильтрацию при запуске системы @@ -95,7 +95,7 @@ sidebar_position: 7 ### Включить запись HAR -Эта опция должна быть включена **только в целях отладки**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. Этот файл можно проанализировать с помощью приложения Fiddler. Обратите внимание, что это может значительно замедлить просмотр веб-страниц. +Эта опция должна быть включена **только в целях отладки**. Если вы установите флажок, AdGuard создаст файл, содержащий информацию обо всех отфильтрованных HTTP-запросах в формате HAR 1.2. Этот файл можно проанализировать с помощью приложения Fiddler. Обратите внимание, что это может значительно замедлить просмотр веб-страниц. ### Добавлять пробел к обычному HTTP-запросу @@ -115,7 +115,7 @@ Host: example.org` Определяет размер фрагментации пакетов TCP, позволяющий избежать глубокой проверки пакетов. Этот параметр влияет только на защищённый трафик (HTTPS). -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +Если эта опция включена, AdGuard разбивает начальный TLS-пакет (пакет ClientHello) на две части: первая имеет указанную длину, а вторая — остаток, вплоть до длины всего начального TLS-пакета. Допустимые значения: 1–1500. Если указан недопустимый размер, будет использоваться значение, установленное системой. Эта настройка применяется только в том случае, если в режиме Антитрекинг включён параметр *Защищать от DPI*. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 5b16e07faea..69689cd10df 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect Windows system logs +title: Как получить файлы журнала Windows sidebar_position: 5 --- @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -Для анализа и диагностики сложных проблем, связанных с работой AdGuard, службе поддержки могут понадобиться файлы журнала Windows. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Ниже представлена инструкция для получения и отправки этих файлов. +Для анализа и диагностики сложных проблем, связанных с работой AdGuard, службе поддержки могут понадобиться файлы журнала Windows. Журналы Windows содержат записи о системных событиях и ошибках за последнее время. Ниже представлена инструкция для получения и отправки этих файлов. 1. Нажмите *Win + R* diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 055a1581a5f..c1286b390bb 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ sidebar_position: 1 ::: -Для фильтрации сетевого трафика AdGuard использует сетевой драйвер. Существует два варианта: драйвер TDI и драйвер WFP. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. Подобные ошибки могут выражаться совершенно по-разному, это зависит от конкретного случая. +Для фильтрации сетевого трафика AdGuard использует сетевой драйвер. Существует два варианта: драйвер TDI и драйвер WFP. Хотя драйвер WFP, как правило, предпочтительнее и включен по умолчанию для всех новых версий ОС Windows (Windows 8 и новее), он потенциально может вызвать проблемы совместимости, особенно с некоторыми антивирусными программами. Подобные ошибки могут выражаться совершенно по-разному, это зависит от конкретного случая. Если вы столкнулись с проблемой, которая предположительно была связана с совместимостью, вы всегда можете перейти на более старый, но более стабильный сетевой драйвер TDI. Для этого: 1. Перейдите в *Настройки → Сеть*. -2. Disable the WFP driver as it’s done in this picture: +2. Отключите драйвер WFP, как показано ниже: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/account/features.md index 5839929135b..bf1b8374ad4 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/account/features.md @@ -31,8 +31,8 @@ sidebar_position: 2 ## Просмотр покупок -В разделе «История покупок» отображаются все лицензии, которые вы когда-либо приобретали, используя адрес электронной почты, на которую зарегистрирован личный кабинет AdGuard. Вы также найдете там информацию о дате покупки, номере заказа, способе оплаты и стоимости покупки. +В разделе «История покупок» отображаются все лицензии, которые вы когда-либо приобретали, используя адрес электронной почты, на которую зарегистрирован личный кабинет AdGuard. You will also find there information about the date of purchase, order ID, payment method, and cost of the purchase. ## Связаться с поддержкой -Вкладка «Поддержка» содержит полезные ссылки, которые помогут вам решить проблемы или найти ответы на ваши вопросы о продуктах AdGuard. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +Вкладка «Поддержка» содержит полезные ссылки, которые помогут вам решить проблемы или найти ответы на ваши вопросы о продуктах AdGuard. Они разделены на шесть разделов: FAQ, «Отправить отчёт об ошибке/новое предложение», «Сообщить о некорректной блокировке», «Написать в поддержку», «База знаний» и «Обсудить». diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/account/register.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/account/register.md index f45dd13e223..89d08a5c867 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/account/register.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/account/register.md @@ -13,7 +13,7 @@ sidebar_position: 1 :::tip -Если вы введёте свой адрес электронной почты при покупке лицензии или получите в подарок лицензию, привязанную к вашему адресу электронной почты, учётная запись будет создана автоматически. Чтобы задать пароль, можно перейти по ссылке из транзакционного или подарочного письма. Вы также можете зарегистрироваться указанным выше способом. +If you enter your email address when purchasing a license, or receive a license linked to your email address as a gift, an account will be created automatically. Чтобы задать пароль, можно перейти по ссылке из транзакционного или подарочного письма. Вы также можете зарегистрироваться указанным выше способом. ::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 0a5b0cf9968..c569c3d7b36 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ sidebar_position: 2 - **Экспериментальный фильтр** предназначен для проверки некоторых новых правил фильтрации, которые потенциально могут вызывать конфликты или ломать работу сайтов. В случае успешной проверки правила из этого фильтра добавляются в основные фильтры. [Посмотреть правила](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Фильтр мобильной рекламы** блокирует рекламу на мобильных устройствах. Содержит все известные нам рекламные сети. [Посмотреть правила](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS-фильтр** составлен из нескольких фильтров (Базовый фильтр AdGuard, Фильтр социальных сетей, Фильтр счётчиков и систем аналитики, Фильтр мобильной рекламы, EasyList и EasyPrivacy) и специально упрощён для лучшей совместимости с блокировкой рекламы на DNS-уровне. Этот фильтр используется серверами [AdGuard DNS](https://adguard-dns.io/kb) для блокировки рекламы и трекинга. [Посмотреть правила](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## Политика фильтров AdGuard -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Чтобы узнать больше, прочтите полный текст [политики фильтров AdGuard](../filter-policy). +Наша политика фильтрации определяет, что фильтры AdGuard должны блокировать, а что нет, а также регулирует порядок добавления и удаления правил из фильтров. Чтобы узнать больше, прочтите полный текст [политики фильтров AdGuard](../filter-policy). ## Участвовать в развитии фильтров AdGuard diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 2164844af5a..77550907e69 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -51,7 +51,7 @@ toc_max_heading_level: 4 - `http://ads.example.org.us/ad1.gif` - `http://example.com/redirect/http://ads.example.org/` -По умолчанию такие правила не действуют для запросов документов. Это означает, что правило `||example.org^` будет блокировать запрос к `example.org`, когда вы попытаетесь перейти на этот домен с другого сайта, но если вы введёте `example.org` в адресную строку и попытаетесь перейти на него, сайт откроется. Чтобы заблокировать запрос документа, нужно использовать правило [с модификатором`$document`:](#document-modifier) `||example.org^$document`. +By default, such rules do not work for document requests. This means that the `||example.org^` rule will block a request made to `example.org` when you try to navigate to this domain from another website, but if you type `example.org` into the address bar and try to navigate to it, the website will open. To block the document request, you will need to use a rule with the [`$document` modifier](#document-modifier): `||example.org^$document`. ### Блокировка конкретного адреса @@ -135,7 +135,7 @@ AdGuard Content Blocker — это расширение для браузеро - Базовые правила блокировки со следующими модификаторами: `$domain`, `$third-party` и [модификаторы типа контента](#content-type-modifiers). - Базовые правила исключения со следующими модификаторами: `$document`, `$elemhide`. -- Базовые правила скрытия элементов [](#cosmetic-elemhide-rules) без поддержки расширенного CSS. +- Базовые правила скрытия элементов [](#cosmetic-elemhide-rules) без расширенной поддержки CSS. Из-за указанных выше ограничений AdGuard Content Blocker не будет упоминаться в примечаниях по совместимости. @@ -168,7 +168,7 @@ AdGuard Content Blocker — это расширение для браузеро modifiers = [modifier0, modifier1[, ...[, modifierN]]] ``` -- **`pattern`** — маска адреса. URL каждого запроса сопоставляется с этой маской. В шаблоне также можно использовать специальные символы, описанные [ниже](#basic-rules-special-characters). Обратите внимание, что AdGuard обрезает URL до 4096 символов, чтобы ускорить сопоставление и избежать проблем с длинными URL. +- **`pattern`** — маска адреса. URL каждого запроса сопоставляется с этой маской. In the template, you can also use the special characters described [below](#basic-rules-special-characters). Note that AdGuard truncates URLs to a length of 4096 characters in order to speed up matching and avoid issues with ridiculously long URLs. - **`@@`** — маркер, который используется для обозначения правил-исключений. С такого маркера должны начинаться правила, отключающие фильтрацию для запроса. - **`modifiers`** — параметры, используемые для «уточнения»‎ базового правила. Некоторые параметры ограничивают область действия правила, а некоторые могут полностью изменить принцип его работы. @@ -181,7 +181,7 @@ modifiers = [modifier0, modifier1[, ...[, modifierN]]] :::note -`|`, `||`, `^` можно использовать только в правилах, содержащих шаблон URL. Например, `||example.com##.advert` неверно и будет проигнорировано блокировщиком. +`|`, `||`, `^` can only be used with rules that have a URL pattern. For example, `||example.com##.advert` is incorrect and will be ignored by the blocker. ::: @@ -235,7 +235,7 @@ Wildcard-символы поддерживаются для TLD-доменов - `||example.com/ads/*` — простое правило, которое соответствует адресам типа `http://example.com/ads/banner.jpg` и даже `http://subdomain.example.com/ads/otherbanner.jpg`. -- `||example.org^$third-party` — правило, которое блокирует сторонние запросы к домену `example.org` и его поддоменам. +- `||example.org^$third-party` — this rule blocks third-party requests to `example.org` and its subdomains. - `@@||example.com$document ` — наиболее общее правило-исключение. Такое правило полностью отключает фильтрацию на домене `example.com` и всех его поддоменах. Существует ряд параметров, которые также можно использовать в правилах-исключениях. Более подробно о правилах-исключениях и параметрах, которые могут в таких правилах использоваться, написано [ниже](#exception-modifiers). @@ -265,26 +265,24 @@ Wildcard-символы поддерживаются для TLD-доменов -| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — полностью поддерживается - ✅ * — поддерживается, но надёжность может быть разной или могут возникнуть ограничения; ознакомьтесь с описанием модификатора для получения подробной информации -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — может быть уже реализован в nightly или бета-версиях, но пока не поддерживается в релизных версиях - ❌ — не поддерживается ::: @@ -326,7 +324,7 @@ Wildcard-символы поддерживаются для TLD-доменов Модификатор `$denyallow` позволяет избежать создания дополнительных правил, когда требуется отключить то или иное правило для определённых доменов. Модификатор `$denyallow` соответствует только целевым доменам, но не доменам реферера. -Добавление этого модификатора в правило равносильно исключению доменов при помощи паттерна правила либо при помощи добавления дополнительных правил-исключений. Чтобы добавить несколько доменов в одно правило, используйте символ `|` в качестве разделителя. +Добавление этого модификатора в правило равносильно исключению доменов при помощи паттерна правила либо при помощи добавления дополнительных правил-исключений. To add multiple domains to one rule, use the `|` character as a separator. **Примеры** @@ -353,8 +351,8 @@ Wildcard-символы поддерживаются для TLD-доменов :::caution Ограничения - Паттерн правила не может указывать на конкретные домены, например, не может начинаться с `||`. -- Домены в значении модификатора не могут быть отменены, например `$denyallow=~x.com`, или иметь подстановочный домен TLD, например `$denyallow=x.*`, или быть регулярным выражением, например `$denyallow=/\.(com\|org)/`. -- `$denyallow` не может использоваться вместе с [`$to`](#to-modifier). Его можно выразить инвертированным `$to`: `$denyallow=a.com|b.com` эквивалентно `$to=~a.com|~b.com`. +- Domains in the modifier value cannot be negated, e.g. `$denyallow=~x.com`, or have a wildcard TLD, e.g. `$denyallow=x.*`, or be a regular expression, e.g. `$denyallow=/\.(com\|org)/`. +- `$denyallow` cannot be used together with [`$to`](#to-modifier). It can be expressed with inverted `$to`: `$denyallow=a.com|b.com` is equivalent to `$to=~a.com|~b.com`. Правила, нарушающие эти ограничения, считаются недействительными. @@ -370,7 +368,7 @@ Wildcard-символы поддерживаются для TLD-доменов `$domain` ограничивает область действия правила запросами, сделанными **с** указанных доменов и их поддоменов (как указано в HTTP-заголовке [Referer](https://developer.mozilla.org/ru/docs/Web/HTTP/Headers/Referer)). -**Синтаксис** +**Syntax** Модификатор представляет собой список из одного или нескольких выражений, разделённых символом `|`, каждое из которых сопоставляется с доменом определённым образом в зависимости от его типа (см. ниже). @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`Regular_domain`** — обычное доменное имя (`domain.com`). Соответствует указанному домену и его поддоменам. Сопоставляется лексикографически. - **`any_tld_domain`** — доменное имя, оканчивающееся подстановочным знаком в качестве [публичного суффикса](https://publicsuffix.org/learn/), например, для `example.*` это `co.uk` в `example.co.uk`. Соответствует указанному домену и его поддоменам с любым публичным суффиксом. Сопоставляется лексикографически. -- **`regexp`** — регулярное выражение, начинается и заканчивается символом `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — регулярное выражение, начинается и заканчивается символом `/`. Паттерн работает так же, как и в основных URL-правилах, но символы `/`, `$` и `,` должны быть экранированы с помощью `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Правила с модификатором `$domain` в виде `regular_domain` или `any_tld_domain` поддерживаются всеми продуктами AdGuard. ::: @@ -409,9 +407,9 @@ Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard p **Модификатор `$domain`, соответствующий целевому домену:** -В некоторых случаях модификатор `$domain` может соответствовать не только домену-рефереру, но и целевому домену. Это происходит при соблюдении всех условий: +В некоторых случаях модификатор `$domain` может соответствовать не только домену-рефереру, но и целевому домену. This happens when all the following conditions are met: -1. Тип контента запроса — `document` +1. The request has the `document` content type 1. Шаблон правила не соответствует ни одному конкретному домену 1. Шаблон правила не содержит регулярных выражений 1. Модификатор `$domain` содержит только исключённые домены, например, `$domain=~example.org|~example.com` @@ -446,12 +444,6 @@ Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard p :::caution Ограничения -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - -:::caution Ограничения - Safari не поддерживает одновременно разрешённые и запрещённые домены, поэтому правила вида `||baddomain.com^$domain=example.org|~foo.example.org` не работают в AdGuard для iOS и AdGuard для Safari. ::: @@ -468,7 +460,7 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.12 or later the `$d Модификатор `$header` позволяет сопоставлять HTTP-ответ, имеющий определённый заголовок, с определённым значением (опционально). -**Синтаксис** +**Syntax** ```text $header "=" h_name [":" h_value] @@ -477,12 +469,12 @@ h_value = string / regexp где: -- **`h_name`** (обязательно) — имя HTTP-заголовка. Сопоставляется без учёта регистра символов. +- **`h_name`** (обязательно) — имя HTTP-заголовка. It is matched case-insensitively. - **`h_value`** (опционально) — выражение для сопоставления значения HTTP-заголовка, может быть одним из: - **`string`** — последовательность символов. Лексикографически сопоставляется со значением заголовка; - **`regexp`** — регулярное выражение, начинается и заканчивается символом `/`. Паттерн работает так же, как и в основных URL-правилах, но символы `/`, `$` и `,` должны быть экранированы с помощью `\`. -Часть модификатора со значением заголовка `":" h_value` может быть опущена. В этом случае модификатор сопоставляет только имя заголовка. +The modifier part, `":" h_value`, may be omitted. В этом случае модификатор сопоставляет только имя заголовка. **Примеры** @@ -491,7 +483,7 @@ h_value = string / regexp - `@@||example.com^$header=set-cookie:/foo\, bar\$/` разблокирует запросы, ответы которых содержат заголовок `Set-Cookie` со значением `foo, bar$`. - `@@||example.com^$header=set-cookie` разблокирует запрос, ответ которого содержит заголовок `Set-Cookie` с любым значением. -##### Ограничения модификатора `$header` {#header-modifier-limitations} +##### `$header` modifier limitations {#header-modifier-limitations} :::caution Ограничения @@ -508,7 +500,7 @@ Rules with the `$header` modifier are supported by AdGuard for Windows, AdGuard #### **`$important`** {#important-modifier} -Модификатор `$important`, применённый к правилу, повышает его приоритет по сравнению с правилами без такого модификатора. Даже относительно базовых правил-исключений. +The `$important` modifier applied to a rule increases its priority over rules without the identical modifier. Даже относительно базовых правил-исключений. Перейдите [к приоритетам правил](#rule-priorities) для более подробной информации. @@ -536,7 +528,7 @@ Rules with the `$header` modifier are supported by AdGuard for Windows, AdGuard :::info Совместимость -Правила с `$match-case` поддерживаются в AdGuard для iOS и AdGuard для Safari с SafariConverterLib версии 2.0.43 или выше. +Rules with the `$match-case` are supported by AdGuard for iOS and AdGuard for Safari with SafariConverterLib v2.0.43 or later. Все остальные продукты уже поддерживают этот модификатор. @@ -555,13 +547,13 @@ Rules with the `$header` modifier are supported by AdGuard for Windows, AdGuard :::caution Ограничения -Правила, где к одному методу применяется инверсия (~), а к другому нет, считаются недействительными. Так, например, правило `||evil.com^$method=get|~head` будет проигнорировано. +Правила, где к одному методу применяется инверсия (~), а к другому нет, считаются недействительными. Так, например, правило `||evil.com^$method=get|~head` будет отклонено. ::: :::info Совместимость -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -573,66 +565,25 @@ AdGuard будет пытаться закрыть браузерную вкла - `||domain.com^$popup` — при попытке перехода на сайт `http://domain.com` с любой страницы в браузере, новая вкладка, в которой должен открыться указанный сайт, будет закрыта. -##### Ограничения модификатора `$popup` {#popup-modifier-limitations} +##### `$popup` modifier limitations {#popup-modifier-limitations} -:::caution Ограничения +:::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. -1. В AdGuard для iOS и AdGuard для Safari `$popup`-правила просто заблокируют страницу. -1. В AdGuard для Windows, AdGuard для Mac и AdGuard для Android модификатор `$popup` в некоторых случаях может не обнаружить всплывающее окно, и оно не будет заблокировано. Модификатор `$popup` применяет тип контента `document` со специальным флагом, который передаётся блокирующей странице. Блокирующая страница сама может провести некоторые проверки и закрыть окно, если это действительно всплывающее окно. В противном случае страница должна быть загружена. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. The `$popup` modifier works best in AdGuard Browser Extension. +1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Блокирующая страница сама может провести некоторые проверки и закрыть окно, если это действительно всплывающее окно. В противном случае страница должна быть загружена. Его можно комбинировать с другими модификаторами типа request, такими как `$third-party` и `$important`. ::: :::info Совместимость -Правила с модификатором `$popup` не поддерживаются в AdGuard Content Blocker. - -::: - -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Примеры** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. Например, запрос с домена `domain.com` к домену `http://domain.com/icon.ico` — это запрос первой стороны. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Совместимость - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Примеры** - -- `||domain.com^$strict-third-party` — правило применяется на всех доменах, кроме `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Совместимость - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. +Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. Например, запрос к домену `example.org`, отправленный с домена `domain.com`, является сторонним. +Ограничение на сторонние или собственные запросы. Сторонним является запрос, отправленный с другого домена. Например, запрос к домену `example.org`, отправленный с домена `domain.com`, является сторонним. :::note @@ -653,7 +604,7 @@ A restriction on third-party and custom requests. A third-party request is a req **`$~third-party`:** -- `||domain.com$~third-party` — это правило применяется исключительно к `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`. +- `||domain.com$~third-party` — this rule is applied exclusively to `domain.com`. Example of a non third-party request: `http://domain.com/icon.ico`. :::note @@ -663,7 +614,7 @@ A restriction on third-party and custom requests. A third-party request is a req #### **`$to`** {#to-modifier} -`$to` ограничивает область действия правила запросами, сделанными **на** указанные домены и их поддомены. Чтобы добавить несколько доменов в одно правило, используйте символ `|` в качестве разделителя. +`$to` ограничивает область действия правила запросами, сделанными **на** указанные домены и их поддомены. To add multiple domains to one rule, use the `|` character as a separator. **Примеры** @@ -673,13 +624,13 @@ A restriction on third-party and custom requests. A third-party request is a req :::caution Ограничения -[`$denyallow`](#denyallow-modifier) не может использоваться вместе с `$to`. Его можно выразить инвертированным `$to`: `$denyallow=a.com|b.com` эквивалентно `$to=~a.com|~b.com`. +[`$denyallow`](#denyallow-modifier) cannot be used together with `$to`. It can be expressed with inverted `$to`: `$denyallow=a.com|b.com` is equivalent to `$to=~a.com|~b.com`. ::: :::info Совместимость -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for -| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------ |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "удалён") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "удалён") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------ |:------------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "удалён") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "удалён") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -741,8 +692,8 @@ Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for - `||example.com^$document` блокирует запрос HTML-документа на `example.com` с помощью блокирующей страницы. - `||example.com^$document,redirect=noopframe` перенаправляет запрос HTML-документа сайта `example.com` на пустой HTML-документ. -- `||example.com^$document,removeparam=test` удаляет параметр `test` из запроса HTML-документа к `example.com`. -- `||example.com^$document,replace=/test1/test2/` заменяет `test1` на `test2` в запросе HTML-документа к `example.com`. +- `||example.com^$document,removeparam=test` removes `test` query parameter from HTML document request to `example.com`. +- `||example.com^$document,replace=/test1/test2/` replaces `test1` with `test2` in HTML document request to `example.com`. :::note @@ -774,17 +725,11 @@ Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Правило соответствует запросам, вызванным атрибутом `navigator.sendBeacon()` или `ping` в ссылках. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Ограничения +:::info Совместимость AdGuard для Windows, Mac и Android часто не может точно определить `navigator.sendBeacon()`. Не рекомендуется использовать `$ping` в фильтрах, которые должны использоваться продуктами AdGuard на базе CoreLibs. -::: - -:::info Совместимость - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Правила с модификатором `$ping` не поддерживаются в AdGuard для Safari и iOS. ::: @@ -817,16 +762,10 @@ Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Ограничения - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. В противном случае некоторые основные страницы могут рассматриваться как поддокументы. - -::: - :::info Совместимость +В AdGuard для Windows, Mac и Android вложенные документы обнаруживаются по заголовку [Sec-Fetch-Dest][sec-fetch-dest-header], если он есть. В противном случае некоторые основные страницы могут рассматриваться как поддокументы. + Правила с модификатором `$subdocument` не поддерживаются в AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ In AdGuard for Windows, Mac, and Android subdocuments are being detected by the Правило применяется только к соединениям WebSocket. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Ограничения - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Совместимость -Модификатор `$websocket` поддерживается во всех продуктах AdGuard, кроме AdGuard Content Blocker. +Модификатор `$websocket` поддерживается во всех продуктах AdGuard, кроме AdGuard Content Blocker. Что касается AdGuard для Safari и AdGuard для iOS, то они поддерживаются на устройствах с macOS Monterey (версия 12) и iOS 16 и выше. ::: @@ -885,7 +816,7 @@ AdGuard для Windows, Mac и Android часто не может точно о **Примеры** -- `||example.com^$webrtc,domain=example.org` — это правило блокирует WebRTC-соединения c `example.com` от `example.org`. +- `||example.com^$webrtc,domain=example.org` blocks webRTC connections to `example.com` from `example.org`. - `@@*$webrtc,domain=example.org` — это правило отключает оболочку RTC для `example.org`. ### Модификаторы правил исключений {#exception-modifiers} @@ -900,17 +831,17 @@ AdGuard для Windows, Mac и Android часто не может точно о -| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -946,13 +877,13 @@ AdGuard для Windows, Mac и Android часто не может точно о Отключает пользовательские скрипты — определённые или все для данного домена. -**Синтаксис** +**Syntax** ```text $extension[="userscript_name1"[|"userscript_name2"[|"userscript_name3"[...]]]] ``` -`userscript_name(i)` обозначает конкретное имя пользовательского скрипта, которое должно быть отключено модификатором. Модификатор может содержать любое количество имён пользовательских скриптов или не содержать их вовсе. В последнем случае модификатор отключает все пользовательские скрипты. +`userscript_name(i)` обозначает конкретное имя пользовательского скрипта, которое должно быть отключено модификатором. The modifier can contain any number of userscript names or none. В последнем случае модификатор отключает все пользовательские скрипты. Имена пользовательских скриптов обычно содержат пробелы или другие специальные символы, поэтому необходимо заключать их в кавычки. Поддерживаются как одинарные (`'`), так и двойные (`"`) ASCII-кавычки. Несколько имён пользовательских скриптов должны быть разделены вертикальной чертой (`|`). Однако если имя пользовательского скрипта представляет собой одно слово без специальных символов, то его можно использовать без кавычек. @@ -978,52 +909,38 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` отключает пользовательский скрипт `AdGuard Assistant` на сайте `example.com`. - `@@||example.com^$extension=MyUserscript` отключает пользовательский скрипт `MyUserscript` на сайте `example.com`. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` отключает оба пользовательских скрипта `AdGuard Assistant` и `Popup Blocker` на сайте `example.com`. - `@@||example.com^$extension=~"AdGuard Assistant"` отключает все пользовательские скрипты на сайте `example.com`, кроме `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` отключает все пользовательские скрипты на сайте `example.com`, кроме `AdGuard Assistant` и `Popup Blocker`. - `@@||example.com^$extension` — пользовательские скрипты не будут работать на страницах сайта `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` отключает пользовательский скрипт `AdGuard "Assistant"` на сайте `example.com`. :::info Совместимость - Только AdGuard для Windows, Mac и Android имеют технические возможности для поддержки правил с модификатором `$extension`. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. О скриптлетах и javascript-правилах речь пойдёт ниже. +Запрещает добавление javascript-кода на страницу. О скриптлетах и javascript-правилах речь пойдёт ниже. **Примеры** - `@@||example.com^$jsinject` отменяет все javascript-правила для страниц на сайте `example.com` и на всех его поддоменах. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Совместимость - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Отключает модуль «Антитрекинг»‎ для всех страниц и запросов, подходящих под это правило. -**Синтаксис** +**Syntax** ```text $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. Модификатор может содержать любое количество опций (см. ниже) или не содержать их вовсе. In the latter case the modifier disables all the Tracking protection features. +Здесь `opt(i)` обозначают опции «Антитрекинг»‎, отключаемые правилами. The modifier can contain any number of specific options (see below) or none. В последнем случае модификатор отключает модуль «Антитрекинг»‎ полностью. Список доступных опций модификатора: @@ -1046,27 +963,27 @@ $stealth [= opt1 [| opt2 [| opt3 [...]]]] **Примеры** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` полностью отключает модуль «Антитрекинг» для запросов к `example.com` и поддоменам, кроме блокировки куки и скрытия параметров отслеживания (см.ниже). +- `@@||domain.com^$script,stealth,domain=example.com` отключает модуль «Антитрекинг» только для script-запросов к `domain.com` (и поддоменам) на `example.com` и всех его поддоменах. - `@@||example.com^$stealth=3p-cookie|dpi` отключает блокировку сторонних куки-файлов и меры защиты от DPI для запросов к `example.com`. :::note -Блокировка куки и удаление параметров отслеживания достигается с помощью правил с модификаторами [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) и [`$removeparam`](#removeparam-modifier). Правила-исключения, которые содержат только модификатор `$stealth`, не будут выполнять эти действия. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: :::caution Ограничения -- Параметры модификатора должны быть написаны строчными буквами, т. е. `$stealth=DPI` будет отклонено. +- Modifier options must be lowercase, i.e. `$stealth=DPI` will be rejected. - Параметры модификатора не могут отрицаться, т.е. `$stealth=~3p-cookie` будет отклонён. -- Браузерное расширение AdGuard поддерживает только опции `searchqueries`, `donottrack`, `referrer`, `xclientdata`, `1p-cookie` и `3p-cookie`. +- AdGuard Browser Extension supports only `searchqueries`, `donottrack`, `referrer`, `xclientdata`, `1p-cookie` and `3p-cookie` options. ::: :::info Совместимость -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. Все остальные продукты будут игнорировать правила с модификатором `$stealth`. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. Все остальные продукты будут игнорировать правила с модификатором `$stealth`. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ $stealth [= opt1 [| opt2 [| opt3 [...]]]] - `@@||example.com^$urlblock` — любые запросы, отправленные со страниц сайта `example.com` и всех его поддоменов, не будут блокироваться. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Ограничения +:::info Совместимость В AdGuard для iOS и AdGuard для Safari правила `$urlblock` работают как [исключение $document](#document-modifier) — они разблокируют всё. -::: - -:::info Совместимость - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Правила с модификатором `$urlblock` не поддерживаются в AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ domain.com###banner - `@@||example.com^$genericblock` отключает базовые правила generic на любых страницах `example.com` и всех поддоменах. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Ограничения +:::info Совместимость В AdGuard для iOS и AdGuard для Safari правила `$genericblock` работают как [исключение $document](#document-modifier) — они разблокируют всё. -::: - -:::info Совместимость - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Правила с модификатором `$genericblock` не поддерживаются в AdGuard Content Blocker. ::: @@ -1184,71 +1089,60 @@ Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker -| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "устарел") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "устарел") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "устарел") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "устарел") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — полностью поддерживается - ✅ * — поддерживается, но надёжность может быть разной или могут возникнуть ограничения; ознакомьтесь с описанием модификатора для получения подробной информации -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — может быть уже реализован в nightly или бета-версиях, но пока не поддерживается в релизных версиях + - ❌ — не поддерживается -- 👎 — устарел; всё ещё поддерживается, но в будущем будет удалён +- 👎 — deprecated; still supported but will be removed in the future ::: #### **`$all`** {#all-modifier} -Модификатор `$all` состоит из [всех модификаторов content-type](#content-type-modifiers) и [`$popup`](#popup-modifier). Например, правило `||example.org^$all` конвертируется в правило: +`$all` modifier is made of [all content-types modifiers](#content-type-modifiers) and [`$popup`](#popup-modifier). E.g. rule `||example.org^$all` is converting into rule: ```adblock ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Ограничения - -Этот модификатор нельзя использовать как исключение с маркером `@@`. - -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Ограничения - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: +This modifier cannot be used as an exception with the `@@` mark. :::info Совместимость -Правила с модификатором `$all` не поддерживаются в AdGuard Content Blocker. +Rules with `$all` modifier are not supported by AdGuard Content Blocker. ::: #### **`$badfilter`** {#badfilter-modifier} -Правила, содержащие модификатор `$badfilter`, отключают другие базовые правила, на которые они ссылаются. Это означает, что текст отключённого правила должен соответствовать тексту `$badfilter`-правила (за исключением самого модификатора `$badfilter`). +The rules with the `$badfilter` modifier disable other basic rules to which they refer. It means that the text of the disabled rule should match the text of the `$badfilter` rule (without the `$badfilter` modifier). **Примеры** @@ -1257,12 +1151,12 @@ Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGu - `@@||example.com$badfilter` отключает `@@||example.com` - `||example.com$domain=domain.com,badfilter` отключает `||example.com$domain=domain.com` -Правила с модификатором `$badfilter` могут отключать другие базовые правила для определённых доменов, если они соответствуют следующим условиям: +Rules with `$badfilter` modifier can disable other basic rules for specific domains if they fulfill the following conditions: 1. В правиле есть модификатор `$domain` 1. В модификаторе `$domain` нет отрицания домена `~` -В этом случае, правило с `$badfilter` отключит соответствующее базовое правило для доменов, указанных как в правиле с `$badfilter`, так и в базовом правиле. Обратите внимание, что [логика wildcard для доменов верхнего уровня (TLD)](#wildcard-for-tld) здесь также применима. +In that case, the `$badfilter` rule will disable the corresponding rule for domains specified in both the `$badfilter` and basic rules. Please note that [wildcard-TLD logic](#wildcard-for-tld) works here as well. **Примеры** @@ -1273,29 +1167,21 @@ Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGu - `/some$domain=example.*` отключено для `example.com` и `example.org` правилом `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` НЕ отключено для `example.com` правилом `/some$domain=example.com|~example.org,badfilter`, поскольку значение модификатора `$domain` содержит отрицание домена -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Ограничения - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Совместимость -Правила с модификатором `$badfilter` не поддерживаются в AdGuard Content Blocker. +Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. ::: #### **`$cookie`** {#cookie-modifier} -Модификатор `$cookie` полностью меняет поведение правила. Вместо того, чтобы блокировать запрос, этот модификатор позволяет AdGuard блокировать или изменять заголовки `Cookie` или `Set-Cookie`. +The `$cookie` modifier completely changes rule behavior. Instead of blocking a request, this modifier makes AdGuard suppress or modify the `Cookie` and `Set-Cookie` headers. -**Несколько правил, соответствующих одному запросу** +**Multiple rules matching a single request** -В случае, когда несколько правил `$cookie` соответствуют одному запросу, мы применим каждое из них по очереди. +In case if multiple `$cookie` rules match a single request, we will apply each of them one by one. -**Синтаксис** +**Syntax** ```adblock $cookie [= name[; maxAge = seconds [; sameSite = strategy ]]] @@ -1305,22 +1191,22 @@ $cookie [= name[; maxAge = seconds [; sameSite = strategy ]]] - **`name`** — опционально, строка или регулярное выражение для сопоставления с именем куки. - **`seconds`** — количество секунд, на которое сместится истечение срока действия куки. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — строка для стратегии [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) для использования куки. -Например, +For example, ```adblock ||example.org^$cookie=NAME;maxAge=3600;sameSite=lax ``` -каждый раз, когда AdGuard встречает куки с именем `NAME` в запросе к `example.org`, он будет делать следующее: +every time AdGuard encounters a cookie called `NAME` in a request to `example.org`, it will do the following: - Установит дату истечения срока хранения на текущее время плюс `3600` секунд - Позволяет куки использовать стратегию [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite). -**Экранирование специальных символов** +**Escaping special characters** -Если для сопоставления используется регулярное выражение `name`, необходимо экранировать два символа: запятую `,` и знак доллара `$`. Use backslash `\` to escape each of them. Например, экранированная запятая будет выглядеть так: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Примеры** @@ -1329,54 +1215,46 @@ $cookie [= name[; maxAge = seconds [; sameSite = strategy ]]] - `$cookie=/__utm[a-z]/` блокирует куки Google Analytics везде - `||facebook.com^$third-party,cookie=c_user` не позволяет Facebook отслеживать вас, даже если вы вошли в систему -Существует два способа деактивации правил `$cookie`: основной предполагает использование исключения с `@@` — `@@||example.org^$cookie`. Альтернативный метод использует исключение `$urlblock` (также входящее в псевдоним исключения `$document` — `$elemhide,jsinject,content,urlblock,extension`). Вот как это работает: +There are two methods to deactivate `$cookie` rules: the primary method involves using an exception marked with `@@` — `@@||example.org^$cookie`. The alternative method employs a `$urlblock` exception (also included under the `$document` exception alias — `$elemhide,jsinject,content,urlblock,extension`). Here's how it works: - `@@||example.org^$cookie` разблокирует все куки-файлы, установленные `example.org` - `@@||example.org^$urlblock` разблокирует все файлы куки, установленные `example.org`, и отключает блокировку всех запросов, отправленных с `example.org` - `@@||example.org^$cookie=concept` разблокирует один куки-файл с именем `concept` - `@@||example.org^$cookie=/^_ga_/` разблокирует все куки, соответствующие регулярному выражению -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Ограничения - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Ограничения -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: :::info Совместимость -Правила с модификатором `$cookie` не поддерживаются в AdGuard Content Blocker, AdGuard для iOS и AdGuard для Safari. +Rules with `$cookie` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: #### **`$csp`** {#csp-modifier} -Этот модификатор полностью меняет поведение правила. Когда он применяется, правило не блокирует запрос. Вместо этого будут изменены заголовки ответа. +This modifier completely changes the rule behavior. If it is applied to a rule, the rule will not block the matching request. Response headers will be modified instead. :::info -Чтобы использовать правила этого типа, необходимо базовое понимание слоя безопасности [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy). +In order to use this type of rules, it is required to have the basic understanding of the [Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy) security layer. ::: -Для запросов, подходящих под `$csp`-правило, мы усилим политику безопасности ответа, добавив дополнительную политику, равнозначную содержимому модификатора `$csp`. Правила `$csp` применяются независимо от правил любого другого типа. На него могут повлиять **только исключения на уровне документа** (см. раздел с примерами), но никак не другие базовые правила. +For the requests matching a `$csp` rule, we will strengthen response security policy by enhancing the content security policy, similar to the content security policy of the `$csp` modifier contents. `$csp` rules are applied independently from any other rule type. **Only document-level exceptions** can influence it (see the examples section), but no other basic rules. -**Несколько правил, соответствующих одному запросу** +**Multiple rules matching a single request** -В случае, когда несколько правил `$csp` соответствуют одному запросу, мы применим каждое из них. +In case if multiple `$csp` rules match a single request, we will apply each of them. -**Синтаксис** +**Syntax** -Синтаксис значений `$csp` похож на синтаксис заголовков Политики Безопасности Контента. +`$csp` value syntax is similar to the Content Security Policy header syntax. -Значение `$csp` может быть пустым в случае правил-исключений. См. примеры ниже. +`$csp` value can be empty in the case of exception rules. See examples section below. **Примеры** @@ -1389,52 +1267,52 @@ In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content- :::caution Ограничения - Некоторые символы запрещены в значении `$csp`: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp`-правила поддерживают ограниченный список модификаторов: `$domain`, `$important`, `$subdocument`. - Правила с директивами `report-*` считаются некорректными. ::: :::info Совместимость -Правила с модификатором `$csp` не поддерживаются в AdGuard Content Blocker, AdGuard для iOS и AdGuard для Safari. +Rules with `$csp` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. ::: #### **`$hls`** {#hls-modifier} -Правила `$hls` модифицируют ответ на соответствующий правилу запрос. Они предназначены для удаления сегментов из [HLS-плейлистов (RFC 8216)](https://datatracker.ietf.org/doc/html/rfc8216). +`$hls` rules modify the response of a matching request. They are intended as a convenient way to remove segments from [HLS playlists (RFC 8216)](https://datatracker.ietf.org/doc/html/rfc8216). :::note -Слово segment в документации означает Media Segment или playlist (как часть Master Playlist): с точки зрения правил `$hls`, Master Playlist и Media Playlist неразличимы. +The word "segment" in this document means either a "Media Segment" or a "playlist" as part of a "Master Playlist": `$hls` rules do not distinguish between a "Master Playlist" and a "Media Playlist". ::: -**Синтаксис** +**Syntax** - `||example.org^$hls=urlpattern` удаляет сегменты, URL которых соответствует паттерну `urlpattern`. Паттерн работает так же, как в базовых URL-правилах, однако символы `/`, `$` и `,` в составе `urlpattern` необходимо экранировать с помощью `\`. - `||example.org^$hls=/regexp/options` удаляет сегменты, в которых URL-адрес или один из тегов (для определённых параметров, если они есть) соответствуют регулярному выражению `regexp`. Доступные значения `options`: - `t` — вместо URL-адреса сегмента проверять каждый тег сегмента на соответствие регулярному выражению. Сегмент с соответствующим тегом будет удалён; - `i` — сделать регулярное выражение нечувствительным к регистру символов. -Символы `/`, `$` и `,` должны быть экранированы символом `\` внутри `regexp`. +The characters `/`, `$` and `,` must be escaped with `\` inside `regexp`. **Исключения** -Базовые URL-исключения не должны отключать правила с модификатором `$hls`. Отключить их можно следующим образом: +Basic URL exceptions shall not disable rules with `$hls` modifier. They can be disabled as described below: - `@@||example.org^$hls` отключает все правила `$hls` для ответов от URL-адресов, соответствующих `||example.org^ URL`. - `@@||example.org^$hls=text` отключает все правила `$hls`, у которых значение модификатора `$hls` равно `text`, для ответов с URL-адресов, соответствующих `||example.org^ URL`. :::tip -`$hls` также можно отключить с помощью правил-исключений с модификаторами `$document`, `$content` и `$urlblock`. +`$hls` rules can also be disabled by `$document`, `$content` and `$urlblock` exception rules. ::: :::note -Если несколько правил `$hls` соответствуют одному и тому же запросу, их эффект суммируется. +When multiple `$hls` rules match the same request, their effect is cumulative. ::: @@ -1444,26 +1322,26 @@ In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content- - `||example.org^$hls=/\/videoplayback\/?\?.*\&source=dclk_video_ads/i` делает почти то же самое, но с помощью регулярного выражения вместо URL-паттерна. - `||example.org^$hls=/#UPLYNK-SEGMENT:.*\,ad/t` удаляет все сегменты с соответствующим тегом. -**О формате HLS-плейлистов** +**Anatomy of an HLS playlist** -Краткое описание [спецификации](https://datatracker.ietf.org/doc/html/rfc8216): +A quick summary of the [specification](https://datatracker.ietf.org/doc/html/rfc8216): 1. HLS-плейлист — это набор текстовых строк 1. Можно использовать пустую строку, комментарий (начинается с `#`), тег (тоже начинается с `#`, распознаётся по содержанию) или URL 1. Строка с URL называется сегментом 1. Тег может относиться к одному сегменту, т.е. к первой строке с URL, следующей после данного тега, ко всем последующим сегментам (пока не встретится тег с тем же названием) или ко всему плейлисту -Замечания, касающиеся правил `$hls`: +Some points specific to the operation of `$hls` rules: 1. Когда сегмент удаляется, все теги, относящиеся только к нему, тоже удаляются 1. Теги, относящиеся к нескольким сегментам, удаляются, если все эти сегменты были удалены 1. Поскольку различные типы тегов невозможно распознать по синтаксису, мы распознаем все теги, указанные в RFC, плюс некоторые нестандартные теги, которые встречались нам в полевых условиях. Любые строки, начинающиеся с `#` и не распознанные как тег, пропускаются без модификации и не сопоставляются с правилами -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. Если вы знаете, что делаете, вы можете использовать правила `$replace` для удаления или перезаписи только одного тега из плейлиста +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. Если вы знаете, что делаете, вы можете использовать правила `$replace` для удаления или перезаписи только одного тега из плейлиста -**Пример работы правил:** +**An example of a transformation done by the rules:**
-Исходный ответ +Original response ```text #EXTM3U @@ -1490,7 +1368,7 @@ preroll.ts
-Применённые правила +Applied rules ```adblock ||example.org^$hls=preroll @@ -1500,7 +1378,7 @@ preroll.ts
-Модифицированный ответ +Modified response ```text #EXTM3U @@ -1520,21 +1398,21 @@ preroll.ts :::caution Ограничения - Правила `$hls` разрешены только [**в доверенных фильтрах**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- Правила `$hls` совместимы с модификаторами `$domain`, `$third-party`, `$app`, `$important`, `$match-case` и `$xmlhttprequest`. - Правила `$hls` применимы только к HLS-плейлистам, т. е. к тексту в кодировке UTF-8, начинающемуся со строки `#EXTM3U`. Никакие другие ответы не будут модифицированы этими правилами. -- Правила с `$hls` не применяются к ответам размером больше 10 МБ. +- `$hls` rules do not apply if the size of the original response is more than 10 MB. ::: :::info Совместимость -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: #### **`$inline-script`** {#inline-script-modifier} -Модификатор `$inline-script` предназначен для блокировки встроенного в страницу кода JavaScript с использованием политики безопасности контента (CSP). Он повышает безопасность, не позволяя загружать встроенную рекламу или потенциально вредоносные скрипты. Правило `||example.org^$inline-script` конвертируется в правило синтаксиса CSP: +The `$inline-script` modifier is designed to block inline JavaScript embedded into the web page, using Content Security Policy (CSP). It improves security and privacy by preventing application of inline ads or potentially malicious scripts. The rule `||example.org^$inline-script` is converting into the CSP-syntax rule: ```adblock ||example.org^$csp=script-src 'self' 'unsafe-eval' http: https: data: blob: mediastream: filesystem: @@ -1542,7 +1420,7 @@ Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for #### **`$inline-font`** {#inline-font-modifier} -Модификатор `$inline-font` предназначен для блокировки встроенных в страницу шрифтов с использованием политики безопасности контента (CSP). Он повышает безопасность, не позволяя загружать встроенные шрифты, которые могут использоваться для сбора данных и фингерпринтинга. Правило `||example.org^$inline-font` конвертируется в правило синтаксиса CSP: +The `$inline-font` modifier is designed to block inline fonts embedded into the web page, using Content Security Policy (CSP). It improves security and privacy by preventing application of inline fonts that could be used for data collection and fingerprinting. The rule `||example.org^$inline-font` is converting into the CSP-syntax rule: ```adblock ||example.org^$csp=font-src 'self' 'unsafe-eval' http: https: data: blob: mediastream: filesystem: @@ -1550,17 +1428,17 @@ Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for #### **`$jsonprune`** {#jsonprune-modifier} -Правила `$jsonprune` модифицируют ответ на соответствующий запрос, удаляя JSON-элементы, которые соответствуют модифицированному выражению [JSONPath](https://goessner.net/articles/JsonPath/). Эти правила не изменяют ответы, которые не являются действительными JSON-документами. +`$jsonprune` rules modify the response to a matching request by removing JSON items that match a modified [JSONPath](https://goessner.net/articles/JsonPath/) expression. They do not modify responses which are not valid JSON documents. In AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, `$jsonprune` also supports modifying JSONP (padded JSON) documents. -**Синтаксис** +**Syntax** - `||example.org^$jsonprune=expression` удаляет из ответа элементы, соответствующие изменённому JSONPath-выражению `expression`. -Из-за особенностей работы парсинга правил символы `$` и `,` внутри `expression` должны экранироваться символом `\`. +Due to the way rule parsing works, the characters `$` and `,` must be escaped with `\` inside `expression`. -Модифицированный синтаксис JSONPath имеет следующие отличия от оригинального: +The modified JSONPath syntax has the following differences from the original: 1. Выражения на сценарном языке (script expressions) не поддерживаются 1. Поддерживаемые предикаты (filter expressions): @@ -1572,24 +1450,24 @@ In AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, `$jso 1. Выражения, оканчивающиеся на `..`, не поддерживаются 1. Разрешено указывать несколько срезов массива (array slices) в квадратных скобках -Существуют различные онлайн-инструменты, которые делают работу с выражениями JSONPath удобнее: +There are various online tools that make working with JSONPath expressions more convenient: https://www.site24x7.com/tools/jsonpath-finder-validator.html https://jsonpathfinder.com/ https://jsonpath.com/ -Обратите внимание, что различные имплементации JSONPath обладают уникальными особенностями и могут быть несовместимы друг с другом. +Keep in mind, though, that all JSONPath implementations have unique features/quirks and are subtly incompatible with each other. **Исключения** -Базовые URL-исключения не должны отключать правила с модификатором `$jsonprune`. Отключить их можно следующим образом: +Basic URL exceptions shall not disable rules with the `$jsonprune` modifier. They can be disabled as described below: - `@@||example.org^$jsonprune` отключает все правила `$jsonprune` для ответов от URL-адресов, соответствующих `||example.org^`. -- `@@||example.org^$jsonprune=text` отключает все правила `$jsonprune`, у которых значение модификатора `$jsonprune` равно `text`, для ответов с URL-адресов, соответствующих `||example.org^ URL`. +- `@@||example.org^$jsonprune=text` disables all `$jsonprune` rules with the value of the `$jsonprune` modifier equal to `text` for responses from URLs matching `||example.org^`. -`$jsonprune` также можно отключить с помощью правил-исключений с модификаторами `$document`, `$content` и `$urlblock`. +`$jsonprune` rules can also be disabled by `$document`, `$content` and `$urlblock` exception rules. :::note -Когда одному и тому же запросу соответствует несколько правил с модификатором `$jsonprune`, они сортируются в лексикографическом порядке: первое правило применяется к исходному ответу, а каждое из оставшихся правил применяется к результату применения предыдущего. +When multiple `$jsonprune` rules match the same request, they are sorted in lexicographical order, the first rule is applied to the original response, and each of the remaining rules is applied to the result of applying the previous one. ::: @@ -1598,7 +1476,7 @@ https://www.site24x7.com/tools/jsonpath-finder-validator.html https://jsonpathfi - `||example.org^$jsonprune=\$..[one\, "two three"]` удаляет все вхождения ключей one и two three в любом месте JSON-документа.
-До +Input ```json { @@ -1613,7 +1491,7 @@ https://www.site24x7.com/tools/jsonpath-finder-validator.html https://jsonpathfi
-После +Output ```json { @@ -1628,7 +1506,7 @@ https://www.site24x7.com/tools/jsonpath-finder-validator.html https://jsonpathfi - `||example.org^$jsonprune=\$.a[?(has ad_origin)]` удаляет всех прямых потомков `a`, которые обладают свойством `ad_origin`.
-До +Input ```json { @@ -1647,7 +1525,7 @@ https://www.site24x7.com/tools/jsonpath-finder-validator.html https://jsonpathfi
-После +Output ```json { @@ -1664,7 +1542,7 @@ https://www.site24x7.com/tools/jsonpath-finder-validator.html https://jsonpathfi - `||example.org^$jsonprune=\$.*.*[?(key-eq 'Some key' 'Some value')]` удаляет все элементы на уровне вложенности 3, обладающие свойством Some key, равным Some value.
-До +Input ```json { @@ -1676,7 +1554,7 @@ https://www.site24x7.com/tools/jsonpath-finder-validator.html https://jsonpathfi
-После +Output ```json { @@ -1687,14 +1565,14 @@ https://www.site24x7.com/tools/jsonpath-finder-validator.html https://jsonpathfi
-**Вложенные выражения JSONPath** +**Nested JSONPath expressions** In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPath expressions may be used as keys in filter expressions. - `||example.org^$jsonprune=\$.elems[?(has "\$.a.b.c")]` удаляет всех прямых потомков `elems`, которые обладают свойством, выбираемым JSONPath-выражением `$.a.b.c`.
-До +Input ```json { @@ -1714,7 +1592,7 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa
-После +Output ```json { @@ -1732,7 +1610,7 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa - `||example.org^$jsonprune=\$.elems[?(key-eq "\$.a.b.c" "abc")]` удаляет всех прямых потомков `elems`, которые обладают свойством, выбираемым выражением JSONPath `$.a.b.c` со значением, равным `"abc"`.
-До +Input ```json { @@ -1750,7 +1628,7 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa
-После +Output ```json { @@ -1766,39 +1644,39 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Ограничения -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. -- Правила с `$jsonprune` не применяются к ответам размером больше 10 МБ. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Совместимость -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: #### **`$xmlprune`** {#xmlprune-modifier} -Правила `$xmlprune` модифицируют ответ на соответствующий запрос, удаляя XML-элементы, которые соответствуют модифицированному выражению [XPath 1.0](https://www.w3.org/TR/1999/REC-xpath-19991116/). Выражение должно возвращать [набор узлов](https://www.w3.org/TR/1999/REC-xpath-19991116/#node-sets). Правила `$xmlprune` не изменяют ответы, которые не являются правильно сформированными XML-документами. +`$xmlprune` rules modify the response to a matching request by removing XML items that match an [XPath 1.0](https://www.w3.org/TR/1999/REC-xpath-19991116/) expression. The expression must return a [node-set](https://www.w3.org/TR/1999/REC-xpath-19991116/#node-sets). `$xmlprune` rules do not modify responses which are not well-formed XML documents. -**Синтаксис** +**Syntax** -- `||example.org^$xmlprune=expression` удаляет из ответа элементы, соответствующие XPath-выражению `expression`. +- `||example.org^$xmlprune=expression` removes items that match the XPath expression `expression` from the response. -Из-за особенностей работы парсинга правил символы `$` и `,` внутри `expression` должны экранироваться символом `\`. +Due to the way rule parsing works, the characters `$` and `,` must be escaped with `\` inside `expression`. **Исключения** -Базовые URL-исключения не должны отключать правила с модификатором `$xmlprune`. Отключить их можно следующим образом: +Basic URL exceptions shall not disable rules with the `$xmlprune` modifier. They can be disabled as described below: -- `@@||example.org^$xmlprune` отключает все правила `$xmlprune` для ответов от URL-адресов, соответствующих `||example.org^`. -- `@@||example.org^$xmlprune=text` отключает все правила `$xmlprune`, у которых значение модификатора `$xmlprune` равно `text`, для ответов с URL-адресов, соответствующих `||example.org^ URL`. +- `@@||example.org^$xmlprune` disables all `$xmlprune` rules for responses from URLs matching `||example.org^`. +- `@@||example.org^$xmlprune=text` disables all `$xmlprune` rules with the value of the `$xmlprune` modifier equal to `text` for responses from URLs matching `||example.org^`. -`$xmlprune` также можно отключить с помощью правил-исключений с модификаторами `$document`, `$content` и `$urlblock`. +`$xmlprune` rules can also be disabled by `$document`, `$content` and `$urlblock` exception rules. :::note -Если одному и тому же запросу соответствует несколько правил `$xmlprune`, они применяются в лексикографическом порядке. +When multiple `$xmlprune` rules match the same request, they are applied in lexicographical order. ::: @@ -1807,7 +1685,7 @@ Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGua - `||example.org^$xmlprune=/bookstore/book[position() mod 2 = 1]` removes odd-numbered books from the bookstore.
-До +Input ```xml @@ -1852,7 +1730,7 @@ Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGua
-После +Output ```xml @@ -1885,7 +1763,7 @@ Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGua - `||example.org^$xmlprune=/bookstore/book[year = 2003]` removes books from the year 2003 from the bookstore.
-До +Input ```xml @@ -1930,7 +1808,7 @@ Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGua
-После +Output ```xml @@ -1960,10 +1838,10 @@ Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGua
-- `||example.org^$xmlprune=//*/@*` удаляет все атрибуты из всех элементов. +- `||example.org^$xmlprune=//*/@*` removes all attributes from all elements.
-До +Input ```xml @@ -1983,7 +1861,7 @@ Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGua
-После +Output ```xml @@ -2004,31 +1882,31 @@ Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGua :::caution Ограничения -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. -- Правила с `$xmlprune` не применяются к ответам размером больше 10 МБ. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Совместимость -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: #### **`$network`** {#network-modifier} -По сути, это правила типа Firewall, позволяющие полностью блокировать или разблокировать доступ к указанному удалённому адресу. +This is basically a Firewall-like rule allowing to fully block or unblock access to a specified remote address. 1. Правила `$network` соответствуют **только IP-адресам**! Вы не можете использовать их, чтобы блокировать или разблокировать доступ к домену. 2. Чтобы сопоставить адрес IPv6, вы должны использовать сжатый синтаксис, например, использовать `[2001:4860:4860::8888]$network` вместо `[2001:4860:4860:0:0:0:0:8888]$network`. -3. Правило белого списка `$network` заставляет AdGuard обходить данные до соответствующей конечной точки, поэтому никакой дальнейшей фильтрации не будет. +3. An allowlist `$network` rule makes AdGuard bypass data to the matching endpoint, hence there will be no further filtering at all. 4. Если часть IP начинается и заканчивается символом `/`, она рассматривается как регулярное выражение. -Рекомендуем ознакомиться [с этой статьёй](#regexp-support) для лучшего понимания регулярных выражений. +We recommend to get acquainted with this [article](#regexp-support) for better understanding of regular expressions. :::caution Ограничения -Модификатор `$network` можно использовать в правилах только вместе с модификаторами `$app` и `$important`, но не с какими-либо другими модификаторами. +The `$network` modifier can only be used in rules together with the `$app` and `$important` modifiers, and not with any other modifiers. ::: @@ -2043,28 +1921,28 @@ Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuar :::info Совместимость -Только в AdGuard для Windows, Mac и Android есть технические возможности для поддержки правил с модификатором `$network`. +Only AdGuard for Windows, Mac, and Android are technically capable of using rules with `$network` modifier. ::: #### **`$permissions`** {#permissions-modifier} -Этот модификатор полностью меняет поведение правила. Когда он применяется, правило не блокирует запрос. Вместо этого будут изменены заголовки ответа. +This modifier completely changes the rule behavior. If it is applied to a rule, the rule will not block the matching request. Response headers will be modified instead. :::info -Чтобы использовать правила этого типа, необходимо базовое понимание слоя безопасности [Feature Policy](https://developer.mozilla.org/ru/docs/Web/HTTP/Permissions_Policy). +In order to use this type of rules, it is required to have a basic understanding of the [Permissions Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Permissions_Policy) security layer. ::: -Для запросов, соответствующих правилу `$permissions`, AdGuard усиливает «политику функций» ответа, добавляя дополнительную политику, равную содержимому модификатора `$permissions`. Правила `$permissions` применяются независимо от правил любого другого типа. На него могут повлиять **только исключения на уровне документа** (см. раздел с примерами), но никак не другие базовые правила. +For the requests matching a `$permissions` rule, AdGuard strengthens response's permissions policy by adding an additional permission policy equal to the `$permissions` modifier contents. `$permissions` rules are applied independently from any other rule type. **Only document-level exceptions** can influence it (see the examples section), but no other basic rules. -**Синтаксис** +**Syntax** `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2093,7 +1971,7 @@ If there are multiple `$permissions` rules that match the same request, multiple ##### `$permissions` modifier limitations {#permissions-modifier-limitations} -:::caution Ограничения +:::caution Limitations Firefox ignores the `Permissions-Policy` header. For more information, see [this issue](https://bugzilla.mozilla.org/show_bug.cgi?id=1694922). @@ -2101,30 +1979,30 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::caution Ограничения -1. В модификаторе `$permissions` запрещён символ `$`. +1. Characters forbidden in the `$permissions` value: `$`. 2. `$permissions` is compatible with a limited set of modifiers: `$domain`, `$important`, `$subdocument`, and [content-type modifiers](#content-type-modifiers). -3. Правила с модификатором `$permissions`, не содержащие [модификаторов типа контента](#content-type-modifiers), будут соответствовать только тем запросам, которые имеют тип контента `document`. +3. `$permissions` rules that do not have any [content-type modifiers](#content-type-modifiers) will match only requests where content type is `document`. ::: :::info Совместимость -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: #### **`$redirect`** {#redirect-modifier} -AdGuard способен перенаправлять веб-запросы на локальный «ресурс». +AdGuard is able to redirect web requests to a local "resource". -**Синтаксис** +**Syntax** -AdGuard использует тот же синтаксис правил фильтрации, что и uBlock Origin. Также он совместим с модификатором ABP `$rewrite=abp-resource`. +AdGuard uses the same filtering rule syntax as uBlock Origin. Also, it is compatible with ABP `$rewrite=abp-resource` modifier. -`$redirect` — это модификатор для [базовых правил фильтрации](#basic-rules), поэтому правила с этим модификатором поддерживают остальные базовые модификаторы, такие как `$domain`, `$third-party`, `$script` и т. д. +`$redirect` is a modifier for the [basic filtering rules](#basic-rules) so rules with this modifier support all other basic modifiers like `$domain`, `$third-party`, `$script`, etc. -Значение модификатора `$redirect` должно быть именем ресурса, который будет использован для переадресации. +The value of the `$redirect` modifier must be the name of the resource that will be used for redirection. ##### Отключение правил `$redirect` @@ -2137,36 +2015,28 @@ More information on redirects and their usage is available [on GitHub](https://g ##### Приоритеты правил `$redirect` {#redirect-rule-priorities} -У правил с `$redirect` более высокий приоритет, чем у обычных базовых правил блокировки. Это означает, что если существует базовое правило блокировки, то правило `$redirect` будет его отменять. У правил белого списка с пометкой `@@` более высокий приоритет, чем у правил `$redirect`. Если базовое правило с модификатором `$important` и правило `$redirect` соответствуют одному и тому же URL-адресу, последнее переопределяется, если оно также не помечено как `$important`. +`$redirect` rules have higher priority than regular basic blocking rules. This means that if there is a basic blocking rule, the `$redirect` rule will override it. Allowlist rules with `@@` mark have higher priority than `$redirect` rules. If a basic rule with the `$important` modifier and the `$redirect` rule matches the same URL, the latter is overridden unless it's also marked as `$important`. -**`$important` > `@@` > `$redirect` > `базовые правила`.** +**In short: `$important` > `@@` > `$redirect` > `basic rules`.** Перейдите [к приоритетам правил](#rule-priorities) для более подробной информации. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Ограничения - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Совместимость -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Правила с модификатором `$redirect` не поддерживаются в AdGuard Content Blocker, AdGuard для iOS и AdGuard для Safari. - `$redirect` в uBlock Origin поддерживает указание приоритета, например, `$redirect=noopjs:42`. AdGuard не поддерживает его и вместо этого просто отбрасывает приоритетный постфикс. ::: #### **`$redirect-rule`** {#redirect-rule-modifier} -По сути это другое имя [`$redirect`](#redirect-modifier), поскольку он имеет те же значения «перенаправления» и почти аналогичную логику. Разница в том, что `$redirect-rule` применяется только в том случае, если целевой запрос заблокирован другим базовым правилом. +This is basically an alias to [`$redirect`](#redirect-modifier) since it has the same "redirection" values and the logic is almost similar. The difference is that `$redirect-rule` is applied only in the case when the target request is blocked by a different basic rule. Перейдите [к приоритетам правил](#rule-priorities) для более подробной информации. -Отключение `$redirect-rule` работает точно так же, как для обычных правил `$redirect`. Даже более того, `@@||example.org^$redirect` будет отключать как правило `$redirect`, так и `$redirect-rule`. +Negating `$redirect-rule` works exactly the same way as for regular `$redirect` rules. Even more than that, `@@||example.org^$redirect` will negate both `$redirect` and `$redirect-rule` rules. **Примеры** @@ -2175,21 +2045,21 @@ In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not su ||example.org^$redirect-rule=noopjs ``` -В этом случае только запросы к `example.org/script.js` будут перенаправлены на `noopjs`. Все остальные запросы к `example.org` останутся без изменений. +In this case, only requests to `example.org/script.js` will be "redirected" to `noopjs`. All other requests to `example.org` will be kept intact. :::info Совместимость -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: #### **`$referrerpolicy`** {#referrerpolicy-modifier} -These rules allow overriding of a page's [referrer policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy). В ответах на соответствующие запросы все заголовки `Referrer-Policy` заменит один заголовок со значением, равным значению модификатора правила сопоставления. Если ответ содержит HTML-документ с тегом `)[\s\S]*<\/VAST>/\$1<\/VAST>/i ``` -У этого правила три части: +There are three parts in this rule: - `regexp` (регулярное выражение) — `()(.|\s)*<\/VAST>` - `replacement` (замена) — `\$1<\/VAST>` где `$` экранируется @@ -2565,35 +2371,36 @@ You can see how this rule works here: http://regexr.com/3cesk :::caution Ограничения -Правила с модификатором `$replace` могут быть использованы [**только в доверенных фильтрах**](#trusted-filters). +Rules with `$replace` modifier can be used [**only in trusted filters**](#trusted-filters). ::: :::info Совместимость -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Другие расширения не могут модифицировать содержимое страниц на сетевом уровне, поэтому там эти правила не работают. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -Правила `$urltransform` позволяют изменять URL-адрес запроса, заменяя текст, соответствующий регулярному выражению. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. -**Функции** +**Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. -- `$urltransform` не будет применяться, если исходный URL-адрес заблокирован другими правилами. -- `$urltransform` будет применяться перед правилами `$removeparam`. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. +- `$urltransform` will not be applied if the original URL is blocked by other rules. +- `$urltransform` will be applied before `$removeparam` rules. -Значение `$urltransform` может быть пустым для правил исключений. +The `$urltransform` value can be empty for exception rules. -**Несколько правил, соответствующих одному запросу** +**Multiple rules matching a single request** -Если несколько правил `$urltransform` соответствуют одному запросу, мы применим каждое из них. **Правила будут применяться в алфавитном порядке.** +If multiple `$urltransform` rules match a single request, we will apply each of them. **The order is defined alphabetically.** -**Синтаксис** +**Syntax** -Синтаксис `$urltransform` аналогичен замене регулярными выражениями [в Perl](http://perldoc.perl.org/perlrequick.html#Search-and-replace). +`$urltransform` syntax is similar to replacement with regular expressions [in Perl](http://perldoc.perl.org/perlrequick.html#Search-and-replace). ```text urltransform = "/" regexp "/" replacement "/" modifiers @@ -2603,17 +2410,7 @@ urltransform = "/" regexp "/" replacement "/" modifiers - **`replacement`** — строка, которая будет использована для замены строки в соответствии с `regexp`. - **`modifiers `** — флаги регулярных выражений. Например, `i` — поиск без учёта регистра, или `s` — режим одной строки. -В значении `$urltransform` необходимо экранировать два символа: запятую `,` и знак доллара `$`. Use the backslash character `\` for this. Например, экранированная запятая будет выглядеть так: `\,`. - -**Изменение происхождения** - -:::info Совместимость - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). +In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. **Примеры** @@ -2621,13 +2418,13 @@ As stated above, normally `$urltransform` rules are only allowed to change the p ||example.org^$urltransform=/(pref\/).*\/(suf)/\$1\$2/i ``` -У этого правила три части: +There are three parts in this rule: - `regexp` — `(pref\/).*\/(suf)`; -- `replacement` — `\$1\$2`, где `$` экранирован; +- `replacement` — `\$1\$2` where `$` is escaped; - `modifiers` (флаги регулярных выражений) — `i` для поиска без учёта регистра -**Несколько правил с `$urltransform`** +**Multiple `$urltransform` rules** 1. `||example.org^$urltransform=/X/Y/` 2. `||example.org^$urltransform=/Z/Y/` @@ -2636,18 +2433,18 @@ As stated above, normally `$urltransform` rules are only allowed to change the p - Правила 1 и 2 будут применены ко всем запросам, отправленным к `example.org`. - Правило 2 отключено для запросов, соответствующих `||example.org/page/`, **но правило 1 при этом всё равно работает!** -**Повторное сопоставление правил после преобразования URL** +**Re-matching rules after transforming the URL** -Если к запросу применяется правило `$urltransform`, все правила будут переоценены относительно нового URL. +If the `$urltransform` rule is applied to a request, all the rules will be re-evaluated against the new URL. -Например, со следующими правилами: +E.g., with the following rules: ```adblock ||example.com^$urltransform=/firstpath/secondpath/ ||example.com/secondpath^ ``` -запрос к `https://example.com/firstpath` будет заблокирован перед отправкой. +the request to `https://example.com/firstpath` will be blocked before it is sent. However, `$urltransform` rules will **not be re-applied** in this case to avoid infinite recursion, e.g., with the following rules: @@ -2656,18 +2453,18 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. -**Отключение правил с `$urltransform`** +**Disabling `$urltransform` rules** -- `@@||example.org^$urltransform` отключит все правила с `$urltransform`, где есть `||example.org^`. -- `@@||example.org^$urltransform=/Z/Y/` отключит правило с `$urltransform=/Z/Y/` для любого запроса, соответствующего `||example.org^`. +- `@@||example.org^$urltransform` will disable all `$urltransform` rules matching `||example.org^`. +- `@@||example.org^$urltransform=/Z/Y/` will disable the rule with `$urltransform=/Z/Y/` for any request matching `||example.org^`. -Правила с `$urltransform` также можно отключить, используя правила-исключения `$document` и `$urlblock`. Но базовые правила исключений без модификаторов не могут этого сделать. Например, `@@||example.com^` не отключит `$urltransform=/X/Y/` для запросов к **example.com**, а `@@||example.com^$urlblock` отключит. +`$urltransform` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$urltransform=/X/Y/` for requests to **example.com**, but `@@||example.com^$urlblock` will. :::caution Ограничения -Правила с модификатором `$urltransform` могут быть использованы [**только в доверенных фильтрах**](#trusted-filters). +Rules with the `$urltransform` modifier can be used [**only in trusted filters**](#trusted-filters). ::: @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -Модификатор `noop` не делает ничего и используется только для того, чтобы улучшить читаемость правил. Он состоит из последовательности символов нижнего подчёркивания (`_`) произвольной длины и может фигурировать в правиле так часто, как это необходимо. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Примеры** @@ -2690,19 +2487,19 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad :::info Совместимость -Правила с модификатором `noop` не поддерживаются в AdGuard Content Blocker. +Rules with `noop` modifier are not supported by AdGuard Content Blocker. ::: #### **`$empty` (устаревший)** {#empty-modifier} -:::caution Скоро устареет +:::caution Deprecation notice -Этот модификатор считается устаревшим. Вместо него теперь используется [модификатор `$redirect`](#redirect-modifier). Правила с `$empty` всё ещё поддерживаются и преобразуются в `$redirect=nooptext`, но в будущем перестанут поддерживаться. +This modifier is deprecated in favor of the [`$redirect` modifier](#redirect-modifier). Rules with `$empty` are still supported and being converted into `$redirect=nooptext` now but the support shall be removed in the future. ::: -Обычно заблокированный запрос выглядит для браузера как ошибка сервера. В случае применения модификатора `$empty` AdGuard эмулирует пустой ответ сервера со статусом `200 OK`. +Usually, blocked requests look like a server error to browser. If you use `$empty` modifier, AdGuard will emulate a blank response from the server with`200 OK` status. **Примеры** @@ -2710,19 +2507,19 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad :::info Совместимость -Правила с модификатором `$empty` не поддерживаются в AdGuard Content Blocker, AdGuard для iOS и AdGuard для Safari. +Rules with `$empty` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: #### **`$mp4` (устаревший)** {#mp4-modifier} -:::caution Скоро устареет +:::caution Deprecation notice -Этот модификатор считается устаревшим. Вместо него теперь используется [модификатор `$redirect`](#redirect-modifier). Правила с `$mp4` всё ещё поддерживаются и преобразуются в `$redirect=noopmp4-1s,media`, но в будущем перестанут поддерживаться. +This modifier is deprecated in favor of the [`$redirect` modifier](#redirect-modifier). Rules with `$mp4` are still supported and being converted into `$redirect=noopmp4-1s,media` now but the support shall be removed in the future. ::: -В качестве ответа на заблокированный запрос AdGuard возвращает короткую видео-заглушку. +As a response to blocked request AdGuard returns a short video placeholder. **Примеры** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,17 +2577,15 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) с доменами, исключаемыми с помощью `~` - [`$match-case`](#match-case-modifier) - [`$method`](#method-modifier) с методами, исключаемыми с помощью `~` -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier) - [`$to`](#to-modifier) - ограниченные модификаторы [сontent-type](#content-type-modifiers) с `~` -При работе с исключаемым доменом, приложением, методом или типом содержимого мы добавляем **1 балл** за существование самого модификатора, независимо от количества исключаемых доменов или типов содержимого. Это связано с тем, что область действия правила и так бесконечно широка. Put simply, by prohibiting multiple domains, content-types, methods or apps, the scope of the rule becomes only minimally smaller. +When dealing with a negated domain, app, method, or content-type, we add **1 point** for the existence of the modifier itself, regardless of the quantity of negated domains or content-types. This is because the rule's scope is already infinitely broad. Put simply, by prohibiting multiple domains, content-types, methods or apps, the scope of the rule becomes only minimally smaller. #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2811,11 +2606,11 @@ This also includes rules that implicitly add all content types: - [`$all`](#all-modifier); -Или правила, которые неявно добавляют модификатор `$document`: +Or rules that implicitly add the modifier `$document`: - [`$popup`](#popup-modifier) -Или некоторые специальные исключения, которые неявно добавляют `$document,subdocument`: +Or some specific exceptions that implicitly add `$document,subdocument`: @@ -2828,25 +2623,25 @@ This also includes rules that implicitly add all content types: - [`$specifichide`](#specifichide-modifier) - [`$urlblock`](#urlblock-modifier) -Или методы, разрешённые модификатором [`$method`](#method-modifier). +Or allowed methods via [`$method`](#method-modifier). -Или правила с [`$header`](#header-modifier). +Or rules with [`$header`](#header-modifier). -Наличие любых модификаторов content-type добавляет `(50 + 50 / N)`, где `N` — количество модификаторов, например: `||example.com^$image,script` добавит `50 + 50 / 2 = 50 + 25 = 75` к общему весу правила. +The presence of any content-type modifiers adds `(50 + 50 / N)`, where `N` is the number of modifiers present, for example: `||example.com^$image,script` will add `50 + 50 / 2 = 50 + 25 = 75` to the total weight of the rule. The `$all` also belongs to this category, because it implicitly adds all content type modifiers, e.g., `$document,subdocument,image,script,media,` + `$popup`. -К этой категории относится и `$popup`, так как в нём неявно добавляется модификатор `$document`. Аналогично, конкретные исключения добавляют `$document,subdocument`. +The `$popup` also belongs to this category, because it implicitly adds the modifier `$document`. Similarly, specific exceptions add `$document,subdocument`. -Если в правиле есть модификатор `$method` с разрешёнными методами, то он добавляет `(50 + 50 / N)`, где `N` — количество разрешённых методов, например: `||example.com^$method=GET|POST|PUT` добавит `50 + 50 / 3 = 50 + 16,6 = 67` к общему весу правила. +If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -Если в правиле есть модификатор `$header`, то он добавляет `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` или `$app` с разрешёнными доменами или приложениями {#priority-category-3} -Домены или приложения, указанные с помощью `$domain` и `$app` соответственно, добавят `100 + 100 / N`, где `N` — количество значений модификатора, например: `||example.com^$domain=example.com|example.org|example.net` добавит `100 + 100 / 3 = 135` или `||example.com^$app=org.example.app1|org.example.app2` добавит `100 + 100 / 2 = 100 + 51 = 151` или `||example.com^$domain=example.com,app=org.example.app1|org.example.app2` добавит `100 + 100/1` (часть $domain) и `100 + 100/2` (часть $app) — в сумме `350`. +Specified domains through `$domain` or specified applications through `$app` add `100 + 100 / N`, where `N` is the number of modifier values for example: `||example.com^$domain=example.com|example.org|example.net` will add `100 + 100 / 3 = 134.3 = 135` or `||example.com^$app=org.example.app1|org.example.app2` will add `100 + 100 / 2 = 151` or `||example.com^$domain=example.com,app=org.example.app1|org.example.app2` will add `100 + 100/1` ($domain part) and `100 + 100/2` ($app part), totaling `350`. -Значения модификаторов regexps или tld будут интерпретироваться как обычные записи вида `example.com` и считаться по одному, например: `||example.com^$domain=example.*` будет добавлено `100 + 100 / 1 = 200` или `||example.com^$domain=example.*|adguard.*` будет добавлено `100 + 100 / 2 = 150`. +Modifier values that are regexps or tld will be interpreted as normal entries of the form `example.com` and counted one by one, for example: `||example.com^$domain=example.*` will add `100 + 100 / 1 = 200` or `||example.com^$domain=example.*|adguard.*` will add `100 + 100 / 2 = 150`. #### Правила `$redirect` {#priority-category-6} @@ -2855,7 +2650,7 @@ The `$all` also belongs to this category, because it implicitly adds all content - [`$redirect`](#redirect-modifier), - [`$redirect-rule`](#redirect-rule-modifier). -Каждое из них добавляет `10^3` к приоритету правила. +Each of which adds `10^3` to rule priority. #### Особые исключения {#priority-category-4} @@ -2870,27 +2665,27 @@ The `$all` also belongs to this category, because it implicitly adds all content - [`$specifichide`](#specifichide-modifier) - [`$urlblock`](#urlblock-modifier) -Каждое из них добавляет `10^4` к приоритету. +Each of which adds `10^4` to the priority. -As well as exception with [`$document modifier`](#document-modifier): because it's an alias for `$elemhide,content,jsinject,urlblock,extension`. Оно добавит `10^4` для каждого модификатора из [верхнего списка](#priority-category-4), `10^4 * 5` в сумме. +As well as exception with [`$document modifier`](#document-modifier): because it's an alias for `$elemhide,content,jsinject,urlblock,extension`. It will add `10^4` for each modifier from [the top list](#priority-category-4), `10^4 * 5` in total. In addition, each of these exceptions implicitly adds the two allowed content-type modifiers `$document,subdocument`. #### Правила белого списка {#priority-category-5} -Модификатор `@@` добавляет `10^5` к приоритету правила. +Modifier `@@` adds `10^5` to rule priority. #### Правила `$important` {#priority-category-7} -Модификатор [`$important`](#important-modifier) добавляет `10^6` к приоритету правила. +Modifier [`$important`](#important-modifier) adds `10^6` to rule priority. #### Правила, для которых нет веса приоритета {#priority-category-extra} -[Прочие модификаторы](#advanced-capabilities), которые должны выполнять дополнительную пост- или предобработку запросов, ничего не добавляют к приоритету правил. +[Other modifiers](#advanced-capabilities), which are supposed to perform additional post- or pre-processing of requests, do not add anything to the rules priority. :::note -Модификатор [`$replace`](#replace-modifier) имеет приоритет над всеми блокирующими правилами категорий 1–3, а также над правилами исключений из категорий 3–5, **, кроме** [`$content`](#content-modifier), поскольку исключение с модификатором `$content` отменяет все правила `$replace`. +The [`$replace`](#replace-modifier) modifier takes precedence over all blocking rules of categories 1-3, as well as exception rules from categories 3-5, **except** [`$content`](#content-modifier), because an exception with the `$content` modifier overrides all `$replace` rules. ::: @@ -2902,23 +2697,23 @@ In addition, each of these exceptions implicitly adds the two allowed content-ty 1. `||example.com^$match-case` - Вес правила: базовый вес + вес модификатора из [категории 1](#priority-category-1): `1 + 1 = 2`. + Rule weight: base weight + weight of the modifier from [category 1](#priority-category-1): `1 + 1 = 2`. 1. `||example.org^$removeparam=p` - Вес правила: базовый вес + 0, так как $removeparam [не участвует](#priority-category-extra) в расчёте приоритета: `1 + 0 = 1`. + Rule weight: base weight + 0, since $removeparam [is not involved](#priority-category-extra) in the priority calculation: `1 + 0 = 1`. 1. `||example.org^$document,redirect=nooptext` - Вес правила: базовый вес + допустимый тип содержимого, [категория 3](#priority-category-3) + $redirect из [категория 6](#priority-category-6): `1 + (100 + 100 / 1) + 1000 = 1201`. + Rule weight: base weight + allowed content type, [category 3](#priority-category-3) + $redirect from [category 6](#priority-category-6): `1 + (100 + 100 / 1) + 1000 = 1201`. 1. `@@||example.org^$removeparam=p,document` - Вес правила: базовый вес + правило белого списка, [категория 5](#priority-category-5) + 0, потому что $removeparam [не участвует](#priority-category-extra) в расчёте приоритета + разрешённый тип контента, [категория 2](#priority-category-2): `1 + 10000 + 0 + (50 + 50 / 1) = 10101`. + Rule weight: base weight + allowlist rule, [category 5](#priority-category-5) + 0 because $removeparam [is not involved](#priority-category-extra) in the priority calculation + allowed content type, [category 2](#priority-category-2): `1 + 10000 + 0 + (50 + 50 / 1) = 10101`. 1. `@@||example.com/ad/*$domain=example.org|example.net,important` - Вес правила: базовый вес + правило белого списка, [категория 5](#priority-category-5) + важное правило, [категория 7](#priority-category-7) + разрешённые домены, [категория 3](#priority-category-3): `1 + 10000 + 1000000 + (100 + 100 / 2) = 1010152`. + Rule weight: base weight + allowlist rule, [category 5](#priority-category-5) + important rule, [category 7](#priority-category-7) + allowed domains, [category 3](#priority-category-3): `1 + 10000 + 1000000 + (100 + 100 / 2) = 1010152`. 1. `@@||example.org^$document` без дополнительных модификаторов — это псевдоним для `@@|||example.com^$elemhide,content,jsinject,urlblock,extension` @@ -2928,22 +2723,22 @@ In addition, each of these exceptions implicitly adds the two allowed content-ty Rule weight: base weight + allowed content type, [category 2](#priority-category-2) + allowed domain, [category 3](#priority-category-3) + denyallow, [category 1](#priority-category-1): `1 + (50 + 50/1) + (100 + 100 / 1) + 1 = 303`. -1. `||example.com^$all` — псевдоним для `||example.com^$document,subdocument,image,script,media и т. д. + $popup` +1. `||example.com^$all` — alias to `||example.com^$document,subdocument,image,script,media,etc. + $popup` - Вес правила: базовый вес + всплывающее окно ([категория 1](#priority-category-1)) + разрешённые типы контента ([категория 2](#priority-category-2)): `1 + 1 + (50 + 50/12) = 55`. + Rule weight: base weight + popup ([category 1](#priority-category-1)) + allowed content types ([category 2](#priority-category-2)): `1 + 1 + (50 + 50/12) = 55`. ## Другие правила {#non-basic-rules} -Базовых правил может быть недостаточно для блокировки рекламы. Иногда для этого требуется скрыть какой-нибудь элемент или изменить часть HTML-кода страницы, при этом ничего не сломав. Для этого предназначены правила, описанные в данном разделе. +However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Категории \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------- |:------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Скрытие элементов](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS-правила](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Расширенный CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Фильтрация HTML](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Скриптлеты](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Категории \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------------- |:------------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Скрытие элементов](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS-правила](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Расширенный CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Фильтрация HTML](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Скриптлеты](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2956,17 +2751,17 @@ In addition, each of these exceptions implicitly adds the two allowed content-ty :::info -Для работы с косметическими правилами необходимы знания HTML и CSS. So, if you want to learn how to make such rules, we recommend to get acquainted with [this documentation](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_started/What_is_CSS). +Work with non-basic rules requires the basic knowledge of HTML and CSS. So, if you want to learn how to make such rules, we recommend to get acquainted with [this documentation](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_started/What_is_CSS). ::: ### Правила скрытия элементов {#cosmetic-elemhide-rules} -Правила скрытия элементов предназначены, как это следует из их названия, для скрытия элементов веб-страниц. По сути это аналогично применению стиля `{ display: none; }` к выбранному элементу. +Element hiding rules are used to hide the elements of web pages. It is similar to applying `{ display: none; }` style to selected element. -Правила скрытия элементов работают по-разному, и их приоритет меняется [в зависимости от платформы](#cosmetic-rules-priority). +Element hiding rules may operate differently [depending on the platform](#cosmetic-rules-priority). -#### Синтаксис +#### Syntax ```text rule = [domains] "##" selector @@ -2976,65 +2771,65 @@ domains = [domain0, domain1[, ...[, domainN]]] - **`selector`** — [CSS-селектор](https://developer.mozilla.org/en-US/docs/Web/Guide/CSS/Getting_Started/Selectors), задающий элементы, которые должны быть скрыты. - **`domains`** — ограничение на домены, на страницах которых будет применено правило. -Если вы хотите ограничить область действия одним или более доменами, просто перечислите их через запятую. Например: `example.org,example.com##selector`. +If you want to limit the rule application area to certain domains, just enter them separated with commas. For example: `example.org,example.com##selector`. -Это правило будет работать также на всех поддоменах `example.org` и `example.com`. +This rule will be also applied to all subdomains of `example.org` and `example.com`. -Если вы хотите, чтобы правило не применялось к определённым доменам, начните доменное имя со знака `~`. Например: `~example.org##selector`. +Если вы хотите, чтобы правило не применялось к определённым доменам, начните доменное имя со знака `~`. For example: `~example.org##selector`. -Вы можете использовать оба подхода в одном правиле. Например, правило `example.org,~subdomain.example.org##domain` будет работать для домена `example.org` и всех его поддоменов, **кроме `subdomain.example.org`**. +You can use both approaches in a single rule. For example, `example.org,~subdomain.example.org##domain` will work for `example.org` and all subdomains, **except `subdomain.example.org`**. :::note -Правила скрытия не зависят друг от друга. Если в фильтре есть правило `example.org##selector` и вы добавляете правило `~example.org##selector`, то оба этих правила будут применены независимо друг от друга. +Element hiding rules are not dependent on each other. If there is a rule `example.org##selector` in the filter and you add `~example.org##selector` both rules will be applied independently. ::: **Примеры** -- `example.com##div.textad` скроет элемент `div` с классом `textad` на домене `example.com` и всех его поддоменах. +- `example.com##div.textad` — hides a `div` with the class `textad` at `example.com` and all subdomains. - `example.com,example.org###adblock` скроет элемент с атрибутом `id` равным `adblock` на доменах `example.com`, `example.org` и всех их поддоменах. -- `~example.com##.textad` скроет элемент с классом `textad` на всех доменах, кроме `example.com` и всех его поддоменов. +- `~example.com##.textad` — hides an element with the class `textad` at all domains, except `example.com` and its subdomains. **Ограничения** -Safari не поддерживает одновременно разрешённые и запрещённые домены. поэтому правила вида `example.org,~foo.example.org##.textad` не работают в AdGuard для Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Исключения** -Исключения могут отключать некоторые правила на определённых доменах. Они очень похожи на обычные правила-исключения, только вместо `##` нужно использовать `#@#`. +Exceptions can disable some rules on particular domains. They are very similar to usual exception rules, but instead of `##` you have to use `#@#`. -Например, в фильтре есть правило: +For example, there is a rule in filter: ```adblock ##.textad ``` -Если вы хотите отключить его для домена `example.com`, вы можете создать правило исключения: +If you want to disable it for `example.com`, you can create an exception rule: ```adblock example.com#@#.textad ``` -В некоторых случаях может потребоваться отключение всех запрещающих правил. Например, на время тестирования. Для этого воспользуйтесь правилом исключения без указания домена. Это полностью отключит соответствующее правило CSS elemhide для ВСЕХ доменов: +Sometimes, it may be necessary to disable all restriction rules. For example, to conduct tests. To do this, use the exclusion rule without specifying a domain. It will completely disable matching CSS elemhide rule on ALL domains: ```adblock #@#.textad ``` -Правило такого вида даст аналогичный результат: +The same can be achieved by adding this rule: ```adblock *#@#.textad ``` -Применять такие исключения рекомендуется только в случае, когда изменить само правило скрытия невозможно. Во всех остальных случаях лучше изменить исходное правило, используя ограничение на домены. +We recommend to use this kind of exceptions only if it is not possible to change the hiding rule itself. In other cases it is better to change the original rule, using domain restrictions. ### CSS-правила {#cosmetic-css-rules} -Иногда недостаточно просто скрыть какой-либо элемент, чтобы заблокировать рекламу. Например, блокировка рекламного элемента может просто сломать вёрстку сайта. Для таких случаев AdGuard позволяет использовать гораздо более гибкие правила, чем обычные правила скрытия. С помощью таких правил вы можете добавить на страницу практически любой CSS-стиль. +Sometimes, simple hiding of an element is not enough to deal with advertising. For example, blocking an advertising element can just break the page layout. In this case AdGuard can use rules that are much more flexible than hiding rules. With these rules you can basically add any CSS styles to the page. -**Синтаксис** +**Syntax** ```text rule = [domains] "#$#" selector "{" style "}" @@ -3051,37 +2846,37 @@ domains = [domain0, domain1[, ...[, domainN]]] example.com#$#body { background-color: #333!important; } ``` -Это правило применит стиль `background-color: #333!important;` к элементу `body` для домена `example.com` и всех его поддоменов. +This rule will apply a style `background-color: #333!important;` to the `body` element at `example.com` and all subdomains. **Исключения** -По аналогии с правилами скрытия существует специальный тип правил, отключающий действие выбранного правила CSS-стилей для определённых доменов. Синтаксис правил-исключений практически такой же, только маркер `#$#` заменяется на `#@$#`. +Just like with element hiding, there is a type of rules that disable the selected CSS style rule for particular domains. Exception rule syntax is almost the same, you just have to change `#$#` to `#@$#`. -Например, в фильтре есть правило: +For example, there is a rule in filter: ```adblock #$#.textad { visibility: hidden; } ``` -Если вы хотите отключить его для домена `example.com`, вы можете создать правило исключения: +If you want to disable it for `example.com`, you can create an exception rule: ```adblock example.com#@$#.textad { visibility: hidden; } ``` -Применять такие исключения рекомендуется только в случае, когда невозможно изменить само CSS-правило. Во всех остальных случаях лучше изменить исходное правило, используя ограничение на домены. +We recommend to use this kind of exceptions only if it is not possible to change the CSS rule itself. In other cases it is better to change the original rule, using domain restrictions. :::caution Ограничения -Запрещено использование стилей, которые могут приводить к загрузке каких-либо ресурсов. Это означает, что нельзя использовать атрибуты типа ``. +Styles that lead to loading any resource are forbidden. Basically, it means that you cannot use any `` type of value in the style. ::: :::info Совместимость -CSS-правила не поддерживаются в AdGuard Content Blocker. +CSS rules are not supported by AdGuard Content Blocker. -CSS-правила работают по-разному, и их приоритет меняется [в зависимости от платформы](#cosmetic-rules-priority). +CSS rules may operate differently [depending on the platform](#cosmetic-rules-priority). ::: @@ -3101,30 +2896,30 @@ CSS-правила работают по-разному, и их приорит - [Псевдокласс `:not()`](#extended-css-not) - [Псевдокласс `:if-not()` (удалён)](#extended-css-if-not) -Возможностей CSS 3.0 не всегда хватает для блокировки рекламы. Чтобы решить эту проблему, AdGuard расширяет возможности CSS, добавляя поддержку новых псевдоэлементов. Мы разработали отдельную [библиотеку с открытым исходным кодом](https://github.com/AdguardTeam/ExtendedCss) для выбора нестандартных элементов и применения CSS-стилей с расширенными свойствами. +CSS 3.0 is not always enough to block ads. To solve this problem AdGuard extends CSS capabilities by adding support for the new pseudo-elements. We have developed a separate [open-source library](https://github.com/AdguardTeam/ExtendedCss) for non-standard element selecting and applying CSS styles with extended properties. -Идея расширенных возможностей заключается в возможности сопоставлять элементы DOM с селекторами на основе их собственного представления (стиль, текстовое содержимое и т. д.) или отношений с другими элементами. Также есть возможность применять стили с нестандартными свойствами CSS. +The idea of extended capabilities is an opportunity to match DOM elements with selectors based on their own representation (style, text content, etc.) or relations with other elements. There is also an opportunity to apply styles with non-standard CSS properties. -**Область применения** +**Application area** -Расширенные селекторы можно применять в любом косметическом правиле, будь то [правила скрытия](#cosmetic-elemhide-rules) или [CSS-правила](#cosmetic-css-rules). +Extended selectors can be used in any cosmetic rule, whether they are [element hiding rules](#cosmetic-elemhide-rules) or [CSS rules](#cosmetic-css-rules). :::info Совместимость -Правила с расширенными CSS-селекторами не поддерживаются в AdGuard Content Blocker. +Rules with extended CSS selectors are not supported by AdGuard Content Blocker. ::: -**Синтаксис** +**Syntax** -Независимо от того, какие CSS-псевдоклассы вы используете в правилах, вы можете использовать специальные маркеры для принудительного применения этих правил с помощью ExtendedCss. Рекомендуется использовать эти маркеры для всех косметических расширенных CSS-правил, чтобы их было легче отличить. +Regardless of the CSS pseudo-classes you are using in the rule, you can use special markers to force applying these rules by ExtendedCss. It is recommended to use these markers for all extended CSS cosmetic rules so that it was easier to find them. -Синтаксис расширенных CSS-правил: +The syntax for extended CSS rules: - `#?#` — для скрытия элементов, `#@?#` — для исключений - `#$?#` — для CSS-стилей, `#@$?#` — для исключений -**Настоятельно рекомендуем** использовать эти маркеры каждый раз, когда вы используете расширенный CSS-селектор. +We **strongly recommend** using these markers any time when you use an extended CSS selector. **Примеры** @@ -3133,13 +2928,13 @@ CSS-правила работают по-разному, и их приорит - `example.net#?#.banner:matches-css(width: 360px)` — это правило блокирует все элементы `.banner`, которые содержат стиль `width: 360px`. При этом правило будет работать только для домена `example.net` и всех его поддоменов. - `example.net#@?#.banner:matches-css(width: 360px)` — это правило отменяет действие предыдущего правила. -Вы можете применять стандартные CSS-селекторы с помощью библиотеки ExtendedCss, используя маркер правила `#?#`. Например, `#?#div.banner`. +You can apply standard CSS selectors using the ExtendedCss library by using the rule marker `#?#`, e.g. `#?#div.banner`. -Больше [об отладке расширенных селекторов](#selectors-debugging-mode). +Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Некоторые псевдоклассы не требуют селектора перед ними. [Универсальный селектор](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` облегчает чтение расширенного селектора, хотя и не влияет на поведение при подборе. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3171,13 +2966,13 @@ Synonyms `:-abp-has()` is supported by ExtendedCss for better compatibility. ::: -**Синтаксис** +**Syntax** ```text [target]:has(selector) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `selector` — необходимый, стандартный или расширенный CSS-селектор The pseudo-class `:has()` selects the `target` elements that fit to the `selector`. Also the `selector` can start with a combinator. @@ -3248,7 +3043,7 @@ Native implementation does not allow any usage of `:scope` inside the `:has()` a ``` -:::danger Старый синтаксис +:::danger Old syntax [Backward compatible syntax for `:has()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-has) is supported but **not recommended**. @@ -3268,18 +3063,18 @@ The `:contains()` pseudo-class uses the `textContent` element property for match Synonyms `:-abp-contains()` and `:has-text()` are supported for better compatibility. -**Синтаксис** +**Syntax** ```text [target]:contains(match) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `match` — требуется, строка или регулярное выражение для соответствия элементу `textContent`. Также поддерживаются флаги регулярных выражений. **Примеры** -Для таких DOM: +For such DOM: ```html @@ -3295,48 +3090,48 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! регулярное выражение -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! регулярное выражение с флагами -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note -Выбран только `div` с `id=match`, так как следующий элемент не содержит текст, а `banner` — это часть кода, а не текст. +Only the `div` with `id=match` is selected because the next element does not contain any text, and `banner` is a part of code, not a text. ::: -:::danger Старый синтаксис +:::danger Old syntax -[Синтаксис обратной совместимости для `:contains()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-contains) поддерживается, но **не рекомендуется**. +[Backward compatible syntax for `:contains()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-contains) is supported but **not recommended**. ::: #### Псевдокласс `:matches-css()` {#extended-css-matches-css} -Псевдокласс `:matches-css()` позволяет сопоставить элемент по свойствам его текущего стиля. Работа псевдокласса основана на использовании метода [`Window.getComputedStyle()`](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle). +The `:matches-css()` pseudo-class allows to match the element by its current style properties. The work of the pseudo-class is based on using the [`Window.getComputedStyle()`](https://developer.mozilla.org/en-US/docs/Web/API/Window/getComputedStyle) method. -**Синтаксис** +**Syntax** ```text [target]:matches-css([pseudo-element, ] property: pattern) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — необязательный, допустимый стандартный псевдоэлемент, например, `before`, `after`, `first-line` и т. д. - `property` — требуется, название CSS-свойства, которое будет проверено у элемента -- `pattern` — требуется, шаблон значений, который использует то же простое сопоставление с подстановочными знаками, что и в основных правилах фильтрации URL-адресов, или регулярное выражение. Для этого типа соответствия AdGuard не обращает внимание на регистр. В случае с регулярными выражениями шаблон будет выглядеть так: `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. Для этого типа соответствия AdGuard не обращает внимание на регистр. В случае с регулярными выражениями шаблон будет выглядеть так: `/regexp/`. -**Экранирование и снятие специальных символов** +**Special characters escaping and unescaping** -Для **нерегулярных выражений** паттерны `(`,`)`,`[`,`]` должны быть **без экранирования**, например, `:matches-css(background-image:url(data:*))`. +For **non-regexp** patterns `(`,`)`,`[`,`]` must be **unescaped**, e.g. `:matches-css(background-image:url(data:*))`. -Для **регулярных выражений** паттерны `\` должны быть **экранированы**, например, `:matches-css(background-image: /^url\\("data:image\\/gif;base64.+/)`. +For **regexp** patterns `\` should be **escaped**, e.g. `:matches-css(background-image: /^url\\("data:image\\/gif;base64.+/)`. **Примеры** -Для таких DOM: +For such DOM: ```html @@ -3349,7 +3144,7 @@ div:contains(/it .*banner/gi)
``` -`div`-элементы с псевдоэлементом `::before` и с указанным свойством `content` могут быть выбраны любым из этих расширенных селекторов: +the `div` elements with pseudo-element `::before` and with specified `content` property can be selected by any of these extended selectors: ```adblock ! паттерн строки @@ -3364,64 +3159,64 @@ div:matches-css(before, content: /block me/) :::caution Ограничения -Паттерны регулярных выражений **не поддерживают** флаги. +Regexp patterns **do not support** flags. ::: :::info Совместимость -Устаревшие псевдоклассы `:matches-css-before()` и `:matches-css-after()` больше не рекомендуются, но по-прежнему поддерживаются для лучшей совместимости. +Obsolete pseudo-classes `:matches-css-before()` and `:matches-css-after()` are no longer recommended but still are supported for better compatibility. ::: -:::danger Старый синтаксис +:::danger Old syntax -[Синтаксис обратной совместимости для `:matches-css()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-matches-css) поддерживается, но **не рекомендуется**. +[Backward compatible syntax for `:matches-css()`](https://github.com/AdguardTeam/ExtendedCss#old-syntax-matches-css) is supported but **not recommended**. ::: #### Псевдокласс `:matches-attr()` {#extended-css-matches-attr} -Псевдокласс `:matches-attr()` позволяет выбрать элемент по его атрибутам, особенно если они рандомизированы. +The `:matches-attr()` pseudo-class allows selecting an element by its attributes, especially if they are randomized. -**Синтаксис** +**Syntax** ```text [target]:matches-attr("name"[="value"]) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `name` — требуется, простая строка, *или* строка с подстановочным знаком, *или* регулярное выражение для сопоставления имени атрибута - `value` — необязательный, простая строка, *или* строка с подстановочным знаком, *или* регулярное выражение для сопоставления значения атрибута -**Экранирование специальных символов** +**Escaping special characters** -Для паттернов **регулярных выражений** `"` и `\` должны быть **экранированы**, например, `div:matches-attr(class=/[\\w]{5}/)`. +For **regexp** patterns `"` and `\` should be **escaped**, e.g. `div:matches-attr(class=/[\\w]{5}/)`. **Примеры** -`div:matches-attr("ad-link")` выбирает элемент `div#target1`: +`div:matches-attr("ad-link")` selects the element `div#target1`: ```html
``` -`div:matches-attr("data-*"="adBanner")` выбирает элемент `div#target2`: +`div:matches-attr("data-*"="adBanner")` selects the element `div#target2`: ```html
``` -`div:matches-attr(*unit*=/^click$/)` выбирает элемент `div#target3`: +`div:matches-attr(*unit*=/^click$/)` selects the element `div#target3`: ```html
``` -`*:matches-attr("/.{5,}delay$/"="/^[0-9]*$/")` выбирает элемент `#target4`: +`*:matches-attr("/.{5,}delay$/"="/^[0-9]*$/")` selects the element `#target4`: ```html @@ -3432,37 +3227,37 @@ div:matches-css(before, content: /block me/) :::caution Ограничения -Паттерны регулярных выражений **не поддерживают** флаги. +Regexp patterns **do not support** flags. ::: #### Псевдокласс `:matches-property()` {#extended-css-property} -Псевдокласс `:matches-property()` позволяет выбирать элемент, сопоставляя его свойства. +The `:matches-property()` pseudo-class allows selecting an element by matching its properties. -**Синтаксис** +**Syntax** ```text [target]:matches-property("name"[="value"]) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `name` — требуется, простая строка, *или* строка с подстановочным знаком, *или* регулярное выражение для сопоставления имени свойства элемента - `value` — необязательный, простая строка, *или* строка с подстановочным знаком, *или* регулярное выражение для сопоставления значения свойства элемента -**Экранирование специальных символов** +**Escaping special characters** -Для паттернов **регулярных выражений** `"` и `\` должны быть экранированы, например, `div:matches-property(prop=/[\\w]{4}/)`. +For **regexp** patterns `"` and `\` must be escaped, e.g. `div:matches-property(prop=/[\\w]{4}/)`. :::note -Паттерны регулярных выражений поддерживаются в `name` для любого свойства в цепочке, например, `prop./^unit[\\d]{4}$/.type`. +Regexp patterns are supported in `name` for any property in chain, e.g. `prop./^unit[\\d]{4}$/.type`. ::: **Примеры** -Элемент с такими свойствами: +An element with such properties: ```javascript divProperties = { @@ -3482,7 +3277,7 @@ divProperties = { }; ``` -может быть выбран любым из этих расширенных селекторов: +can be selected by any of these extended selectors: ```adblock div:matches-property(check.track) @@ -3496,9 +3291,9 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip Для разработчиков фильтров +:::tip For filters maintainers -Чтобы проверить свойства конкретного элемента, сделайте следующее: +To check properties of a specific element, do the following: 1. Проверьте элемент страницы или выберите его в Инструментах разработчика браузера во вкладке `Элементы` 1. Запустите `console.dir($0)` во вкладке `Консоль` @@ -3507,15 +3302,15 @@ div:matches-property(memoizedProps._owner.src=/ad/) :::caution Ограничения -Паттерны регулярных выражений **не поддерживают** флаги. +Regexp patterns **do not support** flags. ::: #### Псевдокласс `:xpath()` {#extended-css-xpath} -Псевдокласс `:xpath()` позволяет выбирать элементы согласно выражению XPath. +The `:xpath()` pseudo-class allows selecting an element by evaluating an XPath expression. -**Синтаксис** +**Syntax** ```text [target]:xpath(expression) @@ -3526,22 +3321,22 @@ div:matches-property(memoizedProps._owner.src=/ad/) ##### Ограничения `:xpath()` {#extended-css-xpath-limitations} -`target` можно опустить, поэтому использовать его необязательно. Для любого другого псевдокласса это будет означать «применить ко *всем* узлам DOM», но в случае `:xpath()` это просто означает «применить к *целым* документам», и такое применение значительно замедляет выбор элементов. Вот почему такие правила, как `#?#:xpath(expression)`, ограничены поиском внутри тега `body`. Например, правило `#?#:xpath(//div[@data-st-area=\'Advert\'])` парсится как `#?#body:xpath(//div[@data-st- area=\'Advert\'])`. +`target` can be omitted so it is optional. For any other pseudo-class that would mean "apply to *all* DOM nodes", but in case of `:xpath()` it just means "apply to the *whole* document", and such applying slows elements selecting significantly. That's why rules like `#?#:xpath(expression)` are limited to looking inside the `body` tag. For example, rule `#?#:xpath(//div[@data-st-area=\'Advert\'])` is parsed as `#?#body:xpath(//div[@data-st-area=\'Advert\'])`. -Расширенные селекторы с `target`, определённым как *любой* селектор, — `*:xpath(expression)` — всё ещё можно использовать, но не рекомендуется. Поэтому следует уточнить `target`. +Extended selectors with defined `target` as *any* selector — `*:xpath(expression)` — can still be used but it is not recommended, so `target` should be specified instead. -Корректно работает только в конце селектора, за исключением псевдокласса [:remove()](#remove-pseudos). +Works properly only at the end of selector, except for [pseudo-class :remove()](#remove-pseudos). **Примеры** -`:xpath(//*[@class="banner"])` выбирает элемент `div#target1`: +`:xpath(//*[@class="banner"])` selects the element `div#target1`: ```html ``` -`:xpath(//*[@class="inner"]/..)` выбирает элемент `div#target2`: +`:xpath(//*[@class="inner"]/..)` selects the element `div#target2`: ```html @@ -3552,7 +3347,7 @@ div:matches-property(memoizedProps._owner.src=/ad/) #### Псевдокласс `:nth-ancestor()` {#extended-css-nth-ancestor} -Псевдокласс `:nth-ancestor()` позволяет искать *n-ного* предка по отношению к ранее выбранному элементу. +The `:nth-ancestor()` pseudo-class allows to lookup the *nth* ancestor relative to the previously selected element. ```text subject:nth-ancestor(n) @@ -3561,22 +3356,22 @@ subject:nth-ancestor(n) - `subject` — обязателен. Стандартный или расширенный CSS-селектор - `n` — обязателен. Число >= 1 и < 256, расстояние до нужного родителя от элемента, выбранного `subject` -**Синтаксис** +**Syntax** ```text subject:nth-ancestor(n) ``` -- `subject` — обязателен. Стандартный или расширенный CSS-селектор +- `subject` — required, standard or extended CSS selector - `n` — обязателен. Число >= 1 и < 256, расстояние до нужного родителя от элемента, выбранного `subject` ##### Ограничения `:nth-ancestor()` {#extended-css-nth-ancestor-limitations} -Псевдокласс `:nth-ancestor()` не поддерживается внутри аргумента псевдокласса [`:not()`](#extended-css-not). +The `:nth-ancestor()` pseudo-class is not supported inside the argument of the [`:not()` pseudo-class](#extended-css-not). **Примеры** -Для таких DOM: +For such DOM: ```html @@ -3593,13 +3388,13 @@ subject:nth-ancestor(n) ``` -`.child:nth-ancestor(1)` выбирает элемент `div#target1`, `div[class="inner"]:nth-ancestor(3)` выбирает элемент `div#target2`. +`.child:nth-ancestor(1)` selects the element `div#target1`, `div[class="inner"]:nth-ancestor(3)` selects the element `div#target2`. #### Псевдокласс `:upward()` {#extended-css-upward} The `:upward()` pseudo-class allows to lookup the ancestor relative to the previously selected element. -**Синтаксис** +**Syntax** ```text subject:upward(ancestor) @@ -3616,7 +3411,7 @@ The `:upward()` pseudo-class is not supported inside the argument of the [`:not( **Примеры** -Для таких DOM: +For such DOM: ```html @@ -3641,7 +3436,7 @@ Sometimes, it is necessary to remove a matching element instead of hiding it or **Pseudo-class `:remove()` can be placed only at the end of a selector.** -**Синтаксис** +**Syntax** ```text ! pseudo-class @@ -3659,7 +3454,7 @@ The `:remove()` pseudo-class is limited to work properly only at the end of sele For applying the `:remove()` pseudo-class to any element, the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` should be used. Otherwise such extended selector may be considered as invalid, e.g. `.banner > :remove()` is not valid for removing any child element of `banner` class element, so it should look like `.banner > *:remove()`. -Если используется псевдокласс `:remove()` или псевдосвойство `remove`, все свойства стиля игнорируются, кроме псевдосвойства [`debug`](#selectors-debug-mode). +If the `:remove()` pseudo-class or the `remove` pseudo-property is used, all style properties are ignored except for the [`debug` pseudo-property](#selectors-debug-mode). **Примеры** @@ -3673,34 +3468,34 @@ div[class]:has(> a > img) { remove: true; } :::note -Правила с псевдосвойством `remove` должны использовать маркер `#$?#`: `$` для синтаксиса правил CSS-стиля, `?` для синтаксиса ExtendedCss. +Rules with the `remove` pseudo-property must use `#$?#` marker: `$` for CSS-style rule syntax, `?` for ExtendedCss syntax. ::: #### Псевдокласс `:is()` {#extended-css-is} -Псевдокласс `:is()` позволяет сопоставить любой элемент, который может быть выбран любым из переданных ему селекторов. Некорректные селекторы пропускаются, и псевдокласс работает с допустимыми селекторами без каких-либо ошибок. Наша реализация [нативного`:is()` псевдокласса](https://developer.mozilla.org/en-US/docs/Web/CSS/:is). +The `:is()` pseudo-class allows to match any element that can be selected by any of selectors passed to it. Invalid selectors are skipped and the pseudo-class deals with valid ones with no error thrown. Our implementation of the [native `:is()` pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:is). -**Синтаксис** +**Syntax** ```text [target]:is(selectors) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов -- `selectors` — [*щадящий список*](https://drafts.csswg.org/selectors-4/#typedef-forgiving-selector-list) стандартных и расширенных селекторов. Для расширенных селекторов поддерживаются только составные селекторы, а не сложные. +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element +- `selectors` — [*щадящий список*](https://drafts.csswg.org/selectors-4/#typedef-forgiving-selector-list) стандартных и расширенных селекторов. For extended selectors, only compound selectors are supported, not complex. ##### Ограничения `:is()` {#extended-css-is-limitations} -Правила с псевдоклассом `:is()` должны использовать [нативную реализацию `:is()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:is), если они используют маркер `##` и если это возможно, то есть без других расширенных селекторов внутри. To force applying ExtendedCss rules with `:is()`, use `#?#`/`#$?#` marker explicitly. +Rules with the `:is()` pseudo-class must use the [native implementation of `:is()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:is) if rules use `##` marker and it is possible, i.e. with no other extended selectors inside. To force applying ExtendedCss rules with `:is()`, use `#?#`/`#$?#` marker explicitly. If the `:is()` pseudo-class argument `selectors` is an extended selector, due to the way how the `:is()` pseudo-class is implemented in ExtendedCss v2.0, it is impossible to apply it to the top DOM node which is `html`, i.e. `#?#html:is()` does not work. So if `target` is not defined or defined as the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, the extended pseudo-class applying is limited to **`html`'s children**, e.g. rules `#?#:is(...)` and `#?#*:is(...)` are parsed as `#?#html *:is(...)`. Please note that there is no such limitation for a standard selector argument, i.e. `#?#html:is(.locked)` works fine. -[Сложные селекторы](https://www.w3.org/TR/selectors-4/#complex) с расширенными псевдоклассами не поддерживаются в качестве аргумента `selectors` для псевдокласса `:is()` — разрешены только [составные](https://www.w3.org/TR/selectors-4/#compound). Ознакомьтесь с примерами, чтобы разобраться в деталях. +[Complex selectors](https://www.w3.org/TR/selectors-4/#complex) with extended pseudo-classes are not supported as `selectors` argument for `:is()` pseudo-class, only [compound ones](https://www.w3.org/TR/selectors-4/#compound) are allowed. Check examples below for more details. **Примеры** -`#container *:is(.inner, .footer)` выбирает только элемент `div#target1`: +`#container *:is(.inner, .footer)` selects only the element `div#target1`: ```html @@ -3713,7 +3508,7 @@ If the `:is()` pseudo-class argument `selectors` is an extended selector, due to ``` -Из-за ограничений `:is(*:not([class]) > .banner)'` не работает, но `:is(*:not([class]):has(> .banner))` можно использовать вместо него для выбора элемента `div#target2`: +Due to limitations `:is(*:not([class]) > .banner)'` does not work but `:is(*:not([class]):has(> .banner))` can be used instead of it to select the element `div#target2`: ```html @@ -3725,30 +3520,30 @@ If the `:is()` pseudo-class argument `selectors` is an extended selector, due to #### Псевдокласс `:not()` {#extended-css-not} -Псевдокласс `:not()` позволяет выбрать элементы, которые *не соответствуют* селекторам, переданным в качестве аргумента. Неправильные селекторы аргументов не допускаются, и будет выдана ошибка. Наша реализация [псевдокласса`:not()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:not). +The `:not()` pseudo-class allows to select elements which are *not matched* by selectors passed as argument. Invalid argument selectors are not allowed and error is to be thrown. Our implementation of the [`:not()` pseudo-class](https://developer.mozilla.org/en-US/docs/Web/CSS/:not). -**Синтаксис** +**Syntax** ```text [target]:not(selectors) ``` -- `target` — необязательный, стандартный или расширенный CSS-селектор, может быть пропущен для проверки *любых* элементов +- `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `selectors` — список стандартных или расширенных селекторов ##### Ограничения `:not()` {#extended-css-not-limitations} -Правила с псевдоклассом `:not()` должны использовать [нативную реализацию `:not()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:not), если они используют маркер `##` и если это возможно, то есть без других расширенных селекторов внутри. Чтобы принудительно применить правила ExtendedCss с `:not()`, используйте маркер `#?#`/`#$?#` явно. +Rules with the `:not()` pseudo-class must use the [native implementation of `:not()`](https://developer.mozilla.org/en-US/docs/Web/CSS/:not) if rules use `##` marker and it is possible, i.e. with no other extended selectors inside. To force applying ExtendedCss rules with `:not()`, use `#?#`/`#$?#` marker explicitly. -Если `selectors` аргумент псевдокласса `:not()` — расширенный селектор, то из-за того, как псевдокласс `:not()` реализован в ExtendedCss 2.0, его невозможно применить к верхнему узлу DOM, который является `html`, т.е. `#?#html:not()` не работает. Таким образом, если `target` не определён или определён как [универсальный селектор](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, применение расширенного псевдокласса ограничено **дочерними `html`-элементами**, например, правила `#?#:not(...)` и `#?#*:not(...)` парсятся как `#?#html *:not(...)`. Обратите внимание, что для стандартного аргумента селектора такого ограничения нет, т.е. `#?#html:not(.locked)` работает нормально. +If the `:not()` pseudo-class argument `selectors` is an extended selector, due to the way how the `:not()` pseudo-class is implemented in ExtendedCss v2.0, it is impossible to apply it to the top DOM node which is `html`, i.e. `#?#html:not()` does not work. So if `target` is not defined or defined as the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*`, the extended pseudo-class applying is limited to **`html`'s children**, e.g. rules `#?#:not(...)` and `#?#*:not(...)` are parsed as `#?#html *:not(...)`. Please note that there is no such limitation for a standard selector argument, i.e. `#?#html:not(.locked)` works fine. -Псевдокласс `:not()` рассматривается как стандартный псевдокласс CSS внутри аргумента псевдокласса [`:upward()`](#extended-css-upward), поскольку `:upward()` поддерживает только стандартные селекторы. +The `:not()` is considered as a standard CSS pseudo-class inside the argument of the [`:upward()` pseudo-class](#extended-css-upward) because `:upward()` supports only standard selectors. -«Восходящие» псевдоклассы [`:nth-ancestor()`](#extended-css-nth-ancestor) и [`:upward()`](#extended-css-upward) не поддерживаются внутри аргумента `selectors` для псевдокласса `:not()`. +"Up-looking" pseudo-classes which are [`:nth-ancestor()`](#extended-css-nth-ancestor) and [`:upward()`](#extended-css-upward) are not supported inside `selectors` argument for `:not()` pseudo-class. **Примеры** -`#container > *:not(h2, .text)` выбирает только элемент `div#target1`: +`#container > *:not(h2, .text)` selects only the element `div#target1`: ```html @@ -3763,33 +3558,33 @@ If the `:is()` pseudo-class argument `selectors` is an extended selector, due to :::danger Уведомление об удалении -Псевдокласс `:if-not()` удалён и больше не поддерживается. Правила с ним не работают. +The `:if-not()` pseudo-class is removed and is no longer supported. Правила с ним не работают. ::: -Этот псевдокласс изначально был сокращением для `:not(:has())`. Он поддерживался ExtendedCss для лучшей совместимости с подписками на некоторые фильтры. +This pseudo-class was basically a shortcut for `:not(:has())`. It was supported by ExtendedCss for better compatibility with some filters subscriptions. ### Приоритет косметических правил {#cosmetic-rules-priority} -То, как применяются правила **скрытия элементов** и **CSS-правила**, зависит от платформы. +The way **element hiding** and **CSS rules** are applied is platform-specific. -**В AdGuard для Windows, Mac и Android** мы используем таблицу стилей, встроенную в страницу. Приоритет у косметических правил такой же, как и у любых других таблиц стилей CSS на сайтах. Но есть ограничение: [правила скрытия элементов](#cosmetic-elemhide-rules) и [CSS-правила](#cosmetic-css-rules) не могут обходить встроенные стили. В таких случаях рекомендуется использовать расширенные селекторы или HTML-фильтрацию. +**In AdGuard for Windows, Mac, and Android**, we use a stylesheet injected into the page. The priority of cosmetic rules is the same as any other websites' CSS stylesheet. But there is a limitation: [element hiding](#cosmetic-elemhide-rules) and [CSS rules](#cosmetic-css-rules) cannot override inline styles. In such cases, it is recommended to use extended selectors or HTML filtering. -**В Браузерном расширении AdGuard** используются так называемые «пользовательские таблицы стилей». Их приоритет выше, даже чем у встроенных стилей. +**In AdGuard Browser Extension**, the so called "user stylesheets" are used. They have higher priority than even the inline styles. -**Расширенные CSS-селекторы** используют для работы JavaScript и добавляют встроенные стили сами, поэтому могут игнорировать любой стиль. +**Extended CSS selectors** use JavaScript to work and basically add an inline style themselves, therefore they can override any style. ## Правила фильтрации HTML {#html-filtering-rules} -В большинстве случаев для фильтрации рекламы достаточно базовых и косметических правил. Но иногда необходимо изменить HTML-код самой страницы перед её загрузкой. Для этого применяются правила фильтрации HTML-контента. Они позволяют указать, какие HTML-элементы необходимо вырезать из страницы перед тем, как страница попадёт в браузер. +In most cases, the basis and cosmetic rules are enough to filter ads. But sometimes it is necessary to change the HTML-code of the page itself before it is loaded. This is when you need filtering rules for HTML content. They allow to indicate the HTML elements to be cut out before the browser loads the page. :::info Совместимость -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Такие правила не работают в расширениях для других браузеров, потому что они не могут модифицировать содержимое страниц на сетевом уровне. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: -### Синтаксис +### Syntax ```text selector = [tagName] [attributes] [pseudoClasses] @@ -3810,37 +3605,37 @@ pseudoClasses = pseudoClass *pseudoClass ### Примеры -**HTML-код:** +**HTML code:** ```html ``` -**Правило:** +**Rule:** ```adblock example.org$$script[data-src="banner"] ``` -Это правило удалит из кода страниц все элементы `script` со значением `data-src`, содержащим подстроку `banner`. При этом правило будет работать только для домена `example.org` и всех его поддоменов. +This rule removes all `script` elements with the attribute `data-src` containing the substring `banner`. The rule applies only to `example.org` and all its subdomains. ### Специальные атрибуты -Помимо обычных атрибутов, значение которых проверяется у каждого элемента, существует набор специальных атрибутов правила, которые изменяют способ работы правила. Ниже мы перечислим все эти атрибуты: +In addition to usual attributes, which value is every element checked for, there is a set of special attributes that change the way a rule works. Below there is a list of these attributes: #### `tag-content` -:::caution Скоро устареет +:::caution Deprecation notice -В будущем этот специальный атрибут может перестать поддерживаться. Предпочтительнее использовать псевдокласс `:contains()` там, где это возможно. +This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class where it is available. ::: -Пожалуй, наиболее часто используемый специальный атрибут. Он ограничивает выбор теми элементами, внутренний HTML-код которых (innerHTML) содержит указанную подстроку. +This is the most frequently used special attribute. It limits selection with those elements whose innerHTML code contains the specified substring. -Используйте `""` для экранирования `"`, например: `$$script[tag-content="alert(""this is ad"")"]` +You must use `""` to escape `"`, for instance: `$$script[tag-content="alert(""this is ad"")"]` -Например, рассмотрим такой HTML-код: +For example, take a look at this HTML code: ```html ``` -Следующее правило удалит все `script` элементы с подстрокой `banner` в их коде: +Following rule will delete all `script` elements with a `banner` substring in their code: ```adblock $$script[tag-content="banner"] ``` -:::caution Ограничения +:::caution Limitations -Специальный атрибут `tag-content` не должен появляться в селекторе слева от комбинатора `>`. +The `tag-content` special attribute must not appear in a selector to the left of a `>` combinator. ::: #### `wildcard` -:::caution Скоро устареет +:::caution Deprecation notice -В будущем этот специальный атрибут может перестать поддерживаться. Предпочтительнее использовать псевдокласс `:contains()` там, где это возможно. +This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class where it is available. ::: This special attribute works almost like `tag-content` and allows you to check the innerHTML code of the document. Rule will check if HTML code of the element fits to the [search pattern](https://en.wikipedia.org/wiki/Glob_(programming)). -Используйте `""` для экранирования `"`, например: `$$script[wildcard=""banner""]` +You must use `""` to escape `"`, for instance: `$$script[wildcard=""banner""]` -Например: `$$script[wildcard="*banner*text*"]` +For example: `$$script[wildcard="*banner*text*"]` -Оно проверяет, что код элемента содержит две последовательные подстроки `banner` и `text`. +It checks if the element code contains the two consecutive substrings `banner` and `text`. -:::caution Ограничения +:::caution Limitations -Специальный атрибут `wildcard` не должен появляться в селекторе слева от комбинатора `>`. +The `wildcard` special attribute must not appear in a selector to the left of a `>` combinator. ::: #### `max-length` -:::caution Скоро устареет +:::caution Deprecation notice -В будущем этот специальный атрибут может перестать поддерживаться. Предпочтительнее использовать псевдокласс `:contains()` там, где это возможно. +This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class with a regular expression where it is available. ::: -Задает максимальную длину содержимого HTML-элемента. Если этот параметр задан и длина содержимого превышает заданное значение, правило не применяется к элементу. +Specifies the maximum length for content of HTML element. If this parameter is set and the content length exceeds the value, a rule does not apply to the element. -**Значение по умолчанию** +**Default value** -Если этот параметр не задан, то `max-length` считается равным 8192. +If this parameter is not specified, the `max-length` is considered to be 8192. Например: @@ -3902,23 +3697,23 @@ This special attribute works almost like `tag-content` and allows you to check t $$div[tag-content="banner"][max-length="400"] ``` -Это правило удалит все элементы `div`, код которых содержит подстроку `banner` и длина которых не превышает `400` символов. +This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which does not exceed `400` characters. -:::caution Ограничения +:::caution Limitations -Специальный атрибут `max-length` не должен появляться в селекторе слева от комбинатора `>`. +The `max-length` special attribute must not appear in a selector to the left of a `>` combinator. ::: #### `min-length` -:::caution Скоро устареет +:::caution Deprecation notice -В будущем этот специальный атрибут может перестать поддерживаться. Предпочтительнее использовать псевдокласс `:contains()` там, где это возможно. +This special attribute may become unsupported in the future. Prefer using the `:contains()` pseudo-class with a regular expression where it is available. ::: -Задаёт минимальную длину содержимого HTML-элемента. Если этот параметр задан, и длина содержимого меньше заданного значения — правило не применяется к элементу. +Specifies the minimum length for content of HTML element. If this parameter is set and the content length is less than preset value, a rule does not apply to the element. Например: @@ -3926,11 +3721,11 @@ $$div[tag-content="banner"][max-length="400"] $$div[tag-content="banner"][min-length="400"] ``` -Это правило удалит все элементы `div`, код которых содержит подстроку `banner` и длина которых превышает `400` символов. +This rule will remove all the `div` elements, whose code contains the substring `banner` and the length of which exceeds `400` characters. -:::caution Ограничения +:::caution Limitations -Специальный атрибут `min-length` не должен появляться в селекторе слева от комбинатора `>`. +The `min-length` special attribute must not appear in a selector to the left of a `>` combinator. ::: @@ -3938,7 +3733,7 @@ $$div[tag-content="banner"][min-length="400"] #### `:contains()` -##### Синтаксис +##### Syntax ```text :contains(текст без кавычек) @@ -3950,9 +3745,9 @@ $$div[tag-content="banner"][min-length="400"] :contains(/reg(ular)?ex(pression)?/) ``` -:::note Совместимость +:::note Compatibility -`:-abp-contains()` и `:has-text()` являются синонимами `:contains()`. +`:-abp-contains()` and `:has-text()` are synonyms for `:contains()`. ::: @@ -3962,52 +3757,52 @@ The `:contains()` pseudo-class is supported by AdGuard for Windows, Mac, and And ::: -Требует, чтобы внутренний HTML-код элемента содержал указанный текст или соответствовал указанному регулярному выражению. +Requires that the inner HTML of the element contains the specified text or matches the specified regular expression. -:::caution Ограничения +:::caution Limitations -Псевдокласс `:contains()` не должен появляться в селекторе слева от комбинатора `>`. +A `:contains()` pseudo-class must not appear in a selector to the left of a `>` combinator. ::: ### Исключения -По аналогии с правилами скрытия, существует специальный тип правил, отключающий действие выбранного правила HTML-фильтрации для определённых доменов. Синтаксис правил-исключений такой же, только маркер `$$` заменяется на `$@$`. +Similar to hiding rules, there is a special type of rules that disable the selected HTML filtering rule for particular domains. The syntax is the same, you just have to change `$$` to `$@$`. -Например, в фильтре есть правило: +For example, there is a rule in filter: ```adblock $$script[tag-content="banner"] ``` -Если вы хотите отключить его для домена `example.com`, вы можете создать правило исключения: +If you want to disable it for `example.com`, you can create an exception rule: ```adblock example.com$@$script[tag-content="banner"] ``` -В некоторых случаях может потребоваться отключение всех запрещающих правил. Например, на время тестирования. Для этого воспользуйтесь правилом исключения без указания домена. +Sometimes, it may be necessary to disable all restriction rules. For example, to conduct tests. To do this, use the exclusion rule without specifying a domain. ```adblock $@$script[tag-content="banner"] ``` -Применять такие исключения рекомендуется только в случае, когда изменить само правило скрытия невозможно. Во всех остальных случаях лучше изменить исходное правило, используя ограничение на домены. +We recommend to use this kind of exceptions only if it is not possible to change the hiding rule itself. In other cases it is better to change the original rule, using domain restrictions. ## Правила JavaScript {#javascript-rules} -AdGuard поддерживает специальный тип правил, позволяющий вставить любой JavaScript-код на страницы сайтов. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. -Мы **настоятельно рекомендуем** использовать [скриптлеты](#scriptlets) вместо JavaScript-правил везде, где это возможно. JS-правила должны помочь в процессе отладки, но в качестве долгосрочного решения следует использовать скриптлеты. +We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. -**Синтаксис** +**Syntax** ```text rule = [domains] "#%#" script ``` - **`domains`** — ограничение на домены, на страницах которых будет применено правило. Строится по тем же правилам, что и в случае [правил скрытия элементов](#cosmetic-elemhide-rules). -- **`script`** — произвольный JavaScript-код **в одну строку**. +- **`script`** — произвольный javascript-код **в одну строку**. **Примеры** @@ -4015,168 +3810,108 @@ rule = [domains] "#%#" script **Исключения** -По аналогии с правилами скрытия, существует специальный тип правил, отключающий действие выбранного javascript-правила фильтрации для определённых доменов. Синтаксис правил-исключений такой же, только маркер `#%#` заменяется на `#@%#`. +Similar to hiding rules, there is a special type of rules that disable the selected javascript rule for particular domains. The syntax is the same, you just have to change `#%#` to `#@%#`. -Например, в фильтре есть правило: +For example, there is a rule in filter: ```adblock #%#window.__gaq = undefined; ``` -Если вы хотите отключить его для домена `example.com`, вы можете создать правило исключения: +If you want to disable it for `example.com`, you can create an exception rule: ```adblock example.com#@%#window.__gaq = undefined; ``` -В некоторых случаях может потребоваться отключение всех запрещающих правил. Например, на время тестирования. Для этого воспользуйтесь правилом исключения без указания домена. +Sometimes, it may be necessary to disable all restriction rules. For example, to conduct tests. To do this, use the exclusion rule without specifying a domain. ```adblock #@%#window.__gaq = undefined; ``` -Применять такие исключения рекомендуется только в случае, когда изменить само правило скрытия невозможно. Во всех остальных случаях лучше изменить исходное правило, используя ограничение на домены. +We recommend to use this kind of exceptions only if it is not possible to change the hiding rule itself. In other cases it is better to change the original rule, using domain restrictions. :::caution Ограничения -Правила JavaScript можно использовать [**только в доверенных фильтрах**](#trusted-filters). +JavaScript rules can be used [**only in trusted filters**](#trusted-filters). ::: :::info Совместимость -JavaScript-правила не поддерживаются в AdGuard Content Blocker. +JavaScript rules are not supported by AdGuard Content Blocker. ::: ## Правила скриптлета {#scriptlets} -Скриптлет — это функция JavaScript с расширенными возможностями для блокировки контента. Такие функции могут использоваться в декларативной манере в правилах фильтрации AdGuard. +Scriptlet is a JavaScript function that provides extended capabilities for content blocking. These functions can be used in a declarative manner in AdGuard filtering rules. :::note -AdGuard поддерживает множество различных скриптлетов. Чтобы добиться совместимости между различными блокировщиками, мы также поддерживаем синтаксис uBO и ABP. +AdGuard supports a lot of different scriptlets. In order to achieve cross-blocker compatibility, we also support syntax of uBO and ABP. ::: -**Синтаксис правил блокировки** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** (обязательно) — это имя скриптлета из библиотеки скриптлетов AdGuard +- **`arguments`** (опционально) — это список аргументов в формате `string` (другие типы аргументов не поддерживаются) **Примеры** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Синтаксис правил исключений** - -Правила исключений могут отключать некоторые скриптлеты на определённых доменах. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Примеры** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` +Learn more about [how to debug scriptlets](#debug-scriptlets). -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` - -Подробнее [об отладке скриптлетов](#debug-scriptlets). - -Более подробную информацию о скриптлетах можно найти [на GitHub](https://github.com/AdguardTeam/Scriptlets#scriptlets). +More information about scriptlets can be found [on GitHub](https://github.com/AdguardTeam/Scriptlets#scriptlets). :::info Совместимость -Скриптлеты не поддерживаются в AdGuard Content Blocker. - -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Предыдущие версии поддерживали только правила исключений, которые отключали определённые скриптлеты. +Scriptlet rules are not supported by AdGuard Content Blocker. ::: ### Доверенные скриптлеты {#trusted-scriptlets} -Доверенные скриптлеты — это [скриптлеты](#scriptlets) с расширенной функциональностью. У них тот же синтаксис и ограничения. У имён доверенных скриптлетов есть префикс `trust-`, например, `trust-set-cookie`, чтобы их было легко отличить от обычных скриптлетов. +Trusted scriptlets are [scriptlets](#scriptlets) with extended functionality. It means the same syntax and restrictions. Trusted scriptlet names are prefixed with `trusted-`, e.g. `trusted-set-cookie`, to be easily distinguished from common scriptlets. :::note -Доверенные скриптлеты несовместимы с другими блокировщиками рекламы, кроме AdGuard. +Trusted scriptlets are not compatible with other ad blockers except AdGuard. ::: :::caution Ограничения -Доверенные скриптлеты можно использовать [**только в доверенных фильтрах**](#trusted-filters). +Trusted scriptlets rules can be used [**only in trusted filters**](#trusted-filters). ::: :::info Совместимость -Доверенные скриптлеты не поддерживаются в AdGuard Content Blocker. +Trusted scriptlets rules are not supported by AdGuard Content Blocker. ::: -Подробнее [об отладке скриптлетов](#debug-scriptlets). +Learn more about [how to debug scriptlets](#debug-scriptlets). -Более подробную информацию о доверенных скриптлетах можно найти [на GitHub](https://github.com/AdguardTeam/Scriptlets#trusted-scriptlets). +More information about trusted scriptlets can be found [on GitHub](https://github.com/AdguardTeam/Scriptlets#trusted-scriptlets). ## Модификаторы для небазовых правил {#non-basic-rules-modifiers} -Поведение любого правила можно изменить, используя модификаторы, описанные ниже. +Each rule can be modified using the modifiers described in the following paragraphs. -**Синтаксис** {#non-basic-rules-modifiers-syntax} +**Syntax** {#non-basic-rules-modifiers-syntax} ```text rule = "[$" modifiers "]" [rule text] @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Модификатор \ Продукты | [Приложения CoreLibs][cl-apps] | [AdGuard для Chromium][ext-chr] | [AdGuard для Firefox][ext-ff] | [AdGuard для iOS][ios-app] | [AdGuard для Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — полностью поддерживается -- ✅ * — поддерживается, но надёжность может быть разной или могут возникнуть ограничения; ознакомьтесь с описанием модификатора для получения подробной информации +- 🧩 — может быть уже реализован в nightly или бета-версиях, но пока не поддерживается в релизных версиях - ❌ — не поддерживается ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Совместимость -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Ограничения - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Совместимость -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4257,7 +3984,7 @@ Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard `$path` modifier limits the rule application area to specific locations or pages on websites. -**Синтаксис** +**Syntax** ```text $path ["=" pattern] @@ -4292,7 +4019,7 @@ Rules with `$path` modifier are not supported by AdGuard Content Blocker. `$url` modifier limits the rule application area to URLs matching the specified mask. -**Синтаксис** +**Syntax** ```text url = pattern @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Совместимость -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Информация для разработчиков фильтров If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Директивы препроцессора -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [включать содержимое отдельного файла в фильтр](#include-directive) - [применять правила в зависимости от типа блокировщика](#conditions-directive) @@ -4342,25 +4069,25 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Включение файла {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. Она поддерживает только файлы из того же источника, чтобы удостовериться, что разработчик фильтров является владельцем указанного файла. Включённый файл также может содержать директивы препроцессора (даже другие`!#include`-директивы). Блокировщики должны принимать во внимание случай рекурсивного использования `!#include` и внедрять защитный механизм. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. -**Синтаксис** +**Syntax** ```adblock !#include file_path ``` -где `file_path` — абсолютный или относительный путь к файлу одного и того же источника, который должен быть включён. +where `file_path` is a same origin absolute or relative file path to be included. -Файлы должны находиться на том же домене, но могут быть расположены в другой директории. +The files must originate from the same domain but may be located in a different folder. -Если включённый файл не найден или недоступен, не будут работать обновления всего фильтра. +If included file is not found or unavailable, the whole filter update should fail. -Для локальных собственных фильтров ограничение на тот же источник не распространяется. +Same-origin limitation should be disabled for local custom filters. **Примеры** -URL фильтра: `https://example.org/path/filter.txt` +Filter URL: `https://example.org/path/filter.txt` ```adblock ! Корректный (тот же источник): @@ -4376,9 +4103,9 @@ URL фильтра: `https://example.org/path/filter.txt` #### Условия {#conditions-directive} -Разработчики фильтров могут использовать условия, чтобы подставлять нужные правила, в зависимости от типа блокировщика. Директива с условием, начинающаяся с директивы `!#if`, должна явно прерываться директивой `!#endif`. Условия поддерживают все основные логические операторы. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. -Есть два возможных сценария: +There are two possible scenarios: 1. Если блокировщик рекламы встречает директиву `!#if` и не встречает директиву `!#else`, то он компилирует код между директивами `!#if` и `!#endif` только в том случае, если указанное условие истинно. @@ -4386,11 +4113,11 @@ URL фильтра: `https://example.org/path/filter.txt` :::note -Пробелы имеют значение. `!#if` — это корректная директива, в то время как `!# if` — не корректная. +Whitespaces matter. `!#if` is a valid directive, while `!# if` is not. ::: -**Синтаксис** +**Syntax** ```adblock !#if (conditions) @@ -4424,7 +4151,7 @@ false_conditions_rules_list - `adguard_ext_edge` — Браузерное расширение AdGuard для Edge Legacy - `adguard_ext_opera` — Браузерное расширение AdGuard для Opera - `adguard_ext_android_cb` — AdGuard Content Blocker для мобильных браузеров Samsung и Яндекс - - `ext_ublock` — special case; this one is declared when a uBlock version of a filter is compiled by the [FiltersRegistry][] + - `ext_ublock` — особый случай; эта константа объявляется, когда версия фильтра для uBlock компилируется при помощи [FiltersRegistry][] - `cap_html_filtering` — продукты, поддерживающие правила HTML-фильтрации: AdGuard для Windows, AdGuard для Mac и AdGuard для Android - `!#else` — начало блока, когда условия ложны - `rules_list`, `true_conditions_rules_list`, `false_conditions_rules_list` — списки правил @@ -4462,7 +4189,7 @@ domain.com##div.ad The `!#else` directive is supported by the [FiltersDownloader][gh-filters-downloader] v1.1.20 or later. -It is already supported for filter lists compiled by the [FiltersRegistry][], but it still may not be supported by AdGuard products when adding a filter list with `!#else` as a custom one. Следующие продукты будут поддерживать его в указанных версиях или более поздних версиях: +It is already supported for filter lists compiled by the [FiltersRegistry][], but it still may not be supported by AdGuard products when adding a filter list with `!#else` as a custom one. The following products will support it in the mentioned versions or later: - AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13; - Браузерное расширение AdGuard 4.2.208; @@ -4472,9 +4199,9 @@ It is already supported for filter lists compiled by the [FiltersRegistry][], bu #### Правила фильтрации в Safari {#safari-affinity-directive} -Лимит каждого блокировщика контента Safari — 150 000 активных правил. Но в AdGuard для Safari и AdGuard для iOS мы разделили правила на 6 блокировщиков контента, тем самым увеличив лимит правил до 900 000. +Safari's limit for each content blocker is 150,000 active rules. But in AdGuard for Safari and AdGuard for iOS, we've split the rules into 6 content blockers, thus increasing the rule limit to 900,000. -Какие фильтры содержатся в каждом блокировщике контента: +Here is the composition of each content blocker: - AdGuard General — Блокировка рекламы, Языковые - AdGuard Privacy — Антитрекинг @@ -4483,15 +4210,15 @@ It is already supported for filter lists compiled by the [FiltersRegistry][], bu - AdGuard Other — Другие - AdGuard Custom — Собственные -Пользовательские правила и белый список добавляются в каждый блокировщик контента. +User rules and allowlist are added to every content blocker. :::caution -Основной недостаток использования нескольких блокировщиков контента в том, что правила из разных блокировщиков применяются независимо друг от друга. На правила блокировки это не влияет, но с правилами разблокировки могут быть проблемы. Если правило блокировки есть в одном блокировщике контента, а исключение — в другом, то исключение не сработает. Разработчики фильтров используют `!#safari_cb_affinity`, чтобы указать, к какому блокировщику контента принадлежат правила. +The main disadvantage of using multiple content blockers is that rules from different blockers are applied independently. Blocking rules are not affected by this, but unblocking rules may cause problems. If a blocking rule is in one content blocker and an exception is in another, the exception will not work. Filter maintainers use `!#safari_cb_affinity` to define Safari content blocker affinity for the rules inside of the directive block. ::: -**Синтаксис** +**Syntax** ```adblock !#safari_cb_affinity(content_blockers) @@ -4523,7 +4250,7 @@ example.org#@#.adBanner ``` ```adblock -! чтобы разблокировать запрос, который блокируется Фильтром счётчиков и систем аналитики: +! to allowlist basic rule from AdGuard Tracking Protection filter: !#safari_cb_affinity(privacy) @@||example.org^ !#safari_cb_affinity @@ -4533,19 +4260,19 @@ example.org#@#.adBanner "Hint" is a special comment, instruction to the filters compiler used on the server side (see [FiltersRegistry][]). -**Синтаксис** +**Syntax** ```adblock !+ HINT_NAME1(PARAMS) HINT_NAME2(PARAMS) ``` -Можно применить несколько подсказок. +Multiple hints can be applied. #### Подсказка `NOT_OPTIMIZED` -Для каждого фильтра AdGuard существуют две версии: полная и оптимизированная. Оптимизированная версия намного легче и не содержит правил, которые не используются вообще или используются редко. +For each filter, AdGuard compiles two versions: full and optimized. Optimized version is much more lightweight and does not contain rules which are not used at all or used rarely. -Частота использования правил определяется собранной [статистикой по рекламным фильтрам](../tracking-filter-statistics). Но оптимизация основана также на исходной конфигурации для каждого фильтра. Например, вот так это выглядит для Базового фильтра: +Rules usage frequency comes from the collected [filter rules statistics](../tracking-filter-statistics). But filters optimization is based on more than that — some filters have specific configuration. This is how it looks like for Base filter: ```text "filter": Базовый фильтр AdGuard, @@ -4563,21 +4290,21 @@ example.org#@#.adBanner - **maxPercent** — верхняя граница значения `percent` - **Strict** — если `percent < minPercent` или `percent > maxPercent` и включён режим Strict, то компиляция фильтра должна завершиться неудачно, в противном случае должны использоваться оригинальные правила -Другими словами, `percent` — это «уровень сжатия». Например, для Базового фильтра он настроен на 40%. Это означает, что алгоритм оптимизации должен убрать 60% правил. +In other words, `percent` is the "compression level". For instance, for the Base filter it is configured to 40%. It means that optimization algorithm should strip 60% of rules. -В итоге, вот так выглядят версии Базового фильтра для Браузерного расширения AdGuard для Chrome: +Eventually, here are the two versions of the Base filter for AdGuard Browser Extension: - полная: https://filters.adtidy.org/extension/chromium/filters/2.txt - оптимизированная: https://filters.adtidy.org/extension/chromium/filters/2_optimized.txt -**Если вы хотите добавить правило, которое не должно удаляться при оптимизации, используйте подсказку `NOT_OPTIMIZED`:** +**If you want to add a rule which should not be removed at optimization use the `NOT_OPTIMIZED` hint:** ```adblock !+ NOT_OPTIMIZED ||example.org^ ``` -**А такое правило не будет оптимизировано только для AdGuard для Android:** +**And this rule will not be optimized only for AdGuard for Android:** ```adblock !+ NOT_OPTIMIZED PLATFORM(android) @@ -4586,7 +4313,7 @@ example.org#@#.adBanner #### Подсказки `PLATFORM` и `NOT_PLATFORM` -Записи этого типа позволяют указывать платформу, для которой применяется правило. Ниже представлен список используемых платформ и ссылки на Базовый фильтр для каждой из них: +Used to specify the platforms to apply the rules. List of existing platforms and links to Base filter, for example, for each of them: - `windows` — AdGuard для Windows — [https://filters.adtidy.org/windows/filters/2.txt](https://filters.adtidy.org/windows/filters/2.txt) @@ -4598,7 +4325,7 @@ example.org#@#.adBanner - `ext_chromium` — Браузерное расширение AdGuard для Chrome — [https://filters.adtidy.org/extension/chromium/filters/2.txt](https://filters.adtidy.org/extension/chromium/filters/2.txt) -- `ext_chromium` — Браузерное расширение AdGuard для Chrome MV3 — [https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt](https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt) +- `ext_chromium_mv3` — AdGuard Browser Extension for Chrome MV3 — [https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt](https://filters.adtidy.org/extension/chromium-mv3/filters/2.txt) - `ext_ff` — Браузерное расширение AdGuard для Firefox — [https://filters.adtidy.org/extension/firefox/filters/2.txt](https://filters.adtidy.org/extension/firefox/filters/2.txt) @@ -4630,34 +4357,34 @@ Except for AdGuard for Safari, AdGuard Content Blocker, and AdGuard for iOS, thi ## Отладка правил фильтрации -Хоть самые простые правила фильтрации и возможно придумать «в голове», для чего-то чуть более сложного вам потребуются дополнительная помощь в их отладке и повторении. Есть инструменты, которые помогут вам в этом. Вы можете использовать «Инструменты разработчика» в Chrome и их аналоги в других браузерах, но большинство продуктов AdGuard предоставляют и другой инструмент — Журнал фильтрации. +It may be possible to create simple filtering rules "in your head" but for anything even slightly more complicated you will need additional tools to debug and iterate them. There are tools to assist you with that. You can use DevTools in Chrome and its analogs in other browsers but most AdGuard products provide another one — Filtering log. ### Журнал фильтрации -Журнал фильтрации — продвинутый инструмент, который полезен в основном разработчикам фильтров. В нём отображаются все веб-запросы, проходящие через AdGuard, даётся исчерпывающая информация по каждому из них, предлагаются различные опции сортировки и другие полезные возможности. +Filtering log is an advanced tool that will be helpful mostly to filter developers. It lists all web requests that pass through AdGuard, gives you exhaustive information on each of them, offers multiple sorting options, and has other useful features. -В зависимости от того, какой продукт AdGuard вы используете, журнал фильтрации может находиться в разных местах. +Depending on which AdGuard product you are using, Filtering log can be located in different places. - В **AdGuard для Windows** вы найдёте его во вкладке настроек *Антибаннер* или через меню трея - В **AdGuard для Mac** он располагается в разделе *Настройки → Дополнительно → Журнал фильтрации* - В **AdGuard для Android** его можно найти в разделе *Статистика → Недавняя активность*. *Доступ к недавней активности* также можно получить из *Помощника* -- В **Браузерном расширении AdGuard** он находится во вкладке настроек *Дополнительно*, а также доступен по клику правой кнопкой мыши по иконке расширения. Только веб-браузеры на основе Chromium и Firefox отображают применённые **правила скрытия элементов** (включая CSS, ExtCSS) и **JS-правила и скриптлеты** в своих Журналах фильтрации +- В **Браузерном расширении AdGuard** он находится во вкладке настроек *Дополнительно*, а также доступен по клику правой кнопкой мыши по иконке расширения. Only Chromium- and Firefox-based web browsers show applied **element hiding rules** (including CSS, ExtCSS) and **JS rules and scriptlets** in their Filtering logs :::note -В **AdGuard для iOS** и в **AdGuard для Safari** Журнал фильтрации отсутствует из-за особенностей реализации блокировщиков контента в Safari. AdGuard сам не видит веб-запросы и поэтому не может отображать их. +In **AdGuard for iOS** and **AdGuard for Safari**, Filtering log does not exist because of the way content blockers are implemented in Safari. AdGuard does not see the web requests and therefore cannot display them. ::: ### Режим отладки селекторов {#selectors-debug-mode} -Иногда может понадобиться проверить производительность того или иного селектора или таблицы стилей. Чтобы сделать это без непосредственного взаимодействия с JavaScript, вы можете использовать свойство стиля `debug`. Когда `ExtendedCss` встречает это свойство, он включает режим отладки для конкретного селектора или для всех селекторов, в зависимости от значения `debug`. +Sometimes, you might need to check the performance of a given selector or a stylesheet. In order to do it without interacting with JavaScript directly, you can use a special `debug` style property. When `ExtendedCss` meets this property, it enables the debugging mode either for a single selector or for all selectors, depending on the `debug` value. -Откройте консоль браузера, находясь на веб-странице, чтобы посмотреть статистику по времени, затраченному на применение селектора(-ов). В режиме отладки следующая статистика отображается в виде объекта, где каждый из отлаживаемых селекторов является ключом, а значение — объектом с такими свойствами: +Open the browser console while on a web page to see the timing statistics for selector(s) that were applied there. Debugging mode displays the following stats as object where each of the debugged selectors are keys, and value is an object with such properties: -**Всегда выводится:** +**Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — окончательный текст селектора после парсинга - `timings` — список узлов DOM, соответствующих селектору - `appliesCount` — общее количество раз, когда на странице был применён селектор - `appliesTimings` — время, которое ушло на применение селектора на странице, для каждого из случаев применения этого селектора (в миллисекундах) @@ -4665,44 +4392,44 @@ Except for AdGuard for Safari, AdGuard Content Blocker, and AdGuard for iOS, thi - `standardDeviation` — стандартное отклонение - `timingsSum` — общее время, ушедшее на все применения селектора на текущей странице -**Выводится только для удалённых псевдоэлементов:** +**Printed only for remove pseudos:** -- `removed` — флаг, сигнализирующий об удалении элементов +- `removed` — flag to signal if elements were removed -**Выводится, если элементы не удалены:** +**Printed if elements are not removed:** - `matchedElements` — список узлов DOM, соответствующих селектору - `styleApplied` — объявление обработанного стиля правила, связанного с селектором **Примеры** -**Отладка конкретного селектора:** +**Debugging a single selector:** -Когда значение свойства `debug` равно `true`, информация только по этому селектору будет отображена в консоли браузера. +When the value of the `debug` property is `true`, only information about this selector will be shown in the browser console. ```adblock #$?#.banner { display: none; debug: true; } ``` -**Включение глобальной отладки:** +**Enabling global debug:** -Когда значение свойства `debug` равно `global`, в консоли будет отображаться информация по всем CSS-селекторам, которые были применены на данной странице, для всех правил из любого из включённых фильтров. +When the value of the `debug` property is `global`, the console will display information about all extended CSS selectors that have matches on the current page, for all the rules from any of the enabled filters. ```adblock #$?#.banner { display: none; debug: global; } ``` -**Тестирование расширенных селекторов без AdGuard** +**Testing extended selectors without AdGuard** -ExtendedCss может быть выполнен на любой странице без использования какого-либо продукта AdGuard. Для этого скопируйте и запустите следующий код в консоли браузера: +ExtendedCss can be executed on any page without using any AdGuard product. In order to do that you should copy and execute the following code in a browser console: ```js !function(e,t,d){C=e.createElement(t),C.src=d,C.onload=function(){alert("ExtendedCss loaded successfully")},s=e.getElementsByTagName(t)[0],s?s.parentNode.insertBefore(C,s):(h=e.getElementsByTagName("head")[0],h.appendChild(C))}(document,"script","https://AdguardTeam.github.io/ExtendedCss/extended-css.min.js"); ``` -Или установите пользовательский скрипт [ExtendedCssDebugger](https://github.com/AdguardTeam/Userscripts/blob/master/extendedCssDebugger/extended-css.debugger.user.js). +Alternatively, install the [ExtendedCssDebugger userscript](https://github.com/AdguardTeam/Userscripts/blob/master/extendedCssDebugger/extended-css.debugger.user.js). -Теперь вы можете использовать `ExtendedCss` глобально и запустить его метод [`query()`](https://github.com/AdguardTeam/ExtendedCss#extended-css-query) как `Document.querySelectorAll()`. +Now you can now use the `ExtendedCss` from global scope, and run its method [`query()`](https://github.com/AdguardTeam/ExtendedCss#extended-css-query) as `Document.querySelectorAll()`. **Примеры** @@ -4715,9 +4442,9 @@ ExtendedCss.query(selector); ### Отладка скриптлетов {#debug-scriptlets} -Если вы используете браузерное расширение AdGuard и хотите отладить правило [скриптлета](#scriptlets) или [доверенного скриптлета](#trusted-scriptlets), то можете получить дополнительную информацию, открыв журнал фильтрации. В этом случае скриптлеты перейдут в режим отладки и будут записывать больше информации в браузерную консоль. +If you are using AdGuard Browser Extension and want to debug a [scriptlet](#scriptlets) or a [trusted scriptlet](#trusted-scriptlets) rule, you can get additional information by opening the Filtering log. In that case, scriptlets will switch to debug mode and there will be more information in the browser console. -Следующие скриптлеты разработаны специально для отладки: +The following scriptlets are especially developed for debug purposes: - [`debug-current-inline-script`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#debug-current-inline-script) - [`debug-on-property-read`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#debug-on-property-read) @@ -4727,7 +4454,7 @@ ExtendedCss.query(selector); - [`log-eval`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#log-eval) - [`log`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#log) -Следующие скриптлеты тоже могут быть использованы для отладки: +The following scriptlets also may be used for debug purposes: - [`json-prune`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#json-prune) - [`prevent-fetch`](https://github.com/AdguardTeam/Scriptlets/blob/master/wiki/about-scriptlets.md#prevent-fetch) @@ -4743,13 +4470,11 @@ ExtendedCss.query(selector); ### Краткие обозначения продуктов {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `Приложения CoreLibs` — AdGuard для Windows, AdGuard для Mac и AdGuard для Android +1. `AdGuard для Chromium` — Браузерное расширение AdGuard для Chrome и других браузеров на основе Chromium, таких как Microsoft Edge и Opera +1. `AdGuard для Firefox` — Браузерное расширение AdGuard для Firefox +1. `AdGuard для iOS` — AdGuard для iOS и AdGuard Pro для iOS (для мобильного браузера Safari) +1. `AdGuard для Safari` — AdGuard для веб-браузера Safari `AdGuard Content Blocker` — Content Blocker для мобильных браузеров Android: Samsung Internet и Яндекс Браузер ### Краткие обозначения совместимости {#what-compatibility} @@ -4758,32 +4483,21 @@ ExtendedCss.query(selector); - ✅ — полностью поддерживается - ✅ * — поддерживается, но надёжность может быть разной или могут возникнуть ограничения; ознакомьтесь с описанием модификатора для получения подробной информации - 🧩 — может быть уже реализован в nightly или бета-версиях, но пока не поддерживается в релизных версиях -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — функция, которая реализована или планируется к реализации, но пока недоступна ни в одном продукте - ❌ — не поддерживается -- 👎 — устарел; всё ещё поддерживается, но в будущем будет удалён +- 👎 — deprecated; still supported but will be removed in the future - 🚫 — удалён и больше не поддерживается ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard для Windows, Mac и Android" [ext-chr]: #what-product "Браузерное расширение AdGuard для Chrome и других браузеров на основе Chromium" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "Браузерное расширение AdGuard для Firefox" [ios-app]: #what-product "AdGuard для iOS и AdGuard Pro для iOS" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard для Safari" -[ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker для браузеров Samsung Internet and Яндекс на Android" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 7c6e23203f6..449243bc5da 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ sidebar_position: 6 - Базовый фильтр AdGuard - Фильтр мобильной рекламы AdGuard - Региональные фильтры, разделённые по языковому принципу — китайский, голландский, французский, немецкий, японский, русский, испанский/португальский, турецкий и украинский -- AdGuard Quick Fixes filter ### Назначение этих фильтров - **Базовый фильтр** предназначен для блокировки рекламы на англоязычных сайтах и тех сайтах, для которых нет отдельного фильтра. Он также содержит общие правила фильтрации, которые применяются ко всем сайтам независимо от языка - **Фильтр мобильной рекламы** блокирует рекламу на мобильных версиях сайтов и в мобильных приложениях. Разделения по языкам нет - **Региональные фильтры** следуют той же политике, что и **Базовый фильтр**, но ограничены сайтами на определённых языках -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. Цель этих фильтров — блокировать все виды рекламы на сайтах, в приложениях и на некоторых устройствах, которые могут загружать рекламу из интернета: @@ -83,7 +81,7 @@ sidebar_position: 6 - Они предоставляют альтернативу отключению блокировщика рекламы, если эта альтернатива не ставит под угрозу конфиденциальность или безопасность пользователей - Они позволяют пользователю перейти к содержимому сайта или предлагают реальный обмен ценностями, который не подвергает риску конфиденциальность или безопасность пользователя - Некоторые устаревшие правила могут продолжать блокировать сообщения, удовлетворяющие одному или нескольким из этих критериев. Если такие правила будут выявлены, они будут обрабатываться в соответствии с этой политикой -- Майнинговые пулы не блокируются, если они публичные и не используются исключительно во вредоносных целях +- Майнинговые пулы не блокируются, если они общедоступны и не используются исключительно во вредоносных целях ## Фильтр счётчиков и систем аналитики diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index 111488a04a9..ce214741cf2 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: Как работает блокировка рекламы sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. Но объединяет их всех то, что они блокируют рекламу и трекеры. Эта статья описывает, как устроена блокировка рекламы изнутри. +В семействе блокировщиков AdGuard есть много продуктов для разных платформ, и каждый из них обладает своими уникальными особенностями. Но объединяет их всех то, что они блокируют рекламу и трекеры. Эта статья описывает, как устроена блокировка рекламы изнутри. :::note diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/search-ads.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/search-ads.md index e1c61d3d015..b4ef9c16109 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/search-ads.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/search-ads.md @@ -3,7 +3,7 @@ title: Поисковая реклама и самореклама sidebar_position: 3 --- -**Важно.** Хотя AdGuard предоставляет опцию «Показывать поисковую рекламу и саморекламу», это не означает, что у нас есть программа «допустимой рекламы», как у Adblock Plus и некоторых других блокировщиков, которые получают деньги, чтобы оставлять определённый тип рекламы за пределами блокировки. Это не наш способ ведения бизнеса. Нам не платят за показ какой-либо рекламы, и мы неслучайно не используем термин «приемлемый»: реклама, которую мы можем показывать, может быть на самом деле полезной, а не просто «приемлемой». Все это относится только к поисковой рекламе и саморекламе. +**Важно.** Хотя AdGuard предоставляет опцию «Показывать поисковую рекламу и саморекламу», это не означает, что у нас есть программа «допустимой рекламы», как у Adblock Plus и некоторых других блокировщиков, которые получают деньги, чтобы оставлять определённый тип рекламы за пределами блокировки. This isn't our way of doing business. Нам не платят за показ какой-либо рекламы, и мы неслучайно не используем термин «приемлемый»: реклама, которую мы можем показывать, может быть на самом деле полезной, а не просто «приемлемой». Все это относится только к поисковой рекламе и саморекламе. Вы можете отключить показ этой рекламы в любой момент. Далее мы объясним, какая именно реклама подпадает под это определение. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md index f451b7262e2..3b6dfd31eba 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/ad-filtering/tracking-filter-statistics.md @@ -36,7 +36,7 @@ sidebar_position: 4 Собранная статистика будет периодически отправляться к нам на сервер для анализа и оптимизации фильтров. -Важно отметить, что вся статистика, которую мы получаем, усреднена и анонимизирована. Мы никогда не используем собранные данные в каких-либо иных целях, кроме оптимизации фильтров, и не продаём данные третьим лицам. Вы можете прочитать об этом в нашей [Политике конфиденциальности](https://adguard.com/privacy.html). +Важно отметить, что вся статистика, которую мы получаем, усреднена и анонимизирована. Мы никогда не используем собранные данные в каких-либо иных целях, кроме оптимизации фильтров, и не продаём данные третьим лицам. You can read about it in our [Privacy policy](https://adguard.com/privacy.html). ### Чем сбор статистики может вам мешать diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/browsing-security.md index 2b216b28b53..2c02c899ebc 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -1,29 +1,29 @@ --- -title: Защита от фишинга и вредоносных программ +title: Phishing and malware protection sidebar_position: 3 --- Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ -Каждый раз, когда вы посещаете сайт, ваш локальный клиент обменивается информацией с нашим внутренним сервером в виде хешей и хеш-префиксов. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. +Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. -### В приложениях +### In apps AdGuard provides the best possible protection by inspecting both the pages and all objects loaded on them. AdGuard checks URLs and domain names using hash prefixes, not the full URLs, so our servers retain no information about the websites you visit and your personal information is completely safe. Our servers respond to the app’s query with a list of all possible addresses that match the hash prefix. When a potential threat is detected based on hash matches, access to that website is immediately blocked. -![DNS-предупреждение](https://cdn.adtidy.org/content/kb/ad_blocker/general/bs_diana.png) +![DNS warning](https://cdn.adtidy.org/content/kb/ad_blocker/general/bs_diana.png) -### В браузерных расширениях +### In browser extensions -Наши браузерные расширения могут проверять только имена доменов, а не полные URL-адреса. They are also unable to check subqueries. This means that if there are potentially malicious elements on the page, they will be loaded even if the page itself is from a safe domain. The extension won’t be able to protect against them. It's also important to note that the check performed is asynchronous, i.e. it happens at the same time as the page is loaded, so it’s possible that malware could be loaded as well. +Our browser extensions can only check domain names, not full URLs. They are also unable to check subqueries. This means that if there are potentially malicious elements on the page, they will be loaded even if the page itself is from a safe domain. The extension won’t be able to protect against them. It's also important to note that the check performed is asynchronous, i.e. it happens at the same time as the page is loaded, so it’s possible that malware could be loaded as well. ## Setting up phishing and malware protection in AdGuard products @@ -33,7 +33,7 @@ AdGuard provides the best possible protection by inspecting both the pages and a - **For Mac**: Enable the *Security* module in *Preferences* -![Безопасность в Mac](https://cdn.adtidy.org/content/kb/ad_blocker/general/bs_mac.png) +![Security in Mac](https://cdn.adtidy.org/content/kb/ad_blocker/general/bs_mac.png) - **For Android**: Turn on *Browsing Security* in the *Protection* tab @@ -45,7 +45,7 @@ AdGuard provides the best possible protection by inspecting both the pages and a - **For Browser extensions**: Enable *Phishing and malware protection* in the *Settings* tab. For enhanced protection, go to *Filters* → *Security* and activate available filters -![Защита от фишинга и вредоносных программ](https://cdn.adtidy.org/content/kb/ad_blocker/general/extension_protection.png) +![Phishing and malware protection](https://cdn.adtidy.org/content/kb/ad_blocker/general/extension_protection.png) - **For Private AdGuard DNS:** Enable malware protection in *Server settings* under *Security* @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. Мы следим, чтобы такого не происходило, но бывают разные случаи. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/https-filtering/known-issues.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/https-filtering/known-issues.md index dbacef0a8d8..7d6a43ba2ef 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/https-filtering/known-issues.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/https-filtering/known-issues.md @@ -9,7 +9,7 @@ sidebar_position: 2 Для начала посмотрите на эту диаграмму, которая показывает общую структуру протокола HTTPS: -![Что такое HTTPS-фильтрация?](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) +![What is HTTPS filtering?](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) AdGuard копирует свойства TLS-соединения, которые использует ваш браузер: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index d64155b7119..09a213f86ed 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (аббр. от англ. HyperText Transfer Protocol Secure) — расширение HTTP-протокола, поддерживающее шифрование для повышения безопасности. Этот протокол используется для защищённой передачи важной информации, такой как персональные данные, реквизиты банковских карт и т. д. -Использование HTTPS — сугубо положительная вещь, ведь зашифрованный трафик защищён от прослушивания третьей стороной, и мы это только приветствуем. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Использование HTTPS — сугубо положительная вещь, ведь зашифрованный трафик защищён от прослушивания третьей стороной, и мы это только приветствуем. Рост HTTPS сильно ускорился в последние годы в связи с тем, что это [поощряется Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html), а также с появлением бесплатного центра сертификации [Let’s Encrypt](https://ru.wikipedia.org/wiki/Let’s_Encrypt). На диаграмме ниже мы описали разницу между простым HTTP-протоколом и защищённым HTTPS-протоколом. @@ -15,17 +15,17 @@ HTTPS (аббр. от англ. HyperText Transfer Protocol Secure) — расш ### Что такое сертификат безопасности -Проще говоря, HTTPS означает шифрование данных. Но остаётся ещё одна проблема: как быть уверенным, что вы установили зашифрованное соединение именно с тем сайтом, с которым планировали? Тут в игру и вступают сертификаты безопасности. A certificate serves as proof that the website is really who or what it claims to be. Если такого сертификата у сайта нет или в нём содержится неправильная информация, браузер не позволит вам установить защищённое соединение. При этом важно, чтобы сертификат, используемый сайтом, был выдан центром сертификации, которому доверяет ваш браузер. Такие центры сертификации гарантируют, что сертификат выдан именно владельцу сайта. +Проще говоря, HTTPS означает шифрование данных. Но остаётся ещё одна проблема: как быть уверенным, что вы установили зашифрованное соединение именно с тем сайтом, с которым планировали? Тут в игру и вступают сертификаты безопасности. Сертификат — это удостоверение, что сайт представляет собой именно тот ресурс, за который себя выдаёт. Если такого сертификата у сайта нет или в нём содержится неправильная информация, браузер не позволит вам установить защищённое соединение. При этом важно, чтобы сертификат, используемый сайтом, был выдан центром сертификации, которому доверяет ваш браузер. Такие центры сертификации гарантируют, что сертификат выдан именно владельцу сайта. ### Зачем AdGuard нужно уметь фильтровать HTTPS? -Большинство сайтов теперь используют HTTPS, то же самое относится и к рекламным сетям. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Большинство сайтов теперь используют HTTPS, то же самое относится и к рекламным сетям. Вот примеры популярных сайтов, рекламу на которых невозможно убрать без HTTPS-фильтрации: youtube.com, facebook.com, twitter.com. ### Как работает HTTPS-фильтрация -Если бы это было просто, HTTPS не был бы безопасным. При попытке браузера соединиться с сервером, AdGuard устанавливает два защищённых соединения: одно с браузером (или с другим приложением), а другое с сервером. Важно, чтобы при этом браузер доверял AdGuard и созданному им соединению. Для этого AdGuard генерирует специальный (и уникальный) корневой сертификат и устанавливает его в систему и, при необходимости, в некоторые браузеры (например, Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +Если бы это было просто, HTTPS не был бы безопасным. При попытке браузера соединиться с сервером, AdGuard устанавливает два защищённых соединения: одно с браузером (или с другим приложением), а другое с сервером. Важно, чтобы при этом браузер доверял AdGuard и созданному им соединению. Для этого AdGuard генерирует специальный (и уникальный) корневой сертификат и устанавливает его в систему и, при необходимости, в некоторые браузеры (например, Firefox). Таким образом, AdGuard может видеть, что происходит внутри защищённого соединения, и выполнять свою работу — блокировать рекламу и трекеры. -For better understanding, we have depicted this process: +Для лучшего понимания мы изобразили этот процесс на картинке: ![Как работает HTTPS-фильтрация](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/license/what-is.md index 5ebc27b8ed2..4efd886fd64 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -12,7 +12,7 @@ sidebar_position: 1 - **Годовые подписки** — эти лицензии обновляются автоматически ежегодно или могут быть продлены вручную - Персональная — до 3 устройств - Семейная — до 9 устройств -- **Вечная** — эти лицензии бессрочные +- **Вечная** — эти лицензии не ограничены по времени - Персональная — до 3 устройств - Семейная — до 9 устройств diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 8125649bfba..174e543733b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Push API даёт серверам возможность отправлять ### Блокировать Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. При включении этой опции AdGuard блокирует возможность браузера определять наличие компонентов (плагинов и объектов ActiveXObject), позволяющих использовать технологии Flash для отображения содержимого. Фактически это означает, что браузеры не могут поддерживать эту технологию. +Плагин Flash Player становится всё более уязвимым для таких интернет-угроз, как вирусы и хакерские атаки и, кроме того, может существенно повлиять на время загрузки сайтов. При включении этой опции AdGuard блокирует возможность браузера определять наличие компонентов (плагинов и объектов ActiveXObject), позволяющих использовать технологии Flash для отображения содержимого. Фактически это означает, что браузеры не могут поддерживать эту технологию. ### Блокировать Java {#java} @@ -95,7 +95,7 @@ Referer — это HTTP-заголовок, используемый в запр Обратите внимание, что для фильтрации трафика приложения AdGuard перехватывают запросы от браузера к серверу. Запросы к рекламным, отслеживающим и фишинговым серверам могут быть изменены перед отправкой на сервер или полностью заблокированы. То же самое относится к настройке *Скрывать Referer от третьих лиц*: если она включена, AdGuard перехватывает HTTP(S)-запросы, в частности, чтобы удалить или изменить заголовок Referer. Однако это происходит только после того, как эти запросы «покинут» браузер. Это означает, что если вы отслеживаете Referer в браузере (например, с помощью инструментов разработчика Chrome), вы увидите оригинальный Referer, потому что запрос ещё не дошёл до AdGuard. Вы можете использовать такое программное обеспечение, как [Fiddler](https://www.telerik.com/fiddler), чтобы убедиться, что Referer изменяется правильно. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. Оно изменит Referer незамедлительно, так что в инструментах разработчика будет виден желаемый Referer для ваших запросов. +И наоборот, из-за особенностей всех браузерных расширений расширение AdGuard работает «внутри» браузера. Оно изменит Referer незамедлительно, так что в инструментах разработчика будет виден желаемый Referer для ваших запросов. ### Скрывать User-Agent {#useragent} @@ -120,9 +120,3 @@ DPI (Deep Packet Inspection) — это система глубокого ана AdGuard может изменять данные исходящих пакетов, чтобы клиент не попадал под критерии блокировки по DPI. А это значит, что, включив эту опцию, пользователи смогут обойти ограничения и получить доступ к необходимому контенту. Пока функция обхода DPI работает не для всех провайдеров, но мы продолжаем работать над её улучшением. Функция «Защита от DPI» уже реализована в приложениях AdGuard для Windows, AdGuard для Mac и AdGuard для Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/ru/docusaurus-plugin-content-docs/current/general/userscripts.md index 445f5a35979..2a1e7445868 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,17 +4,17 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. Они модифицируют или расширяют функциональность одного или нескольких сайтов. Многие пользователи AdGuard уже наверняка знакомы с такими расширениями, как Помощник AdGuard, Блокировщик всплывающей рекламы и AdGuard Extra. +Пользовательские скрипты (мы также называем их «‎расширениями»‎) — это, по сути, мини-программы, написанные на языке JavaScript. Они модифицируют или расширяют функциональность одного или нескольких сайтов. Многие пользователи AdGuard уже наверняка знакомы с такими расширениями, как Помощник AdGuard, Блокировщик всплывающей рекламы и AdGuard Extra. :::note Поддерживаемые приложения -AdGuard может значительно расширять функциональность сайтов, работая как менеджер пользовательских скриптов. Добавлять собственные скрипты или управлять существующими вы можете в трёх наших продуктах: [AdGuard для Windows](/adguard-for-windows/features/extensions), [AdGuard для Android](/adguard-for-android/features/settings#userscripts) и [AdGuard для Mac](/adguard-for-mac/features/extensions). +AdGuard может значительно расширять функциональность сайтов, работая как менеджер пользовательских скриптов. You can add your custom scripts or manage the existing ones in our three products: [AdGuard for Windows](/adguard-for-windows/features/extensions), [AdGuard for Android](/adguard-for-android/features/settings#userscripts), and [AdGuard for Mac](/adguard-for-mac/features/extensions). ::: ## Рекомендуемые скрипты AdGuard -Эти пользовательские скрипты разработаны в AdGuard, и мы можем гарантировать, что они эффективны и безопасны. Есть и другие пользовательские скрипты, разработанными другими людьми, которые мы считаем хорошими и надёжными. Чтобы ознакомиться с ними, [прокрутите страницу вниз до следующего раздела](#top-picks). Вы также можете найти некоторые [популярные сайты со скриптами](#more-userscripts) ниже, но помните, что всякий раз, когда вы загружаете пользовательский скрипт из неизвестного источника, вы подвергаете себя определённому риску, поскольку некоторые скрипты могут быть опасны для вашего компьютера. +Эти пользовательские скрипты разработаны в AdGuard, и мы можем гарантировать, что они эффективны и безопасны. For some of the userscripts developed by others that we consider good and reliable, [scroll down to the next section](#top-picks). You can also find some of the [popular websites with scripts](#more-userscripts) below, but remember that whenever you download a userscript from an unknown source, you expose yourself to a certain risk, as some scripts may be harmful to your computer. ### AdGuard Extra @@ -46,13 +46,13 @@ AdGuard может значительно расширять функциона ## Top picks outside AdGuard{#top-picks} -Эти пользовательские скрипты не разработаны AdGuard, поэтому мы не можем дать 100% гарантию, что они безопасны и/или работают всегда. Однако, исходя из нашего опыта, они заслуживают рекомендации, поскольку заслужили свою хорошую репутацию. +These userscripts are not developed by AdGuard and therefore we can't give a 100% guarantee that they are safe and/or work at all times. However, in our experience they deserve a recommendation as they've all earned their good reputation. ### Don't track me Google -Этот скрипт удаляет функцию отслеживания Google из ссылок в результатах поиска Google. Это ускоряет загрузку результатов поиска и позволяет скопировать URL-адрес ссылки, щёлкнув по нему правой кнопкой мыши или нажав на него. +This script removes Google's tracking feature from the links in Google search results. It speeds up the loading of search results and allows you to right-click or tap to copy the link URL. -Его исходный код [доступен на GitHub](https://github.com/Rob--W/dont-track-me-google). Этот пользовательский скрипт можно загрузить с [GreasyFork](https://greasyfork.org/en/scripts/428243-don-t-track-me-google) и установить в любое приложение AdGuard на базе CoreLibs. +Its source code is [available on GitHub](https://github.com/Rob--W/dont-track-me-google). This userscript can be downloaded from [GreasyFork](https://greasyfork.org/en/scripts/428243-don-t-track-me-google) and installed in any AdGuard CoreLibs-based app. ### microShield @@ -60,7 +60,7 @@ AdGuard может значительно расширять функциона ## Где взять больше пользовательских скриптов{#more-userscripts} -По большей части пользовательские скрипты создаются любителями, поэтому, устанавливая тот или иной скрипт, нужно быть очень осторожными. Любой скрипт из неизвестного источника несёт в себе потенциальный риск. Тем не менее, существует огромное количество интересных скриптов, которые, если установить их аккуратно и ответственно, могут действительно сделать использование некоторых сайтов более удобным. +As userscripts are mainly created by enthusiasts, you should be cautious when installing them. Any script from an unknown source carries a potential risk. Yet, there is a great variety of interesting scripts that, if installed carefully and responsibly, can really make using some websites more convenient. Здесь мы опишем несколько популярных каталогов пользовательских скриптов. @@ -134,7 +134,7 @@ AdGuard может значительно расширять функциона ##### Неподдерживаемые свойства -These properties will be simply ignored by AdGuard. +AdGuard проигнорирует эти свойства. ```text @unwrap diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/ru/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 9ad18f45b47..ee971cbcc5c 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: Как создать файл HAR +title: Как собрать файл HAR sidebar_position: 1 --- @@ -92,7 +92,7 @@ sidebar_position: 1 ## Internet Explorer 11 {#ie11} -Чтобы создать файл HAR в Internet Explorer 11, выполните следующие действия: +To create a HAR file in Internet Explorer 11, follow these steps: 1. Перейдите по URL-адресу, по которому возникает ошибка. Пока не воспроизводите её. @@ -119,7 +119,7 @@ sidebar_position: 1 ## Safari {#safari} -Чтобы создать файл HAR в Safari, выполните следующие действия: +To create a HAR file in Safari, follow these steps: 1. Найдите в строке меню Safari раздел **Разработка**. @@ -131,7 +131,7 @@ sidebar_position: 1 1. Откройте вкладку **Сеть** в веб-инспекторе: - Из меню: **Разработка → Показывать веб-инспектор → Сеть**. - - Клавиатура: **⌥+⌘+I → Сеть** + - Keyboard: **⌥+⌘+I → Network** 1. Установите флажок **Сохранить журнал** в левой части вкладок Сеть в меню **Другие параметры фильтра...**. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/guides/family-link-certificate.md b/i18n/ru/docusaurus-plugin-content-docs/current/guides/family-link-certificate.md index fb769aed303..6c9dd32390f 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/guides/family-link-certificate.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/guides/family-link-certificate.md @@ -11,7 +11,7 @@ sidebar_position: 6 - На устройстве ребёнка перейдите в Настройки → Учётные записи → Google - Найдите учётную запись ребёнка и проверьте, можно ли её удалить. Если такой опции нет, перейдите к следующему пункту - Нажмите на три точки в правом верхнем углу и проверьте, можно ли удалить учётную запись - - Следуя инструкциям, удалите учётную запись ребёнка с устройства + - Follow the instructions removing the child’s account from the device 1. Запустите AdGuard и установите сертификат 1. Повторно добавьте учётную запись ребёнка: diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/guides/minidump.md b/i18n/ru/docusaurus-plugin-content-docs/current/guides/minidump.md index 04ada095647..daee4bbeda9 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/guides/minidump.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/guides/minidump.md @@ -18,7 +18,7 @@ sidebar_position: 8 ## Как разрешить создание файла minidump -Даже если вы не сталкивались с ошибками BSoD, лучше настроить эту опцию — это общая рекомендация, не обязательно связанная с продуктами AdGuard. Следуйте этой инструкции, чтобы автоматически создать minidump-файл. +Even if you don’t experience any BSoD crash errors, you can still set this option — this is a general recommendation, not necessarily related to AdGuard products. Следуйте этой инструкции, чтобы автоматически создать minidump-файл. 1. Наберите *sysdm.cpl* в строке поиска Windows и нажмите **Открыть**. На экране появится окно **Свойства системы**. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/guides/proxy-certificate.md b/i18n/ru/docusaurus-plugin-content-docs/current/guides/proxy-certificate.md index 97140866a39..82783c6bb05 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/guides/proxy-certificate.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/guides/proxy-certificate.md @@ -21,17 +21,17 @@ HTTP-трафик будет фильтроваться в любом случа 1. Note the IP address of your desktop computer with AdGuard installed. -1. Убедитесь, что защита AdGuard включена. На компьютере с Windows установите флажок **Использовать AdGuard как HTTP-прокси** во вкладке **Сеть** в его настройках. For Mac, go to **Settings** → **Preferences** → **Network** and enable **HTTP proxy**. +1. Make sure that AdGuard protection is enabled. On a Windows computer, check the box **Use AdGuard as an HTTP proxy** in the **Network** tab of its settings. For Mac, go to **Settings** → **Preferences** → **Network** and enable **HTTP proxy**. -1. На том же компьютере с AdGuard перейдите по этой ссылке: [http://local.adguard.org/cert](http://local.adguard.org/cert). +1. On the same computer with AdGuard, follow this link: [http://local.adguard.org/cert](http://local.adguard.org/cert). -1. Нажмите кнопку **Скачать** . Если загрузка не начинается, попробуйте другой браузер, например Firefox. +1. Нажмите кнопку **Скачать** . If the download doesn’t start, try another browser, for example Firefox. -1. Перенесите загруженный файл **cert.cer** на устройство Windows, трафик которого вы хотите направлять через AdGuard. Для этого можно использовать USB-кабель, Bluetooth или облачные сервисы. +1. Transfer the downloaded **cert.cer** file to the Windows device whose traffic you want to route through AdGuard. You can use a USB cable, Bluetooth, or cloud services to do this. -1. На этом устройстве нажмите **Win**, введите `Управление сертификатами компьютеров` и нажмите **Enter**. +1. On that device, press **Win**, type `Manage computer certificates` and press **Enter**. -1. На странице *Сертификаты — Локальный компьютер* найдите папку *Доверенные корневые центры сертификации* → *Сертификаты*. +1. On the *Certificates — Local Computer* page, find the *Trusted Root Certification Authorities* → *Certificates* folder. 1. Щёлкните правой кнопкой мыши папку *Сертификаты* и выберите **Все задачи** → **Импорт...**. @@ -39,15 +39,15 @@ HTTP-трафик будет фильтроваться в любом случа 1. Щёлкните **Обзор...**, чтобы импортировать сертификат. -1. Перейдите к файлу сертификата **cert.cer**, выберите его и нажмите **Открыть**, а затем **Далее**. +1. Navigate to the **cert.cer** certificate file, select it, click **Open**, then **Next**. 1. Установите флажок **Поместить все сертификаты в следующее хранилище**. -1. Убедитесь, что в поле *Хранилище сертификатов* отображаются *Доверенные корневые центры сертификации*, и нажмите **Далее**. +1. Make sure that the *Certificate store* field displays *Trusted Root Certification Authorities* and click **Next**. 1. Нажмите **Готово**. -1. Нажмите **Win**, затем откройте **Настройки**. +1. Press **Win**, then open **Settings**. 1. Выберите **Сеть и интернет** → **Прокси-сервер**. @@ -55,7 +55,7 @@ HTTP-трафик будет фильтроваться в любом случа 1. Нажмите **Настройка** во вкладке *Использовать прокси-сервер*. -1. Включите эту опцию. В поле **IP-адрес прокси-сервера** введите IP-адрес из пункта 1. В поле **Порт** введите порт, выбранный в сетевых настройках десктопного приложения AdGuard. +1. Включите эту опцию. For **Proxy IP address**, type the IP address of your desktop computer that you noted in step 1. В поле **Порт** введите порт, выбранный в сетевых настройках десктопного приложения AdGuard. 1. Нажмите **Сохранить**. @@ -63,13 +63,13 @@ HTTP-трафик будет фильтроваться в любом случа 1. Узнайте IP-адрес вашего десктопного компьютера, на котором установлен AdGuard. -1. Убедитесь, что защита AdGuard включена. На компьютере с Windows установите флажок **Использовать AdGuard как HTTP-прокси** во вкладке **Сеть** в его настройках. For Mac, go to **Settings** → **Preferences** → **Network** and enable **HTTP proxy**. +1. Make sure that AdGuard protection is enabled. On a Windows computer, check the box **Use AdGuard as an HTTP proxy** in the **Network** tab of its settings. For Mac, go to **Settings** → **Preferences** → **Network** and enable **HTTP proxy**. -1. Перейдите по этой ссылке, используя веб-браузер: [http://local.adguard.org/cert](http://local.adguard.org/cert). +1. Follow this link using a web browser: [http://local.adguard.org/cert](http://local.adguard.org/cert). -1. Нажмите кнопку **Скачать**. Если загрузка не начинается, попробуйте другой браузер, например Firefox. +1. Нажмите кнопку **Скачать**. If the download doesn’t start, try another browser, for example Firefox. -1. Перенесите загруженный файл **cert.cer** на устройство Mac, трафик которого вы хотите направлять через AdGuard. Для этого можно использовать USB-кабель, Bluetooth или облачные сервисы. +1. Transfer the downloaded **cert.cer** file to the Mac device whose traffic you want to route through AdGuard. You can use a USB cable, Bluetooth, or cloud services to do this. 1. Дважды щёлкните загруженный файл сертификата. @@ -79,49 +79,49 @@ HTTP-трафик будет фильтроваться в любом случа 1. В разделе *Система* выделите добавленный сертификат. -1. Щёлкните по нему правой кнопкой мыши и в контекстном меню выберите **Свойства**. +1. Right-click it and select **Get Info** from the context menu. 1. Разверните *Доверие*, чтобы увидеть политики доверия для сертификата. 1. В разделе *Протокол защищённых сокетов (SSL)* выберите **Всегда доверять**. -1. Откройте **Системные настройки** → **Сеть** → и выберите верхнее активное соединение. +1. Open **System Preferences** → **Network** and select the active connection at the top. 1. Нажмите **Подробности...** и перейдите на вкладку **Прокси**. -1. Установите два флажка: *Веб-прокси (HTTP)* и *Безопасный веб-прокси (HTTPS)*. В поле **Сервер** введите IP-адрес компьютера, указанный в шаге 1. В поле **Порт** введите порт, выбранный в сетевых настройках десктопного приложения AdGuard. +1. Tick two checkboxes: *Web proxy (HTTP)* and *Secure web proxy (HTTPS)*. In the **Server** field, type the IP address of your computer that you noted in step 1. В поле **Порт** введите порт, выбранный в сетевых настройках десктопного приложения AdGuard. ### Android {#android} 1. Узнайте IP-адрес вашего десктопного компьютера, на котором установлен AdGuard. -1. Убедитесь, что защита AdGuard включена. На компьютере с Windows установите флажок **Использовать AdGuard как HTTP-прокси** во вкладке **Сеть** в его настройках. For Mac, go to **Settings** → **Preferences** → **Network** and enable **HTTP proxy**. +1. Make sure that AdGuard protection is enabled. On a Windows computer, check the box **Use AdGuard as an HTTP proxy** in the **Network** tab of its settings. For Mac, go to **Settings** → **Preferences** → **Network** and enable **HTTP proxy**. 1. На том же компьютере с AdGuard перейдите по этой ссылке, используя браузер: [http://local.adguard.org/cert](http://local.adguard.org/cert). -1. Нажмите кнопку **Скачать**. Если загрузка не начинается, попробуйте другой браузер, например Firefox. +1. Нажмите кнопку **Скачать**. If the download doesn’t start, try another browser, for example Firefox. -1. Перенесите загруженный файл **cert.cer** на устройство Android, трафик которого вы хотите направлять через AdGuard. Для этого можно использовать USB-кабель, Bluetooth или облачные сервисы. +1. Transfer the downloaded **cert.cer** file to the Android device whose traffic you want to route through AdGuard. You can use a USB cable, Bluetooth, or cloud services to do this. -1. Найдите и коснитесь ранее загруженного сертификата **cert.cer**, чтобы открыть файл и следовать инструкции по установке сертификата. +1. Locate and tap the previously downloaded **cert.cer** certificate to open the file and follow the instructions to install the certificate. -1. Устройства Android по умолчанию не доверяют сертификатам, поэтому появится предупреждение — его можно игнорировать. На некоторых телефонах вам может быть предложено ввести пароль устройства. Сделайте это, затем нажмите **OK**. Сертификат будет установлен. +1. Android devices do not trust certificates by default, so there will be a warning — you can ignore it. On some phones you may be asked to enter your device password. Do so, then press **OK**. The certificate will be installed. 1. Откройте настройки активной сети Wi-Fi. -1. Измените **Тип прокси** на **Вручную**. В поле **Имя узла прокси** введите IP-адрес из пункта 1. В поле **Порт** введите порт, выбранный в сетевых настройках десктопного приложения AdGuard. +1. Change the **Proxy type** to **Manual**. For **Proxy hostname**, enter the noted IP address of your desktop computer you noted in step 1. В поле **Порт** введите порт, выбранный в сетевых настройках десктопного приложения AdGuard. ### iOS {#ios} 1. Узнайте IP-адрес вашего десктопного компьютера, на котором установлен AdGuard. -1. Убедитесь, что защита AdGuard включена. На компьютере с Windows установите флажок **Использовать AdGuard как HTTP-прокси** во вкладке **Сеть** в его настройках. For Mac, go to **Settings** → **Preferences** → **Network** and enable **HTTP proxy**. +1. Make sure that AdGuard protection is enabled. On a Windows computer, check the box **Use AdGuard as an HTTP proxy** in the **Network** tab of its settings. For Mac, go to **Settings** → **Preferences** → **Network** and enable **HTTP proxy**. 1. На том же компьютере с AdGuard перейдите по этой ссылке, используя браузер: [http://local.adguard.org/cert](http://local.adguard.org/cert). -1. Нажмите кнопку **Скачать** . Если загрузка не начинается, попробуйте другой браузер, например Firefox. +1. Нажмите кнопку **Скачать** . If the download doesn’t start, try another browser, for example Firefox. -1. Перенесите загруженный файл **cert.cer** на устройство iOS, трафик которого вы хотите направлять через AdGuard. Для этого можно использовать USB-кабель, Bluetooth или облачные сервисы. +1. Перенесите загруженный файл **cert.cer** на устройство с iOS, трафик которого вы хотите направлять через AdGuard. You can use a USB cable, Bluetooth, or cloud services to do this. 1. На устройстве iOS откройте **Настройки** → **Профиль загружен** и нажмите **Установить** в правом верхнем углу. Введите пароль и подтвердите установку. Нажмите **Готово**. @@ -129,4 +129,4 @@ HTTP-трафик будет фильтроваться в любом случа 1. На этом устройстве откройте настройки активной сети Wi-Fi. -1. Измените **Тип прокси** на **Вручную**. В поле **Имя узла прокси** введите IP-адрес из пункта 1. В поле **Порт** введите порт, выбранный в сетевых настройках десктопного приложения AdGuard. +1. Change the **Proxy type** to **Manual**. В поле **Имя узла прокси** введите IP-адрес из пункта 1. В поле **Порт** введите порт, выбранный в сетевых настройках десктопного приложения AdGuard. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/ru/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 524829280ec..8c5d6d030e8 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ sidebar_position: 4 ### Как описать проблему -Постарайтесь предоставить как можно больше подробностей — так нам будет проще воспроизвести ошибку и понять, как её исправить. Here’s what we expect a bug report to include: +Постарайтесь предоставить как можно больше подробностей — так нам будет проще воспроизвести ошибку и понять, как её исправить. Вот что мы ожидаем увидеть в сообщении об ошибке: - Версия приложения - Версия ОС @@ -26,9 +26,9 @@ sidebar_position: 4 - Повторялось ли она и с какой частотой - Используете ли вы VPN или программу-антивирус -### How to collect logs +### Как собирать логи -Read about collecting logs in dedicated articles for each platform. +О сборе логов читайте в статьях для каждой платформы. ## Как голосовать за сообщения об ошибках или запросы на добавление функций diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/guides/report-website.md b/i18n/ru/docusaurus-plugin-content-docs/current/guides/report-website.md index 1438541173a..7c8e0400311 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/guides/report-website.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/guides/report-website.md @@ -12,7 +12,7 @@ sidebar_position: 3 - Ошибка, допущенная авторами фильтров при создании правила; - Повторное размещение рекламы. Узнайте больше об этом методе [в нашем блоге](https://adguard.com/en/blog/ad-reinsertion.html). -Вы можете помочь нам, заполнив форму с примерами рекламы, с которой вы столкнулись. Для этого воспользуйтесь инструкциями для вашей ОС. +You can help us by filling in a form with examples of ads you have encountered. Для этого воспользуйтесь инструкциями для вашей ОС. ## Отправка жалобы {#report} @@ -26,8 +26,8 @@ sidebar_position: 3 ### Браузерное расширение {#extension} -- Откройте настройки расширения браузера, нажав на соответствующий значок; -- Нажмите на **Сообщить о проблеме**: +- Open the browser extension settings by clicking the corresponding icon; +- Click **Report an issue**: ![проблема с расширением *mobile_border](https://cdn.adtidy.org/blog/new/5si74extension.png) @@ -53,7 +53,7 @@ sidebar_position: 3 ### Mac {#mac} -- Откройте [Браузерный помощник AdGuard](/adguard-for-mac/features/browser-assistant) и нажмите **Сообщить о проблеме**: +- Open [AdGuard Browser Assistant](/adguard-for-mac/features/browser-assistant) and hit **Report an issue**: ![mac *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/guides/browser-assistant-mac.png) @@ -135,7 +135,7 @@ sidebar_position: 3 1. Отключите **Антитрекинг**; 2. Если это решило проблему, включите модуль и поочерёдно отключите опции **Антитрекинга** c проверкой результата. Это необходимо для того, чтобы определить, какие именно настройки приводят к некорректной блокировке; -3. Если вам удалось выявить, какая настройка приводит к некорректной работе страницы, сообщите об этом разработчикам при заполнении формы (см. выше). Также желательно восстановить настройки по умолчанию; +3. If you have managed to detect which setting "breaks" a page, you should inform the developers when filling out the form (see above). Также желательно восстановить настройки по умолчанию; 4. Если проблема не решилась, перейдите к разделу **Расширения**. ### **Расширения** @@ -146,4 +146,4 @@ sidebar_position: 3 ### **Сторонние блокировщики** -Некоторые браузеры и антивирусы (такие как Яндекс.Браузер, Kaspersky и т. д.) имеют встроенные блокировщики рекламы. Они могут влиять на функционирование сайтов, вызывать конфликты с AdGuard и приводить к некорректной работе сайтов. Если вы пользуетесь подобными программами, убедитесь, что проблема вызвана именно **AdGuard**: отключите фильтрацию **AdGuard** и попробуйте повторить проблему. Если проблема сохранится, значит, она вызвана другим приложением или браузером. Если же проблема вызвана **AdGuard**, выполните действия, указанные в предыдущих пунктах. +Некоторые браузеры и антивирусы (такие как Яндекс.Браузер, Kaspersky и т. д.) имеют встроенные блокировщики рекламы. Они могут влиять на функционирование сайтов, вызывать конфликты с AdGuard и приводить к некорректной работе сайтов. If you are using such programs, first make sure that the problem is caused by **AdGuard**: disable **AdGuard** filtering and try to reproduce the problem. Если проблема сохранится, значит, она вызвана другим приложением или браузером. Если же проблема вызвана **AdGuard**, выполните действия, указанные в предыдущих пунктах. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/ru/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index fa9ff5ddb2d..3498141d3e3 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -5,32 +5,32 @@ sidebar_position: 5 Скриншот — это снимок экрана вашего компьютера или мобильного устройства, который можно сделать с помощью стандартных инструментов или специальной программы/приложения. -Иногда служба поддержки запрашивает скриншоты для лучшего понимания. В этом разделе приведены все необходимые комбинации для создания скриншотов на компьютерах и мобильных устройствах на различных платформах. +Sometimes screenshots are requested by the support team for a better understanding. В этом разделе приведены все необходимые комбинации для создания скриншотов на компьютерах и мобильных устройствах на различных платформах. ### Android {#android} -Сделать скриншот на устройствах Android можно несколькими способами, в зависимости от модели устройства и его производителя. +Taking a screenshot on an Android device can be done in various ways, depending on the device model and its manufacturer. -Как правило, для Android используется следующая комбинация кнопок: +Generally, the following button combination is used for Android: -- **Одновременно нажмите кнопки *уменьшения громкости* и *питания*** +- **Press the *Volume Down* and the *Power* buttons at the same time** Ваше Android-устройство захватит весь экран и сохранит его в виде фотографии, которую вы сможете найти в папке Скриншот в Галерее. -Для старых устройств можно использовать следующие комбинации: +For older devices, you may use following combinations: -- **Одновременно нажмите кнопки *Домой* и *Питание*** -- **Одновременно нажмите кнопки *Назад* и *Домой*** +- **Press *Home* and *Power* at the same time** +- **Press *Back* and *Home* at the same time** -На Android 8 и более поздних версиях вы также можете сделать скриншот, например, проведя рукой по экрану под углом 90 градусов (устройства Samsung), проведя тремя пальцами вниз (устройства OnePlus) и т. д. +On Android 8 and later you can also take a screenshot with other manipulations, for example, with swiping your hand over the screen at a 90-degree angle to trigger a screenshot (Samsung devices), or with swiping down three fingers (OnePlus devices), etc. -Возможности создания скриншота зависят от марки и модели. Проверьте настройки устройства, чтобы найти метод, который лучше всего подходит для вас. +The options for taking a screenshot vary by brand and model. Check your device’s settings to find the method that works best for you. -Кроме того, вы можете использовать приложения для создания скриншотов, такие как *Screenshot Easy*, *Screenshot Snap*, *Screenshot Ultimate* и другие. +Besides, you can always use any special apps for taking screenshots on your devices, for example — *Screenshot Easy*, *Screenshot Ultimate*, *Screenshot Snap*, etc. ### iOS {#ios} -Все устройства на базе iOS (за исключением совсем ранних версий) позволяют создавать скриншоты, используя стандартные средства. +Any iOS device (except very old ones) lets you take a screenshot using standard tools. Для того, чтобы сделать скриншот на iOS-устройстве, воспользуйтесь следующей комбинацией: @@ -44,25 +44,25 @@ sidebar_position: 5 ### Windows {#windows} -- **Чтобы сделать снимок экрана компьютера, нажмите клавишу *PrtScn*** +- **To take a screenshot on Windows, press the *PrtScn* key** На некоторых ноутбуках необходимо удерживать клавишу *Fn*, а затем нажимать *PrtScn*. *Please note: The PrtScn (Print Screen) key may be abbreviated differently on different keyboards — PrntScrn, PrtScn, PrtScr, or PrtSc.* -Windows сделает снимок всего экрана и скопирует его в буфер обмена. +Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Нажмите и удерживайте клавишу *Alt* и нажмите *PrtScn* (или *Fn + Alt + PrtScn * на некоторых ноутбуках)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: -- ***Нажмите сочетание клавиш ***Win + Shift + S****** +- ***Press ***Win + Shift + S****** -После того, как вы сделаете скриншот, он сохранится в буфере обмена. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Или, если вам нужно сохранить скриншот как файл, откройте стандартную программу **Paint** (или любую другую, работающую с изображениями). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +После того, как вы сделаете скриншот, он сохранится в буфере обмена. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Или, если вам нужно сохранить скриншот как файл, откройте стандартную программу **Paint** (или любую другую, работающую с изображениями). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. Как только вы нажмете пки, снимок экрана будет автоматически сохранён в виде файла в вашей папке *Картинки* → *Папка скриншотов*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. Существует также специальная программа *Ножницы* для создания скриншотов, которая запускается из меню *Пуск > Все программы > Стандартные*. Ножницы позволяют сделать скриншот любой области экрана или всего экрана целиком. После создания скриншота с помощью данной программы вы сможете редактировать изображение и сохранить его в любой папке вашего компьютера. @@ -70,26 +70,26 @@ Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: -- ***Нажмите и удерживайте ***⌘ Cmd + Shift + 3****** +- ***Press and hold ***⌘ Cmd + Shift + 3****** Ваш компьютер зафиксирует изображение всего экрана и сохранит его на рабочем столе. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: -- **Нажмите и удерживайте *⌘ Cmd + Shift + 4 + пробел*. Указатель мыши изменится на значок камеры. Щёлкните по окну, чтобы захватить его. Чтобы отменить создание скриншота, нажмите Esc** +- **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. Указатель мыши изменится на значок камеры. Щёлкните по окну, чтобы захватить его. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Перетащите перекрестие, чтобы выделить нужную область. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: -- ***Нажмите сочетание клавиш ***⌘ Cmd + Shift + 6****** +- ***Press ***⌘ Cmd + Shift + 6****** Ваш компьютер зафиксирует изображение всего *Touch Bar* и сохранит его как файл на вашем рабочем столе. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. Вы также можете сделать скриншот, используя **Preview** и выбрав **Сделать скриншот** (выбранной зоны, окна или всего экрана). Пользуясь **Preview** вы можете сохранять файлы в форматах JPG, TIFF, PDF и др. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/intro.md b/i18n/ru/docusaurus-plugin-content-docs/current/intro.md index dda9303d0e6..b9aa779fdb2 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/intro.md @@ -6,7 +6,7 @@ slug: / ## Что такое Блокировщик рекламы AdGuard -AdGuard — один из лидеров на рынке программ для блокировки рекламы с более чем 15-летним опытом, почти десятком продуктов для разных платформ и более чем 375 млн установок пользователями. В отличие от других решений по блокировке рекламы, большинство из которых работают на основе браузера, мы предлагаем отдельные приложения для всех основных платформ, как десктопных, так и мобильных. Приложения AdGuard более мощные, чем браузерные расширения, могут блокировать больше и делать это эффективнее: +AdGuard is one of the leaders on the market of ad-blocking software with 15+ years of experience, almost a dozen products for various platforms, and over 375 million user installs. В отличие от других решений по блокировке рекламы, большинство из которых работают на основе браузера, мы предлагаем отдельные приложения для всех основных платформ, как десктопных, так и мобильных. Приложения AdGuard более мощные, чем браузерные расширения, могут блокировать больше и делать это эффективнее: - [AdGuard для Windows](/adguard-for-windows/features/home-screen) - [AdGuard для Mac](/adguard-for-mac/features/main) @@ -20,4 +20,4 @@ AdGuard — один из лидеров на рынке программ для ## Не только блокировка рекламы -Блокировщик рекламы AdGuard не просто блокирует рекламу. Он защитит вас от онлайн-отслеживания и повысит вашу конфиденциальность во многих отношениях. В зависимости от конкретного продукта AdGuard также может предложить такие преимущества, как DNS-фильтрация для более полной защиты, Родительский контроль для защиты детей от неприемлемого контента, Журнал фильтрации для лучшего контроля над интернет-трафиком и многое другое. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +Блокировщик рекламы AdGuard не просто блокирует рекламу. Он защитит вас от онлайн-отслеживания и повысит вашу конфиденциальность во многих отношениях. В зависимости от конкретного продукта AdGuard также может предложить такие преимущества, как DNS-фильтрация для более полной защиты, Родительский контроль для защиты детей от неприемлемого контента, Журнал фильтрации для лучшего контроля над интернет-трафиком и многое другое. Эта База знаний содержит подробную информацию обо всех продуктах и функциях — переходите к любой интересующей вас статье. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index 7b086cf7236..442a7d5ef6e 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ sidebar_position: 4 Работа с фильтрами, блокирующими рекламу, требует специальных навыков. Если они у вас есть, и вы знаете, как создавать правила, то направляйтесь прямо в наш репозиторий [AdGuard Filters](https://github.com/AdguardTeam/AdguardFilters) на GitHub. Там вы найдёте множество открытых вопросов, каждый из которых ссылается на проблему с каким-либо сайтом — пропущенное объявление, ложное срабатывание и т. д. Выбирайте любой и предлагайте свои правила в комментариях. Инженеры фильтров AdGuard рассмотрят ваше предложение и добавят правило в фильтры, если оно окажется корректным. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +Если вы ещё не знакомы с синтаксисом наших правил фильтрации или просто хотите освежить знания, то вам нужно обратиться к [нашей Базе знаний](/general/ad-filtering/create-own-filters). ### Как мы благодарим помощников {#rewards} diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/guidelines.md b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/guidelines.md index c6d9d184e02..f85ca109cb8 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/guidelines.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/guidelines.md @@ -58,7 +58,7 @@ sidebar_position: 3 ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/request.png) -1. Помимо предложения новых переводов, вы также можете оставлять комментарии к строкам. Используйте комментарии, чтобы сообщать нам об ошибках в исходном тексте или существующих переводах, делать заметки или задавать вопросы. Если вы видите комментарий к вашему переводу — попробуйте ответить на него. +1. Помимо предложения новых переводов, вы также можете оставлять комментарии к строкам. Use comments to let us know about mistakes in the source text or existing translations, make notes, or ask questions. Если вы видите комментарий к вашему переводу — попробуйте ответить на него. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/comments.png) diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index f32ac7ee267..cad59b1b93f 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -14,7 +14,7 @@ sidebar_position: 4 Например, у английских слов две словоформы: в единственном числе — *one star*, «одна звезда», во множественном — *two stars*, «две звезды». Неважно, скажете ли вы пять, двадцать шесть или даже пятьсот тридцать две звезды — окончание «s» останется прежним. Но некоторые языки могут содержать только одну плюральную форму или наоборот — больше, чем две. -В отличие от английского, в польском языке есть три формы множественного числа существительных. Одна из них используется, когда говорят о чём-либо в единственном числе, другая — во множественном числе, но с числами, оканчивающимися на 2–4, не включая 12–14, а третья форма — для слов, перед которыми стоят все остальные числа. +В отличие от английского, в польском языке есть три формы множественного числа существительных. One of them is used when speaking about something in the singular, another form is used in the plural but with numbers ending in 2–4, excluding 12–14, and the third form — for words with other numbers in front of them. Ниже показано разделение на плюральные формы в зависимости от числительных в польском языке. Группы числительных определяют форму слова, которое к ним относится. @@ -24,13 +24,13 @@ sidebar_position: 4 Английская версия: Польские эквиваленты: - 1. форма — It takes one hour. 1. форма — Zajmuje to godzinę. - 2. форма — It takes two hours. 2. форма — Zajmuje to dwie godziny. - 3. форма — It takes five hours. 3. форма — Zajmuje to pięć godzin. + 1. form — It takes one hour. 1. form — Zajmuje to godzinę. + 2. form — It takes two hours. 2. form — Zajmuje to dwie godziny. + 3. form — It takes five hours. 3. form — Zajmuje to pięć godzin. Польское *'godzinę'* (час) имеет три разные формы, английское слово с теми же числительными склоняется только по двум формам. -Кроме польского, есть много других языков, которые имеют три и более форм множественного числа: например, русский, сербский, словацкий, чешский и т. д. Но не все они подчиняются одному и тому же правилу. Поэтому важно знать, сколько плюральных форм содержится в вашем языке и как их правильно применять. +Кроме польского, есть много других языков, которые имеют три и более форм множественного числа: например, русский, сербский, словацкий, чешский и т. д. Но не все они подчиняются одному и тому же правилу. That's why it's so important to know how many plurals your language has, and how to use them correctly. ## Где можно узнать о количестве форм множественного числа? {#where-to-learn} @@ -38,7 +38,7 @@ sidebar_position: 4 Вот некоторые источники информации, которые можно использовать. -На сайте [Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) есть информация о большом количестве языков. Количество форм множественного числа для разных языков показано так: `nplurals=2`, `nplurals=4` и так далее. Цифра после знака равенства `=` означает количество форм множественного числа соответствующего языка. +На сайте [Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) есть информация о большом количестве языков. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Информацию о плюральных формах можно также найти на сайте [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). В правилах плюральных форм CLDR указана дополнительная форма слова для десятичных чисел (1,5; 2,3; 100,1…), но мы не используем их в переводах AdGuard. @@ -92,7 +92,7 @@ sidebar_position: 4 ### 4. Строки, разделённые вертикальной чертой {#4type} -Это самый сложный тип строк AdGuard, который в основном используется в проекте `AdGuard Websites`. +This is the most complicated type of AdGuard strings which is mostly used in the `AdGuard Websites` project. Обратите внимание на знак вертикальной черты между предложениями и плейсхолдер **%count%** в оригинальных фразах — это поможет вам определить фразы, в которых перевод требует использования форм множественного числа. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 7c1290f2fde..9f5ab926e7d 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: Переводы AdGuard sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Примечание:** Вы можете задать нам любые вопросы о переводах AdGuard — просто отправьте письмо по адресу [translate@adguard.com](mailto:translate@adguard.com) или присоединитесь к нам в [Telegram](https://t.me/joinchat/UVYTLcHbr8JmOGIy). -When it comes to translations, we at AdGuard always heavily rely on volunteers. +В переводах AdGuard мы в значительной степени полагаемся на помощь волонтёров. -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +На данный момент мы используем платформу [Crowdin](https://crowdin.com/) для управления переводами наших продуктов. Регистрируйтесь там, если тоже хотите принять участие в переводах AdGuard. -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +Если вы хотите быть в числе волонтёров, которые помогают переводить AdGuard, прочитайте, [как стать нашим переводчиком](../become-translator) и [что вы можете получить взамен](../rewards). diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 268ecf63ed4..0bdebf1498b 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: 'AdGuard в Crowdin: что переводить в первую очер sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +В Crowdin есть пять основных проектов AdGuard — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), и [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). У нас нет чётких указаний, с каких файлов или продуктов проекта *AdGuard Applications*, а также проектов для баз знаний, начинать. Просто выберите любой понравившийся продукт. Мы хотим подчеркнуть только пару моментов: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- Наше приложение становится доступным только на тех языках, для которых выполнены все переводы в Crowdin; - Мы рекомендуем переводить описания для магазинов приложений во вторую очередь, потому что без перевода самих продуктов описания будут не нужны. В проекте *AdGuard Websites* ситуация иная. Языки могут быть добавлены на сайт, даже если сайт полностью не переведён. Однако переводы некоторых файлов всё-таки необходимы для добавления локали. Именно с них мы и рекомендуем вам начинать — они перечислены ниже: @@ -32,4 +32,4 @@ There are five major AdGuard projects on Crowdin — [AdGuard Applications](http Добавление новых строк, а также обновление существующих в этих файлах требует особого внимания со стороны переводчиков и пруфридеров проекта. -Помимо сайтов в проекте AdGuard Websites есть файл для перевода [транзакционных писем](https://crowdin.com/project/adguard-websites/en#/emails). Вновь добавленные строки в этом файле также имеют высокий приоритет. +In addition to websites, there is a file for translating [transactional emails](https://crowdin.com/project/adguard-websites/en#/emails) in the AdGuard Websites project. Вновь добавленные строки в этом файле также имеют высокий приоритет. diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index ced50c8e41c..46997e752e6 100644 --- a/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/ru/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -25,4 +25,4 @@ Cуществующие статьи Базы знаний можно перев ## Работа над существующими задачами -Иногда появляются [открытые задачи](https://github.com/AdguardTeam/KnowledgeBase/issues), связанные с обновлением Базы знаний. Помочь можно [таким же образом](#suggest-change), как вы предлагаете любые другие изменения в Базе знаний. Выберите любую задачу, которая кажется вам интересной, и начните работать над ней. Все возникающие вопросы вы можете задавать прямо в комментариях к задаче. +Помимо написания и перевода статей, вы можете поработать над [открытыми задачами](https://github.com/AdguardTeam/KnowledgeBase/issues), связанными с обновлением данной Базы знаний. Помочь можно [таким же образом](#suggest-change) , как вы предлагаете любые другие изменения в Базе знаний. Выберите любую задачу, которая кажется вам интересной, и начните работать над ней. Все возникающие вопросы вы можете задавать прямо в комментариях к задаче. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/sk/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/sk/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/sk/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/sk/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/intro.md b/i18n/sk/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/sk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/sl/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/sl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/sl/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/sl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/intro.md b/i18n/sl/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/sl/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/sv/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/sv/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/sv/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/sv/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/intro.md b/i18n/sv/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/sv/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/ta/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/ta/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/ta/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/ta/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/intro.md b/i18n/ta/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/ta/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 693bb2b4d39..25ad26543b8 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ AdGuard Tarayıcı Uzantısı ücretsiz ve yüklemesi kolay olmasına, reklamlar ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. Kötü amaçlı veya izleme uzantısı, sunucusuna size reklam göstermek veya etkinliğinizi izlemek için bir istek gönderirse, AdGuard Tarayıcı Uzantısı bu isteği engellemeyecektir; +`2` – the extension is unable to detect requests from other extensions. Kötü amaçlı veya izleme uzantısı, sunucusuna size reklam göstermek veya etkinliğinizi izlemek için bir istek gönderirse, AdGuard Tarayıcı Uzantısı bu isteği engellemeyecektir; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Bazı öğeler sayfaya ulaşabilir ve yükleme sürecini yavaşlatabilir. Ayrıca, tarayıcı tabanlı reklam engelleyicilerin aksine, AdGuard uygulaması reklamları tarayıcıya yüklenmeden önce engeller. Bu, veri tasarrufu ve sayfa açılışını hızlandırır. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Bazı öğeler sayfaya ulaşabilir ve yükleme sürecini yavaşlatabilir. Ayrıca, tarayıcı tabanlı reklam engelleyicilerin aksine, AdGuard uygulaması reklamları tarayıcıya yüklenmeden önce engeller. Bu, veri tasarrufu ve sayfa açılışını hızlandırır. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index f4dc446a1f1..fb6fb0cdc5c 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ Tüm filtreler rollerine göre gruplandırılmıştır. Örneğin, reklam engell ## Özel filtreler -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 80a9bff5454..fb6563a132b 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ Uzantının ana sayfasına, tarayıcınızın araç çubuğundaki uzantı simges On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Ayrıca, herhangi bir site hakkında bir şikayet gönderebilir (örneğin, sayfada gözden kaçan reklamlar varsa, filtre mühendislerimiz raporu inceler ve sorunu çözer) ve uygulanan engelleme kurallarına ilişkin istatistikleri görebilirsiniz. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Ayrıca, herhangi bir isteği engellemenize veya daha önce engellenen bir isteği iki tıklamayla İzin listesine eklemenize olanak tanır. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Ayrıca, herhangi bir isteği engellemenize veya daha önce engellenen bir isteği iki tıklamayla İzin listesine eklemenize olanak tanır. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). Uzantının ana menüsünün sağ üst köşesindeki simgelere tıklayarak uzantı ayarlarını açabilir veya korumayı duraklatabilirsiniz. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 83991f0b8b8..98c102c36df 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. Ayarlar bir .json dosyası olarak kaydedilecektir. To import the previously saved settings configuration, use the _Import settings_ function. Farklı ayar profilleri arasında hızlıca geçiş yapmak ve hatta ayar yapılandırmalarını farklı tarayıcılar arasında aktarmak için bile kullanabilirsiniz. +You can save your settings configuration by clicking the _Export settings_ button. Ayarlar bir .json dosyası olarak kaydedilecektir. To upload the previously saved settings configuration, use the _Import settings_ function. Farklı ayar profilleri arasında hızlıca geçiş yapmak ve hatta ayar yapılandırmalarını farklı tarayıcılar arasında aktarmak için bile kullanabilirsiniz. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Ayrıca, uygulanan kurallarla ilgili istatistikleri göndererek filtrelerin geli ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index ebc02ad3467..00000000000 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: Chrome için AdGuard Tarayıcı Uzantısı MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Uzantılarımızı nerede bulabilirsiniz - -MV3 sürümü\*\* yakında [Chrome Web Mağazası'ndaki](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg) eski uzantımızın yerini alacak. - -MV3'ün **beta sürümü** [Chrome Web Mağazasında](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf) hâlâ mevcut olacaktır. - -Eski beta uzantısı [**AdGuard Reklam Engelleyici MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) olarak yeniden adlandırılacak ve Google tarafından kullanımdan kaldırılana kadar desteklenecektir. - -## Özellikler ve ayarlarda temel değişiklikler - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Bazı kurallar artık DNR formunda uygulandığından, filtreleri istek üzerine güncelleyemiyoruz, yalnızca mağazalardaki incelemeyle birlikte uzantıyı güncelleme işleminin tamamını gerçekleştiriyoruz. - -- **Filtreleme günlüğü** - - ![Filtreleme günlüğü \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. Kesin bilgi için, uzantının "Paketlenmemiş öğe" hâlini tarayıcınıza kendiniz yüklemeniz gerekir. Bunu nasıl yapacağınıza dair ayrıntılı talimatları [ayrı bir makalede](adguard-browser-extension/solving-problems/debug-rules) bulabilirsiniz. - -- _İzleme koruması_ (eski adıyla _Gizlilik modu_) - - ![İzleme koruması \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Güvenlik](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maksimum kural ve filtre sayısı - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Kural limitleri \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Çok fazla uzantı \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -Daha fazla örnek [GitHub'da](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples) bulunabilir. - -### Ağ kuralları - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index 649c54f91d5..44fb1f0273c 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Tarayıcı korumalı sayfalar -sidebar_position: 6 +sidebar_position: 5 --- :::bilgi diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index aae5132dfa4..00000000000 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Ön koşullar - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## Uzantı nasıl klonlanır - -1. Depoyu klonlayın: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Dizine gidin: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## Tarayıcıda paketlenmemiş öğe nasıl yüklenir - -1. Geliştirici modunu açın: - - ![Geliştirici modu](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. _Paketlenmemiş öğe yükle_ öğesine tıklayın: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -Bu kadar! - -## Kurallarda nasıl hata ayıklanır - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 2e04c4d06e2..0b0eb9e26b9 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ Bağlam menüsünden uygulamanın istatistiklerine de erişebilirsiniz. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. Bu nedenle, tüm uygulamaları yönlendirmeye veya filtrelemeye çalışırken aşağıdaki uyarıyı görebilirsiniz: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 8788797bc9b..a2c6fe4c824 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 57fe66c3a0b..aa16c3cdcd2 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Bildirimler -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index bfd5d67085e..5eddfe5032a 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index ccbff6464c5..ea5555a56a6 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Android işletim sisteminin güvenlik önlemleri nedeniyle bazı AdGuard özellikleri yalnızca root erişimli cihazlarda kullanılabilir. İşte bunların listesi: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index ccd9ae387a3..2e729730402 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -27,7 +27,7 @@ _Automation_ allows you to manage AdGuard via tasker apps. _Watchdog_ helps protect AdGuard from being disabled by the system ([read more about Android's battery save mode](/adguard-for-android/solving-problems/background-work/)). Girdiğiniz değer, watchdog denetimleri arasındaki saniye cinsinden aralık olacaktır. -_Logging level_ defines what data about the app's operation should be logged. Varsayılan olarak, uygulama etkinlikleriyle ilgili verileri toplar. The _Debug_ level logs more events — enable it if asked by the AdGuard team to help them get a better understanding of the problem. [Günlükleri toplama ve gönderme hakkında daha fazla bilgi edinin](/adguard-for-android/solving-problems/log/) +_Logging level_ defines what data about the app's operation should be logged. Varsayılan olarak, uygulama etkinlikleriyle ilgili verileri toplar. The _Debug_ level logs more events — enable it if asked by the AdGuard team to help them get a better understanding of the problem. [Read more about collecting and sending logs](/adguard-for-android/solving-problems/log/) ![Advanced \*mobile\_border](https://cdn.adtidy.org/blog/new/vshfnadvanced.png) @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Kullanıcı Betikleri -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. Bir kullanıcı betiği yüklemek için özel bir kullanıcı betiği yöneticisine ihtiyacınız vardır. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. Bir kullanıcı betiği yüklemek için özel bir kullanıcı betiği yöneticisine ihtiyacınız vardır. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index 954cd3d18ff..3e2eeeaa775 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index 46e42cc4966..a43e68e1cf9 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Tamamlandı! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Ayarları *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index bbcd686c319..e9ead1a414a 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. Bunun nedeni, AdGuard'ın çeşitli uygulamalardan filtrelediği tüm trafiği saymasıdır. Sonuç olarak, AdGuard'ın toplam veri ve pil kullanımındaki payı abartılırken, diğer uygulamalar olduğundan az gösterildi. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. Bunun nedeni, AdGuard'ın çeşitli uygulamalardan filtrelediği tüm trafiği saymasıdır. Sonuç olarak, AdGuard'ın toplam veri ve pil kullanımındaki payı abartılırken, diğer uygulamalar olduğundan az gösterildi. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 6c6913c7a74..417604dce71 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index 569d0f797a6..b3da26e4c1a 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: HAR dosyaları nasıl edinilir sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR dosyaları [AdGuard Gizlilik Politikasına](https://adguard.com/en/privacy.h ## HAR dosyaları nedir? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## HAR dosyaları nasıl edinilir -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. HAR dosyalarını edinmek için şu adımları izleyin: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::not diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index b1849142add..2cbf4562b09 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. [**adguardcert** Magisk modülünün son sürümünü](https://github.com/AdguardTeam/adguardcert/releases/latest/) yükleyin. -1. *Magisk → Modüller → Depolamadan yükle* öğesini açın ve indirilen **adguardcert** dosyasını seçin. AdGuard Kişisel CA sertifikası sistem depolamasına kopyalanacaktır. +1. *Magisk → Modüller → Depolamadan yükle* öğesini açın ve indirilen **adguardcert** dosyasını seçin. Bu, AdGuard Personal CA'yı kullanıcı depolamasından sistem depolamasına taşır. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f040140a75e..00c8ccfd95f 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,7 +23,7 @@ AdGuard gizliliğinizi korumaya kararlıdır. [Gizlilik Politikamıza](https://a ::: -### Recording debug log +### Hata ayıklama günlüğü toplama **hata ayıklama** günlüğünü toplamak ve bize göndermek için aşağıdaki adımları uygulamanız gerekir: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index 6c70d001232..c0ab25d4c61 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -15,7 +15,7 @@ Günlüklerde sağlanan veriler ve/veya dosyalar [AdGuard Gizlilik Politikasına ::: -Bazen normal bir günlük, sorunun kaynağını belirlemek için yeterli olmayabilir. In such cases a system log is needed. Aşağıda nasıl toplanacağı ve alınacağı ile ilgili talimatlar bulunmaktadır: Geliştirici seçenekleri ve Logcat aracılığıyla. +Bazen normal bir günlük, sorunun kaynağını belirlemek için yeterli olmayabilir. In such cases a system log is needed. Below are instructions on how to collect and get it: via Developer options and Logcat. :::not diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 22795d9b125..efa9c73f730 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Yalnızca hata ayıklama amacıyla kullanın! #### Encrypted Client Hello -Her şifrelenmiş internet bağlantısının bir de şifrelenmemiş kısmı vardır. Bu, bağlandığınız sunucunun adını içeren ilk pakettir. Encrypted Client Hello teknolojisinin bu sorunu çözmesi ve şifrelenmemiş bilgilerin son kısmını şifrelemesi gerekiyor. To benefit from it, enable the *Encrypted Client Hello* option. Alan adı için ECH yapılandırmasını aramak için yerel bir DNS proxy'si kullanır. If it is found, Client Hello packet will be encrypted. +Her şifrelenmiş internet bağlantısının bir de şifrelenmemiş kısmı vardır. Bu, bağlandığınız sunucunun adını içeren ilk pakettir. Encrypted Client Hello teknolojisinin bu sorunu çözmesi ve şifrelenmemiş bilgilerin son kısmını şifrelemesi gerekiyor. To benefit from it, enable the *Encrypted Client Hello* option. Alan adı için ECH yapılandırmasını aramak için yerel bir DNS proxy'si kullanır. Eğer bulunursa, ClientHello paketi şifrelenecektir. #### OCSP denetimi @@ -147,7 +147,7 @@ Burada filtrelenmesi gereken bağlantı noktası aralıklarını belirtebilirsin Bu ayar etkinleştirilirse, AdGuard engellenen HTML öğelerini *Son etkinlik* öğesinde kaydeder. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index c72fcd75b2c..19b56544a31 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Daha sonra size aşağıdakileri açıklayan üç ekran sunulacaktır: - Why filter HTTPS traffic - Bu filtreleme işleminin güvenliği - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index 949a0441600..2de8fe4d500 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Aşağıda AdGuard'da proxy olarak çalışacak şekilde yapılandırabileceğiniz en ünlü uygulamaların bir listesini bulabilirsiniz. :::not @@ -41,11 +41,11 @@ Bu makalede, AdGuard ile çalışmak için en popüler proxy'lerden bazıların | Proxy ana makine | *127.0.0.1* | | Proxy bağlantı noktası | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Veya **Proxy sunucusu** → **Proxy sunucusu ekle** öğesine dokunabilir, bu değerleri elle girebilir ve Orbot'u varsayılan proxy olarak ayarlayabilirsiniz. 1. Cihazınızın trafiğini proxy üzerinden yönlendirmek için ana Proxy düğmesini ve AdGuard korumasını etkinleştirin. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Artık AdGuard tüm trafiği Orbot üzerinden yönlendirir. Orbot'u devre dışı bırakırsanız, AdGuard'da giden proxy ayarlarını devre dışı bırakana kadar internet bağlantısı kullanılamayacaktır. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. Bunu yapmak için **Uygulama yönetimi** öğesine ilerlemeniz, uygulamayı seçmeniz ve **Trafiği AdGuard üzerinden yönlendir** öğesini açmanız gerekir. +AdGuard proxy ayarlarını yapılandırdıktan sonra bile belirli trafiğin giden proxy üzerinden yönlendirilmesini engelleyebilecek bir faktör vardır. Uygulamanın kendisini trafiği AdGuard üzerinden gönderecek şekilde ayarlamazsanız bu durumla karşılaşabilirsiniz. Bunu yapmak için **Uygulama yönetimi** öğesine ilerlemeniz, uygulamayı seçmeniz ve **Trafiği AdGuard üzerinden yönlendir** öğesini açmanız gerekir. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 9b9f0e4f3bd..637e8231bdb 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::not -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 7e07ac16220..00000000000 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Ücretsiz ile tam sürüm karşılaştırması -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. Nasıl çalıştığını görmek için [AdGuard uygulamasını indirin](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index f370b3b68c0..6a67e860b1e 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. Cihazınıza yüklemek iç ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index 8eaed412014..05c04a2a109 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ Bu makale, cihazınızı sistem düzeyinde koruyan çok işlevli bir reklam enge 1. Bir video seçin ve *Paylaş* öğesine dokunun. 1. *Diğer* öğesine dokunun ve ardından *YouTube Reklamlarını Engelle (AdGuard tarafından)* öğesini seçin. -The video now opens in AdGuard's ad-free player. +AdGuard reklamsız video oynatıcısını açar. ## Safari'de YouTube'daki reklamlar nasıl engellenir @@ -31,4 +31,4 @@ AdGuard'a tüm sitelere erişim izni verdiğinizden emin olun. Bunu Safari → U 1. Bir video seçin ve *Paylaş* öğesine dokunun. 1. *YouTube Reklamlarını Engelle (AdGuard tarafından)* öğesine dokunun. -The video now opens in AdGuard's ad-free player. +AdGuard reklamsız video oynatıcısını açar. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5148bbbcc6..6332d15d871 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index 0af686901cf..155dcf51a7f 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ Changing *Low-level settings* can cause problems with the performance of AdGuard İki ana tünel modu vardır: *Bölünmüş* ve *Tam*. *Split-Tunnel* modu, AdGuard ve sözde "Kişisel VPN" uygulamalarının uyumluluğunu sağlar. *Tam Tünel* modunda başka hiçbir VPN AdGuard ile aynı anda çalışamaz. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. Şu anda hiçbir reklam engellenmiyor ve DNS trafiği şifrelenmiyor. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. Şu anda hiçbir reklam engellenmiyor ve DNS trafiği şifrelenmiyor. -*Tam Tünel* modunda yalnızca AdGuard ayarlarında belirtilen DNS sunucusu kullanılır. Yanıt vermezse, internet basitçe çalışmaz. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +*Tam Tünel* modunda yalnızca AdGuard ayarlarında belirtilen DNS sunucusu kullanılır. Yanıt vermezse, internet basitçe çalışmaz. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. Varsayılan olarak, AdGuard en kararlı seçenek olarak *Bölünmüş Tünel* modunu kullanır. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index ca4ce73a155..553aa7ca6df 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. Bulunursa, ClientHellos'u şifreler. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 22108b71673..6639d36ce2e 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index c49d63675f1..5a4bb244094 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ Bu makale, cihazınızı sistem düzeyinde koruyan çok işlevli bir reklam enge ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index bbcc8cd07a5..aa1836e921a 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 94444a40a33..64542cf31d1 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index d46d0285183..1025a2bdf1c 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -11,7 +11,7 @@ Bu makale, yalnızca Safari tarayıcınızı koruyan Safari için AdGuard hakkı Safari için AdGuard ile oluşabilecek çeşitli sorunları analiz etmek ve teşhis etmek için AdGuard destek hizmetinin günlük dosyalarına ihtiyacı olabilir. Bu dosyalar hataların ve diğer yazılım olaylarının kayıtlarını içerir. Aşağıda günlüklerin nasıl toplanacağı ve gerektiğinde desteğe nasıl gönderileceği hakkında kısa talimatlar bulunmaktadır. -### Günlükler nasıl toplanır +### How to collect logs 1. Safari için AdGuard uygulamasını açın. 2. Aşağı kaydırın ve _Günlükleri dışa aktar_ öğesine tıklayın. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index a64e91ecc9e..831acbd4d7b 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Uygulamanın bu şekilde kurulmasının ve elle güncellemelerin tavsiye edilmed ## 5. Test your installation {#installation-test} -Hedef makinede AdGuard'ı başlatın. Open the license screen to check that it is using the specified license. AdGuard'ın lisans anahtarını doğrulamasını sağlamak için "Durumu yenile" öğesine tıklamanız gerekebilir. +Hedef makinede AdGuard'ı başlatın. Ayarladığınız lisansı kullanıp kullanmadığını kontrol etmek için lisans ekranını açın. AdGuard'ın lisans anahtarını doğrulamasını sağlamak için "Durumu yenile" öğesine tıklamanız gerekebilir. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 2c445bcf3b6..19360164bd1 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Arka plan bilgisi: AdGuard Tarayıcı Uzantısının önceki sürümlerinde (v3.5'ten önce), Windows için AdGuard uygulamasıyla birlikte yüklediyseniz, uzantı Asistanı işlevlerini devralıyor, kendini filtrelemeyi bırakıyor ve bunu yapmak için uygulamaya güveniyordu. -Eklenti ve uygulama birlikte çalışıyordu ancak bazen entegrasyon başarısız oluyordu. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +Eklenti ve uygulama birlikte çalışıyordu ancak bazen entegrasyon başarısız oluyordu. Bazı siteler masaüstü programı tarafından korunmuyor ve yalnızca daha az seçeneğe sahip uzantı tarafından korunuyordu. Tarayıcı Asistanını kullanırken, özünde herhangi bir çakışma olamayacağı için tüm bu sorunlar önemli değildir. Tarayıcı Asistanının rolü iyi tanımlanmıştır ve ana uygulamanın işleyişini engelleyemez, bu nedenle endişelenmenize gerek yoktur. @@ -42,4 +42,4 @@ Eski Asistan, bir tarayıcı uzantısı değil, yalnızca bir kullanıcı betiğ Tarayıcı Asistanını varsayılan tarayıcınız için yüklemek isterseniz bunu doğrudan uygulama ayarlarından yapabilirsiniz ancak diğer tarayıcılar için de yükleme olanağınız vardır. -AdGuard Tarayıcı Asistanı tüm popüler tarayıcılarda kullanılabilir: Chrome, Firefox, Edge, Opera ve Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. Bu kadar! +AdGuard Tarayıcı Asistanı tüm popüler tarayıcılarda kullanılabilir: Chrome, Firefox, Edge, Opera ve Yandex. İhtiyacınız olanı (veya birçoğunu, yasak değil, hatta teşvik edilir) yüklemek için [sitemize](https://adguard.com/adguard-assistant/overview.html) gidin, tarayıcı simgesine tıklayın ve *Yükle* düğmesine dokunun. Bu kadar! diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 73673a4b6f5..9b49999ea02 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra, aslında sayfaların çalışma şeklini, sitelerin engelleyicileri atlamak için yukarıda belirtilen yöntemleri kullanmasını çok daha zor hâle getirecek şekilde değiştiren bir mini programdır. **AdGuard Açılır Pencere Engelleyici** -Bu uzantı, web sayfalarını görüntülediğinizde açılır pencerelerin açılmasını engeller. Bazı açılır pencereler yararlı kabul edilir — site yönetimi için ayarlar veya bir bağlantıya tıklandığında gösterilen ek referans bilgileri içerebilirler. Bu nedenle gerekirse Engelleyiciyi kapatabilirsiniz. Bu uzantı, AdGuard istisnalar listesine eklenen sitelerde de çalışmaz. Varsayılan olarak kapalıdır, ancak uygulama ayarlarından açabilirsiniz. You will find more detailed information about this extension in our Knowledge Base. +Bu uzantı, web sayfalarını görüntülediğinizde açılır pencerelerin açılmasını engeller. Bazı açılır pencereler yararlı kabul edilir — site yönetimi için ayarlar veya bir bağlantıya tıklandığında gösterilen ek referans bilgileri içerebilirler. Bu nedenle gerekirse Engelleyiciyi kapatabilirsiniz. Bu uzantı, AdGuard istisnalar listesine eklenen sitelerde de çalışmaz. Varsayılan olarak kapalıdır, ancak uygulama ayarlarından açabilirsiniz. Bu uzantı hakkında daha ayrıntılı bilgiyi Bilgi tabanımızda bulabilirsiniz. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust, kullanıcılarının görüşlerine dayanarak her sitenin itibarı ### Ağ -Sondan bir önceki modül ağ filtrelemeye ayrılmıştır ve burada ağla ilgili ek seçenekler bulacaksınız. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. Bunlar, web alanınızı daha iyi filtrelemek için önemli olağanüstü önlemlerdir. Çoğu site artık HTTPS kullanıyor ve aynı durum reklamcılık için de geçerli. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +Sondan bir önceki modül ağ filtrelemeye ayrılmıştır ve burada ağla ilgili ek seçenekler bulacaksınız. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. Bunlar, web alanınızı daha iyi filtrelemek için önemli olağanüstü önlemlerdir. Çoğu site artık HTTPS kullanıyor ve aynı durum reklamcılık için de geçerli. Youtube.com, facebook.com ve twitter.com gibi birçok siteden HTTPS filtreleme olmadan reklamları kaldırmak imkansızdır. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index c8c4dfcf298..ed8e76ca192 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ _Ayarlar_ en fazla dikkat gerektiren bölümdür. Burası, uygulamayı gereksini ### Genel ayarlar -Burada dili ve temayı (Koyu veya Açık) ayarlayabilir, AdGuard'ın sistem başlangıcında başlatılmasını ve sessiz otomatik güncellemeleri etkinleştirebilir, güncelleme kanalını ve filtre güncelleme denetimi aralığını seçebilirsiniz. Ayrıca Ayarlar, Windows için AdGuard düzgün çalışmıyorsa ve destek ekibi sizden [_Hata ayıklama günlüklerini_ toplamanızı](/adguard-for-windows/solving-problems/adguard-logs.md) istediyse gidilecek yerdir. +Burada dili ve temayı (Koyu veya Açık) ayarlayabilir, AdGuard'ın sistem başlangıcında başlatılmasını ve sessiz otomatik güncellemeleri etkinleştirebilir, güncelleme kanalını ve filtre güncelleme denetimi aralığını seçebilirsiniz. Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). ![Advanced Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ In the DNS protection module of AdGuard for Windows you can select the DNS serve Modül, tarayıcıda açılan web sayfalarının içeriğini kontrol eder ve çocuklar için istenmeyen içeriğe sahip olanları filtreler: yetişkinler için resimler ve metinler, kaba dil, şiddet, uyuşturucu kullanımı, vb. Ebeveyn Denetimi ayarları parola korumalıdır, böylece çocuk kısıtlamaların ötesine geçemez. Bu modül sadece istenmeyen sitelere yönlendirmeleri engellemekle kalmaz, aynı zamanda çocuklar için uygun olmayan bağlantıları da arama sonuçlarından silebilir. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Çocuğunuzun bilgisayara yazılım indirip yüklemesini engellemek için _Yürütülebilen dosyaların indirilmesini engelle_ kutusunu da işaretleyebilirsiniz. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. Çocuğunuzun bilgisayara yazılım indirip yüklemesini engellemek için _Yürütülebilen dosyaların indirilmesini engelle_ kutusunu da işaretleyebilirsiniz. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Ebeveyn Denetimi \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index d34304f3d3c..69dc27c2319 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ Bu makale, cihazınızı sistem düzeyinde koruyan çok işlevli bir reklam enge AdGuard'ı Microsoft Windows altında bir PC veya tablette kullanmak için kurulum paketini indirmeli ve kurulum programını başlatmalısınız. Aşağıdaki işlemleri gerçekleştirin: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Adres çubuğunda [AdGuard sitesine](http://adguard.com) gidin ve [açılan sayfada](https://adguard.com/download.html?auto=1) *İndir* öğesine tıklayın. ![AdGuard'ı indir](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Sonraki adımları yalnızca ilk iki adımı gerçekleştirmek herhangi bir nede ::: -- *AdGuard Reklam Engelleyici* ve *Genişletilmiş* kaldırma türünü seçin, ardından *Kaldır* öğesine tıklayın. Click *Yes, continue* in the window prompt. +- *AdGuard Reklam Engelleyici* ve *Genişletilmiş* kaldırma türünü seçin, ardından *Kaldır* öğesine tıklayın. Clcik *Yes, continue* in the window prompt. ![Genişletilmiş kaldırma *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 9c344d1adfc..3a433c6c36c 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Günlüklerde sağlanan veriler ve/veya dosyalar [AdGuard Gizlilik Politikasına ::: -Ortaya çıkabilecek farklı sorunları analiz etmek ve teşhis etmek için AdGuard destek hizmetinin AdGuard günlük dosyalarına ihtiyacı olabilir. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +Ortaya çıkabilecek farklı sorunları analiz etmek ve teşhis etmek için AdGuard destek hizmetinin AdGuard günlük dosyalarına ihtiyacı olabilir. Bu dosyalar, yazılımda meydana gelen hatalar ve diğer olaylarla ilgili kayıtları içerir. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::not @@ -25,7 +25,7 @@ AdGuard gizliliğinizi korumaya kararlıdır. [Gizlilik Politikamıza](https://a ### Hata ayıklama günlükleri {#debug-logs} -1. AdGuard ayarlarını açın. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. AdGuard ayarlarını açın. *Genel Ayarlar* bölümüne gidin, ekranın sonuna kadar aşağı kaydırın ve *Günlük kayıt düzeyi* öğesini *Hata ayıklama* olarak değiştirin. ![Hata ayıklama günlük kayıt düzeyi *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard gizliliğinizi korumaya kararlıdır. [Gizlilik Politikamıza](https://a Sorunu yeniden oluşturduğunuz tam zamanı not almanızı önemle tavsiye ederiz: bu, destek ekibimizin ilgili günlük girdilerini bulmasına ve sorunu daha hızlı çözmesine yardımcı olur. -1. *Günlükleri dışa aktar* düğmesine kullanarak toplanan günlükleri dışa aktarın. +1. *Günlükleri dışa aktar* düğmesine kullanarak kaydedilen günlükleri dışa aktarın. ![Günlükleri dışa aktar *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Arşivi herhangi bir klasöre kaydedin. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Hata ayıklama* günlük kayıt düzeyi uygulamayı yavaşlatır. +1. **Önemli**: Günlükleri dışa aktardıktan sonra, günlük kayıt düzeyini tekrar *Varsayılan* olarak ayarlayın. *Hata ayıklama* günlük kayıt düzeyi uygulamayı yavaşlatır. 1. Arşivi **support@adguard.com** adresinden AdGuard destek servisine gönderin, sorunu açıklayın ve sorunu yeniden oluşturduğunuz zamanı belirtmeyi unutmayın. @@ -65,7 +65,7 @@ Windows için AdGuard'ın eski bir sürümüne sahipseniz, 64 bit Windows kullan Sorunu yeniden oluşturduğunuz tam zamanı not almanızı önemle tavsiye ederiz: bu, destek ekibimizin ilgili günlük girdilerini bulmasına ve sorunu daha hızlı çözmesine yardımcı olur. -1. *Günlükleri dışa aktar* düğmesine kullanarak toplanan günlükleri dışa aktarın. +1. *Günlükleri dışa aktar* düğmesine kullanarak kaydedilen günlükleri dışa aktarın. ![Günlükleri dışa aktar *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index a0a94d69f74..ffac14cc597 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ Bu makale, Windows için AdGuard kurulumu sırasında karşılaşabileceğiniz e ### Hata 5: Erişim Reddedildi {#error-5} -This error message appears when required permissions haven't been granted. AdGuard kurulum programının, kurma işlemini düzgün bir şekilde tamamlamak için ihtiyaç duyduğu izinlere sahip olmamasının birkaç farklı nedeni olabilir. Aşağıdaki adımları deneyebilirsiniz: +Bu hata, izinlerle ilgili bir sorun olduğunda ortaya çıkar. AdGuard kurulum programının, kurma işlemini düzgün bir şekilde tamamlamak için ihtiyaç duyduğu izinlere sahip olmamasının birkaç farklı nedeni olabilir. Aşağıdaki adımları deneyebilirsiniz: -- Temporarily disable your antivirus. Bazıları, ayarlarının ciddiyetine bağlı olarak kuruluma müdahale edebilir. +- Antivirüslerinizi geçici olarak devre dışı bırakın. Bazıları, ayarlarının ciddiyetine bağlı olarak kuruluma müdahale edebilir. - Farklı bir kurulum klasörü seçin. Mevcut kurulum klasörünün bazı erişim kısıtlamaları olabilir. Ayrıca harici sürücü, sanal sürücü, vb. seçmediğinizden emin olun. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. AdGua ### Hata 112: Disk dolu, Hata 1632: Geçici klasör dolu veya erişilemiyor {#error-112} -Bunlar çok benzer çözümlere sahip iki farklı hatadır. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. Sorunu çözmek için deneyebileceğiniz birkaç şey var: +Bunlar çok benzer çözümlere sahip iki farklı hatadır. Adlarından da anlaşılacağı gibi, AdGuard kurulum programı, kurulumu tamamlamak için yeterli disk alanı bulamadı. Sorunu çözmek için deneyebileceğiniz birkaç şey var: - AdGuard'ı kurmaya çalıştığınız sürücüden bazı programları kaldırın veya gereksiz dosyaları silin. -- Malwarebytes'in ücretsiz bir yazılımı olan [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/) yazılımını indirin, kurun ve çalıştırın. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. Biraz disk alanı temizlemeye yardımcı olur. +- Malwarebytes'in ücretsiz bir yazılımı olan [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/) yazılımını indirin, kurun ve çalıştırın. Diğer şeylerin yanı sıra, sisteminizi yanlış bir şekilde kaldırılan programlar ve benzerlerinden sonra kalan her türlü fazladan "artık" dosyalardan temizler. Biraz disk alanı temizlemeye yardımcı olur. - Bilgisayarınızı yeniden başlatın. Bazen geçici dosyalar önemli miktarda disk alanı kaplayabilir ve PC'nizi yeniden başlatmak bunlardan kurtulmanın en güvenilir yoludur. ### Hata 1601: Windows Installer Hizmetine Erişilemiyor {#error-1601} -You could say this is a particular subcategory of Error 1603. Olası çözümler benzerdir: +Bunun, Hata 1603'ün belirli bir alt türü olduğunu söyleyebilirsiniz. Olası çözümler benzerdir: - Microsoft Installer hizmetini başlatın ve yeniden kaydettirin. Bu biraz uğraş gerektirir. @@ -75,7 +75,7 @@ Bu hata, aynı anda başlatılan birkaç AdGuard kurulum programı olduğunda or - PC'yi yeniden başlatın ve kurulum programını tekrar başlatın. Bilgisayarı yeniden başlattığınızda, kurulum programının tüm kopyaları dahil devam eden tüm işlemler durur. -- Don't make multiple clicks on the installer even if it doesn't start right away. Bazen kurulum programı kullanıcı arayüzünün görüntülenmesi birkaç saniye sürebilir. +- Hemen başlamasa bile kurulum programına birden çok tıklama yapmayın. Bazen kurulum programı kullanıcı arayüzünün görüntülenmesi birkaç saniye sürebilir. ### Error 1638: Bu ürünün başka bir sürümü zaten kurulu {#error-1638} @@ -83,14 +83,14 @@ Daha önce AdGuard kurmuş olmanız çok olasıdır. - AdGuard'ın bilgisayarınızda kurulu olup olmadığını kontrol edin. Bunu *Win* tuşuna basarak ve ***AdGuard*** yazarak yapabilirsiniz. -- Maybe there're some leftover files from a previous AdGuard installation. Özel [kaldırma aracımızı](../../installation#advanced) kullanarak AdGuard'ı kaldırın ve ardından kurulumu tekrarlayın. +- Belki önceki bir AdGuard kurulumundan kalan bazı dosyalar vardır. Özel [kaldırma aracımızı](../../installation#advanced) kullanarak AdGuard'ı kaldırın ve ardından kurulumu tekrarlayın. ### Diğer hatalar {#other} Yukarıda listelenmeyen bir hatayla karşılaştıysanız, bunu kendimiz çözmemiz mümkündür. Ancak bunu yapabilmek için sizden günlük dosyalarına ihtiyacımız var. Lütfen aşağıdaki adımları uygulayın: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [Bu makale](../system-logs) bunun nasıl yapılacağını açıklar. +- **Olay Görüntüleyicisi** günlüklerini bulun ve diske kaydedin. [Bu makale](../system-logs) bunun nasıl yapılacağını açıklar. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Teknik destek temsilcilerimiz size mümkün olan en kısa sürede cevap verir. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index 09c70db7923..316a5c30679 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ Bu makale, cihazınızı sistem düzeyinde koruyan çok işlevli bir reklam enge Windows için AdGuard, kullanıcıların, sorguları çözümlemek için, sistem ayarlarında geçersiz kılınmadığı sürece İSS'niz tarafından sağlanan sistem DNS sunucusu yerine bir DNS sunucu adresi belirtmesine olanak tanır. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Ayrıca, şifrelenmiş ve/veya filtrelenmiş bir DNS sunucusu seçerek, kötü aktörlere ve rahatsız edici reklamlara karşı başka bir koruma katmanı elde edersiniz. -Windows için AdGuard kullanıcılarının çoğu, DNS koruma özelliğini takdir ediyor. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. Bu yazıda size bunun neden olduğunu ve bundan nasıl kaçınılacağını anlatacağız. +Windows için AdGuard kullanıcılarının çoğu, DNS koruma özelliğini takdir ediyor. Ancak bazıları şu sorunla karşılaşıyor: https://ipleak.net/ gibi bir sitede yapılan kontrol, isteklerin seçilen sunucu yerine varsayılan DNS sunucusu tarafından işlendiğini gösteriyor. Bu yazıda size bunun neden olduğunu ve bundan nasıl kaçınılacağını anlatacağız. ## Önyükleme DNS adresi @@ -21,7 +21,7 @@ DNS sunucu adresleri IP veya alan adı olarak yazılabilir. IP adresleri söz ko - *Gelişmiş ayarlar* öğesine gidin - *Özel önyükleme adresleri listesi* bölümüne aşağı kaydırın -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- özel önyükleme adresini IP adresi biçiminde girin ([bilinen DNS sağlayıcıları listesini](https://adguard-dns.io/kb/general/dns-providers/) kullanabilirsiniz) - *kaydet* öğesine tıklayın ## Yedek DNS sunucusu @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - *Gelişmiş ayarlar* öğesine gidin - *Yedek sunucular* bölümüne aşağı kaydırın - *Özel sunucuları kullan* seçeneğini işaretleyin -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- daha sonra *Özel yedek sunucuların listesi* bölümünü bulun ve her satıra bir tane olmak üzere özel yedek sunucular girin veya diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 4fec7f19a38..d3cd20483ac 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ Döküm dosyasını oluşturduktan sonra lütfen dosya konumuna gidin. Döküm d :::not -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +Windows için AdGuard'ın iki çalışan işlemi vardır (`Adguard.exe` ve `AdguardSvc.exe`). Bu nedenle her işlem için ayrı ayrı döküm dosyası oluşturmanız gerekir. ::: ![AdGuard hizmetleri](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -Döküm dosyalarını destek ekibine gönderdiğinizde lütfen AdGuard uygulama günlüklerini de ekleyin, böylece sorunu çözme şansımız artar. [Here](../adguard-logs) you can check the instructions on how to get the log file. +Döküm dosyalarını destek ekibine gönderdiğinizde lütfen AdGuard uygulama günlüklerini de ekleyin, böylece sorunu çözme şansımız artar. [Burada](../adguard-logs) günlük dosyasının nasıl toplanacağına ilişkin talimatları kontrol edebilirsiniz. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 9d6a6b53830..ecb44592a56 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Sistem günlüklerinde sağlanan veriler ve/veya dosyalar [AdGuard Gizlilik Poli AdGuard kurulumu sırasında herhangi bir sorun oluşursa, destek ekibi sizden AdGuard kurulum günlüklerini toplamanızı ve göndermenizi isteyebilir. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. *%tmp%* yazın ve *Tamam* öğesine tıklayın. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index eaca5059d46..d86cb99f319 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Gelişmiş Ayarlar öğesini açtığınızda size aşağıdaki seçenekler sunu Etkinleştirilirse, AdGuard Edge tarayıcısında TCP Fast Open'ı engeller. Ayarları uygulamak için tarayıcıyı yeniden başlatmanız gerekir. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Her şifrelenmiş internet bağlantısının bir de şifrelenmemiş kısmı vardır. Bu, bağlandığınız sunucunun adını içeren ilk pakettir. Encrypted Client Hello teknolojisinin bu sorunu çözmesi ve şifrelenmemiş bilgilerin son kısmını şifrelemesi gerekiyor. To benefit from it, enable the *Use Encrypted Client Hello* option. Alan adı için ECH yapılandırmasını aramak için yerel bir DNS proxy'si kullanır. If it is found, Client Hello packet will be encrypted. +Her şifrelenmiş internet bağlantısının bir de şifrelenmemiş kısmı vardır. Bu, bağlandığınız sunucunun adını içeren ilk pakettir. Encrypted Client Hello teknolojisinin bu sorunu çözmesi ve şifrelenmemiş bilgilerin son kısmını şifrelemesi gerekiyor. To benefit from it, enable the *Use Encrypted ClientHello* option. Alan adı için ECH yapılandırmasını aramak için yerel bir DNS proxy'si kullanır. Eğer bulunursa, ClientHello paketi şifrelenecektir. ### Sitelerin sertifika şeffaflığını kontrol et @@ -73,7 +73,7 @@ Aksi takdirde, AdGuard tüm trafiği yönlendirme olmadan anında filtreler. Bu ### Sistem başlangıcında ana pencereyi aç -Sistem yüklendikten sonra ana AdGuard penceresinin açılmasını sağlamak için bu seçeneği etkinleştirin. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Sistem yüklendikten sonra ana AdGuard penceresinin açılmasını sağlamak için bu seçeneği etkinleştirin. Gerçek filtreleme hizmetinin başlatılıp başlatılmamasını etkilemediğini unutmayın, bu ayar *Ayarlar → Genel Ayarlar* öğesinde bulunur. ### Sistem başlangıcında filtrelemeyi etkinleştir @@ -95,7 +95,7 @@ AdGuard'ın belirli alt ağları filtrelemesini istemiyorsanız, bu özelliği e ### HAR yazımını etkinleştir -Bu seçenek **yalnızca hata ayıklama amacıyla** etkinleştirilmelidir. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. Bu dosya Fiddler uygulamasıyla analiz edilebilir. İnternette gezinmeyi önemli ölçüde yavaşlatabileceğini unutmayın. +Bu seçenek **yalnızca hata ayıklama amacıyla** etkinleştirilmelidir. Onay işaretini işaretlerseniz AdGuard, filtrelenen tüm HTTP istekleri hakkında bilgileri içeren HAR 1.2 biçiminde bir dosya oluşturur. Bu dosya Fiddler uygulamasıyla analiz edilebilir. İnternette gezinmeyi önemli ölçüde yavaşlatabileceğini unutmayın. ### Düz HTTP isteğine fazladan boşluk ekle @@ -115,7 +115,7 @@ Bu seçenek yalnızca *DPİ'den koru* Gizlilik Modu seçeneği etkinleştirildi Derin paket incelemesinden kaçınarak TCP paket parçalanmasının boyutunu belirtir. Bu seçenek yalnızca güvenli (HTTPS) trafiğini etkiler. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Geçerli değerler: 1–1500. Geçersiz boyut belirtilirse, sistem tarafından seçilen değer kullanılacaktır. Bu seçenek yalnızca *DPİ'den koru* Gizlilik Modu seçeneği etkinleştirildiğinde uygulanır. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index a992428aa2c..50f4e3f71c9 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Sistem günlüklerinde sağlanan veriler ve/veya dosyalar [AdGuard Gizlilik Poli ::: -Ortaya çıkabilecek farklı sorunları analiz etmek ve teşhis etmek için AdGuard destek hizmetinin Windows sistem günlük dosyalarına ihtiyacı olabilir. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Aşağıda günlük dosyalarını nasıl alacağınızı ve gerekirse destek servisimize nasıl göndereceğinizi açıklayan kısa talimat bulunmaktadır. +Ortaya çıkabilecek farklı sorunları analiz etmek ve teşhis etmek için AdGuard destek hizmetinin Windows sistem günlük dosyalarına ihtiyacı olabilir. Windows olay günlükleri, AdGuard da dahil olmak üzere yüklü yazılımda meydana gelen tüm hatalara ilişkin kayıtları içerir. Aşağıda günlük dosyalarını nasıl alacağınızı ve gerekirse destek servisimize nasıl göndereceğinizi açıklayan kısa talimat bulunmaktadır. 1. *Win + R* tuşlarına basın diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index d12b3df2981..4998fde77dd 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ Bu makale, cihazınızı sistem düzeyinde koruyan çok işlevli bir reklam enge ::: -Ağ trafiğini filtrelemek için AdGuard bir ağ sürücüsü kullanır. İki seçenek vardır: TDI sürücüsü ve WFP sürücüsü. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. Bu sorunlar ve sonraki hatalar her durumda çok farklı olabilir. +Ağ trafiğini filtrelemek için AdGuard bir ağ sürücüsü kullanır. İki seçenek vardır: TDI sürücüsü ve WFP sürücüsü. WFP sürücüsü genellikle tercih edilir ve tüm yeni Windows işletim sistemi sürümleri için (Windows 8 ve daha yeni) varsayılan olarak etkinleştirilmiş olsa da, özellikle bazı antivirüslerde uyumluluk sorunlarına neden olabilir. Bu sorunlar ve sonraki hatalar her durumda çok farklı olabilir. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. Bunu yapmak için: 1. *Ayarlar → Ağ* öğesine gidin. -2. Disable the WFP driver as it’s done in this picture: +2. Bu resimde yapıldığı gibi WFP sürücüsünü devre dışı bırakın: ![WFP sürücüsü *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/account/features.md index 1bb4b38f733..fa8b2d7fad7 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 36e76fc66b2..1959ec4e1f4 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -40,14 +40,13 @@ Bu sayfada bu filtre hakkında daha fazla bilgi edinin. [Kuralları görüntüle - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Bilinen tüm mobil reklam ağlarını içerir. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) -- **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Hızlı Çözümler filtresi** — MV3 uzantısını güncellemeden popüler sitelerdeki kritik içerik filtreleme sorunlarını hızlı bir şekilde çözmek için kullanılır. [Kuralları görüntüle](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) +- **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index ccb58bb8ed4..1c7d4484da8 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -253,7 +253,7 @@ The features described in this section are intended for experienced users. They You can change the behavior of a "basic rule" by using additional modifiers. Modifiers should be located in the end of the rule after a `$` sign and be separated by commas. -Örnek: +Example: ```adblock ||domain.com^$popup,third-party @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Temel olarak, s -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [Chrome MV3 için AdGuard][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:------------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::not - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — uygulanması planlanan ancak henüz hiçbir üründe mevcut olmayan özellik +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -318,7 +316,7 @@ Değiştirici değerindeki uygulamaların joker karakteri olamaz, örneğin `$ap :::info Uyumluluk - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$app` modifier. -- Windows'ta işlem adı, [CoreLibs][] v1.12 veya sonraki sürümlere sahip Windows için AdGuard ile başlayarak büyük/küçük harfe duyarlı değildir. +- On Windows the process name is case-insensitive starting with AdGuard for Windows with [CoreLibs][] v1.12 or later. ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::bilgi -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::dikkat Kısıtlamalar Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::dikkat Kısıtlamalar -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Uyumluluk -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Sayfanın kendisinin engellenmesi bazı kontroller yapabilir ve eğer gerçekten bir açılır pencere ise pencereyi kapatabilir. Aksi takdirde, sayfa yüklenmelidir. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Sayfanın kendisinin engellenmesi bazı kontroller yapabilir ve eğer gerçekten bir açılır pencere ise pencereyi kapatabilir. Aksi takdirde, sayfa yüklenmelidir. `$third-party` ve `$important` gibi diğer istek türü değiştiricileriyle birleştirilebilir. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Örnekler** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::not - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Uyumluluk - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Örnekler** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::not - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Uyumluluk - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::not @@ -679,7 +630,7 @@ Tam değiştirici adını kullanmak yerine daha kısa bir ad (takma ad) kullanab :::info Uyumluluk -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Değiştirici \ Ürünler | [CoreLibs uygulamaları][cl-apps] | [AdGuard for Chromium][ext-chr] | [Chrome MV3 için AdGuard][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:----------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:------------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Değiştirici \ Ürünler | [CoreLibs uygulamaları][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | +| ------------------------------------------------------------- |:--------------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:------------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::not @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Uyumluluk AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Uyumluluk - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ Tam değiştirici adını kullanmak yerine daha kısa bir ad (takma ad) kullanab ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Uyumluluk +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Uyumluluk -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [Chrome MV3 için AdGuard][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:------------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:------------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::not @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Uyumluluk - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Örnekler** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Uyumluluk - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Söz dizimi** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. Değiştirici herhangi bir sayıda belirli seçenek içerebilir (aşağıya bakın) veya hiçbirini içerebilir. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. Değiştirici herhangi bir sayıda belirli seçenek içerebilir (aşağıya bakın) veya hiçbirini içerebilir. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Örnekler** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::not -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Uyumluluk -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Gizlilik Modu Windows için AdGuard, Mac için AdGuard, Android için AdGuard ve AdGuard Tarayıcı Uzantısında mevcuttur. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Uyumluluk In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Uyumluluk - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Uyumluluk In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Uyumluluk - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [Chrome MV3 için AdGuard][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:---------------------------:|:------------------------------:|:------------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:---------------------------:|:------------------------------:|:------------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::not - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — uygulanması planlanan ancak henüz hiçbir üründe mevcut olmayan özellik +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — desteklenmiyor - 👎 — kullanımdan kaldırıldı; hâlâ destekleniyor ancak gelecekte kaldırılacaktır @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::dikkat Kısıtlamalar - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Uyumluluk Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. Sadece kısmen iptal edilmişse bunu hesaplayamayız. [Örnekler](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Uyumluluk Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. Örneğin, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Örnekler** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::dikkat Kısıtlamalar -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::dikkat Kısıtlamalar - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::dikkat Kısıtlamalar - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Diğer yanıtlar bu kurallar tarafından değiştirilmeyecektir. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Uyumluluk -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::dikkat Kısıtlamalar -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Uyumluluk -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::dikkat Kısıtlamalar -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Uyumluluk -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox, `Permissions-Policy` başlığını yok sayar. Daha fazla bilgi için [ :::info Uyumluluk -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Uyumluluk -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Uyumluluk -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Uyumluluk -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Uyumluluk -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Uyumluluk + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Örnek: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::dikkat Kısıtlamalar - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Uyumluluk -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Uyumluluk -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Özellikler** -- `$urltransform` kuralları normalde yalnızca URL'nin yol ve sorgu bölümleri için geçerlidir, bir istisna için aşağıya bakın. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Uyumluluk - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -Yukarıda belirtildiği gibi, normalde `$urltransform` kurallarının yalnızca URL'nin yol ve sorgu bölümlerini değiştirmesine izin verilir. Ancak, kuralın `regexp` öğesinin `^http` dizesiyle başlıyorsa, URL'nin tamamı aranır ve kural tarafından değiştirilebilir. URL dönüşümü bir HTTP yönlendirmesi yoluyla gerçekleştirilemiyorsa (örneğin, isteğin yöntemi `POST` ise) böyle bir kural uygulanmayacaktır. - **Örnekler** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Örnekler** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [Chrome MV3 için AdGuard][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:----------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:------------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS kuralları](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:---------------------------:|:------------------------------:|:------------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS kuralları](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::not @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::not -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::not @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Uyumluluk -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript kuralları {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Örnekler** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Engelleme kuralları söz dizimi** +**Söz dizimi** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Örnekler** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**İstisna kuralları söz dizimi** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Örnekler** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [Chrome MV3 için AdGuard][ext-mv3] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:---------------------------:|:------------------------------:|:------------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [iOS için AdGuard][ios-app] | [Safari için AdGuard][ext-saf] | [AdGuard İçerik Engelleyici][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:---------------------------:|:------------------------------:|:------------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::not - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Uyumluluk -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Uyumluluk -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::dikkat Kısıtlamalar In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Uyumluluk -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Filtre yöneticileri için bilgiler If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Dosya dahil etme {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Söz dizimi** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4424,7 +4151,7 @@ where: - `adguard_ext_edge` — AdGuard Browser Extension for Edge Legacy - `adguard_ext_opera` — AdGuard Browser Extension for Opera - `adguard_ext_android_cb` — AdGuard Content Blocker for mobile Samsung and Yandex browsers - - `ext_ublock` — special case; this one is declared when a uBlock version of a filter is compiled by the [FiltersRegistry][] + - `ext_ublock` — özel durumdur; bu, bir filtrenin uBlock sürümü [FiltersRegistry][] tarafından derlendiğinde bildirilir - `cap_html_filtering` — HTML filtreleme kurallarını destekleyen ürünler: Windows için AdGuard, Mac için AdGuard ve Android için AdGuard - `!#else` — koşullar yanlış olduğunda bloğun başlangıcı - `rules_list`, `true_conditions_rules_list`, `false_conditions_rules_list` — kural listeleri @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Ürün kısayolları {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `Firefox için AdGuard` — Firefox için AdGuard Tarayıcı Uzantısı +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Uyumluluk kısayolları {#what-compatibility} @@ -4758,38 +4483,26 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — uygulanması planlanan ancak henüz hiçbir üründe mevcut olmayan özellik +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — kullanımdan kaldırıldı; hâlâ destekleniyor ancak gelecekte kaldırılacaktır - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [cl-apps]: #what-product "Windows, Mac, Android için AdGuard" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "Chrome için AdGuard Tarayıcı Uzantısı MV3" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ext-ff]: #what-product "Firefox için AdGuard Tarayıcı Uzantısı" [ios-app]: #what-product "iOS için AdGuard ve iOS için AdGuard Pro" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "Safari için AdGuard" -[ext-saf]: #what-product "AdGuard for Safari" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 47f4240c11e..f7b2720e957 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Temel filtresi - AdGuard Mobil Reklam filtresi - Dil ilkesine göre ayrılmış bölgesel filtreler — Çince, Felemenkçe, Fransızca, Almanca, Japonca, Rusça, İspanyolca/Portekizce, Türkçe ve Ukraynaca -- AdGuard Hızlı Çözümler filtresi ### Bu filtrelerin amacı - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. Ayrıca, dilden bağımsız olarak tüm siteler için geçerli olan genel filtreleme kuralları da içerir - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. Dile dayalı bir sınıflandırma yoktur - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Hızlı Çözümler filtresi**, MV3 uzantısını güncellemeden popüler sitelerdeki kritik içerik filtreleme sorunlarını hızlı bir şekilde çözmek için kullanılır. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index 74624b4112c..baa5add454f 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: Reklam engelleme nasıl çalışır sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::not diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/browsing-security.md index c32ec5a56e8..37eb5cfec4b 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Yardım etmek ister misiniz? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 27f06d36f27..b31a54e1c69 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Çoğu site artık HTTPS kullanıyor ve aynı durum reklamcılık için de geçerli. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Çoğu site artık HTTPS kullanıyor ve aynı durum reklamcılık için de geçerli. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/license/what-is.md index 8f65e261723..fca27fe638f 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Ömür boyu** — bu lisanslar kalıcıdır +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 24f3b0915c5..191e4096793 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/tr/docusaurus-plugin-content-docs/current/general/userscripts.md index 9ed44b2bb16..868fc78bbd0 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Desteklenen uygulamalar @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/tr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 699f988254b..9ad9b73b7ec 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: HAR dosyası nasıl toplanır sidebar_position: 1 --- diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/guides/minidump.md b/i18n/tr/docusaurus-plugin-content-docs/current/guides/minidump.md index 0cbed163714..790dd94e9c4 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/guides/minidump.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/guides/minidump.md @@ -10,7 +10,7 @@ Almost all Windows users are familiar with the [Blue Screen of Death (BSoD)](htt A minidump file is a file that contains the information about the nature of the system crash. It is created just before the blue screen appears and it has the minimum amount of useful information that can be used to solve the problem. The minidump file usually has a *.dmp* extension. :::note -Windows 10'da mavi ekran bir durdurma kodu ve bir QR kodu gösterir. The user can use this information and search the Web for the specific problem. +On Windows 10, the blue screen shows a stop code and a QR code. The user can use this information and search the Web for the specific problem. ::: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/tr/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0f780663a02..e861f5467fa 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version @@ -26,9 +26,9 @@ Try to provide as many details as possible — that'll make it easier for us to - Whether it recurred and with what frequency - Whether you have a VPN or an antivirus software -### Günlükler nasıl toplanır +### How to collect logs -Her platform için özel makalelerde günlük toplama hakkında bilgi edinin. +Read about collecting logs in dedicated articles for each platform. ## How to vote for bug reports or feature requests diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/tr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index daf2a4ea648..f2b4c0cc839 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows tüm ekranı yakalar ve panoya kopyalar. -To take a screenshot of an active window, use the following shortcut keys: +Etkin bir pencerenin ekran görüntüsünü almak için aşağıdaki kısayolu kullanın: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +Belirli bir alanın ekran görüntüsünü almak için aşağıdaki kısayolu kullanın: - ******Win + Shift + S*** tuşlarına basın*** -Bir ekran görüntüsü aldıktan sonra panoya kaydedilecektir. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatif olarak, ekran görüntüsünü bir dosyaya kaydetmeniz gerekiyorsa, standart **Paint** programını (veya görüntülerle çalışabilen başka bir uygulamayı) açmalısınız. Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +Bir ekran görüntüsü aldıktan sonra panoya kaydedilecektir. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatif olarak, ekran görüntüsünü bir dosyaya kaydetmeniz gerekiyorsa, standart **Paint** programını (veya görüntülerle çalışabilen başka bir uygulamayı) açmalısınız. Ekran görüntünüzü aynı kısayolu kullanarak veya Yapıştır düğmesine (genellikle ekranın sol üst köşesinde) tıklayarak buraya yapıştırın ve ardından kaydedin. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. Bu tuşlara basar basmaz, ekran görüntüsü otomatik olarak *Resimler* → *Ekran Görüntüleri Klasörünüze* bir dosya olarak kaydedilecektir. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. Bu tuşlara basar basmaz, ekran görüntüsü otomatik olarak *Resimler* → *Ekran Görüntüleri Klasörünüze* bir dosya olarak kaydedilecektir. Bilgisayarınızın standart programları arasında Başlat menüsünden bulabileceğiniz *Ekran Alıntısı Aracı* adlı ekran görüntüsü almak için özel bir program da bulunmaktadır. Ekran Alıntısı Aracı, masaüstünüzün herhangi bir alanını veya tüm ekranı yakalamanıza olanak tanır. Bu programı kullanarak ekran görüntüsü aldıktan sonra resmi düzenleyebilir ve bilgisayarınızdaki herhangi bir klasöre kaydedebilirsiniz. @@ -70,26 +70,26 @@ Ayrıca, bilgisayarınızda ekran görüntüsü almak için **PicPick**, **Nimbu ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +Mac'te ekran görüntüsü almak için aşağıdaki kısayolu kullanın: - ******⌘ Cmd + Shift + 3*** tuşlarını basılı tutun*** Mac'iniz tüm ekranı yakalar ve masaüstünde bir dosya olarak kaydeder. -To take a screenshot of an active window, use the following shortcut keys: +Etkin bir pencerenin ekran görüntüsünü almak için aşağıdaki kısayolu kullanın: - ***⌘ Cmd + Shift + 4 + Boşluk çubuğu* tuşlarını basılı tutun. The pointer will change to a camera icon. Click the window to capture it. Ekran görüntüsü almayı iptal etmek için Esc tuşuna basın** -To take a screenshot of a specific area, use the following shortcut keys: +Belirli bir alanın ekran görüntüsünü almak için aşağıdaki kısayolu kullanın: - *** ***⌘ Cmd + Shift + 5****** tuşlarına basın. Gerekli alanı seçmek için artı işaretine sürükleyin. Ekran görüntüsü almak için farenizi veya dokunmatik farenizi bırakın, iptal etmek için Esc düğmesine basın. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +*Touch Bar* (MacBook Pro) ekran görüntüsü almak için aşağıdaki kısayolu kullanın: - ******⌘ Cmd + Shift + 6*** tuşlarına basın*** Mac'iniz *Touch Bar'ın* tamamını yakalar ve masaüstünde bir dosya olarak kaydeder. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +Ekran görüntüsünü kaydetmek yerine panoya kopyalamak için yukarıdaki kısayollardan herhangi biriyle birlikte *Ctrl* tuşuna basılı tutun. Ardından ekran görüntüsünü (panodan) *Cmd + V* kısayolunu kullanarak düzenlemekte olduğunuz bir belgeye veya görüntüye yapıştırabilirsiniz. Ayrıca **Önizleme** öğesini kullanarak ve **Ekran görüntüsü al** öğesini (seçilen alan, pencere veya tüm ekran) seçerek de ekran görüntüsü alabilirsiniz. **Önizleme** ile ekran görüntülerinizi JPG, TIFF, PDF ve diğer dosya formatlarında kaydedebilirsiniz. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/intro.md b/i18n/tr/docusaurus-plugin-content-docs/current/intro.md index ca050310783..cceb856a7bb 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ Ancak tüm popüler tarayıcılar için ücretsiz tarayıcı uzantıları da gel ## Sadece reklam engelleme değil -AdGuard Reklam Engelleyici, reklamları engellemekten daha fazlasını yapar. Sizi çevrimiçi izlemeden korur ve gizliliğinizi birçok yönden geliştirir. Belirli ürüne bağlı olarak AdGuard, daha kapsamlı koruma için DNS filtreleme, çocuklarınızı uygunsuz içerikten korumak için Ebeveyn Denetimi, internet trafiğiniz üzerinde daha iyi kontrol sahibi olmak için Filtreleme günlüğü ve daha fazlası gibi avantajlar da sunabilir. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Reklam Engelleyici, reklamları engellemekten daha fazlasını yapar. Sizi çevrimiçi izlemeden korur ve gizliliğinizi birçok yönden geliştirir. Belirli ürüne bağlı olarak AdGuard, daha kapsamlı koruma için DNS filtreleme, çocuklarınızı uygunsuz içerikten korumak için Ebeveyn Denetimi, internet trafiğiniz üzerinde daha iyi kontrol sahibi olmak için Filtreleme günlüğü ve daha fazlası gibi avantajlar da sunabilir. Bu Bilgi tabanı bunların hepsi hakkında ayrıntılı bilgi içerir — ilginizi çeken herhangi bir makaleye atlamaktan çekinmeyin. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index 17d8cca2626..e0d0e15ed79 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +Filtreleme kural söz dizimimize henüz aşina değilseniz veya belki de tazelemeye ihtiyacınız varsa, söz dizimi hakkındaki temel bilgileri [Bilgi tabanımızda](/general/ad-filtering/create-own-filters) bulabilirsiniz. ### Ödüller {#rewards} diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index b35f98fe7c0..ecbac9da1b7 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index 770305136c3..aaa98ddc7bf 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index d2f92ec5097..db13d188052 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index e9bc9362d3e..b2dd9a8ec12 100644 --- a/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/tr/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Makaleleri çevirme {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/uk/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/uk/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/uk/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/uk/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/intro.md b/i18n/uk/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/uk/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/vi/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/vi/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/vi/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/vi/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/intro.md b/i18n/vi/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/vi/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md index 88955590746..816a7059ef9 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/compatibility.md @@ -1,5 +1,5 @@ --- -title: 与独立应用程序兼容 +title: Compatibility with the standalone app sidebar_position: 4 --- @@ -9,16 +9,16 @@ sidebar_position: 4 ::: -虽然 AdGuard 浏览器扩展可以拦截浏览器中的广告，但 [AdGuard 独立应用](/adguard-browser-extension/comparison-standalone)能过滤设备上的所有流量，包括浏览器和应用程序的流量。 +While AdGuard Browser Extension can block ads in browsers, [AdGuard standalone programs](/adguard-browser-extension/comparison-standalone) filter all the traffic on your device, including from browsers and apps. -在电脑上同时安装扩展程序和独立应用程序，可能会引起一些兼容性问题。 问题是，在某些情况下，应用程序和扩展会相互干扰。 因此，有些网站将不再受桌面程序的保护，而只能受扩展程序的保护，但是扩展程序的拦截效果没有桌面程序强。 结果，某些网站的过滤功能可能无法正常工作。 这就是我们不建议将扩展与应用程序一起使用的原因。 +If you decide to install both the extension and the standalone program on your PC, you may encounter some compatibility issues. The problem is that in some cases the application and the extension may interfere with each other. Some websites will no longer be protected by the desktop program and will only be protected by the extension, which has fewer options. Also, filtering may work incorrectly for some websites. Therefore, we don't recommend using the extension together with the application. -如果电脑上已安装桌面版 AdGuard，最好使用 AdGuard 浏览器助手而不是浏览器扩展。 +If you have the desktop version of AdGuard installed on your PC, it is better to use AdGuard Browser Assistant instead of the extension. ## AdGuard 浏览器助手 -![AdGuard 浏览器助手 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) +![AdGuard Browser Assistant \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/browser_extension/ad_blocker_browser_extension_assistant.png) -AdGuard 浏览器助手是一款浏览器扩展，其工作方式和样式与 AdGuard 浏览器扩展一样，但它更轻量，并且不会干扰桌面应用程序。 用户可以[阅读有关适用于 Windows 的浏览器助手的更多信息](/adguard-for-windows/browser-assistant)或[Mac](/adguard-for-mac/features/browser-assistant)，或[在我们的网站下载助手](https://adguard.com/adguard-assistant/overview.html)。 +AdGuard Browser Assistant is a browser extension that works and feels just like AdGuard Browser Extension, but it's much lighter and doesn't interfere with the desktop apps. You can [read more about Browser Assistant for Windows](/adguard-for-windows/browser-assistant) or [Mac](/adguard-for-mac/features/browser-assistant), or [download it from our website](https://adguard.com/adguard-assistant/overview.html). -AdGuard 浏览器助手可以在所有主流浏览器中下载。 +AdGuard Browser Assistant is available in all major browsers. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index d96d87913bb..ad924a6d5ad 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -11,15 +11,15 @@ sidebar_position: 1 显然拦截广告是任何广告拦截器的主要功能，AdGuard 扩展程序也不例外。 广告拦截基于过滤器，即一种特殊语言编写的规则集。 这些规则指定哪些元素应该被屏蔽。 AdGuard 解释规则，并根据规则修改网络请求。 这样，用户就不会在网页上看到广告。 -![过滤器 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters.png) +![Filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters.png) 所有过滤器都根据其作用分组。 例如，有广告拦截过滤器、隐私保护过滤器、社交媒体相关过滤器等类别。 用户可以启用单个过滤器或一键启用整组过滤器。 -![广告拦截的过滤器 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters1.png) +![Ad blocking filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_filters1.png) ## 自定义过滤器 -虽然其他过滤器组的功能易于理解，但一个名为「自定义」的组可能会引起额外的问题。 +虽然其他过滤器组的功能或多或少可以预测，但一个名为「自定义」的组可能会引起额外的问题。 ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) @@ -27,13 +27,13 @@ sidebar_position: 1 要添加过滤器，只需要单击「添加自定义过滤器」，输入要添加的过滤器的 URL 或文件路径，然后单击「下一步」。 -![添加自定义过滤器 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters1.png) +![Add a custom filter \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters1.png) ## 用户规则 {#user-rules} 「用户规则」是另一个可以帮助用户自定义广告拦截的工具。 -![用户规则 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_user_rules.png) +![User rules \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_user_rules.png) 有几种方法来添加新规则。 第一个是，直接键入规则，但用户需要使用一定的[规则语法](/general/ad-filtering/create-own-filters)。 @@ -47,10 +47,10 @@ sidebar_position: 1 「白名单」用于排除某些网站的过滤。 拦截规则不适用于列表中的网站。 -![白名单 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist.png) +![Allowlist \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist.png) 「白名单」也可以反转使用：可以在除此列表的网站之外的任何地方放行广告。 为此，请激活「颠倒白名单」选项。 -![颠倒白名单 \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist1.png) +![Invert allowlist \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_allowlist1.png) 用户还可以导入和导出现有的白名单。 例如，如果您想在各个浏览器中应用相同的白名单，那么这个功能就很有用。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index a48f7e4004d..836d643dd36 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -19,7 +19,7 @@ sidebar_position: 3 此外，还可以启用[「钓鱼和恶意保护」](/general/browsing-security)。 -您可以单击「导出设置」来保存设置配置。 设置将保存为 .json 文件。 要导入以前保存的设置配置，请使用「导入设置」功能。 用户还可以使用该功能在不同的设置配置文件之间快速切换，甚至可以在不同的浏览器之间传输设置配置。 +您可以单击「导出设置」来保存设置配置。 设置将保存为 .json 文件。 要上传以前保存的设置配置，请使用「导入设置」功能。 用户还可以使用该功能在不同的设置配置文件之间快速切换，甚至可以在不同的浏览器之间传输设置配置。 ## 附加设置 {#misc} diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3e42439e29a..00000000000 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## 限制 - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index b0396de6cef..19811220f3f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: 受浏览器保护的网页 -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md index 9cd3a2c504f..2a769c1665d 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/logs.md @@ -1,63 +1,63 @@ --- -title: 如何从后台页面导出日志 +title: How to export logs from the background page sidebar_position: 1 --- -## 从扩展程序的后台页面导出日志 +## Exporting logs from the background page in the extension ### Chrome 浏览器 -1. 打开 AdGuard 浏览器扩展，如果可以的话，请您尽可能重复导致错误的操作。 请记下错误发生的确切时间。 +1. Open AdGuard Browser Extension and, if possible, repeat the actions that led to the error. Note the exact time when the error occurred. -2. 转到 `chrome://extensions`。 +2. Navigate to `chrome://extensions`. -3. 启用「开发者模式」。 +3. Enable _Developer mode_. - ![开发者模式 \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/developer_mode1.png) + ![Developer mode \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/developer_mode1.png) 4. Click `background.html`. - ![背景 \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/background1.png) + ![Background \*border](https://cdn.adguardvpn.com/content/kb/ad_blocker/browser_extension/background1.png) -5. 打开「Console」（控制台）选项卡。 +5. Open the tab _Console_. - ![控制台选项卡 \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/console.png) + ![The Console tab \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/console.png) -6. 打开上下文菜单，选择「另存为…」。 +6. Open the context menu and select _Save as…_. - ![另存为 \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/save.png) + ![Save as \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/save.png) ### Firefox 浏览器 -1. 打开 AdGuard 浏览器扩展，如果可以的话，请您尽可能重复导致错误的操作。 请记下错误发生的确切时间。 +1. Open AdGuard Browser Extension and, if possible, repeat the actions that led to the error. Note the exact time when the error occurred. -2. 转到 `about:addons`。 +2. Navigate to `about:addons`. -3. 单击「调试附加组件」。 +3. Click _Debug Add-ons_. - ![调试组件 \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/add-ons.png) + ![Debug Add-ons \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/add-ons.png) -4. 点击「检查」。 +4. Click _Inspect_. - ![检查 \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/inspect.png) + ![Inspect \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/inspect.png) -5. 打开「Console」（控制台）选项卡。 +5. Go to the tab _Console_. - ![控制台 \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/ff_console.png) + ![Console \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/ff_console.png) -6. 单击「Save all Messages to File」（将所有信息保存到文件）。 +6. Click _Save all Messages to File_. - ![保存 \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/save-to-file.png) + ![Save \*border](https://cdn.adguardvpn.com/content/kb/vpn/browser_extension/save-to-file.png) -## 发送日志记录 +## Sending logs :::note -AdGuard 致力于保护用户的个人隐私。 我们严格遵守[隐私政策](https://adguard.com/privacy/browser-extension.html)，不收集用户的私人信息。 请注意：在将您的日志记录发送给客户支持团队之前，请检查文件，因为它会包含您不想分享的附加信息。 如果其中包含此类个人信息，我们建议您先将其删除。 +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/browser-extension.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -现在，您已经收集了日志，请按照以下步骤将日志提交给我们的开发团队： +Now that you have collected the logs, please follow these steps to submit them to our development team: -1. 在 [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose) 上报告错误。 -2. 将包含日志和复现时间的存档发送至 devteam@adguard.com 并附上指向您的 GitHub Issue 的链接。 您也可以将存档上传到 Google Drive，然后添加链接，而不是附加文件。 +1. Report the bug on [GitHub](https://github.com/AdguardTeam/AdguardBrowserExtension/issues/new/choose). +2. Send your archive with logs and playback time to `devteam@adguard.com` and add a link to your GitHub issue. You can also upload the archive to Google Drive and add the link to it instead of attaching the file. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 00c0f1f9d9b..bb0d8052469 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ sidebar_position: 2 ### “无问题”与“有问题”的应用 -大多数应用程序在过滤后都能正常运行。 对于此类应用，它们的流量经过 AdGuard 路由，默认进行过滤。 +过滤开启时，大部分应用都可正常工作。 对于此类应用，它们的流量经过 AdGuard 路由，默认进行过滤。 某些应用程序（如下载管理器、收音机、UID 1000 和 1001 的系统应用程序（如 Google Play 服务））存在“问题”，通过 AdGuard 路由时可能会发生异常。 这就是在尝试路由或过滤所有应用程序时，用户可能会看到以下警告的原因。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index f6a1095545b..ff69e071df4 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -43,10 +43,10 @@ sidebar_position: 1 要从「自定义规则」移除规则或应用，请将其滑动到左侧。 -### 通知 +### Notifications -启用该功能后，当应用程序试图违反适用的防火墙规则时（例如，试图访问被阻止的移动数据），用户将收到通知。 用户可以设置所有应用程序或单独某个应用程序的通知开关状态。 +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. -点击通知即可进入应用程序的防火墙设置，或者点击通知中的相应按钮暂时禁用该应用程序的所有防火墙规则。 用户还可以通过点击应用程序通知中的「静音」按钮来静音该应用程序的所有防火墙通知。 +Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. -请注意，如果显示多个应用程序的通知，它们将被折叠为单个通知。 +Note that if notifications for multiple apps would be displayed, they will be bundled into a single notification instead. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index d0b9d366217..e0243f34350 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ sidebar_position: 7 由于 Android 操作系统的安全措施，AdGuard 的一些功能只能在有 Root 权限的设备上使用。 以下是具体列表： -- 在大多数情况下，应用程序中的「**HTTPS 过滤**」需要将 [CA 证书安装到系统存储](/adguard-for-android/features/settings#security-certificates)上，因为大多数应用程序不信任用户存储中的证书。 +- 大多数应用程序中的「**HTTPS 过滤**」需要将 [CA 证书安装到系统存储](/adguard-for-android/features/settings#security-certificates)上，因为大多数应用程序不信任用户存储中的证书。 只有在 Root 设备上才能将证书安装到系统存储区。 - [「**自动代理**」路由模式](/adguard-for-android/features/settings#routing-mode)需要 Root 权限，因为 Android 对系统范围的流量过滤有限制。 - [「**手动代理**」路由模式](/adguard-for-android/features/settings#routing-mode)在 Android 10 及以上版本需要 Root 权限，因为不再可能确定与 AdGuard 过滤的连接相关联的应用程序的名称。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 7b4b3850aaf..6bea013bd98 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -132,8 +132,8 @@ HTTPS 过滤允许 AdGuard 过滤请求和响应的内容，但我们从不收 - 购买 AdGuard 许可证以激活[完整版功能](/adguard-for-android/features/free-vs-full)。 - 登录 AdGuard 账号或输入许可证密钥以激活许可证。 -- 如果尚未使用许可证，请激活 7 天试用期。 -- 通过三点菜单（⋮）刷新许可证状态。 +- 如果尚未使用许可证，请激活 7 天试用期 +- 通过三点菜单（:）刷新许可证状态 - 打开 AdGuard 账号管理许可证。 - 重置许可证。在您已达到此许可证可绑定的设备数量限制，并希望申请另一个许可证的情况下。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c5992ebce75..89cd70b075d 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -27,25 +27,25 @@ Asus 设备后台工作的潜在问题主要来自「Power Master」这一优化 小米（特别是 MIUI 系统）是在后台运行方面限制最多的系统之一。 众所周知，小米的系统会限制后台进程，具有非标准权限，还缺乏适当的文档。 有时应用程序就是无法在小米手机上正常运行，而且我们对此还无能为力。 如果您在各种小米设备上遇到有关 AdGuard 后台工作的问题，您可以尝试执行以下操作。 -### MIUI 13+ 和 HyperOS +### MIUI 13+ and HyperOS -取决于 MIUI 和 HyperOS 版本，有两种方法可以更改手机电池优化设置并更有效地拦截广告。 +Depending on the MIUI and HyperOS versions, there are two ways to change the battery optimization settings on your phone and block ads more efficiently. -方案一 +Option 1 -1. 转到「**设置**」→「**应用程序**」→「**权限**」→「**后台自动启动**」并允许 AdGuard 在后台运行。 +1. Go to **Settings** → **Apps** → **Permissions** → **Background autostart** and allow AdGuard to run in the background -1. 返回「**设置**」→「**应用程序**」→「**管理应用程序**」→「**AdGuard**」并取消选中「**在未使用时暂停应用程序**」。 +1. Return to **Settings** → **Apps** → **Manage apps** → **AdGuard** and uncheck **Pause app activity if unused** -1. 转到「**省电模式**」并点击「**无限**」。 +1. Go to **Battery saver** and tap **No restrictions** -方案二 +Option 2 -1. 转到「**设置**」→「**应用程序**」→「**管理应用程序**」→「**AdGuard**」并启用「**自动启动**」。 +1. Go to **Settings** → **Apps** → **Manage apps** → **AdGuard** and enable **Autostart** -1. 转到「**省电模式**」并点击「**无限**」。 +1. Go to **Battery saver** and tap **No restrictions** -完成！ 您已成功设置 AdGuard 在后台运行。 +Done! You have successfully set up AdGuard to work in the background. ### MIUI 12.0.8 @@ -529,7 +529,7 @@ Sony 是第一家引入非标准后台进程优化的移动操作系统开发商 您还需要将 AdGuard 从省电功能中排除： -「**系统设置**」→「**应用程序和通知**」→「**高级**」→「**特殊应用程序访问权限**」→「**省电功能**」→ 将 AdGuard 切换到「**除外**」。 +「**系统设置**」→「**应用和通知**」→「**高级**」→「**特殊应用访问权限**」→「**省电功能**」→ 将 AdGuard 切换为「**除外**」 ## WIKO diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 36ec9029f98..6df58b4d849 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ sidebar_position: 1 ::: -由于内置统计过程，Android 6 及更早版本经常将高数据和/或电量消耗归因于 AdGuard。 这是因为 AdGuard 计算从各应用过滤的所有流量。 从而高估 AdGuard 总数据和电池使用率所占份额，而低估其它应用所占份额。 +在运行 Android 版本 6 和更早版本的设备上，内置的统计数据常将高数据/电池使用率归因于 AdGuard。 这是因为 AdGuard 计算从各应用过滤的所有流量。 从而高估 AdGuard 总数据和电池使用率所占份额，而低估其它应用所占份额。 在 Android 7 此种情况得到改善。 现在 Android 内置的数据使用统计中反映的数据非常接近现实，尽管电池使用数据存在细微差异。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 021d55523e5..e4989438422 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Android Pie 中引入了私有 DNS 功能。 在 Q 版本之前，私有 DNS 不 ### UC 浏览器：UC 浏览器、适用于 x86 的 UC 浏览器、UC Mini、UC 浏览器 HD -要过滤 HTTPS 流量，AdGuard 要求用户将证书添加到设备的受信任用户证书中。 不幸的是，UC 浏览器不信任用户证书，因此 AdGuard 无法执行 HTTPS 过滤。 +要过滤 HTTPS 流量，AdGuard 要求用户将证书添加到设备的受信任用户证书中。 不幸的是，UC 系列浏览器不信任用户证书，因此 AdGuard 无法执行 HTTPS 过滤。 - 要解决此问题，请将[证书移至系统证书存储](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/extending-restricted-settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/extending-restricted-settings.md index 33f7a7a93a2..07547ff3748 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/extending-restricted-settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/extending-restricted-settings.md @@ -1,5 +1,5 @@ --- -title: 扩展受限设置造成的问题 +title: Problems caused by extending restricted settings sidebar_position: 18 --- @@ -9,28 +9,28 @@ sidebar_position: 18 ::: -为了提高用户隐私保护，Google 在 Android 15 中扩展了限制设置。 现在，更多设置需要额外的权限才能启用包，比如「应用程序使用访问权限」。 由于[防火墙](/adguard-for-android/features/protection/firewall)和[检测 Samsung Pay](/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea) 功能需要启用「应用使用访问权限」设置才能正常工作，因此用户在使用它们时可能会遇到问题。 要解决这些问题，请按照以下步骤操作： +In an effort to improve user privacy, Google has expanded the restriction settings in Android 15. More settings, such as _App usage access_, now require an additional permission to be enabled. Since the _[Firewall](/adguard-for-android/features/protection/firewall)_ and _[Detect Samsung Pay](/adguard-for-android/solving-problems/samsungpay-with-adguard-in-south-korea)_ features require the _App usage access_ setting to be enabled for them to work properly, you may have experienced problems using them. To resolve these issues, please follow the steps below: :::note -AdGuard 有严格的不记录政策，就是说我们不会收集您的数据或将其发送给第三方。 我们只要求访问应用无法运行的数据。 +AdGuard has a strict no-logging policy, which means that we do not collect your data or send it to third parties. We only ask for access to data without which the application cannot function. ::: -1. 在 Android 设备上，打开「**设置**」。 -2. 点击「**应用**」。 -3. 点击「**AdGuard**」。 +1. On your Android device, open the **Settings app**. +2. Tap **Apps**. +3. Tap **AdGuard** -![AdGuard 在应用程序中 \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/problems-caused-by-extending-restricted-settings/restricted1.png) +![AdGuard in Apps \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/problems-caused-by-extending-restricted-settings/restricted1.png) -如您无法找到它，请先点击「**查看所有应用**」或「**应用信息**」。 +If you can't find it, first tap **See all apps** or **App info**. -1. 点击「**更多**」(⁝) →「允许受限设置」。 +1. Tap **More** (⁝) → _Allow restricted settings_. -![允许受限设置 \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/problems-caused-by-extending-restricted-settings/restricted2.png) +![Allow restricted settings \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/problems-caused-by-extending-restricted-settings/restricted2.png) -按照屏幕上的说明操作。 +Follow the on-screen instructions. -完成！ 「防火墙」和「检测三星支付」功能可正常工作。 +All done! Now the _Firewall_ and _Detect Samsung Pay_ features will work correctly. -![对 AdGuard 允许的限制设置 \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/problems-caused-by-extending-restricted-settings/restricted3.png) +![Restricted settings allowed for AdGuard \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/problems-caused-by-extending-restricted-settings/restricted3.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index 2f5e22743db..eddd8c4b916 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: 如何生成 HAR 文件 +title: 如何收集 HAR 文件 sidebar_position: 5 --- @@ -11,7 +11,7 @@ sidebar_position: 5 :::note -HAR 文件将根据 [AdGuard 隐私政策](https://adguard.com/en/privacy.html)处理。 +HAR files are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: @@ -19,7 +19,7 @@ HAR 文件将根据 [AdGuard 隐私政策](https://adguard.com/en/privacy.html) HAR（HTTP ARchive）格式是 JSON 格式的存档文件，用于记录 Web 浏览器与站点的交互。 HAR 格式的规范定义了 HTTP 交易的存档数据，浏览器使用该数据来导出其加载的网页的详细信息。 您可以在 [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) 网站上找到有关 HAR 文件格式及其使用规范的更详细说明。 -## 如何生成 HAR 文件 +## 如何收集 HAR 文件 有时我们需要对文件进行分析以拦截由于某种原因难以再现的特定广告。 要获取 HAR 文件，请执行以下步骤： @@ -31,7 +31,7 @@ HAR（HTTP ARchive）格式是 JSON 格式的存档文件，用于记录 Web 浏 6. 回到「**高级设置**」。 7. 点击「**导出日志和系统信息**」→「**允许**」（如有必要）→「**保存**」。 -**将生成的文件与日志记录一起发送至 AdGuard 支持服务。** +**请将导出的日志记录发送给 AdGuard 客服支持。** :::note diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index d6b611772e4..849b57bd06b 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Android 版 AdGuard 可以[过滤加密的 HTTPS 流量](/general/https-filterin 1. 安装[最新版本的 **adguardcert** Magisk 模块](https://github.com/AdguardTeam/adguardcert/releases/latest/)。 -1. 打开*「Magisk」→「模块」→「从存储安装」*并选择下载的 **adguardcert** 文件。 AdGuard Personal CA 证书将被复制到系统存储。 +1. 打开*「Magisk」→「模块」→「从存储安装」*并选择下载的 **adguardcert** 文件。 这样 AdGuard Personal CA 就从用户存储移到了系统存储。 ![打开 Magisk 模块 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index 0e9442644e2..555e8eaa915 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -11,7 +11,7 @@ sidebar_position: 2 :::note -日志记录中提供的数据和/或文件将根据 [AdGuard 隐私政策](https://adguard.com/en/privacy.html)处理。 +Data and/or files provided in logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: @@ -19,13 +19,13 @@ sidebar_position: 2 :::note -AdGuard 致力于保护用户的个人隐私。 我们严格遵守我们的[隐私政策](https://adguard.com/privacy/android.html) ，不收集任何有关用户的私人信息。 请注意：在将您的日志记录发送给客户支持团队之前，请检查文件，因为它会包含您不想分享的附加信息。 如果其中包含此类个人信息，我们建议您先将其删除。 +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -### 记录调试日志 +### 收集调试日志 -为了收集**调试**日志并将其转发给我们，要完成以下操作步骤： +为了收集**调试**日志并将其转发给我们，您要完成以下操作步骤： 1. 转至「*设置*」→「*常规*」→「*高级*」。 1. 点击「*日志记录级别*」并设置为「*调试*」。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md index db277bd408f..4dbab96ec16 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/logcat.md @@ -11,7 +11,7 @@ sidebar_position: 4 :::note -日志记录中提供的数据和/或文件将根据 [AdGuard 隐私政策](https://adguard.com/en/privacy.html)处理。 +Data and/or files provided in logs are processed in accordance with [the AdGuard Privacy Policy](https://adguard.com/en/privacy.html). ::: @@ -19,7 +19,7 @@ sidebar_position: 4 :::note -AdGuard 致力于保护用户的个人隐私。 我们严格遵守我们的[隐私政策](https://adguard.com/privacy/android.html) ，不收集任何有关用户的私人信息。 请注意：在将您的日志记录发送给客户支持团队之前，请检查文件，因为它会包含您不想分享的附加信息。 如果其中包含此类个人信息，我们建议您先将其删除。 +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/android.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 2c8051ef1ec..b87a8defd01 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -93,13 +93,13 @@ DoH、DoT 和 DoQ 服务器的 Bootstrap DNS。 默认使用的是「*自动 DNS 如果启用此设置，AdGuard 将在添加或更新自定义 DNS 服务器之前测试 DNS 上游。 -#### 过滤安全 DNS +#### Filter secure DNS -开启后，AdGuard 将所有启用的 DNS 过滤器和 DNS 用户规则应用于加密的 DNS-over-HTTPS (DoH) 流量，而不仅仅是普通 DNS。 DoH 流量主要来自 Chrome 和其他具有*安全 DNS* （或类似）设置的浏览器。 用户可以在两种不同模式下使用「*过滤安全 DNS*」功能： +If this setting is on, AdGuard will apply all enabled DNS filters and DNS user rules to encrypted DNS-over-HTTPS (DoH) traffic and not only to plain DNS. DoH traffic mostly comes from Chrome and other browsers that have a *Secure DNS* (or similar) setting. You can use *Filter secure DNS* in two different modes: -- **即时过滤**模式。 AdGuard 对 DoH 流量应用所有已启用的 DNS 过滤器和 DNS 用户规则，但不会将其重定向到本地 DNS 代理。 如果在浏览器设置中指定 DNS 服务器，该服务器将处理该浏览器的 DoH 流量。 +- **Filter on the fly**. In this mode, AdGuard applies all enabled DNS filters and DNS user rules to DoH traffic but doesn’t redirect it to the local DNS proxy. If a DNS server is specified in the browser’s settings, this server will handle the DoH traffic for this browser -- **重定向到 DNS 代理**模式。 AdGuard 通过将流量重定向到本地 DNS 代理，将所有已启用的 DNS 过滤器和 DNS 用户规则应用于 DoH 流量。 AdGuard DNS 设置中指定的 DNS 服务器将处理所有 DoH 流量。 +- **Redirect to DNS proxy**. In this mode, AdGuard applies all enabled DNS filters and DNS user rules to DoH traffic by redirecting it to the local DNS proxy. The DNS server specified in the AdGuard’s DNS settings will handle all DoH traffic ### 过滤 @@ -113,7 +113,7 @@ DoH、DoT 和 DoQ 服务器的 Bootstrap DNS。 默认使用的是「*自动 DNS #### Encrypted Client Hello -每一个加密的互联网连接都有一个未加密的部分， 就是发送的第一个数据包，包含用户要连接的服务器名称。 Encrypted ClientHello（ECH）的技术能够解决该问题，成功加密最后一位未加密的信息。 要使用该功能，请启用「*Encrypted ClientHello*」选项。 本功能使用本地 DNS 代理查找域名的 ECH 配置。 如果找到，将对 Client Hello 数据包进行加密。 +每一个加密的互联网连接都有一个未加密的部分， 就是发送的第一个数据包，包含用户要连接的服务器名称。 Encrypted ClientHello（ECH）的技术能够解决该问题，成功加密最后一位未加密的信息。 要使用该功能，请启用「*Encrypted ClientHello*」选项。 本功能使用本地 DNS 代理查找域名的 ECH 配置。 如果找到，将对 ClientHello 数据包进行加密。 #### OCSP 检查 @@ -147,7 +147,7 @@ DoH、DoT 和 DoQ 服务器的 Bootstrap DNS。 默认使用的是「*自动 DNS 如果启用此设置，AdGuard 将在「*最近活动*」中记录被阻止的 HTML 元素。 -#### 小脚本调试 +#### Scriplet 调试 如果启用此设置，Scriptlets 中的调试将被激活，浏览器日志将记录 Scriptlets 规则的应用情况。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index d020fb268a7..932e84ba095 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -1,5 +1,5 @@ --- -title: 如何设置出站代理 +title: 如何设置出战代理 sidebar_position: 8 --- @@ -9,7 +9,7 @@ sidebar_position: 8 ::: -以下是最常用的应用程序列表，用户可以将其配置为 AdGuard 的代理。 +以下是最著名的应用程序列表，用户可以将其配置为 AdGuard 的代理。 :::note @@ -89,25 +89,25 @@ AdGuard 可以通过代理服务器路由设备流量。 要访问代理设置 ### 如何同时使用 AdGuard 和 NordVPN -1. 登录您的 NordVPN 账号。 +1. Log in to your NordVPN account. -1. 转到「**服务**」→「**NordVPN**」→「**手动设置**」，手动设置您的服务信息。 +1. Go to **Services** → **NordVPN** → **Manual setup** and set up your service credentials manually. -1. 用户将通过 NordVPN 使用的电子邮件地址收到验证码。 按照要求请在您的 NordVPN 账号上输入代码，然后点击「*应用*」和「*确定*」保存更改。 +1. You will receive a verification code on the email address you use for NordVPN. Use it on your NordVPN account as requested, then tap *Apply* and *OK* to save the changes. -![手动设置](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/outbound-proxy/nordvpn-manual-setup.png) +![Manual setup](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/outbound-proxy/nordvpn-manual-setup.png) -1. 打开 AdGuard 应用程序，进入「**设置**」→「**过滤**」→「**网络**」→「**代理**」→「**代理服务器**」→「**添加代理服务器**」。 +1. Open the AdGuard app, go to **Settings** → **Filtering** → **Network** → **Proxy** → **Proxy server** → **Add proxy server**. -1. 输入以下信息： +1. Enter the following data: - | 字符串 | 数值 | - | ---- | -------------------------------------------------------------------------------------------------------------- | - | 代理分类 | *SOCKS5* | - | 代理主机 | [此列表](https://support.nordvpn.com/hc/en-us/articles/20195967385745-NordVPN-proxy-setup-for-qBittorrent)中的任何服务器 | - | 代理端口 | *1080* | + | 字符串 | 数值 | + | ---- | ----------------------------------------------------------------------------------------------------------------------------- | + | 代理分类 | *SOCKS5* | + | 代理主机 | Any server from [this list](https://support.nordvpn.com/hc/en-us/articles/20195967385745-NordVPN-proxy-setup-for-qBittorrent) | + | 代理端口 | *1080* | -1. 在「**用户名**」和「**密码**」字段中输入 NordVPN 信息。 +1. Enter your NordVPN credentials in the **Username** and **Password** fields. 1. 点击「**选择并保存**」。 @@ -157,4 +157,4 @@ AdGuard 可以通过代理服务器路由设备流量。 要访问代理设置 ## 限制 -即使用户配置 AdGuard 代理设置，也有一个原因会阻止流量通过出站代理路由。 这个原因是，应用程序本身未配置通过 AdGuard 发送其流量。 要解决这个问题，请进一步设置「**应用管理**」，选择应用程序，并打开「**通过 AdGuard 路由流量**」。 +即使用户配置 AdGuard 代理设置，也有一个因素会阻止流量通过出站代理路由。 如果用户没有设置应用程序本身通过 AdGuard 发送流量，这种情况就会发生。 要做到这一点，请进一步设置「**应用管理**」，选择应用程序，并打开「**通过 AdGuard 路由流量**」。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index e1aad7968b9..ff087f248c4 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -41,13 +41,13 @@ sidebar_position: 3 `enable:true` 或 `enable:false` 相应地启用或禁用 DNS 过滤。 -`fake_dns` 允许在指定的代理服务器上解析 DNS 请求。 这个设置需要额外的标志： +`fake_dns` allows resolving DNS requests on the specified proxy server. This requires an extra flag: -`enable:true` 或 `enable:false` 可以分别启用或禁用「*使用 FakeDNS*」设置。 +`enable:true` or `enable:false` enables or disables the *Use FakeDNS* setting, respectively. :::note -启用「*使用 FakeDNS*」设置时，「*DNS 保护*」将自动禁用。 DNS 请求不会在本地被过滤。 +When the *Use FakeDNS* setting is enabled, *DNS Protection* will be automatically disabled. DNS requests won't be filtered locally. ::: @@ -65,7 +65,7 @@ sidebar_position: 3 `server:custom` 切换到之前添加的名为 `custom` 的服务器； - `server:tls://dns.adguard.com` 如果之前添加的服务器和提供商不包含具有相同地址的服务器，则创建一个新服务器并切换到该服务器。 否则，它会切换到相应的服务器。 用户可以将服务器地址添加为 IP（普通 DNS）、`sdns://…`（DNSCrypt 或 DNS-over-HTTPS）、`https://…`（DNS-over-HTTPS）或 `tls:`//...(DNS-over-TLS）； + `server:tls://dns.adguard.com` 如果之前添加的服务器和提供商不包含具有相同地址的服务器，则创建一个新服务器并切换到该服务器。 否则，它会切换到相应的服务器。 You can add server addresses as IP ( regular DNS), `sdns://…` (DNSCrypt or DNS-over-HTTPS), `https://…` (DNS-over-HTTPS) or `tls://...` (DNS-over-TLS); `server:1.1.1.1, tls://1.1.1.1` 创建一个用逗号分隔地址的服务器并切换到它。 通过`server:1.1.1.1, tls://1`.1.1 添加服务器时，先前添加的服务器将被移除。 @@ -126,7 +126,7 @@ sidebar_position: 3 ::: -**请别忘记包含密码、包名称和类别。 您需要为每个 intent 消息都这样做。** +**别忘记把密码作为附加项，并提及软件包名称和类别。 您需要为每个 intent 消息都这样做。** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -在 v4.0 之前，该类被称为 `com.adguard.android.receivers.AutomationReceiver` 但是后来我们将其名称更改为 `com.adguard.android.receiver.AutomationReceiver`。 如果用户使用该功能，请记得更新名称。 +在 v4.0 之前，该类被称为 `com.adguard.android.receivers.AutomationReceiver` 但是后来我们将其名称更改为 `com.adguard.android.receiver.AutomationReceiver`。 如果用户使用过该功能，请留意并使用新的名称。 ::: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 786b71a3755..00000000000 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: 免费版和完整版 -sidebar_position: 9 ---- - -:::info - -本文所述 AdGuard iOS 版是在系统级上保护设备的多功能的广告拦截器。 要了解其工作原理，请[下载 AdGuard 应用程序](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index 7ab28e82398..daa217b4e55 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard iOS版是 App Store 中的一款应用程序。 To install it on your de ![在 App Store 主屏幕上，点击「搜索」 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![在搜索栏中输入 "AdGuard" *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro 是 AdGuard iOS版的付费版本。AdGuard Pro 为用户提供更 ![在 App Store 主屏幕上，点击「搜索」 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![在搜索栏中输入 "AdGuard" *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. 为了完成安装过程，您可能会看到要求输入您的苹果 ID 和密码的弹窗。 输入您的 ID 和密码后，请等待安装成功完成。 +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. 为了完成安装过程，您可能会看到要求输入您的苹果 ID 和密码的弹窗。 输入您的 ID 和密码后，请等待安装成功完成。 ![点击 AdGuard 应用程序下方的「获取」 *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index 57e23bc4861..7e10e1f981f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -1,5 +1,5 @@ --- -title: 如何拦截 Youtube 广告 +title: How to block YouTube ads sidebar_position: 4 --- @@ -9,26 +9,26 @@ sidebar_position: 4 ::: - + ## 如何在 YouTube 应用中拦截广告 -1. 打开 YouTube 应用程序。 -1. 选择视频并点击「*分享*」。 -1. 点击「*更多*」，然后选择「*拦截 YouTube 的广告（由 AdGuard 创建）*」。 +1. Open the YouTube app. +1. Choose a video and tap *Share*. +1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -视频将在 AdGuard 的无广告播放器中打开。 +AdGuard will open its ad-free video player. ## 如何在 Safari 中拦截 YouTube 广告 :::tip -请确保您已给 AdGuard 管理所有网站的权限。 要开启访问权限，前往「Safari」→「扩展」→「AdGuard」。 然后打开 AdGuard 并启用「*高级保护*」。 +Make sure you've given AdGuard access to all websites. You can check it in Safari → Extensions → AdGuard. Then open AdGuard and enable *Advanced protection*. ::: 1. 在 Safari 中打开 youtube.com -1. 选择视频并点击「*分享*」。 -1. 点击「*拦截 YouTube 的广告（由 AdGuard 创建）*」。 +1. Choose a video and tap *Share*. +1. Tap *Block YouTube Ads (by AdGuard)*. -视频将在 AdGuard 的无广告播放器中打开。 +AdGuard will open its ad-free video player. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index 77cf4ceccc1..24dbfec7bb8 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: 如何避免与 FaceTime 的兼容性问题 +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index e3cacc6ac51..9dcb2e255dc 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md index 4ed2dab3878..6df88b22e6f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/features/general.md @@ -11,7 +11,7 @@ sidebar_position: 2 ## 如何打开应用设置 -要配置 Mac 版 AdGuard，请单击主窗口右上角的齿轮图标并选择「设置」。 +To configure AdGuard for Mac, click the gear icon in the upper right corner of the main window and select _Preferences_. ![主窗口 \*mobile](https://cdn.adtidy.org/content/kb/ad_blocker/mac/main.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md index 6c49ff2183b..b9bfab394b8 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/installation.md @@ -11,7 +11,7 @@ sidebar_position: 2 ## 系统要求 -**操作系统版本**： macOS 10.15（64 位）或更高版本 +**Operating system version:** macOS 10.15 (64 bit) or higher **RAM**： 至少 2 GB @@ -21,11 +21,11 @@ sidebar_position: 2 ## 安装过程 -要将 AdGuard Mac 版安装到电脑上，请打开浏览器，在地址栏键入 *adguard.com* 后，在[打开的网页](https://adguard.com/download.html?auto=1)上点击「**下载**」按钮。 +To install AdGuard for Mac on your computer, launch your browser, type *adguard.com* in the address bar, and press **Download** [on the page that opens](https://adguard.com/download.html?auto=1). ![下载应用 *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/1.jpg) -请等待 *AdguardInstaller.dmg* 下载完成后，在 Dock 栏上已安装的文件列表里双击它的图标。 +Wait for *AdguardInstaller.dmg* to download and double-click its icon in the list of downloaded files on the Dock panel. ![双击打开文件](https://cdn.adtidy.org/content/kb/ad_blocker/mac/installation_open_the_file.jpg) @@ -45,7 +45,7 @@ AdGuard 图标将出现在您的桌面上。 单击它打开安装应用程序 ![等到下载必要的文件](https://cdn.adtidy.org/content/kb/ad_blocker/mac/6.jpg) -以使用应用程序，需要输入 macOS 账号的用户名和密码。 在弹出的对话框上输入用户名和密码后，点击**好**。 +以使用应用程序，需要输入 macOS 账号的用户名和密码。 Enter the password when prompted in the dialogue box and press **OK**. ![输入密码](https://cdn.adtidy.org/content/kb/ad_blocker/mac/7.jpg) @@ -80,7 +80,7 @@ AdGuard 图标将出现在您的桌面上。 单击它打开安装应用程序 - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard-pac.daemon.log（文件）。 - /Library/Logs/com.adguard.mac.adguard/com.adguard.mac.adguard.adguard-tun-helper.daemon.log（文件） - 为了执行上述步骤，请您打开 Terminal 终端，然后输入并执行以下的指令： + To do so, open the Terminal app, then enter and execute the following commands: ```bash sudo rm -R "/Library/Application Support/AdGuard Software/com.adguard.mac.adguard" @@ -99,7 +99,7 @@ AdGuard 图标将出现在您的桌面上。 单击它打开安装应用程序 ![开启活动监视器](https://cdn.adtidy.org/content/kb/ad_blocker/mac/22.jpg) -1. 退出在用户态下运行的进程（不是在 root 权限运行的）。 为了退出，请点击进程，然后在左上角点击 X。 在对话窗确认要退出。 +1. 退出在用户态下运行的进程（不是在 root 权限运行的）。 为了退出，请点击进程，然后在左上角点击 X。 Confirm the action in the dialogue window. ![确认](https://cdn.adtidy.org/content/kb/ad_blocker/mac/33.jpg) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 94b9522bb7f..0903a387afd 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -21,7 +21,7 @@ sidebar_position: 9 ## 高级设置 -### 网络设置 +### Network settings #### `network.extension.exclude.domains` @@ -71,7 +71,7 @@ sidebar_position: 9 #### `network.https.ech.enabled` -使用本地 DNS 代理在 ECH 配置列表中查找配置。 如果找到，加密 Client Hellos。 +使用本地 DNS 代理在 ECH 配置列表中查找配置。 如果找到，加密 ClientHellos。 #### `network.https.enforce.certificate.transparency` @@ -89,7 +89,7 @@ sidebar_position: 9 设置为 `true` 即可启用 LoopBack 过滤功能。 -### DNS 设置 +### DNS settings #### `dns.proxy.bootstrap.ips` @@ -145,7 +145,7 @@ sidebar_position: 9 #### `dns.proxy.parallel.upstream.queries.enabled` -同时查询所有上游。 返回第一个响应。 +同时查询所有上游。 The first response is returned. #### `dns.proxy.servfail.on.upstreams.failure.enabled` @@ -159,7 +159,7 @@ sidebar_position: 9 删除响应中的 Encrypted Client Hello 参数。 -### 隐身模式设置 +### Stealth Mode settings #### `stealth.antidpi.http.split.fragment.size` @@ -177,7 +177,7 @@ sidebar_position: 9 如果执行了分片，用户可以在此处指定发送第一个分片后的延迟（以毫秒为单位）。 -### 订阅链接拦截设置（用户脚本和过滤器） +### Subscription link interception settings (userscripts and filters) #### `subscription.link.interception.userscript` diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index 20473782f99..b532ab8b4d2 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -31,7 +31,7 @@ Apple 公司尚未解决这些问题，或者只解决了部分问题。 用户可以禁用 AdGuard，防止它使用「默认路由」功能。 前往「高级设置」→「`network.extension.monterey.force.split.tunnel`」进行设置。 请注意，启用此设置会导致上述问题。 -![高级设置指南 *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_adguard_advanced_settings.jpg) +![Advanced Settings *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_adguard_advanced_settings.jpg) #### 与保护邮件活动（Protect Mail Activity）的兼容性 @@ -63,7 +63,7 @@ Apple 公司尚未解决这些问题，或者只解决了部分问题。 #### 使用旧版 API 的 VPN 应用程序 -尽管 AdGuard 在系统设置中显示为 VPN，但与其他基于 VPN 的应用程序一起使用时应该不会引起任何冲突。 但是，如果使用的是在 App Store 以外下载的基于 VPN 的应用程序，有可能是具有旧 VPN API 的应用，因此需要将其排除在过滤范围之外： +尽管 AdGuard 在系统设置中显示为 VPN，但与其他基于 VPN 的应用程序一起使用时应该不会引起任何冲突。 不过，如果用户使用的是从 App Store 以外下载的基于 VPN 的应用程序，它有可能使用旧的 VPN API，用户必须将其排除在过滤之外： 1. 开启 AdGuard 菜单。 1. 选择「*首选项...*」。 @@ -71,7 +71,7 @@ Apple 公司尚未解决这些问题，或者只解决了部分问题。 1. 单击「*应用程序*」按钮。 1. 找到要排除的应用程序，取消选中旁边的复选框。 -![过滤应用程序](https://cdn.adtidy.org/content/kb/ad_blocker/mac/legacy.jpg) +![Filtered applications](https://cdn.adtidy.org/content/kb/ad_blocker/mac/legacy.jpg) ## 已修复的问题 @@ -81,7 +81,7 @@ Apple 公司现已修复了以下问题，但在旧版本的 macOS Big Sur 中 目前，AdGuard 的「网络扩展」模式无法与 [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html) 兼容。 当这两个程序都在运行时，有可能会遇到各种应用程序的行为问题，即使它们没有被 AdGuard 过滤。 这个问题是由 Big Sur 中的一个错误造成的，我们已经向 Apple 公司通报这一情况。 这让我们相信，这个问题会在下一次更新中得到解决。 -但是，禁用 Little Snitch 中的连接监控无法解决问题，因为该行为无法从系统内存中卸载 Little Snitch 扩展。 我们建议，至少在 Apple 修复该错误之前，切换到「[**自动代理**](#automatic-proxy)」过滤模式。 +请注意，这个问题无法通过禁用「Little Snitch」的连接监控来解决，因为这一操作并不能从系统中卸载「Little Snitch」的扩展。 我们建议，至少在 Apple 修复该错误之前，切换到「[**自动代理**](#automatic-proxy)」过滤模式。 ### 与本地代理的兼容性 @@ -121,82 +121,82 @@ Apple 公司现已修复了以下问题，但在旧版本的 macOS Big Sur 中 :::tip -请参阅 [Shadowsocks 网站](https://shadowsocks.org/guide/what-is-shadowsocks.html) 了解更多信息。 +您可以在 [Shadowsocks 网站](https://shadowsocks.org/guide/what-is-shadowsocks.html)上找到有关如何开始设置的更多信息。 ::: 然后，用户要在 Mac 上安装 Shadowsocks 客户端。 请确保在设置中选择「手动模式」或「自动模式」！ 如果您选择「全局模式」（或 11.1 之前 Big Sur 版本中的「自动模式」），配置将不起作用。 -![在设置中选择手动模式或自动模式 *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/mac/shadowsocks.jpg) +![Select Manual Mode or Auto Mode in settings *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/mac/shadowsocks.jpg) -现在进入*AdGuard 菜单 →「高级」→「高级设置」*，并将 `upstream.proxy` 设置的*数值*设置为 `socks5://localhost:1080`。 请注意，需要使用 JSON 文件中的 “local_port” 值。 +Now go to *AdGuard menu → Advanced → Advanced Settings...* and set the *Value* area of the `upstream.proxy` setting to `socks5://localhost:1080`. Notice that you need to use "local_port" value from the JSON file here. -由于 Shadowsocks 使用 SOCKS5，因此还需要将 AdGuard 高级设置中的 `upstream.proxy.socks5udp` 值设置为 `true`，以便 AdGuard 将 UDP 流量路由到代理服务器。 +Because Shadowsocks uses SOCKS5, you also need to set the value of the `upstream.proxy.socks5udp` setting in AdGuard Advanced Settings to `true` to make AdGuard route UDP traffic to the proxy server. -#### 示例 2：配置上游 Surge 代理 +#### Example 2: Configuring an upstream Surge proxy -在 Big Sur v11.1+ 中，AdGuard 和 Surge 代理之间没有已知的冲突。 如果用户使用的是旧版本的 Big Sur（11.1 之前的版本），请检查右下角的「**系统代理**」是否已禁用。 否则，Surge 无法与 AdGuard 一起使用。 另一方面，「**增强模式**」可以在任何 Big Sur 版本中启用而不会引起冲突。 +In Big Sur v11.1+, there are no known conflicts between AdGuard and Surge proxy. If you are using an older version of Big Sur (prior to 11.1), check that **System Proxy** in the bottom right corner is disabled. Otherwise, Surge won't work with AdGuard. On the other hand, **Enhanced Mode** can be enabled without causing a conflict in any Big Sur version. -![配置上游 Surge 代理 *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/outbound-proxy.png) +![Configuring an upstream Surge proxy *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/outbound-proxy.png) -请转到*「首选项」→「网络」→「出站代理」*并填写字段。 SOCKS5 代理类型： +Now go to *Preferences → Network → Outbound proxy* and fill in the fields. For SOCKS5 proxy type: -- `host`：localhost -- `port`：6153 HTTP 代理类型： -- `host`：localhost -- `port`：6152 +- `host`: localhost +- `port`: 6153 For HTTP proxy type: +- `host`: localhost +- `port`: 6152 -## 使用网络扩展的替代方案 +## Alternatives to using a Network Extension -我们无法预见到 Big Sur 或 Monterey 可能出现的所有问题，因为有无数不同的硬件/软件和设置配置。 如果您遇到任何兼容性问题，联系我们的支持团队前，请尝试使用以下解决方案。 +It's impossible to foresee each and every possible problem that can pop up in Big Sur or Monterey, there are countless various hardware/software and settings configurations. If you face any compatibility issues, please contact our support team, but feel free to try one of these workarounds first. -### 使用「自动代理」过滤模式 {#automatic-proxy} +### Using "Automatic proxy" filtering mode {#automatic-proxy} -如果用户在 Big Sur 或 Monterey 上遇到的问题无法通过上述任何方法解决，您可以尝试将 AdGuard 切换到「*自动代理*」模式。 +If you face problems in Big Sur or Monterey which can't be resolved by any of the methods above, you can try switching AdGuard to *Automatic proxy* mode. 1. 开启 AdGuard 菜单。 1. 选择「*首选项...*」。 1. 切换到「*网络*」选项卡。 -1. 单击「*选择模式...*」按钮。 -1. 选择「*自动代理*」。 +1. Click the *Select Mode...* button. +1. Select *Automatic Proxy*. -![将 AdGuard 切换到自动代理模式](https://cdn.adtidy.org/content/kb/ad_blocker/mac/automatic-proxy_en.jpg) +![Switch AdGuard to Automatic proxy mode](https://cdn.adtidy.org/content/kb/ad_blocker/mac/automatic-proxy_en.jpg) -现在，AdGuard 自动在 Mac 的网络设置中添加一个 **.pac** 文件。这样系统就会将 AdGuard 视为代理，并尝试通过 AdGuard 发送所有流量。 +Now AdGuard has automatically added a **.pac** file to your Mac's network settings, so that the system will consider AdGuard a proxy and try to send all traffic through AdGuard. :::note -有些应用程序可能会忽略这一系统设置，其流量将不会被过滤。 +Some apps may ignore this system setting and their traffic will not be filtered. ::: -### 在 Big Sur 和 Monterey 中启用内核扩展 {#kernel-extension} +### Enabling Kernel Extension in Big Sur and Monterey {#kernel-extension} -默认情况下，Big Sur 和 Monterey 禁用了旧内核扩展框架，因此 AdGuard 使用网络扩展框架。 这可能会导致兼容性问题，但要重新启用内核扩展，必须首先禁用系统完整性保护（英语：System Integrity Protection，英语缩写：SIP）。 要禁用 SIP，请按此说明操作： +By default AdGuard uses Network Extension framework in Big Sur and Monterey as the old Kernel Extension framework is disabled there. This can cause some compatibility problems, but to enable Kernel Extension back, you need to disable System Integrity Protection (SIP) first. To disable SIP, follow this instruction: 1. Click the *Apple symbol* in the Menu bar. -1. 点击「*重启…*」。 -1. 按住 *Command-R* 重启进入恢复模式。 -1. 单击「*实用程序*」。 -1. 选择「*终端*」。 -1. 输入 `csrutil disable`。 -1. 按键盘上的 *Return* 或 *Enter* 键。 -1. 单击菜单栏中的 * Apple 符号*。 -1. 点击「*重启…*」。 +1. Click *Restart…* +1. Hold down *Command-R* to reboot into Recovery Mode. +1. Click *Utilities*. +1. Select *Terminal*. +1. Type `csrutil disable`. +1. Press *Return* or *Enter* on your keyboard. +1. Click the *Apple symbol* in the Menu bar. +1. Click *Restart…* -禁用 SIP 后，就可以启用内核扩展： +Now that SIP is disabled, this is how you enable Kernel Extension: -![启用内核扩展](https://cdn.adtidy.org/content/kb/ad_blocker/mac/kernel_en.jpg) +![Enable Kernel Extension](https://cdn.adtidy.org/content/kb/ad_blocker/mac/kernel_en.jpg) 1. 开启 AdGuard 菜单。 1. 选择「*首选项...*」。 1. 切换到「*网络*」选项卡。 -1. 单击「*选择模式...*」按钮。 -1. 选择「*内核扩展*」。 -1. 确认要切换到内核扩展。 +1. Click the *Select Mode...* button. +1. Select *Kernel Extension*. +1. Confirm that you want to switch to Kernel Extension. :::caution -不过，我们只建议在其他方法都失败的情况下使用上述方法，因为这可能会导致一些问题。 +However, we only recommend using this method if everything else fails, as this may lead to unexpected issues. ::: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md index a79e9021b53..f079e8b307b 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/icloud-private-relay.md @@ -27,22 +27,22 @@ AdGuard 默认使用「默认路由」功能，禁用 iCloud 专用代理的原 因此，AdGuard 无法与 iCloud 专用代理和邮件应用程序的隐私功能一起使用： -1. iCloud 专用代理应用于库级别的连接，在连接到达 AdGuard 运行的套接字级别之前。 -2. iCloud 专用代理使用 QUIC，AdGuard 无法在已过滤的应用程序中过滤 QUIC，因为 HTTP/3 过滤尚未可用。 -3. 因此，AdGuard 会阻止 QUIC，包括 iCloud 专用代理的流量，否则就无法拦截广告。 -4. 当用户使用 iCloud 专用代理，将 AdGuard 切换到「分离隧道」模式时，就无法在 Safari 中打开网站。 -5. 要在 Monterey 上解决这个问题，我们应用「默认路由」规则。 专用代理检测到该规则时，功能将自动禁用。 因此，AdGuard 可以在 Monterey 上无缝运行，但 iCloud 专用代理会被禁用。 +1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. +2. iCloud Private Relay uses QUIC, which AdGuard can't filter in filtered apps because HTTP/3 filtering is not yet available. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic — otherwise, ad blocking is impossible. +4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. +5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. -`network.extension.monterey.force.split.tunnel` 恢复了 Big Sur 行为，但由于（3）和（4）的原因，该选项会中断网站访问权限。 我们努力寻找能够解决这个问题的办法。 一种可能的解决方案是实施 HTTP/3 过滤。 +`network.extension.monterey.force.split.tunnel` restores the "Big Sur" behavior, but this option may break access to websites due to (3) and (4). We keep searching for a solution to this issue. One of the options is implementing HTTP/3 filtering. -## 建议的解决方案 +## Recommended solution -我们建议将 AdGuard 与更传统的 VPN 服务（如 [AdGuard VPN](https://adguard-vpn.com/)）一起使用。 +We recommend using AdGuard together with a more traditional VPN service such as [AdGuard VPN](https://adguard-vpn.com/). -## 替代解决方案 +## Alternative solution -用户可以禁用「默认路由」，防止 AdGuard 使用「默认路由」。 前往「高级设置」→ `network.extension.monterey.force.split.tunnel` 进行设置。 +You can prevent AdGuard from using the "default route" by disabling the "default route". It can be done via Advanced Settings → `network.extension.monterey.force.split.tunnel`. -![在高级设置中禁用默认路由 *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_adguard_advanced_settings.jpg) +![Disable default route in advanced settings *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_adguard_advanced_settings.jpg) -请注意，在这种情况下，用户将面临上述问题。 +Bear in mind that, in this case, you'll face the issues described above. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/launch-issues.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/launch-issues.md index 64640a9aa83..2a16fa9d5bd 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/launch-issues.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/launch-issues.md @@ -1,5 +1,5 @@ --- -title: 在 macOS 上无法启动 AdGuard 应用程序的问题 +title: Launch issues on macOS sidebar_position: 6 --- @@ -9,32 +9,32 @@ sidebar_position: 6 ::: -在 macOS 上，AdGuard 网络扩展偶尔会损坏，导致 AdGuard 应用程序无法使用。 在这种情况下，用户应根据操作系统版本，遵循以下其中一条指令。 +Occasionally macOS may cause the corruption of AdGuard's Network Extension module, making it unable to use the app. In this case you should follow one of these instructions, based on your OS version. -## macOS 11 及更高版本上的启动问题 +## Launch issues on macOS 11 and higher -如果在 Big Sur、Monterey 和 Ventura 操作系统上启动 Mac 版 AdGuard 时遇到问题，请按照以下说明操作： +If you have problems launching AdGuard for Mac on Big Sur and Monterey operating systems, please use this instruction: -1. 重启 Mac 并进入[恢复模式](https://support.apple.com/en-us/HT201255)。 -1. 禁用 SIP（从**实用工具**菜单启动**终端**，输入 `csrutil disable`）。 -1. 重新启动 Mac。 -1. 关闭 AdGuard 应用程序，打开**终端**并键入 `systemextensionsctl reset`。 -1. 重新启动 Mac 并进入恢复模式。 -1. 启动 SIP（从**实用工具**菜单启动**终端**，输入 `csrutil disable`）。 -1. 启动 AdGuard 应用程序并启用保护。 +1. Reboot Mac and enter [recovery mode](https://support.apple.com/en-us/HT201255). +1. Disable SIP (Launch **Terminal** from the **Utilities** menu and type `csrutil disable`). +1. Reboot Mac. +1. Close the AdGuard app, open **Terminal** and type `systemextensionsctl reset`. +1. Reboot Mac and enter recovery mode. +1. Enable SIP (Launch **Terminal** from the **Utilities** menu and type `csrutil enable`). +1. Launch the AdGuard app and enable protection. -## 在 macOS 10 上无法启动 AdGuard 应用程序的问题 +## Launch issues on macOS 10 -如果在 Sierra、Mojave 和 Catalina 操作系统上启动 Mac 版 AdGuard 时遇到问题，请执行以下操作： +If you have problems launching AdGuard for Mac on Sierra, Mojave and Catalina operating systems, please use this instruction: -1. 打开**终端**并输入命令 `ls -@lOae /private/var/db/KernelExtensionManagement`。 -1. 请确认没有 ` restricted ` 标志（如截图所示）。 ![命令示例 *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/restricted-flag.jpg) -1. 在恢复模式下重启 Mac。 -1. 打开**实用程序** → **终端**。 -1. 输入 `csrutil disable`。 -1. 输入管理员密码。 -1. 重新启动 Mac。 -1. 打开**终端**，输入以下命令：`sudo chflags restricted /private/var/db/KernelExtensionManagement`。 -1. 在恢复模式下重启 Mac。 -1. 打开**实用工具** → **终端** → 输入 `csrutil enable` → 输入管理员密码 → 重新启动 Mac。 -1. 开启 AdGuard 保护。 +1. Open **Terminal** and enter command `ls -@lOae /private/var/db/KernelExtensionManagement`. +1. Check that the `restricted` flag is not present (like on the screenshot). ![Command example *border](https://cdn.adtidy.org/content/kb/ad_blocker/mac/restricted-flag.jpg) +1. Reboot your Mac in recovery mode. +1. Open **Utilities** → **Terminal**. +1. Enter `csrutil disable`. +1. Enter administrator password. +1. Reboot your Mac. +1. Open **Terminal** and enter the following command: `sudo chflags restricted /private/var/db/KernelExtensionManagement`. +1. Reboot your Mac in recovery mode. +1. Open **Utilities** → **Terminal** → Enter `csrutil enable` → Enter administrator password → Reboot your Mac. +1. Enable AdGuard protection. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md index cd18b0f0bea..3f1d33780db 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/manual-certificate-installation.md @@ -1,5 +1,5 @@ --- -title: 手动安装证书 +title: Manual certificate installation sidebar_position: 1 --- @@ -9,20 +9,20 @@ sidebar_position: 1 ::: -Mac 版 AdGuard 需要将 Root 证书安装到证书存储区，才能进行 [HTTPS 流量过滤](/general/https-filtering/what-is-https-filtering)。 在大多数情况下，首次运行应用程序时会自动执行安装，但使用基于 Gecko 的浏览器（如 Firefox、Waterfox）的用户，如果在浏览器中设置了主密码，则可能需要采取额外步骤（这些浏览器使用自己的证书存储空间，而不是系统的证书存储空间）。 出现提示时（允许 AdGuard 访问证书存储），必须输入主密码或手动安装证书。 +AdGuard for Mac needs to install the root certificate into certificate storage to be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering). This action is performed automatically in most cases as you run the app for the first time, but users of Gecko-based browsers (Firefox, Waterfox etc.) who have a master password set up for their browser may be required to take additional steps (because these browsers use their own certificate storage instead of the system one). They need to either enter the master password when prompted (to grant AdGuard access to the certificate storage) or manually install the certificate. -如何在基于 Firefox 的浏览器中手动安装证书： +To manually install the certificate into Firefox-like browser: - 1. 打开「*首选项*」。 + 1. Open *Preferences* - 2. 转至「*隐私和安全*」→「*证书*」。 + 2. Go to *Privacy & Security* → *Certificates* - 3. 点击「*查看证书*」。 + 3. Click *View Certificates* - 4. 转到「*授权*」选项卡并单击「*导入..*」按钮。 + 4. Navigate to the *Authorities* tab and click the *Import...* button - 5. 选择 `/Library/Application Support/AdGuard Software/com.adguard.mac.adguard/AdguardCore/Adguard Personal CA.cer` 文件，或使用基于 Chromium 的浏览器（如 Google Chrome 或新 Edge）并在 AdGuard 中运行 HTTPS 过滤，从 http://local.adguard.org/cert 下载该文件。 + 5. Select file `/Library/Application Support/AdGuard Software/com.adguard.mac.adguard/AdguardCore/Adguard Personal CA.cer` or just download it from http://local.adguard.org/cert using a Chromium-based browser (e.g Google Chrome or new Edge) and with a HTTPS-filtering running in AdGuard -不同的基于 Gecko 的浏览器可能需要不同的操作，但 `AdGuard Personal CA.cer ` 文件的基本流程和路径是相同的。 +Exact actions required for different Gecko-based browsers may vary, but the general sequence and the path to `AdGuard Personal CA.cer` file will be the same. -附注：[Setapp 应用程序版本](https://setapp.com/apps/adguard)的文件路径如下：`/Library/Application Support/com.adguard.mac.adguard-setapp/AdguardCore/Adguard Personal CA.cer` +P.S.: For [Setapp application version](https://setapp.com/apps/adguard) the file path is the following: `/Library/Application Support/com.adguard.mac.adguard-setapp/AdguardCore/Adguard Personal CA.cer` diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index d18842d0502..9350814f208 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -1,5 +1,5 @@ --- -title: 保护邮件活动和 AdGuard +title: Protect Mail Activity and AdGuard sidebar_position: 8 --- @@ -9,34 +9,34 @@ sidebar_position: 8 ::: -## 简述 +## In a nutshell Apple 邮件应用现于下载邮件图像时使用代理以隐藏用户的 IP 地址。 -![邮件隐私保护](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_protectMailActivity.jpg) +![Mail privacy protection](https://cdn.adtidy.org/content/kb/ad_blocker/mac/mac_protectMailActivity.jpg) -但如有启动的 VPN 连接，保护邮件活动功能将无法工作。 因其视 AdGuard 为 VPN，所以它不会自动预载图像。 +However, it won't work if there's an active VPN connection. 因其视 AdGuard 为 VPN，所以它不会自动预载图像。 -Apple [在此](https://support.apple.com/HT212797)解释此问题。 +Apple explains this issue [here](https://support.apple.com/HT212797). -## 详述 +## 更详细的说明 -现在，Mac 版 AdGuard 使用基于网络扩展 API 的 macOS 内置的 Socket 过滤。 这种新的漏洞百出的机制取代了老式的内核扩展。 在过去的一年半内，我们向 Apple 报告了超过 20 个（！）关于其新过滤方式的错误。 +现在 Mac 版 AdGuard 使用基于网络扩展 API 的 macOS 内置的 Socket 过滤。 这种新的漏洞百出的机制取代了老式的内核扩展。 在过去的一年半内，我们向 Apple 报告了超过 20 个（！）关于其新过滤方式的错误。 -网络扩展 API 有一个类似 VPN 的配置，其中包含一个类似路由的条目列表。 在 Big Sur 上，AdGuard 使用了「分离隧道」规则，以避免创建「默认路由」规则，因为它会给 Big Sur 早期版本带来问题。 这些问题已在 Monterey 中得到解决，因此没有什么能阻止「默认路由」规则。 +网络扩展 API 有一个类似 VPN 的配置，其中包含一个类似路由的条目列表。 On Big Sur, AdGuard used "split-tunnel" rules to avoid creating the "default route" rule because it causes problems on early Big Sur releases. These problems were solved in Monterey so nothing prevents us from using the "default route" rule. -在 Monterey 上，推出了 iCloud 专用代理。 邮件应用程序的隐私功能也使用专用代理服务器。 +在 Monterey 上，推出了 iCloud 专用代理。 Privacy features of Mail.app also use Private Relay servers. -因此，AdGuard 无法与 iCloud 专用代理和邮件应用程序的隐私功能一起使用： +As a consequence, AdGuard can't work together with iCloud Private Relay and Mail app privacy features: -1. iCloud 专用代理应用于库级别的连接，在连接到达 AdGuard 运行的套接字级别之前。 -2. iCloud 专用代理使用 QUIC，AdGuard 无法对其进行过滤，因为 HTTP/3 过滤功能尚不可用。 -3. 因此，AdGuard 会阻止 QUIC，包括 iCloud 专用代理的流量，否则就无法拦截广告。 -4. 当用户使用 iCloud 专用代理，将 AdGuard 切换到「分离隧道」模式时，就无法在 Safari 中打开网站。 -5. 要在 Monterey 上解决这个问题，我们应用「默认路由」规则。 专用代理检测到该规则时，功能将自动禁用。 因此，AdGuard 可以在 Monterey 上无缝运行，但 iCloud 专用代理会被禁用。 +1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. +2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. +4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. +5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. -`network.extension.monterey.force.split.tunnel` 恢复了 Big Sur 行为，但由于（3）和（4）的原因，该选项会中断网站访问权限。 我们努力寻找能够解决这个问题的办法。 一种可能的解决方案是实施 HTTP/3 过滤。 +`network.extension.monterey.force.split.tunnel` restores the "Big Sur" behavior, but this option may break access to websites due to (3) and (4). We keep searching for a solution to this issue. One of the options is implementing HTTP/3 filtering. -## 建议的解决方案 +## Recommended solution -此时，我们建议使用更传统的 VPN 服务，如 [AdGuard VPN](https://adguard-vpn.com/)，而不是较新的 Apple 隐私功能。 +At this point, we recommend using a more traditional VPN service, such as [AdGuard VPN](https://adguard-vpn.com/), instead of the newer Apple privacy features. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md index a644237c875..9459b018bc5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protection-cannot-be-enabled.md @@ -1,5 +1,5 @@ --- -title: 无法启用保护 +title: Protection cannot be enabled sidebar_position: 2 --- @@ -9,14 +9,14 @@ sidebar_position: 2 ::: -如果由于某种原因无法启用 AdGuard 保护，请执行以下操作： +If AdGuard Protection cannot be enabled for some reason, perform the following steps: -1. 单击菜单栏上的 AdGuard 图标并转到「*高级*」→「*重置设置...*」→「*退出 AdGuard...*」。 +1. Click the AdGuard icon at the menu bar and go to *Advanced* → *Reset settings...* → *Quit AdGuard...* -2. 在 Spotlight 搜索工具中，键入‘终端’，输入并执行 `sudo rm -R /Library/Application\ Support/com.adguard.adguard` 命令。 +2. In the Spotlight Search, type Terminal, enter `sudo rm -R /Library/Application\ Support/com.adguard.adguard` and execute. -3. 重启计算机。 +3. Restart your computer. -4. 再次打开终端，输入并执行 `ls -al /Library/StagedExtensions/Library/Application\ Support/com.adguard.adguard/` 命令。 用户将收到以下信息：`No such file or directory`。 +4. Open the Terminal again, type `ls -al /Library/StagedExtensions/Library/Application\ Support/com.adguard.adguard/` and execute. You should receive the following: `No such file or directory`. -5. 启动 AdGuard 并按提示输入登录信息。 +5. Start AdGuard and enter your login information when prompted. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md index f0b3ebf1c47..da10ff0dce0 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/screen-time-issues.md @@ -1,5 +1,5 @@ --- -title: 屏幕时间兼容性问题 +title: Incompatibility with Screen Time sidebar_position: 11 --- @@ -9,10 +9,10 @@ sidebar_position: 11 ::: -启用 AdGuard 时，在「屏幕时间」中启用内容限制可能会导致网页加载问题。 检查「内容限制」是否已激活： +If you have Content Restrictions enabled in _Screen Time_ while AdGuard is on, you may experience problems loading web pages. To check if Content Restrictions are active: -1. 转到系统设置 →「屏幕时间」→「内容和隐私」→「内容限制」 +1. Go to System Settings → Screen Time → Content & Privacy → Content Restrictions -2. 检查「访问网页内容」设置是否设为「_限制成人网站_」 +2. Check if the setting for Access to Web Content is set to _Limit Adult Websites_ -如果设置已启用，网页将无法加载。 要继续使用 AdGuard，请在「屏幕时间」中禁用「内容与隐私」，然后重新启动系统。 +If this setting is on, pages won’t load. To continue using AdGuard, disable Content & Privacy in Screen Time, and then restart the system. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/tor-filtering.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/tor-filtering.md index 1f3a24d114a..79782d54856 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/tor-filtering.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/tor-filtering.md @@ -27,4 +27,4 @@ Public Key Pinning（公钥固定）是一种安全措施，允许网站确保 为了应用更改，请重新开启 Tor 浏览器。 -如果您手动改变设置，Tor 浏览器过滤将被停止。 +If you manually change these settings, Tor filtering will be stopped. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md index b491f8aeb0f..35c950c2233 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-safari/solving-problems/logs.md @@ -21,10 +21,10 @@ sidebar_position: 4 :::note -AdGuard 致力于保护用户的个人隐私。 我们严格遵守[隐私政策](https://adguard.com/privacy/safari.html)，不收集用户的私人信息。 请注意：在将您的日志记录发送给客户支持团队之前，请检查文件，因为它会包含您不想分享的附加信息。 如果其中包含此类个人信息，我们建议您先将其删除。 +AdGuard is committed to protecting your privacy. We strictly follow our [Privacy Policy](https://adguard.com/privacy/safari.html) and do not collect any private information about users. Before sending your logs to the support team, please review the file as it may contain additional information that you don’t want to share. If it contains such personal information, we recommend that you delete it first. ::: -1. 打开[适用于 Safari 的 AdGuard GitHub 存储库](https://github.com/AdguardTeam/AdGuardForSafari/issues)，然后点击「_New issue_」。 -2. 将日志记录文件发送至 devteam@adguard.com。 包括错误发生的时间并附加指向您的问题或其编号的链接（它在标题旁边显示为 #number）。 - 或者，您可以将日志文件上传到 Google Drive 并将其发送至 devteam@adguard.com。 将文件链接添加到您的 GitHub 问题. +1. Open the [AdGuard for Safari GitHub repo](https://github.com/AdguardTeam/AdGuardForSafari/issues) and click _New issue_. +2. Send the log file to devteam@adguard.com. 包括错误发生的时间并附加指向您的问题或其编号的链接（它在标题旁边显示为 #number）。 + 或者，您可以将日志文件上传到 Google Drive 并将其发送至 devteam@adguard.com。 Add the file link to your GitHub issue. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index ba92aa3ad6c..0fd9d34a537 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 386f29cd9ee..db0b6d34c1b 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard 可作为[用户脚本管理器](/general/userscripts)以显著扩展网 此自定义扩展设计用于对抗重新插入已拦截广告技术，即所谓的广告拦截器规避/广告重新注入。 两者都是受广告商欢迎的先进的反广告拦截方式。 -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra 是一个改变页面工作方式的小程序。它改变页面的工作方式，使得网站更难以使用上述方法绕过拦截器。 **AdGuard 弹窗拦截器** -用户在查看网页时此扩展防止弹出窗口被打开。 一些弹窗被认为是有用的，它们可能包含网站管理设置或点击链接时显示附加参考信息。 这就是用户可按需关闭拦截器的原因。 此扩展程序也不适用于那些已添加到 AdGuard 排除项列表的网站。 默认情况下其是关闭的，但用户可以在应用程序设置内打开它。 You will find more detailed information about this extension in our Knowledge Base. +用户在查看网页时此扩展防止弹出窗口被打开。 一些弹窗被认为是有用的，它们可能包含网站管理设置或点击链接时显示附加参考信息。 这就是用户可按需关闭拦截器的原因。 此扩展程序也不适用于那些已添加到 AdGuard 排除项列表的网站。 默认情况下其是关闭的，但用户可以在应用程序设置内打开它。 用户可以在我们的知识库内找到更多关于此扩展到信息。 **Web of Trust**（信任网站） @@ -41,7 +41,7 @@ Web of Trust 让用户根据自己的意见查看每个网站的声誉。 网站 ### 网络 -倒数第二个模块专用于网络过滤，用户可以在此处找到附加的网络相关选项。 Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. 这些重要的额外预防措施可更好地过滤您的网络空间。 当前大部分网站使用 HTTPS，广告亦是如此。 From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +倒数第二个模块专用于网络过滤，用户可以在此处找到附加的网络相关选项。 其中两项默认启动：「开启流量过滤」和「过滤 HTTPS 协议」。 这些重要的额外预防措施可更好地过滤您的网络空间。 当前大部分网站使用 HTTPS，广告亦是如此。 众多网站，如 youtube.com，facebook.com 和 twitter.com，不进行 HTTPS 过滤是无法移除广告的。 因此除非用户有充分的理由不开启它，否则请保持「过滤 HTTPS 协议」功能的开启状态。 ![网络设置 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 022a483020c..244e95e8f0e 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -15,7 +15,7 @@ sidebar_position: 2 ### 常规设置 -用户可以在此处设置语言和主题（暗色或亮色），开启 AdGuard 随系统启动运行，静寂自动更新，选择更新通道和过滤器更新检查时间间隔。 Also Settings is the place to go if AdGuard for Windows is not working properly and the support team asked you to [collect _Debug logs_](/adguard-for-windows/solving-problems/adguard-logs.md). +用户可以在此处设置语言和主题（暗色或亮色），开启 AdGuard 随系统启动运行，静寂自动更新，选择更新通道和过滤器更新检查时间间隔。 如果 Windows 版 AdGuard 无法正常工作，而支持团队要求用户[收集「调试日志」](/adguard-for-windows/solving-problems/adguard-logs.md)，那么「设置」也是要查看的地方。 ![高级设置 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/advanced-settings.png) @@ -80,7 +80,7 @@ sidebar_position: 2 此模块检查浏览器打开的网页内容，过滤儿童不宜的内容：成人图像和文字、粗俗语言、暴力、毒品宣传等。 家长控制设置受密码保护，孩子无法绕过限制。 此模块不仅拦截对不良网站的指向，也可从搜索结果中移除儿童不宜的链接。 -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. 用户也可以选中「阻止下载可执行文件」以防止儿童在计算机上下载和安装软件。 「家长控制」模块有多个选项：用户可以选择「家长控制」保护特定的 Windows 用户，设置密码保护 AdGuard 设置以防更改。 +在家长控制模块，用户可以开启「安全搜索」，管理「黑名单」和「白名单」以自定义此选项的工作方式。 用户也可以选中「阻止下载可执行文件」以防止儿童在计算机上下载和安装软件。 「家长控制」模块有多个选项：用户可以选择「家长控制」保护特定的 Windows 用户，设置密码保护 AdGuard 设置以防更改。 ![家长控制 \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index 95fbfe320ac..d0215a0417f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ sidebar_position: 2 如您想要在 Microsoft Windows 操作系统的电脑或笔记本上使用 AdGuard ，您要下载安装包并启用安装程序。 请执行以下步骤： -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. 在地址栏输入 [AdGuard 官网](http://adguard.com)，在[打开的页面](https://adguard.com/download.html?auto=1)中点击「*下载*」。 ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -49,13 +49,13 @@ sidebar_position: 2 Congratulations! You have successfully installed AdGuard on your computer. On the screen you will see the main window where you can change the app’s settings. -## 如何卸载 Windows 版 AdGuard {#uninstall} +## 如何卸载 AdGuard Windows版 {#uninstall} ### 常规方式 If you need to uninstall or reinstall AdGuard, do the following: -- Microsoft Windows 10&11：点击「*开始菜单*」并选择「*设置*」。 在弹出的窗口里点击「*应用*」。 在「*应用程序*」窗口中，从左边的列表中选择「*应用和功能*」。 在已安装的应用程序列表中选择「*AdGuard*」，并点击「*卸载*」。 在弹出的对话框确认「*卸载*」。 +- Microsoft Windows 10&11：点击「*开始菜单*」并选择「*设置*」。 在弹出的视窗里点击「*应用*」。 在「*应用程序*」窗口中，从左边的列表中选择「*应用和功能*」。 在已安装的应用程序列表中选择「*AdGuard*」，并点击「*卸载*」。 在弹出的对话框确认「*卸载*」。 ![Windows 10 & 11 uninstallation *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/win10-uninstall.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index b9afcaf8049..7999b75a345 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard logs +title: 如何收集 AdGuard 日志记录 sidebar_position: 3 --- @@ -15,7 +15,7 @@ sidebar_position: 3 ::: -要分析和诊断可能潜在的问题，AdGuard 技术人员可能需要 AdGuard 日志记录文件。 These files contain records about errors and other events that occur with the software. 下面是简短的说明，描述获取日志文件的方法，并在必要时将其发送给支持服务。 +要分析和诊断可能潜在的问题，AdGuard 技术人员可能需要 AdGuard 日志记录文件。 这些文件包含本软件发生的错误记录和其它事件。 下面是简短的说明，描述获取日志文件的方法，并在必要时将其发送给支持服务。 :::note @@ -25,7 +25,7 @@ AdGuard 致力于保护用户的个人隐私。 我们严格遵守我们的[隐 ### 调试日志 {#debug-logs} -1. 打开 AdGuard 设置。 Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. 打开 AdGuard 设置。 转到「*常规设置*」部分，下滚至界面底部并切换「*日志级别*」至「*调试*」。 ![调试级别日志 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard 致力于保护用户的个人隐私。 我们严格遵守我们的[隐 我们强烈建议用户记录问题重现的确切时间：这将有助于我们的支持团队找到相关日志条目并更快地解决问题。 -1. Export the collected logs using the *Export Logs* button. +1. 请使用「*导出日志*」按钮以导出记录日志。 ![导出日志 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) 将存档保存到任意文件夹。 -1. **Important**: after exporting the logs, set the logging level back to *Default*. 「*调试*」日志记录级别会降低应用程序的运行速度。 +1. **注意**：导出日志后，将日志记录级别设置为「*标准*」。 「*调试*」日志记录级别会降低应用程序的运行速度。 1. 发送存档给 AdGuard 支持团队 **support@adguard.com** 时，请描述问题和出现问题的时间。 @@ -65,7 +65,7 @@ AdGuard 致力于保护用户的个人隐私。 我们严格遵守我们的[隐 我们强烈建议用户记录问题重现的确切时间：这将有助于我们的支持团队找到相关日志条目并更快地解决问题。 -1. Export the collected logs using the *Export Logs* button. +1. 请使用「*导出日志*」按钮以导出记录日志。 ![导出日志 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 65fc17297c1..7fe3ad779b6 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ sidebar_position: 6 ### 错误 5：拒绝访问 {#error-5} -This error message appears when required permissions haven't been granted. AdGuard 安装程序没有正确完成安装过程所需的权限可能有多种不同的原因。 用户可以尝试以下步骤： +这个错误发生在权限设置有问题的时候。 AdGuard 安装程序没有正确完成安装过程所需的权限可能有多种不同的原因。 用户可以尝试以下步骤： -- Temporarily disable your antivirus. 部分防病毒软件可能会干扰安装，具体取决于其设置的严格程度。 +- 暂时禁用防病毒软件。 部分防病毒软件可能会干扰安装，具体取决于其设置的严格程度。 - 选择不同的安装文件夹。 当前安装文件夹可能有一些访问限制。 用户还要确保没有选择外部驱动器、虚拟驱动器等。 @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. AdGua ### 错误 112：磁盘已满；错误 1632：临时文件夹已满或无法访问 {#error-112} -这是两个不同的错误，但解决方案非常相似。 As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. 有几种方法可以尝试解决问题： +这是两个不同的错误，但解决方案非常相似。 顾名思义，AdGuard 安装程序没有找到足够的磁盘空间来完成安装。 有几种方法可以尝试解决问题： - 从尝试安装 AdGuard 的驱动器中卸载一些程序或删除不需要的文件。 -- 下载、安装并运行 [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/)，这是一款由 Malwarebytes 提供的免费软件。 It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. 它有助于清理出磁盘空间。 +- 下载、安装并运行 [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/)，这是一款由 Malwarebytes 提供的免费软件。 软件能够清除系统中因卸载程序错误而产生的各种额外“遗留”文件。 它有助于清理出磁盘空间。 - 重新启动计算机。 有时候临时文件会占用大量磁盘空间，重启电脑是清除临时文件最可靠的方法。 ### 错误 1601：无法访问 Windows Installer {#error-1601} -You could say this is a particular subcategory of Error 1603. 解决方案是相似的： +可以说，这是错误 1603 的一个特殊子案例。 解决方案是相似的： - 启动并重新注册 Microsoft Installer 服务。 这需要如下操作： @@ -75,7 +75,7 @@ You could say this is a particular subcategory of Error 1603. 解决方案是相 - 重启电脑并重新开始安装。 当您重启计算机后，所有正在进行的进程都将停止，包括所有运行中的安装程序。 -- Don't make multiple clicks on the installer even if it doesn't start right away. 有时候显示安装界面可能会需要几秒钟。 +- 即使安装没有立即开始，也不要多次点击安装程序。 有时候显示安装界面可能会需要几秒钟。 ### 错误 1638：已安装此软件的另一个版本 {#error-1638} @@ -83,14 +83,14 @@ You could say this is a particular subcategory of Error 1603. 解决方案是相 - 检查 AdGuard 是否已安装在计算机上。 您可以通过按「*Win*」键并输入 ***AdGuard*** 来完成。 -- Maybe there're some leftover files from a previous AdGuard installation. 使用我们的专用[卸载工具](../../installation#advanced)卸载 AdGuard，然后重复安装。 +- 也许有一些以前安装 AdGuard 时遗留下来的文件。 使用我们的专用[卸载工具](../../installation#advanced)卸载 AdGuard，然后重复安装。 ### 其他错误 {#other} 如果您遇到了上面没有列出的错误，请与支持团队联系，我们帮您解决问题。 与我们联系以前，请收集日志文件。 执行以下步骤： -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- 找到并保存 **AdGuard 安装日志**，详细步骤见[这篇文章](../installation-logs)。 -- Find and save to disk the **Event Viewer** logs. [这篇文章](../system-logs)中有操作步骤。 +- 找到并保存**事件查看器**中有关磁盘的日志。 [这篇文章](../system-logs)中有操作步骤。 - 请将前两个步骤中得到的文件通过电子邮件发送到我们的支持团队 **support@adguard.com**，并在邮件正文中描述您的问题。 我们的技术支持团队将尽快回复您。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index b638f40678b..0304785b4de 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ sidebar_position: 9 Windows 版 AdGuard 让用户指定 DNS 服务器地址来解决查询，而不使用 ISP 提供的系统 DNS 服务器（如果未在系统中更改设置）。 使用非默认 DNS 服务器可以保护 DNS 流量不被互联网服务提供商拦截。 此外，选择一个进行加密和/或过滤的 DNS 服务器后，用户还可以获得另一层保护，防止恶意行为和恼人的广告。 -许多 Windows 版 AdGuard 的用户都赞赏 DNS 保护功能。 But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. 在本文中，我们将解释为什么会发生这种情况以及如何避免它。 +许多 Windows 版 AdGuard 的用户都赞赏 DNS 保护功能。 但有些用户遇到以下问题：https://ipleak.net/ 等网站的检查结果显示，有默认 DNS 服务器而不是所选的服务器处理请求。 在本文中，我们将解释为什么会发生这种情况以及如何避免它。 ## Bootstrap DNS 地址 @@ -21,7 +21,7 @@ DNS 服务器地址可以写为 IP 或域名。 在 IP 地址的情况下没有 - 转到「*高级设置*」 - 向下滚动到「*自定义 Bootstrap 地址的列表*」部分 -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- 以 IP 地址格式输入自定义引导地址（可以使用「[已知 DNS 提供商列表](https://adguard-dns.io/kb/general/dns-providers/)」） - 单击「*保存*」 ## 后备 DNS 服务器 @@ -33,7 +33,7 @@ DNS 服务器地址可以写为 IP 或域名。 在 IP 地址的情况下没有 - 转到「*高级设置*」 - 向下滚动到「*后备服务器*」部分 - 勾选「*使用自定义服务器*」 -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- 然后找到「*自定义后备服务器的列表*」部分，每行输入一个自定义后备服务器 或者 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index c2e3a48b868..f9ed9c196c2 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ sidebar_position: 8 :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +Windows 版 AdGuard 有两个运行中的进程（`Adguard.exe` 和 `AdguardSvc.exe`）。 所以用户需要为它们分别创建转储文件。 ::: ![AdGuard 进程](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -当您发送转储文件给我们的支持团队时，也请附上 AdGuard 程序日志以便我们更好的解决问题。 [Here](../adguard-logs) you can check the instructions on how to get the log file. +当您发送转储文件给我们的支持团队时，也请附上 AdGuard 程序日志以便我们更好的解决问题。 您可以[在此](../adguard-logs)检查收集日志文件的指示说明。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 744e08e4ea1..b00afc379ac 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect AdGuard installation logs +title: AdGuard 安装日志收集方式 sidebar_position: 4 --- @@ -17,7 +17,7 @@ sidebar_position: 4 如您在安装 AdGuard 期间发生问题，可以发送技术请求给我们的支持团队，但他们会要求您收集并发送 AdGuard 安装日志。 在这种情况下，您需要执行以下操作： -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. 从开始菜单选择「*运行*」命令或按按键组合「*Win + R*」。 1. 在字段内键入「*%tmp%*」点击「*确定*」。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 1c093f6477d..9f4039fcc06 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ sidebar_position: 7 如果启用，AdGuard 将阻止 Edge 浏览器中的 TCP 快速打开。 要应用设置，请重新启动浏览器。 -### Use Encrypted Client Hello +### 使用 Encrypted ClientHello -每一个加密的互联网连接都有一个未加密的部分， 就是发送的第一个数据包，包含用户要连接的服务器名称。 Encrypted ClientHello（ECH）的技术能够解决该问题，成功加密最后一位未加密的信息。 To benefit from it, enable the *Use Encrypted Client Hello* option. 本功能使用本地 DNS 代理查找域名的 ECH 配置。 If it is found, Client Hello packet will be encrypted. +每一个加密的互联网连接都有一个未加密的部分， 就是发送的第一个数据包，包含用户要连接的服务器名称。 Encrypted ClientHello（ECH）的技术能够解决该问题，成功加密最后一位未加密的信息。 要使用该功能，请启用「*使用 Encrypted ClientHello*」选项。 本功能使用本地 DNS 代理查找域名的 ECH 配置。 如果找到，将对 ClientHello 数据包进行加密。 ### 检查网站的证书透明度 @@ -73,7 +73,7 @@ sidebar_position: 7 ### 随系统启动时显示主窗口 -启用此选项可在加载系统后打开 AdGuard 主窗口。 Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +启用此选项可在加载系统后打开 AdGuard 主窗口。 请注意，本功能不影响实际过滤服务是否启动，此设置位于*「设置」→「常规设置」*中。 ### 在系统启动时启用过滤 @@ -95,7 +95,7 @@ sidebar_position: 7 ### 启用 HAR 写入 -此选项**仅用于调试目的**。 Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. 这个文件可以用 Fiddler 应用程序分析。 注意，这可能会显著降低网页加载速度。 +此选项**仅用于调试目的**。 如果勾选复选标记，AdGuard 将创建一个文件，其中包含 HAR 1.2 格式的所有已过滤 HTTP 请求的信息。 这个文件可以用 Fiddler 应用程序分析。 注意，这可能会显著降低网页加载速度。 ### 在普通的 HTTP 请求中添加额外的空间 @@ -115,7 +115,7 @@ Host: example.org` 指定 TCP 数据包碎片的大小，避免深度包检测。 此选项仅影响安全（HTTPS）流量。 -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +如果开启该选项，AdGuard 将初始 TLS 数据包（ClientHello 数据包）分成两部分：第一部分包含指定的长度，第二部分包含剩余的长度，直到整个初始 TLS 数据包的长度。 有效值：1–1500。 如果指定无效大小，将使用系统选择的数值。 此选项仅在启用隐身模式的「*保护免受 DPI 影响*」选项时被应用。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 9664df16c00..2b85921eead 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -1,5 +1,5 @@ --- -title: How to collect Windows system logs +title: 如何收集 Windows 系统日志 sidebar_position: 5 --- @@ -15,7 +15,7 @@ sidebar_position: 5 ::: -要分析和诊断可能潜在的问题，AdGuard 支持服务可能需要 Windows 系统日志文件。 Windows event logs contain records about all errors that occur with the installed software, including AdGuard. 下面我们简述获取日志文件的方式并在需要的时候反送给我们的支持服务。 +要分析和诊断可能潜在的问题，AdGuard 支持服务可能需要 Windows 系统日志文件。 Windows 事件日志记录着所有已安装软件发生的错误，包括 AdGuard 在内。 下面我们简述获取日志文件的方式并在需要的时候反送给我们的支持服务。 1. 按「*Win + R*」 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 7f01aff22a6..a74299ad2ae 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ sidebar_position: 1 ::: -要过滤网络流量，AdGuard 会使用网络驱动程序。 有两个设置选项：TDI 驱动程序和 WFP 驱动程序。 While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. 这些问题和随后的错误在每种情况下可能会有很大不同。 +要过滤网络流量，AdGuard 会使用网络驱动程序。 有两个设置选项：TDI 驱动程序和 WFP 驱动程序。 WFP 驱动程序通常是首选且默认情况下，所有较新的 Windows 操作系统版本（Windows 8 及更新版本）都是开启的，但它可能会导致兼容性问题，尤其是与某些防病毒软件。 这些问题和随后的错误在每种情况下可能会有很大不同。 如果您遇到怀疑可能由此引起的问题，可以随时切换到较旧但更稳定的 TDI 网络驱动程序。 具体操作： 1. 转到*「设置」→「网络」*。 -2. Disable the WFP driver as it’s done in this picture: +2. 按照下图所示禁用 WFP 驱动程序： ![WFP 驱动程序 *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/account/features.md index 97412e07425..dd9d8a33142 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ sidebar_position: 2 ## 联系支持 -支持标签包含有帮助用户解决问题，查找 AdGuard 产品相关问题答案的有用链接。 They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +支持标签包含有帮助用户解决问题，查找 AdGuard 产品相关问题答案的有用链接。 它们分为六个部分：常见问题解答，发送错误报告/功能请求，报告拦截错误，联系支持，知识库和讨论。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 53a37eaa5ba..c890ec43a89 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ sidebar_position: 2 - **实验性过滤器**，此过滤器设计用于在将某些有风险的过滤规则添加到基本过滤器之前对其进行测试。 如果这些规则执行没有任何问题，它们会被添加到主过滤器中。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **移动广告过滤器**拦截移动设备上的广告。 包含所有已知的移动广告网络。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS 过滤器** — 此过滤器由其他几个过滤器 (AdGuard 基础过滤器、社交媒体过滤器、防跟踪保护过滤器、移动广告过滤器、EasyList 和 EasyPrivacy) 组成，并经过简化，以便更好地与 DNS 级别的广告拦截兼容。 [AdGuard DNS](https://adguard-dns.io/kb) 服务器使用此过滤器来拦截广告和跟踪器。 [查看规则](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard 过滤器政策 -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. 阅读全文 [AdGuard 过滤政策](../filter-policy)了解详细信息。 +我们的过滤器政策定义在过滤器中添加和删除的规则，以及 AdGuard 过滤器应该拦截和不应该拦截的内容的规则。 阅读全文 [AdGuard 过滤政策](../filter-policy)了解详细信息。 ## 为 AdGuard 过滤器做贡献 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index 4baa00928b7..71f93efef31 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:-----------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:-----------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:-----------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:-----------------------:|:--------------------------:|:-----------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:-----------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:-----------------------:|:--------------------------:|:-----------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:-----------------------:|:--------------------------:|:-----------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------:|:--------------------------:|:-----------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------:|:--------------------------:|:-----------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:-----------------------:|:--------------------------:|:-----------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **限制** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:-----------------------:|:--------------------------:|:-----------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard iOS版][ios-app] | [AdGuard Safari版][ext-saf] | [AdGuard 内容拦截器][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:-----------------------:|:--------------------------:|:-----------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,32 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" -[ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard Safari版" -[ext-saf]: #what-product "AdGuard for Safari" -[and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index f441bac20e3..9ac23833eb3 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard 广告拦截的过滤器包含以下过滤器： - AdGuard 基础过滤器 - AdGuard 移动广告过滤器 - 按语言原则划分的地区过滤器，包括中文、荷兰语、法语、德语、日语、俄语、西班牙语/葡萄牙语、土耳其语和乌克兰语 -- AdGuard Quick Fixes filter ### 过滤器的用途 - **基础过滤器**旨在拦截英语网站和没有单独过滤器的网站上的广告。 它还包含适用于所有网站（无论网站的语言）的一般过滤规则。 - **移动广告过滤器**拦截移动版网站和移动应用程序中的广告。 没有基于语言的细分。 - **地区过滤器**遵循与**基础过滤器**相同的政策，但仅限于特定语言的网站。 -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. 广告拦截过滤器的主要目标在于拦截网站、应用程序和某些可以从互联网上加载广告的设备上的所有类型广告。广告类型如下： diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/browsing-security.md index 0784f312254..5363522285f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 3bf0770abeb..6f87f95d87f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -当前大部分网站使用 HTTPS，广告亦是如此。 Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +当前大部分网站使用 HTTPS，广告亦是如此。 Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/license/what-is.md index e85ce61bb97..db44d4dd487 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: 什么是 AdGuard 许可证密钥? sidebar_position: 1 --- @@ -12,7 +12,7 @@ sidebar_position: 1 - **一年订阅**：许可证每年自动更新，也可手动续订。 - 个人（最多支持 3 台设备） - 家庭（最多支持 9 台设备） -- **Lifetime** — these licenses are perpetual +- **终身**：许可证没有时间限制。 - 个人（最多支持 3 台设备） - 家庭（最多支持 9 台设备） diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 9fa43d5d574..7b0dac51553 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ WebRTC（网络实时通信）是一种允许在浏览器和应用程序之间 ### 拦截 Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. 启用此设置后，AdGuard 将阻止浏览器检测允许 Flash 显示内容的组件（例如插件和 ActiveXObject 对象）。 这实际上意味着浏览器无法支持 Flash。 +Flash Player 插件越来越容易受到如病毒和黑客之类的在线威胁的影响；它还可能会显著影响网站的加载时间。 启用此设置后，AdGuard 将阻止浏览器检测允许 Flash 显示内容的组件（例如插件和 ActiveXObject 对象）。 这实际上意味着浏览器无法支持 Flash。 ### 拦截 Java {#java} @@ -89,13 +89,13 @@ The Flash Player plugin has become increasingly vulnerable to such online threat ### 隐藏第三方 Referer {#referer} -Referrer 是浏览器发送请求到服务器时所用的 HTTP 头部。 其包含请求源的 URL。 当您在各网页间导航时，Referer 会保存初始页的 URL。 托管目标网页的服务器通常具备解析 Referrer 的软件，并从中提取各种信息。 开启「*隐藏第三方 Referrer*」选项后，通过更改 HTTP 头部使第三方网站不可视当前网站。 +Referrer 是浏览器发送请求到服务器时所用的 HTTP 头部。 其包含请求源的 URL。 当您在各网页间导航时，Referer ​ ​会保存初始页的 URL。 托管目标网页的服务器通常具备解析 Referrer 的软件，并从中提取各种信息。 开启「*隐藏第三方 Referrer*」选项后，通过更改 HTTP 头部使第三方网站不可视当前网站。 -您也可在 *Referer* 字段输入任意值以设置 Referer。 要使用默认 Referer，置空此字段即可。 +您也可在 *Referer* ​ ​字段输入任意值以设置 Referer。 要使用默认 Referer，置空此字段即可。 请注意，要过滤流量，AdGuard 应用会“劫持”浏览器到服务器的请求。 对广告，跟踪和钓鱼网站的请求可在发送其请求到服务器之前更改或完全拦截。 「*隐藏第三方 Referer*」也是如此：AdGuard 拦截 HTTP(S) 请求，在启用该选项后软件删除或更改 Referer 标头。 但是，只有在这些请求“离开”浏览器后软件才开始拦截。 这意味着，如果在浏览器内监视 Referer（例如，借助 Chrome 浏览器的开发者工具），用户将看到原来的 Referer，因为请求尚未到达 AdGuard。 您可以使用 [Fiddler](https://www.telerik.com/fiddler) 等软件来确保 Referer 被正确更改。 -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. 它将立即更改 Referer，因此开发工具将为用户的请求显示所需的 Referer。 +相反，由于所有浏览器扩展的性质，AdGuard 浏览器扩展在浏览器“内部”运行。 它将立即更改 Referer，因此开发工具将为用户的请求显示所需的 Referer。 ### 隐藏 User-Agent {#useragent} @@ -120,9 +120,3 @@ On the other hand, due to the nature of all browser extensions, AdGuard Browser AdGuard 可以修改传出数据包，使客户端不受 DPI 拦截标准限制。 这意味着通过启用此选项，用户可以访问他们想要的内容。 目前还不能绕过所有 DPI 系统，但我们不断努力改进。 Windows 版 AdGuard、Mac 版 AdGuard 和 Android 版 AdGuard 已经有「保护免受 DPI 影响」功能。 - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/userscripts.md index 1514007530b..785f78c6a17 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. 用户脚本修改或扩展一个或多个网站的功能。 许多 AdGuard 用户已经熟悉 AdGuard 助手、弹窗拦截器和 AdGuard Extra 等用户脚本。 +用户脚本（我们也称之为“扩展”）实质上是用 JavaScript 编写的小程序。 用户脚本修改或扩展一个或多个网站的功能。 许多 AdGuard 用户已经熟悉 AdGuard 助手、弹窗拦截器和 AdGuard Extra 等用户脚本。 :::note 支持的应用程序 @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 0e5da2bf04e..ea979bc38e5 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: 收集 HAR 文件的方式 sidebar_position: 1 --- @@ -18,7 +18,7 @@ HAR 文件可帮助我们的技术支持团队解决复杂的问题。 为了创 1. 点击「**Network**」标签。 -1. 找到 Network（网络）标签中的左上角的圆形按钮，并确认它处于红色录音模式。 如果其为灰色，则请点击它使其变为红色以开始录制。 +1. 找到 Network 标签中的左上角的圆形按钮，并确认它处于红色录音模式。 如果是灰色的，请您单击使其变为红色的，并开始录音。 1. 使用「**Clear**」按钮（记录按钮旁边带有一条线的圆圈按钮）以清除所有之前的活动。 @@ -45,7 +45,7 @@ HAR 文件可帮助我们的技术支持团队解决复杂的问题。 为了创 1. 点击「**Network**」标签。 -1. 找到 Network（网络）标签中的左上角的圆形按钮，并确认它处于红色录音模式。 如果其为灰色，则请点击它使其变为红色以开始录制。 +1. 找到 Network 标签中的左上角的圆形按钮，并确认它处于红色录音模式。 如果是灰色的，请您单击使其变为红色的，并开始录音。 1. 使用「**Clear**」按钮（记录按钮旁边带有一条线的圆圈按钮）以清除所有之前的活动。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 3cfbedd3ac3..0b744e06de9 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ sidebar_position: 4 ### 如何描述错误 -请您提供尽量多的细节，这将使我们更容易重现该错误，然后着手修复它。 Here’s what we expect a bug report to include: +请您提供尽量多的细节，这将使我们更容易重现该错误，然后着手修复它。 因此，请大家在上报错误时参考以下模版： - 应用程序版本 - 操作系统版本 @@ -28,7 +28,7 @@ sidebar_position: 4 ### 如何收集日志记录 -Read about collecting logs in dedicated articles for each platform. +请在描述相应操作系统的文章上了解如何收集日志记录。 ## 为错误报告或功能请求投票 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index e60299fd2a6..8ff8ece6510 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ sidebar_position: 5 Windows 可以截取整个屏幕并将截图复制到剪贴板。 -To take a screenshot of an active window, use the following shortcut keys: +要获取活动窗口的屏幕截图，请使用以下组合： - **同时按住 *Alt* 和 *PrtScn* (或在某些笔记本电脑上按 *Fn + Alt + PrtScn* )** -To take a screenshot of a specific area, use the following shortcut keys: +要获取活动窗口的屏幕截图，请使用以下组合： - ***按住 ***Win + Shift + S****** -截屏后，它将保存在剪贴板中。 在大多数情况下，用户可以使用 *Ctrl + V* 按钮组合将其粘贴到当前正在编辑的文档中。 另外，如果您需要将屏幕截图保存到文件中，则应打开标准的 Paint 程序（或任何其他可以处理图像的应用程序）。 Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +截屏后，它将保存在剪贴板中。 在大多数情况下，用户可以使用 *Ctrl + V* 按钮组合将其粘贴到当前正在编辑的文档中。 另外，如果您需要将屏幕截图保存到文件中，则应打开标准的 Paint 程序（或任何其他可以处理图像的应用程序）。 使用相同的按钮组合或单击「粘贴」按钮（通常在屏幕的左上角）将您的屏幕截图粘贴到那里，然后将其保存。 -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. 按下这些按钮后，屏幕快照将自动作为文件保存到*图片* → *屏幕截图文件夹*中。 +在 Windows 8 和 10 上可以通过 *Win + PrtScn* 组合快速捕获屏幕截图。 按下这些按钮后，屏幕快照将自动作为文件保存到*图片* → *屏幕截图文件夹*中。 还有一个专用的屏幕截图程序，称为 *Snipping Tool* (自带截图工具) ，可通过开始菜单在计算机的标准程序中找到。 该截图工具使您可以捕获桌面的任何区域或整个屏幕。 使用此程序拍摄屏幕快照后，您可以编辑图片并将其保存到计算机上的任何文件夹中。 @@ -70,26 +70,26 @@ Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* ### macOS 系统 {#mac} -To take a screenshot on Mac, use the following shortcut keys: +要获取活动窗口的屏幕截图，请使用以下组合： - ***同时按住 ***⌘Cmd + Shift + 3****** Mac 会捕获整个屏幕，并将其另存为在桌面上的文件。 -To take a screenshot of an active window, use the following shortcut keys: +要获取活动窗口的屏幕截图，请使用以下组合： - **同时按住 *⌘Cmd + Shift + 4 + 空格键*。 指针将变为相机图标。 单击窗口以捕获它。 按 Esc 按钮取消截屏** -To take a screenshot of a specific area, use the following shortcut keys: +要获取活动窗口的屏幕截图，请使用以下组合： - ***按 ***⌘ Cmd + Shift + 5******。 拖动十字准线以选择所需的区域。 释放鼠标或触控板以截取屏幕截图。然后按 Esc 按钮将其取消。 -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +要获取 *Touch Bar*（MacBook Pro）的截图，请使用以下组合： - ***按住 ***Win + Shift + S****** 您的 Mac 会捕获整个 *Touch Bar*，并在桌面上另存为文件。 -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +若您想将屏幕截图复制到剪贴板而不是保存到剪贴板，请同时按住 *Ctrl* 和上面的任意组合。 然后，您可以使用 *Cmd + V* 组合将屏幕截图（从剪贴板）粘贴到您当前正在编辑的文档或图像中。 您还可以通过使用**预览**并选择**截图**（获取所选区域，窗口或整个屏幕的）来截屏。 使用**预览**时，您可以将屏幕截图保存为 JPG、TIFF、PDF 等文件格式。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/intro.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/intro.md index 17e3d168662..ba1157f826f 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ AdGuard is one of the leaders on the market of ad-blocking software with 15+ yea ## 不仅仅是广告拦截 -AdGuard 广告拦截程序可不只能拦截广告。 它将保护用户免受在线跟踪的危害并以多种方式增强个人隐私。 根据具体的产品，AdGuard 还可以提供诸如 「DNS 过滤」来提供更全面的保护、「家长控制」以保护您的孩子免受不当内容的侵害、「过滤日志」以更好地控制您的互联网流量等等。 This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard 广告拦截程序可不只能拦截广告。 它将保护用户免受在线跟踪的危害并以多种方式增强个人隐私。 根据具体的产品，AdGuard 还可以提供诸如 「DNS 过滤」来提供更全面的保护、「家长控制」以保护您的孩子免受不当内容的侵害、「过滤日志」以更好地控制您的互联网流量等等。 该知识库包含有关所有这些内容的详细信息，请随意跳转到任何引起您兴趣的文章。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index e0c38119c2f..6d298cad3f8 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ sidebar_position: 4 当然，改进并创建拦截过滤器需要有特定的技能。 如果您已经了解如何创建规则，请直接访问我们在 GitHub 上的 [AdGuard 过滤器存储库](https://github.com/AdguardTeam/AdguardFilters)。 在那里，您可发现很多待解决的问题。每个问题都涉及某个网站上的问题，包括广告漏洞，错误报告等等。 选择任何一个问题并在注释中建议您个人的规则， AdGuard 过滤器工程师将审核您的建议。 如果正确，则您的规则会被添加到 AdGuard 过滤器中。 -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +如果您还不太熟悉或者需要复习我们的过滤规则语法，请[在我们的知识库中](/general/ad-filtering/create-own-filters)找到有关语法的基础知识。 ### 奖励 {#rewards} diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index cb8d5336699..2f6b6aee9f9 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: 如何成为翻译员/审核员 sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +如您想要加入 AdGuard 翻译员家族，首先，请前往 [Crowdin](https://crowdin.com/) 并注册/登录。 ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index e73c0c91434..0971beffc40 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ sidebar_position: 4 以下是您可以使用的一些信息来源。 -[本地化指南](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) 包含广泛的语言列表。 不同语言复数形式的数量以这种方式显示：`nplurals=2`、`nplurals=4`，依此类推。 The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[本地化指南](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) 包含广泛的语言列表。 不同语言复数形式的数量以这种方式显示：`nplurals=2`、`nplurals=4`，依此类推。 `=` 等号后的数字表示相应语言的形式数量。 此外，您还可以在 [Unicode 通用语言环境数据存储库](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules)（CLDR）中获取有关复数形式的相关信息。 CLDR 复数规则，即指十进制数字（1.5; 2.3; 100.1…）的其他词形式。但在 AdGuard 翻译中我们不使用它们。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 93387dfd296..045530a4016 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,10 +3,10 @@ title: AdGuard 翻译 sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **免责声明**：欢迎您通过给我们发邮件的方式：[translate@adguard.com](mailto:translate@adguard.com) 询问任何与 AdGuard 翻译相关的问题，或您也可以加入我们的 [Telegram 群](https://t.me/joinchat/UVYTLcHbr8JmOGIy)。 -When it comes to translations, we at AdGuard always heavily rely on volunteers. +说到翻译，我们 AdGuard 非常依赖志愿者们的无私奉献。 -We now use the [Crowdin platform](https://crowdin.com/) to manage translations of our products. So this is the place for anyone who wants to contribute to AdGuard by translating any of our products. +现在我们使用 [Crowdin 平台](https://crowdin.com/)来管理我们产品的翻译。 所以，所有想通过翻译任何喜欢的产品对 AdGuard 做贡献的志愿者们请移步 Crowdin 平台。 -If you want to be among the volunteers who help us translate AdGuard, please read the information on [how to become our translator](../become-translator) and [how we collaborate with them](../rewards). +如您想加入 AdGuard 的翻译员大家族，请阅读信息以了解更多关于[如何成为 AdGuard 翻译员](../become-translator)，以及我们[双方合作方式](../rewards)的详情。 diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index 4e2c08b59d1..a6a432a4aff 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: AdGuard Crowdin：翻译文件的优先级 sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +Crowdin上有五个主要的 AdGuard 项目，包括 [AdGuard 应用程序（AdGuard Applications）](https://crowdin.com/project/adguard-applications)、[AdGuard 网站（AdGuard Websites）](https://crowdin.com/project/adguard-websites)、[AdGuard 广告拦截程序的知识库（AdGuard Ad Blocker Knowledge base）](https://crowdin.com/project/adguard-knowledge-base)、[AdGuard VPN 知识库（AdGuard VPN Knowledge Base）](https://crowdin.com/project/adguard-vpn-knowledge-base)和 [AdGuard DNS 知识库（AdGuard DNS Knowledge Base）](https://crowdin.com/project/adguard-knowledge-bases)。 我们没有明确的用户该从哪一个文件或软件开始翻译 *AdGuard Applications* 项目的要求。 用户可以选择最喜欢的文件或软件即可。 我们只想强调几个要点： -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- 用户在 Crowdin 上完成软件的所有翻译后，我们才能在相应的应用程序里添加新翻译。 - 我们建议译员在翻译软件内容后才翻译应用商店上的描述，因为没有软件的翻译，应用商店上的说明就没有必要了。 在 *AdGuard Websites* 项目里情况有所不同。 即使没有 100% 的翻译，我们也可以添加网站的新语言版本。 但是，这取决于已经翻译的文件。 这就是我们建议您从最重要的文件开始翻译。下面是文件排序（重要的文件排在前面，次要的文件排在后面）： diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 84235fe200e..6ad4a2fd1e1 100644 --- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: 更新知识库 sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. 但是事情总是在不断变化。有时一篇文章不再反映当前的情况了。 +知识库的目的在于为所有人提供与 AdGuard 相关的包含各种主题的最新信息。 但是事情总是在不断变化。有时一篇文章不再反映当前的情况了。 这就是我们将所有知识库内容都移至 [GitHub](https://github.com/AdguardTeam/KnowledgeBase) 的原因。现在，实际上任何人都可以通过建议对现有或新文章进行编辑或翻译。 ## 如何建议更改或写新文章 {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. 如果您不熟悉该平台的使用方法，请先阅读 [GitHub 的文档](https://docs.github.com/en)。 +您可以使用上述 GitHub 的功能建议对当前文章进行更改并将新文章添加到知识库。 如果您不熟悉该平台的使用方法，请先阅读 [GitHub 的文档](https://docs.github.com/en)。 -准备就绪后，在[知识库](https://github.com/AdguardTeam/KnowledgeBase)处理。 All texts in our Knowledge Base are written in `Markdown` markup language. 在编辑或撰写文章时，请牢记这一点。 点击[链接](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)了解关于 Markdown 语法的更多信息。 +准备就绪后，在[知识库](https://github.com/AdguardTeam/KnowledgeBase)处理。 我们知识库中的所有文本都是用 `Markdown` 标记语言编写的。 在编辑或撰写文章时，请牢记这一点。 点击[链接](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax)了解关于 Markdown 语法的更多信息。 -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. 在提出修改或补充建议时，要考虑到所有文件必须符合平台的规则。 用户可以在 [ Docusaurus 指南](https://docusaurus.io/docs/category/guides)了解它们。 +知识库网站是用 Docusaurus 2 建立的，这是一个现代静态网站生成器。 在提出修改或补充建议时，要考虑到所有文件必须符合平台的规则。 用户可以在 [ Docusaurus 指南](https://docusaurus.io/docs/category/guides)了解它们。 -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +您可以把这个知识库部署在您的电脑上，以概述您建议的变化。 有关执行此操作的详细说明，可以在此知识库的 GitHub 页面上的 [README 文件](https://github.com/AdguardTeam/KnowledgeBase#readme)中找到。 ## 翻译文章 {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +知识库现有文章的翻译是在 [Crowdin 平台](https://crowdin.com/profile/adguard)上进行的。 有关翻译和使用 Crowdin 的所有详细信息，都可以在 [AdGuard 广告拦截程序知识库的专用文章](../translate/guidelines)中找到。 -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [在另一篇文章中](../translate/plural-forms)，我们详细描述了翻译具有复数形式的字符串时可能出现的困难，并就如何在 Crowdin 平台上处理这些问题给出了大量说明。 +在撰写 AdGuard 知识库文章时，您可能会遇到包含复数形式的字符串，您应该格外注意翻译。 [在另一篇文章中](../translate/plural-forms)，我们详细描述了翻译具有复数形式的字符串时可能出现的困难，并就如何在 Crowdin 平台上处理这些问题给出了大量说明。 ## 处理未解决的问题 -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. 选择您认为有吸引力的任何问题并开始处理它。 如果您有任何问题，您可以在对该问题的评论中直接提问。 +有时存在与更新知识库相关的[未完成任务](https://github.com/AdguardTeam/KnowledgeBase/issues)。 您可以帮助我们以加速完成[就像](#suggest-change)您对这个知识库提出任何其他修改建议一样。 选择您认为有吸引力的任何问题并开始处理它。 如果您有任何问题，您可以在对该问题的评论中直接提问。 diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md index 717c0484f5a..34ea1af5bc3 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/comparison-standalone.md @@ -19,8 +19,8 @@ Whereas AdGuard Browser Extension is free and easy to install, and has filters t ![Extension vs. App \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_comparison.png) -`1` — within browser restrictions and only in the browser where it is installed; +`1` – within browser restrictions and only in the browser where it is installed; -`2` — the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; +`2` – the extension is unable to detect requests from other extensions. If a malicious or tracking extension sends a request to its server to show you ads or track your activity, AdGuard Browser Extension will not be able to block that request; -`3` — not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. +`3` – not all types of ads and threats can be blocked by browser extensions due to certain browser limitations. Some elements may get to the page and slow down the loading process. Besides, unlike browser-based ad blockers, the AdGuard app blocks ads before they are loaded to the browser. This saves traffic and speeds up page loading. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md index c896201fe70..0d16517eaa0 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/filters.md @@ -19,7 +19,7 @@ All filters are grouped according to their role. For example, there are categori ## Custom filters -While the features of other filter groups are more or less self-explanatory, there is a group called _Custom_ that may raise additional questions. +While the features of other filter groups are more or less predictable, there is a group called _Custom_ that may raise additional questions. ![Custom filters \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_custom_filters.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md index 47f297a52cd..d899396ea53 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/main-menu.md @@ -15,6 +15,6 @@ The extension's main page can be accessed by clicking the extension's icon on th On the main page, you can hide any element on any page manually (a corresponding rule will be added to the _User rules_), open the _Filtering log_ to view the complete information about your browser's traffic and block requests on the go, or look at a website’s security report. Besides, you can submit a complaint about any website (for example, if there are missed ads on the page, our filter engineers will review the report and fix the problem) and see the statistics on applied blocking rules. -All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the _Additional settings_ tab). +All web requests made by the browser are displayed in the _Filtering log_, along with detailed information about each request. The _Filtering log_ makes it easy, for example, to monitor requests blocked by AdGuard Browser Extension. Besides, it allows you to block any request or add a previously blocked request to Allowlist in two clicks. The _Filtering log_ also offers you a wide variety of options for sorting web requests, which can be helpful when creating your own filtering rules. You can open the _Filtering log_ by selecting the corresponding item in the main menu, or from the settings page (in the "Additional settings" tab). By clicking the icons in the top right corner of the extension's main menu, you can open the extension settings or pause the protection. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md index 978f995eeea..25e574037fe 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/features/other-features.md @@ -13,13 +13,13 @@ Apart from the large key modules of AdGuard Browser Extension, there are several ## General {#general} -In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters' update interval, etc. +In the _General_ tab, you can allow search ads and the [self-promotion of websites](/general/ad-filtering/search-ads), enable the automatic activation of language-specific filters, indicate the filters update interval, etc. ![General \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_general.png) Besides, here you can enable [_Phishing and malware protection_](/general/browsing-security). -You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To import the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. +You can save your settings configuration by clicking the _Export settings_ button. The settings will be saved as a .json file. To upload the previously saved settings configuration, use the _Import settings_ function. You can even use it to quickly switch between different settings profiles or even to transfer settings configurations between different browsers. ## Additional settings {#misc} @@ -33,6 +33,6 @@ Besides, you can opt to help us with the development of filters by sending the s ## About {#about} -In the _About_ section, you can find info about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. +In the _About_ section, you can find infos about the current version, links to the EULA and Privacy policy, and to the repository of the Browser extension on GitHub. ![About \*border](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/ad_blocker_browser_extension_about.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md deleted file mode 100644 index 3cb82b928ca..00000000000 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/mv3-version.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -title: AdGuard Browser Extension for Chrome MV3 -sidebar_position: 5 ---- - -As MV2 extensions are being phased out in the Chrome Web Store, Chrome users may need to switch to MV3 extensions that are compatible with Chrome’s new API Manifest V3. Our thoughts on this topic are extensively discussed on [our blog](https://adguard.com/en/blog/tag/manifest-v3.html). - -Our MV3 extension effectively blocks ads and trackers while seamlessly managing social widgets, banners, and video ads. Most users will not notice any operational differences, but there are some limitations and changes to be aware of. - -## Where to find our extensions - -The **MV3 version** will soon replace our old extension in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker/bgnkhhnnamicmpeenaelnjfhikgbkllg). - -The **beta version of MV3** will still be available in the [Chrome Web Store](https://chromewebstore.google.com/detail/adguard-adblocker-mv3-exp/apjcbfpjihpedihablmalmbbhjpklbdf). - -The old beta extension will be renamed to [**AdGuard Ad Blocker MV2**](https://chromewebstore.google.com/detail/adguard-adblocker-beta/gfggjaccafhcbfogfkogggoepomehbjl) and will be supported until Google phases it out. - -## Main changes in features and settings - -- **No auto and manual filter updates.** The options _Auto-update filters_ and _Check filters update_ are no longer available in the _Filters_ tab. Since some of the rules are now applied in DNR form, we can’t update filters on request, only through the full process of updating the extension along with the review in the stores. - -- **Filtering log** - - ![Filtering log \*border](https://cdn.adtidy.org/content/blog/mv3/new/log.png) - - Due to DNR restrictions, we can’t show exactly which rule worked, but we will provide an “approximate rule that was triggered” based on our engine. For precise information, you’ll need to install the “unpacked” form of the extension in your browser yourself. You’ll find detailed instructions on how to do this in a [separate article](adguard-browser-extension/solving-problems/debug-rules). - -- _Tracking protection_ (formerly known as _Stealth mode_) - - ![Tracking protection \*border](https://cdn.adtidy.org/content/blog/mv3/new/tracking_screen.png) - - There are no _Cookies_ section, along with _Self-destruction of first-party cookies_ and _Self-destruction of third-party cookies_ since we cannot set the TTL of cookies using declarative rules. - -- _Phishing & malware protection_ is no longer available in the general settings. To protect yourself from malicious websites and scams, enable the appropriate filters in the _Security_ tab. - - ![Security](https://cdn.adtidy.org/content/blog/mv3/new/security.png) - -## Limitations - -### Maximum number of rules and filters - -Manifest V3 imposes limits on static and regex rules per extension. Users may receive notifications when these limits are exceeded. - -![Rule limits \*border](https://cdn.adtidy.org/content/blog/new/rulelimits.png) - -![Too many extensions \*border](https://cdn.adtidy.org/content/blog/new/other_extension.png) - -Basically, Manifest V3 divides rules into static (built-in) and dynamic, with strict limits in place. - -**Static rules:** minimum **30,000** rules per extension, with a cumulative limit of **330,000** for all extensions installed by a single user. - -For regex rules, the limit is set at **1,000 per extension**. - -The maximum number of simultaneously enabled filters is **50**. - -**Dynamic rules:** a strict cap of **5,000** rules is imposed, which includes a maximum of 1,000 regex rules. - -If this limit is exceeded, only **5,000 converted rules** will be applied in the following order: first allowlist, then user rules, and finally — custom filters. - -> **Converted rules** are rules that have been transformed to [DNR](https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest#build-rules) format using the [declarative converter](https://github.com/AdguardTeam/tsurlfilter/tree/master/packages/tsurlfilter/src/rules/declarative-converter). During this conversion process, some rules may overwrite others (`badfilter`), some may be combined (`removeparame`), resulting in a list of rules with a slightly different order. -> -> From this list of converted rules, we will only use 5,000 rules. The rest of them will be displayed in the editor, but not applied. - -Here's how a rule with a basic modifier is converted to a declarative rule: - -```bash -||example.org^$script,third-party,domain=example.com -``` - -is converted to - -```bash -[ -{ - "id": 1, - "action": { - "type": "block" - }, - "condition": { - "urlFilter": "||example.org^", - "domainType": "thirdParty", - "initiatorDomains": [ - "example.com" - ], - "resourceTypes": [ - "script" - ] - }, - "priority": 302 -} -] -``` - -More examples can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#basic-examples). - -### Network rules - -Network rules have limitations: some types of rules cannot be implemented in MV3, or can only be implemented with restrictions. - -Below is a list of modifiers that are supported, partially supported, or not supported at all. More details about the limitations can be found on [GitHub](https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter). For further information on modifiers, please refer to our [Knowledge base](/general/ad-filtering/create-own-filters/#basic-rules-basic-modifiers). diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md index afd0fac98fa..25ce5b9f33f 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/protected-pages.md @@ -1,6 +1,6 @@ --- title: Browser-protected pages -sidebar_position: 6 +sidebar_position: 5 --- :::info diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md deleted file mode 100644 index e076e8ca803..00000000000 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-browser-extension/solving-problems/debug-rules.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -title: How to debug rules in AdGuard for Chrome MV3 -sidebar_position: 2 ---- - -In [AdGuard for Chrome MV3](/adguard-browser-extension/mv3-version), the Filtering log only shows the approximate rules that were applied, which we call “assumed rules”. This is because the browser doesn’t provide details about which specific declarative rules were used unless the extension is in an “unpacked” format. To get precise information, you’ll need to install the unpacked version of the extension in your browser yourself. - -These instructions are also meant for problematic cases where you want to modify the rules that are bundled with the extension statically. In most cases, using _User rules_ in the extension should be sufficient. - -## Prerequisites - -1. **Git:** [Install Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - -2. **Node:** [Install Node.js](https://nodejs.org/en/download/package-manager) - -3. **Yarn:** [Install Yarn](https://classic.yarnpkg.com/lang/en/docs/install) - -## How to clone extension - -1. Clone the repository: - - ```bash - git clone git@github.com:AdguardTeam/AdguardBrowserExtension.git - ``` - -2. Navigate to the directory: - - ```bash - cd AdguardBrowserExtension - ``` - -3. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -4. Install dependencies: - - ```bash - yarn install - ``` - -## How to build extension - -1. Switch to the `v5.0` branch: - - ```bash - git checkout v5.0 - ``` - -2. Run the following command in the terminal: - - ```bash - yarn dev chrome-mv3 - ``` - -3. The built extension will be located in the directory: - - ```bash - ./build/dev/chrome-mv3 - ``` - -## How to install unpacked in the browser - -1. Turn on developer mode: - - ![Developer mode](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/developer_mode.png) - -2. Click _Load unpacked_: - - ![Load unacked](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/load_unpacked.png) - -3. Select the extension directory and click `Select`: - - ![Select](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/select.png) - -That’s it! - -## How to debug rules - -1. Find and modify the rule you need in the `./Extension/filters/chromium-mv3` directory in the `.txt` files. - -2. Convert the rules from txt to declarative form: - - ```bash - yarn convert-declarative - ``` - -3. Build the extension again: - - ```bash - yarn dev chrome-mv3 - ``` - -4. Reload the extension in the browser: - - ![Reload extension](https://cdn.adtidy.org/content/Kb/ad_blocker/browser_extension/reload_extension.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md index 7c5a50ef53b..43a35d21793 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/app-management.md @@ -28,7 +28,7 @@ From the context menu, you can also access the app's stats. ### “Problem-free” and “problematic” apps -Most apps work correctly when filtered. For such apps, their traffic is routed through AdGuard and filtered by default. +Most apps work properly when filtering is enabled. For such apps, their traffic is routed through AdGuard and filtered by default. Some apps, such as Download Manager, radio, system apps with UID 1000 and 1001 (for example, Google Play services), are “problematic” and may work incorrectly when routed through AdGuard. That's why you may see the following warning when trying to route or filter all apps: diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md index 3ecae5f658d..40a5d951cab 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/dns-protection.md @@ -13,7 +13,7 @@ The DNS protection module can be accessed by tapping the _Protection_ tab (secon :::tip -DNS protection works differently from regular ad and tracker blocking. You can [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) +DNS protection works differently from regular ad and tracker blocking. You cam [learn more about it and how it works from a dedicated article](https://adguard-dns.io/kb/general/dns-filtering/#how-does-dns-filtering-work) ::: diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md index 2417406eb35..bea7cc2433e 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/firewall/firewall.md @@ -45,7 +45,7 @@ To delete a rule or app from _Custom rules_, swipe it to the left. ### Notifications -If enabled, this feature notifies you when an app is attempting to violate an applicable firewall rule, e.g. attempts to access mobile data from which it is blocked. You can turn notifications on and off for all apps or for each app separately. +If enabled, this feature notifies you when an app tries to break one of the Firewall rules set for that app (for example, to access mobile data when it shouldn’t). You can turn notifications on and off for all apps or for each app separately. Tap the notification to access the app’s Firewall settings, or temporary disable all Firewall rules for that app by tapping the corresponding button in the notification. You can also mute all Firewall notifications for the app by tapping the _Mute_ button in the notification for that app. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md index a867a6d217b..35a5d712674 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/protection/tracking-protection.md @@ -77,4 +77,4 @@ Here are the active features of the pre-configured levels: k. _Remove X-Client-Data header_. This feature prevents Google Chrome from sending its version and modifications information to Google domains (including DoubleClick and Google Analytics) -You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Read more about what the various _Tracking protection_ settings do](/general/stealth-mode) and utilize them cautiously, as some may interfere with the functionality of websites and browser extensions. +You can tweak individual settings in _Tracking protection_ and come up with a custom configuration. Every setting has a description that will help you understand its role. [Learn more about what various _Tracking protection_ settings do](/general/stealth-mode) and approach them with caution, as some may interfere with the functionality of websites and browser extensions. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md index 8e5d5274c8b..e19db3de82e 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/rooted.md @@ -11,6 +11,6 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro Due to security measures of the Android OS, some AdGuard features are only available on rooted devices. Here's the list of them: -- In most cases, **HTTPS filtering in apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps don't trust certificates in the user store +- **HTTPS filtering in most apps** requires [installing a CA certificate into the system store](/adguard-for-android/features/settings#security-certificates), as most apps do not trust certificates in the user store. Installing a certificate into the system store is only possible on rooted devices - The [**Automatic proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access due to Android's restrictions on system-wide traffic filtering - The [**Manual proxy** routing mode](/adguard-for-android/features/settings#routing-mode) requires root access on Android 10 and above as it's no longer possible to determine the name of the app associated with a connection filtered by AdGuard diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md index 3835efd702f..1ee2404abd3 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/features/settings.md @@ -59,7 +59,7 @@ If you activate too many filters, some websites may work incorrectly. ### Userscripts -Userscripts are miniprograms written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. +Userscripts are mini-programs written in JavaScript that extend the functionality of one or more websites. To install a userscripts, you need a special userscript manager. AdGuard has such a functionality and allows you to add userscripts by URL or from file. ![Userscripts \*mobile\_border](https://cdn.adtidy.org/blog/new/isv6userscripts.png) @@ -133,7 +133,7 @@ In this section, you can find information about your license and manage it: - Buy an AdGuard license to activate [the full version's features](/adguard-for-android/features/free-vs-full) - Log in to your AdGuard account or enter the license key to activate your license - Sign up to activate your 7-day trial period if you haven't used it yet -- Refresh the license status from the three-dots menu (⋮) +- Refresh the license status from the three-dots menu (:) - Open the AdGuard account to manage your license there - Reset your license — for example, if you've reached device limit for this license and want to apply another one diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md index d3a7c3abf7a..38bb89ed9bf 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/adguard-for-android-tv.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android TV, an ad blocker that protects your T ::: -In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will go through an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. +In most cases, stock browsers cannot install a file on your TV, but you can download a browser from the Google Play Store that has this functionality. In our guide, we will consider an example of installation using the TV Bro browser, but there are other options and you can choose the one that better suits your needs. As an alternative, you can use the [Downloader](https://play.google.com/store/apps/details?id=com.esaba.downloader) app. ## Installing AdGuard for Android TV via browser diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md index c1c9ed8e242..fcdafe0d6bc 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/background-work.md @@ -51,7 +51,7 @@ Done! You have successfully set up AdGuard to work in the background. To let your AdGuard app run successfully in the background, do the following: -In **Settings** → **Apps** → **Manage apps**, scroll down to locate **AdGuard** and set **Autostart** to “On”. +In **Settings** → **Apps** → **Manage apps** → scroll down to locate **AdGuard**, set **Autostart** to “On”. ![Xiaomi Settings *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/background-work/xiaomi4en.jpeg) @@ -529,7 +529,7 @@ On Android 11+, on the same screen with STAMINA mode, there is a setting called You also need to be set AdGuard as Excepted from Power-saving feature: -**System settings** → **Apps & Notifications** → **Advanced** → **Special app access** → **Power saving feature** → Switch AdGuard to **Excepted** +**System settings** ​→ **Apps & Notifications** ​→ **Advanced** ​→ **Special app access** ​→ **Power saving feature** → Switch AdGuard to **Excepted** ## Wiko diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md index 7367e63cef9..0ffc5a34d37 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/battery.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Due to built-in statistics processes, high data and/or battery consumption was often attributed to AdGuard by Android 6 and earlier. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. +On Android devices running OS 6 and earlier, built-in statistics often attributed high data and/or battery usage to AdGuard. This was because AdGuard counted all the traffic it filtered from various apps. As a result, AdGuard's share of total data and battery usage was overstated, while other apps were understated. With Android 7, however, this scenario has improved. Now the data reflected in Android's built-in data usage statistics is very close to reality, although there are minor discrepancies in the battery usage data. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md index 31faca135f4..a0de5c6236a 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/compatibility-issues.md @@ -36,7 +36,7 @@ Some device manufacturers keep Private DNS settings hidden and set 'Automatic' m ### UC Browsers: UC Browser, UC Browser for x86, UC Mini, UC Browser HD -To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. +To be able to filter HTTPS traffic, AdGuard requires the user to add a certificate to the device's trusted user certificates. Unfortunately, UC-family browsers don't trust user certificates, so AdGuard cannot perform HTTPS filtering there. - To solve this problem, move the [certificate to the system certificate store](../solving-problems/https-certificate-for-rooted.md/) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md index de1fbe7b144..95536eb9f29 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/har.md @@ -1,5 +1,5 @@ --- -title: How to generate HAR files +title: How to get HAR files sidebar_position: 5 --- @@ -17,11 +17,11 @@ HAR files are processed in accordance with [the AdGuard Privacy Policy](https:// ## What are HAR files? -The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format define archival data for HTTP transactions that a browser uses to export detailed information about the web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. +The HAR (HTTP ARchive) format is a JSON-formatted archive file for logging of a web browser's interaction with a site. The specifications of HAR format defines an archival data for HTTP transactions that used by a browser to export detailed information about web pages it loads. More detailed description of HAR file format and its specification you can find at [softwareishard.com](http://www.softwareishard.com/blog/har-12-spec/) website. -## How to generate HAR files +## How to get HAR files -Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files, follow these steps: +Sometimes we need to analyze it to block specific ads that are difficult to reproduce for some reason. To get HAR files follow these steps: 1. Open AdGuard and go to **Settings** (⚙ icon in the lower right corner). 2. Tap **General** →**Advanced** → **Low-level settings**. @@ -31,7 +31,7 @@ Sometimes we need to analyze it to block specific ads that are difficult to repr 6. Go back to **Advanced**. 7. Tap **Export logs and system info** → **Allow** (if necessary) → **Save**. -**Send the generated file with the logs to the AdGuard support service.** +**Please send the file with logs (that you've got as a result) to the AdGuard support service.** :::note diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md index c5b7755321a..e3f0d778650 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/https-certificate-for-rooted.md @@ -29,7 +29,7 @@ Here's how to do that. 1. Install the [latest release of the **adguardcert** Magisk module](https://github.com/AdguardTeam/adguardcert/releases/latest/). -1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. The AdGuard Personal CA certificate will be copied to the system store. +1. Open *Magisk → Modules → Install from storage* and select the downloaded **adguardcert** file. This will move the AdGuard Personal CA from the user store to the system store. ![Open Magisk modules *mobile](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/https-certificate-for-rooted/magisk-module-4.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md index f081bc3cadc..daf395b8c53 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/log.md @@ -23,9 +23,9 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ::: -### Recording debug log +### Collecting debug log -To collect **debug** log and send it to us, you need to perform following steps: +To collect **debug** log and send it to us you need to perform following steps: 1. Go to *Settings* → *General* → *Advanced*. 1. Tap *Logging level* and set it to *Debug*. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md index 86d917c35d4..20243b19ddd 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/low-level-settings.md @@ -113,7 +113,7 @@ Use it only for debugging purposes! #### Encrypted Client Hello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. #### OCSP checking @@ -147,7 +147,7 @@ Here you can specify port ranges that should be filtered. If this setting is enabled, AdGuard will record blocked HTML elements in *Recent activity*. -#### Scriptlet debugging +#### Scriplet debugging If this setting is enabled, debugging in scriptlets will be activated, and the browser log will record when scriptlet rules are applied. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md index 8bd8d837ac5..f0abeb8bcbb 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/manual-certificate.md @@ -9,18 +9,18 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install its certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. +To be able to [filter HTTPS traffic](/general/https-filtering/what-is-https-filtering.md) (which is extremely important as most ads use HTTPS), AdGuard needs to install a certificate into your device's user storage. On older versions of the Android OS this was done automatically, but on Android 11 and later users have to install it manually. ![Certificate *mobile_border](https://cdn.adtidy.org/content/kb/ad_blocker/android/solving_problems/manual-certificate/g.gif) -Follow these steps to install the AdGuard certificate: +Follow these steps to install AdGuard certificate: 1. When you see the *HTTPS filtering is off* notification, tap *Enable*. 1. Then you'll be presented with three screens that explain: - Why filter HTTPS traffic - The safety of this filtering process - - The necessity of the AdGuard certificate + - The necessity of AdGuard certificate Consecutively tap *Next* → *Next* → *Save certificate*. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md index b23ab1e8108..8fa89725a88 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/outbound-proxy.md @@ -9,7 +9,7 @@ This article is about AdGuard for Android, a multifunctional ad blocker that pro ::: -Below is a list of the most well-known applications that can be configured to work as proxies in AdGuard. +Below you can find a list of the most famous applications that you can configure to work as proxies in AdGuard. :::note @@ -41,11 +41,11 @@ In this article we give examples of how to set up some of the most popular proxi | Proxy host | *127.0.0.1* | | Proxy port | *9050* | - Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as the default proxy. + Or you can tap **Proxy server** → **Add proxy server**, enter these values manually, and set Orbot as a default proxy. 1. Enable the main Proxy switch and AdGuard protection to route your device's traffic through the proxy. - Now AdGuard will route all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable the outbound proxy settings in AdGuard. + Now AdGuard will forward all traffic through Orbot. If you disable Orbot, Internet connection will be unavailable until you disable outbound proxy settings in AdGuard. ### How to use AdGuard with PIA (Private Internet Access) @@ -157,4 +157,4 @@ You should remove Shadowsocks app from filtering before setting up the process ( ## Limitations -However, at least one factor may prevent certain traffic from being routed through the outbound proxy, even after configuring the AdGuard proxy settings. That would be if the app itself isn't configured to send its traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. +There is a factor that can prevent certain traffic from being routed through the outgoing proxy even after you configure AdGuard proxy settings. It can happen if you don't set up the app itself to send the traffic through AdGuard. To do it, you need to proceed to **App management**, choose the app, and turn on **Route traffic through AdGuard**. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md index 001e509b43d..1af95ed681d 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-android/solving-problems/tasker.md @@ -126,7 +126,7 @@ Or you can configure remove parameters manually: ::: -**Don't forget to include the password, package name, and class. You need to do so for every intent.** +**Don't forget to include the password as an extra and mention package name and class. You need to do so for every intent.** Extra: `password:*******` @@ -136,7 +136,7 @@ Class: `com.adguard.android.receiver.AutomationReceiver` :::note -Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If this function is used, remember to update to the new name. +Before v4.0 the class was called `com.adguard.android.receivers.AutomationReceiver` but then we changed its name to `com.adguard.android.receiver.AutomationReceiver`. If you used this feature, please pay attention and use the new name. ::: diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md deleted file mode 100644 index 3499f3ed56d..00000000000 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/features/free-vs-full.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Free vs. full version -sidebar_position: 9 ---- - -:::info - -This article is about AdGuard for iOS, a multifunctional ad blocker that protects your device at the system level. To see how it works, [download the AdGuard app](https://agrd.io/download-kb-adblock) - -::: - -:::note - -Both AdGuard for iOS with enabled Premium and AdGuard Pro block ads on Apple smartphones and tablets. They used to differ in functionality due to certain changes made to App Store review policies in the past, but now AdGuard with a purchased subscription and AdGuard Pro are identical in their functionality. - -::: - -Premium AdGuard for iOS features several differences from the free version, including custom DNS settings. With these settings, you can block ads not only in Safari but in other apps too, protect your kids from adult content online, and keep your personal information safe from theft. There are other differences, too. Let’s explore them all in more detail. - -1. The **DNS protection** module encrypts your DNS traffic to enhance privacy. It works across all apps and browsers, not just Safari, offering broad protection against ads and trackers. - - - **Custom DNS servers:** Choose from one of the popular DNS servers from our list or add your own custom server. - - - **Family Protection:** The Internet isn’t always kid-friendly. With AdGuard Premium, you can switch to DNS providers that block adult content and other inappropriate material to keep your children safe online. - - - **Monitoring and flexible configuration:** Recent activity log allows you to view all DNS requests sent by your device and easily manage your traffic by adding websites to blocklist or allowlist with just a tap. - -2. **Advanced protection** lets you use advanced filtering rules to block more complex ads that would be left unblocked otherwise. - -3. **More filter options:** When purchasing AdGuard Premium, you get access to custom filters and a security filter category, where you can choose from over 50 filters, including AdGuard’s and other popular lists. - -Access these features by [purchasing a license](https://adguard.com/license.html). diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md index d85fb63cc1f..6cd12b2a9ce 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/installation.md @@ -29,7 +29,7 @@ AdGuard for iOS is an app presented in the App Store. To install it on your devi ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search bar and tap the string *AdGuard* which will be among search results. +Type *adguard* in the search bar and tap the string *adGuard* which will be among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) @@ -43,11 +43,11 @@ AdGuard Pro is a paid version of AdGuard for iOS, offering an expanded set of fu ![On the App Store main screen, tap Search *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/1.png) -Type *adguard* in the search form, and then tap the string *AdGuard Pro — adblock* which will be shown among search results. +Type *adguard* in the search form, and then tap the string *adGuard pro - adblock* which will be shown among search results. ![Type "AdGuard" in the search bar *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/2.png) -On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro — adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. +On the opened page of the App Store tap the button with the cost of the license under the string *AdGuard Pro - adblock*, and then tap *BUY*. You may be requested to enter your Apple ID login and password. Type it in and wait for the installation to complete. ![Tap GET below the AdGuard app *mobile_border](https://cdn.adtidy.org/public/Adguard/kb/installation/iOS/en/3.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md index bfd3e9280e8..74715146465 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/block-youtube-ads.md @@ -17,7 +17,7 @@ This article covers AdGuard for iOS, a multifunctional ad blocker that protects 1. Choose a video and tap *Share*. 1. Tap *More*, then select *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. ## How to block ads on YouTube in Safari @@ -31,4 +31,4 @@ Make sure you've given AdGuard access to all websites. You can check it in Safar 1. Choose a video and tap *Share*. 1. Tap *Block YouTube Ads (by AdGuard)*. -The video now opens in AdGuard's ad-free player. +AdGuard will open its ad-free video player. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md index b5363e14c44..701acc8189a 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/facetime-compatibility-issues.md @@ -1,5 +1,5 @@ --- -title: How to avoid compatibility issues with FaceTime +title: How to avoid compatibility problem with FaceTime sidebar_position: 3 --- diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md index ce6f0d9d846..5667afb6dc9 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-ios/solving-problems/low-level-settings.md @@ -25,9 +25,9 @@ To go to *Low-level settings*, tap the gear icon at the bottom right of the scre There are two main tunnel modes: *Split* and *Full*. *Split-Tunnel* mode provides compatibility of AdGuard and so-called "Personal VPN" apps. In *Full-Tunnel* mode no other VPN can work simultaneously with AdGuard. -There is a specific feature of the *Split-Tunnel* mode: In case of poor DNS proxy performance, for example, if the response from the AdGuard DNS server isn't returned in timely, iOS will instead reroute traffic through the DNS server specified in the iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. +There is a specific feature of *Split-Tunnel* mode: if DNS proxy does not perform well, for example, if the response from the AdGuard DNS server was not returned in time, iOS will "amerce" it and reroute traffic through DNS server, specified in iOS settings. No ads are blocked at this time and DNS traffic is not encrypted. -In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may negatively impact the performance of some programs (e.g., FaceTime) and cause app update issues. +In *Full-Tunnel* mode only the DNS server specified in AdGuard settings is used. If it does not respond, the Internet will simply not work. Enabled *Full-Tunnel* mode may cause the incorrect performance of some programs (for instance, Facetime), and lead to problems with app updates. By default, AdGuard uses *Split-Tunnel* mode as the most stable option. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md index 98eb0b9d4bc..1f1e87cb9e7 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/advanced-settings.md @@ -71,7 +71,7 @@ Time, in seconds, before sending another keepalive probe to an unresponsive peer #### `network.https.ech.enabled` -Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts Client Hellos. +Uses a local DNS proxy to look for configs in the ECH Config Lists. If found, encrypts ClientHellos. #### `network.https.enforce.certificate.transparency` diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md index d1bb5a02f60..8473bfb654a 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/big-sur-issues.md @@ -63,7 +63,7 @@ If you use Flutter alongside AdGuard in "Network Extension" mode (or any other " #### VPN apps with legacy API -Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if a VPN-based app downloaded outside the App Store is used, there is a risk that it uses the old VPN API and needs to be excluded from filtering: +Despite AdGuard is displayed as a VPN in system settings, it shouldn't cause any conflicts when working alongside other VPN-based apps. However, if you're using a VPN-based app that was downloaded from outside App Store, there's a chance it uses the old VPN API and you have to exclude it from filtering: 1. Open AdGuard's menu. 1. Select *Preferences...*. @@ -79,9 +79,9 @@ These problems have been fixed by Apple by now but can be encountered in the old ### Compatibility with Little Snitch 5 -At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a risk to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. +At this moment, Network Extension mode in AdGuard isn't compatible with [Little Snitch 5](https://obdev.at/products/littlesnitch/index.html). When both are running, there's a chance to encounter issues with various apps' behavior, even if they aren't filtered by AdGuard. This problem is directly caused by a bug in Big Sur, and we've already informed Apple about it. This leaves us to believe that this issue will get resolved in one of the next updates. -However, disabling connection monitoring in Little Snitch doesn't solve the issue, as this doesn't unload the Little Snitch extension from the system memory. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. +It needs to be said that this problem can't be solved by disabling connections monitoring in Little Snitch, because this action doesn't unload Little Snitch's extension from the system. We recommend to switch to [**Automatic Proxy**](#automatic-proxy) filtering mode when running AdGuard alongside with Little Snitch on Big Sur, at least until Apple fixes the bug. ### Compatibility with local proxies @@ -121,7 +121,7 @@ First of all, you need a working server side for your proxy. Most likely, to set :::tip -More information on how to get started can be found on the [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). +You can find more information about how to get started on [Shadowsocks website](https://shadowsocks.org/guide/what-is-shadowsocks.html). ::: diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md index f79e71c4433..9dd7c456e6d 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/high-sierra-compatibility.md @@ -9,7 +9,7 @@ This article is about AdGuard for Mac, a multifunctional ad blocker that protect ::: -During the installation of AdGuard on macOS High Sierra (or later), you may see this message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. +During the Installation of AdGuard on macOS High Sierra (or later versions) you may see a message: "System Extension Blocked". This is a new security mechanism that appeared in High Sierra, it requires you to explicitly allow the installation of a third-party system extension. To complete the installation of AdGuard you have to manually allow loading the extension in *System Preferences* → *Security & Privacy* → *General*. ![Allow extension installation in settings](https://cdn.adtidy.org/public/Adguard/kb/PicturesEN/highsierra.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md index 634a8b204ed..dae74532b9f 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-mac/solving-problems/protect-mail-activity.md @@ -31,7 +31,7 @@ As a consequence, AdGuard can't work together with iCloud Private Relay and Mail 1. iCloud Private Relay is applied to connections at the library level — before they reach the socket level, where AdGuard operates. 2. iCloud Private Relay uses QUIC, which AdGuard can't filter because HTTP/3 filtering is not yet available. -3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic —otherwise, ad blocking is impossible. +3. Consequently, AdGuard blocks QUIC, including iCloud Private Relay traffic – otherwise, ad blocking is impossible. 4. When you use iCloud Private Relay and switch AdGuard into the "split-tunnel" mode, you can't open websites in Safari. 5. To work around this issue for Monterey, we apply the "default route" rule. When Private Relay sees that rule, it disables itself automatically. So, AdGuard works seamlessly on Monterey, but iCloud Private Relay gets disabled. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md index 1ea971ff745..f4b94445dce 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-safari/features/about.md @@ -9,6 +9,6 @@ In the About tab, you can see info about the current version of your product and :::note Reminder -AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge Base](/adguard-for-safari/installation/). +AdGuard for Safari can be downloaded for free [from the App Store](https://apps.apple.com/app/adguard-for-safari/id1440147259). A detailed setup instruction is available in the [Knowledge base](/adguard-for-safari/installation/). ::: diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md index a6d541c8861..276126312a2 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-safari/features/rules.md @@ -3,4 +3,4 @@ title: User rules sidebar_position: 4 --- -User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filtering rules, use a [special syntax](/general/ad-filtering/create-own-filters). +User rules can be used to customize ad blocking. They can be added manually, imported, or created automatically when you block an element on the page. To add your own filering rules, use a [special syntax](/general/ad-filtering/create-own-filters). diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md index 96b26f764af..24105703afd 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/admins-documentation.md @@ -51,4 +51,4 @@ Please note that such installation of the application and manual updates are not ## 5. Test your installation {#installation-test} -On a target machine, launch AdGuard. Open the license screen to check that it is using the specified license. You might need to click "Refresh status" to make AdGuard validate the license key. +On a target machine, launch AdGuard. Open the license screen to check that it uses the one you've set. You might need to click "Refresh status" to make AdGuard validate the license key. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md index 75c5dcab959..b6abab38d8f 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/browser-assistant.md @@ -21,7 +21,7 @@ Background information: In previous versions of the AdGuard Browser Extension (before v3.5), if you had it installed along with the AdGuard for Windows app, the extension took over the functions of Assistant, stopped filtering itself and relied on the app to do this. -The extension and the app worked in conjunction but sometimes the integration would fail. The protection normally provided by the desktop program would stop on certain sites, where only the less powerful extension would then provide protection. +The extension and the app worked in conjunction but sometimes the integration would fail. Some websites would stop being protected by the desktop program and be backed up only by the less powerful extension. When using the Browser Assistant, all these problems don’t matter as there can be no conflicts in essence. The role of the Browser Assistant is well-defined and it can’t hinder the functioning of the main app, so there is no need to worry. @@ -42,4 +42,4 @@ Legacy Assistant is the previous version of Assistant, which is a mere userscrip If you want to install the Browser Assistant for your default browser, you can do it directly from the app settings, but you also have an opportunity to install it for other browsers. -AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and then the *Install* button. That’s it! +AdGuard Browser Assistant is available for all popular browsers: Chrome, Firefox, Edge, Opera, and Yandex. To install the one you need (or many, it is not prohibited but even encouraged), go to [our website](https://adguard.com/adguard-assistant/overview.html), click the browser icon and tap the *Install* button. That’s it! diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md index 0dda1ff7459..95d880f2478 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/extensions.md @@ -29,11 +29,11 @@ AdGuard Assistant is Legacy Assistant that you may use if the [new Assistant](/a This is a custom extension designed to fight the technique of re-inserting blocked ads — the so-called ad blocker circumvention/ad reinjection. Both are advanced anti-ad blocker methods that continue to rise in popularity among advertisers. -AdGuard Extra is essentially a miniprogram that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. +AdGuard Extra is essentially a mini-program that changes the way pages work in such a way that it becomes much more difficult for sites to use the above-mentioned methods to bypass blockers. **AdGuard Popup Blocker** -This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge Base. +This extension prevents popup windows from opening when you view web pages. Some pop-ups are considered useful — they may contain settings for site administering or additional reference information demonstrated upon clicking a link. That is why you can turn off the Blocker if needed. This extension doesn’t work on websites added to the AdGuard exceptions list either. It is turned off by default, but you can turn it on in the application settings. You will find more detailed information about this extension in our Knowledge base. **Web of Trust** @@ -41,7 +41,7 @@ Web of Trust lets you see the reputation of each website based on its users’ o ### Network -The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and x.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS_ feature enabled unless you have a strong reason not to. +The penultimate module is dedicated to network filtering, and here you will find additional network-related options. Two of them are enabled by default: _Enable traffic filtering_ and _Filter HTTPS protocol_. These are important extra precautions to better filter your web space. Most websites are now using HTTPS, and the same applies to advertising. From many sites, like youtube.com, facebook.com and twitter.com, it is impossible to remove ads without HTTPS filtering. So keep the _Filter HTTPS protocol_ feature enabled unless you have a strong reason not to. ![Network Settings \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/network-settings.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md index 3f3f8df2d18..58facaff37a 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/features/settings.md @@ -80,7 +80,7 @@ There are several websites to which access should be restricted from a PC used b The module checks the contents of web pages opened in the browser and filters those with content undesirable for children: images and texts for adults, crude language, violence, drug propaganda, etc. Parental Control settings are password-protected so that the child is not able to go round the restrictions. This module not only blocks directions to undesirable sites but can also delete the links that are inappropriate for children from the search results. -In the _Parental Control_ module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. +In the Parental Control module you can enable the _Safe search_ and manage the _blocklist_ and the _allowlist_ to customize how this option works. You can also check the _Block executable files download_ box to prevent your child from downloading and installing software on the computer. There are two more options in the _Parental Control_ module: you can select a specific Windows user to be protected by _Parental Control_ and set a password to protect AdGuard settings from change. ![Parental Control \*mobile\_border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/overview/parental-control.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md index cd6513c2796..b87021fd4d2 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/installation.md @@ -23,7 +23,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote To use AdGuard on a PC or tablet under Microsoft Windows, you should download the installation package and launch the installation program. Perform the following actions: -1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the homepage](https://adguard.com/download.html?auto=1). +1. Go to the [AdGuard website](http://adguard.com) in the address bar and click *Download* [on the opened page](https://adguard.com/download.html?auto=1). ![Download AdGuard](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/download-from-website.png) @@ -91,7 +91,7 @@ Follow the next steps only if performing the first two steps wasn’t enough for ::: -- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Click *Yes, continue* in the window prompt. +- Select *AdGuard Ad Blocker* and *Extended* uninstall type, then click *Uninstall*. Clcik *Yes, continue* in the window prompt. ![Extended uninstall *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/installation/ab_extended.jpg) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md index 071290f8c2a..95058d17d53 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/adguard-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in logs are processed in accordance with [the AdGuard ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occur with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need AdGuard log files. These files contain records about errors and other events that occurr with the software. Below is the brief instruction describing the way to get the log files and send them to the support service if necessary. :::note @@ -25,7 +25,7 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy ### Debug logs {#debug-logs} -1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the bottom of the screen, and switch the *Logging Level* to *Debug*. +1. Open the AdGuard settings. Go to the *General Settings* section, scroll down to the end of the screen and switch the *Logging Level* to *Debug*. ![Debug logging level *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-1.png) @@ -33,13 +33,13 @@ AdGuard is committed to protecting your privacy. We strictly follow our [Privacy We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) Save the archive to any folder. -1. **Important**: after exporting the logs, set the logging level back to *Default*. *Debug* logging level will slow down the application. +1. **Important**: after exporting the logs, set the logging level back to *Standard*. *Debug* logging level will slow down the application. 1. Send the archive to the AdGuard support service at **support@adguard.com**, describe the problem and don't forget to mention the time when you reproduced the issue. @@ -65,7 +65,7 @@ If you have an older version of AdGuard for Windows, run the application with th We strongly advise to take note of the exact time when you reproduced the issue: it will help our support team to find relevant log entries and solve the problem faster. -1. Export the collected logs using the *Export Logs* button. +1. Export the recorded logs using the *Export Logs* button. ![Export logs *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/adg-logs-2.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md index 3d608dd81f2..597f7801950 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/common-installer-errors.md @@ -13,9 +13,9 @@ This article contains some of the most common errors that you can encounter duri ### Error 5: Access Denied {#error-5} -This error message appears when required permissions haven't been granted. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: +This error occurs when there's something wrong with permissions. There may be several different reasons why AdGuard installer doesn't have the permissions it requires to properly finish the installation process. You can try the following steps: -- Temporarily disable your antivirus. Some of them may interfere with the installation, depending on the severity of their settings. +- Temporarily disable your antiviruses. Some of them may interfere with the installation, depending on the severity of their settings. - Choose a different installation folder. It is possible that the current installation folder has some access restrictions. Also make sure you don't select an external drive, a virtual drive, etc. @@ -23,17 +23,17 @@ This error message appears when required permissions haven't been granted. There ### Error 112: Disk is full, Error 1632: Temporary folder full or inaccessible {#error-112} -These are two different errors with very similar solutions. As their titles suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: +These are two different errors with very similar solutions. As their names suggest, AdGuard installer didn't find enough disk space to complete the installation. There are several things you can attempt to fix the problem: - Uninstall some programs or delete unnecessary files from the drive you were trying to install AdGuard to. -- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstalled programs and such. It will help clean up some disk space. +- Download, install, and run [AdwCleaner](http://www.bleepingcomputer.com/download/adwcleaner/), a free piece of software by Malwarebytes. It will, among other things, clean your system from all kinds of extra "leftover" files that remain after incorrectly uninstall programs and such. It will help clean up some disk space. - Reboot your computer. Sometimes temporary files can take up a considerable amount of disk space, and restarting your PC is the most reliable way to get rid of them. ### Error 1601: Windows Installer is not accessible {#error-1601} -You could say this is a particular subcategory of Error 1603. The possible solutions are similar: +You could say this is a particular sub-case of Error 1603. The possible solutions are similar: - Start and re-register Microsoft Installer service. It requires some work. @@ -75,7 +75,7 @@ This error occurs when there are several instances of AdGuard installer launched - Reboot your PC and start the installer again. When you restart the computer, all ongoing processes will stop, including all copies of the installer. -- Don't make multiple clicks on the installer even if it doesn't start right away. Sometimes it may take a few seconds to display the installer UI. +- Don't make multiple clicks on the installer even if doesn't start right away. Sometimes it may take a few seconds to display the installer UI. ### Error 1638: Another version of this product is already installed {#error-1638} @@ -83,14 +83,14 @@ It's very likely that you've already installed AdGuard before. - Check if AdGuard is already installed on your computer. You can do it by pressing the *Win* key and typing in ***AdGuard***. -- Maybe there're some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. +- Maybe there's some leftover files from a previous AdGuard installation. Uninstall AdGuard using our special [uninstall tool](../../installation#advanced) and then repeat the installation. ### Other errors {#other} If you've encountered an error that's not listed above, it is possible that we can solve it by ourselves. But in order to do that, we need log files from you. Please perform the following steps: -- Find and archive the **AdGuard installation logs** as it is described in [this article](../installation-logs). +- Find and archive **AdGuard installation logs** as it is described in [this article](../installation-logs). -- Find and save to disk the **Event Viewer** logs. [This article](../system-logs) explains how to do that. +- Find and save to disk **Event Viewer** logs. [This article](../system-logs) explains how to do that. - Please email all these files from two previous steps to the support team at **support@adguard.com** and describe the problem in the message body. Our tech support agents will reply to you as soon as possible. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md index d23387c5c20..0941a879340 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dns-leaks.md @@ -11,7 +11,7 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote AdGuard for Windows allows users to specify a DNS server address to resolve queries instead of system DNS server, which is provided by your ISP if not overridden in the system settings. Using a non-default DNS server can safeguard your DNS traffic from the ISP’s interception. Moreover, by choosing an encrypted and/or filtering DNS server, you get another layer of protection against bad actors and annoying ads. -Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by the default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. +Many AdGuard for Windows users appreciate the DNS protection feature. But some of them encounter the following issue: a check on a website like https://ipleak.net/ shows that requests are handled by default DNS server instead of the selected one. In this article we will tell you why this happens and how to avoid it. ## Bootstrap DNS address @@ -21,7 +21,7 @@ The DNS server addresses could be written as IPs or as domain names. In the case - go to the *Advanced settings* - scroll down to the *List of custom bootstrap addresses* section -- enter the custom bootstrap address in the IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) +- enter the custom bootstrap address in IP address format (you may use [the list of known DNS providers](https://adguard-dns.io/kb/general/dns-providers/)) - click *Save* ## Fallback DNS server @@ -33,7 +33,7 @@ It could happen that AdGuard cannot reach the specified server because of a weak - go to the *Advanced settings* - scroll down to the *Fallback servers* section - check the *Use custom servers* option -- then find the *List of custom fallback servers* section and enter the custom fallback servers one per line +- then find the *List of custom fallback servers* section and enter custom fallback servers one per line or diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md index 0808dd59a2c..d10cbac1a2d 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/dump-file.md @@ -35,10 +35,10 @@ After you’ve created the dump file, please navigate to the file location. You :::note -AdGuard for Windows has two running processes, `Adguard.exe` and `AdguardSvc.exe`. Therefore, it's necessary to create a separate dump file for each process. +AdGuard for Windows has two running processes (`Adguard.exe` and `AdguardSvc.exe`). So you need to create the dump file separately for each process. ::: ![AdGuard processes](https://cdn.adtidy.org/public/Adguard/kb/Windows_dump/processes_en.png) -When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to get the log file. +When you send the dump files to the support team, please also attach the AdGuard application logs so we have a better chance at solving the problem. [Here](../adguard-logs) you can check the instructions on how to collect the log file. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md index 207f6204675..6c45a70da18 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/installation-logs.md @@ -17,7 +17,7 @@ Data and/or files provided in system logs are processed in accordance with [the If any problems occur during the installation of AdGuard, the support team might ask you to collect and send them AdGuard installation logs. In this case you need to: -1. Select the *Run* command in Start menu or press *Win + R* on the keyboard. +1. Select *Run* command in Start menu or press *Win + R* on the keyboard. 1. Type in *%tmp%* and click *OK*. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md index 4cf483f5d23..26fd04c4863 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/low-level-settings.md @@ -29,9 +29,9 @@ Once you open Advanced Settings, you will be presented with the following option If enabled, AdGuard will block TCP Fast Open in the Edge browser. To apply settings, you need to restart the browser. -### Use Encrypted Client Hello +### Use Encrypted ClientHello -Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted Client Hello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, Client Hello packet will be encrypted. +Every encrypted Internet connection has an unencrypted part. This is the very first packet which contains the name of the server you are connecting to. Encrypted Client Hello technology is supposed to solve this issue and encrypt that last bit of unencrypted information. To benefit from it, enable the *Use Encrypted ClientHello* option. It uses a local DNS proxy to look for the ECH configuration for the domain. If it is found, ClientHello packet will be encrypted. ### Check websites' certificate transparency @@ -73,7 +73,7 @@ Otherwise, AdGuard will filter all the traffic on the fly, without redirection. ### Open main window at system start-up -Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings*. +Enable this option to make the main AdGuard window open after the system is loaded. Note that it doesn't affect whether the actual filtering service is launched or not, this setting is located in *Settings → General Settings* ### Enable filtering at system start-up @@ -95,7 +95,7 @@ If you don't want AdGuard to filter particular subnets, enable this feature and ### Enable HAR writing -This option should be enabled **only for debugging purposes**. Ticking the checkbox will make AdGuard create a file in the HAR 1.2 format containing information about all filtered HTTP requests. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. +This option should be enabled **only for debugging purposes**. If you tick the checkmark, AdGuard will create a file that contains information about all filtered HTTP requests in HAR 1.2 format. This file can be analyzed with the Fiddler app. Note that it may slow down your web browsing significantly. ### Add an extra space to the plain HTTP request @@ -115,7 +115,7 @@ This option is only applied when the *Protect from DPI* Stealth mode option is e Specifies the size of the TCP packet fragmentation, avoiding deep packet inspection. This option only affects secured (HTTPS) traffic. -If this option is enabled, AdGuard splits the initial TLS packet (the Client Hello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. +If this option is enabled, AdGuard splits the initial TLS packet (the ClientHello packet) into two parts: the first one has the specified length and the second one has the rest, up to the length of the whole initial TLS packet. Valid values: 1–1500. If invalid size is specified, the value selected by the system will be used. This option is only applied when the *Protect from DPI* Stealth mode option is enabled. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md index 27c8a562ab8..89743cc50a7 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/system-logs.md @@ -15,7 +15,7 @@ Data and/or files provided in system logs are processed in accordance with [the ::: -To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occur with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. +To analyze and diagnose different problems that may potentially arise, the AdGuard support service might need Windows system log files. Windows event logs contain records about all errors that occurr with the installed software, including AdGuard. Below is the brief instruction describing the way to get the log files and to send them to our support service if necessary. 1. Press *Win + R* diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md index 5fbe4081260..397d6a4cff1 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows/solving-problems/wfp-driver.md @@ -9,12 +9,12 @@ This article covers AdGuard for Windows, a multifunctional ad blocker that prote ::: -To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While a WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. +To filter network traffic, AdGuard uses a network driver. There are two options: TDI driver and WFP driver. While WFP driver is generally preferrable and is enabled by default for all newer Windows OS versions (Windows 8 and newer), it can potentially cause compatibility problems, especially with some antiviruses. These problems and subsequent errors can be very different in each case. If you encounter a problem that you suspect might be caused by this, you can always switch to the older but more stable TDI network driver. To do so: 1. Go to *Settings → Network*. -2. Disable the WFP driver as it’s done in this picture: +2. Disable WFP driver as it’s done in this picture: ![WFP driver *border](https://cdn.adtidy.org/content/kb/ad_blocker/windows/solving-problems/wfp-driver.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/account/features.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/account/features.md index e19bd4ef2c9..bb4bbc47a70 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/account/features.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/account/features.md @@ -35,4 +35,4 @@ The Purchase history section displays all the licenses that you have ever purcha ## Contact support -The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge Base, and Discuss. +The Support tab contains useful links to help you solve problems or find answers to your questions about AdGuard products. They are divided into six sections: FAQ, Send a bug repot/feature request, Report incorrect blocking, Contact support, Knowledge base and Discuss. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md index 085f30ad6ce..aa3e499d36d 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/adguard-filters.md @@ -38,11 +38,10 @@ This article is about the filters we create to use in AdGuard and other ad-block - **Experimental filter** serves to test some new filtering rules that can potentially cause conflicts and mess with websites' work. In case these rules perform without any issues, they get added to main filters. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_5_Experimental/filter.txt) - **Mobile ads filter** blocks ads on mobile devices. Contains all known mobile ad networks. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_11_Mobile/filter.txt) - **DNS filter** — composed of several other filters (AdGuard Base filter, Social media filter, Spyware filter, Mobile ads filter, EasyList and EasyPrivacy) and simplified specifically to be better compatible with DNS-level ad blocking. This filter is used by [AdGuard DNS](https://adguard-dns.io/kb) servers to block ads and tracking. [View rules](https://raw.githubusercontent.com/AdguardTeam/FiltersRegistry/master/filters/filter_15_DnsFilter/filter.txt) -- **Quick Fixes filter** — used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. [View rules](https://filters.adtidy.org/extension/chromium-mv3/filters/24.txt) ## AdGuard Filters Policy -Our filter policy defines what AdGuard filters should and shouldn't block, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. +Our filter policy defines what AdGuard filters should block and what they should not, as well as the rules for adding and removing rules from filters. Read the full text of [AdGuard filter policy](../filter-policy) for detailed information. ## Contributing to AdGuard filters diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md index af4f16edc1f..a6a8ece4e6e 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/create-own-filters.md @@ -265,26 +265,24 @@ The following modifiers are the most simple and frequently used. Basically, they -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------------------- |:-------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:--------------------------------------:|:---------------------------------:| -| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$domain](#domain-modifier) | ✅ | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ | ✅ [*[1]](#domain-modifier-limitations) | ✅ [*[1]](#domain-modifier-limitations) | ✅ | -| [$header](#header-modifier) | ✅ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ✅ [*[2]](#header-modifier-limitations) | ❌ | ❌ | ❌ | -| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$method](#method-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$popup](#popup-modifier) | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ | ✅ [*[3]](#popup-modifier-limitations) | ✅ [*[3]](#popup-modifier-limitations) | ❌ | -| [$strict-first-party](#strict-first-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$strict-third-party](#strict-third-party-modifier) | ⏳ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$to](#to-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:------------------------------------:|:---------------------------------:| +| [$app](#app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$denyallow](#denyallow-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$domain](#domain-modifier) | ✅ | ✅ | ✅ | ✅ [*](#domain-modifier-limitations) | ✅ [*](#domain-modifier-limitations) | ✅ | +| [$header](#header-modifier) | ✅ | 🧩 [**](#header-modifier-limitations) | 🧩 [**](#header-modifier-limitations) | ❌ | ❌ | ❌ | +| [$important](#important-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$match-case](#match-case-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$method](#method-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$popup](#popup-modifier) | ✅ [***](#popup-modifier-limitations) | ✅ | ✅ | ✅ [***](#popup-modifier-limitations) | ✅ [***](#popup-modifier-limitations) | ❌ | +| [$third-party](#third-party-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$to](#to-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -381,11 +379,11 @@ entry_i = ( regular_domain / any_tld_domain / regexp ) - **`regular_domain`** — a regular domain name (`domain.com`). Corresponds the specified domain and its subdomains. It is matched lexicographically. - **`any_tld_domain`** — a domain name ending with a wildcard character as a [public suffix](https://publicsuffix.org/learn/), e.g. for `example.*` it is `co.uk` in `example.co.uk`. Corresponds to the specified domain and its subdomains with any public suffix. It is matched lexicographically. -- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, `,`, and `|` must be escaped with `\`. +- **`regexp`** — a regular expression, starts and ends with `/`. The pattern works the same way as in the basic URL rules, but the characters `/`, `$`, and `|` must be escaped with `\`. :::info -Rules with `$domain` modifier as `regular_domain` are supported by all AdGuard products. +Rules with `$domain` modifier as `regular_domain` or `any_tld_domain` are supported by all AdGuard products. ::: @@ -444,12 +442,6 @@ In the following examples it is implied that requests are sent from `http://exam ##### `$domain` modifier limitations {#domain-modifier-limitations} -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] `regexp` and `any_tld domains` are not supported. - -::: - :::caution Restrictions Safari does not support the simultaneous use of allowed and disallowed domains, so rules like `||baddomain.com^$domain=example.org|~foo.example.org` will not work in AdGuard for iOS and AdGuard for Safari. @@ -555,13 +547,13 @@ This modifier limits the rule scope to requests that use the specified set of HT :::caution Restrictions -Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be ignored. +Rules with mixed negated and not negated values are considered invalid. So, for example, the rule `||evil.com^$method=get|~head` will be rejected. ::: :::info Compatibility -Rules with `$method` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. +Rules with `$method` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v2.1.1 or later. ::: @@ -577,10 +569,9 @@ AdGuard will try to close the browser tab with any address that matches a blocki :::caution Limitations -1. The `$popup` modifier works best in AdGuard Browser Extension for Chromium-based browsers and Firefox. -1. In [AdGuard for Chrome MV3][ext-mv3] rules with the [`$popup`][popup-in-mv3] modifier would not work, so we disable converting them to declarative rules. We will try to use them only in our [TSUrlFilter][] engine and close new tabs programmatically. +1. The `$popup` modifier works best in AdGuard Browser Extension. 1. In AdGuard for iOS and AdGuard for Safari, `$popup` rules simply block the page right away. -1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party`, `$strict-third-party`, `$strict-first-party`, and `$important`. +1. In AdGuard for Windows, AdGuard for Mac, and AdGuard for Android, the `$popup` modifier may not detect a popup in some cases and it will not be blocked. The `$popup` modifier applies the `document` content type with a special flag which is passed to a blocking page. Blocking page itself can do some checks and close the window if it is really a popup. Otherwise, page should be loaded. It can be combined with other request type modifiers, such as `$third-party` and `$important`. ::: @@ -590,49 +581,9 @@ Rules with the `$popup` modifier are not supported by AdGuard Content Blocker. ::: -#### **`$strict-first-party`** {#strict-first-party-modifier} - -Works the same as the [`$~third-party`](#third-party-modifier) modifier, but only treats the request as first-party if the referrer and origin have exactly the same hostname. - -**Examples** - -- domain.com$strict-first-party' — this rule applies only to `domain.com`. For example, a request from `domain.com` to `http://domain.com/icon.ico` is a first-party request. A request from `sub.domain.com` to `http://domain.com/icon.ico` is treated as a third-party one (as opposed to the `$~third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict1p`. - -::: - -:::info Compatibility - -Rules with the `$strict-first-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - -#### **`$strict-third-party`** {#strict-third-party-modifier} - -Works the same as the [`$third-party`](#third-party-modifier) modifier but also treats requests from the domain to its subdomains and vice versa as third-party requests. - -**Examples** - -- `||domain.com^$strict-third-party` — this rule applies to all domains except `domain.com`. An example of a third-party request: `http://sub.domain.com/banner.jpg` (as opposed to the `$third-party` modifier). - -:::note - -You can use a shorter name (alias) instead of using the full modifier name: `$strict3p`. - -::: - -:::info Compatibility - -Rules with the `$strict-third-party` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later. - -::: - #### **`$third-party`** {#third-party-modifier} -A restriction on third-party and custom requests. A third-party request is a request from an external domain. For example, a request to `example.org` from `domain.com` is a third-party request. +A restriction of third-party and own requests. A third-party request is a request from a different domain. For example, a request to `example.org` from `domain.com` is a third-party request. :::note @@ -679,7 +630,7 @@ You may use a shorter name (alias) instead of using the full modifier name: `$3p :::info Compatibility -Rules with the `$to` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later, and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. +Rules with the `$to` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later and AdGuard Browser Extension with [TSUrlFilter][] v2.1.3 or later. ::: @@ -701,22 +652,22 @@ There is a big difference in how AdGuard determines the content type on differen -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:-----------------------------------------:|:-----------------------------------------:|:---------------------------------:| -| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$ping](#ping-modifier) | ✅ [*[1]](#ping-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | ❌ | ✅ | -| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$subdocument](#subdocument-modifier) | ✅ [*[2]](#subdocument-modifier-limitations) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#websocket-modifier-limitations) | ✅ [*[3]](#websocket-modifier-limitations) | ❌ | -| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$document](#document-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$font](#font-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$image](#image-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$media](#media-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$object](#object-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$other](#other-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$ping](#ping-modifier) | ✅ * | ✅ | ✅ | ❌ | ❌ | ✅ | +| [$script](#script-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$stylesheet](#stylesheet-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$subdocument](#subdocument-modifier) | ✅ * | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$websocket](#websocket-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ✅ | +| [$xmlhttprequest](#xmlhttprequest-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$webrtc 🚫](#webrtc-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$object-subrequest 🚫](#object-subrequest-modifier "removed") | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | :::note @@ -774,17 +725,11 @@ The rule applies to requests for which the type has not been determined or does The rule corresponds to requests caused by either `navigator.sendBeacon()` or the `ping` attribute on links. -##### `$ping` modifier limitations {#ping-modifier-limitations} - -:::caution Limitations +:::info Compatibility AdGuard for Windows, Mac, and Android often cannot accurately detect `navigator.sendBeacon()`. Using `$ping` is not recommended in the filter lists that are supposed to be used by CoreLibs-based AdGuard products. -::: - -:::info Compatibility - -Rules with `$ping` modifier are not supported by AdGuard for Safari and AdGuard for iOS. +Rules with `$ping` modifier are not supported by AdGuard for Safari and iOS. ::: @@ -817,16 +762,10 @@ You may use a shorter name (alias) instead of using the full modifier name: `$fr ::: -##### `$subdocument` modified limitations {#subdocument-modifier-limitations} - -:::caution Limitations - -In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][] if it is present. Otherwise, some main pages may be treated as subdocuments. - -::: - :::info Compatibility +In AdGuard for Windows, Mac, and Android subdocuments are being detected by the [Sec-Fetch-Dest header][sec-fetch-dest-header] if it is present. Otherwise, some main pages may be treated as subdocuments. + Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. ::: @@ -835,17 +774,9 @@ Rules with `$subdocument` modifier are not supported by AdGuard Content Blocker. The rule applies only to WebSocket connections. -##### `$websocket` modifier limitations {#websocket-modifier-limitations} - -:::caution Limitations - -For AdGuard for Safari and AdGuard for iOS, it is supported on devices with macOS Monterey (version 12) and iOS 16 or higher respectively. - -::: - :::info Compatibility -`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. +`$websocket` modifier is supported in all AdGuard products except AdGuard Content Blocker. As for AdGuard for Safari and AdGuard for iOS, it's supported on devices with macOS Monterey (version 12) and iOS 16 or higher. ::: @@ -900,17 +831,17 @@ We recommend to get acquainted with [the Adblock Plus filter cheatsheet](https:/ -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| --------------------------------------- |:------------------------:|:-------------------------------:|:----------------------------------------:|:-----------------------------:|:--------------------------------------------:|:--------------------------------------------:|:---------------------------------:| -| [$content](#content-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ [*[1]](#jsinject-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$stealth](#stealth-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ [*[2]](#urlblock-modifier-limitations) | ✅ [*[2]](#urlblock-modifier-limitations) | ❌ | -| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ [*[3]](#genericblock-modifier-limitations) | ✅ [*[3]](#genericblock-modifier-limitations) | ❌ | -| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| --------------------------------------- |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$content](#content-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$elemhide](#elemhide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$extension](#extension-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$jsinject](#jsinject-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$stealth](#stealth-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$urlblock](#urlblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$genericblock](#genericblock-modifier) | ✅ | ✅ | ✅ | ✅ * | ✅ * | ❌ | +| [$generichide](#generichide-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [$specifichide](#specifichide-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note @@ -978,44 +909,30 @@ $extension="userscript name\, with \"quote\"" - `@@||example.com^$extension="AdGuard Assistant"` disables the `AdGuard Assistant` userscript on `example.com` website. - `@@||example.com^$extension=MyUserscript` disables the `MyUserscript` userscript on `example.com` website. -- `@@||example.com^$extension='AdGuard Assistant'|'AdGuard Popup Blocker'` disables both `AdGuard Assistant` and `AdGuard Popup Blocker` userscripts on `example.com` website. +- `@@||example.com^$extension='AdGuard Assistant'|'Popup Blocker'` disables both `AdGuard Assistant` and `Popup Blocker` userscripts on `example.com` website. - `@@||example.com^$extension=~"AdGuard Assistant"` disables all user scripts on `example.com` website, except `AdGuard Assistant`. -- `@@||example.com^$extension=~"AdGuard Assistant"|~"AdGuard Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `AdGuard Popup Blocker`. +- `@@||example.com^$extension=~"AdGuard Assistant"|~"Popup Blocker"` disables all user scripts on `example.com` website, except `AdGuard Assistant` and `Popup Blocker`. - `@@||example.com^$extension` no userscript will work on webpages on `example.com`. - `@@||example.com^$extension="AdGuard \"Assistant\""` disables the `AdGuard "Assistant"` userscript on `example.com` website. :::info Compatibility - Only AdGuard for Windows, Mac, Android are technically capable of using rules with `$extension` modifier. -- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.13 or later. +- Rules with `$extension` modifier with specific userscript name are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.13 or later. ::: #### **`$jsinject`** {#jsinject-modifier} -Forbids adding of JavaScript code to the page. You can read about scriptlets and javascript rules further. +Forbids adding of javascript code to the page. You can read about scriptlets and javascript rules further. **Examples** - `@@||example.com^$jsinject` disables javascript on pages at `example.com` and all subdomains. -##### `$jsinject` modifier limitations {#jsinject-modifier-limitations} - -:::info Limitations - -Rules with the [`$jsinject`][jsinject-in-mv3] modifier cannot be converted to DNR in [AdGuard for Chrome MV3][ext-mv3]. We only use them in the [TSUrlFilter][] engine to disable some cosmetic rules. - -::: - -:::info Compatibility - -The `$jsinject` modifier is not supported by AdGuard for Chrome MV3 ([yet][jsinject-in-mv3]) and AdGuard Content Blocker. - -::: - #### **`$stealth`** {#stealth-modifier} -Disables the Tracking protection (formerly Stealth Mode) module for all corresponding pages and requests. +Disables the Stealth Mode module for all corresponding pages and requests. **Syntax** @@ -1023,7 +940,7 @@ Disables the Tracking protection (formerly Stealth Mode) module for all correspo $stealth [= opt1 [| opt2 [| opt3 [...]]]] ``` -`opt(i)` stand for certain Tracking protection options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Tracking protection features. +`opt(i)` stand for certain Stealth Mode options disabled by the modifier. The modifier can contain any number of specific options (see below) or none. In the latter case the modifier disables all the Stealth Mode features. The list of the available modifier options: @@ -1046,13 +963,13 @@ The list of the available modifier options: **Examples** -- `@@||example.com^$stealth` disables Tracking protection for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). -- `@@||domain.com^$script,stealth,domain=example.com` disables Tracking protection only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. +- `@@||example.com^$stealth` disables Stealth Mode for `example.com` (and subdomains) requests, except for blocking cookies and hiding tracking parameters (see below). +- `@@||domain.com^$script,stealth,domain=example.com` disables Stealth Mode only for script requests to `domain.com` (and its subdomains) on `example.com` and all its subdomains. - `@@||example.com^$stealth=3p-cookie|dpi` disables blocking third-party cookies and DPI fooling measures for `example.com`. :::note -Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Tracking protection features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. +Blocking cookies and removing tracking parameters is achieved by using rules with the [`$cookie`](#cookie-modifier), [`$urltransform`](#urltransform-modifier) and [`$removeparam`](#removeparam-modifier) modifiers. Exception rules that contain only the `$stealth` modifier will not do these things. If you want to completely disable all Stealth mode features for a given domain, you must include all three modifiers: `@@||example.org^$stealth,removeparam,cookie`. ::: @@ -1066,7 +983,7 @@ Blocking cookies and removing tracking parameters is achieved by using rules wit :::info Compatibility -- Tracking protection (formerly Stealth Mode) is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox and Chromium-based browsers, except AdGuard for Chrome MV3. All other products will ignore the rules with `$stealth` modifier. +- Stealth Mode is available in AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension. All other products will ignore the rules with `$stealth` modifier. - Rules with `$stealth` modifier with specific options are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -1079,17 +996,11 @@ Disables blocking of all requests sent from the pages matching the rule and disa - `@@||example.com^$urlblock` — any requests sent from the pages at `example.com` and all subdomains are not going to be blocked. -##### `$urlblock` modifier limitations {#urlblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$urlblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$urlblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1124,17 +1035,11 @@ Disables generic basic rules on pages that correspond to exception rule. - `@@||example.com^$genericblock` disables generic basic rules on any pages at `example.com` and all subdomains. -##### `$genericblock` modifier limitations {#genericblock-modifier-limitations} - -:::caution Limitations +:::info Compatibility In AdGuard for iOS and AdGuard for Safari, rules with `$genericblock` work as [$document exclusion](#document-modifier) — unblock everything. -::: - -:::info Compatibility - -Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker, and AdGuard for Chrome MV3. +Rules with `$genericblock` modifier are not supported by AdGuard Content Blocker. ::: @@ -1184,35 +1089,36 @@ These modifiers are able to completely change the behavior of basic rules. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------- |:-------------------------------------------:|:-------------------------------:|:-------------------------------------------:|:-------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$all](#all-modifier) | ✅ | ✅ | ✅ [*[1]](#all-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ [*[2]](#badfilter-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ [*[3]](#cookie-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$permissions](#permissions-modifier) | ✅ [*[4]](#permissions-modifier-limitations) | ✅ | ✅ | ✅ [*[4]](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | -| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ [*[5]](#redirect-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ⏳ | ❌ | ❌ | ❌ | ❌ | -| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ [*[6]](#removeparam-modifier-limitations) | ✅ | ❌ | ❌ | ❌ | -| [$replace](#replace-modifier) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | -| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------- |:----------------------------------------:|:-------------------------------:|:----------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$all](#all-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$badfilter](#badfilter-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$cookie](#cookie-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$csp](#csp-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$hls](#hls-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$inline-font](#inline-font-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$inline-script](#inline-script-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$jsonprune](#jsonprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$xmlprune](#xmlprune-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$network](#network-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$permissions](#permissions-modifier) | ✅ [*](#permissions-modifier-limitations) | 🧩 | 🧩 [*](#permissions-modifier-limitations) | ❌ | ❌ | ❌ | +| [$redirect](#redirect-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$redirect-rule](#redirect-rule-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$referrerpolicy](#referrerpolicy-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$removeheader](#removeheader-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$removeparam](#removeparam-modifier) | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$replace](#replace-modifier) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [$urltransform](#urltransform-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [noop](#noop-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$empty 👎](#empty-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | +| [$mp4 👎](#mp4-modifier "deprecated") | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | :::note - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions + - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future @@ -1226,20 +1132,8 @@ These modifiers are able to completely change the behavior of basic rules. ||example.org^$document,subdocument,font,image,media,object,other,ping,script,stylesheet,websocket,xmlhttprequest,popup ``` -:::caution Restrictions - This modifier cannot be used as an exception with the `@@` mark. -::: - -##### `$all` modifier limitations {#all-modifier-limitations} - -:::caution Limitations - -Since `$popup` is a part if `$all`, the `$all` modifier is not supported by AdGuard for Chrome MV3 because of [`$popup` modifier limitations](#popup-modifier-limitations). - -::: - :::info Compatibility Rules with `$all` modifier are not supported by AdGuard Content Blocker. @@ -1273,14 +1167,6 @@ In that case, the `$badfilter` rule will disable the corresponding rule for doma - `/some$domain=example.*` is disabled for `example.com` and `example.org` by `/some$domain=example.com|example.org,badfilter` - `/some$domain=example.com|example.org|example.io` is NOT disabled for `example.com` by `/some$domain=example.com|~example.org,badfilter` because the value of `$domain` modifier contains a negated domain -##### `$badfilter` modifier limitations {#badfilter-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] a rule with the `$badfilter` modifier is applied in DNR only if it fully cancels the source rule. We cannot calculate it if it is only partially canceled. [Examples](https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#badfilter) - -::: - :::info Compatibility Rules with `$badfilter` modifier are not supported by AdGuard Content Blocker. @@ -1305,7 +1191,7 @@ where: - **`name`** — optional, string or regular expression to match cookie name. - **`seconds`** — number of seconds for current time to offset the expiration date of cookie. -- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to be applied to the cookie. +- **`strategy`** — string for [Same-Site](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite) strategy to make cookie use. For example, @@ -1320,7 +1206,7 @@ every time AdGuard encounters a cookie called `NAME` in a request to `example.or **Escaping special characters** -If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` to escape each of them. For example, escaped comma looks like this: `\,`. +If regular expression `name` is used for matching, two characters must be escaped: comma `,` and dollar sign `$`. Use backslash `\` escape each of them. For example, escaped comma looks like this: `\,`. **Examples** @@ -1336,17 +1222,9 @@ There are two methods to deactivate `$cookie` rules: the primary method involves - `@@||example.org^$cookie=concept` unblocks a single cookie named `concept` - `@@||example.org^$cookie=/^_ga_/` unblocks every cookie that matches the regular expression -##### `$cookie` modifier limitations {#cookie-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] we delete cookies in 2 ways: from `content-script` side (to which we have access) and from `onBeforeSendHeaders` listener. Since `onBeforeSendHeaders` and other listeners are no longer blocking, we are not able to delete them in all cases. You can check if a rule works with [this test](https://testcases.agrd.dev/Filters/cookie-rules/test-cookie-rules). - -::: - :::caution Restrictions -`$cookie` rules support these types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, `$~third-party`, `strict-third-party`, and `strict-first-party`. +`$cookie` rules support three types of modifiers: `$domain`, `$~domain`, `$important`, `$third-party`, and `$~third-party`. ::: @@ -1389,7 +1267,7 @@ In case if multiple `$csp` rules match a single request, we will apply each of t :::caution Restrictions - There are a few characters forbidden in the `$csp` value: `,`, `$`. -- `$csp` rules support three types of modifiers: `$domain`, `$important`, `$subdocument`. +- `$csp` rules support limited list of modifiers: `$domain`, `$important`, `$subdocument`. - Rules with `report-*` directives are considered invalid. ::: @@ -1458,7 +1336,7 @@ Some points specific to the operation of `$hls` rules: 1. When a segment is removed, all of the tags that apply only to that segment are also removed 1. When there is a tag that applies to multiple segments, and all of those segments are removed, the tag is also removed 1. Since there is no way to recognize different kinds of tags by syntax, we recognize all of the tags specified by the RFC, plus some non-standard tags that we have seen in the field. Any lines starting with `#` and not recognized as a tag are passed through without modification, and are not matched against the rules -1. Tags will not be matched if they apply to the entire playlist, and `$hls` rules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist +1. Tags will not be matched if they apply to the entire playlist, and `$hls` rrules cannot be used to remove them, as these rule types are intended for segment removals. If you know what you are doing, you can use `$replace` rules to remove or rewrite just a single tag from the playlist **An example of a transformation done by the rules:** @@ -1520,7 +1398,7 @@ preroll.ts :::caution Restrictions - `$hls` rules are only allowed [**in trusted filters**](#trusted-filters). -- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. +- `$hls` rules are compatible with the modifiers `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest` only. - `$hls` rules only apply to HLS playlists, which are UTF-8 encoded text starting with the line `#EXTM3U`. Any other response will not be modified by these rules. - `$hls` rules do not apply if the size of the original response is more than 10 MB. @@ -1528,7 +1406,7 @@ preroll.ts :::info Compatibility -Rules with the `$hls` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$hls` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -1766,14 +1644,14 @@ In AdGuard for Windows, Mac and Android with [CoreLibs][] v1.11 or later, JSONPa :::caution Restrictions -- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$jsonprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$jsonprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.10 or later. +Rules with the `$jsonprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later. ::: @@ -2004,14 +1882,14 @@ When multiple `$xmlprune` rules match the same request, they are applied in lexi :::caution Restrictions -- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. +- `$xmlprune` rules are only compatible with these modifiers: `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and `$xmlhttprequest`. - `$xmlprune` rules do not apply if the size of the original response is greater than 10 MB. ::: :::info Compatibility -Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.15 or later. +Rules with the `$xmlprune` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.15 or later. ::: @@ -2064,7 +1942,7 @@ For the requests matching a `$permissions` rule, AdGuard strengthens response's `$permissions` value syntax is identical to that of the `Permissions-Policy` header [syntax](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy) with the following exceptions: 1. A comma that separates multiple features **MUST** be escaped — see examples below. -2. A pipe character (`|`) can be used instead of a comma to separate features. +2. A pipe character (`|`) can be used to separate features instead of a comma. The list of available directives is available [here](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy#directives). @@ -2109,8 +1987,8 @@ Firefox ignores the `Permissions-Policy` header. For more information, see [this :::info Compatibility -- Rules with the `$permissions` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. -- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Rules with the `$permissions` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +- Pipe separator `|` instead of escaped comma is supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.14 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: @@ -2145,17 +2023,9 @@ More information on redirects and their usage is available [on GitHub](https://g Go to [rules priorities](#rule-priorities) for more details. -##### `$redirect` modifier limitations {#redirect-modifier-limitations} - -:::caution Limitations - -In [AdGuard for Chrome MV3][ext-mv3] allowlist rules with `$redirect` are not supported. - -::: - :::info Compatibility -- Rules with `$redirect` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], and [AdGuard for Safari][ext-saf] . +- Rules with `$redirect` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS and AdGuard for Safari. - `$redirect` in uBlock Origin supports specifying priority, e.g. `$redirect=noopjs:42`. AdGuard does not support it and instead just discards the priority postfix. ::: @@ -2179,7 +2049,7 @@ In this case, only requests to `example.org/script.js` will be "redirected" to ` :::info Compatibility -Rules with `$redirect-rule` modifier are not supported by [AdGuard Content Blocker][and-cb], [AdGuard for iOS][ios-app], [AdGuard for Safari][ext-saf], and [AdGuard for Chrome MV3][ext-mv3]. [The discussion about adding support for `$redirect-rule` rules in Chrome MV3 extensions](https://github.com/w3c/webextensions/issues/493) is currently open. +Rules with `$redirect-rule` modifier are not supported by AdGuard Content Blocker, AdGuard for iOS, and AdGuard for Safari. ::: @@ -2199,7 +2069,7 @@ If a request matches multiple `$referrerpolicy` rules not disabled by exceptions :::info Compatibility -Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.12 or later. +Rules with the `$referrerpolicy` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.12 or later. ::: @@ -2301,13 +2171,13 @@ This type of rules can be used [**only in trusted filters**](#trusted-filters). - `transfer-encoding` - `upgrade` -1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$strict-third-party`, `$strict-first-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. +1. `$removeheader` rules are only compatible with `$domain`, `$third-party`, `$app`, `$important`, `$match-case`, and [content type modifiers](#content-type-modifiers) such as `$script` and `$stylesheet`. The rules which have any other modifiers are considered invalid and will be discarded. ::: :::info Compatibility -Rules with `$removeheader` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. +Rules with `$removeheader` modifier are supported by AdGuard for Windows, Mac, and Android, and AdGuard Browser Extension for Chrome, Firefox, and Edge. ::: @@ -2329,6 +2199,12 @@ Rules with `$removeparam` modifier are intended to strip query parameters from r - `$removeparam=param` removes query parameter with the name `param` from URLs of any request, e.g. a request to `http://example.com/page?param=1&another=2` will be transformed into `http://example.com/page?another=2`. +:::note Compatibility + +Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac and, Android with [CoreLibs][] v1.7 or later and AdGuard Browser Extension v3.6 or later. + +::: + **Regular expressions** You can also use regular expressions to match query parameters and/or their values: @@ -2416,76 +2292,6 @@ With these rules, specified UTM parameters will be removed from any request save `$removeparam` rules can also be disabled by `$document` and `$urlblock` exception rules. But basic exception rules without modifiers do not do that. For example, `@@||example.com^` will not disable `$removeparam=p` for requests to **example.com**, but `@@||example.com^$urlblock` will. -##### `$removeparam` modifier limitations {#removeparam-modifier-limitations} - -:::caution Limitations - -[AdGuard for Chrome MV3][ext-mv3] has some limitations: - -- Regular expressions, negation and allowlist rules are not supported. -- Group of similar `$removeparam` rules will be combined into one. Example: - - ```bash - ||testcases.adguard.com$xmlhttprequest,removeparam=p1case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=p2case1 - ||testcases.adguard.com$xmlhttprequest,removeparam=P3Case1 - $xmlhttprequest,removeparam=p1case2 - ``` - - is converted to - - ```bash - [ - { - "id": 1, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case1", - "p2case1", - "P3Case1" - ] - } - } - } - }, - "condition": { - "urlFilter": "||testcases.adguard.com", - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - }, - { - "id": 4, - "action": { - "type": "redirect", - "redirect": { - "transform": { - "queryTransform": { - "removeParams": [ - "p1case2" - ] - } - } - } - }, - "condition": { - "resourceTypes": [ - "xmlhttprequest" - ], - "isUrlFilterCaseSensitive": false - } - } - ] - ``` - -::: - :::caution Restrictions - Rules with `$removeparam` modifier can be used [**only in trusted filters**](#trusted-filters). @@ -2495,8 +2301,8 @@ With these rules, specified UTM parameters will be removed from any request save :::info Compatibility -- Rules with `$removeparam` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.7 or later, and AdGuard Browser Extension v3.6 or later. -- `$removeparam` syntax for regular expressions is supported AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.8 or later, and AdGuard Browser Extension v4.0 or later. +- Rules with `$removeparam` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Chrome, Firefox, and Edge. +- `$removeparam` syntax for regular expressions is supported by AdGuard Browser Extension v4.0 and AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.8 or later. - `POST` request types are supported only by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.10 or later, and AdGuard Browser Extension with [TSWebExtension][] v0.4.6 or later. ::: @@ -2511,7 +2317,7 @@ You will need some knowledge of regular expressions to use `$replace` modifier. - `$replace` rules apply to any text response, but will not apply to binary (`media`, `image`, `object`, etc.). - `$replace` rules do not apply if the size of the original response is more than 10 MB. -- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request natches two different rules, one of which has the `$replace` modifier, this rule will be applied. +- `$replace` rules have a higher priority than other basic rules (**including** exception rules). So if a request corresponds to two different rules one of which has the `$replace` modifier, this rule will be applied. - Document-level exception rules with `$content` or `$document` modifiers do disable `$replace` rules for requests matching them. - Other document-level exception rules (`$generichide`, `$elemhide` or `$jsinject` modifiers) are applied alongside `$replace` rules. It means that you can modify the page content with a `$replace` rule and disable cosmetic rules there at the same time. @@ -2571,17 +2377,18 @@ Rules with `$replace` modifier can be used [**only in trusted filters**](#truste :::info Compatibility -Rules with `$replace` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. +Rules with `$replace` modifier are supported by AdGuard for Windows, Mac, and Android and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on the network level. ::: #### **`urltransform`** {#urltransform-modifier} -The `$urltransform` rules allow you to modify the request URL by replacing text matched by a regular expression. +The `$urltransform` rules allow you to modify the request URL by replacing the text matched by the regular expression. **Features** -- `$urltransform` rules normally only apply to the path and query parts of the URL, see below for one exception. +- `$urltransform` rules apply to any request URL text. +- `$urltransform` rules can also **modify the query part** of the URL. - `$urltransform` will not be applied if the original URL is blocked by other rules. - `$urltransform` will be applied before `$removeparam` rules. @@ -2605,16 +2412,6 @@ urltransform = "/" regexp "/" replacement "/" modifiers In the `$urltransform` value, two characters must be escaped: the comma `,` and the dollar sign `$`. Use the backslash character `\` for this. For example, an escaped comma looks like this: `\,`. -**Changing the origin** - -:::info Compatibility - -This section only applies to AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.17 or later. - -::: - -As stated above, normally `$urltransform` rules are only allowed to change the path and query parts of the URL. However, if the rule's `regexp` begins with the string `^http`, then the full URL is searched and can be modified by the rule. Such a rule will not be applied if the URL transformation can not be achieved via an HTTP redirect (for example, if the request's method is `POST`). - **Examples** ```adblock @@ -2656,7 +2453,7 @@ However, `$urltransform` rules will **not be re-applied** in this case to avoid ||example.com/secondpath^$urltransform=/secondpath/firstpath/ ``` -the request to `https://example.com/firstpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. +the request to `https://example.com/fisrtpath` will be transformed to `https://example.com/secondpath` and the second rule will not be applied. **Disabling `$urltransform` rules** @@ -2679,7 +2476,7 @@ Rules with the `$urltransform` modifier are supported by AdGuard for Windows, Ad #### **`noop`** {#noop-modifier} -`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of arbitrary length and can appear in a rule as often as needed. +`noop` modifier does nothing and can be used solely to increase rules' readability. It consists of a sequence of underscore characters (`_`) of any length and can appear in a rule as many times as needed. **Examples** @@ -2740,13 +2537,13 @@ Each rule has its own priority, which is necessary when several rules match the :::note Collisions -When two rules with the same priority match the same request, the filter engine implementation determines which one is chosen. +When two rules with the same priority match the same request, it depends on the filtering engine implementation which one will be selected. ::: :::info -The concept of rule priorities becomes increasingly important in light of Manifest V3, as the existing rules need to be converted to declarativeNetRequest rules. +The concept of rule priorities becomes increasingly important in light of Manifest V3 as the existing rules need to be converted to declarativeNetRequest rules. ::: @@ -2780,8 +2577,6 @@ Modifier aliases (`1p`, `3p`, etc.) are not included in these categories, howeve - [`$domain`](#domain-modifier) with negated domains using `~`, - [`$match-case`](#match-case-modifier), - [`$method`](#method-modifier) with negated methods using `~`, -- [`$strict-first-party`](#strict-first-party-modifier), -- [`$strict-third-party`](#strict-third-party-modifier), - [`$third-party`](#third-party-modifier), - [`$to`](#to-modifier), - restricted [content-types](#content-type-modifiers) with `~`. @@ -2790,7 +2585,7 @@ When dealing with a negated domain, app, method, or content-type, we add **1 poi #### Defined content-type modifiers, defined methods, defined headers, $all, $popup, specific exceptions {#priority-category-2} -All valid content types: +All allowed content types: @@ -2840,7 +2635,7 @@ The `$popup` also belongs to this category, because it implicitly adds the modif If there is a `$method` modifier in the rule with allowed methods it adds `(50 + 50 / N)`, where `N` is the number of methods allowed, for example: `||example.com^$method=GET|POST|PUT` will add `50 + 50 / 3 = 50 + 16.6 = 67` to the total weight of the rule. -If there is a `$header` modifier in the rule, it adds `50`. +If there is a `$header` modifier in the rule it adds `50`. #### `$domain` or `$app` with allowed domains or applications {#priority-category-3} @@ -2936,14 +2731,14 @@ The [`$replace`](#replace-modifier) modifier takes precedence over all blocking However, basic rules may not be enough to block ads. Sometimes you need to hide an element or change part of the HTML code of a web page without breaking anything. The rules described in this section are created specifically for this purpose. -| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------------ |:------------------------:|:-------------------------------:|:---------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | -| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ❌ | ✅ | ❌ | ❌ | ❌ | -| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | -| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| Categories \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------------ |:------------------------:|:-------------------------------:|:-----------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [Element hiding](#cosmetic-elemhide-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | +| [CSS rules](#cosmetic-css-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Extended CSS](#extended-css-selectors) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [HTML filtering](#html-filtering-rules) | ✅ | ❌ | ✅ | ❌ | ❌ | ❌ | +| [JavaScript](#javascript-rules) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [Scriptlets](#scriptlets) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | :::note @@ -2998,7 +2793,7 @@ Element hiding rules are not dependent on each other. If there is a rule `exampl **Limitations** -Safari does not support both allowed and disallowed domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. +Safari does not support both permitted and restricted domains. So the rules like `example.org,~foo.example.org##.textad` are invalid in AdGuard for Safari. **Exceptions** @@ -3139,7 +2934,7 @@ Learn more about [how to debug extended selectors](#selectors-debugging-mode). :::note -Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)`, but the second one is more obvious. +Some pseudo-classes do not require selector before it. Still adding the [universal selector](https://www.w3.org/TR/selectors-4/#the-universal-selector) `*` makes an extended selector easier to read, even though it has no effect on the matching behavior. So selector `#block :has(> .inner)` works exactly like `#block *:has(> .inner)` but second one is more obvious. Pseudo-class names are case-insensitive, e.g. `:HAS()` works as `:has()`. Still the lower-case names are used commonly. @@ -3295,10 +3090,10 @@ the element `div#match` can be selected by any of these extended selectors: div:contains(banner) ! regular expression -div:contains(/as .*banner/) +div:contains(/as .* banner/) ! regular expression with flags -div:contains(/it .*banner/gi) +div:contains(/it .* banner/gi) ``` :::note @@ -3326,7 +3121,7 @@ The `:matches-css()` pseudo-class allows to match the element by its current sty - `target` — optional, standard or extended CSS selector, can be skipped for checking *any* element - `pseudo-element` — optional, valid standard pseudo-element, e.g. `before`, `after`, `first-line`, etc. - `property` — required, a name of CSS property to check the element for -- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic URL filtering rules or a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. +- `pattern` — required, a value pattern that is using the same simple wildcard matching as in the basic url filtering rules OR a regular expression. For this type of matching, AdGuard always does matching in a case-insensitive manner. In the case of a regular expression, the pattern looks like `/regexp/`. **Special characters escaping and unescaping** @@ -3496,7 +3291,7 @@ div:matches-property(memoizedProps.key="null") div:matches-property(memoizedProps._owner.src=/ad/) ``` -:::tip For filter maintainers +:::tip For filters maintainers To check properties of a specific element, do the following: @@ -3785,7 +3580,7 @@ In most cases, the basis and cosmetic rules are enough to filter ads. But someti :::info Compatibility -HTML filtering rules are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. +HTML filtering rules are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Firefox. Such rules do not work in extensions for other browsers because they are unable to modify content on network level. ::: @@ -3996,7 +3791,7 @@ We recommend to use this kind of exceptions only if it is not possible to change ## JavaScript rules {#javascript-rules} -AdGuard supports a special type of rules that allows you to inject any JavaScript code to websites pages. +AdGuard supports a special type of rules that allows you to inject any javascript code to websites pages. We **strongly recommend** using [scriptlets](#scriptlets) instead of JavaScript rules whenever possible. JS rules are supposed to help with debugging, but as a long-time solution a scriptlet rule should be used. @@ -4007,7 +3802,7 @@ rule = [domains] "#%#" script ``` - **`domains`** — domain restriction for the rule. Same principles as in [element hiding rules](#cosmetic-elemhide-rules). -- **`script`** — arbitrary JavaScript code **in one string**. +- **`script`** — arbitrary javascript code **in one string**. **Examples** @@ -4059,80 +3854,22 @@ AdGuard supports a lot of different scriptlets. In order to achieve cross-blocke ::: -**Blocking rules syntax** +**Syntax** ```text -[domains]#%#//scriptlet(name[, arguments]) +rule = [domains] "#%#//scriptlet(" scriptletName arguments ")" ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — required, a name of the scriptlet from AdGuard Scriptlets library; -- `arguments` — optional, a list of `string` arguments (no other types of arguments are supported). +- **`scriptletName`** — required, a name of the scriptlet from AdGuard's Scriptlets library +- **`arguments`** — optional, a list of `string` arguments (no other types of arguments are supported) **Examples** -1. Apply the `abort-on-property-read` scriptlet on all pages of `example.org` and its subdomains, and pass it an `alert` argument: - - ```adblock - example.org#%#//scriptlet('abort-on-property-read', 'alert') - ``` - -1. Remove the `branding` class from all `div[class^="inner"]` elements on all pages of `example.org` and its subdomains: - - ```adblock - example.org#%#//scriptlet('remove-class', 'branding', 'div[class^="inner"]') - ``` - -**Exception rules syntax** - -Exception rules can disable some scriptlets on particular domains. The syntax for exception scriptlet rules is similar to normal scriptlet rules but uses `#@%#` instead of `#%#`: - -```text -[domains]#@%#//scriptlet([name[, arguments]]) +```adblock +example.org#%#//scriptlet("abort-on-property-read", "alert") ``` -- `domains` — optional, a list of domains where the rule should be applied; -- `name` — optional, a name of the scriptlet to except from the applying; if not set, all scriptlets will not be applied; -- `arguments` — optional, a list of `string` arguments to match the same blocking rule and disable it. - -**Examples** - -1. Disable specific scriptlet rule so that only `abort-on-property-read` is applied only on `example.org` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read", "alert") - ``` - -1. Disable all `abort-on-property-read` scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet("abort-on-property-read") - ``` - -1. Disable all scriptlets for `example.com` and its subdomains: - - ```adblock - example.org,example.com#%#//scriptlet("abort-on-property-read", "alert") - example.com#@%#//scriptlet() - ``` - -1. Apply `set-constant` and `set-cookie` to any web page, but due to special scriptlet exception rule only the `set-constant` scriptlet will be applied on `example.org` and its subdomains: - - ```adblock - #%#//scriptlet('set-constant', 'adList', 'emptyArr') - #%#//scriptlet('set-cookie', 'accepted', 'true') - example.org#@%#//scriptlet('set-cookie') - ``` - -1. Apply `adjust-setInterval` to any web page and `set-local-storage-item` on `example.com` and its subdomains, but there are also multiple scriptlet exception rules, so no scriptlet rules will be applied on `example.com` and its subdomains: - - ```adblock - #%#//scriptlet('adjust-setInterval', 'count', '*', '0.001') - example.com#%#//scriptlet('set-local-storage-item', 'ALLOW_COOKIES', 'false') - example.com#@%#//scriptlet() - ``` +This rule will be applied to `example.org` and subdomains pages and will execute the `abort-on-property-read` scriptlet with the `alert` parameter. Learn more about [how to debug scriptlets](#debug-scriptlets). @@ -4142,8 +3879,6 @@ More information about scriptlets can be found [on GitHub](https://github.com/Ad Scriptlet rules are not supported by AdGuard Content Blocker. -The full syntax of scriptlet exception rules is supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.16 or later, and AdGuard Browser Extension for Chrome, Firefox, and Edge with [TSUrlFilter][] v3.0 or later. Previous versions only support exception rules that disable specific scriptlets. - ::: ### Trusted scriptlets {#trusted-scriptlets} @@ -4190,17 +3925,17 @@ For example, `[$domain=example.com,app=test_app]##selector`. In the modifiers values, the following characters must be escaped: `[`, `]`, `,`, and `\` (unless it is used for the escaping). Use `\` to escape them. For example, an escaped bracket looks like this: `\]`. -| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Chrome MV3][ext-mv3] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | -| ------------------------------------- |:------------------------:|:---------------------------------------------:|:------------------------------------------------:|:---------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| -| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | -| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ [*[1]](#non-basic-domain-modifier-limitations) | ✅ | ✅ | ✅ | ❌ | -| [$path](#non-basic-path-modifier) | ✅ | ✅ | ❌ | ✅ | ✅ | ✅ | ❌ | -| [$url](#non-basic-url-modifier) | ✅ | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ✅ [*[2]](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | +| Modifier \ Products | [CoreLibs apps][cl-apps] | [AdGuard for Chromium][ext-chr] | [AdGuard for Firefox][ext-ff] | [AdGuard for iOS][ios-app] | [AdGuard for Safari][ext-saf] | [AdGuard Content Blocker][and-cb] | +| ------------------------------------- |:------------------------:|:------------------------------------------:|:------------------------------------------:|:--------------------------:|:-----------------------------:|:---------------------------------:| +| [$app](#non-basic-app-modifier) | ✅ | ❌ | ❌ | ❌ | ❌ | ❌ | +| [$domain](#non-basic-domain-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$path](#non-basic-path-modifier) | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | +| [$url](#non-basic-url-modifier) | ✅ | 🧩 [*](#non-basic-url-modifier-limitations) | 🧩 [*](#non-basic-url-modifier-limitations) | ❌ | ❌ | ❌ | :::note - ✅ — fully supported -- ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details +- 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions - ❌ — not supported ::: @@ -4218,7 +3953,7 @@ In the modifiers values, the following characters must be escaped: `[`, `]`, `,` :::info Compatibility -Such rules with `$app` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. +Such rules with `$app` modifier are supported by AdGuard for Windows, Mac, and Android. ::: @@ -4239,17 +3974,9 @@ There are 2 ways to specify domain restrictions for non-basic rules: But rules with mixed style domains restriction are considered invalid. So, for example, the rule `[$domain=example.org]example.com##.textad` will be ignored. -### Non-basic `$domain` modifier limitations {#non-basic-domain-modifier-limitations} - -:::caution Limitations - -Since the non-basic `$domain` works the same as the basic one, it has the same [limitations](#domain-modifier-limitations). - -::: - :::info Compatibility -Such rules with `$domain` modifier are supported by AdGuard for Windows, AdGuard for Mac, AdGuard for Android, AdGuard Browser Extension for Chrome, for Chrome MV3, Firefox, and Edge. +Such rules with `$domain` modifier are supported by AdGuard for Windows, Mac, Android, and AdGuard Browser Extension for Chrome, Firefox, Edge. ::: @@ -4308,7 +4035,7 @@ where `pattern` is pretty much the same as [`pattern` of the basic rules](#basic #### `$url` modifier limitations {#non-basic-url-modifier-limitations} -:::caution Limitations +:::caution Restrictions In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with domain-specific rules and other non-basic modifiers — [`$domain`](#non-basic-domain-modifier) and [`$path`](#non-basic-path-modifier). For example, the rule `[$url=/category/*]example.com###textad` will not be applied. @@ -4316,17 +4043,17 @@ In AdGuard Browser Extension, non-basic `$url` modifier is not compatible with d :::info Compatibility -Rules with the `$url` modifier are supported by AdGuard for Windows, AdGuard for Mac, and AdGuard for Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. +Rules with the `$url` modifier are supported by AdGuard for Windows, Mac, and Android with [CoreLibs][] v1.11 or later, and AdGuard Browser Extension with [TSUrlFilter][] v3.0.0 or later. ::: -## Information for filter maintainers +## Information for filters maintainers If you maintain a third-party filter that is known to AdGuard, you might be interested in the information presented in this section. Please note that hints will be applied to registered filters only. The filter is considered to be registered and known by AdGuard, if it is present in the [known filters index](https://filters.adtidy.org/extension/chromium/filters.json). If you want your filter to be registered, please file an issue to [AdguardFilters repo](https://github.com/AdguardTeam/AdguardFilters). ### Preprocessor directives -We provide preprocessor directives that can be used by filter maintainers to improve compatibility with different ad blockers and provide: +We provide preprocessor directives that can be used by filters maintainers to improve compatibility with different ad blockers and provide: - [including a file](#include-directive) - [applying rules conditionally by ad blocker type](#conditions-directive) @@ -4342,7 +4069,7 @@ Preprocessor directives can be used in the user rules or in the custom filters. #### Including a file {#include-directive} -The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre-directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. +The `!#include` directive allows to include contents of a specified file into the filter. It supports only files from the same origin to make sure that the filter maintainer is in control of the specified file. The included file can also contain pre- directives (even other `!#include` directives). Ad blockers should consider the case of recursive `!#include` and implement a protection mechanism. **Syntax** @@ -4352,7 +4079,7 @@ The `!#include` directive allows to include contents of a specified file into th where `file_path` is a same origin absolute or relative file path to be included. -The files must originate from the same domain, but may be located in a different folder. +The files must originate from the same domain but may be located in a different folder. If included file is not found or unavailable, the whole filter update should fail. @@ -4376,7 +4103,7 @@ Filter URL: `https://example.org/path/filter.txt` #### Conditions {#conditions-directive} -Filter maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. +Filters maintainers can use conditions to supply different rules depending on the ad blocker type. A conditional directive beginning with an `!#if` directive must explicitly be terminated with an `!#endif` directive. Conditions support all basic logical operators. There are two possible scenarios: @@ -4657,7 +4384,7 @@ Open the browser console while on a web page to see the timing statistics for se **Always printed:** -- `selectorParsed` — text of the parsed selector, may differ from the input one +- `selectorParsed` — text of eventually parsed selector - `timings` — list of DOM nodes matched by the selector - `appliesCount` — total number of times that the selector has been applied on the page - `appliesTimings` — time that it took to apply the selector on the page, for each of the instances that it has been applied (in milliseconds) @@ -4743,13 +4470,11 @@ The following scriptlets also may be used for debug purposes: ### Product shortcuts {#what-product} -1. `CoreLibs apps` — [AdGuard for Windows](/adguard-for-windows/features/home-screen), [AdGuard for Mac](/adguard-for-mac/features/main), and [AdGuard for Android](/adguard-for-android/features/protection/ad-blocking) -1. `AdGuard for Chromium` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera -1. `AdGuard for Chrome MV3` — [AdGuard Browser Extension for Chrome MV3](/adguard-browser-extension/mv3-version) -1. `AdGuard for Firefox` — [AdGuard Browser Extension](/adguard-browser-extension/availability) for Firefox -1. `AdGuard for iOS` — [AdGuard for iOS](/adguard-for-ios/features/safari-protection) and AdGuard Pro for iOS (for mobile Safari browser) -1. `AdGuard for Safari` — [AdGuard for desktop Safari browser](/adguard-for-safari/features/general) -1. `AdGuard Content Blocker` — [Content Blocker](/adguard-content-blocker/overview) for Android mobile browsers: Samsung Internet and Yandex Browser +1. `CoreLibs apps` — AdGuard for Windows, AdGuard for Mac, and AdGuard for Android +1. `AdGuard for Chromium` — AdGuard Browser Extension for Chrome and other Chromium-based browsers such as Microsoft Edge, Opera +1. `AdGuard for Firefox` — AdGuard Browser Extension for Firefox +1. `AdGuard for iOS` — AdGuard for iOS and AdGuard Pro for iOS (for mobile Safari browser) +1. `AdGuard for Safari` — AdGuard for desktop Safari browser `AdGuard Content Blocker` — Content Blocker for Android mobile browsers: Samsung Internet and Yandex Browser ### Compatibility shortcuts {#what-compatibility} @@ -4758,29 +4483,21 @@ The following scriptlets also may be used for debug purposes: - ✅ — fully supported - ✅ * — supported, but reliability may vary or limitations may occur; check the modifier description for more details - 🧩 — may already be implemented in nightly or beta versions but is not yet supported in release versions -- ⏳ — feature that is planned to be implemented but is not yet available in any product +- ⏳ — feature that has been implemented or is planned to be implemented but is not yet available in any product - ❌ — not supported - 👎 — deprecated; still supported but will be removed in the future - 🚫 — removed and no longer supported ::: -[popup-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/epic/tswebextension/packages/tsurlfilter/src/rules/declarative-converter#popup - -[Sec-Fetch-Dest header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - -[jsinject-in-mv3]: https://github.com/AdguardTeam/tsurlfilter/tree/release/v3.1/packages/tsurlfilter/src/rules/declarative-converter#jsinject - [cl-apps]: #what-product "AdGuard for Windows, Mac, Android" [ext-chr]: #what-product "AdGuard Browser Extension for Chrome and other Chromium-based browsers" -[ext-mv3]: #what-product "AdGuard Browser Extension for Chrome MV3" [ext-ff]: #what-product "AdGuard Browser Extension for Firefox" [ios-app]: #what-product "AdGuard for iOS and AdGuard Pro for iOS" [ext-saf]: #what-product "AdGuard for Safari" [and-cb]: #what-product "AdGuard Content Blocker for Samsung Internet and Yandex Browser on Android" +[sec-fetch-dest-header]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Sec-Fetch-Dest [gh-filters-downloader]: https://github.com/AdguardTeam/FiltersDownloader [FiltersRegistry]: https://github.com/AdguardTeam/FiltersRegistry [CoreLibs]: https://adguard.com/en/blog/introducing-corelibs.html diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md index 4cf25b18560..5c11ef5cbd6 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/filter-policy.md @@ -41,14 +41,12 @@ AdGuard ad-blocking filters include: - AdGuard Base filter - AdGuard Mobile Ads filter - Regional filters divided by language principle — Chinese, Dutch, French, German, Japanese, Russian, Spanish/Portuguese, Turkish, and Ukrainian -- AdGuard Quick Fixes filter ### The purpose of these filters - **Base filter** is designed to block ads on English-language websites and those for which there is no separate filter. It also contains general filtering rules that apply to all sites regardless of language - **Mobile Ads filter** blocks advertisements on mobile versions of websites and within mobile apps. There is no segmentation based on language - **Regional filters** follow the same policy as the **Base filter**, but limited to websites in certain languages -- **Quick Fixes filter** used to quickly resolve critical content filtering issues on popular websites without updating the MV3 extension. The goal of ad-blocking filters is to block all types of advertising on websites, applications, and certain devices that can load ads from the Internet: diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md index c53c2ee53b4..1be581733ac 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/ad-filtering/how-ad-blocking-works.md @@ -3,7 +3,7 @@ title: How ad blocking works sidebar_position: 1 --- -AdGuard has many ad-blocking products for different platforms, each with its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. +AdGuard has many ad-blocking products for various platforms, and each product has its own unique features. But what unites them all is that they block ads and trackers. This article describes how ad blocking works from the inside. :::note diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/browsing-security.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/browsing-security.md index bed4b9c77bb..37eb5cfec4b 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/browsing-security.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/browsing-security.md @@ -5,13 +5,13 @@ sidebar_position: 3 Falling prey to phishing and malware remains a common issue. To enhance digital security, we’ve incorporated special filters in AdGuard products to shield you from malicious and phishing websites. To date, we’ve categorized over 15 million sites and built a database of 1.5 million websites known for phishing and malware. Using this database, AdGuard checks the websites you visit to protect you from online threats. -:::note +::: note We strictly do not collect or use any information about the websites you visit. ::: -## How does AdGuard check websites? +## How does AdGuard check websites?​ Each time you visit a website, your local client exchanges information with our backend server in the form of hashes and hash prefixes. Based on this exchange, the local client determines whether or not the website is listed in the potentially dangerous websites database. There is a difference in the scope of this check for apps and extensions. @@ -61,11 +61,11 @@ AdGuard maintains an extensive database of phishing and malware websites, and it We automatically analyze complaints about suspicious sites and spend a great deal of time keeping the database up-to-date, cleaning up false positives, and implementing mechanisms to prevent them in the future. -### Want to help? +### Want to help?​ Any help is welcome! If you encounter a phishing or malware website, please report it to . -### False-positive responses +### False-positive responses​ Occasionally, some non-malicious websites are added to AdGuard’s filters. We do our best to reduce the percentage of false positives, but they still occur. If you encounter this behavior from AdGuard, please report the false positive to our technical support at . diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md index 6523a9ee1e3..582fafe55cf 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/https-filtering/what-is-https-filtering.md @@ -7,7 +7,7 @@ sidebar_position: 1 HTTPS (HyperText Transfer Protocol Secure) is an extension of the HTTP protocol that supports encryption to increase security. This protocol is used to securely transmit valuable information like personal data, credit card details, etc. -Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of the free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). +Using HTTPS is highly advantageous because encrypted traffic is protected against eavesdropping by a third party, and we can only welcome this. HTTPS acceptance has been growing in recent years, mainly because it is [encouraged by Google](https://webmasters.googleblog.com/2014/08/https-as-ranking-signal.html) and also due to the emergence of a free certificate authority [Let’s Encrypt](https://en.wikipedia.org/wiki/Let's_Encrypt). The diagram below describes the difference between plain HTTP protocol and secure HTTPS protocol. @@ -15,17 +15,17 @@ The diagram below describes the difference between plain HTTP protocol and secur ### What is a security certificate? -Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really who or what it claims to be. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. +Simply put, HTTPS means data encryption. But there’s still a problem: how can you be sure that you’ve established an encrypted connection with the right website? That’s where security certificates come into play. A certificate serves as proof that the website is really what it tells you it is. If a website doesn’t have such a certificate, or if the certificate contains incorrect information, the browser will not allow you to establish a secure connection. It is important that the certificate a website uses is issued by a certificate authority (CA) trusted by your browser. Such a CA guarantees that the SSL certificate is, indeed, issued to the website’s owner. ### Why does AdGuard need to be able to filter HTTPS? -Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and x.com. +Most websites are now using HTTPS, and the same applies to advertising. Here are a few popular websites where you can’t remove ads without HTTPS filtering: youtube.com, facebook.com, and twitter.com. ### How does HTTPS filtering work? -If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). AdGuard can now see the data packets inside the secure connection and thus do its job — block ads and trackers. +If it were easy, HTTPS wouldn’t be that secure. When a browser attempts to connect to a server, AdGuard establishes two secure connections: one with the browser (or another app) and the other with the server. The browser must trust AdGuard and the connections it creates. For this purpose, AdGuard generates a special (and unique) root certificate and installs it into the system and, when it is required, into some browsers (e.g., Firefox). Thus, AdGuard can see what is happening inside the secure connection and do its job — block ads and trackers. -For better understanding, we have depicted this process: +For better understanding we depicted this process: ![How does HTTPS filtering work](https://cdn.adtidy.org/public/Adguard/Blog/https/what_is_https_filtering.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/license/what-is.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/license/what-is.md index ce4579cee8c..e74909f64f6 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/license/what-is.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/license/what-is.md @@ -1,5 +1,5 @@ --- -title: What is an AdGuard license? +title: What is AdGuard license? sidebar_position: 1 --- @@ -12,7 +12,7 @@ On the [purchase page](https://adguard.com/license.html), you can see the follow - **1-year subscriptions** — these licenses are renewed automatically every year or can be extended manually - Personal — up to 3 devices - Family — up to 9 devices -- **Lifetime** — these licenses are perpetual +- **Lifetime** — these licenses are not time-limited - Personal — up to 3 devices - Family — up to 9 devices diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/stealth-mode.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/stealth-mode.md index 77b251967d1..91f40a30692 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/stealth-mode.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/stealth-mode.md @@ -79,7 +79,7 @@ Enabling this option will prevent the browser from sending GPS data that could b ### Block Flash {#flash} -The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly increase website load times. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. +The Flash Player plugin has become increasingly vulnerable to such online threats as viruses and hackers; it may also significantly affect website loading time. Turning this setting on makes AdGuard block browsers' ability to detect components (such as plugins and ActiveXObject objects) that allow Flash to display content. This effectively means that browsers are unable to support Flash. ### Block Java {#java} @@ -95,7 +95,7 @@ You can also set an arbitrary value for Referer by entering it into the *Custom Note that to be able to filter traffic, AdGuard applications 'intercept' browser-to-server requests. Requests to ad, tracking, and phishing servers may be altered before sending them to the server or blocked completely. Same goes for the *Hide Referer from third parties* option: AdGuard intercepts HTTP(S) requests, in particular to remove or change the Referer header if this option is enabled. However, it happens only after these requests “leave” the browser. This means that if you monitor Referer inside the browser (for example, with the help of Chrome's Developer Tools), you will see the original Referer because the request hasn't reached AdGuard yet. You can use software like [Fiddler](https://www.telerik.com/fiddler) to make sure that Referer gets altered correctly. -On the other hand, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. +On the opposite, due to the nature of all browser extensions, AdGuard Browser Extension works 'inside' the browser. It will alter the Referer right then and there, so Developer Tools will show the desired Referer for your requests. ### Hide your User-Agent {#useragent} @@ -120,9 +120,3 @@ The Deep Packet Inspection is a system of deep analysis and filtering of traffic AdGuard can modify outgoing packet data so that the client does not fall under the DPI blocking criteria. This means that by enabling this option, users can get access to the content they want. Not all DPI systems can be bypassed at this time, but we are constantly working to improve this. The "Protect from DPI" feature is already implemented in AdGuard for Windows, AdGuard for Mac, and AdGuard for Android. - -:::caution - -If this feature is enabled in AdGuard for Windows, it may interfere with ESET antivirus. Anti-DPI will prevent ESET from filtering traffic, leaving blacklisted and malicious websites unblocked. - -::: diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/userscripts.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/userscripts.md index c517d7ac99d..efc75a8efd6 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/userscripts.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/general/userscripts.md @@ -4,7 +4,7 @@ sidebar_position: 5 toc_max_heading_level: 4 --- -Userscripts (we also call them "extensions") are, de facto, miniprograms written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. +Userscripts (we also call them "extensions") are, de-facto, mini-programs written in JavaScript. They modify or extend the functionality of one or more websites. Many AdGuard users may be already familiar with such userscripts as AdGuard Assistant, Popup Blocker, and AdGuard Extra. :::note Supported apps @@ -134,7 +134,7 @@ Here is a [mailto link](mailto:devteam@adguard.com?Subject=Userscript%20author%2 ##### Unsupported properties -These properties will be simply ignored by AdGuard. +These properties will be simply ignored by Adguard. ```text @unwrap diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/collect-har-file.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/collect-har-file.md index 20e022aef73..6ecb7eb5ecd 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/collect-har-file.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/collect-har-file.md @@ -1,5 +1,5 @@ --- -title: How to generate a HAR file +title: How to collect a HAR file sidebar_position: 1 --- diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/report-bugs.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/report-bugs.md index 0338945dbfc..9dc0e35955e 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/report-bugs.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/report-bugs.md @@ -17,7 +17,7 @@ Check if the bug hasn’t been reported before. We advise paying attention to bo ### How to describe a problem -Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we expect a bug report to include: +Try to provide as many details as possible — that'll make it easier for us to reproduce the bug and figure out how to fix it. Here’s what we’re expecting to see in a bug report: - Your app version - Your OS version diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/take-screenshot.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/take-screenshot.md index c137c7ae223..99e6055e131 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/take-screenshot.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/guides/take-screenshot.md @@ -52,17 +52,17 @@ On some notebooks you have to hold *Fn* and then press *PrtScn*. Windows captures the entire screen and copies it to the clipboard. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Hold down *Alt* and press *PrtScn* (or *Fn + Alt + PrtScn* on some laptops)** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***Win + Shift + S****** -After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut keys or by clicking the Paste button (usually in the top left corner of the screen) and then save it. +After you take a screenshot, it will be saved in the clipboard. In most cases, you will be able to paste it into a document that you are currently editing by using the *Ctrl + V* shortcut. Alternatively, if you need to save the screenshot into a file, you should open the standard **Paint** program (or any other app that can work with images). Paste your screenshot there using the same shortcut or by clicking the Paste button (usually in the top left corner of the screen) and then save it. -Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut keys. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. +Windows 8 and 10 let you take a screenshot very quickly with the *Win + PrtScn* shortcut. As soon as you press these keys, the screenshot will be automatically saved as a file to your *Pictures* → *Screenshots Folder*. There is also a dedicated program for taking screenshots called *Snipping Tool* that you can find via Start menu among standard programs of your computer. Snipping Tool lets you capture of any area of your desktop or the entire screen. After taking a screenshot using this program you can edit the picture and save it to any folder on your computer. @@ -70,26 +70,26 @@ Besides, you can also try using different apps for taking screenshots on your co ### macOS {#mac} -To take a screenshot on Mac, use the following shortcut keys: +To take a screenshot on Mac, use the following shortcut: - ***Press and hold ***⌘ Cmd + Shift + 3****** Your Mac will capture the entire screen and save it as a file on the desktop. -To take a screenshot of an active window, use the following shortcut keys: +To take a screenshot of an active window, use the following shortcut: - **Press and hold *⌘ Cmd + Shift + 4 + Space bar*. The pointer will change to a camera icon. Click the window to capture it. Press Esc to cancel taking a screenshot** -To take a screenshot of a specific area, use the following shortcut keys: +To take a screenshot of a specific area, use the following shortcut: - ***Press ***⌘ Cmd + Shift + 5******. Drag the crosshair to select the needed area. Release your mouse or trackpad to take a screenshot, press Esc to cancel it. -To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut keys: +To take a screenshot of the *Touch Bar* (MacBook Pro), use the following shortcut: - ***Press ***⌘ Cmd + Shift + 6****** Your Mac captures the entire *Touch Bar* and saves it as a file on the desktop. -To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcut keys above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut keys. +To copy a screenshot to the clipboard instead of saving it, hold down *Ctrl* together with any of the shortcuts above. Then you can paste the screenshot (from the clipboard) into a document or an image you are currently editing by using *Cmd + V* shortcut. You can also take screenshots by using **Preview** and choosing **Take screenshot** (of the selected area, window, or the entire screen). With **Preview** you can save your screenshots in JPG, TIFF, PDF, and other file formats. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/intro.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/intro.md index 8b3da975675..3600ce23223 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/intro.md @@ -20,4 +20,4 @@ But we also develop and maintain free browser extensions for all popular browser ## Not just ad blocking -AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge Base contains detailed information about any and all of them — feel free to jump to any article that interests you. +AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways. Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more. This Knowledge base contains detailed information about any and all of them — feel free to jump to any article that interests you. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md index cf402e668fb..963fdf6dfae 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/filters.md @@ -13,7 +13,7 @@ Websites constantly change the way they embed ads, and we add new rules to our f However, working with blocking filters requires specific skills. If you have them and know how to create rules, then head straight to our [AdGuard Filters repository](https://github.com/AdguardTeam/AdguardFilters) on GitHub. There you will find a lot of open issues, each one referencing a problem with some website problem — a missed ad, a false positive, etc. Choose any and suggest your own rules in comments. AdGuard filter engineers will review your suggestions, and if they find them appropriate, your rules will be added to AdGuard filters. -If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge Base](/general/ad-filtering/create-own-filters). +If you are not yet familiar with our filtering rule syntax, or maybe need a refresher, you'll find the basics about the syntax [in our Knowledge base](/general/ad-filtering/create-own-filters). ### Rewards {#rewards} diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md index fadef91a25e..5cc72b61a94 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/become-translator.md @@ -3,7 +3,7 @@ title: Becoming a translator/proofreader sidebar_position: 2 --- -If you want to help translate AdGuard products, websites, and Knowledge Bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. +If you want to help translate AdGuard products, websites, and Knowledge bases, go to [Crowdin](https://crowdin.com/) and sign up/log in there. ![crowdin *border](https://cdn.adtidy.org/public/Adguard/kb/en/ag-translations/main-screen.png) diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md index ebd6f3ceaad..7a29c291399 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/plural-forms.md @@ -38,7 +38,7 @@ When you are faced with a translation that requires the use of plurals, you may Here are some sources of information you can use. -[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` indicates the number of plural forms of the respective language. +[Localization Guide](http://docs.translatehouse.org/projects/localization-guide/en/latest/l10n/pluralforms.html) contains a wide list of languages. The number of plural forms for different languages is shown this way: `nplurals=2`, `nplurals=4` and so on. The numeral after the Equals sign `=` means the number of plural forms of the respective language. Also, you can get information about plural forms in the [Unicode Common Locale Data Repository](http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html#rules) (CLDR). The CLDR Plural Rules indicate an additional word form for decimal numbers (1.5; 2.3; 100.1…), but we don’t use them in AdGuard translations. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md index 88bd46d19cd..4eed3126873 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/program.md @@ -3,7 +3,7 @@ title: AdGuard translation program sidebar_position: 1 --- -You can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). +> **Disclaimer:** you can ask us any questions about translating AdGuard by sending an email to [translate@adguard.com](mailto:translate@adguard.com) or by joining our [Telegram chat](https://t.me/joinchat/UVYTLcHbr8JmOGIy). When it comes to translations, we at AdGuard always heavily rely on volunteers. diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md index b32ee730370..4c15594b389 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/translate/translation-priority.md @@ -3,13 +3,13 @@ title: How to prioritize the translations of Crowdin files sidebar_position: 5 --- -There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge Base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). +There are five major AdGuard projects on Crowdin — [AdGuard Applications](https://crowdin.com/project/adguard-applications), [AdGuard Websites](https://crowdin.com/project/adguard-websites), [AdGuard Ad Blocker Knowledge base](https://crowdin.com/project/adguard-knowledge-base), [AdGuard VPN Knowledge Base](https://crowdin.com/project/adguard-vpn-knowledge-base), and [AdGuard DNS Knowledge Base](https://crowdin.com/project/adguard-knowledge-bases). We do not have clear guidelines on which files or products of the *AdGuard Applications* project to start with. Just choose any product you like. There are just a couple of things we want to mention: -- The app is only available to users in those languages for which all translations have been completed on Crowdin; +- You can see the app only in those languages for which all translations are completed in Crowdin; - We recommend translating the descriptions for app stores in the second place, because without the translation of products themselves, the descriptions won't be needed. The situation is different in the *AdGuard Websites* project. Languages can be added to the site even if a full set of translations is not available. However, this depends on which files have already been translated. That's why we recommend that you start with the most important files — they are listed below: diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md index 771673d1c12..b0978dc0171 100644 --- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md +++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/miscellaneous/contribute/updating-knowledge-base.md @@ -1,28 +1,28 @@ --- -title: Updating the Knowledge Base +title: Updating the Knowledge base sidebar_position: 2 --- -The goal of AdGuard Ad Blocker Knowledge Base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. +The goal of AdGuard Ad Blocker Knowledge base is to provide everyone with the most up-to-date information on all kinds of AdGuard-related topics. But things constantly change, and sometimes an article doesn't reflect the current state of things anymore. This is why we placed all of our KB content on [GitHub](https://github.com/AdguardTeam/KnowledgeBase), and now literally anyone can contribute to it by suggesting edits and translations to existing articles, as well as totally new ones. ## How to suggest a change or write a new article {#suggest-change} -You can suggest changes to current articles and add new ones to our Knowledge Base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). +You can suggest changes to current articles and add new ones to our Knowledge base using the functionality of GitHub mentioned above. If you are unfamiliar with principles of working with the platform, start by reading [GitHub documentation](https://docs.github.com/en). -Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge Base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. +Once you are ready to start, work in the [KnowledgeBase repository](https://github.com/AdguardTeam/KnowledgeBase). All texts in our Knowledge base are written in `Markdown` markup language. Keep this in mind when editing or writing articles. Follow [this link](https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax) to learn more about Markdown syntax. -The Knowledge Base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). +The Knowledge base website is built using Docusaurus 2 — a modern static website generator. When suggesting changes or additions, take into account that all documents must comply with the principles of the platform. You can read about them in [Docusaurus Guides](https://docusaurus.io/docs/category/guides). -You can deploy this Knowledge Base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge Base's GitHub page. +You can deploy this Knowledge base locally on your computer to preview the changes you suggest. Detailed instructions on how to do this can be found [in the README file](https://github.com/AdguardTeam/KnowledgeBase#readme) on this Knowledge base's GitHub page. ## Translating articles {#translate-adguard} -Translation of the existing articles of the Knowledge Base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge Base. +Translation of the existing articles of the Knowledge base is carried out on [the Crowdin platform](https://crowdin.com/profile/adguard). All the details about translations and working with Crowdin can be found [in the dedicated article](../translate/guidelines) of the AdGuard Ad Blocker Knowledge base. -When working on AdGuard Knowledge Base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. +When working on AdGuard Knowledge base articles, you may meet strings containing plural forms that you should translate with extra attention. [In a separate article](../translate/plural-forms), we described in detail the difficulties that can arise when translating strings with plural forms and gave extensive instructions on how to work with them on the Crowdin platform. ## Working on open issues -Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge Base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge Base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. +Sometimes there exist [open tasks](https://github.com/AdguardTeam/KnowledgeBase/issues) related to updating the Knowledge base. You can help us speed up their completion [the same way](#suggest-change) you would suggest any other changes to the Knowledge base. Choose any issue that you find appealing and start working on it. If you have any questions — you can ask them right in the comments to that issue. diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index 946d5db03dd..dd2dd334fbf 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -1,5022 +1,71 @@ -lockfileVersion: '9.0' +lockfileVersion: '6.0' settings: autoInstallPeers: true excludeLinksFromLockfile: false -importers: - - .: - dependencies: - '@crowdin/cli': - specifier: 3.13.0 - version: 3.13.0 - '@docusaurus/core': - specifier: 2.2.0 - version: 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) - '@docusaurus/preset-classic': - specifier: 2.2.0 - version: 2.2.0(@algolia/client-search@4.24.0)(@swc/core@1.7.18)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(search-insights@2.17.0)(typescript@5.5.4) - '@mdx-js/react': - specifier: ^1.6.21 - version: 1.6.22(react@17.0.2) - '@svgr/webpack': - specifier: ^5.5.0 - version: 5.5.0 - '@swc/core': - specifier: ^1.7.18 - version: 1.7.18 - clsx: - specifier: ^1.1.1 - version: 1.2.1 - docusaurus-theme-search-typesense: - specifier: ^0.8.0 - version: 0.8.0(@algolia/client-search@4.24.0)(@babel/runtime@7.25.4)(@docusaurus/core@2.2.0)(@docusaurus/theme-common@2.2.0)(@swc/core@1.7.18)(@types/react@18.3.4)(algoliasearch@4.24.0)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) - file-loader: - specifier: ^6.2.0 - version: 6.2.0(webpack@5.94.0) - prism-react-renderer: - specifier: ^1.2.1 - version: 1.3.5(react@17.0.2) - react: - specifier: ^17.0.1 - version: 17.0.2 - react-dom: - specifier: ^17.0.1 - version: 17.0.2(react@17.0.2) - swc-loader: - specifier: ^0.2.6 - version: 0.2.6(@swc/core@1.7.18)(webpack@5.94.0) - url-loader: - specifier: ^4.1.1 - version: 4.1.1(file-loader@6.2.0)(webpack@5.94.0) - devDependencies: - markdownlint: - specifier: ^0.29.0 - version: 0.29.0 - markdownlint-cli: - specifier: ^0.35.0 - version: 0.35.0 - -packages: - - '@algolia/autocomplete-core@1.7.1': - resolution: {integrity: sha512-eiZw+fxMzNQn01S8dA/hcCpoWCOCwcIIEUtHHdzN5TGB3IpzLbuhqFeTfh2OUhhgkE8Uo17+wH+QJ/wYyQmmzg==} - - '@algolia/autocomplete-core@1.9.3': - resolution: {integrity: sha512-009HdfugtGCdC4JdXUbVJClA0q0zh24yyePn+KUGk3rP7j8FEe/m5Yo/z65gn6nP/cM39PxpzqKrL7A6fP6PPw==} - - '@algolia/autocomplete-plugin-algolia-insights@1.9.3': - resolution: {integrity: sha512-a/yTUkcO/Vyy+JffmAnTWbr4/90cLzw+CC3bRbhnULr/EM0fGNvM13oQQ14f2moLMcVDyAx/leczLlAOovhSZg==} - peerDependencies: - search-insights: '>= 1 < 3' - - '@algolia/autocomplete-preset-algolia@1.7.1': - resolution: {integrity: sha512-pJwmIxeJCymU1M6cGujnaIYcY3QPOVYZOXhFkWVM7IxKzy272BwCvMFMyc5NpG/QmiObBxjo7myd060OeTNJXg==} - peerDependencies: - '@algolia/client-search': ^4.9.1 - algoliasearch: ^4.9.1 - - '@algolia/autocomplete-preset-algolia@1.9.3': - resolution: {integrity: sha512-d4qlt6YmrLMYy95n5TB52wtNDr6EgAIPH81dvvvW8UmuWRgxEtY0NJiPwl/h95JtG2vmRM804M0DSwMCNZlzRA==} - peerDependencies: - '@algolia/client-search': '>= 4.9.1 < 6' - algoliasearch: '>= 4.9.1 < 6' - - '@algolia/autocomplete-shared@1.7.1': - resolution: {integrity: sha512-eTmGVqY3GeyBTT8IWiB2K5EuURAqhnumfktAEoHxfDY2o7vg2rSnO16ZtIG0fMgt3py28Vwgq42/bVEuaQV7pg==} - - '@algolia/autocomplete-shared@1.9.3': - resolution: {integrity: sha512-Wnm9E4Ye6Rl6sTTqjoymD+l8DjSTHsHboVRYrKgEt8Q7UHm9nYbqhN/i0fhUYA3OAEH7WA8x3jfpnmJm3rKvaQ==} - peerDependencies: - '@algolia/client-search': '>= 4.9.1 < 6' - algoliasearch: '>= 4.9.1 < 6' - - '@algolia/cache-browser-local-storage@4.24.0': - resolution: {integrity: sha512-t63W9BnoXVrGy9iYHBgObNXqYXM3tYXCjDSHeNwnsc324r4o5UiVKUiAB4THQ5z9U5hTj6qUvwg/Ez43ZD85ww==} - - '@algolia/cache-common@4.24.0': - resolution: {integrity: sha512-emi+v+DmVLpMGhp0V9q9h5CdkURsNmFC+cOS6uK9ndeJm9J4TiqSvPYVu+THUP8P/S08rxf5x2P+p3CfID0Y4g==} - - '@algolia/cache-in-memory@4.24.0': - resolution: {integrity: sha512-gDrt2so19jW26jY3/MkFg5mEypFIPbPoXsQGQWAi6TrCPsNOSEYepBMPlucqWigsmEy/prp5ug2jy/N3PVG/8w==} - - '@algolia/client-account@4.24.0': - resolution: {integrity: sha512-adcvyJ3KjPZFDybxlqnf+5KgxJtBjwTPTeyG2aOyoJvx0Y8dUQAEOEVOJ/GBxX0WWNbmaSrhDURMhc+QeevDsA==} - - '@algolia/client-analytics@4.24.0': - resolution: {integrity: sha512-y8jOZt1OjwWU4N2qr8G4AxXAzaa8DBvyHTWlHzX/7Me1LX8OayfgHexqrsL4vSBcoMmVw2XnVW9MhL+Y2ZDJXg==} - - '@algolia/client-common@4.24.0': - resolution: {integrity: sha512-bc2ROsNL6w6rqpl5jj/UywlIYC21TwSSoFHKl01lYirGMW+9Eek6r02Tocg4gZ8HAw3iBvu6XQiM3BEbmEMoiA==} - - '@algolia/client-personalization@4.24.0': - resolution: {integrity: sha512-l5FRFm/yngztweU0HdUzz1rC4yoWCFo3IF+dVIVTfEPg906eZg5BOd1k0K6rZx5JzyyoP4LdmOikfkfGsKVE9w==} - - '@algolia/client-search@4.24.0': - resolution: {integrity: sha512-uRW6EpNapmLAD0mW47OXqTP8eiIx5F6qN9/x/7HHO6owL3N1IXqydGwW5nhDFBrV+ldouro2W1VX3XlcUXEFCA==} - - '@algolia/events@4.0.1': - resolution: {integrity: sha512-FQzvOCgoFXAbf5Y6mYozw2aj5KCJoA3m4heImceldzPSMbdyS4atVjJzXKMsfX3wnZTFYwkkt8/z8UesLHlSBQ==} - - '@algolia/logger-common@4.24.0': - resolution: {integrity: sha512-LLUNjkahj9KtKYrQhFKCzMx0BY3RnNP4FEtO+sBybCjJ73E8jNdaKJ/Dd8A/VA4imVHP5tADZ8pn5B8Ga/wTMA==} - - '@algolia/logger-console@4.24.0': - resolution: {integrity: sha512-X4C8IoHgHfiUROfoRCV+lzSy+LHMgkoEEU1BbKcsfnV0i0S20zyy0NLww9dwVHUWNfPPxdMU+/wKmLGYf96yTg==} - - '@algolia/recommend@4.24.0': - resolution: {integrity: sha512-P9kcgerfVBpfYHDfVZDvvdJv0lEoCvzNlOy2nykyt5bK8TyieYyiD0lguIJdRZZYGre03WIAFf14pgE+V+IBlw==} - - '@algolia/requester-browser-xhr@4.24.0': - resolution: {integrity: sha512-Z2NxZMb6+nVXSjF13YpjYTdvV3032YTBSGm2vnYvYPA6mMxzM3v5rsCiSspndn9rzIW4Qp1lPHBvuoKJV6jnAA==} - - '@algolia/requester-common@4.24.0': - resolution: {integrity: sha512-k3CXJ2OVnvgE3HMwcojpvY6d9kgKMPRxs/kVohrwF5WMr2fnqojnycZkxPoEg+bXm8fi5BBfFmOqgYztRtHsQA==} - - '@algolia/requester-node-http@4.24.0': - resolution: {integrity: sha512-JF18yTjNOVYvU/L3UosRcvbPMGT9B+/GQWNWnenIImglzNVGpyzChkXLnrSf6uxwVNO6ESGu6oN8MqcGQcjQJw==} - - '@algolia/transporter@4.24.0': - resolution: {integrity: sha512-86nI7w6NzWxd1Zp9q3413dRshDqAzSbsQjhcDhPIatEFiZrL1/TjnHL8S7jVKFePlIMzDsZWXAXwXzcok9c5oA==} - - '@ampproject/remapping@2.3.0': - resolution: {integrity: sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw==} - engines: {node: '>=6.0.0'} - - '@babel/code-frame@7.24.7': - resolution: {integrity: sha512-BcYH1CVJBO9tvyIZ2jVeXgSIMvGZ2FDRvDdOIVQyuklNKSsx+eppDEBq/g47Ayw+RqNFE+URvOShmf+f/qwAlA==} - engines: {node: '>=6.9.0'} - - '@babel/compat-data@7.25.4': - resolution: {integrity: sha512-+LGRog6RAsCJrrrg/IO6LGmpphNe5DiK30dGjCoxxeGv49B10/3XYGxPsAwrDlMFcFEvdAUavDT8r9k/hSyQqQ==} - engines: {node: '>=6.9.0'} - - '@babel/core@7.12.9': - resolution: {integrity: sha512-gTXYh3M5wb7FRXQy+FErKFAv90BnlOuNn1QkCK2lREoPAjrQCO49+HVSrFoe5uakFAF5eenS75KbO2vQiLrTMQ==} - engines: {node: '>=6.9.0'} - - '@babel/core@7.25.2': - resolution: {integrity: sha512-BBt3opiCOxUr9euZ5/ro/Xv8/V7yJ5bjYMqG/C1YAo8MIKAnumZalCN+msbci3Pigy4lIQfPUpfMM27HMGaYEA==} - engines: {node: '>=6.9.0'} - - '@babel/generator@7.25.5': - resolution: {integrity: sha512-abd43wyLfbWoxC6ahM8xTkqLpGB2iWBVyuKC9/srhFunCd1SDNrV1s72bBpK4hLj8KLzHBBcOblvLQZBNw9r3w==} - engines: {node: '>=6.9.0'} - - '@babel/helper-annotate-as-pure@7.24.7': - resolution: {integrity: sha512-BaDeOonYvhdKw+JoMVkAixAAJzG2jVPIwWoKBPdYuY9b452e2rPuI9QPYh3KpofZ3pW2akOmwZLOiOsHMiqRAg==} - engines: {node: '>=6.9.0'} - - '@babel/helper-builder-binary-assignment-operator-visitor@7.24.7': - resolution: {integrity: sha512-xZeCVVdwb4MsDBkkyZ64tReWYrLRHlMN72vP7Bdm3OUOuyFZExhsHUUnuWnm2/XOlAJzR0LfPpB56WXZn0X/lA==} - engines: {node: '>=6.9.0'} - - '@babel/helper-compilation-targets@7.25.2': - resolution: {integrity: sha512-U2U5LsSaZ7TAt3cfaymQ8WHh0pxvdHoEk6HVpaexxixjyEquMh0L0YNJNM6CTGKMXV1iksi0iZkGw4AcFkPaaw==} - engines: {node: '>=6.9.0'} - - '@babel/helper-create-class-features-plugin@7.25.4': - resolution: {integrity: sha512-ro/bFs3/84MDgDmMwbcHgDa8/E6J3QKNTk4xJJnVeFtGE+tL0K26E3pNxhYz2b67fJpt7Aphw5XcploKXuCvCQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/helper-create-regexp-features-plugin@7.25.2': - resolution: {integrity: sha512-+wqVGP+DFmqwFD3EH6TMTfUNeqDehV3E/dl+Sd54eaXqm17tEUNbEIn4sVivVowbvUpOtIGxdo3GoXyDH9N/9g==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/helper-define-polyfill-provider@0.6.2': - resolution: {integrity: sha512-LV76g+C502biUK6AyZ3LK10vDpDyCzZnhZFXkH1L75zHPj68+qc8Zfpx2th+gzwA2MzyK+1g/3EPl62yFnVttQ==} - peerDependencies: - '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 - - '@babel/helper-member-expression-to-functions@7.24.8': - resolution: {integrity: sha512-LABppdt+Lp/RlBxqrh4qgf1oEH/WxdzQNDJIu5gC/W1GyvPVrOBiItmmM8wan2fm4oYqFuFfkXmlGpLQhPY8CA==} - engines: {node: '>=6.9.0'} - - '@babel/helper-module-imports@7.24.7': - resolution: {integrity: sha512-8AyH3C+74cgCVVXow/myrynrAGv+nTVg5vKu2nZph9x7RcRwzmh0VFallJuFTZ9mx6u4eSdXZfcOzSqTUm0HCA==} - engines: {node: '>=6.9.0'} - - '@babel/helper-module-transforms@7.25.2': - resolution: {integrity: sha512-BjyRAbix6j/wv83ftcVJmBt72QtHI56C7JXZoG2xATiLpmoC7dpd8WnkikExHDVPpi/3qCmO6WY1EaXOluiecQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/helper-optimise-call-expression@7.24.7': - resolution: {integrity: sha512-jKiTsW2xmWwxT1ixIdfXUZp+P5yURx2suzLZr5Hi64rURpDYdMW0pv+Uf17EYk2Rd428Lx4tLsnjGJzYKDM/6A==} - engines: {node: '>=6.9.0'} - - '@babel/helper-plugin-utils@7.10.4': - resolution: {integrity: sha512-O4KCvQA6lLiMU9l2eawBPMf1xPP8xPfB3iEQw150hOVTqj/rfXz0ThTb4HEzqQfs2Bmo5Ay8BzxfzVtBrr9dVg==} - - '@babel/helper-plugin-utils@7.24.8': - resolution: {integrity: sha512-FFWx5142D8h2Mgr/iPVGH5G7w6jDn4jUSpZTyDnQO0Yn7Ks2Kuz6Pci8H6MPCoUJegd/UZQ3tAvfLCxQSnWWwg==} - engines: {node: '>=6.9.0'} - - '@babel/helper-remap-async-to-generator@7.25.0': - resolution: {integrity: sha512-NhavI2eWEIz/H9dbrG0TuOicDhNexze43i5z7lEqwYm0WEZVTwnPpA0EafUTP7+6/W79HWIP2cTe3Z5NiSTVpw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/helper-replace-supers@7.25.0': - resolution: {integrity: sha512-q688zIvQVYtZu+i2PsdIu/uWGRpfxzr5WESsfpShfZECkO+d2o+WROWezCi/Q6kJ0tfPa5+pUGUlfx2HhrA3Bg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/helper-simple-access@7.24.7': - resolution: {integrity: sha512-zBAIvbCMh5Ts+b86r/CjU+4XGYIs+R1j951gxI3KmmxBMhCg4oQMsv6ZXQ64XOm/cvzfU1FmoCyt6+owc5QMYg==} - engines: {node: '>=6.9.0'} - - '@babel/helper-skip-transparent-expression-wrappers@7.24.7': - resolution: {integrity: sha512-IO+DLT3LQUElMbpzlatRASEyQtfhSE0+m465v++3jyyXeBTBUjtVZg28/gHeV5mrTJqvEKhKroBGAvhW+qPHiQ==} - engines: {node: '>=6.9.0'} - - '@babel/helper-string-parser@7.24.8': - resolution: {integrity: sha512-pO9KhhRcuUyGnJWwyEgnRJTSIZHiT+vMD0kPeD+so0l7mxkMT19g3pjY9GTnHySck/hDzq+dtW/4VgnMkippsQ==} - engines: {node: '>=6.9.0'} - - '@babel/helper-validator-identifier@7.24.7': - resolution: {integrity: sha512-rR+PBcQ1SMQDDyF6X0wxtG8QyLCgUB0eRAGguqRLfkCA87l7yAP7ehq8SNj96OOGTO8OBV70KhuFYcIkHXOg0w==} - engines: {node: '>=6.9.0'} - - '@babel/helper-validator-option@7.24.8': - resolution: {integrity: sha512-xb8t9tD1MHLungh/AIoWYN+gVHaB9kwlu8gffXGSt3FFEIT7RjS+xWbc2vUD1UTZdIpKj/ab3rdqJ7ufngyi2Q==} - engines: {node: '>=6.9.0'} - - '@babel/helper-wrap-function@7.25.0': - resolution: {integrity: sha512-s6Q1ebqutSiZnEjaofc/UKDyC4SbzV5n5SrA2Gq8UawLycr3i04f1dX4OzoQVnexm6aOCh37SQNYlJ/8Ku+PMQ==} - engines: {node: '>=6.9.0'} - - '@babel/helpers@7.25.0': - resolution: {integrity: sha512-MjgLZ42aCm0oGjJj8CtSM3DB8NOOf8h2l7DCTePJs29u+v7yO/RBX9nShlKMgFnRks/Q4tBAe7Hxnov9VkGwLw==} - engines: {node: '>=6.9.0'} - - '@babel/highlight@7.24.7': - resolution: {integrity: sha512-EStJpq4OuY8xYfhGVXngigBJRWxftKX9ksiGDnmlY3o7B/V7KIAc9X4oiK87uPJSc/vs5L869bem5fhZa8caZw==} - engines: {node: '>=6.9.0'} - - '@babel/parser@7.25.4': - resolution: {integrity: sha512-nq+eWrOgdtu3jG5Os4TQP3x3cLA8hR8TvJNjD8vnPa20WGycimcparWnLK4jJhElTK6SDyuJo1weMKO/5LpmLA==} - engines: {node: '>=6.0.0'} - hasBin: true - - '@babel/plugin-bugfix-firefox-class-in-computed-class-key@7.25.3': - resolution: {integrity: sha512-wUrcsxZg6rqBXG05HG1FPYgsP6EvwF4WpBbxIpWIIYnH8wG0gzx3yZY3dtEHas4sTAOGkbTsc9EGPxwff8lRoA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/plugin-bugfix-safari-class-field-initializer-scope@7.25.0': - resolution: {integrity: sha512-Bm4bH2qsX880b/3ziJ8KD711LT7z4u8CFudmjqle65AZj/HNUFhEf90dqYv6O86buWvSBmeQDjv0Tn2aF/bIBA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@7.25.0': - resolution: {integrity: sha512-lXwdNZtTmeVOOFtwM/WDe7yg1PL8sYhRk/XH0FzbR2HDQ0xC+EnQ/JHeoMYSavtU115tnUk0q9CDyq8si+LMAA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.24.7': - resolution: {integrity: sha512-+izXIbke1T33mY4MSNnrqhPXDz01WYhEf3yF5NbnUtkiNnm+XBZJl3kNfoK6NKmYlz/D07+l2GWVK/QfDkNCuQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.13.0 - - '@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@7.25.0': - resolution: {integrity: sha512-tggFrk1AIShG/RUQbEwt2Tr/E+ObkfwrPjR6BjbRvsx24+PSjK8zrq0GWPNCjo8qpRx4DuJzlcvWJqlm+0h3kw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/plugin-proposal-object-rest-spread@7.12.1': - resolution: {integrity: sha512-s6SowJIjzlhx8o7lsFx5zmY4At6CTtDvgNQDdPzkBQucle58A6b/TTeEBYtyDgmcXjUTM+vE8YOGHZzzbc/ioA==} - deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead. - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2': - resolution: {integrity: sha512-SOSkfJDddaM7mak6cPEpswyTRnuRltl429hMraQEglW+OkovnCzsiszTmsrlY//qLFjCpQDFRvjdm2wA5pPm9w==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-async-generators@7.8.4': - resolution: {integrity: sha512-tycmZxkGfZaxhMRbXlPXuVFpdWlXpir2W4AMhSJgRKzk/eDlIXOhb2LHWoLpDF7TEHylV5zNhykX6KAgHJmTNw==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-class-properties@7.12.13': - resolution: {integrity: sha512-fm4idjKla0YahUNgFNLCB0qySdsoPiZP3iQE3rky0mBUtMZ23yDJ9SJdg6dXTSDnulOVqiF3Hgr9nbXvXTQZYA==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-class-static-block@7.14.5': - resolution: {integrity: sha512-b+YyPmr6ldyNnM6sqYeMWE+bgJcJpO6yS4QD7ymxgH34GBPNDM/THBh8iunyvKIZztiwLH4CJZ0RxTk9emgpjw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-dynamic-import@7.8.3': - resolution: {integrity: sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-export-namespace-from@7.8.3': - resolution: {integrity: sha512-MXf5laXo6c1IbEbegDmzGPwGNTsHZmEy6QGznu5Sh2UCWvueywb2ee+CCE4zQiZstxU9BMoQO9i6zUFSY0Kj0Q==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-import-assertions@7.24.7': - resolution: {integrity: sha512-Ec3NRUMoi8gskrkBe3fNmEQfxDvY8bgfQpz6jlk/41kX9eUjvpyqWU7PBP/pLAvMaSQjbMNKJmvX57jP+M6bPg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-import-attributes@7.24.7': - resolution: {integrity: sha512-hbX+lKKeUMGihnK8nvKqmXBInriT3GVjzXKFriV3YC6APGxMbP8RZNFwy91+hocLXq90Mta+HshoB31802bb8A==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-import-meta@7.10.4': - resolution: {integrity: sha512-Yqfm+XDx0+Prh3VSeEQCPU81yC+JWZ2pDPFSS4ZdpfZhp4MkFMaDC1UqseovEKwSUpnIL7+vK+Clp7bfh0iD7g==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-json-strings@7.8.3': - resolution: {integrity: sha512-lY6kdGpWHvjoe2vk4WrAapEuBR69EMxZl+RoGRhrFGNYVK8mOPAW8VfbT/ZgrFbXlDNiiaxQnAtgVCZ6jv30EA==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-jsx@7.12.1': - resolution: {integrity: sha512-1yRi7yAtB0ETgxdY9ti/p2TivUxJkTdhu/ZbF9MshVGqOx1TdB3b7xCXs49Fupgg50N45KcAsRP/ZqWjs9SRjg==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-jsx@7.24.7': - resolution: {integrity: sha512-6ddciUPe/mpMnOKv/U+RSd2vvVy+Yw/JfBB0ZHYjEZt9NLHmCUylNYlsbqCCS1Bffjlb0fCwC9Vqz+sBz6PsiQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-logical-assignment-operators@7.10.4': - resolution: {integrity: sha512-d8waShlpFDinQ5MtvGU9xDAOzKH47+FFoney2baFIoMr952hKOLp1HR7VszoZvOsV/4+RRszNY7D17ba0te0ig==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-nullish-coalescing-operator@7.8.3': - resolution: {integrity: sha512-aSff4zPII1u2QD7y+F8oDsz19ew4IGEJg9SVW+bqwpwtfFleiQDMdzA/R+UlWDzfnHFCxxleFT0PMIrR36XLNQ==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-numeric-separator@7.10.4': - resolution: {integrity: sha512-9H6YdfkcK/uOnY/K7/aA2xpzaAgkQn37yzWUMRK7OaPOqOpGS1+n0H5hxT9AUw9EsSjPW8SVyMJwYRtWs3X3ug==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-object-rest-spread@7.8.3': - resolution: {integrity: sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-optional-catch-binding@7.8.3': - resolution: {integrity: sha512-6VPD0Pc1lpTqw0aKoeRTMiB+kWhAoT24PA+ksWSBrFtl5SIRVpZlwN3NNPQjehA2E/91FV3RjLWoVTglWcSV3Q==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-optional-chaining@7.8.3': - resolution: {integrity: sha512-KoK9ErH1MBlCPxV0VANkXW2/dw4vlbGDrFgz8bmUsBGYkFRcbRwMh6cIJubdPrkxRwuGdtCk0v/wPTKbQgBjkg==} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-private-property-in-object@7.14.5': - resolution: {integrity: sha512-0wVnp9dxJ72ZUJDV27ZfbSj6iHLoytYZmh3rFcxNnvsJF3ktkzLDZPy/mA17HGsaQT3/DQsWYX1f1QGWkCoVUg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-top-level-await@7.14.5': - resolution: {integrity: sha512-hx++upLv5U1rgYfwe1xBQUhRmU41NEvpUvrp8jkrSCdvGSnM5/qdRMtylJ6PG5OFkBaHkbTAKTnd3/YyESRHFw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-typescript@7.25.4': - resolution: {integrity: sha512-uMOCoHVU52BsSWxPOMVv5qKRdeSlPuImUCB2dlPuBSU+W2/ROE7/Zg8F2Kepbk+8yBa68LlRKxO+xgEVWorsDg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-syntax-unicode-sets-regex@7.18.6': - resolution: {integrity: sha512-727YkEAPwSIQTv5im8QHz3upqp92JTWhidIC81Tdx4VJYIte/VndKf1qKrfnnhPLiPghStWfvC/iFaMCQu7Nqg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/plugin-transform-arrow-functions@7.24.7': - resolution: {integrity: sha512-Dt9LQs6iEY++gXUwY03DNFat5C2NbO48jj+j/bSAz6b3HgPs39qcPiYt77fDObIcFwj3/C2ICX9YMwGflUoSHQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-async-generator-functions@7.25.4': - resolution: {integrity: sha512-jz8cV2XDDTqjKPwVPJBIjORVEmSGYhdRa8e5k5+vN+uwcjSrSxUaebBRa4ko1jqNF2uxyg8G6XYk30Jv285xzg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-async-to-generator@7.24.7': - resolution: {integrity: sha512-SQY01PcJfmQ+4Ash7NE+rpbLFbmqA2GPIgqzxfFTL4t1FKRq4zTms/7htKpoCUI9OcFYgzqfmCdH53s6/jn5fA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-block-scoped-functions@7.24.7': - resolution: {integrity: sha512-yO7RAz6EsVQDaBH18IDJcMB1HnrUn2FJ/Jslc/WtPPWcjhpUJXU/rjbwmluzp7v/ZzWcEhTMXELnnsz8djWDwQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-block-scoping@7.25.0': - resolution: {integrity: sha512-yBQjYoOjXlFv9nlXb3f1casSHOZkWr29NX+zChVanLg5Nc157CrbEX9D7hxxtTpuFy7Q0YzmmWfJxzvps4kXrQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-class-properties@7.25.4': - resolution: {integrity: sha512-nZeZHyCWPfjkdU5pA/uHiTaDAFUEqkpzf1YoQT2NeSynCGYq9rxfyI3XpQbfx/a0hSnFH6TGlEXvae5Vi7GD8g==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-class-static-block@7.24.7': - resolution: {integrity: sha512-HMXK3WbBPpZQufbMG4B46A90PkuuhN9vBCb5T8+VAHqvAqvcLi+2cKoukcpmUYkszLhScU3l1iudhrks3DggRQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.12.0 - - '@babel/plugin-transform-classes@7.25.4': - resolution: {integrity: sha512-oexUfaQle2pF/b6E0dwsxQtAol9TLSO88kQvym6HHBWFliV2lGdrPieX+WgMRLSJDVzdYywk7jXbLPuO2KLTLg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-computed-properties@7.24.7': - resolution: {integrity: sha512-25cS7v+707Gu6Ds2oY6tCkUwsJ9YIDbggd9+cu9jzzDgiNq7hR/8dkzxWfKWnTic26vsI3EsCXNd4iEB6e8esQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-destructuring@7.24.8': - resolution: {integrity: sha512-36e87mfY8TnRxc7yc6M9g9gOB7rKgSahqkIKwLpz4Ppk2+zC2Cy1is0uwtuSG6AE4zlTOUa+7JGz9jCJGLqQFQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-dotall-regex@7.24.7': - resolution: {integrity: sha512-ZOA3W+1RRTSWvyqcMJDLqbchh7U4NRGqwRfFSVbOLS/ePIP4vHB5e8T8eXcuqyN1QkgKyj5wuW0lcS85v4CrSw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-duplicate-keys@7.24.7': - resolution: {integrity: sha512-JdYfXyCRihAe46jUIliuL2/s0x0wObgwwiGxw/UbgJBr20gQBThrokO4nYKgWkD7uBaqM7+9x5TU7NkExZJyzw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-duplicate-named-capturing-groups-regex@7.25.0': - resolution: {integrity: sha512-YLpb4LlYSc3sCUa35un84poXoraOiQucUTTu8X1j18JV+gNa8E0nyUf/CjZ171IRGr4jEguF+vzJU66QZhn29g==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/plugin-transform-dynamic-import@7.24.7': - resolution: {integrity: sha512-sc3X26PhZQDb3JhORmakcbvkeInvxz+A8oda99lj7J60QRuPZvNAk9wQlTBS1ZynelDrDmTU4pw1tyc5d5ZMUg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-exponentiation-operator@7.24.7': - resolution: {integrity: sha512-Rqe/vSc9OYgDajNIK35u7ot+KeCoetqQYFXM4Epf7M7ez3lWlOjrDjrwMei6caCVhfdw+mIKD4cgdGNy5JQotQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-export-namespace-from@7.24.7': - resolution: {integrity: sha512-v0K9uNYsPL3oXZ/7F9NNIbAj2jv1whUEtyA6aujhekLs56R++JDQuzRcP2/z4WX5Vg/c5lE9uWZA0/iUoFhLTA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-for-of@7.24.7': - resolution: {integrity: sha512-wo9ogrDG1ITTTBsy46oGiN1dS9A7MROBTcYsfS8DtsImMkHk9JXJ3EWQM6X2SUw4x80uGPlwj0o00Uoc6nEE3g==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-function-name@7.25.1': - resolution: {integrity: sha512-TVVJVdW9RKMNgJJlLtHsKDTydjZAbwIsn6ySBPQaEAUU5+gVvlJt/9nRmqVbsV/IBanRjzWoaAQKLoamWVOUuA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-json-strings@7.24.7': - resolution: {integrity: sha512-2yFnBGDvRuxAaE/f0vfBKvtnvvqU8tGpMHqMNpTN2oWMKIR3NqFkjaAgGwawhqK/pIN2T3XdjGPdaG0vDhOBGw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-literals@7.25.2': - resolution: {integrity: sha512-HQI+HcTbm9ur3Z2DkO+jgESMAMcYLuN/A7NRw9juzxAezN9AvqvUTnpKP/9kkYANz6u7dFlAyOu44ejuGySlfw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-logical-assignment-operators@7.24.7': - resolution: {integrity: sha512-4D2tpwlQ1odXmTEIFWy9ELJcZHqrStlzK/dAOWYyxX3zT0iXQB6banjgeOJQXzEc4S0E0a5A+hahxPaEFYftsw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-member-expression-literals@7.24.7': - resolution: {integrity: sha512-T/hRC1uqrzXMKLQ6UCwMT85S3EvqaBXDGf0FaMf4446Qx9vKwlghvee0+uuZcDUCZU5RuNi4781UQ7R308zzBw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-modules-amd@7.24.7': - resolution: {integrity: sha512-9+pB1qxV3vs/8Hdmz/CulFB8w2tuu6EB94JZFsjdqxQokwGa9Unap7Bo2gGBGIvPmDIVvQrom7r5m/TCDMURhg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-modules-commonjs@7.24.8': - resolution: {integrity: sha512-WHsk9H8XxRs3JXKWFiqtQebdh9b/pTk4EgueygFzYlTKAg0Ud985mSevdNjdXdFBATSKVJGQXP1tv6aGbssLKA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-modules-systemjs@7.25.0': - resolution: {integrity: sha512-YPJfjQPDXxyQWg/0+jHKj1llnY5f/R6a0p/vP4lPymxLu7Lvl4k2WMitqi08yxwQcCVUUdG9LCUj4TNEgAp3Jw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-modules-umd@7.24.7': - resolution: {integrity: sha512-3aytQvqJ/h9z4g8AsKPLvD4Zqi2qT+L3j7XoFFu1XBlZWEl2/1kWnhmAbxpLgPrHSY0M6UA02jyTiwUVtiKR6A==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-named-capturing-groups-regex@7.24.7': - resolution: {integrity: sha512-/jr7h/EWeJtk1U/uz2jlsCioHkZk1JJZVcc8oQsJ1dUlaJD83f4/6Zeh2aHt9BIFokHIsSeDfhUmju0+1GPd6g==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/plugin-transform-new-target@7.24.7': - resolution: {integrity: sha512-RNKwfRIXg4Ls/8mMTza5oPF5RkOW8Wy/WgMAp1/F1yZ8mMbtwXW+HDoJiOsagWrAhI5f57Vncrmr9XeT4CVapA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-nullish-coalescing-operator@7.24.7': - resolution: {integrity: sha512-Ts7xQVk1OEocqzm8rHMXHlxvsfZ0cEF2yomUqpKENHWMF4zKk175Y4q8H5knJes6PgYad50uuRmt3UJuhBw8pQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-numeric-separator@7.24.7': - resolution: {integrity: sha512-e6q1TiVUzvH9KRvicuxdBTUj4AdKSRwzIyFFnfnezpCfP2/7Qmbb8qbU2j7GODbl4JMkblitCQjKYUaX/qkkwA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-object-rest-spread@7.24.7': - resolution: {integrity: sha512-4QrHAr0aXQCEFni2q4DqKLD31n2DL+RxcwnNjDFkSG0eNQ/xCavnRkfCUjsyqGC2OviNJvZOF/mQqZBw7i2C5Q==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-object-super@7.24.7': - resolution: {integrity: sha512-A/vVLwN6lBrMFmMDmPPz0jnE6ZGx7Jq7d6sT/Ev4H65RER6pZ+kczlf1DthF5N0qaPHBsI7UXiE8Zy66nmAovg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-optional-catch-binding@7.24.7': - resolution: {integrity: sha512-uLEndKqP5BfBbC/5jTwPxLh9kqPWWgzN/f8w6UwAIirAEqiIVJWWY312X72Eub09g5KF9+Zn7+hT7sDxmhRuKA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-optional-chaining@7.24.8': - resolution: {integrity: sha512-5cTOLSMs9eypEy8JUVvIKOu6NgvbJMnpG62VpIHrTmROdQ+L5mDAaI40g25k5vXti55JWNX5jCkq3HZxXBQANw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-parameters@7.24.7': - resolution: {integrity: sha512-yGWW5Rr+sQOhK0Ot8hjDJuxU3XLRQGflvT4lhlSY0DFvdb3TwKaY26CJzHtYllU0vT9j58hc37ndFPsqT1SrzA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-private-methods@7.25.4': - resolution: {integrity: sha512-ao8BG7E2b/URaUQGqN3Tlsg+M3KlHY6rJ1O1gXAEUnZoyNQnvKyH87Kfg+FoxSeyWUB8ISZZsC91C44ZuBFytw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-private-property-in-object@7.24.7': - resolution: {integrity: sha512-9z76mxwnwFxMyxZWEgdgECQglF2Q7cFLm0kMf8pGwt+GSJsY0cONKj/UuO4bOH0w/uAel3ekS4ra5CEAyJRmDA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-property-literals@7.24.7': - resolution: {integrity: sha512-EMi4MLQSHfd2nrCqQEWxFdha2gBCqU4ZcCng4WBGZ5CJL4bBRW0ptdqqDdeirGZcpALazVVNJqRmsO8/+oNCBA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-react-constant-elements@7.25.1': - resolution: {integrity: sha512-SLV/giH/V4SmloZ6Dt40HjTGTAIkxn33TVIHxNGNvo8ezMhrxBkzisj4op1KZYPIOHFLqhv60OHvX+YRu4xbmQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-react-display-name@7.24.7': - resolution: {integrity: sha512-H/Snz9PFxKsS1JLI4dJLtnJgCJRoo0AUm3chP6NYr+9En1JMKloheEiLIhlp5MDVznWo+H3AAC1Mc8lmUEpsgg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-react-jsx-development@7.24.7': - resolution: {integrity: sha512-QG9EnzoGn+Qar7rxuW+ZOsbWOt56FvvI93xInqsZDC5fsekx1AlIO4KIJ5M+D0p0SqSH156EpmZyXq630B8OlQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-react-jsx@7.25.2': - resolution: {integrity: sha512-KQsqEAVBpU82NM/B/N9j9WOdphom1SZH3R+2V7INrQUH+V9EBFwZsEJl8eBIVeQE62FxJCc70jzEZwqU7RcVqA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-react-pure-annotations@7.24.7': - resolution: {integrity: sha512-PLgBVk3fzbmEjBJ/u8kFzOqS9tUeDjiaWud/rRym/yjCo/M9cASPlnrd2ZmmZpQT40fOOrvR8jh+n8jikrOhNA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-regenerator@7.24.7': - resolution: {integrity: sha512-lq3fvXPdimDrlg6LWBoqj+r/DEWgONuwjuOuQCSYgRroXDH/IdM1C0IZf59fL5cHLpjEH/O6opIRBbqv7ELnuA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-reserved-words@7.24.7': - resolution: {integrity: sha512-0DUq0pHcPKbjFZCfTss/pGkYMfy3vFWydkUBd9r0GHpIyfs2eCDENvqadMycRS9wZCXR41wucAfJHJmwA0UmoQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-runtime@7.25.4': - resolution: {integrity: sha512-8hsyG+KUYGY0coX6KUCDancA0Vw225KJ2HJO0yCNr1vq5r+lJTleDaJf0K7iOhjw4SWhu03TMBzYTJ9krmzULQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-shorthand-properties@7.24.7': - resolution: {integrity: sha512-KsDsevZMDsigzbA09+vacnLpmPH4aWjcZjXdyFKGzpplxhbeB4wYtury3vglQkg6KM/xEPKt73eCjPPf1PgXBA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-spread@7.24.7': - resolution: {integrity: sha512-x96oO0I09dgMDxJaANcRyD4ellXFLLiWhuwDxKZX5g2rWP1bTPkBSwCYv96VDXVT1bD9aPj8tppr5ITIh8hBng==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-sticky-regex@7.24.7': - resolution: {integrity: sha512-kHPSIJc9v24zEml5geKg9Mjx5ULpfncj0wRpYtxbvKyTtHCYDkVE3aHQ03FrpEo4gEe2vrJJS1Y9CJTaThA52g==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-template-literals@7.24.7': - resolution: {integrity: sha512-AfDTQmClklHCOLxtGoP7HkeMw56k1/bTQjwsfhL6pppo/M4TOBSq+jjBUBLmV/4oeFg4GWMavIl44ZeCtmmZTw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-typeof-symbol@7.24.8': - resolution: {integrity: sha512-adNTUpDCVnmAE58VEqKlAA6ZBlNkMnWD0ZcW76lyNFN3MJniyGFZfNwERVk8Ap56MCnXztmDr19T4mPTztcuaw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-typescript@7.25.2': - resolution: {integrity: sha512-lBwRvjSmqiMYe/pS0+1gggjJleUJi7NzjvQ1Fkqtt69hBa/0t1YuW/MLQMAPixfwaQOHUXsd6jeU3Z+vdGv3+A==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-unicode-escapes@7.24.7': - resolution: {integrity: sha512-U3ap1gm5+4edc2Q/P+9VrBNhGkfnf+8ZqppY71Bo/pzZmXhhLdqgaUl6cuB07O1+AQJtCLfaOmswiNbSQ9ivhw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-unicode-property-regex@7.24.7': - resolution: {integrity: sha512-uH2O4OV5M9FZYQrwc7NdVmMxQJOCCzFeYudlZSzUAHRFeOujQefa92E74TQDVskNHCzOXoigEuoyzHDhaEaK5w==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-unicode-regex@7.24.7': - resolution: {integrity: sha512-hlQ96MBZSAXUq7ltkjtu3FJCCSMx/j629ns3hA3pXnBXjanNP0LHi+JpPeA81zaWgVK1VGH95Xuy7u0RyQ8kMg==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/plugin-transform-unicode-sets-regex@7.25.4': - resolution: {integrity: sha512-qesBxiWkgN1Q+31xUE9RcMk79eOXXDCv6tfyGMRSs4RGlioSg2WVyQAm07k726cSE56pa+Kb0y9epX2qaXzTvA==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0 - - '@babel/preset-env@7.25.4': - resolution: {integrity: sha512-W9Gyo+KmcxjGahtt3t9fb14vFRWvPpu5pT6GBlovAK6BTBcxgjfVMSQCfJl4oi35ODrxP6xx2Wr8LNST57Mraw==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/preset-modules@0.1.6-no-external-plugins': - resolution: {integrity: sha512-HrcgcIESLm9aIR842yhJ5RWan/gebQUJ6E/E5+rf0y9o6oj7w0Br+sWuL6kEQ/o/AdfvR1Je9jG18/gnpwjEyA==} - peerDependencies: - '@babel/core': ^7.0.0-0 || ^8.0.0-0 <8.0.0 - - '@babel/preset-react@7.24.7': - resolution: {integrity: sha512-AAH4lEkpmzFWrGVlHaxJB7RLH21uPQ9+He+eFLWHmF9IuFQVugz8eAsamaW0DXRrTfco5zj1wWtpdcXJUOfsag==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/preset-typescript@7.24.7': - resolution: {integrity: sha512-SyXRe3OdWwIwalxDg5UtJnJQO+YPcTfwiIY2B0Xlddh9o7jpWLvv8X1RthIeDOxQ+O1ML5BLPCONToObyVQVuQ==} - engines: {node: '>=6.9.0'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@babel/regjsgen@0.8.0': - resolution: {integrity: sha512-x/rqGMdzj+fWZvCOYForTghzbtqPDZ5gPwaoNGHdgDfF2QA/XZbCBp4Moo5scrkAMPhB7z26XM/AaHuIJdgauA==} - - '@babel/runtime-corejs3@7.25.0': - resolution: {integrity: sha512-BOehWE7MgQ8W8Qn0CQnMtg2tHPHPulcS/5AVpFvs2KCK1ET+0WqZqPvnpRpFN81gYoFopdIEJX9Sgjw3ZBccPg==} - engines: {node: '>=6.9.0'} - - '@babel/runtime@7.25.4': - resolution: {integrity: sha512-DSgLeL/FNcpXuzav5wfYvHCGvynXkJbn3Zvc3823AEe9nPwW9IK4UoCSS5yGymmQzN0pCPvivtgS6/8U2kkm1w==} - engines: {node: '>=6.9.0'} - - '@babel/template@7.25.0': - resolution: {integrity: sha512-aOOgh1/5XzKvg1jvVz7AVrx2piJ2XBi227DHmbY6y+bM9H2FlN+IfecYu4Xl0cNiiVejlsCri89LUsbj8vJD9Q==} - engines: {node: '>=6.9.0'} - - '@babel/traverse@7.25.4': - resolution: {integrity: sha512-VJ4XsrD+nOvlXyLzmLzUs/0qjFS4sK30te5yEFlvbbUNEgKaVb2BHZUpAL+ttLPQAHNrsI3zZisbfha5Cvr8vg==} - engines: {node: '>=6.9.0'} - - '@babel/types@7.25.4': - resolution: {integrity: sha512-zQ1ijeeCXVEh+aNL0RlmkPkG8HUiDcU2pzQQFjtbntgAczRASFzj4H+6+bV+dy1ntKR14I/DypeuRG1uma98iQ==} - engines: {node: '>=6.9.0'} - - '@colors/colors@1.5.0': - resolution: {integrity: sha512-ooWCrlZP11i8GImSjTHYHLkvFDP48nS4+204nGb1RiX/WXYHmJA2III9/e2DWVabCESdW7hBAEzHRqUn9OUVvQ==} - engines: {node: '>=0.1.90'} - - '@crowdin/cli@3.13.0': - resolution: {integrity: sha512-4YY1XSJyFdIADMX3U11WtkhL9wVWU/KCBEB6N360ybZVOWKE6G2/ERmWmYs8N1kXO6eoM2UUOp4qb8LmJ9UGTg==} - hasBin: true - - '@discoveryjs/json-ext@0.5.7': - resolution: {integrity: sha512-dBVuXR082gk3jsFp7Rd/JI4kytwGHecnCoTtXFb7DB6CNHp4rg5k1bhg0nWdLGLnOV71lmDzGQaLMy8iPLY0pw==} - engines: {node: '>=10.0.0'} - - '@docsearch/css@3.6.1': - resolution: {integrity: sha512-VtVb5DS+0hRIprU2CO6ZQjK2Zg4QU5HrDM1+ix6rT0umsYvFvatMAnf97NHZlVWDaaLlx7GRfR/7FikANiM2Fg==} - - '@docsearch/react@3.6.1': - resolution: {integrity: sha512-qXZkEPvybVhSXj0K7U3bXc233tk5e8PfhoZ6MhPOiik/qUQxYC+Dn9DnoS7CxHQQhHfCvTiN0eY9M12oRghEXw==} - peerDependencies: - '@types/react': '>= 16.8.0 < 19.0.0' - react: '>= 16.8.0 < 19.0.0' - react-dom: '>= 16.8.0 < 19.0.0' - search-insights: '>= 1 < 3' - peerDependenciesMeta: - '@types/react': - optional: true - react: - optional: true - react-dom: - optional: true - search-insights: - optional: true - - '@docusaurus/core@2.2.0': - resolution: {integrity: sha512-Vd6XOluKQqzG12fEs9prJgDtyn6DPok9vmUWDR2E6/nV5Fl9SVkhEQOBxwObjk3kQh7OY7vguFaLh0jqdApWsA==} - engines: {node: '>=16.14'} - hasBin: true - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/cssnano-preset@2.2.0': - resolution: {integrity: sha512-mAAwCo4n66TMWBH1kXnHVZsakW9VAXJzTO4yZukuL3ro4F+JtkMwKfh42EG75K/J/YIFQG5I/Bzy0UH/hFxaTg==} - engines: {node: '>=16.14'} - - '@docusaurus/logger@2.2.0': - resolution: {integrity: sha512-DF3j1cA5y2nNsu/vk8AG7xwpZu6f5MKkPPMaaIbgXLnWGfm6+wkOeW7kNrxnM95YOhKUkJUophX69nGUnLsm0A==} - engines: {node: '>=16.14'} - - '@docusaurus/mdx-loader@2.2.0': - resolution: {integrity: sha512-X2bzo3T0jW0VhUU+XdQofcEeozXOTmKQMvc8tUnWRdTnCvj4XEcBVdC3g+/jftceluiwSTNRAX4VBOJdNt18jA==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/module-type-aliases@2.2.0': - resolution: {integrity: sha512-wDGW4IHKoOr9YuJgy7uYuKWrDrSpsUSDHLZnWQYM9fN7D5EpSmYHjFruUpKWVyxLpD/Wh0rW8hYZwdjJIQUQCQ==} - peerDependencies: - react: '*' - react-dom: '*' - - '@docusaurus/plugin-content-blog@2.2.0': - resolution: {integrity: sha512-0mWBinEh0a5J2+8ZJXJXbrCk1tSTNf7Nm4tYAl5h2/xx+PvH/Bnu0V+7mMljYm/1QlDYALNIIaT/JcoZQFUN3w==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/plugin-content-docs@2.2.0': - resolution: {integrity: sha512-BOazBR0XjzsHE+2K1wpNxz5QZmrJgmm3+0Re0EVPYFGW8qndCWGNtXW/0lGKhecVPML8yyFeAmnUCIs7xM2wPw==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/plugin-content-pages@2.2.0': - resolution: {integrity: sha512-+OTK3FQHk5WMvdelz8v19PbEbx+CNT6VSpx7nVOvMNs5yJCKvmqBJBQ2ZSxROxhVDYn+CZOlmyrC56NSXzHf6g==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/plugin-debug@2.2.0': - resolution: {integrity: sha512-p9vOep8+7OVl6r/NREEYxf4HMAjV8JMYJ7Bos5fCFO0Wyi9AZEo0sCTliRd7R8+dlJXZEgcngSdxAUo/Q+CJow==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/plugin-google-analytics@2.2.0': - resolution: {integrity: sha512-+eZVVxVeEnV5nVQJdey9ZsfyEVMls6VyWTIj8SmX0k5EbqGvnIfET+J2pYEuKQnDIHxy+syRMoRM6AHXdHYGIg==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/plugin-google-gtag@2.2.0': - resolution: {integrity: sha512-6SOgczP/dYdkqUMGTRqgxAS1eTp6MnJDAQMy8VCF1QKbWZmlkx4agHDexihqmYyCujTYHqDAhm1hV26EET54NQ==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/plugin-sitemap@2.2.0': - resolution: {integrity: sha512-0jAmyRDN/aI265CbWZNZuQpFqiZuo+5otk2MylU9iVrz/4J7gSc+ZJ9cy4EHrEsW7PV8s1w18hIEsmcA1YgkKg==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/preset-classic@2.2.0': - resolution: {integrity: sha512-yKIWPGNx7BT8v2wjFIWvYrS+nvN04W+UameSFf8lEiJk6pss0kL6SG2MRvyULiI3BDxH+tj6qe02ncpSPGwumg==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/react-loadable@5.5.2': - resolution: {integrity: sha512-A3dYjdBGuy0IGT+wyLIGIKLRE+sAk1iNk0f1HjNDysO7u8lhL4N3VEm+FAubmJbAztn94F7MxBTPmnixbiyFdQ==} - peerDependencies: - react: '*' - - '@docusaurus/theme-classic@2.2.0': - resolution: {integrity: sha512-kjbg/qJPwZ6H1CU/i9d4l/LcFgnuzeiGgMQlt6yPqKo0SOJIBMPuz7Rnu3r/WWbZFPi//o8acclacOzmXdUUEg==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/theme-common@2.2.0': - resolution: {integrity: sha512-R8BnDjYoN90DCL75gP7qYQfSjyitXuP9TdzgsKDmSFPNyrdE3twtPNa2dIN+h+p/pr+PagfxwWbd6dn722A1Dw==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/theme-search-algolia@2.2.0': - resolution: {integrity: sha512-2h38B0tqlxgR2FZ9LpAkGrpDWVdXZ7vltfmTdX+4RsDs3A7khiNsmZB+x/x6sA4+G2V2CvrsPMlsYBy5X+cY1w==} - engines: {node: '>=16.14'} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/theme-translations@2.2.0': - resolution: {integrity: sha512-3T140AG11OjJrtKlY4pMZ5BzbGRDjNs2co5hJ6uYJG1bVWlhcaFGqkaZ5lCgKflaNHD7UHBHU9Ec5f69jTdd6w==} - engines: {node: '>=16.14'} - - '@docusaurus/types@2.2.0': - resolution: {integrity: sha512-b6xxyoexfbRNRI8gjblzVOnLr4peCJhGbYGPpJ3LFqpi5nsFfoK4mmDLvWdeah0B7gmJeXabN7nQkFoqeSdmOw==} - peerDependencies: - react: ^16.8.4 || ^17.0.0 - react-dom: ^16.8.4 || ^17.0.0 - - '@docusaurus/utils-common@2.2.0': - resolution: {integrity: sha512-qebnerHp+cyovdUseDQyYFvMW1n1nv61zGe5JJfoNQUnjKuApch3IVsz+/lZ9a38pId8kqehC1Ao2bW/s0ntDA==} - engines: {node: '>=16.14'} - peerDependencies: - '@docusaurus/types': '*' - peerDependenciesMeta: - '@docusaurus/types': - optional: true - - '@docusaurus/utils-validation@2.2.0': - resolution: {integrity: sha512-I1hcsG3yoCkasOL5qQAYAfnmVoLei7apugT6m4crQjmDGxq+UkiRrq55UqmDDyZlac/6ax/JC0p+usZ6W4nVyg==} - engines: {node: '>=16.14'} - - '@docusaurus/utils@2.2.0': - resolution: {integrity: sha512-oNk3cjvx7Tt1Lgh/aeZAmFpGV2pDr5nHKrBVx6hTkzGhrnMuQqLt6UPlQjdYQ3QHXwyF/ZtZMO1D5Pfi0lu7SA==} - engines: {node: '>=16.14'} - peerDependencies: - '@docusaurus/types': '*' - peerDependenciesMeta: - '@docusaurus/types': - optional: true - - '@hapi/hoek@9.3.0': - resolution: {integrity: sha512-/c6rf4UJlmHlC9b5BaNvzAcFv7HZ2QHaV0D4/HNlBdvFnvQq8RI4kYdhyPCl7Xj+oWvTWQ8ujhqS53LIgAe6KQ==} - - '@hapi/topo@5.1.0': - resolution: {integrity: sha512-foQZKJig7Ob0BMAYBfcJk8d77QtOe7Wo4ox7ff1lQYoNNAb6jwcY1ncdoy2e9wQZzvNy7ODZCYJkK8kzmcAnAg==} - - '@isaacs/cliui@8.0.2': - resolution: {integrity: sha512-O8jcjabXaleOG9DQ0+ARXWZBTfnP4WNAqzuiJK7ll44AmxGKv/J2M4TPjxjY3znBCfvBXFzucm1twdyFybFqEA==} - engines: {node: '>=12'} - - '@jest/schemas@29.6.3': - resolution: {integrity: sha512-mo5j5X+jIZmJQveBKeS/clAueipV7KgiX1vMgCxam1RNYiqE1w62n0/tJJnHtjW8ZHcQco5gY85jA3mi0L+nSA==} - engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} - - '@jest/types@29.6.3': - resolution: {integrity: sha512-u3UPsIilWKOM3F9CXtrG8LEJmNxwoCQC/XVj4IKYXvvpx7QIi/Kg1LI5uDmDpKlac62NUtX7eLjRh+jVZcLOzw==} - engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} - - '@jridgewell/gen-mapping@0.3.5': - resolution: {integrity: sha512-IzL8ZoEDIBRWEzlCcRhOaCupYyN5gdIK+Q6fbFdPDg6HqX6jpkItn7DFIpW9LQzXG6Df9sA7+OKnq0qlz/GaQg==} - engines: {node: '>=6.0.0'} - - '@jridgewell/resolve-uri@3.1.2': - resolution: {integrity: sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==} - engines: {node: '>=6.0.0'} - - '@jridgewell/set-array@1.2.1': - resolution: {integrity: sha512-R8gLRTZeyp03ymzP/6Lil/28tGeGEzhx1q2k703KGWRAI1VdvPIXdG70VJc2pAMw3NA6JKL5hhFu1sJX0Mnn/A==} - engines: {node: '>=6.0.0'} - - '@jridgewell/source-map@0.3.6': - resolution: {integrity: sha512-1ZJTZebgqllO79ue2bm3rIGud/bOe0pP5BjSRCRxxYkEZS8STV7zN84UBbiYu7jy+eCKSnVIUgoWWE/tt+shMQ==} - - '@jridgewell/sourcemap-codec@1.5.0': - resolution: {integrity: sha512-gv3ZRaISU3fjPAgNsriBRqGWQL6quFx04YMPW/zD8XMLsU32mhCCbfbO6KZFLjvYpCZ8zyDEgqsgf+PwPaM7GQ==} - - '@jridgewell/trace-mapping@0.3.25': - resolution: {integrity: sha512-vNk6aEwybGtawWmy/PzwnGDOjCkLWSD2wqvjGGAgOAwCGWySYXfYoxt00IJkTF+8Lb57DwOb3Aa0o9CApepiYQ==} - - '@leichtgewicht/ip-codec@2.0.5': - resolution: {integrity: sha512-Vo+PSpZG2/fmgmiNzYK9qWRh8h/CHrwD0mo1h1DzL4yzHNSfWYujGTYsWGreD000gcgmZ7K4Ys6Tx9TxtsKdDw==} - - '@mdx-js/mdx@1.6.22': - resolution: {integrity: sha512-AMxuLxPz2j5/6TpF/XSdKpQP1NlG0z11dFOlq+2IP/lSgl11GY8ji6S/rgsViN/L0BDvHvUMruRb7ub+24LUYA==} - - '@mdx-js/react@1.6.22': - resolution: {integrity: sha512-TDoPum4SHdfPiGSAaRBw7ECyI8VaHpK8GJugbJIJuqyh6kzw9ZLJZW3HGL3NNrJGxcAixUvqROm+YuQOo5eXtg==} - peerDependencies: - react: ^16.13.1 || ^17.0.0 - - '@mdx-js/util@1.6.22': - resolution: {integrity: sha512-H1rQc1ZOHANWBvPcW+JpGwr+juXSxM8Q8YCkm3GhZd8REu1fHR3z99CErO1p9pkcfcxZnMdIZdIsXkOHY0NilA==} - - '@nodelib/fs.scandir@2.1.5': - resolution: {integrity: sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==} - engines: {node: '>= 8'} - - '@nodelib/fs.stat@2.0.5': - resolution: {integrity: sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==} - engines: {node: '>= 8'} - - '@nodelib/fs.walk@1.2.8': - resolution: {integrity: sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==} - engines: {node: '>= 8'} - - '@pkgjs/parseargs@0.11.0': - resolution: {integrity: sha512-+1VkjdD0QBLPodGrJUeqarH8VAIvQODIbwh9XpP5Syisf7YoQgsJKPNFoqqLQlu+VQ/tVSshMR6loPMn8U+dPg==} - engines: {node: '>=14'} - - '@polka/url@1.0.0-next.25': - resolution: {integrity: sha512-j7P6Rgr3mmtdkeDGTe0E/aYyWEWVtc5yFXtHCRHs28/jptDEWfaVOc5T7cblqy1XKPPfCxJc/8DwQ5YgLOZOVQ==} - - '@sideway/address@4.1.5': - resolution: {integrity: sha512-IqO/DUQHUkPeixNQ8n0JA6102hT9CmaljNTPmQ1u8MEhBo/R4Q8eKLN/vGZxuebwOroDB4cbpjheD4+/sKFK4Q==} - - '@sideway/formula@3.0.1': - resolution: {integrity: sha512-/poHZJJVjx3L+zVD6g9KgHfYnb443oi7wLu/XKojDviHy6HOEOA6z1Trk5aR1dGcmPenJEgb2sK2I80LeS3MIg==} - - '@sideway/pinpoint@2.0.0': - resolution: {integrity: sha512-RNiOoTPkptFtSVzQevY/yWtZwf/RxyVnPy/OcA9HBM3MlGDnBEYL5B41H0MTn0Uec8Hi+2qUtTfG2WWZBmMejQ==} - - '@sinclair/typebox@0.27.8': - resolution: {integrity: sha512-+Fj43pSMwJs4KRrH/938Uf+uAELIgVBmQzg/q1YG10djyfA3TnrU8N8XzqCh/okZdszqBQTZf96idMfE5lnwTA==} - - '@sindresorhus/is@0.14.0': - resolution: {integrity: sha512-9NET910DNaIPngYnLLPeg+Ogzqsi9uM4mSboU5y6p8S5DzMTVEsJZrawi+BoDNUVBa2DhJqQYUFvMDfgU062LQ==} - engines: {node: '>=6'} - - '@slorber/static-site-generator-webpack-plugin@4.0.7': - resolution: {integrity: sha512-Ug7x6z5lwrz0WqdnNFOMYrDQNTPAprvHLSh6+/fmml3qUiz6l5eq+2MzLKWtn/q5K5NpSiFsZTP/fck/3vjSxA==} - engines: {node: '>=14'} - - '@svgr/babel-plugin-add-jsx-attribute@5.4.0': - resolution: {integrity: sha512-ZFf2gs/8/6B8PnSofI0inYXr2SDNTDScPXhN7k5EqD4aZ3gi6u+rbmZHVB8IM3wDyx8ntKACZbtXSm7oZGRqVg==} - engines: {node: '>=10'} - - '@svgr/babel-plugin-add-jsx-attribute@6.5.1': - resolution: {integrity: sha512-9PYGcXrAxitycIjRmZB+Q0JaN07GZIWaTBIGQzfaZv+qr1n8X1XUEJ5rZ/vx6OVD9RRYlrNnXWExQXcmZeD/BQ==} - engines: {node: '>=10'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@svgr/babel-plugin-remove-jsx-attribute@5.4.0': - resolution: {integrity: sha512-yaS4o2PgUtwLFGTKbsiAy6D0o3ugcUhWK0Z45umJ66EPWunAz9fuFw2gJuje6wqQvQWOTJvIahUwndOXb7QCPg==} - engines: {node: '>=10'} - - '@svgr/babel-plugin-remove-jsx-attribute@8.0.0': - resolution: {integrity: sha512-BcCkm/STipKvbCl6b7QFrMh/vx00vIP63k2eM66MfHJzPr6O2U0jYEViXkHJWqXqQYjdeA9cuCl5KWmlwjDvbA==} - engines: {node: '>=14'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@svgr/babel-plugin-remove-jsx-empty-expression@5.0.1': - resolution: {integrity: sha512-LA72+88A11ND/yFIMzyuLRSMJ+tRKeYKeQ+mR3DcAZ5I4h5CPWN9AHyUzJbWSYp/u2u0xhmgOe0+E41+GjEueA==} - engines: {node: '>=10'} - - '@svgr/babel-plugin-remove-jsx-empty-expression@8.0.0': - resolution: {integrity: sha512-5BcGCBfBxB5+XSDSWnhTThfI9jcO5f0Ai2V24gZpG+wXF14BzwxxdDb4g6trdOux0rhibGs385BeFMSmxtS3uA==} - engines: {node: '>=14'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@svgr/babel-plugin-replace-jsx-attribute-value@5.0.1': - resolution: {integrity: sha512-PoiE6ZD2Eiy5mK+fjHqwGOS+IXX0wq/YDtNyIgOrc6ejFnxN4b13pRpiIPbtPwHEc+NT2KCjteAcq33/F1Y9KQ==} - engines: {node: '>=10'} - - '@svgr/babel-plugin-replace-jsx-attribute-value@6.5.1': - resolution: {integrity: sha512-8DPaVVE3fd5JKuIC29dqyMB54sA6mfgki2H2+swh+zNJoynC8pMPzOkidqHOSc6Wj032fhl8Z0TVn1GiPpAiJg==} - engines: {node: '>=10'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@svgr/babel-plugin-svg-dynamic-title@5.4.0': - resolution: {integrity: sha512-zSOZH8PdZOpuG1ZVx/cLVePB2ibo3WPpqo7gFIjLV9a0QsuQAzJiwwqmuEdTaW2pegyBE17Uu15mOgOcgabQZg==} - engines: {node: '>=10'} - - '@svgr/babel-plugin-svg-dynamic-title@6.5.1': - resolution: {integrity: sha512-FwOEi0Il72iAzlkaHrlemVurgSQRDFbk0OC8dSvD5fSBPHltNh7JtLsxmZUhjYBZo2PpcU/RJvvi6Q0l7O7ogw==} - engines: {node: '>=10'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@svgr/babel-plugin-svg-em-dimensions@5.4.0': - resolution: {integrity: sha512-cPzDbDA5oT/sPXDCUYoVXEmm3VIoAWAPT6mSPTJNbQaBNUuEKVKyGH93oDY4e42PYHRW67N5alJx/eEol20abw==} - engines: {node: '>=10'} - - '@svgr/babel-plugin-svg-em-dimensions@6.5.1': - resolution: {integrity: sha512-gWGsiwjb4tw+ITOJ86ndY/DZZ6cuXMNE/SjcDRg+HLuCmwpcjOktwRF9WgAiycTqJD/QXqL2f8IzE2Rzh7aVXA==} - engines: {node: '>=10'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@svgr/babel-plugin-transform-react-native-svg@5.4.0': - resolution: {integrity: sha512-3eYP/SaopZ41GHwXma7Rmxcv9uRslRDTY1estspeB1w1ueZWd/tPlMfEOoccYpEMZU3jD4OU7YitnXcF5hLW2Q==} - engines: {node: '>=10'} - - '@svgr/babel-plugin-transform-react-native-svg@6.5.1': - resolution: {integrity: sha512-2jT3nTayyYP7kI6aGutkyfJ7UMGtuguD72OjeGLwVNyfPRBD8zQthlvL+fAbAKk5n9ZNcvFkp/b1lZ7VsYqVJg==} - engines: {node: '>=10'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@svgr/babel-plugin-transform-svg-component@5.5.0': - resolution: {integrity: sha512-q4jSH1UUvbrsOtlo/tKcgSeiCHRSBdXoIoqX1pgcKK/aU3JD27wmMKwGtpB8qRYUYoyXvfGxUVKchLuR5pB3rQ==} - engines: {node: '>=10'} - - '@svgr/babel-plugin-transform-svg-component@6.5.1': - resolution: {integrity: sha512-a1p6LF5Jt33O3rZoVRBqdxL350oge54iZWHNI6LJB5tQ7EelvD/Mb1mfBiZNAan0dt4i3VArkFRjA4iObuNykQ==} - engines: {node: '>=12'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@svgr/babel-preset@5.5.0': - resolution: {integrity: sha512-4FiXBjvQ+z2j7yASeGPEi8VD/5rrGQk4Xrq3EdJmoZgz/tpqChpo5hgXDvmEauwtvOc52q8ghhZK4Oy7qph4ig==} - engines: {node: '>=10'} - - '@svgr/babel-preset@6.5.1': - resolution: {integrity: sha512-6127fvO/FF2oi5EzSQOAjo1LE3OtNVh11R+/8FXa+mHx1ptAaS4cknIjnUA7e6j6fwGGJ17NzaTJFUwOV2zwCw==} - engines: {node: '>=10'} - peerDependencies: - '@babel/core': ^7.0.0-0 - - '@svgr/core@5.5.0': - resolution: {integrity: sha512-q52VOcsJPvV3jO1wkPtzTuKlvX7Y3xIcWRpCMtBF3MrteZJtBfQw/+u0B1BHy5ColpQc1/YVTrPEtSYIMNZlrQ==} - engines: {node: '>=10'} - - '@svgr/core@6.5.1': - resolution: {integrity: sha512-/xdLSWxK5QkqG524ONSjvg3V/FkNyCv538OIBdQqPNaAta3AsXj/Bd2FbvR87yMbXO2hFSWiAe/Q6IkVPDw+mw==} - engines: {node: '>=10'} - - '@svgr/hast-util-to-babel-ast@5.5.0': - resolution: {integrity: sha512-cAaR/CAiZRB8GP32N+1jocovUtvlj0+e65TB50/6Lcime+EA49m/8l+P2ko+XPJ4dw3xaPS3jOL4F2X4KWxoeQ==} - engines: {node: '>=10'} - - '@svgr/hast-util-to-babel-ast@6.5.1': - resolution: {integrity: sha512-1hnUxxjd83EAxbL4a0JDJoD3Dao3hmjvyvyEV8PzWmLK3B9m9NPlW7GKjFyoWE8nM7HnXzPcmmSyOW8yOddSXw==} - engines: {node: '>=10'} - - '@svgr/plugin-jsx@5.5.0': - resolution: {integrity: sha512-V/wVh33j12hGh05IDg8GpIUXbjAPnTdPTKuP4VNLggnwaHMPNQNae2pRnyTAILWCQdz5GyMqtO488g7CKM8CBA==} - engines: {node: '>=10'} - - '@svgr/plugin-jsx@6.5.1': - resolution: {integrity: sha512-+UdQxI3jgtSjCykNSlEMuy1jSRQlGC7pqBCPvkG/2dATdWo082zHTTK3uhnAju2/6XpE6B5mZ3z4Z8Ns01S8Gw==} - engines: {node: '>=10'} - peerDependencies: - '@svgr/core': ^6.0.0 - - '@svgr/plugin-svgo@5.5.0': - resolution: {integrity: sha512-r5swKk46GuQl4RrVejVwpeeJaydoxkdwkM1mBKOgJLBUJPGaLci6ylg/IjhrRsREKDkr4kbMWdgOtbXEh0fyLQ==} - engines: {node: '>=10'} - - '@svgr/plugin-svgo@6.5.1': - resolution: {integrity: sha512-omvZKf8ixP9z6GWgwbtmP9qQMPX4ODXi+wzbVZgomNFsUIlHA1sf4fThdwTWSsZGgvGAG6yE+b/F5gWUkcZ/iQ==} - engines: {node: '>=10'} - peerDependencies: - '@svgr/core': '*' - - '@svgr/webpack@5.5.0': - resolution: {integrity: sha512-DOBOK255wfQxguUta2INKkzPj6AIS6iafZYiYmHn6W3pHlycSRRlvWKCfLDG10fXfLWqE3DJHgRUOyJYmARa7g==} - engines: {node: '>=10'} - - '@svgr/webpack@6.5.1': - resolution: {integrity: sha512-cQ/AsnBkXPkEK8cLbv4Dm7JGXq2XrumKnL1dRpJD9rIO2fTIlJI9a1uCciYG1F2aUsox/hJQyNGbt3soDxSRkA==} - engines: {node: '>=10'} - - '@swc/core-darwin-arm64@1.7.18': - resolution: {integrity: sha512-MwLc5U+VGPMZm8MjlFBjEB2wyT1EK0NNJ3tn+ps9fmxdFP+PL8EpMiY1O1F2t1ydy2OzBtZz81sycjM9RieFBg==} - engines: {node: '>=10'} - cpu: [arm64] - os: [darwin] - - '@swc/core-darwin-x64@1.7.18': - resolution: {integrity: sha512-IkukOQUw7/14VkHp446OkYGCZEHqZg9pTmTdBawlUyz2JwZMSn2VodCl7aFSdGCsU4Cwni8zKA8CCgkCCAELhw==} - engines: {node: '>=10'} - cpu: [x64] - os: [darwin] - - '@swc/core-linux-arm-gnueabihf@1.7.18': - resolution: {integrity: sha512-ATnb6jJaBeXCqrTUawWdoOy7eP9SCI7UMcfXlYIMxX4otKKspLPAEuGA5RaNxlCcj9ObyO0J3YGbtZ6hhD2pjg==} - engines: {node: '>=10'} - cpu: [arm] - os: [linux] - - '@swc/core-linux-arm64-gnu@1.7.18': - resolution: {integrity: sha512-poHtH7zL7lEp9K2inY90lGHJABWxURAOgWNeZqrcR5+jwIe7q5KBisysH09Zf/JNF9+6iNns+U0xgWTNJzBuGA==} - engines: {node: '>=10'} - cpu: [arm64] - os: [linux] - - '@swc/core-linux-arm64-musl@1.7.18': - resolution: {integrity: sha512-qnNI1WmcOV7Wz1ZDyK6WrOlzLvJ01rnni8ec950mMHWkLRMP53QvCvhF3S+7gFplWBwWJTOOPPUqJp/PlSxWyQ==} - engines: {node: '>=10'} - cpu: [arm64] - os: [linux] - - '@swc/core-linux-x64-gnu@1.7.18': - resolution: {integrity: sha512-x9SCqCLzwtlqtD5At3I1a7Gco+EuXnzrJGoucmkpeQohshHuwa+cskqsXO6u1Dz0jXJEuHbBZB9va1wYYfjgFg==} - engines: {node: '>=10'} - cpu: [x64] - os: [linux] - - '@swc/core-linux-x64-musl@1.7.18': - resolution: {integrity: sha512-qtj8iOpMMgKjzxTv+islmEY0JBsbd93nka0gzcTTmGZxKtL5jSUsYQvkxwNPZr5M9NU1fgaR3n1vE6lFmtY0IQ==} - engines: {node: '>=10'} - cpu: [x64] - os: [linux] - - '@swc/core-win32-arm64-msvc@1.7.18': - resolution: {integrity: sha512-ltX/Ol9+Qu4SXmISCeuwVgAjSa8nzHTymknpozzVMgjXUoZMoz6lcynfKL1nCh5XLgqh0XNHUKLti5YFF8LrrA==} - engines: {node: '>=10'} - cpu: [arm64] - os: [win32] - - '@swc/core-win32-ia32-msvc@1.7.18': - resolution: {integrity: sha512-RgTcFP3wgyxnQbTCJrlgBJmgpeTXo8t807GU9GxApAXfpLZJ3swJ2GgFUmIJVdLWyffSHF5BEkF3FmF6mtH5AQ==} - engines: {node: '>=10'} - cpu: [ia32] - os: [win32] - - '@swc/core-win32-x64-msvc@1.7.18': - resolution: {integrity: sha512-XbZ0wAgzR757+DhQcnv60Y/bK9yuWPhDNRQVFFQVRsowvK3+c6EblyfUSytIidpXgyYFzlprq/9A9ZlO/wvDWw==} - engines: {node: '>=10'} - cpu: [x64] - os: [win32] - - '@swc/core@1.7.18': - resolution: {integrity: sha512-qL9v5N5S38ijmqiQRvCFUUx2vmxWT/JJ2rswElnyaHkOHuVoAFhBB90Ywj4RKjh3R0zOjhEcemENTyF3q3G6WQ==} - engines: {node: '>=10'} - peerDependencies: - '@swc/helpers': '*' - peerDependenciesMeta: - '@swc/helpers': - optional: true - - '@swc/counter@0.1.3': - resolution: {integrity: sha512-e2BR4lsJkkRlKZ/qCHPw9ZaSxc0MVUd7gtbtaB7aMvHeJVYe8sOB8DBZkP2DtISHGSku9sCK6T6cnY0CtXrOCQ==} - - '@swc/types@0.1.12': - resolution: {integrity: sha512-wBJA+SdtkbFhHjTMYH+dEH1y4VpfGdAc2Kw/LK09i9bXd/K6j6PkDcFCEzb6iVfZMkPRrl/q0e3toqTAJdkIVA==} - - '@szmarczak/http-timer@1.1.2': - resolution: {integrity: sha512-XIB2XbzHTN6ieIjfIMV9hlVcfPU26s2vafYWQcZHWXHOxiaRZYEDKEwdl129Zyg50+foYV2jCgtrqSA6qNuNSA==} - engines: {node: '>=6'} - - '@trysound/sax@0.2.0': - resolution: {integrity: sha512-L7z9BgrNEcYyUYtF+HaEfiS5ebkh9jXqbszz7pC0hRBPaatV0XjSD3+eHrpqFemQfgwiFF0QPIarnIihIDn7OA==} - engines: {node: '>=10.13.0'} - - '@types/body-parser@1.19.5': - resolution: {integrity: sha512-fB3Zu92ucau0iQ0JMCFQE7b/dv8Ot07NI3KaZIkIUNXq82k4eBAqUaneXfleGY9JWskeS9y+u0nXMyspcuQrCg==} - - '@types/bonjour@3.5.13': - resolution: {integrity: sha512-z9fJ5Im06zvUL548KvYNecEVlA7cVDkGUi6kZusb04mpyEFKCIZJvloCcmpmLaIahDpOQGHaHmG6imtPMmPXGQ==} - - '@types/connect-history-api-fallback@1.5.4': - resolution: {integrity: sha512-n6Cr2xS1h4uAulPRdlw6Jl6s1oG8KrVilPN2yUITEs+K48EzMJJ3W1xy8K5eWuFvjp3R74AOIGSmp2UfBJ8HFw==} - - '@types/connect@3.4.38': - resolution: {integrity: sha512-K6uROf1LD88uDQqJCktA4yzL1YYAK6NgfsI0v/mTgyPKWsX1CnJ0XPSDhViejru1GcRkLWb8RlzFYJRqGUbaug==} - - '@types/estree@1.0.5': - resolution: {integrity: sha512-/kYRxGDLWzHOB7q+wtSUQlFrtcdUccpfy+X+9iMBpHK8QLLhx2wIPYuS5DYtR9Wa/YlZAbIovy7qVdB1Aq6Lyw==} - - '@types/express-serve-static-core@4.19.5': - resolution: {integrity: sha512-y6W03tvrACO72aijJ5uF02FRq5cgDR9lUxddQ8vyF+GvmjJQqbzDcJngEjURc+ZsG31VI3hODNZJ2URj86pzmg==} - - '@types/express@4.17.21': - resolution: {integrity: sha512-ejlPM315qwLpaQlQDTjPdsUFSc6ZsP4AN6AlWnogPjQ7CVi7PYF3YVz+CY3jE2pwYf7E/7HlDAN0rV2GxTG0HQ==} - - '@types/hast@2.3.10': - resolution: {integrity: sha512-McWspRw8xx8J9HurkVBfYj0xKoE25tOFlHGdx4MJ5xORQrMGZNqJhVQWaIbm6Oyla5kYOXtDiopzKRJzEOkwJw==} - - '@types/history@4.7.11': - resolution: {integrity: sha512-qjDJRrmvBMiTx+jyLxvLfJU7UznFuokDv4f3WRuriHKERccVpFU+8XMQUAbDzoiJCsmexxRExQeMwwCdamSKDA==} - - '@types/html-minifier-terser@6.1.0': - resolution: {integrity: sha512-oh/6byDPnL1zeNXFrDXFLyZjkr1MsBG667IM792caf1L2UPOOMf65NFzjUH/ltyfwjAGfs1rsX1eftK0jC/KIg==} - - '@types/http-errors@2.0.4': - resolution: {integrity: sha512-D0CFMMtydbJAegzOyHjtiKPLlvnm3iTZyZRSZoLq2mRhDdmLfIWOCYPfQJ4cu2erKghU++QvjcUjp/5h7hESpA==} - - '@types/http-proxy@1.17.15': - resolution: {integrity: sha512-25g5atgiVNTIv0LBDTg1H74Hvayx0ajtJPLLcYE3whFv75J0pWNtOBzaXJQgDTmrX1bx5U9YC2w/n65BN1HwRQ==} - - '@types/istanbul-lib-coverage@2.0.6': - resolution: {integrity: sha512-2QF/t/auWm0lsy8XtKVPG19v3sSOQlJe/YHZgfjb/KBBHOGSV+J2q/S671rcq9uTBrLAXmZpqJiaQbMT+zNU1w==} - - '@types/istanbul-lib-report@3.0.3': - resolution: {integrity: sha512-NQn7AHQnk/RSLOxrBbGyJM/aVQ+pjj5HCgasFxc0K/KhoATfQ/47AyUl15I2yBUpihjmas+a+VJBOqecrFH+uA==} - - '@types/istanbul-reports@3.0.4': - resolution: {integrity: sha512-pk2B1NWalF9toCRu6gjBzR69syFjP4Od8WRAX+0mmf9lAjCRicLOWc+ZrxZHx/0XRjotgkF9t6iaMJ+aXcOdZQ==} - - '@types/json-schema@7.0.15': - resolution: {integrity: sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==} - - '@types/keyv@3.1.4': - resolution: {integrity: sha512-BQ5aZNSCpj7D6K2ksrRCTmKRLEpnPvWDiLPfoGyhZ++8YtiK9d/3DBKPJgry359X/P1PfruyYwvnvwFjuEiEIg==} - - '@types/mdast@3.0.15': - resolution: {integrity: sha512-LnwD+mUEfxWMa1QpDraczIn6k0Ee3SMicuYSSzS6ZYl2gKS09EClnJYGd8Du6rfc5r/GZEk5o1mRb8TaTj03sQ==} - - '@types/mime@1.3.5': - resolution: {integrity: sha512-/pyBZWSLD2n0dcHE3hq8s8ZvcETHtEuF+3E7XVt0Ig2nvsVQXdghHVcEkIWjy9A0wKfTn97a/PSDYohKIlnP/w==} - - '@types/node-forge@1.3.11': - resolution: {integrity: sha512-FQx220y22OKNTqaByeBGqHWYz4cl94tpcxeFdvBo3wjG6XPBuZ0BNgNZRV5J5TFmmcsJ4IzsLkmGRiQbnYsBEQ==} - - '@types/node@17.0.45': - resolution: {integrity: sha512-w+tIMs3rq2afQdsPJlODhoUEKzFP1ayaoyl1CcnwtIlsVe7K7bA1NGm4s3PraqTLlXnbIN84zuBlxBWo1u9BLw==} - - '@types/node@22.5.0': - resolution: {integrity: sha512-DkFrJOe+rfdHTqqMg0bSNlGlQ85hSoh2TPzZyhHsXnMtligRWpxUySiyw8FY14ITt24HVCiQPWxS3KO/QlGmWg==} - - '@types/parse-json@4.0.2': - resolution: {integrity: sha512-dISoDXWWQwUquiKsyZ4Ng+HX2KsPL7LyHKHQwgGFEA3IaKac4Obd+h2a/a6waisAoepJlBcx9paWqjA8/HVjCw==} - - '@types/parse5@5.0.3': - resolution: {integrity: sha512-kUNnecmtkunAoQ3CnjmMkzNU/gtxG8guhi+Fk2U/kOpIKjIMKnXGp4IJCgQJrXSgMsWYimYG4TGjz/UzbGEBTw==} - - '@types/prop-types@15.7.12': - resolution: {integrity: sha512-5zvhXYtRNRluoE/jAp4GVsSduVUzNWKkOZrCDBWYtE7biZywwdC2AcEzg+cSMLFRfVgeAFqpfNabiPjxFddV1Q==} - - '@types/q@1.5.8': - resolution: {integrity: sha512-hroOstUScF6zhIi+5+x0dzqrHA1EJi+Irri6b1fxolMTqqHIV/Cg77EtnQcZqZCu8hR3mX2BzIxN4/GzI68Kfw==} - - '@types/qs@6.9.15': - resolution: {integrity: sha512-uXHQKES6DQKKCLh441Xv/dwxOq1TVS3JPUMlEqoEglvlhR6Mxnlew/Xq/LRVHpLyk7iK3zODe1qYHIMltO7XGg==} - - '@types/range-parser@1.2.7': - resolution: {integrity: sha512-hKormJbkJqzQGhziax5PItDUTMAM9uE2XXQmM37dyd4hVM+5aVl7oVxMVUiVQn2oCQFN/LKCZdvSM0pFRqbSmQ==} - - '@types/react-router-config@5.0.11': - resolution: {integrity: sha512-WmSAg7WgqW7m4x8Mt4N6ZyKz0BubSj/2tVUMsAHp+Yd2AMwcSbeFq9WympT19p5heCFmF97R9eD5uUR/t4HEqw==} - - '@types/react-router-dom@5.3.3': - resolution: {integrity: sha512-kpqnYK4wcdm5UaWI3fLcELopqLrHgLqNsdpHauzlQktfkHL3npOSwtj1Uz9oKBAzs7lFtVkV8j83voAz2D8fhw==} - - '@types/react-router@5.1.20': - resolution: {integrity: sha512-jGjmu/ZqS7FjSH6owMcD5qpq19+1RS9DeVRqfl1FeBMxTDQAGwlMWOcs52NDoXaNKyG3d1cYQFMs9rCrb88o9Q==} - - '@types/react@18.3.4': - resolution: {integrity: sha512-J7W30FTdfCxDDjmfRM+/JqLHBIyl7xUIp9kwK637FGmY7+mkSFSe6L4jpZzhj5QMfLssSDP4/i75AKkrdC7/Jw==} - - '@types/responselike@1.0.3': - resolution: {integrity: sha512-H/+L+UkTV33uf49PH5pCAUBVPNj2nDBXTN+qS1dOwyyg24l3CcicicCA7ca+HMvJBZcFgl5r8e+RR6elsb4Lyw==} - - '@types/retry@0.12.0': - resolution: {integrity: sha512-wWKOClTTiizcZhXnPY4wikVAwmdYHp8q6DmC+EJUzAMsycb7HB32Kh9RN4+0gExjmPmZSAQjgURXIGATPegAvA==} - - '@types/sax@1.2.7': - resolution: {integrity: sha512-rO73L89PJxeYM3s3pPPjiPgVVcymqU490g0YO5n5By0k2Erzj6tay/4lr1CHAAU4JyOWd1rpQ8bCf6cZfHU96A==} - - '@types/send@0.17.4': - resolution: {integrity: sha512-x2EM6TJOybec7c52BX0ZspPodMsQUd5L6PRwOunVyVUhXiBSKf3AezDL8Dgvgt5o0UfKNfuA0eMLr2wLT4AiBA==} - - '@types/serve-index@1.9.4': - resolution: {integrity: sha512-qLpGZ/c2fhSs5gnYsQxtDEq3Oy8SXPClIXkW5ghvAvsNuVSA8k+gCONcUCS/UjLEYvYps+e8uBtfgXgvhwfNug==} - - '@types/serve-static@1.15.7': - resolution: {integrity: sha512-W8Ym+h8nhuRwaKPaDw34QUkwsGi6Rc4yYqvKFo5rm2FUEhCFbzVWrxXUxuKK8TASjWsysJY0nsmNCGhCOIsrOw==} - - '@types/sockjs@0.3.36': - resolution: {integrity: sha512-MK9V6NzAS1+Ud7JV9lJLFqW85VbC9dq3LmwZCuBe4wBDgKC0Kj/jd8Xl+nSviU+Qc3+m7umHHyHg//2KSa0a0Q==} - - '@types/unist@2.0.11': - resolution: {integrity: sha512-CmBKiL6NNo/OqgmMn95Fk9Whlp2mtvIv+KNpQKN2F4SjvrEesubTRWGYSg+BnWZOnlCaSTU1sMpsBOzgbYhnsA==} - - '@types/ws@8.5.12': - resolution: {integrity: sha512-3tPRkv1EtkDpzlgyKyI8pGsGZAGPEaXeu0DOj5DI25Ja91bdAYddYHbADRYVrZMRbfW+1l5YwXVDKohDJNQxkQ==} - - '@types/yargs-parser@21.0.3': - resolution: {integrity: sha512-I4q9QU9MQv4oEOz4tAHJtNz1cwuLxn2F3xcc2iV5WdqLPpUnj30aUuxt1mAxYTG+oe8CZMV/+6rU4S4gRDzqtQ==} - - '@types/yargs@17.0.33': - resolution: {integrity: sha512-WpxBCKWPLr4xSsHgz511rFJAM+wS28w2zEO1QDNY5zM/S8ok70NNfztH0xwhqKyaK0OHCbN98LDAZuy1ctxDkA==} - - '@webassemblyjs/ast@1.12.1': - resolution: {integrity: sha512-EKfMUOPRRUTy5UII4qJDGPpqfwjOmZ5jeGFwid9mnoqIFK+e0vqoi1qH56JpmZSzEL53jKnNzScdmftJyG5xWg==} - - '@webassemblyjs/floating-point-hex-parser@1.11.6': - resolution: {integrity: sha512-ejAj9hfRJ2XMsNHk/v6Fu2dGS+i4UaXBXGemOfQ/JfQ6mdQg/WXtwleQRLLS4OvfDhv8rYnVwH27YJLMyYsxhw==} - - '@webassemblyjs/helper-api-error@1.11.6': - resolution: {integrity: sha512-o0YkoP4pVu4rN8aTJgAyj9hC2Sv5UlkzCHhxqWj8butaLvnpdc2jOwh4ewE6CX0txSfLn/UYaV/pheS2Txg//Q==} - - '@webassemblyjs/helper-buffer@1.12.1': - resolution: {integrity: sha512-nzJwQw99DNDKr9BVCOZcLuJJUlqkJh+kVzVl6Fmq/tI5ZtEyWT1KZMyOXltXLZJmDtvLCDgwsyrkohEtopTXCw==} - - '@webassemblyjs/helper-numbers@1.11.6': - resolution: {integrity: sha512-vUIhZ8LZoIWHBohiEObxVm6hwP034jwmc9kuq5GdHZH0wiLVLIPcMCdpJzG4C11cHoQ25TFIQj9kaVADVX7N3g==} - - '@webassemblyjs/helper-wasm-bytecode@1.11.6': - resolution: {integrity: sha512-sFFHKwcmBprO9e7Icf0+gddyWYDViL8bpPjJJl0WHxCdETktXdmtWLGVzoHbqUcY4Be1LkNfwTmXOJUFZYSJdA==} - - '@webassemblyjs/helper-wasm-section@1.12.1': - resolution: {integrity: sha512-Jif4vfB6FJlUlSbgEMHUyk1j234GTNG9dBJ4XJdOySoj518Xj0oGsNi59cUQF4RRMS9ouBUxDDdyBVfPTypa5g==} - - '@webassemblyjs/ieee754@1.11.6': - resolution: {integrity: sha512-LM4p2csPNvbij6U1f19v6WR56QZ8JcHg3QIJTlSwzFcmx6WSORicYj6I63f9yU1kEUtrpG+kjkiIAkevHpDXrg==} - - '@webassemblyjs/leb128@1.11.6': - resolution: {integrity: sha512-m7a0FhE67DQXgouf1tbN5XQcdWoNgaAuoULHIfGFIEVKA6tu/edls6XnIlkmS6FrXAquJRPni3ZZKjw6FSPjPQ==} - - '@webassemblyjs/utf8@1.11.6': - resolution: {integrity: sha512-vtXf2wTQ3+up9Zsg8sa2yWiQpzSsMyXj0qViVP6xKGCUT8p8YJ6HqI7l5eCnWx1T/FYdsv07HQs2wTFbbof/RA==} - - '@webassemblyjs/wasm-edit@1.12.1': - resolution: {integrity: sha512-1DuwbVvADvS5mGnXbE+c9NfA8QRcZ6iKquqjjmR10k6o+zzsRVesil54DKexiowcFCPdr/Q0qaMgB01+SQ1u6g==} - - '@webassemblyjs/wasm-gen@1.12.1': - resolution: {integrity: sha512-TDq4Ojh9fcohAw6OIMXqiIcTq5KUXTGRkVxbSo1hQnSy6lAM5GSdfwWeSxpAo0YzgsgF182E/U0mDNhuA0tW7w==} - - '@webassemblyjs/wasm-opt@1.12.1': - resolution: {integrity: sha512-Jg99j/2gG2iaz3hijw857AVYekZe2SAskcqlWIZXjji5WStnOpVoat3gQfT/Q5tb2djnCjBtMocY/Su1GfxPBg==} - - '@webassemblyjs/wasm-parser@1.12.1': - resolution: {integrity: sha512-xikIi7c2FHXysxXe3COrVUPSheuBtpcfhbpFj4gmu7KRLYOzANztwUU0IbsqvMqzuNK2+glRGWCEqZo1WCLyAQ==} - - '@webassemblyjs/wast-printer@1.12.1': - resolution: {integrity: sha512-+X4WAlOisVWQMikjbcvY2e0rwPsKQ9F688lksZhBcPycBBuii3O7m8FACbDMWDojpAqvjIncrG8J0XHKyQfVeA==} - - '@xtuc/ieee754@1.2.0': - resolution: {integrity: sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==} - - '@xtuc/long@4.2.2': - resolution: {integrity: sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==} - - accepts@1.3.8: - resolution: {integrity: sha512-PYAthTa2m2VKxuvSD3DPC/Gy+U+sOA1LAuT8mkmRuvw+NACSaeXEQ+NHcVF7rONl6qcaxV3Uuemwawk+7+SJLw==} - engines: {node: '>= 0.6'} - - acorn-import-attributes@1.9.5: - resolution: {integrity: sha512-n02Vykv5uA3eHGM/Z2dQrcD56kL8TyDb2p1+0P83PClMnC/nc+anbQRhIOWnSq4Ke/KvDPrY3C9hDtC/A3eHnQ==} - peerDependencies: - acorn: ^8 - - acorn-walk@8.3.3: - resolution: {integrity: sha512-MxXdReSRhGO7VlFe1bRG/oI7/mdLV9B9JJT0N8vZOhF7gFRR5l3M8W9G8JxmKV+JC5mGqJ0QvqfSOLsCPa4nUw==} - engines: {node: '>=0.4.0'} - - acorn@8.12.1: - resolution: {integrity: sha512-tcpGyI9zbizT9JbV6oYE477V6mTlXvvi0T0G3SNIYE2apm/G5huBa1+K89VGeovbg+jycCrfhl3ADxErOuO6Jg==} - engines: {node: '>=0.4.0'} - hasBin: true - - address@1.2.2: - resolution: {integrity: sha512-4B/qKCfeE/ODUaAUpSwfzazo5x29WD4r3vXiWsB7I2mSDAihwEqKO+g8GELZUQSSAo5e1XTYh3ZVfLyxBc12nA==} - engines: {node: '>= 10.0.0'} - - aggregate-error@3.1.0: - resolution: {integrity: sha512-4I7Td01quW/RpocfNayFdFVk1qSuoh0E7JrbRJ16nH01HhKFQ88INq9Sd+nd72zqRySlr9BmDA8xlEJ6vJMrYA==} - engines: {node: '>=8'} - - ajv-formats@2.1.1: - resolution: {integrity: sha512-Wx0Kx52hxE7C18hkMEggYlEifqWZtYaRgouJor+WMdPnQyEK13vgEWyVNup7SoeeoLMsr4kf5h6dOW11I15MUA==} - peerDependencies: - ajv: ^8.0.0 - peerDependenciesMeta: - ajv: - optional: true - - ajv-keywords@3.5.2: - resolution: {integrity: sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==} - peerDependencies: - ajv: ^6.9.1 - - ajv-keywords@5.1.0: - resolution: {integrity: sha512-YCS/JNFAUyr5vAuhk1DWm1CBxRHW9LbJ2ozWeemrIqpbsqKjHVxYPyi5GC0rjZIT5JxJ3virVTS8wk4i/Z+krw==} - peerDependencies: - ajv: ^8.8.2 - - ajv@6.12.6: - resolution: {integrity: sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==} - - ajv@8.17.1: - resolution: {integrity: sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g==} - - algoliasearch-helper@3.22.4: - resolution: {integrity: sha512-fvBCywguW9f+939S6awvRMstqMF1XXcd2qs1r1aGqL/PJ1go/DqN06tWmDVmhCDqBJanm++imletrQWf0G2S1g==} - peerDependencies: - algoliasearch: '>= 3.1 < 6' - - algoliasearch@4.24.0: - resolution: {integrity: sha512-bf0QV/9jVejssFBmz2HQLxUadxk574t4iwjCKp5E7NBzwKkrDEhKPISIIjAU/p6K5qDx3qoeh4+26zWN1jmw3g==} - - ansi-align@3.0.1: - resolution: {integrity: sha512-IOfwwBF5iczOjp/WeY4YxyjqAFMQoZufdQWDd19SEExbVLNXqvpzSJ/M7Za4/sCPmQ0+GRquoA7bGcINcxew6w==} - - ansi-html-community@0.0.8: - resolution: {integrity: sha512-1APHAyr3+PCamwNw3bXCPp4HFLONZt/yIH0sZp0/469KWNTEy+qN5jQ3GVX6DMZ1UXAi34yVwtTeaG/HpBuuzw==} - engines: {'0': node >= 0.8.0} - hasBin: true - - ansi-regex@5.0.1: - resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==} - engines: {node: '>=8'} - - ansi-regex@6.0.1: - resolution: {integrity: sha512-n5M855fKb2SsfMIiFFoVrABHJC8QtHwVx+mHWP3QcEqBHYienj5dHSgjbxtC0WEZXYt4wcD6zrQElDPhFuZgfA==} - engines: {node: '>=12'} - - ansi-styles@3.2.1: - resolution: {integrity: sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==} - engines: {node: '>=4'} - - ansi-styles@4.3.0: - resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==} - engines: {node: '>=8'} - - ansi-styles@6.2.1: - resolution: {integrity: sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==} - engines: {node: '>=12'} - - anymatch@3.1.3: - resolution: {integrity: sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==} - engines: {node: '>= 8'} - - arg@5.0.2: - resolution: {integrity: sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==} - - argparse@1.0.10: - resolution: {integrity: sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==} - - argparse@2.0.1: - resolution: {integrity: sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==} - - array-buffer-byte-length@1.0.1: - resolution: {integrity: sha512-ahC5W1xgou+KTXix4sAO8Ki12Q+jf4i0+tmk3sC+zgcynshkHxzpXdImBehiUYKKKDwvfFiJl1tZt6ewscS1Mg==} - engines: {node: '>= 0.4'} - - array-flatten@1.1.1: - resolution: {integrity: sha512-PCVAQswWemu6UdxsDFFX/+gVeYqKAod3D3UVm91jHwynguOwAvYPhx8nNlM++NqRcK6CxxpUafjmhIdKiHibqg==} - - array-union@2.1.0: - resolution: {integrity: sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==} - engines: {node: '>=8'} - - array.prototype.reduce@1.0.7: - resolution: {integrity: sha512-mzmiUCVwtiD4lgxYP8g7IYy8El8p2CSMePvIbTS7gchKir/L1fgJrk0yDKmAX6mnRQFKNADYIk8nNlTris5H1Q==} - engines: {node: '>= 0.4'} - - arraybuffer.prototype.slice@1.0.3: - resolution: {integrity: sha512-bMxMKAjg13EBSVscxTaYA4mRc5t1UAXa2kXiGTNfZ079HIWXEkKmkgFrh/nJqamaLSrXO5H4WFFkPEaLJWbs3A==} - engines: {node: '>= 0.4'} - - asap@2.0.6: - resolution: {integrity: sha512-BSHWgDSAiKs50o2Re8ppvp3seVHXSRM44cdSsT9FfNEUUZLOGWVCsiWaRPWM1Znn+mqZ1OfVZ3z3DWEzSp7hRA==} - - asynckit@0.4.0: - resolution: {integrity: sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q==} - - at-least-node@1.0.0: - resolution: {integrity: sha512-+q/t7Ekv1EDY2l6Gda6LLiX14rU9TV20Wa3ofeQmwPFZbOMo9DXrLbOjFaaclkXKWidIaopwAObQDqwWtGUjqg==} - engines: {node: '>= 4.0.0'} - - autoprefixer@10.4.20: - resolution: {integrity: sha512-XY25y5xSv/wEoqzDyXXME4AFfkZI0P23z6Fs3YgymDnKJkCGOnkL0iTxCa85UTqaSgfcqyf3UA6+c7wUvx/16g==} - engines: {node: ^10 || ^12 || >=14} - hasBin: true - peerDependencies: - postcss: ^8.1.0 - - available-typed-arrays@1.0.7: - resolution: {integrity: sha512-wvUjBtSGN7+7SjNpq/9M2Tg350UZD3q62IFZLbRAR1bSMlCo1ZaeW+BJ+D090e4hIIZLBcTDWe4Mh4jvUDajzQ==} - engines: {node: '>= 0.4'} - - axios@0.25.0: - resolution: {integrity: sha512-cD8FOb0tRH3uuEe6+evtAbgJtfxr7ly3fQjYcMcuPlgkwVS9xboaVIpcDV+cYQe+yGykgwZCs1pzjntcGa6l5g==} - - axios@1.7.5: - resolution: {integrity: sha512-fZu86yCo+svH3uqJ/yTdQ0QHpQu5oL+/QE+QPSv6BZSkDAoky9vytxp7u5qk83OJFS3kEBcesWni9WTZAv3tSw==} - - babel-loader@8.3.0: - resolution: {integrity: sha512-H8SvsMF+m9t15HNLMipppzkC+Y2Yq+v3SonZyU70RBL/h1gxPkH08Ot8pEE9Z4Kd+czyWJClmFS8qzIP9OZ04Q==} - engines: {node: '>= 8.9'} - peerDependencies: - '@babel/core': ^7.0.0 - webpack: '>=2' - - babel-plugin-apply-mdx-type-prop@1.6.22: - resolution: {integrity: sha512-VefL+8o+F/DfK24lPZMtJctrCVOfgbqLAGZSkxwhazQv4VxPg3Za/i40fu22KR2m8eEda+IfSOlPLUSIiLcnCQ==} - peerDependencies: - '@babel/core': ^7.11.6 - - babel-plugin-dynamic-import-node@2.3.3: - resolution: {integrity: sha512-jZVI+s9Zg3IqA/kdi0i6UDCybUI3aSBLnglhYbSSjKlV7yF1F/5LWv8MakQmvYpnbJDS6fcBL2KzHSxNCMtWSQ==} - - babel-plugin-extract-import-names@1.6.22: - resolution: {integrity: sha512-yJ9BsJaISua7d8zNT7oRG1ZLBJCIdZ4PZqmH8qa9N5AK01ifk3fnkc98AXhtzE7UkfCsEumvoQWgoYLhOnJ7jQ==} - - babel-plugin-polyfill-corejs2@0.4.11: - resolution: {integrity: sha512-sMEJ27L0gRHShOh5G54uAAPaiCOygY/5ratXuiyb2G46FmlSpc9eFCzYVyDiPxfNbwzA7mYahmjQc5q+CZQ09Q==} - peerDependencies: - '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 - - babel-plugin-polyfill-corejs3@0.10.6: - resolution: {integrity: sha512-b37+KR2i/khY5sKmWNVQAnitvquQbNdWy6lJdsr0kmquCKEEUgMKK4SboVM3HtfnZilfjr4MMQ7vY58FVWDtIA==} - peerDependencies: - '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 - - babel-plugin-polyfill-regenerator@0.6.2: - resolution: {integrity: sha512-2R25rQZWP63nGwaAswvDazbPXfrM3HwVoBXK6HcqeKrSrL/JqcC/rDcf95l4r7LXLyxDXc8uQDa064GubtCABg==} - peerDependencies: - '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 - - bail@1.0.5: - resolution: {integrity: sha512-xFbRxM1tahm08yHBP16MMjVUAvDaBMD38zsM9EMAUN61omwLmKlOpB/Zku5QkjZ8TZ4vn53pj+t518cH0S03RQ==} - - balanced-match@1.0.2: - resolution: {integrity: sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==} - - base16@1.0.0: - resolution: {integrity: sha512-pNdYkNPiJUnEhnfXV56+sQy8+AaPcG3POZAUnwr4EeqCUZFz4u2PePbo3e5Gj4ziYPCWGUZT9RHisvJKnwFuBQ==} - - batch@0.6.1: - resolution: {integrity: sha512-x+VAiMRL6UPkx+kudNvxTl6hB2XNNCG2r+7wixVfIYwu/2HKRXimwQyaumLjMveWvT2Hkd/cAJw+QBMfJ/EKVw==} - - big.js@5.2.2: - resolution: {integrity: sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==} - - binary-extensions@2.3.0: - resolution: {integrity: sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==} - engines: {node: '>=8'} - - body-parser@1.20.2: - resolution: {integrity: sha512-ml9pReCu3M61kGlqoTm2umSXTlRTuGTx0bfYj+uIUKKYycG5NtSbeetV3faSU6R7ajOPw0g/J1PvK4qNy7s5bA==} - engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16} - - bonjour-service@1.2.1: - resolution: {integrity: sha512-oSzCS2zV14bh2kji6vNe7vrpJYCHGvcZnlffFQ1MEoX/WOeQ/teD8SYWKR942OI3INjq8OMNJlbPK5LLLUxFDw==} - - boolbase@1.0.0: - resolution: {integrity: sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==} - - boxen@5.1.2: - resolution: {integrity: sha512-9gYgQKXx+1nP8mP7CzFyaUARhg7D3n1dF/FnErWmu9l6JvGpNUN278h0aSb+QjoiKSWG+iZ3uHrcqk0qrY9RQQ==} - engines: {node: '>=10'} - - boxen@6.2.1: - resolution: {integrity: sha512-H4PEsJXfFI/Pt8sjDWbHlQPx4zL/bvSQjcilJmaulGt5mLDorHOHpmdXAJcBcmru7PhYSp/cDMWRko4ZUMFkSw==} - engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} - - brace-expansion@1.1.11: - resolution: {integrity: sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==} - - brace-expansion@2.0.1: - resolution: {integrity: sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==} - - braces@3.0.3: - resolution: {integrity: sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==} - engines: {node: '>=8'} - - browserslist@4.23.3: - resolution: {integrity: sha512-btwCFJVjI4YWDNfau8RhZ+B1Q/VLoUITrm3RlP6y1tYGWIOa+InuYiRGXUBXo8nA1qKmHMyLB/iVQg5TT4eFoA==} - engines: {node: ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7} - hasBin: true - - buffer-crc32@0.2.13: - resolution: {integrity: sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ==} - - buffer-from@1.1.2: - resolution: {integrity: sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==} - - bytes@3.0.0: - resolution: {integrity: sha512-pMhOfFDPiv9t5jjIXkHosWmkSyQbvsgEVNkz0ERHbuLh2T/7j4Mqqpz523Fe8MVY89KC6Sh/QfS2sM+SjgFDcw==} - engines: {node: '>= 0.8'} - - bytes@3.1.2: - resolution: {integrity: sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==} - engines: {node: '>= 0.8'} - - cacheable-request@6.1.0: - resolution: {integrity: sha512-Oj3cAGPCqOZX7Rz64Uny2GYAZNliQSqfbePrgAQ1wKAihYmCUnraBtJtKcGR4xz7wF+LoJC+ssFZvv5BgF9Igg==} - engines: {node: '>=8'} - - call-bind@1.0.7: - resolution: {integrity: sha512-GHTSNSYICQ7scH7sZ+M2rFopRoLh8t2bLSW6BbgrtLsahOIB5iyAVJf9GjWK3cYTDaMj4XdBpM1cA6pIS0Kv2w==} - engines: {node: '>= 0.4'} - - callsites@3.1.0: - resolution: {integrity: sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==} - engines: {node: '>=6'} - - camel-case@4.1.2: - resolution: {integrity: sha512-gxGWBrTT1JuMx6R+o5PTXMmUnhnVzLQ9SNutD4YqKtI6ap897t3tKECYla6gCWEkplXnlNybEkZg9GEGxKFCgw==} - - camelcase-css@2.0.1: - resolution: {integrity: sha512-QOSvevhslijgYwRx6Rv7zKdMF8lbRmx+uQGx2+vDc+KI/eBnsy9kit5aj23AgGu3pa4t9AgwbnXWqS+iOY+2aA==} - engines: {node: '>= 6'} - - camelcase@6.3.0: - resolution: {integrity: sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==} - engines: {node: '>=10'} - - caniuse-api@3.0.0: - resolution: {integrity: sha512-bsTwuIg/BZZK/vreVTYYbSWoe2F+71P7K5QGEX+pT250DZbfU1MQ5prOKpPR+LL6uWKK3KMwMCAS74QB3Um1uw==} - - caniuse-lite@1.0.30001653: - resolution: {integrity: sha512-XGWQVB8wFQ2+9NZwZ10GxTYC5hk0Fa+q8cSkr0tgvMhYhMHP/QC+WTgrePMDBWiWc/pV+1ik82Al20XOK25Gcw==} - - ccount@1.1.0: - resolution: {integrity: sha512-vlNK021QdI7PNeiUh/lKkC/mNHHfV0m/Ad5JoI0TYtlBnJAslM/JIkm/tGC88bkLIwO6OQ5uV6ztS6kVAtCDlg==} - - chalk@2.4.2: - resolution: {integrity: sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==} - engines: {node: '>=4'} - - chalk@4.1.2: - resolution: {integrity: sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==} - engines: {node: '>=10'} - - character-entities-legacy@1.1.4: - resolution: {integrity: sha512-3Xnr+7ZFS1uxeiUDvV02wQ+QDbc55o97tIV5zHScSPJpcLm/r0DFPcoY3tYRp+VZukxuMeKgXYmsXQHO05zQeA==} - - character-entities@1.2.4: - resolution: {integrity: sha512-iBMyeEHxfVnIakwOuDXpVkc54HijNgCyQB2w0VfGQThle6NXn50zU6V/u+LDhxHcDUPojn6Kpga3PTAD8W1bQw==} - - character-reference-invalid@1.1.4: - resolution: {integrity: sha512-mKKUkUbhPpQlCOfIuZkvSEgktjPFIsZKRRbC6KWVEMvlzblj3i3asQv5ODsrwt0N3pHAEvjP8KTQPHkp0+6jOg==} - - cheerio-select@2.1.0: - resolution: {integrity: sha512-9v9kG0LvzrlcungtnJtpGNxY+fzECQKhK4EGJX2vByejiMX84MFNQw4UxPJl3bFbTMw+Dfs37XaIkCwTZfLh4g==} - - cheerio@1.0.0: - resolution: {integrity: sha512-quS9HgjQpdaXOvsZz82Oz7uxtXiy6UIsIQcpBj7HRw2M63Skasm9qlDocAM7jNuaxdhpPU7c4kJN+gA5MCu4ww==} - engines: {node: '>=18.17'} - - chokidar@3.6.0: - resolution: {integrity: sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==} - engines: {node: '>= 8.10.0'} - - chownr@1.1.4: - resolution: {integrity: sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==} - - chrome-trace-event@1.0.4: - resolution: {integrity: sha512-rNjApaLzuwaOTjCiT8lSDdGN1APCiqkChLMJxJPWLunPAt5fy8xgU9/jNOchV84wfIxrA0lRQB7oCT8jrn/wrQ==} - engines: {node: '>=6.0'} - - ci-info@2.0.0: - resolution: {integrity: sha512-5tK7EtrZ0N+OLFMthtqOj4fI2Jeb88C4CAZPu25LDVUgXJ0A3Js4PMGqrn0JU1W0Mh1/Z8wZzYPxqUrXeBboCQ==} - - ci-info@3.9.0: - resolution: {integrity: sha512-NIxF55hv4nSqQswkAeiOi1r83xy8JldOFDTWiug55KBu9Jnblncd2U6ViHmYgHf01TPZS77NJBhBMKdWj9HQMQ==} - engines: {node: '>=8'} - - clean-css@5.3.3: - resolution: {integrity: sha512-D5J+kHaVb/wKSFcyyV75uCn8fiY4sV38XJoe4CUyGQ+mOU/fMVYUdH1hJC+CJQ5uY3EnW27SbJYS4X8BiLrAFg==} - engines: {node: '>= 10.0'} - - clean-stack@2.2.0: - resolution: {integrity: sha512-4diC9HaTE+KRAMWhDhrGOECgWZxoevMc5TlkObMqNSsVU62PYzXZ/SMTjzyGAFF1YusgxGcSWTEXBhp0CPwQ1A==} - engines: {node: '>=6'} - - cli-boxes@2.2.1: - resolution: {integrity: sha512-y4coMcylgSCdVinjiDBuR8PCC2bLjyGTwEmPb9NHR/QaNU6EUOXcTY/s6VjGMD6ENSEaeQYHCY0GNGS5jfMwPw==} - engines: {node: '>=6'} - - cli-boxes@3.0.0: - resolution: {integrity: sha512-/lzGpEWL/8PfI0BmBOPRwp0c/wFNX1RdUML3jK/RcSBA9T8mZDdQpqYBKtCFTOfQbwPqWEOpjqW+Fnayc0969g==} - engines: {node: '>=10'} - - cli-table3@0.6.5: - resolution: {integrity: sha512-+W/5efTR7y5HRD7gACw9yQjqMVvEMLBHmboM/kPWam+H+Hmyrgjh6YncVKK122YZkXrLudzTuAukUw9FnMf7IQ==} - engines: {node: 10.* || >= 12.*} - - clone-deep@4.0.1: - resolution: {integrity: sha512-neHB9xuzh/wk0dIHweyAXv2aPGZIVk3pLMe+/RNzINf17fe0OG96QroktYAUm7SM1PBnzTabaLboqqxDyMU+SQ==} - engines: {node: '>=6'} - - clone-response@1.0.3: - resolution: {integrity: sha512-ROoL94jJH2dUVML2Y/5PEDNaSHgeOdSDicUyS7izcF63G6sTc/FTjLub4b8Il9S8S0beOfYt0TaA5qvFK+w0wA==} - - clsx@1.2.1: - resolution: {integrity: sha512-EcR6r5a8bj6pu3ycsa/E/cKVGuTgZJZdsyUYHOksG/UHIiKfjxzRxYJpyVBwYaQeOvghal9fcc4PidlgzugAQg==} - engines: {node: '>=6'} - - coa@2.0.2: - resolution: {integrity: sha512-q5/jG+YQnSy4nRTV4F7lPepBJZ8qBNJJDBuJdoejDyLXgmL7IEo+Le2JDZudFTFt7mrCqIRaSjws4ygRCTCAXA==} - engines: {node: '>= 4.0'} - - collapse-white-space@1.0.6: - resolution: {integrity: sha512-jEovNnrhMuqyCcjfEJA56v0Xq8SkIoPKDyaHahwo3POf4qcSXqMYuwNcOTzp74vTsR9Tn08z4MxWqAhcekogkQ==} - - color-convert@1.9.3: - resolution: {integrity: sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==} - - color-convert@2.0.1: - resolution: {integrity: sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==} - engines: {node: '>=7.0.0'} - - color-name@1.1.3: - resolution: {integrity: sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw==} - - color-name@1.1.4: - resolution: {integrity: sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==} - - colord@2.9.3: - resolution: {integrity: sha512-jeC1axXpnb0/2nn/Y1LPuLdgXBLH7aDcHu4KEKfqw3CUhX7ZpfBSlPKyqXE6btIgEzfWtrX3/tyBCaCvXvMkOw==} - - colorette@2.0.20: - resolution: {integrity: sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w==} - - combine-promises@1.2.0: - resolution: {integrity: sha512-VcQB1ziGD0NXrhKxiwyNbCDmRzs/OShMs2GqW2DlU2A/Sd0nQxE1oWDAE5O0ygSx5mgQOn9eIFh7yKPgFRVkPQ==} - engines: {node: '>=10'} - - combined-stream@1.0.8: - resolution: {integrity: sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==} - engines: {node: '>= 0.8'} - - comma-separated-tokens@1.0.8: - resolution: {integrity: sha512-GHuDRO12Sypu2cV70d1dkA2EUmXHgntrzbpvOB+Qy+49ypNfGgFQIC2fhhXbnyrJRynDCAARsT7Ou0M6hirpfw==} - - command-exists-promise@2.0.2: - resolution: {integrity: sha512-T6PB6vdFrwnHXg/I0kivM3DqaCGZLjjYSOe0a5WgFKcz1sOnmOeIjnhQPXVXX3QjVbLyTJ85lJkX6lUpukTzaA==} - engines: {node: '>=6'} - - commander@11.0.0: - resolution: {integrity: sha512-9HMlXtt/BNoYr8ooyjjNRdIilOTkVJXB+GhxMTtOKwk0R4j4lS4NpjuqmRxroBfnfTSHQIHQB7wryHhXarNjmQ==} - engines: {node: '>=16'} - - commander@2.20.3: - resolution: {integrity: sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==} - - commander@5.1.0: - resolution: {integrity: sha512-P0CysNDQ7rtVw4QIQtm+MRxV66vKFSvlsQvGYXZWR3qFU0jlMKHZZZgw8e+8DSah4UDKMqnknRDQz+xuQXQ/Zg==} - engines: {node: '>= 6'} - - commander@7.2.0: - resolution: {integrity: sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==} - engines: {node: '>= 10'} - - commander@8.3.0: - resolution: {integrity: sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==} - engines: {node: '>= 12'} - - commondir@1.0.1: - resolution: {integrity: sha512-W9pAhw0ja1Edb5GVdIF1mjZw/ASI0AlShXM83UUGe2DVr5TdAPEA1OA8m/g8zWp9x6On7gqufY+FatDbC3MDQg==} - - compressible@2.0.18: - resolution: {integrity: sha512-AF3r7P5dWxL8MxyITRMlORQNaOA2IkAFaTr4k7BUumjPtRpGDTZpl0Pb1XCO6JeDCBdp126Cgs9sMxqSjgYyRg==} - engines: {node: '>= 0.6'} - - compression@1.7.4: - resolution: {integrity: sha512-jaSIDzP9pZVS4ZfQ+TzvtiWhdpFhE2RDHz8QJkpX9SIpLq88VueF5jJw6t+6CUQcAoA6t+x89MLrWAqpfDE8iQ==} - engines: {node: '>= 0.8.0'} - - concat-map@0.0.1: - resolution: {integrity: sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==} - - configstore@5.0.1: - resolution: {integrity: sha512-aMKprgk5YhBNyH25hj8wGt2+D52Sw1DRRIzqBwLp2Ya9mFmY8KPvvtvmna8SxVR9JMZ4kzMD68N22vlaRpkeFA==} - engines: {node: '>=8'} - - connect-history-api-fallback@2.0.0: - resolution: {integrity: sha512-U73+6lQFmfiNPrYbXqr6kZ1i1wiRqXnp2nhMsINseWXO8lDau0LGEffJ8kQi4EjLZympVgRdvqjAgiZ1tgzDDA==} - engines: {node: '>=0.8'} - - consola@2.15.3: - resolution: {integrity: sha512-9vAdYbHj6x2fLKC4+oPH0kFzY/orMZyG2Aj+kNylHxKGJ/Ed4dpNyAQYwJOdqO4zdM7XpVHmyejQDcQHrnuXbw==} - - content-disposition@0.5.2: - resolution: {integrity: sha512-kRGRZw3bLlFISDBgwTSA1TMBFN6J6GWDeubmDE3AF+3+yXL8hTWv8r5rkLbqYXY4RjPk/EzHnClI3zQf1cFmHA==} - engines: {node: '>= 0.6'} - - content-disposition@0.5.4: - resolution: {integrity: sha512-FveZTNuGw04cxlAiWbzi6zTAL/lhehaWbTtgluJh4/E95DqMwTmha3KZN1aAWA8cFIhHzMZUvLevkw5Rqk+tSQ==} - engines: {node: '>= 0.6'} - - content-type@1.0.5: - resolution: {integrity: sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==} - engines: {node: '>= 0.6'} - - convert-source-map@1.9.0: - resolution: {integrity: sha512-ASFBup0Mz1uyiIjANan1jzLQami9z1PoYSZCiiYW2FczPbenXc45FZdBZLzOT+r6+iciuEModtmCti+hjaAk0A==} - - convert-source-map@2.0.0: - resolution: {integrity: sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==} - - cookie-signature@1.0.6: - resolution: {integrity: sha512-QADzlaHc8icV8I7vbaJXJwod9HWYp8uCqf1xa4OfNu1T7JVxQIrUgOWtHdNDtPiywmFbiS12VjotIXLrKM3orQ==} - - cookie@0.6.0: - resolution: {integrity: sha512-U71cyTamuh1CRNCfpGY6to28lxvNwPG4Guz/EVjgf3Jmzv0vlDp1atT9eS5dDjMYHucpHbWns6Lwf3BKz6svdw==} - engines: {node: '>= 0.6'} - - copy-text-to-clipboard@3.2.0: - resolution: {integrity: sha512-RnJFp1XR/LOBDckxTib5Qjr/PMfkatD0MUCQgdpqS8MdKiNUzBjAQBEN6oUy+jW7LI93BBG3DtMB2KOOKpGs2Q==} - engines: {node: '>=12'} - - copy-webpack-plugin@11.0.0: - resolution: {integrity: sha512-fX2MWpamkW0hZxMEg0+mYnA40LTosOSa5TqZ9GYIBzyJa9C3QUaMPSE2xAi/buNr8u89SfD9wHSQVBzrRa/SOQ==} - engines: {node: '>= 14.15.0'} - peerDependencies: - webpack: ^5.1.0 - - core-js-compat@3.38.1: - resolution: {integrity: sha512-JRH6gfXxGmrzF3tZ57lFx97YARxCXPaMzPo6jELZhv88pBH5VXpQ+y0znKGlFnzuaihqhLbefxSJxWJMPtfDzw==} - - core-js-pure@3.38.1: - resolution: {integrity: sha512-BY8Etc1FZqdw1glX0XNOq2FDwfrg/VGqoZOZCdaL+UmdaqDwQwYXkMJT4t6In+zfEfOJDcM9T0KdbBeJg8KKCQ==} - - core-js@3.38.1: - resolution: {integrity: sha512-OP35aUorbU3Zvlx7pjsFdu1rGNnD4pgw/CWoYzRY3t2EzoVT7shKHY1dlAy3f41cGIO7ZDPQimhGFTlEYkG/Hw==} - - core-util-is@1.0.3: - resolution: {integrity: sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==} - - cosmiconfig@6.0.0: - resolution: {integrity: sha512-xb3ZL6+L8b9JLLCx3ZdoZy4+2ECphCMo2PwqgP1tlfVq6M6YReyzBJtvWWtbDSpNr9hn96pkCiZqUcFEc+54Qg==} - engines: {node: '>=8'} - - cosmiconfig@7.1.0: - resolution: {integrity: sha512-AdmX6xUzdNASswsFtmwSt7Vj8po9IuqXm0UXz7QKPuEUmPB4XyjGfaAr2PSuELMwkRMVH1EpIkX5bTZGRB3eCA==} - engines: {node: '>=10'} - - cosmiconfig@8.3.6: - resolution: {integrity: sha512-kcZ6+W5QzcJ3P1Mt+83OUv/oHFqZHIx8DuxG6eZ5RGMERoLqp4BuGjhHLYGK+Kf5XVkQvqBSmAy/nGWN3qDgEA==} - engines: {node: '>=14'} - peerDependencies: - typescript: '>=4.9.5' - peerDependenciesMeta: - typescript: - optional: true - - cross-fetch@3.1.8: - resolution: {integrity: sha512-cvA+JwZoU0Xq+h6WkMvAUqPEYy92Obet6UdKLfW60qn99ftItKjB5T+BkyWOFWe2pUyfQ+IJHmpOTznqk1M6Kg==} - - cross-spawn@7.0.3: - resolution: {integrity: sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==} - engines: {node: '>= 8'} - - crypto-random-string@2.0.0: - resolution: {integrity: sha512-v1plID3y9r/lPhviJ1wrXpLeyUIGAZ2SHNYTEapm7/8A9nLPoyvVp3RK/EPFqn5kEznyWgYZNsRtYYIWbuG8KA==} - engines: {node: '>=8'} - - css-declaration-sorter@6.4.1: - resolution: {integrity: sha512-rtdthzxKuyq6IzqX6jEcIzQF/YqccluefyCYheovBOLhFT/drQA9zj/UbRAa9J7C0o6EG6u3E6g+vKkay7/k3g==} - engines: {node: ^10 || ^12 || >=14} - peerDependencies: - postcss: ^8.0.9 - - css-loader@6.11.0: - resolution: {integrity: sha512-CTJ+AEQJjq5NzLga5pE39qdiSV56F8ywCIsqNIRF0r7BDgWsN25aazToqAFg7ZrtA/U016xudB3ffgweORxX7g==} - engines: {node: '>= 12.13.0'} - peerDependencies: - '@rspack/core': 0.x || 1.x - webpack: ^5.0.0 - peerDependenciesMeta: - '@rspack/core': - optional: true - webpack: - optional: true - - css-minimizer-webpack-plugin@4.2.2: - resolution: {integrity: sha512-s3Of/4jKfw1Hj9CxEO1E5oXhQAxlayuHO2y/ML+C6I9sQ7FdzfEV6QgMLN3vI+qFsjJGIAFLKtQK7t8BOXAIyA==} - engines: {node: '>= 14.15.0'} - peerDependencies: - '@parcel/css': '*' - '@swc/css': '*' - clean-css: '*' - csso: '*' - esbuild: '*' - lightningcss: '*' - webpack: ^5.0.0 - peerDependenciesMeta: - '@parcel/css': - optional: true - '@swc/css': - optional: true - clean-css: - optional: true - csso: - optional: true - esbuild: - optional: true - lightningcss: - optional: true - - css-select-base-adapter@0.1.1: - resolution: {integrity: sha512-jQVeeRG70QI08vSTwf1jHxp74JoZsr2XSgETae8/xC8ovSnL2WF87GTLO86Sbwdt2lK4Umg4HnnwMO4YF3Ce7w==} - - css-select@2.1.0: - resolution: {integrity: sha512-Dqk7LQKpwLoH3VovzZnkzegqNSuAziQyNZUcrdDM401iY+R5NkGBXGmtO05/yaXQziALuPogeG0b7UAgjnTJTQ==} - - css-select@4.3.0: - resolution: {integrity: sha512-wPpOYtnsVontu2mODhA19JrqWxNsfdatRKd64kmpRbQgh1KtItko5sTnEpPdpSaJszTOhEMlF/RPz28qj4HqhQ==} - - css-select@5.1.0: - resolution: {integrity: sha512-nwoRF1rvRRnnCqqY7updORDsuqKzqYJ28+oSMaJMMgOauh3fvwHqMS7EZpIPqK8GL+g9mKxF1vP/ZjSeNjEVHg==} - - css-tree@1.0.0-alpha.37: - resolution: {integrity: sha512-DMxWJg0rnz7UgxKT0Q1HU/L9BeJI0M6ksor0OgqOnF+aRCDWg/N2641HmVyU9KVIu0OVVWOb2IpC9A+BJRnejg==} - engines: {node: '>=8.0.0'} - - css-tree@1.1.3: - resolution: {integrity: sha512-tRpdppF7TRazZrjJ6v3stzv93qxRcSsFmW6cX0Zm2NVKpxE1WV1HblnghVv9TreireHkqI/VDEsfolRF1p6y7Q==} - engines: {node: '>=8.0.0'} - - css-what@3.4.2: - resolution: {integrity: sha512-ACUm3L0/jiZTqfzRM3Hi9Q8eZqd6IK37mMWPLz9PJxkLWllYeRf+EHUSHYEtFop2Eqytaq1FizFVh7XfBnXCDQ==} - engines: {node: '>= 6'} - - css-what@6.1.0: - resolution: {integrity: sha512-HTUrgRJ7r4dsZKU6GjmpfRK1O76h97Z8MfS1G0FozR+oF2kG6Vfe8JE6zwrkbxigziPHinCJ+gCPjA9EaBDtRw==} - engines: {node: '>= 6'} - - cssesc@3.0.0: - resolution: {integrity: sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==} - engines: {node: '>=4'} - hasBin: true - - cssnano-preset-advanced@5.3.10: - resolution: {integrity: sha512-fnYJyCS9jgMU+cmHO1rPSPf9axbQyD7iUhLO5Df6O4G+fKIOMps+ZbU0PdGFejFBBZ3Pftf18fn1eG7MAPUSWQ==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - cssnano-preset-default@5.2.14: - resolution: {integrity: sha512-t0SFesj/ZV2OTylqQVOrFgEh5uanxbO6ZAdeCrNsUQ6fVuXwYTxJPNAGvGTxHbD68ldIJNec7PyYZDBrfDQ+6A==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - cssnano-utils@3.1.0: - resolution: {integrity: sha512-JQNR19/YZhz4psLX/rQ9M83e3z2Wf/HdJbryzte4a3NSuafyp9w/I4U+hx5C2S9g41qlstH7DEWnZaaj83OuEA==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - cssnano@5.1.15: - resolution: {integrity: sha512-j+BKgDcLDQA+eDifLx0EO4XSA56b7uut3BQFH+wbSaSTuGLuiyTa/wbRYthUXX8LC9mLg+WWKe8h+qJuwTAbHw==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - csso@4.2.0: - resolution: {integrity: sha512-wvlcdIbf6pwKEk7vHj8/Bkc0B4ylXZruLvOgs9doS5eOsOpuodOV2zJChSpkp+pRpYQLQMeF04nr3Z68Sta9jA==} - engines: {node: '>=8.0.0'} - - csstype@3.1.3: - resolution: {integrity: sha512-M1uQkMl8rQK/szD0LNhtqxIPLpimGm8sOBwU7lLnCpSbTyY3yeU1Vc7l4KT5zT4s/yOxHH5O7tIuuLOCnLADRw==} - - data-view-buffer@1.0.1: - resolution: {integrity: sha512-0lht7OugA5x3iJLOWFhWK/5ehONdprk0ISXqVFn/NFrDu+cuc8iADFrGQz5BnRK7LLU3JmkbXSxaqX+/mXYtUA==} - engines: {node: '>= 0.4'} - - data-view-byte-length@1.0.1: - resolution: {integrity: sha512-4J7wRJD3ABAzr8wP+OcIcqq2dlUKp4DVflx++hs5h5ZKydWMI6/D/fAot+yh6g2tHh8fLFTvNOaVN357NvSrOQ==} - engines: {node: '>= 0.4'} - - data-view-byte-offset@1.0.0: - resolution: {integrity: sha512-t/Ygsytq+R995EJ5PZlD4Cu56sWa8InXySaViRzw9apusqsOO2bQP+SbYzAhR0pFKoB+43lYy8rWban9JSuXnA==} - engines: {node: '>= 0.4'} - - debounce@1.2.1: - resolution: {integrity: sha512-XRRe6Glud4rd/ZGQfiV1ruXSfbvfJedlV9Y6zOlP+2K04vBYiJEte6stfFkCP03aMnY5tsipamumUjL14fofug==} - - debug@2.6.9: - resolution: {integrity: sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==} - peerDependencies: - supports-color: '*' - peerDependenciesMeta: - supports-color: - optional: true - - debug@4.3.6: - resolution: {integrity: sha512-O/09Bd4Z1fBrU4VzkhFqVgpPzaGbw6Sm9FEkBT1A/YBXQFGuuSxa1dN2nxgxS34JmKXqYx8CZAwEVoJFImUXIg==} - engines: {node: '>=6.0'} - peerDependencies: - supports-color: '*' - peerDependenciesMeta: - supports-color: - optional: true - - decompress-response@3.3.0: - resolution: {integrity: sha512-BzRPQuY1ip+qDonAOz42gRm/pg9F768C+npV/4JOsxRC2sq+Rlk+Q4ZCAsOhnIaMrgarILY+RMUIvMmmX1qAEA==} - engines: {node: '>=4'} - - deep-extend@0.6.0: - resolution: {integrity: sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==} - engines: {node: '>=4.0.0'} - - deepmerge@4.3.1: - resolution: {integrity: sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A==} - engines: {node: '>=0.10.0'} - - default-gateway@6.0.3: - resolution: {integrity: sha512-fwSOJsbbNzZ/CUFpqFBqYfYNLj1NbMPm8MMCIzHjC83iSJRBEGmDUxU+WP661BaBQImeC2yHwXtz+P/O9o+XEg==} - engines: {node: '>= 10'} - - defer-to-connect@1.1.3: - resolution: {integrity: sha512-0ISdNousHvZT2EiFlZeZAHBUvSxmKswVCEf8hW7KWgG4a8MVEu/3Vb6uWYozkjylyCxe0JBIiRB1jV45S70WVQ==} - - define-data-property@1.1.4: - resolution: {integrity: sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A==} - engines: {node: '>= 0.4'} - - define-lazy-prop@2.0.0: - resolution: {integrity: sha512-Ds09qNh8yw3khSjiJjiUInaGX9xlqZDY7JVryGxdxV7NPeuqQfplOpQ66yJFZut3jLa5zOwkXw1g9EI2uKh4Og==} - engines: {node: '>=8'} - - define-properties@1.2.1: - resolution: {integrity: sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==} - engines: {node: '>= 0.4'} - - del@6.1.1: - resolution: {integrity: sha512-ua8BhapfP0JUJKC/zV9yHHDW/rDoDxP4Zhn3AkA6/xT6gY7jYXJiaeyBZznYVujhZZET+UgcbZiQ7sN3WqcImg==} - engines: {node: '>=10'} - - delayed-stream@1.0.0: - resolution: {integrity: sha512-ZySD7Nf91aLB0RxL4KGrKHBXl7Eds1DAmEdcoVawXnLD7SDhpNgtuII2aAkg7a7QS41jxPSZ17p4VdGnMHk3MQ==} - engines: {node: '>=0.4.0'} - - depd@1.1.2: - resolution: {integrity: sha512-7emPTl6Dpo6JRXOXjLRxck+FlLRX5847cLKEn00PLAgc3g2hTZZgr+e4c2v6QpSmLeFP3n5yUo7ft6avBK/5jQ==} - engines: {node: '>= 0.6'} - - depd@2.0.0: - resolution: {integrity: sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw==} - engines: {node: '>= 0.8'} - - destroy@1.2.0: - resolution: {integrity: sha512-2sJGJTaXIIaR1w4iJSNoN0hnMY7Gpc/n8D4qSCJw8QqFWXf7cuAgnEHxBpweaVcPevC2l3KpjYCx3NypQQgaJg==} - engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16} - - detab@2.0.4: - resolution: {integrity: sha512-8zdsQA5bIkoRECvCrNKPla84lyoR7DSAyf7p0YgXzBO9PDJx8KntPUay7NS6yp+KdxdVtiE5SpHKtbp2ZQyA9g==} - - detect-node@2.1.0: - resolution: {integrity: sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g==} - - detect-port-alt@1.1.6: - resolution: {integrity: sha512-5tQykt+LqfJFBEYaDITx7S7cR7mJ/zQmLXZ2qt5w04ainYZw6tBf9dBunMjVeVOdYVRUzUOE4HkY5J7+uttb5Q==} - engines: {node: '>= 4.2.1'} - hasBin: true - - detect-port@1.6.1: - resolution: {integrity: sha512-CmnVc+Hek2egPx1PeTFVta2W78xy2K/9Rkf6cC4T59S50tVnzKj+tnx5mmx5lwvCkujZ4uRrpRSuV+IVs3f90Q==} - engines: {node: '>= 4.0.0'} - hasBin: true - - dir-glob@3.0.1: - resolution: {integrity: sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==} - engines: {node: '>=8'} - - dns-packet@5.6.1: - resolution: {integrity: sha512-l4gcSouhcgIKRvyy99RNVOgxXiicE+2jZoNmaNmZ6JXiGajBOJAesk1OBlJuM5k2c+eudGdLxDqXuPCKIj6kpw==} - engines: {node: '>=6'} - - docusaurus-theme-search-typesense@0.8.0: - resolution: {integrity: sha512-7cQVHJFtSYg2yT8xhzw6MpudAUZzPjvs51dU3Jwn2WBY+Qek2hHpej9gArd5UaRPffJIZqwBheVCxPpT3kkbdA==} - engines: {node: '>=16.14'} - peerDependencies: - '@docusaurus/core': 2.2.0 - '@docusaurus/theme-common': 2.2.0 - react: ^16.8.4 || ^17.0.2 - react-dom: ^16.8.4 || ^17.0.2 - - dom-converter@0.2.0: - resolution: {integrity: sha512-gd3ypIPfOMr9h5jIKq8E3sHOTCjeirnl0WK5ZdS1AW0Odt0b1PaWaHdJ4Qk4klv+YB9aJBS7mESXjFoDQPu6DA==} - - dom-serializer@0.2.2: - resolution: {integrity: sha512-2/xPb3ORsQ42nHYiSunXkDjPLBaEj/xTwUO4B7XCZQTRk7EBtTOPaygh10YAAh2OI1Qrp6NWfpAhzswj0ydt9g==} - - dom-serializer@1.4.1: - resolution: {integrity: sha512-VHwB3KfrcOOkelEG2ZOfxqLZdfkil8PtJi4P8N2MMXucZq2yLp75ClViUlOVwyoHEDjYU433Aq+5zWP61+RGag==} - - dom-serializer@2.0.0: - resolution: {integrity: sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==} - - domelementtype@1.3.1: - resolution: {integrity: sha512-BSKB+TSpMpFI/HOxCNr1O8aMOTZ8hT3pM3GQ0w/mWRmkhEDSFJkkyzz4XQsBV44BChwGkrDfMyjVD0eA2aFV3w==} - - domelementtype@2.3.0: - resolution: {integrity: sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==} - - domhandler@4.3.1: - resolution: {integrity: sha512-GrwoxYN+uWlzO8uhUXRl0P+kHE4GtVPfYzVLcUxPL7KNdHKj66vvlhiweIHqYYXWlw+T8iLMp42Lm67ghw4WMQ==} - engines: {node: '>= 4'} - - domhandler@5.0.3: - resolution: {integrity: sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==} - engines: {node: '>= 4'} - - domutils@1.7.0: - resolution: {integrity: sha512-Lgd2XcJ/NjEw+7tFvfKxOzCYKZsdct5lczQ2ZaQY8Djz7pfAD3Gbp8ySJWtreII/vDlMVmxwa6pHmdxIYgttDg==} - - domutils@2.8.0: - resolution: {integrity: sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A==} - - domutils@3.1.0: - resolution: {integrity: sha512-H78uMmQtI2AhgDJjWeQmHwJJ2bLPD3GMmO7Zja/ZZh84wkm+4ut+IUnUdRa8uCGX88DiVx1j6FRe1XfxEgjEZA==} - - dot-case@3.0.4: - resolution: {integrity: sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==} - - dot-prop@5.3.0: - resolution: {integrity: sha512-QM8q3zDe58hqUqjraQOmzZ1LIH9SWQJTlEKCH4kJ2oQvLZk7RbQXvtDM2XEq3fwkV9CCvvH4LA0AV+ogFsBM2Q==} - engines: {node: '>=8'} - - duplexer3@0.1.5: - resolution: {integrity: sha512-1A8za6ws41LQgv9HrE/66jyC5yuSjQ3L/KOpFtoBilsAK2iA2wuS5rTt1OCzIvtS2V7nVmedsUU+DGRcjBmOYA==} - - duplexer@0.1.2: - resolution: {integrity: sha512-jtD6YG370ZCIi/9GTaJKQxWTZD045+4R4hTk/x1UyoqadyJ9x9CgSi1RlVDQF8U2sxLLSnFkCaMihqljHIWgMg==} - - eastasianwidth@0.2.0: - resolution: {integrity: sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==} - - ee-first@1.1.1: - resolution: {integrity: sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==} - - electron-to-chromium@1.5.13: - resolution: {integrity: sha512-lbBcvtIJ4J6sS4tb5TLp1b4LyfCdMkwStzXPyAgVgTRAsep4bvrAGaBOP7ZJtQMNJpSQ9SqG4brWOroNaQtm7Q==} - - emoji-regex@8.0.0: - resolution: {integrity: sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==} - - emoji-regex@9.2.2: - resolution: {integrity: sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==} - - emojis-list@3.0.0: - resolution: {integrity: sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q==} - engines: {node: '>= 4'} - - emoticon@3.2.0: - resolution: {integrity: sha512-SNujglcLTTg+lDAcApPNgEdudaqQFiAbJCqzjNxJkvN9vAwCGi0uu8IUVvx+f16h+V44KCY6Y2yboroc9pilHg==} - - encodeurl@1.0.2: - resolution: {integrity: sha512-TPJXq8JqFaVYm2CWmPvnP2Iyo4ZSM7/QKcSmuMLDObfpH5fi7RUGmd/rTDf+rut/saiDiQEeVTNgAmJEdAOx0w==} - engines: {node: '>= 0.8'} - - encoding-sniffer@0.2.0: - resolution: {integrity: sha512-ju7Wq1kg04I3HtiYIOrUrdfdDvkyO9s5XM8QAj/bN61Yo/Vb4vgJxy5vi4Yxk01gWHbrofpPtpxM8bKger9jhg==} - - end-of-stream@1.4.4: - resolution: {integrity: sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q==} - - enhanced-resolve@5.17.1: - resolution: {integrity: sha512-LMHl3dXhTcfv8gM4kEzIUeTQ+7fpdA0l2tUf34BddXPkz2A5xJ5L/Pchd5BL6rdccM9QGvu0sWZzK1Z1t4wwyg==} - engines: {node: '>=10.13.0'} - - entities@2.2.0: - resolution: {integrity: sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==} - - entities@3.0.1: - resolution: {integrity: sha512-WiyBqoomrwMdFG1e0kqvASYfnlb0lp8M5o5Fw2OFq1hNZxxcNk8Ik0Xm7LxzBhuidnZB/UtBqVCgUz3kBOP51Q==} - engines: {node: '>=0.12'} - - entities@4.5.0: - resolution: {integrity: sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==} - engines: {node: '>=0.12'} - - error-ex@1.3.2: - resolution: {integrity: sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==} - - es-abstract@1.23.3: - resolution: {integrity: sha512-e+HfNH61Bj1X9/jLc5v1owaLYuHdeHHSQlkhCBiTK8rBvKaULl/beGMxwrMXjpYrv4pz22BlY570vVePA2ho4A==} - engines: {node: '>= 0.4'} - - es-array-method-boxes-properly@1.0.0: - resolution: {integrity: sha512-wd6JXUmyHmt8T5a2xreUwKcGPq6f1f+WwIJkijUqiGcJz1qqnZgP6XIK+QyIWU5lT7imeNxUll48bziG+TSYcA==} - - es-define-property@1.0.0: - resolution: {integrity: sha512-jxayLKShrEqqzJ0eumQbVhTYQM27CfT1T35+gCgDFoL82JLsXqTJ76zv6A0YLOgEnLUMvLzsDsGIrl8NFpT2gQ==} - engines: {node: '>= 0.4'} - - es-errors@1.3.0: - resolution: {integrity: sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==} - engines: {node: '>= 0.4'} - - es-module-lexer@1.5.4: - resolution: {integrity: sha512-MVNK56NiMrOwitFB7cqDwq0CQutbw+0BvLshJSse0MUNU+y1FC3bUS/AQg7oUng+/wKrrki7JfmwtVHkVfPLlw==} - - es-object-atoms@1.0.0: - resolution: {integrity: sha512-MZ4iQ6JwHOBQjahnjwaC1ZtIBH+2ohjamzAO3oaHcXYup7qxjF2fixyH+Q71voWHeOkI2q/TnJao/KfXYIZWbw==} - engines: {node: '>= 0.4'} - - es-set-tostringtag@2.0.3: - resolution: {integrity: sha512-3T8uNMC3OQTHkFUsFq8r/BwAXLHvU/9O9mE0fBc/MY5iq/8H7ncvO947LmYA6ldWw9Uh8Yhf25zu6n7nML5QWQ==} - engines: {node: '>= 0.4'} - - es-to-primitive@1.2.1: - resolution: {integrity: sha512-QCOllgZJtaUo9miYBcLChTUaHNjJF3PYs1VidD7AwiEj1kYxKeQTctLAezAOH5ZKRH0g2IgPn6KwB4IT8iRpvA==} - engines: {node: '>= 0.4'} - - escalade@3.1.2: - resolution: {integrity: sha512-ErCHMCae19vR8vQGe50xIsVomy19rg6gFu3+r3jkEO46suLMWBksvVyoGgQV+jOfl84ZSOSlmv6Gxa89PmTGmA==} - engines: {node: '>=6'} - - escape-goat@2.1.1: - resolution: {integrity: sha512-8/uIhbG12Csjy2JEW7D9pHbreaVaS/OpN3ycnyvElTdwM5n6GY6W6e2IPemfvGZeUMqZ9A/3GqIZMgKnBhAw/Q==} - engines: {node: '>=8'} - - escape-html@1.0.3: - resolution: {integrity: sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==} - - escape-string-regexp@1.0.5: - resolution: {integrity: sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==} - engines: {node: '>=0.8.0'} - - escape-string-regexp@4.0.0: - resolution: {integrity: sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==} - engines: {node: '>=10'} - - eslint-scope@5.1.1: - resolution: {integrity: sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw==} - engines: {node: '>=8.0.0'} - - esprima@4.0.1: - resolution: {integrity: sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==} - engines: {node: '>=4'} - hasBin: true - - esrecurse@4.3.0: - resolution: {integrity: sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==} - engines: {node: '>=4.0'} - - estraverse@4.3.0: - resolution: {integrity: sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==} - engines: {node: '>=4.0'} - - estraverse@5.3.0: - resolution: {integrity: sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==} - engines: {node: '>=4.0'} - - esutils@2.0.3: - resolution: {integrity: sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==} - engines: {node: '>=0.10.0'} - - eta@1.14.2: - resolution: {integrity: sha512-wZmJAV7EFUG5W8XNXSazIdichnWEhGB1OWg4tnXWPj0CPNUcFdgorGNO6N9p6WBUgoUe4P0OziJYn1+6zxP2aQ==} - engines: {node: '>=6.0.0'} - - etag@1.8.1: - resolution: {integrity: sha512-aIL5Fx7mawVa300al2BnEE4iNvo1qETxLrPI/o05L7z6go7fCw1J6EQmbK4FmJ2AS7kgVF/KEZWufBfdClMcPg==} - engines: {node: '>= 0.6'} - - eval@0.1.8: - resolution: {integrity: sha512-EzV94NYKoO09GLXGjXj9JIlXijVck4ONSr5wiCWDvhsvj5jxSrzTmRU/9C1DyB6uToszLs8aifA6NQ7lEQdvFw==} - engines: {node: '>= 0.8'} - - eventemitter3@4.0.7: - resolution: {integrity: sha512-8guHBZCwKnFhYdHr2ysuRWErTwhoN2X8XELRlrRwpmfeY2jjuUN4taQMsULKUVo1K4DvZl+0pgfyoysHxvmvEw==} - - events@3.3.0: - resolution: {integrity: sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==} - engines: {node: '>=0.8.x'} - - execa@5.1.1: - resolution: {integrity: sha512-8uSpZZocAZRBAPIEINJj3Lo9HyGitllczc27Eh5YYojjMFMn8yHMDMaUHE2Jqfq05D/wucwI4JGURyXt1vchyg==} - engines: {node: '>=10'} - - express@4.19.2: - resolution: {integrity: sha512-5T6nhjsT+EOMzuck8JjBHARTHfMht0POzlA60WV2pMD3gyXw2LZnZ+ueGdNxG+0calOJcWKbpFcuzLZ91YWq9Q==} - engines: {node: '>= 0.10.0'} - - extend-shallow@2.0.1: - resolution: {integrity: sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==} - engines: {node: '>=0.10.0'} - - extend@3.0.2: - resolution: {integrity: sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==} - - fast-deep-equal@3.1.3: - resolution: {integrity: sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==} - - fast-glob@3.3.2: - resolution: {integrity: sha512-oX2ruAFQwf/Orj8m737Y5adxDQO0LAB7/S5MnxCdTNDd4p6BsyIVsv9JQsATbTSq8KHRpLwIHbVlUNatxd+1Ow==} - engines: {node: '>=8.6.0'} - - fast-json-stable-stringify@2.1.0: - resolution: {integrity: sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==} - - fast-uri@3.0.1: - resolution: {integrity: sha512-MWipKbbYiYI0UC7cl8m/i/IWTqfC8YXsqjzybjddLsFjStroQzsHXkc73JutMvBiXmOvapk+axIl79ig5t55Bw==} - - fast-url-parser@1.1.3: - resolution: {integrity: sha512-5jOCVXADYNuRkKFzNJ0dCCewsZiYo0dz8QNYljkOpFC6r2U4OBmKtvm/Tsuh4w1YYdDqDb31a8TVhBJ2OJKdqQ==} - - fastq@1.17.1: - resolution: {integrity: sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w==} - - faye-websocket@0.11.4: - resolution: {integrity: sha512-CzbClwlXAuiRQAlUyfqPgvPoNKTckTPGfwZV4ZdAhVcP2lh9KUxJg2b5GkE7XbjKQ3YJnQ9z6D9ntLAlB+tP8g==} - engines: {node: '>=0.8.0'} - - fbemitter@3.0.0: - resolution: {integrity: sha512-KWKaceCwKQU0+HPoop6gn4eOHk50bBv/VxjJtGMfwmJt3D29JpN4H4eisCtIPA+a8GVBam+ldMMpMjJUvpDyHw==} - - fbjs-css-vars@1.0.2: - resolution: {integrity: sha512-b2XGFAFdWZWg0phtAWLHCk836A1Xann+I+Dgd3Gk64MHKZO44FfoD1KxyvbSh0qZsIoXQGGlVztIY+oitJPpRQ==} - - fbjs@3.0.5: - resolution: {integrity: sha512-ztsSx77JBtkuMrEypfhgc3cI0+0h+svqeie7xHbh1k/IKdcydnvadp/mUaGgjAOXQmQSxsqgaRhS3q9fy+1kxg==} - - fd-slicer@1.1.0: - resolution: {integrity: sha512-cE1qsB/VwyQozZ+q1dGxR8LBYNZeofhEdUNGSMbQD3Gw2lAzX9Zb3uIU6Ebc/Fmyjo9AWWfnn0AUCHqtevs/8g==} - - feed@4.2.2: - resolution: {integrity: sha512-u5/sxGfiMfZNtJ3OvQpXcvotFpYkL0n9u9mM2vkui2nGo8b4wvDkJ8gAkYqbA8QpGyFCv3RK0Z+Iv+9veCS9bQ==} - engines: {node: '>=0.4.0'} - - file-loader@6.2.0: - resolution: {integrity: sha512-qo3glqyTa61Ytg4u73GultjHGjdRyig3tG6lPtyX/jOEJvHif9uB0/OCI2Kif6ctF3caQTW2G5gym21oAsI4pw==} - engines: {node: '>= 10.13.0'} - peerDependencies: - webpack: ^4.0.0 || ^5.0.0 - - filesize@8.0.7: - resolution: {integrity: sha512-pjmC+bkIF8XI7fWaH8KxHcZL3DPybs1roSKP4rKDvy20tAWwIObE4+JIseG2byfGKhud5ZnM4YSGKBz7Sh0ndQ==} - engines: {node: '>= 0.4.0'} - - fill-range@7.1.1: - resolution: {integrity: sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==} - engines: {node: '>=8'} - - finalhandler@1.2.0: - resolution: {integrity: sha512-5uXcUVftlQMFnWC9qu/svkWv3GTd2PfUhK/3PLkYNAe7FbqJMt3515HaxE6eRL74GdsriiwujiawdaB1BpEISg==} - engines: {node: '>= 0.8'} - - find-cache-dir@3.3.2: - resolution: {integrity: sha512-wXZV5emFEjrridIgED11OoUKLxiYjAcqot/NJdAkOhlJ+vGzwhOAfcG5OX1jP+S0PcjEn8bdMJv+g2jwQ3Onig==} - engines: {node: '>=8'} - - find-up@3.0.0: - resolution: {integrity: sha512-1yD6RmLI1XBfxugvORwlck6f75tYL+iR0jqwsOrOxMZyGYqUuDhJ0l4AXdO1iX/FTs9cBAMEk1gWSEx1kSbylg==} - engines: {node: '>=6'} - - find-up@4.1.0: - resolution: {integrity: sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==} - engines: {node: '>=8'} - - find-up@5.0.0: - resolution: {integrity: sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==} - engines: {node: '>=10'} - - flat@5.0.2: - resolution: {integrity: sha512-b6suED+5/3rTpUBdG1gupIl8MPFCAMA0QXwmljLhvCUKcUvdE4gWky9zpuGCcXHOsz4J9wPGNWq6OKpmIzz3hQ==} - hasBin: true - - flux@4.0.4: - resolution: {integrity: sha512-NCj3XlayA2UsapRpM7va6wU1+9rE5FIL7qoMcmxWHRzbp0yujihMBm9BBHZ1MDIk5h5o2Bl6eGiCe8rYELAmYw==} - peerDependencies: - react: ^15.0.2 || ^16.0.0 || ^17.0.0 - - follow-redirects@1.15.6: - resolution: {integrity: sha512-wWN62YITEaOpSK584EZXJafH1AGpO8RVgElfkuXbTOrPX4fIfOyEpW/CsiNd8JdYrAoOvafRTOEnvsO++qCqFA==} - engines: {node: '>=4.0'} - peerDependencies: - debug: '*' - peerDependenciesMeta: - debug: - optional: true - - for-each@0.3.3: - resolution: {integrity: sha512-jqYfLp7mo9vIyQf8ykW2v7A+2N4QjeCeI5+Dz9XraiO1ign81wjiH7Fb9vSOWvQfNtmSa4H2RoQTrrXivdUZmw==} - - foreground-child@3.3.0: - resolution: {integrity: sha512-Ld2g8rrAyMYFXBhEqMz8ZAHBi4J4uS1i/CxGMDnjyFWddMXLVcDp051DZfu+t7+ab7Wv6SMqpWmyFIj5UbfFvg==} - engines: {node: '>=14'} - - fork-ts-checker-webpack-plugin@6.5.3: - resolution: {integrity: sha512-SbH/l9ikmMWycd5puHJKTkZJKddF4iRLyW3DeZ08HTI7NGyLS38MXd/KGgeWumQO7YNQbW2u/NtPT2YowbPaGQ==} - engines: {node: '>=10', yarn: '>=1.0.0'} - peerDependencies: - eslint: '>= 6' - typescript: '>= 2.7' - vue-template-compiler: '*' - webpack: '>= 4' - peerDependenciesMeta: - eslint: - optional: true - vue-template-compiler: - optional: true - - form-data@4.0.0: - resolution: {integrity: sha512-ETEklSGi5t0QMZuiXoA/Q6vcnxcLQP5vdugSpuAyi6SVGi2clPPp+xgEhuMaHC+zGgn31Kd235W35f7Hykkaww==} - engines: {node: '>= 6'} - - forwarded@0.2.0: - resolution: {integrity: sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow==} - engines: {node: '>= 0.6'} - - fraction.js@4.3.7: - resolution: {integrity: sha512-ZsDfxO51wGAXREY55a7la9LScWpwv9RxIrYABrlvOFBlH/ShPnrtsXeuUIfXKKOVicNxQ+o8JTbJvjS4M89yew==} - - fresh@0.5.2: - resolution: {integrity: sha512-zJ2mQYM18rEFOudeV4GShTGIQ7RbzA7ozbU9I/XBpm7kqgMywgmylMwXHxZJmkVoYkna9d2pVXVXPdYTP9ej8Q==} - engines: {node: '>= 0.6'} - - fs-extra@10.1.0: - resolution: {integrity: sha512-oRXApq54ETRj4eMiFzGnHWGy+zo5raudjuxN0b8H7s/RU2oW0Wvsx9O0ACRN/kRq9E8Vu/ReskGB5o3ji+FzHQ==} - engines: {node: '>=12'} - - fs-extra@9.1.0: - resolution: {integrity: sha512-hcg3ZmepS30/7BSFqRvoo3DOMQu7IjqxO5nCDt+zM9XWjb33Wg7ziNT+Qvqbuc3+gWpzO02JubVyk2G4Zvo1OQ==} - engines: {node: '>=10'} - - fs-minipass@1.2.7: - resolution: {integrity: sha512-GWSSJGFy4e9GUeCcbIkED+bgAoFyj7XF1mV8rma3QW4NIqX9Kyx79N/PF61H5udOV3aY1IaMLs6pGbH71nlCTA==} - - fs-monkey@1.0.6: - resolution: {integrity: sha512-b1FMfwetIKymC0eioW7mTywihSQE4oLzQn1dB6rZB5fx/3NpNEdAWeCSMB+60/AeT0TCXsxzAlcYVEFCTAksWg==} - - fs.realpath@1.0.0: - resolution: {integrity: sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==} - - fsevents@2.3.3: - resolution: {integrity: sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==} - engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0} - os: [darwin] - - function-bind@1.1.2: - resolution: {integrity: sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==} - - function.prototype.name@1.1.6: - resolution: {integrity: sha512-Z5kx79swU5P27WEayXM1tBi5Ze/lbIyiNgU3qyXUOf9b2rgXYyF9Dy9Cx+IQv/Lc8WCG6L82zwUPpSS9hGehIg==} - engines: {node: '>= 0.4'} - - functions-have-names@1.2.3: - resolution: {integrity: sha512-xckBUXyTIqT97tq2x2AMb+g163b5JFysYk0x4qxNFwbfQkmNZoiRHb6sPzI9/QV33WeuvVYBUIiD4NzNIyqaRQ==} - - gensync@1.0.0-beta.2: - resolution: {integrity: sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==} - engines: {node: '>=6.9.0'} - - get-intrinsic@1.2.4: - resolution: {integrity: sha512-5uYhsJH8VJBTv7oslg4BznJYhDoRI6waYCxMmCdnTrcCrHA/fCFKoTFz2JKKE0HdDFUF7/oQuhzumXJK7paBRQ==} - engines: {node: '>= 0.4'} - - get-own-enumerable-property-symbols@3.0.2: - resolution: {integrity: sha512-I0UBV/XOz1XkIJHEUDMZAbzCThU/H8DxmSfmdGcKPnVhu2VfFqr34jr9777IyaTYvxjedWhqVIilEDsCdP5G6g==} - - get-stdin@9.0.0: - resolution: {integrity: sha512-dVKBjfWisLAicarI2Sf+JuBE/DghV4UzNAVe9yhEJuzeREd3JhOTE9cUaJTeSa77fsbQUK3pcOpJfM59+VKZaA==} - engines: {node: '>=12'} - - get-stream@4.1.0: - resolution: {integrity: sha512-GMat4EJ5161kIy2HevLlr4luNjBgvmj413KaQA7jt4V8B4RDsfpHk7WQ9GVqfYyyx8OS/L66Kox+rJRNklLK7w==} - engines: {node: '>=6'} - - get-stream@5.2.0: - resolution: {integrity: sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==} - engines: {node: '>=8'} - - get-stream@6.0.1: - resolution: {integrity: sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==} - engines: {node: '>=10'} - - get-symbol-description@1.0.2: - resolution: {integrity: sha512-g0QYk1dZBxGwk+Ngc+ltRH2IBp2f7zBkBMBJZCDerh6EhlhSR6+9irMCuT/09zD6qkarHUSn529sK/yL4S27mg==} - engines: {node: '>= 0.4'} - - github-slugger@1.5.0: - resolution: {integrity: sha512-wIh+gKBI9Nshz2o46B0B3f5k/W+WI9ZAv6y5Dn5WJ5SK1t0TnDimB4WE5rmTD05ZAIn8HALCZVmCsvj0w0v0lw==} - - glob-parent@5.1.2: - resolution: {integrity: sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==} - engines: {node: '>= 6'} - - glob-parent@6.0.2: - resolution: {integrity: sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==} - engines: {node: '>=10.13.0'} - - glob-to-regexp@0.4.1: - resolution: {integrity: sha512-lkX1HJXwyMcprw/5YUZc2s7DrpAiHB21/V+E1rHUrVNokkvB6bqMzT0VfV6/86ZNabt1k14YOIaT7nDvOX3Iiw==} - - glob@10.2.7: - resolution: {integrity: sha512-jTKehsravOJo8IJxUGfZILnkvVJM/MOfHRs8QcXolVef2zNI9Tqyy5+SeuOAZd3upViEZQLyFpQhYiHLrMUNmA==} - engines: {node: '>=16 || 14 >=14.17'} - hasBin: true - - glob@7.2.3: - resolution: {integrity: sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==} - deprecated: Glob versions prior to v9 are no longer supported - - global-dirs@3.0.1: - resolution: {integrity: sha512-NBcGGFbBA9s1VzD41QXDG+3++t9Mn5t1FpLdhESY6oKY4gYTFpX4wO3sqGUa0Srjtbfj3szX0RnemmrVRUdULA==} - engines: {node: '>=10'} - - global-modules@2.0.0: - resolution: {integrity: sha512-NGbfmJBp9x8IxyJSd1P+otYK8vonoJactOogrVfFRIAEY1ukil8RSKDz2Yo7wh1oihl51l/r6W4epkeKJHqL8A==} - engines: {node: '>=6'} - - global-prefix@3.0.0: - resolution: {integrity: sha512-awConJSVCHVGND6x3tmMaKcQvwXLhjdkmomy2W+Goaui8YPgYgXJZewhg3fWC+DlfqqQuWg8AwqjGTD2nAPVWg==} - engines: {node: '>=6'} - - globals@11.12.0: - resolution: {integrity: sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==} - engines: {node: '>=4'} - - globalthis@1.0.4: - resolution: {integrity: sha512-DpLKbNU4WylpxJykQujfCcwYWiV/Jhm50Goo0wrVILAv5jOr9d+H+UR3PhSCD2rCCEIg0uc+G+muBTwD54JhDQ==} - engines: {node: '>= 0.4'} - - globby@11.1.0: - resolution: {integrity: sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==} - engines: {node: '>=10'} - - globby@13.2.2: - resolution: {integrity: sha512-Y1zNGV+pzQdh7H39l9zgB4PJqjRNqydvdYCDG4HFXM4XuvSaQQlEc91IU1yALL8gUTDomgBAfz3XJdmUS+oo0w==} - engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} - - gopd@1.0.1: - resolution: {integrity: sha512-d65bNlIadxvpb/A2abVdlqKqV563juRnZ1Wtk6s1sIR8uNsXR70xqIzVqxVf1eTqDunwT2MkczEeaezCKTZhwA==} - - got@9.6.0: - resolution: {integrity: sha512-R7eWptXuGYxwijs0eV+v3o6+XH1IqVK8dJOEecQfTmkncw9AV4dcw/Dhxi8MdlqPthxxpZyizMzyg8RTmEsG+Q==} - engines: {node: '>=8.6'} - - graceful-fs@4.2.11: - resolution: {integrity: sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==} - - gray-matter@4.0.3: - resolution: {integrity: sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==} - engines: {node: '>=6.0'} - - gzip-size@6.0.0: - resolution: {integrity: sha512-ax7ZYomf6jqPTQ4+XCpUGyXKHk5WweS+e05MBO4/y3WJ5RkmPXNKvX+bx1behVILVwr6JSQvZAku021CHPXG3Q==} - engines: {node: '>=10'} - - handle-thing@2.0.1: - resolution: {integrity: sha512-9Qn4yBxelxoh2Ow62nP+Ka/kMnOXRi8BXnRaUwezLNhqelnN49xKz4F/dPP8OYLxLxq6JDtZb2i9XznUQbNPTg==} - - has-bigints@1.0.2: - resolution: {integrity: sha512-tSvCKtBr9lkF0Ex0aQiP9N+OpV4zi2r/Nee5VkRDbaqv35RLYMzbwQfFSZZH0kR+Rd6302UJZ2p/bJCEoR3VoQ==} - - has-flag@3.0.0: - resolution: {integrity: sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==} - engines: {node: '>=4'} - - has-flag@4.0.0: - resolution: {integrity: sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==} - engines: {node: '>=8'} - - has-property-descriptors@1.0.2: - resolution: {integrity: sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg==} - - has-proto@1.0.3: - resolution: {integrity: sha512-SJ1amZAJUiZS+PhsVLf5tGydlaVB8EdFpaSO4gmiUKUOxk8qzn5AIy4ZeJUmh22znIdk/uMAUT2pl3FxzVUH+Q==} - engines: {node: '>= 0.4'} - - has-symbols@1.0.3: - resolution: {integrity: sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A==} - engines: {node: '>= 0.4'} - - has-tostringtag@1.0.2: - resolution: {integrity: sha512-NqADB8VjPFLM2V0VvHUewwwsw0ZWBaIdgo+ieHtK3hasLz4qeCRjYcqfB6AQrBggRKppKF8L52/VqdVsO47Dlw==} - engines: {node: '>= 0.4'} - - has-yarn@2.1.0: - resolution: {integrity: sha512-UqBRqi4ju7T+TqGNdqAO0PaSVGsDGJUBQvk9eUWNGRY1CFGDzYhLWoM7JQEemnlvVcv/YEmc2wNW8BC24EnUsw==} - engines: {node: '>=8'} - - hasown@2.0.2: - resolution: {integrity: sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==} - engines: {node: '>= 0.4'} - - hast-to-hyperscript@9.0.1: - resolution: {integrity: sha512-zQgLKqF+O2F72S1aa4y2ivxzSlko3MAvxkwG8ehGmNiqd98BIN3JM1rAJPmplEyLmGLO2QZYJtIneOSZ2YbJuA==} - - hast-util-from-parse5@6.0.1: - resolution: {integrity: sha512-jeJUWiN5pSxW12Rh01smtVkZgZr33wBokLzKLwinYOUfSzm1Nl/c3GUGebDyOKjdsRgMvoVbV0VpAcpjF4NrJA==} - - hast-util-parse-selector@2.2.5: - resolution: {integrity: sha512-7j6mrk/qqkSehsM92wQjdIgWM2/BW61u/53G6xmC8i1OmEdKLHbk419QKQUjz6LglWsfqoiHmyMRkP1BGjecNQ==} - - hast-util-raw@6.0.1: - resolution: {integrity: sha512-ZMuiYA+UF7BXBtsTBNcLBF5HzXzkyE6MLzJnL605LKE8GJylNjGc4jjxazAHUtcwT5/CEt6afRKViYB4X66dig==} - - hast-util-to-parse5@6.0.0: - resolution: {integrity: sha512-Lu5m6Lgm/fWuz8eWnrKezHtVY83JeRGaNQ2kn9aJgqaxvVkFCZQBEhgodZUDUvoodgyROHDb3r5IxAEdl6suJQ==} - - hastscript@6.0.0: - resolution: {integrity: sha512-nDM6bvd7lIqDUiYEiu5Sl/+6ReP0BMk/2f4U/Rooccxkj0P5nm+acM5PrGJ/t5I8qPGiqZSE6hVAwZEdZIvP4w==} - - he@1.2.0: - resolution: {integrity: sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw==} - hasBin: true - - history@4.10.1: - resolution: {integrity: sha512-36nwAD620w12kuzPAsyINPWJqlNbij+hpK1k9XRloDtym8mxzGYl2c17LnV6IAGB2Dmg4tEa7G7DlawS0+qjew==} - - hoist-non-react-statics@3.3.2: - resolution: {integrity: sha512-/gGivxi8JPKWNm/W0jSmzcMPpfpPLc3dY/6GxhX2hQ9iGj3aDfklV4ET7NjKpSinLpJ5vafa9iiGIEZg10SfBw==} - - hpack.js@2.1.6: - resolution: {integrity: sha512-zJxVehUdMGIKsRaNt7apO2Gqp0BdqW5yaiGHXXmbpvxgBYVZnAql+BJb4RO5ad2MgpbZKn5G6nMnegrH1FcNYQ==} - - html-entities@2.5.2: - resolution: {integrity: sha512-K//PSRMQk4FZ78Kyau+mZurHn3FH0Vwr+H36eE0rPbeYkRRi9YxceYPhuN60UwWorxyKHhqoAJl2OFKa4BVtaA==} - - html-escaper@2.0.2: - resolution: {integrity: sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg==} - - html-minifier-terser@6.1.0: - resolution: {integrity: sha512-YXxSlJBZTP7RS3tWnQw74ooKa6L9b9i9QYXY21eUEvhZ3u9XLfv6OnFsQq6RxkhHygsaUMvYsZRV5rU/OVNZxw==} - engines: {node: '>=12'} - hasBin: true - - html-tags@3.3.1: - resolution: {integrity: sha512-ztqyC3kLto0e9WbNp0aeP+M3kTt+nbaIveGmUxAtZa+8iFgKLUOD4YKM5j+f3QD89bra7UeumolZHKuOXnTmeQ==} - engines: {node: '>=8'} - - html-void-elements@1.0.5: - resolution: {integrity: sha512-uE/TxKuyNIcx44cIWnjr/rfIATDH7ZaOMmstu0CwhFG1Dunhlp4OC6/NMbhiwoq5BpW0ubi303qnEk/PZj614w==} - - html-webpack-plugin@5.6.0: - resolution: {integrity: sha512-iwaY4wzbe48AfKLZ/Cc8k0L+FKG6oSNRaZ8x5A/T/IVDGyXcbHncM9TdDa93wn0FsSm82FhTKW7f3vS61thXAw==} - engines: {node: '>=10.13.0'} - peerDependencies: - '@rspack/core': 0.x || 1.x - webpack: ^5.20.0 - peerDependenciesMeta: - '@rspack/core': - optional: true - webpack: - optional: true - - htmlparser2@6.1.0: - resolution: {integrity: sha512-gyyPk6rgonLFEDGoeRgQNaEUvdJ4ktTmmUh/h2t7s+M8oPpIPxgNACWa+6ESR57kXstwqPiCut0V8NRpcwgU7A==} - - htmlparser2@9.1.0: - resolution: {integrity: sha512-5zfg6mHUoaer/97TxnGpxmbR7zJtPwIYFMZ/H5ucTlPZhKvtum05yiPK3Mgai3a0DyVxv7qYqoweaEd2nrYQzQ==} - - http-cache-semantics@4.1.1: - resolution: {integrity: sha512-er295DKPVsV82j5kw1Gjt+ADA/XYHsajl82cGNQG2eyoPkvgUhX+nDIyelzhIWbbsXP39EHcI6l5tYs2FYqYXQ==} - - http-deceiver@1.2.7: - resolution: {integrity: sha512-LmpOGxTfbpgtGVxJrj5k7asXHCgNZp5nLfp+hWc8QQRqtb7fUy6kRY3BO1h9ddF6yIPYUARgxGOwB42DnxIaNw==} - - http-errors@1.6.3: - resolution: {integrity: sha512-lks+lVC8dgGyh97jxvxeYTWQFvh4uw4yC12gVl63Cg30sjPX4wuGcdkICVXDAESr6OJGjqGA8Iz5mkeN6zlD7A==} - engines: {node: '>= 0.6'} - - http-errors@2.0.0: - resolution: {integrity: sha512-FtwrG/euBzaEjYeRqOgly7G0qviiXoJWnvEH2Z1plBdXgbyjv34pHTSb9zoeHMyDy33+DWy5Wt9Wo+TURtOYSQ==} - engines: {node: '>= 0.8'} - - http-parser-js@0.5.8: - resolution: {integrity: sha512-SGeBX54F94Wgu5RH3X5jsDtf4eHyRogWX1XGT3b4HuW3tQPM4AaBzoUji/4AAJNXCEOWZ5O0DgZmJw1947gD5Q==} - - http-proxy-middleware@2.0.6: - resolution: {integrity: sha512-ya/UeJ6HVBYxrgYotAZo1KvPWlgB48kUJLDePFeneHsVujFaW5WNj2NgWCAE//B1Dl02BIfYlpNgBy8Kf8Rjmw==} - engines: {node: '>=12.0.0'} - peerDependencies: - '@types/express': ^4.17.13 - peerDependenciesMeta: - '@types/express': - optional: true - - http-proxy@1.18.1: - resolution: {integrity: sha512-7mz/721AbnJwIVbnaSv1Cz3Am0ZLT/UBwkC92VlxhXv/k/BBQfM2fXElQNC27BVGr0uwUpplYPQM9LnaBMR5NQ==} - engines: {node: '>=8.0.0'} - - human-signals@2.1.0: - resolution: {integrity: sha512-B4FFZ6q/T2jhhksgkbEW3HBvWIfDW85snkQgawt07S7J5QXTk6BkNV+0yAeZrM5QpMAdYlocGoljn0sJ/WQkFw==} - engines: {node: '>=10.17.0'} - - iconv-lite@0.4.24: - resolution: {integrity: sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==} - engines: {node: '>=0.10.0'} - - iconv-lite@0.6.3: - resolution: {integrity: sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==} - engines: {node: '>=0.10.0'} - - icss-utils@5.1.0: - resolution: {integrity: sha512-soFhflCVWLfRNOPU3iv5Z9VUdT44xFRbzjLsEzSr5AQmgqPMTHdU3PMT1Cf1ssx8fLNJDA1juftYl+PUcv3MqA==} - engines: {node: ^10 || ^12 || >= 14} - peerDependencies: - postcss: ^8.1.0 - - ignore@5.2.4: - resolution: {integrity: sha512-MAb38BcSbH0eHNBxn7ql2NH/kX33OkB3lZ1BNdh7ENeRChHTYsTvWrMubiIAMNS2llXEEgZ1MUOBtXChP3kaFQ==} - engines: {node: '>= 4'} - - ignore@5.3.2: - resolution: {integrity: sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==} - engines: {node: '>= 4'} - - image-size@1.1.1: - resolution: {integrity: sha512-541xKlUw6jr/6gGuk92F+mYM5zaFAc5ahphvkqvNe2bQ6gVBkd6bfrmVJ2t4KDAfikAYZyIqTnktX3i6/aQDrQ==} - engines: {node: '>=16.x'} - hasBin: true - - immer@9.0.21: - resolution: {integrity: sha512-bc4NBHqOqSfRW7POMkHd51LvClaeMXpm8dx0e8oE2GORbq5aRK7Bxl4FyzVLdGtLmvLKL7BTDBG5ACQm4HWjTA==} - - import-fresh@3.3.0: - resolution: {integrity: sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==} - engines: {node: '>=6'} - - import-lazy@2.1.0: - resolution: {integrity: sha512-m7ZEHgtw69qOGw+jwxXkHlrlIPdTGkyh66zXZ1ajZbxkDBNjSY/LGbmjc7h0s2ELsUDTAhFr55TrPSSqJGPG0A==} - engines: {node: '>=4'} - - imurmurhash@0.1.4: - resolution: {integrity: sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==} - engines: {node: '>=0.8.19'} - - indent-string@4.0.0: - resolution: {integrity: sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==} - engines: {node: '>=8'} - - infima@0.2.0-alpha.42: - resolution: {integrity: sha512-ift8OXNbQQwtbIt6z16KnSWP7uJ/SysSMFI4F87MNRTicypfl4Pv3E2OGVv6N3nSZFJvA8imYulCBS64iyHYww==} - engines: {node: '>=12'} - - inflight@1.0.6: - resolution: {integrity: sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==} - deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. - - inherits@2.0.3: - resolution: {integrity: sha512-x00IRNXNy63jwGkJmzPigoySHbaqpNuzKbBOmzK+g2OdZpQ9w+sxCN+VSB3ja7IAge2OP2qpfxTjeNcyjmW1uw==} - - inherits@2.0.4: - resolution: {integrity: sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==} - - ini@1.3.8: - resolution: {integrity: sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew==} - - ini@2.0.0: - resolution: {integrity: sha512-7PnF4oN3CvZF23ADhA5wRaYEQpJ8qygSkbtTXWBeXWXmEVRXK+1ITciHWwHhsjv1TmW0MgacIv6hEi5pX5NQdA==} - engines: {node: '>=10'} - - ini@3.0.1: - resolution: {integrity: sha512-it4HyVAUTKBc6m8e1iXWvXSTdndF7HbdN713+kvLrymxTaU4AUBWrJ4vEooP+V7fexnVD3LKcBshjGGPefSMUQ==} - engines: {node: ^12.13.0 || ^14.15.0 || >=16.0.0} - - inline-style-parser@0.1.1: - resolution: {integrity: sha512-7NXolsK4CAS5+xvdj5OMMbI962hU/wvwoxk+LWR9Ek9bVtyuuYScDN6eS0rUm6TxApFpw7CX1o4uJzcd4AyD3Q==} - - internal-slot@1.0.7: - resolution: {integrity: sha512-NGnrKwXzSms2qUUih/ILZ5JBqNTSa1+ZmP6flaIp6KmSElgE9qdndzS3cqjrDovwFdmwsGsLdeFgB6suw+1e9g==} - engines: {node: '>= 0.4'} - - interpret@1.4.0: - resolution: {integrity: sha512-agE4QfB2Lkp9uICn7BAqoscw4SZP9kTE2hxiFI3jBPmXJfdqiahTbUuKGsMoN2GtqL9AxhYioAcVvgsb1HvRbA==} - engines: {node: '>= 0.10'} - - invariant@2.2.4: - resolution: {integrity: sha512-phJfQVBuaJM5raOpJjSfkiD6BpbCE4Ns//LaXl6wGYtUBY83nWS6Rf9tXm2e8VaK60JEjYldbPif/A2B1C2gNA==} - - ipaddr.js@1.9.1: - resolution: {integrity: sha512-0KI/607xoxSToH7GjN1FfSbLoU0+btTicjsQSWQlh/hZykN8KpmMf7uYwPW3R+akZ6R/w18ZlXSHBYXiYUPO3g==} - engines: {node: '>= 0.10'} - - ipaddr.js@2.2.0: - resolution: {integrity: sha512-Ag3wB2o37wslZS19hZqorUnrnzSkpOVy+IiiDEiTqNubEYpYuHWIf6K4psgN2ZWKExS4xhVCrRVfb/wfW8fWJA==} - engines: {node: '>= 10'} - - is-alphabetical@1.0.4: - resolution: {integrity: sha512-DwzsA04LQ10FHTZuL0/grVDk4rFoVH1pjAToYwBrHSxcrBIGQuXrQMtD5U1b0U2XVgKZCTLLP8u2Qxqhy3l2Vg==} - - is-alphanumerical@1.0.4: - resolution: {integrity: sha512-UzoZUr+XfVz3t3v4KyGEniVL9BDRoQtY7tOyrRybkVNjDFWyo1yhXNGrrBTQxp3ib9BLAWs7k2YKBQsFRkZG9A==} - - is-array-buffer@3.0.4: - resolution: {integrity: sha512-wcjaerHw0ydZwfhiKbXJWLDY8A7yV7KhjQOpb83hGgGfId/aQa4TOvwyzn2PuswW2gPCYEL/nEAiSVpdOj1lXw==} - engines: {node: '>= 0.4'} - - is-arrayish@0.2.1: - resolution: {integrity: sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg==} - - is-bigint@1.0.4: - resolution: {integrity: sha512-zB9CruMamjym81i2JZ3UMn54PKGsQzsJeo6xvN3HJJ4CAsQNB6iRutp2To77OfCNuoxspsIhzaPoO1zyCEhFOg==} - - is-binary-path@2.1.0: - resolution: {integrity: sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==} - engines: {node: '>=8'} - - is-boolean-object@1.1.2: - resolution: {integrity: sha512-gDYaKHJmnj4aWxyj6YHyXVpdQawtVLHU5cb+eztPGczf6cjuTdwve5ZIEfgXqH4e57An1D1AKf8CZ3kYrQRqYA==} - engines: {node: '>= 0.4'} - - is-buffer@2.0.5: - resolution: {integrity: sha512-i2R6zNFDwgEHJyQUtJEk0XFi1i0dPFn/oqjK3/vPCcDeJvW5NQ83V8QbicfF1SupOaB0h8ntgBC2YiE7dfyctQ==} - engines: {node: '>=4'} - - is-callable@1.2.7: - resolution: {integrity: sha512-1BC0BVFhS/p0qtw6enp8e+8OD0UrK0oFLztSjNzhcKA3WDuJxxAPXzPuPtKkjEY9UUoEWlX/8fgKeu2S8i9JTA==} - engines: {node: '>= 0.4'} - - is-ci@2.0.0: - resolution: {integrity: sha512-YfJT7rkpQB0updsdHLGWrvhBJfcfzNNawYDNIyQXJz0IViGf75O8EBPKSdvw2rF+LGCsX4FZ8tcr3b19LcZq4w==} - hasBin: true - - is-core-module@2.15.1: - resolution: {integrity: sha512-z0vtXSwucUJtANQWldhbtbt7BnL0vxiFjIdDLAatwhDYty2bad6s+rijD6Ri4YuYJubLzIJLUidCh09e1djEVQ==} - engines: {node: '>= 0.4'} - - is-data-view@1.0.1: - resolution: {integrity: sha512-AHkaJrsUVW6wq6JS8y3JnM/GJF/9cf+k20+iDzlSaJrinEo5+7vRiteOSwBhHRiAyQATN1AmY4hwzxJKPmYf+w==} - engines: {node: '>= 0.4'} - - is-date-object@1.0.5: - resolution: {integrity: sha512-9YQaSxsAiSwcvS33MBk3wTCVnWK+HhF8VZR2jRxehM16QcVOdHqPn4VPHmRK4lSr38n9JriurInLcP90xsYNfQ==} - engines: {node: '>= 0.4'} - - is-decimal@1.0.4: - resolution: {integrity: sha512-RGdriMmQQvZ2aqaQq3awNA6dCGtKpiDFcOzrTWrDAT2MiWrKQVPmxLGHl7Y2nNu6led0kEyoX0enY0qXYsv9zw==} - - is-docker@2.2.1: - resolution: {integrity: sha512-F+i2BKsFrH66iaUFc0woD8sLy8getkwTwtOBjvs56Cx4CgJDeKQeqfz8wAYiSb8JOprWhHH5p77PbmYCvvUuXQ==} - engines: {node: '>=8'} - hasBin: true - - is-extendable@0.1.1: - resolution: {integrity: sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==} - engines: {node: '>=0.10.0'} - - is-extglob@2.1.1: - resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==} - engines: {node: '>=0.10.0'} - - is-fullwidth-code-point@3.0.0: - resolution: {integrity: sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==} - engines: {node: '>=8'} - - is-glob@4.0.3: - resolution: {integrity: sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==} - engines: {node: '>=0.10.0'} - - is-hexadecimal@1.0.4: - resolution: {integrity: sha512-gyPJuv83bHMpocVYoqof5VDiZveEoGoFL8m3BXNb2VW8Xs+rz9kqO8LOQ5DH6EsuvilT1ApazU0pyl+ytbPtlw==} - - is-installed-globally@0.4.0: - resolution: {integrity: sha512-iwGqO3J21aaSkC7jWnHP/difazwS7SFeIqxv6wEtLU8Y5KlzFTjyqcSIT0d8s4+dDhKytsk9PJZ2BkS5eZwQRQ==} - engines: {node: '>=10'} - - is-negative-zero@2.0.3: - resolution: {integrity: sha512-5KoIu2Ngpyek75jXodFvnafB6DJgr3u8uuK0LEZJjrU19DrMD3EVERaR8sjz8CCGgpZvxPl9SuE1GMVPFHx1mw==} - engines: {node: '>= 0.4'} - - is-npm@5.0.0: - resolution: {integrity: sha512-WW/rQLOazUq+ST/bCAVBp/2oMERWLsR7OrKyt052dNDk4DHcDE0/7QSXITlmi+VBcV13DfIbysG3tZJm5RfdBA==} - engines: {node: '>=10'} - - is-number-object@1.0.7: - resolution: {integrity: sha512-k1U0IRzLMo7ZlYIfzRu23Oh6MiIFasgpb9X76eqfFZAqwH44UI4KTBvBYIZ1dSL9ZzChTB9ShHfLkR4pdW5krQ==} - engines: {node: '>= 0.4'} - - is-number@7.0.0: - resolution: {integrity: sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==} - engines: {node: '>=0.12.0'} - - is-obj@1.0.1: - resolution: {integrity: sha512-l4RyHgRqGN4Y3+9JHVrNqO+tN0rV5My76uW5/nuO4K1b6vw5G8d/cmFjP9tRfEsdhZNt0IFdZuK/c2Vr4Nb+Qg==} - engines: {node: '>=0.10.0'} - - is-obj@2.0.0: - resolution: {integrity: sha512-drqDG3cbczxxEJRoOXcOjtdp1J/lyp1mNn0xaznRs8+muBhgQcrnbspox5X5fOw0HnMnbfDzvnEMEtqDEJEo8w==} - engines: {node: '>=8'} - - is-path-cwd@2.2.0: - resolution: {integrity: sha512-w942bTcih8fdJPJmQHFzkS76NEP8Kzzvmw92cXsazb8intwLqPibPPdXf4ANdKV3rYMuuQYGIWtvz9JilB3NFQ==} - engines: {node: '>=6'} - - is-path-inside@3.0.3: - resolution: {integrity: sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==} - engines: {node: '>=8'} - - is-plain-obj@2.1.0: - resolution: {integrity: sha512-YWnfyRwxL/+SsrWYfOpUtz5b3YD+nyfkHvjbcanzk8zgyO4ASD67uVMRt8k5bM4lLMDnXfriRhOpemw+NfT1eA==} - engines: {node: '>=8'} - - is-plain-obj@3.0.0: - resolution: {integrity: sha512-gwsOE28k+23GP1B6vFl1oVh/WOzmawBrKwo5Ev6wMKzPkaXaCDIQKzLnvsA42DRlbVTWorkgTKIviAKCWkfUwA==} - engines: {node: '>=10'} - - is-plain-object@2.0.4: - resolution: {integrity: sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==} - engines: {node: '>=0.10.0'} - - is-regex@1.1.4: - resolution: {integrity: sha512-kvRdxDsxZjhzUX07ZnLydzS1TU/TJlTUHHY4YLL87e37oUA49DfkLqgy+VjFocowy29cKvcSiu+kIv728jTTVg==} - engines: {node: '>= 0.4'} - - is-regexp@1.0.0: - resolution: {integrity: sha512-7zjFAPO4/gwyQAAgRRmqeEeyIICSdmCqa3tsVHMdBzaXXRiqopZL4Cyghg/XulGWrtABTpbnYYzzIRffLkP4oA==} - engines: {node: '>=0.10.0'} - - is-root@2.1.0: - resolution: {integrity: sha512-AGOriNp96vNBd3HtU+RzFEc75FfR5ymiYv8E553I71SCeXBiMsVDUtdio1OEFvrPyLIQ9tVR5RxXIFe5PUFjMg==} - engines: {node: '>=6'} - - is-shared-array-buffer@1.0.3: - resolution: {integrity: sha512-nA2hv5XIhLR3uVzDDfCIknerhx8XUKnstuOERPNNIinXG7v9u+ohXF67vxm4TPTEPU6lm61ZkwP3c9PCB97rhg==} - engines: {node: '>= 0.4'} - - is-stream@2.0.1: - resolution: {integrity: sha512-hFoiJiTl63nn+kstHGBtewWSKnQLpyb155KHheA1l39uvtO9nWIop1p3udqPcUd/xbF1VLMO4n7OI6p7RbngDg==} - engines: {node: '>=8'} - - is-string@1.0.7: - resolution: {integrity: sha512-tE2UXzivje6ofPW7l23cjDOMa09gb7xlAqG6jG5ej6uPV32TlWP3NKPigtaGeHNu9fohccRYvIiZMfOOnOYUtg==} - engines: {node: '>= 0.4'} - - is-symbol@1.0.4: - resolution: {integrity: sha512-C/CPBqKWnvdcxqIARxyOh4v1UUEOCHpgDa0WYgpKDFMszcrPcffg5uhwSgPCLD2WWxmq6isisz87tzT01tuGhg==} - engines: {node: '>= 0.4'} - - is-typed-array@1.1.13: - resolution: {integrity: sha512-uZ25/bUAlUY5fR4OKT4rZQEBrzQWYV9ZJYGGsUmEJ6thodVJ1HX64ePQ6Z0qPWP+m+Uq6e9UugrE38jeYsDSMw==} - engines: {node: '>= 0.4'} - - is-typedarray@1.0.0: - resolution: {integrity: sha512-cyA56iCMHAh5CdzjJIa4aohJyeO1YbwLi3Jc35MmRU6poroFjIGZzUzupGiRPOjgHg9TLu43xbpwXk523fMxKA==} - - is-weakref@1.0.2: - resolution: {integrity: sha512-qctsuLZmIQ0+vSSMfoVvyFe2+GSEvnmZ2ezTup1SBse9+twCCeial6EEi3Nc2KFcf6+qz2FBPnjXsk8xhKSaPQ==} - - is-whitespace-character@1.0.4: - resolution: {integrity: sha512-SDweEzfIZM0SJV0EUga669UTKlmL0Pq8Lno0QDQsPnvECB3IM2aP0gdx5TrU0A01MAPfViaZiI2V1QMZLaKK5w==} - - is-word-character@1.0.4: - resolution: {integrity: sha512-5SMO8RVennx3nZrqtKwCGyyetPE9VDba5ugvKLaD4KopPG5kR4mQ7tNt/r7feL5yt5h3lpuBbIUmCOG2eSzXHA==} - - is-wsl@2.2.0: - resolution: {integrity: sha512-fKzAra0rGJUUBwGBgNkHZuToZcn+TtXHpeCgmkMJMMYx1sQDYaCSyjJBSCa2nH1DGm7s3n1oBnohoVTBaN7Lww==} - engines: {node: '>=8'} - - is-yarn-global@0.3.0: - resolution: {integrity: sha512-VjSeb/lHmkoyd8ryPVIKvOCn4D1koMqY+vqyjjUfc3xyKtP4dYOxM44sZrnqQSzSds3xyOrUTLTC9LVCVgLngw==} - - isarray@0.0.1: - resolution: {integrity: sha512-D2S+3GLxWH+uhrNEcoh/fnmYeP8E8/zHl644d/jdA0g2uyXvy3sb0qxotE+ne0LtccHknQzWwZEzhak7oJ0COQ==} - - isarray@1.0.0: - resolution: {integrity: sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==} - - isarray@2.0.5: - resolution: {integrity: sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==} - - isexe@2.0.0: - resolution: {integrity: sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==} - - isobject@3.0.1: - resolution: {integrity: sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg==} - engines: {node: '>=0.10.0'} - - jackspeak@2.3.6: - resolution: {integrity: sha512-N3yCS/NegsOBokc8GAdM8UcmfsKiSS8cipheD/nivzr700H+nsMOxJjQnvwOcRYVuFkdH0wGUvW2WbXGmrZGbQ==} - engines: {node: '>=14'} - - jest-util@29.7.0: - resolution: {integrity: sha512-z6EbKajIpqGKU56y5KBUgy1dt1ihhQJgWzUlZHArA/+X2ad7Cb5iF+AK1EWVL/Bo7Rz9uurpqw6SiBCefUbCGA==} - engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} - - jest-worker@27.5.1: - resolution: {integrity: sha512-7vuh85V5cdDofPyxn58nrPjBktZo0u9x1g8WtjQol+jZDaE+fhN+cIvTj11GndBnMnyfrUOG1sZQxCdjKh+DKg==} - engines: {node: '>= 10.13.0'} - - jest-worker@29.7.0: - resolution: {integrity: sha512-eIz2msL/EzL9UFTFFx7jBTkeZfku0yUAyZZZmJ93H2TYEiroIx2PQjEXcwYtYl8zXCxb+PAmA2hLIt/6ZEkPHw==} - engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} - - jiti@1.21.6: - resolution: {integrity: sha512-2yTgeWTWzMWkHu6Jp9NKgePDaYHbntiwvYuuJLbbN9vl7DC9DvXKOB2BC3ZZ92D3cvV/aflH0osDfwpHepQ53w==} - hasBin: true - - joi@17.13.3: - resolution: {integrity: sha512-otDA4ldcIx+ZXsKHWmp0YizCweVRZG96J10b0FevjfuncLO1oX59THoAmHkNubYJ+9gWsYsp5k8v4ib6oDv1fA==} - - js-tokens@4.0.0: - resolution: {integrity: sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==} - - js-yaml@3.14.1: - resolution: {integrity: sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==} - hasBin: true - - js-yaml@4.1.0: - resolution: {integrity: sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==} - hasBin: true - - jsesc@0.5.0: - resolution: {integrity: sha512-uZz5UnB7u4T9LvwmFqXii7pZSouaRPorGs5who1Ip7VO0wxanFvBL7GkM6dTHlgX+jhBApRetaWpnDabOeTcnA==} - hasBin: true - - jsesc@2.5.2: - resolution: {integrity: sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==} - engines: {node: '>=4'} - hasBin: true - - json-buffer@3.0.0: - resolution: {integrity: sha512-CuUqjv0FUZIdXkHPI8MezCnFCdaTAacej1TZYulLoAg1h/PhwkdXFN4V/gzY4g+fMBCOV2xF+rp7t2XD2ns/NQ==} - - json-parse-even-better-errors@2.3.1: - resolution: {integrity: sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==} - - json-schema-traverse@0.4.1: - resolution: {integrity: sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==} - - json-schema-traverse@1.0.0: - resolution: {integrity: sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==} - - json5@2.2.3: - resolution: {integrity: sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==} - engines: {node: '>=6'} - hasBin: true - - jsonc-parser@3.2.1: - resolution: {integrity: sha512-AilxAyFOAcK5wA1+LeaySVBrHsGQvUFCDWXKpZjzaL0PqW+xfBOttn8GNtWKFWqneyMZj41MWF9Kl6iPWLwgOA==} - - jsonfile@6.1.0: - resolution: {integrity: sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==} - - keyv@3.1.0: - resolution: {integrity: sha512-9ykJ/46SN/9KPM/sichzQ7OvXyGDYKGTaDlKMGCAlg2UK8KRy4jb0d8sFc+0Tt0YYnThq8X2RZgCg74RPxgcVA==} - - kind-of@6.0.3: - resolution: {integrity: sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==} - engines: {node: '>=0.10.0'} - - kleur@3.0.3: - resolution: {integrity: sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==} - engines: {node: '>=6'} - - latest-version@5.1.0: - resolution: {integrity: sha512-weT+r0kTkRQdCdYCNtkMwWXQTMEswKrFBkm4ckQOMVhhqhIMI1UT2hMj+1iigIhgSZm5gTmrRXBNoGUgaTY1xA==} - engines: {node: '>=8'} - - launch-editor@2.8.1: - resolution: {integrity: sha512-elBx2l/tp9z99X5H/qev8uyDywVh0VXAwEbjk8kJhnc5grOFkGh7aW6q55me9xnYbss261XtnUrysZ+XvGbhQA==} - - leven@3.1.0: - resolution: {integrity: sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A==} - engines: {node: '>=6'} - - lilconfig@2.1.0: - resolution: {integrity: sha512-utWOt/GHzuUxnLKxB6dk81RoOeoNeHgbrXiuGk4yyF5qlRz+iIVWu56E2fqGHFrXz0QNUhLB/8nKqvRH66JKGQ==} - engines: {node: '>=10'} - - lines-and-columns@1.2.4: - resolution: {integrity: sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==} - - linkify-it@4.0.1: - resolution: {integrity: sha512-C7bfi1UZmoj8+PQx22XyeXCuBlokoyWQL5pWSP+EI6nzRylyThouddufc2c1NDIcP9k5agmN9fLpA7VNJfIiqw==} - - loader-runner@4.3.0: - resolution: {integrity: sha512-3R/1M+yS3j5ou80Me59j7F9IMs4PXs3VqRrm0TU3AbKPxlmpoY1TNscJV/oGJXo8qCatFGTfDbY6W6ipGOYXfg==} - engines: {node: '>=6.11.5'} - - loader-utils@2.0.4: - resolution: {integrity: sha512-xXqpXoINfFhgua9xiqD8fPFHgkoq1mmmpE92WlDbm9rNRd/EbRb+Gqf908T2DMfuHjjJlksiK2RbHVOdD/MqSw==} - engines: {node: '>=8.9.0'} - - loader-utils@3.3.1: - resolution: {integrity: sha512-FMJTLMXfCLMLfJxcX9PFqX5qD88Z5MRGaZCVzfuqeZSPsyiBzs+pahDQjbIWz2QIzPZz0NX9Zy4FX3lmK6YHIg==} - engines: {node: '>= 12.13.0'} - - locate-path@3.0.0: - resolution: {integrity: sha512-7AO748wWnIhNqAuaty2ZWHkQHRSNfPVIsPIfwEOWO22AmaoVrWavlOcMR5nzTLNYvp36X220/maaRsrec1G65A==} - engines: {node: '>=6'} - - locate-path@5.0.0: - resolution: {integrity: sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==} - engines: {node: '>=8'} - - locate-path@6.0.0: - resolution: {integrity: sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==} - engines: {node: '>=10'} - - lodash.curry@4.1.1: - resolution: {integrity: sha512-/u14pXGviLaweY5JI0IUzgzF2J6Ne8INyzAZjImcryjgkZ+ebruBxy2/JaOOkTqScddcYtakjhSaeemV8lR0tA==} - - lodash.debounce@4.0.8: - resolution: {integrity: sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow==} - - lodash.flow@3.5.0: - resolution: {integrity: sha512-ff3BX/tSioo+XojX4MOsOMhJw0nZoUEF011LX8g8d3gvjVbxd89cCio4BCXronjxcTUIJUoqKEUA+n4CqvvRPw==} - - lodash.memoize@4.1.2: - resolution: {integrity: sha512-t7j+NzmgnQzTAYXcsHYLgimltOV1MXHtlOWf6GjL9Kj8GK5FInw5JotxvbOs+IvV1/Dzo04/fCGfLVs7aXb4Ag==} - - lodash.uniq@4.5.0: - resolution: {integrity: sha512-xfBaXQd9ryd9dlSDvnvI0lvxfLJlYAZzXomUYzLKtUeOQvOP5piqAWuGtrhWeqaXK9hhoM/iyJc5AV+XfsX3HQ==} - - lodash@4.17.21: - resolution: {integrity: sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==} - - loglevel@1.9.1: - resolution: {integrity: sha512-hP3I3kCrDIMuRwAwHltphhDM1r8i55H33GgqjXbrisuJhF4kRhW1dNuxsRklp4bXl8DSdLaNLuiL4A/LWRfxvg==} - engines: {node: '>= 0.6.0'} - - loose-envify@1.4.0: - resolution: {integrity: sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==} - hasBin: true - - lower-case@2.0.2: - resolution: {integrity: sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==} - - lowercase-keys@1.0.1: - resolution: {integrity: sha512-G2Lj61tXDnVFFOi8VZds+SoQjtQC3dgokKdDG2mTm1tx4m50NUHBOZSBwQQHyy0V12A0JTG4icfZQH+xPyh8VA==} - engines: {node: '>=0.10.0'} - - lowercase-keys@2.0.0: - resolution: {integrity: sha512-tqNXrS78oMOE73NMxK4EMLQsQowWf8jKooH9g7xPavRT706R6bkQJ6DY2Te7QukaZsulxa30wQ7bk0pm4XiHmA==} - engines: {node: '>=8'} - - lru-cache@10.4.3: - resolution: {integrity: sha512-JNAzZcXrCt42VGLuYz0zfAzDfAvJWW6AfYlDBQyDV5DClI2m5sAmK+OIO7s59XfsRsWHp02jAJrRadPRGTt6SQ==} - - lru-cache@5.1.1: - resolution: {integrity: sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==} - - make-dir@3.1.0: - resolution: {integrity: sha512-g3FeP20LNwhALb/6Cz6Dd4F2ngze0jz7tbzrD2wAV+o9FeNHe4rL+yK2md0J/fiSf1sa1ADhXqi5+oVwOM/eGw==} - engines: {node: '>=8'} - - markdown-escapes@1.0.4: - resolution: {integrity: sha512-8z4efJYk43E0upd0NbVXwgSTQs6cT3T06etieCMEg7dRbzCbxUCK/GHlX8mhHRDcp+OLlHkPKsvqQTCvsRl2cg==} - - markdown-it@13.0.1: - resolution: {integrity: sha512-lTlxriVoy2criHP0JKRhO2VDG9c2ypWCsT237eDiLqi09rmbKoUetyGHq2uOIRoRS//kfoJckS0eUzzkDR+k2Q==} - hasBin: true - - markdownlint-cli@0.35.0: - resolution: {integrity: sha512-lVIIIV1MrUtjoocgDqXLxUCxlRbn7Ve8rsWppfwciUNwLlNS28AhNiyQ3PU7jjj4Qvj+rWTTvwkqg7AcdG988g==} - engines: {node: '>=16'} - hasBin: true - - markdownlint-micromark@0.1.5: - resolution: {integrity: sha512-HvofNU4QCvfUCWnocQP1IAWaqop5wpWrB0mKB6SSh0fcpV0PdmQNS6tdUuFew1utpYlUvYYzz84oDkrD76GB9A==} - engines: {node: '>=16'} - - markdownlint@0.29.0: - resolution: {integrity: sha512-ASAzqpODstu/Qsk0xW5BPgWnK/qjpBQ4e7IpsSvvFXcfYIjanLTdwFRJK1SIEEh0fGSMKXcJf/qhaZYHyME0wA==} - engines: {node: '>=16'} - - mdast-squeeze-paragraphs@4.0.0: - resolution: {integrity: sha512-zxdPn69hkQ1rm4J+2Cs2j6wDEv7O17TfXTJ33tl/+JPIoEmtV9t2ZzBM5LPHE8QlHsmVD8t3vPKCyY3oH+H8MQ==} - - mdast-util-definitions@4.0.0: - resolution: {integrity: sha512-k8AJ6aNnUkB7IE+5azR9h81O5EQ/cTDXtWdMq9Kk5KcEW/8ritU5CeLg/9HhOC++nALHBlaogJ5jz0Ybk3kPMQ==} - - mdast-util-to-hast@10.0.1: - resolution: {integrity: sha512-BW3LM9SEMnjf4HXXVApZMt8gLQWVNXc3jryK0nJu/rOXPOnlkUjmdkDlmxMirpbU9ILncGFIwLH/ubnWBbcdgA==} - - mdast-util-to-string@2.0.0: - resolution: {integrity: sha512-AW4DRS3QbBayY/jJmD8437V1Gombjf8RSOUCMFBuo5iHi58AGEgVCKQ+ezHkZZDpAQS75hcBMpLqjpJTjtUL7w==} - - mdn-data@2.0.14: - resolution: {integrity: sha512-dn6wd0uw5GsdswPFfsgMp5NSB0/aDe6fK94YJV/AJDYXL6HVLWBsxeq7js7Ad+mU2K9LAlwpk6kN2D5mwCPVow==} - - mdn-data@2.0.4: - resolution: {integrity: sha512-iV3XNKw06j5Q7mi6h+9vbx23Tv7JkjEVgKHW4pimwyDGWm0OIQntJJ+u1C6mg6mK1EaTv42XQ7w76yuzH7M2cA==} - - mdurl@1.0.1: - resolution: {integrity: sha512-/sKlQJCBYVY9Ers9hqzKou4H6V5UWc/M59TH2dvkt+84itfnq7uFOMLpOiOS4ujvHP4etln18fmIxA5R5fll0g==} - - media-typer@0.3.0: - resolution: {integrity: sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ==} - engines: {node: '>= 0.6'} - - memfs@3.5.3: - resolution: {integrity: sha512-UERzLsxzllchadvbPs5aolHh65ISpKpM+ccLbOJ8/vvpBKmAWf+la7dXFy7Mr0ySHbdHrFv5kGFCUHHe6GFEmw==} - engines: {node: '>= 4.0.0'} - - merge-descriptors@1.0.1: - resolution: {integrity: sha512-cCi6g3/Zr1iqQi6ySbseM1Xvooa98N0w31jzUYrXPX2xqObmFGHJ0tQ5u74H3mVh7wLouTseZyYIq39g8cNp1w==} - - merge-stream@2.0.0: - resolution: {integrity: sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==} - - merge2@1.4.1: - resolution: {integrity: sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==} - engines: {node: '>= 8'} - - methods@1.1.2: - resolution: {integrity: sha512-iclAHeNqNm68zFtnZ0e+1L2yUIdvzNoauKU4WBA3VvH/vPFieF7qfRlwUZU+DA9P9bPXIS90ulxoUoCH23sV2w==} - engines: {node: '>= 0.6'} - - micromatch@4.0.8: - resolution: {integrity: sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==} - engines: {node: '>=8.6'} - - mime-db@1.33.0: - resolution: {integrity: sha512-BHJ/EKruNIqJf/QahvxwQZXKygOQ256myeN/Ew+THcAa5q+PjyTTMMeNQC4DZw5AwfvelsUrA6B67NKMqXDbzQ==} - engines: {node: '>= 0.6'} - - mime-db@1.52.0: - resolution: {integrity: sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==} - engines: {node: '>= 0.6'} - - mime-db@1.53.0: - resolution: {integrity: sha512-oHlN/w+3MQ3rba9rqFr6V/ypF10LSkdwUysQL7GkXoTgIWeV+tcXGA852TBxH+gsh8UWoyhR1hKcoMJTuWflpg==} - engines: {node: '>= 0.6'} - - mime-types@2.1.18: - resolution: {integrity: sha512-lc/aahn+t4/SWV/qcmumYjymLsWfN3ELhpmVuUFjgsORruuZPVSwAQryq+HHGvO/SI2KVX26bx+En+zhM8g8hQ==} - engines: {node: '>= 0.6'} - - mime-types@2.1.35: - resolution: {integrity: sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==} - engines: {node: '>= 0.6'} - - mime@1.6.0: - resolution: {integrity: sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==} - engines: {node: '>=4'} - hasBin: true - - mimic-fn@2.1.0: - resolution: {integrity: sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==} - engines: {node: '>=6'} - - mimic-response@1.0.1: - resolution: {integrity: sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ==} - engines: {node: '>=4'} - - mini-css-extract-plugin@2.9.1: - resolution: {integrity: sha512-+Vyi+GCCOHnrJ2VPS+6aPoXN2k2jgUzDRhTFLjjTBn23qyXJXkjUWQgTL+mXpF5/A8ixLdCc6kWsoeOjKGejKQ==} - engines: {node: '>= 12.13.0'} - peerDependencies: - webpack: ^5.0.0 - - minimalistic-assert@1.0.1: - resolution: {integrity: sha512-UtJcAD4yEaGtjPezWuO9wC4nwUnVH/8/Im3yEHQP4b67cXlD/Qr9hdITCU1xDbSEXg2XKNaP8jsReV7vQd00/A==} - - minimatch@3.1.2: - resolution: {integrity: sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==} - - minimatch@9.0.5: - resolution: {integrity: sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==} - engines: {node: '>=16 || 14 >=14.17'} - - minimist@1.2.8: - resolution: {integrity: sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==} - - minipass@2.9.0: - resolution: {integrity: sha512-wxfUjg9WebH+CUDX/CdbRlh5SmfZiy/hpkxaRI16Y9W56Pa75sWgd/rvFilSgrauD9NyFymP/+JFV3KwzIsJeg==} - - minipass@6.0.2: - resolution: {integrity: sha512-MzWSV5nYVT7mVyWCwn2o7JH13w2TBRmmSqSRCKzTw+lmft9X4z+3wjvs06Tzijo5z4W/kahUCDpRXTF+ZrmF/w==} - engines: {node: '>=16 || 14 >=14.17'} - - minizlib@1.3.3: - resolution: {integrity: sha512-6ZYMOEnmVsdCeTJVE0W9ZD+pVnE8h9Hma/iOwwRDsdQoePpoX56/8B6z3P9VNwppJuBKNRuFDRNRqRWexT9G9Q==} - - mkdirp@0.5.6: - resolution: {integrity: sha512-FP+p8RB8OWpF3YZBCrP5gtADmtXApB5AMLn+vdyA+PyxCjrCs00mjyUozssO33cwDeT3wNGdLxJ5M//YqtHAJw==} - hasBin: true - - mrmime@2.0.0: - resolution: {integrity: sha512-eu38+hdgojoyq63s+yTpN4XMBdt5l8HhMhc4VKLO9KM5caLIBvUm4thi7fFaxyTmCKeNnXZ5pAlBwCUnhA09uw==} - engines: {node: '>=10'} - - ms@2.0.0: - resolution: {integrity: sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==} - - ms@2.1.2: - resolution: {integrity: sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==} - - ms@2.1.3: - resolution: {integrity: sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==} - - multicast-dns@7.2.5: - resolution: {integrity: sha512-2eznPJP8z2BFLX50tf0LuODrpINqP1RVIm/CObbTcBRITQgmC/TjcREF1NeTBzIcR5XO/ukWo+YHOjBbFwIupg==} - hasBin: true - - nanoid@3.3.7: - resolution: {integrity: sha512-eSRppjcPIatRIMC1U6UngP8XFcz8MQWGQdt1MTBQ7NaAmvXDfvNxbvWV3x2y6CdEUciCSsDHDQZbhYaB8QEo2g==} - engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1} - hasBin: true - - negotiator@0.6.3: - resolution: {integrity: sha512-+EUsqGPLsM+j/zdChZjsnX51g4XrHFOIXwfnCVPGlQk/k5giakcKsuxCObBRu6DSm9opw/O6slWbJdghQM4bBg==} - engines: {node: '>= 0.6'} - - neo-async@2.6.2: - resolution: {integrity: sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw==} - - no-case@3.0.4: - resolution: {integrity: sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==} - - node-emoji@1.11.0: - resolution: {integrity: sha512-wo2DpQkQp7Sjm2A0cq+sN7EHKO6Sl0ctXeBdFZrL9T9+UywORbufTcTZxom8YqpLQt/FqNMUkOpkZrJVYSKD3A==} - - node-fetch@2.6.7: - resolution: {integrity: sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==} - engines: {node: 4.x || >=6.0.0} - peerDependencies: - encoding: ^0.1.0 - peerDependenciesMeta: - encoding: - optional: true - - node-fetch@2.7.0: - resolution: {integrity: sha512-c4FRfUm/dbcWZ7U+1Wq0AwCyFL+3nt2bEw05wfxSz+DWpWsitgmSgYmy2dQdWyKC1694ELPqMs/YzUSNozLt8A==} - engines: {node: 4.x || >=6.0.0} - peerDependencies: - encoding: ^0.1.0 - peerDependenciesMeta: - encoding: - optional: true - - node-forge@1.3.1: - resolution: {integrity: sha512-dPEtOeMvF9VMcYV/1Wb8CPoVAXtp6MKMlcbAt4ddqmGqUJ6fQZFXkNZNkNlfevtNkGtaSoXf/vNNNSvgrdXwtA==} - engines: {node: '>= 6.13.0'} - - node-releases@2.0.18: - resolution: {integrity: sha512-d9VeXT4SJ7ZeOqGX6R5EM022wpL+eWPooLI+5UpWn2jCT1aosUQEhQP214x33Wkwx3JQMvIm+tIoVOdodFS40g==} - - normalize-path@3.0.0: - resolution: {integrity: sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==} - engines: {node: '>=0.10.0'} - - normalize-range@0.1.2: - resolution: {integrity: sha512-bdok/XvKII3nUpklnV6P2hxtMNrCboOjAcyBuQnWEhO665FwrSNRxU+AqpsyvO6LgGYPspN+lu5CLtw4jPRKNA==} - engines: {node: '>=0.10.0'} - - normalize-url@4.5.1: - resolution: {integrity: sha512-9UZCFRHQdNrfTpGg8+1INIg93B6zE0aXMVFkw1WFwvO4SlZywU6aLg5Of0Ap/PgcbSw4LNxvMWXMeugwMCX0AA==} - engines: {node: '>=8'} - - normalize-url@6.1.0: - resolution: {integrity: sha512-DlL+XwOy3NxAQ8xuC0okPgK46iuVNAK01YN7RueYBqqFeGsBjV9XmCAzAdgt+667bCl5kPh9EqKKDwnaPG1I7A==} - engines: {node: '>=10'} - - npm-run-path@4.0.1: - resolution: {integrity: sha512-S48WzZW777zhNIrn7gxOlISNAqi9ZC/uQFnRdbeIHhZhCA6UqpkOT8T1G7BvfdgP4Er8gF4sUbaS0i7QvIfCWw==} - engines: {node: '>=8'} - - nprogress@0.2.0: - resolution: {integrity: sha512-I19aIingLgR1fmhftnbWWO3dXc0hSxqHQHQb3H8m+K3TnEn/iSeTZZOyvKXWqQESMwuUVnatlCnZdLBZZt2VSA==} - - nth-check@1.0.2: - resolution: {integrity: sha512-WeBOdju8SnzPN5vTUJYxYUxLeXpCaVP5i5e0LF8fg7WORF2Wd7wFX/pk0tYZk7s8T+J7VLy0Da6J1+wCT0AtHg==} - - nth-check@2.1.1: - resolution: {integrity: sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==} - - object-assign@4.1.1: - resolution: {integrity: sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==} - engines: {node: '>=0.10.0'} - - object-inspect@1.13.2: - resolution: {integrity: sha512-IRZSRuzJiynemAXPYtPe5BoI/RESNYR7TYm50MC5Mqbd3Jmw5y790sErYw3V6SryFJD64b74qQQs9wn5Bg/k3g==} - engines: {node: '>= 0.4'} - - object-keys@1.1.1: - resolution: {integrity: sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==} - engines: {node: '>= 0.4'} - - object.assign@4.1.5: - resolution: {integrity: sha512-byy+U7gp+FVwmyzKPYhW2h5l3crpmGsxl7X2s8y43IgxvG4g3QZ6CffDtsNQy1WsmZpQbO+ybo0AlW7TY6DcBQ==} - engines: {node: '>= 0.4'} - - object.getownpropertydescriptors@2.1.8: - resolution: {integrity: sha512-qkHIGe4q0lSYMv0XI4SsBTJz3WaURhLvd0lKSgtVuOsJ2krg4SgMw3PIRQFMp07yi++UR3se2mkcLqsBNpBb/A==} - engines: {node: '>= 0.8'} - - object.values@1.2.0: - resolution: {integrity: sha512-yBYjY9QX2hnRmZHAjG/f13MzmBzxzYgQhFrke06TTyKY5zSTEqkOeukBzIdVA3j3ulu8Qa3MbVFShV7T2RmGtQ==} - engines: {node: '>= 0.4'} - - obuf@1.1.2: - resolution: {integrity: sha512-PX1wu0AmAdPqOL1mWhqmlOd8kOIZQwGZw6rh7uby9fTc5lhaOWFLX3I6R1hrF9k3zUY40e6igsLGkDXK92LJNg==} - - on-finished@2.4.1: - resolution: {integrity: sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg==} - engines: {node: '>= 0.8'} - - on-headers@1.0.2: - resolution: {integrity: sha512-pZAE+FJLoyITytdqK0U5s+FIpjN0JP3OzFi/u8Rx+EV5/W+JTWGXG8xFzevE7AjBfDqHv/8vL8qQsIhHnqRkrA==} - engines: {node: '>= 0.8'} - - once@1.4.0: - resolution: {integrity: sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==} - - onetime@5.1.2: - resolution: {integrity: sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==} - engines: {node: '>=6'} - - open@8.4.2: - resolution: {integrity: sha512-7x81NCL719oNbsq/3mh+hVrAWmFuEYUqrq/Iw3kUzH8ReypT9QQ0BLoJS7/G9k6N81XjW4qHWtjWwe/9eLy1EQ==} - engines: {node: '>=12'} - - opener@1.5.2: - resolution: {integrity: sha512-ur5UIdyw5Y7yEj9wLzhqXiy6GZ3Mwx0yGI+5sMn2r0N0v3cKJvUmFH5yPP+WXh9e0xfyzyJX95D8l088DNFj7A==} - hasBin: true - - p-cancelable@1.1.0: - resolution: {integrity: sha512-s73XxOZ4zpt1edZYZzvhqFa6uvQc1vwUa0K0BdtIZgQMAJj9IbebH+JkgKZc9h+B05PKHLOTl4ajG1BmNrVZlw==} - engines: {node: '>=6'} - - p-limit@2.3.0: - resolution: {integrity: sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==} - engines: {node: '>=6'} - - p-limit@3.1.0: - resolution: {integrity: sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==} - engines: {node: '>=10'} - - p-locate@3.0.0: - resolution: {integrity: sha512-x+12w/To+4GFfgJhBEpiDcLozRJGegY+Ei7/z0tSLkMmxGZNybVMSfWj9aJn8Z5Fc7dBUNJOOVgPv2H7IwulSQ==} - engines: {node: '>=6'} - - p-locate@4.1.0: - resolution: {integrity: sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==} - engines: {node: '>=8'} - - p-locate@5.0.0: - resolution: {integrity: sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==} - engines: {node: '>=10'} - - p-map@4.0.0: - resolution: {integrity: sha512-/bjOqmgETBYB5BoEeGVea8dmvHb2m9GLy1E9W43yeyfP6QQCZGFNa+XRceJEuDB6zqr+gKpIAmlLebMpykw/MQ==} - engines: {node: '>=10'} - - p-retry@4.6.2: - resolution: {integrity: sha512-312Id396EbJdvRONlngUx0NydfrIQ5lsYu0znKVUzVvArzEIt08V1qhtyESbGVd1FGX7UKtiFp5uwKZdM8wIuQ==} - engines: {node: '>=8'} - - p-try@2.2.0: - resolution: {integrity: sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==} - engines: {node: '>=6'} - - package-json@6.5.0: - resolution: {integrity: sha512-k3bdm2n25tkyxcjSKzB5x8kfVxlMdgsbPr0GkZcwHsLpba6cBjqCt1KlcChKEvxHIcTB1FVMuwoijZ26xex5MQ==} - engines: {node: '>=8'} - - param-case@3.0.4: - resolution: {integrity: sha512-RXlj7zCYokReqWpOPH9oYivUzLYZ5vAPIfEmCTNViosC78F8F0H9y7T7gG2M39ymgutxF5gcFEsyZQSph9Bp3A==} - - parent-module@1.0.1: - resolution: {integrity: sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==} - engines: {node: '>=6'} - - parse-entities@2.0.0: - resolution: {integrity: sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ==} - - parse-json@5.2.0: - resolution: {integrity: sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==} - engines: {node: '>=8'} - - parse-numeric-range@1.3.0: - resolution: {integrity: sha512-twN+njEipszzlMJd4ONUYgSfZPDxgHhT9Ahed5uTigpQn90FggW4SA/AIPq/6a149fTbE9qBEcSwE3FAEp6wQQ==} - - parse5-htmlparser2-tree-adapter@7.0.0: - resolution: {integrity: sha512-B77tOZrqqfUfnVcOrUvfdLbz4pu4RopLD/4vmu3HUPswwTA8OH0EMW9BlWR2B0RCoiZRAHEUu7IxeP1Pd1UU+g==} - - parse5-parser-stream@7.1.2: - resolution: {integrity: sha512-JyeQc9iwFLn5TbvvqACIF/VXG6abODeB3Fwmv/TGdLk2LfbWkaySGY72at4+Ty7EkPZj854u4CrICqNk2qIbow==} - - parse5@6.0.1: - resolution: {integrity: sha512-Ofn/CTFzRGTTxwpNEs9PP93gXShHcTq255nzRYSKe8AkVpZY7e1fpmTfOyoIvjP5HG7Z2ZM7VS9PPhQGW2pOpw==} - - parse5@7.1.2: - resolution: {integrity: sha512-Czj1WaSVpaoj0wbhMzLmWD69anp2WH7FXMB9n1Sy8/ZFF9jolSQVMu1Ij5WIyGmcBmhk7EOndpO4mIpihVqAXw==} - - parseurl@1.3.3: - resolution: {integrity: sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==} - engines: {node: '>= 0.8'} - - pascal-case@3.1.2: - resolution: {integrity: sha512-uWlGT3YSnK9x3BQJaOdcZwrnV6hPpd8jFH1/ucpiLRPh/2zCVJKS19E4GvYHvaCcACn3foXZ0cLB9Wrx1KGe5g==} - - path-exists@3.0.0: - resolution: {integrity: sha512-bpC7GYwiDYQ4wYLe+FA8lhRjhQCMcQGuSgGGqDkg/QerRWw9CmGRT0iSOVRSZJ29NMLZgIzqaljJ63oaL4NIJQ==} - engines: {node: '>=4'} - - path-exists@4.0.0: - resolution: {integrity: sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==} - engines: {node: '>=8'} - - path-is-absolute@1.0.1: - resolution: {integrity: sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==} - engines: {node: '>=0.10.0'} - - path-is-inside@1.0.2: - resolution: {integrity: sha512-DUWJr3+ULp4zXmol/SZkFf3JGsS9/SIv+Y3Rt93/UjPpDpklB5f1er4O3POIbUuUJ3FXgqte2Q7SrU6zAqwk8w==} - - path-key@3.1.1: - resolution: {integrity: sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==} - engines: {node: '>=8'} - - path-parse@1.0.7: - resolution: {integrity: sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==} - - path-scurry@1.11.1: - resolution: {integrity: sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==} - engines: {node: '>=16 || 14 >=14.18'} - - path-to-regexp@0.1.7: - resolution: {integrity: sha512-5DFkuoqlv1uYQKxy8omFBeJPQcdoE07Kv2sferDCrAq1ohOU+MSDswDIbnx3YAM60qIOnYa53wBhXW0EbMonrQ==} - - path-to-regexp@1.8.0: - resolution: {integrity: sha512-n43JRhlUKUAlibEJhPeir1ncUID16QnEjNpwzNdO3Lm4ywrBpBZ5oLD0I6br9evr1Y9JTqwRtAh7JLoOzAQdVA==} - - path-to-regexp@2.2.1: - resolution: {integrity: sha512-gu9bD6Ta5bwGrrU8muHzVOBFFREpp2iRkVfhBJahwJ6p6Xw20SjT0MxLnwkjOibQmGSYhiUnf2FLe7k+jcFmGQ==} - - path-type@4.0.0: - resolution: {integrity: sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==} - engines: {node: '>=8'} - - pend@1.2.0: - resolution: {integrity: sha512-F3asv42UuXchdzt+xXqfW1OGlVBe+mxa2mqI0pg5yAHZPvFmY3Y6drSf/GQ1A86WgWEN9Kzh/WrgKa6iGcHXLg==} - - picocolors@1.0.1: - resolution: {integrity: sha512-anP1Z8qwhkbmu7MFP5iTt+wQKXgwzf7zTyGlcdzabySa9vd0Xt392U0rVmz9poOaBj0uHJKyyo9/upk0HrEQew==} - - picomatch@2.3.1: - resolution: {integrity: sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==} - engines: {node: '>=8.6'} - - pkg-dir@4.2.0: - resolution: {integrity: sha512-HRDzbaKjC+AOWVXxAU/x54COGeIv9eb+6CkDSQoNTt4XyWoIJvuPsXizxu/Fr23EiekbtZwmh1IcIG/l/a10GQ==} - engines: {node: '>=8'} - - pkg-up@3.1.0: - resolution: {integrity: sha512-nDywThFk1i4BQK4twPQ6TA4RT8bDY96yeuCVBWL3ePARCiEKDRSrNGbFIgUJpLp+XeIR65v8ra7WuJOFUBtkMA==} - engines: {node: '>=8'} - - possible-typed-array-names@1.0.0: - resolution: {integrity: sha512-d7Uw+eZoloe0EHDIYoe+bQ5WXnGMOpmiZFTuMWCwpjzzkL2nTjcKiAk4hh8TjnGye2TwWOk3UXucZ+3rbmBa8Q==} - engines: {node: '>= 0.4'} - - postcss-calc@8.2.4: - resolution: {integrity: sha512-SmWMSJmB8MRnnULldx0lQIyhSNvuDl9HfrZkaqqE/WHAhToYsAvDq+yAsA/kIyINDszOp3Rh0GFoNuH5Ypsm3Q==} - peerDependencies: - postcss: ^8.2.2 - - postcss-colormin@5.3.1: - resolution: {integrity: sha512-UsWQG0AqTFQmpBegeLLc1+c3jIqBNB0zlDGRWR+dQ3pRKJL1oeMzyqmH3o2PIfn9MBdNrVPWhDbT769LxCTLJQ==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-convert-values@5.1.3: - resolution: {integrity: sha512-82pC1xkJZtcJEfiLw6UXnXVXScgtBrjlO5CBmuDQc+dlb88ZYheFsjTn40+zBVi3DkfF7iezO0nJUPLcJK3pvA==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-discard-comments@5.1.2: - resolution: {integrity: sha512-+L8208OVbHVF2UQf1iDmRcbdjJkuBF6IS29yBDSiWUIzpYaAhtNl6JYnYm12FnkeCwQqF5LeklOu6rAqgfBZqQ==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-discard-duplicates@5.1.0: - resolution: {integrity: sha512-zmX3IoSI2aoenxHV6C7plngHWWhUOV3sP1T8y2ifzxzbtnuhk1EdPwm0S1bIUNaJ2eNbWeGLEwzw8huPD67aQw==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-discard-empty@5.1.1: - resolution: {integrity: sha512-zPz4WljiSuLWsI0ir4Mcnr4qQQ5e1Ukc3i7UfE2XcrwKK2LIPIqE5jxMRxO6GbI3cv//ztXDsXwEWT3BHOGh3A==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-discard-overridden@5.1.0: - resolution: {integrity: sha512-21nOL7RqWR1kasIVdKs8HNqQJhFxLsyRfAnUDm4Fe4t4mCWL9OJiHvlHPjcd8zc5Myu89b/7wZDnOSjFgeWRtw==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-discard-unused@5.1.0: - resolution: {integrity: sha512-KwLWymI9hbwXmJa0dkrzpRbSJEh0vVUd7r8t0yOGPcfKzyJJxFM8kLyC5Ev9avji6nY95pOp1W6HqIrfT+0VGw==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-loader@7.3.4: - resolution: {integrity: sha512-iW5WTTBSC5BfsBJ9daFMPVrLT36MrNiC6fqOZTTaHjBNX6Pfd5p+hSBqe/fEeNd7pc13QiAyGt7VdGMw4eRC4A==} - engines: {node: '>= 14.15.0'} - peerDependencies: - postcss: ^7.0.0 || ^8.0.1 - webpack: ^5.0.0 - - postcss-merge-idents@5.1.1: - resolution: {integrity: sha512-pCijL1TREiCoog5nQp7wUe+TUonA2tC2sQ54UGeMmryK3UFGIYKqDyjnqd6RcuI4znFn9hWSLNN8xKE/vWcUQw==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-merge-longhand@5.1.7: - resolution: {integrity: sha512-YCI9gZB+PLNskrK0BB3/2OzPnGhPkBEwmwhfYk1ilBHYVAZB7/tkTHFBAnCrvBBOmeYyMYw3DMjT55SyxMBzjQ==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-merge-rules@5.1.4: - resolution: {integrity: sha512-0R2IuYpgU93y9lhVbO/OylTtKMVcHb67zjWIfCiKR9rWL3GUk1677LAqD/BcHizukdZEjT8Ru3oHRoAYoJy44g==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-minify-font-values@5.1.0: - resolution: {integrity: sha512-el3mYTgx13ZAPPirSVsHqFzl+BBBDrXvbySvPGFnQcTI4iNslrPaFq4muTkLZmKlGk4gyFAYUBMH30+HurREyA==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-minify-gradients@5.1.1: - resolution: {integrity: sha512-VGvXMTpCEo4qHTNSa9A0a3D+dxGFZCYwR6Jokk+/3oB6flu2/PnPXAh2x7x52EkY5xlIHLm+Le8tJxe/7TNhzw==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-minify-params@5.1.4: - resolution: {integrity: sha512-+mePA3MgdmVmv6g+30rn57USjOGSAyuxUmkfiWpzalZ8aiBkdPYjXWtHuwJGm1v5Ojy0Z0LaSYhHaLJQB0P8Jw==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-minify-selectors@5.2.1: - resolution: {integrity: sha512-nPJu7OjZJTsVUmPdm2TcaiohIwxP+v8ha9NehQ2ye9szv4orirRU3SDdtUmKH+10nzn0bAyOXZ0UEr7OpvLehg==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-modules-extract-imports@3.1.0: - resolution: {integrity: sha512-k3kNe0aNFQDAZGbin48pL2VNidTF0w4/eASDsxlyspobzU3wZQLOGj7L9gfRe0Jo9/4uud09DsjFNH7winGv8Q==} - engines: {node: ^10 || ^12 || >= 14} - peerDependencies: - postcss: ^8.1.0 - - postcss-modules-local-by-default@4.0.5: - resolution: {integrity: sha512-6MieY7sIfTK0hYfafw1OMEG+2bg8Q1ocHCpoWLqOKj3JXlKu4G7btkmM/B7lFubYkYWmRSPLZi5chid63ZaZYw==} - engines: {node: ^10 || ^12 || >= 14} - peerDependencies: - postcss: ^8.1.0 - - postcss-modules-scope@3.2.0: - resolution: {integrity: sha512-oq+g1ssrsZOsx9M96c5w8laRmvEu9C3adDSjI8oTcbfkrTE8hx/zfyobUoWIxaKPO8bt6S62kxpw5GqypEw1QQ==} - engines: {node: ^10 || ^12 || >= 14} - peerDependencies: - postcss: ^8.1.0 - - postcss-modules-values@4.0.0: - resolution: {integrity: sha512-RDxHkAiEGI78gS2ofyvCsu7iycRv7oqw5xMWn9iMoR0N/7mf9D50ecQqUo5BZ9Zh2vH4bCUR/ktCqbB9m8vJjQ==} - engines: {node: ^10 || ^12 || >= 14} - peerDependencies: - postcss: ^8.1.0 - - postcss-normalize-charset@5.1.0: - resolution: {integrity: sha512-mSgUJ+pd/ldRGVx26p2wz9dNZ7ji6Pn8VWBajMXFf8jk7vUoSrZ2lt/wZR7DtlZYKesmZI680qjr2CeFF2fbUg==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-normalize-display-values@5.1.0: - resolution: {integrity: sha512-WP4KIM4o2dazQXWmFaqMmcvsKmhdINFblgSeRgn8BJ6vxaMyaJkwAzpPpuvSIoG/rmX3M+IrRZEz2H0glrQNEA==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-normalize-positions@5.1.1: - resolution: {integrity: sha512-6UpCb0G4eofTCQLFVuI3EVNZzBNPiIKcA1AKVka+31fTVySphr3VUgAIULBhxZkKgwLImhzMR2Bw1ORK+37INg==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-normalize-repeat-style@5.1.1: - resolution: {integrity: sha512-mFpLspGWkQtBcWIRFLmewo8aC3ImN2i/J3v8YCFUwDnPu3Xz4rLohDO26lGjwNsQxB3YF0KKRwspGzE2JEuS0g==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-normalize-string@5.1.0: - resolution: {integrity: sha512-oYiIJOf4T9T1N4i+abeIc7Vgm/xPCGih4bZz5Nm0/ARVJ7K6xrDlLwvwqOydvyL3RHNf8qZk6vo3aatiw/go3w==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-normalize-timing-functions@5.1.0: - resolution: {integrity: sha512-DOEkzJ4SAXv5xkHl0Wa9cZLF3WCBhF3o1SKVxKQAa+0pYKlueTpCgvkFAHfk+Y64ezX9+nITGrDZeVGgITJXjg==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-normalize-unicode@5.1.1: - resolution: {integrity: sha512-qnCL5jzkNUmKVhZoENp1mJiGNPcsJCs1aaRmURmeJGES23Z/ajaln+EPTD+rBeNkSryI+2WTdW+lwcVdOikrpA==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-normalize-url@5.1.0: - resolution: {integrity: sha512-5upGeDO+PVthOxSmds43ZeMeZfKH+/DKgGRD7TElkkyS46JXAUhMzIKiCa7BabPeIy3AQcTkXwVVN7DbqsiCew==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-normalize-whitespace@5.1.1: - resolution: {integrity: sha512-83ZJ4t3NUDETIHTa3uEg6asWjSBYL5EdkVB0sDncx9ERzOKBVJIUeDO9RyA9Zwtig8El1d79HBp0JEi8wvGQnA==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-ordered-values@5.1.3: - resolution: {integrity: sha512-9UO79VUhPwEkzbb3RNpqqghc6lcYej1aveQteWY+4POIwlqkYE21HKWaLDF6lWNuqCobEAyTovVhtI32Rbv2RQ==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-reduce-idents@5.2.0: - resolution: {integrity: sha512-BTrLjICoSB6gxbc58D5mdBK8OhXRDqud/zodYfdSi52qvDHdMwk+9kB9xsM8yJThH/sZU5A6QVSmMmaN001gIg==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-reduce-initial@5.1.2: - resolution: {integrity: sha512-dE/y2XRaqAi6OvjzD22pjTUQ8eOfc6m/natGHgKFBK9DxFmIm69YmaRVQrGgFlEfc1HePIurY0TmDeROK05rIg==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-reduce-transforms@5.1.0: - resolution: {integrity: sha512-2fbdbmgir5AvpW9RLtdONx1QoYG2/EtqpNQbFASDlixBbAYuTcJ0dECwlqNqH7VbaUnEnh8SrxOe2sRIn24XyQ==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-selector-parser@6.1.2: - resolution: {integrity: sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==} - engines: {node: '>=4'} - - postcss-sort-media-queries@4.4.1: - resolution: {integrity: sha512-QDESFzDDGKgpiIh4GYXsSy6sek2yAwQx1JASl5AxBtU1Lq2JfKBljIPNdil989NcSKRQX1ToiaKphImtBuhXWw==} - engines: {node: '>=10.0.0'} - peerDependencies: - postcss: ^8.4.16 - - postcss-svgo@5.1.0: - resolution: {integrity: sha512-D75KsH1zm5ZrHyxPakAxJWtkyXew5qwS70v56exwvw542d9CRtTo78K0WeFxZB4G7JXKKMbEZtZayTGdIky/eA==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-unique-selectors@5.1.1: - resolution: {integrity: sha512-5JiODlELrz8L2HwxfPnhOWZYWDxVHWL83ufOv84NrcgipI7TaeRsatAhK4Tr2/ZiYldpK/wBvw5BD3qfaK96GA==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss-value-parser@4.2.0: - resolution: {integrity: sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==} - - postcss-zindex@5.1.0: - resolution: {integrity: sha512-fgFMf0OtVSBR1va1JNHYgMxYk73yhn/qb4uQDq1DLGYolz8gHCyr/sesEuGUaYs58E3ZJRcpoGuPVoB7Meiq9A==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - postcss@8.4.41: - resolution: {integrity: sha512-TesUflQ0WKZqAvg52PWL6kHgLKP6xB6heTOdoYM0Wt2UHyxNa4K25EZZMgKns3BH1RLVbZCREPpLY0rhnNoHVQ==} - engines: {node: ^10 || ^12 || >=14} - - prepend-http@2.0.0: - resolution: {integrity: sha512-ravE6m9Atw9Z/jjttRUZ+clIXogdghyZAuWJ3qEzjT+jI/dL1ifAqhZeC5VHzQp1MSt1+jxKkFNemj/iO7tVUA==} - engines: {node: '>=4'} - - pretty-error@4.0.0: - resolution: {integrity: sha512-AoJ5YMAcXKYxKhuJGdcvse+Voc6v1RgnsR3nWcYU7q4t6z0Q6T86sv5Zq8VIRbOWWFpvdGE83LtdSMNd+6Y0xw==} - - pretty-time@1.1.0: - resolution: {integrity: sha512-28iF6xPQrP8Oa6uxE6a1biz+lWeTOAPKggvjB8HAs6nVMKZwf5bG++632Dx614hIWgUPkgivRfG+a8uAXGTIbA==} - engines: {node: '>=4'} - - prism-react-renderer@1.3.5: - resolution: {integrity: sha512-IJ+MSwBWKG+SM3b2SUfdrhC+gu01QkV2KmRQgREThBfSQRoufqRfxfHUxpG1WcaFjP+kojcFyO9Qqtpgt3qLCg==} - peerDependencies: - react: '>=0.14.9' - - prismjs@1.29.0: - resolution: {integrity: sha512-Kx/1w86q/epKcmte75LNrEoT+lX8pBpavuAbvJWRXar7Hz8jrtF+e3vY751p0R8H9HdArwaCTNDDzHg/ScJK1Q==} - engines: {node: '>=6'} - - process-nextick-args@2.0.1: - resolution: {integrity: sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==} - - promise@7.3.1: - resolution: {integrity: sha512-nolQXZ/4L+bP/UGlkfaIujX9BKxGwmQ9OT4mOt5yvy8iK1h3wqTEJCijzGANTCCl9nWjY41juyAn2K3Q1hLLTg==} - - prompts@2.4.2: - resolution: {integrity: sha512-NxNv/kLguCA7p3jE8oL2aEBsrJWgAakBpgmgK6lpPWV+WuOmY6r2/zbAVnP+T8bQlA0nzHXSJSJW0Hq7ylaD2Q==} - engines: {node: '>= 6'} - - prop-types@15.8.1: - resolution: {integrity: sha512-oj87CgZICdulUohogVAR7AjlC0327U4el4L6eAvOqCeudMDVU0NThNaV+b9Df4dXgSP1gXMTnPdhfe/2qDH5cg==} - - property-information@5.6.0: - resolution: {integrity: sha512-YUHSPk+A30YPv+0Qf8i9Mbfe/C0hdPXk1s1jPVToV8pk8BQtpw10ct89Eo7OWkutrwqvT0eicAxlOg3dOAu8JA==} - - proxy-addr@2.0.7: - resolution: {integrity: sha512-llQsMLSUDUPT44jdrU/O37qlnifitDP+ZwrmmZcoSKyLKvtZxpyV0n2/bD/N4tBAAZ/gJEdZU7KMraoK1+XYAg==} - engines: {node: '>= 0.10'} - - proxy-from-env@1.1.0: - resolution: {integrity: sha512-D+zkORCbA9f1tdWRK0RaCR3GPv50cMxcrz4X8k5LTSUD1Dkw47mKJEZQNunItRTkWwgtaUSo1RVFRIG9ZXiFYg==} - - pump@3.0.0: - resolution: {integrity: sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==} - - punycode@1.4.1: - resolution: {integrity: sha512-jmYNElW7yvO7TV33CjSmvSiE2yco3bV2czu/OzDKdMNVZQWfxCblURLhf+47syQRBntjfLdd/H0egrzIG+oaFQ==} - - punycode@2.3.1: - resolution: {integrity: sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==} - engines: {node: '>=6'} - - pupa@2.1.1: - resolution: {integrity: sha512-l1jNAspIBSFqbT+y+5FosojNpVpF94nlI+wDUpqP9enwOTfHx9f0gh5nB96vl+6yTpsJsypeNrwfzPrKuHB41A==} - engines: {node: '>=8'} - - pure-color@1.3.0: - resolution: {integrity: sha512-QFADYnsVoBMw1srW7OVKEYjG+MbIa49s54w1MA1EDY6r2r/sTcKKYqRX1f4GYvnXP7eN/Pe9HFcX+hwzmrXRHA==} - - q@1.5.1: - resolution: {integrity: sha512-kV/CThkXo6xyFEZUugw/+pIOywXcDbFYgSct5cT3gqlbkBE1SJdwy6UQoZvodiWF/ckQLZyDE/Bu1M6gVu5lVw==} - engines: {node: '>=0.6.0', teleport: '>=0.2.0'} - deprecated: |- - You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. - - (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) - - qs@6.11.0: - resolution: {integrity: sha512-MvjoMCJwEarSbUYk5O+nmoSzSutSsTwF85zcHPQ9OrlFoZOYIjaqBAJIqIXjptyD5vThxGq52Xu/MaJzRkIk4Q==} - engines: {node: '>=0.6'} - - queue-microtask@1.2.3: - resolution: {integrity: sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==} - - queue@6.0.2: - resolution: {integrity: sha512-iHZWu+q3IdFZFX36ro/lKBkSvfkztY5Y7HMiPlOUjhupPcG2JMfst2KKEpu5XndviX/3UhFbRngUPNKtgvtZiA==} - - randombytes@2.1.0: - resolution: {integrity: sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==} - - range-parser@1.2.0: - resolution: {integrity: sha512-kA5WQoNVo4t9lNx2kQNFCxKeBl5IbbSNBl1M/tLkw9WCn+hxNBAW5Qh8gdhs63CJnhjJ2zQWFoqPJP2sK1AV5A==} - engines: {node: '>= 0.6'} - - range-parser@1.2.1: - resolution: {integrity: sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==} - engines: {node: '>= 0.6'} - - raw-body@2.5.2: - resolution: {integrity: sha512-8zGqypfENjCIqGhgXToC8aB2r7YrBX+AQAfIPs/Mlk+BtPTztOvTS01NRW/3Eh60J+a48lt8qsCzirQ6loCVfA==} - engines: {node: '>= 0.8'} - - rc@1.2.8: - resolution: {integrity: sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==} - hasBin: true - - react-base16-styling@0.6.0: - resolution: {integrity: sha512-yvh/7CArceR/jNATXOKDlvTnPKPmGZz7zsenQ3jUwLzHkNUR0CvY3yGYJbWJ/nnxsL8Sgmt5cO3/SILVuPO6TQ==} - - react-dev-utils@12.0.1: - resolution: {integrity: sha512-84Ivxmr17KjUupyqzFode6xKhjwuEJDROWKJy/BthkL7Wn6NJ8h4WE6k/exAv6ImS+0oZLRRW5j/aINMHyeGeQ==} - engines: {node: '>=14'} - peerDependencies: - typescript: '>=2.7' - webpack: '>=4' - peerDependenciesMeta: - typescript: - optional: true - - react-dom@17.0.2: - resolution: {integrity: sha512-s4h96KtLDUQlsENhMn1ar8t2bEa+q/YAtj8pPPdIjPDGBDIVNsrD9aXNWqspUe6AzKCIG0C1HZZLqLV7qpOBGA==} - peerDependencies: - react: 17.0.2 - - react-error-overlay@6.0.11: - resolution: {integrity: sha512-/6UZ2qgEyH2aqzYZgQPxEnz33NJ2gNsnHA2o5+o4wW9bLM/JYQitNP9xPhsXwC08hMMovfGe/8retsdDsczPRg==} - - react-fast-compare@3.2.2: - resolution: {integrity: sha512-nsO+KSNgo1SbJqJEYRE9ERzo7YtYbou/OqjSQKxV7jcKox7+usiUVZOAC+XnDOABXggQTno0Y1CpVnuWEc1boQ==} - - react-helmet-async@1.3.0: - resolution: {integrity: sha512-9jZ57/dAn9t3q6hneQS0wukqC2ENOBgMNVEhb/ZG9ZSxUetzVIw4iAmEU38IaVg3QGYauQPhSeUTuIUtFglWpg==} - peerDependencies: - react: ^16.6.0 || ^17.0.0 || ^18.0.0 - react-dom: ^16.6.0 || ^17.0.0 || ^18.0.0 - - react-helmet-async@2.0.5: - resolution: {integrity: sha512-rYUYHeus+i27MvFE+Jaa4WsyBKGkL6qVgbJvSBoX8mbsWoABJXdEO0bZyi0F6i+4f0NuIb8AvqPMj3iXFHkMwg==} - peerDependencies: - react: ^16.6.0 || ^17.0.0 || ^18.0.0 - - react-is@16.13.1: - resolution: {integrity: sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ==} - - react-json-view@1.21.3: - resolution: {integrity: sha512-13p8IREj9/x/Ye4WI/JpjhoIwuzEgUAtgJZNBJckfzJt1qyh24BdTm6UQNGnyTq9dapQdrqvquZTo3dz1X6Cjw==} - peerDependencies: - react: ^17.0.0 || ^16.3.0 || ^15.5.4 - react-dom: ^17.0.0 || ^16.3.0 || ^15.5.4 - - react-lifecycles-compat@3.0.4: - resolution: {integrity: sha512-fBASbA6LnOU9dOU2eW7aQ8xmYBSXUIWr+UmF9b1efZBazGNO+rcXT/icdKnYm2pTwcRylVUYwW7H1PHfLekVzA==} - - react-loadable-ssr-addon-v5-slorber@1.0.1: - resolution: {integrity: sha512-lq3Lyw1lGku8zUEJPDxsNm1AfYHBrO9Y1+olAYwpUJ2IGFBskM0DMKok97A6LWUpHm+o7IvQBOWu9MLenp9Z+A==} - engines: {node: '>=10.13.0'} - peerDependencies: - react-loadable: '*' - webpack: '>=4.41.1 || 5.x' - - react-router-config@5.1.1: - resolution: {integrity: sha512-DuanZjaD8mQp1ppHjgnnUnyOlqYXZVjnov/JzFhjLEwd3Z4dYjMSnqrEzzGThH47vpCOqPPwJM2FtthLeJ8Pbg==} - peerDependencies: - react: '>=15' - react-router: '>=5' - - react-router-dom@5.3.4: - resolution: {integrity: sha512-m4EqFMHv/Ih4kpcBCONHbkT68KoAeHN4p3lAGoNryfHi0dMy0kCzEZakiKRsvg5wHZ/JLrLW8o8KomWiz/qbYQ==} - peerDependencies: - react: '>=15' - - react-router@5.3.4: - resolution: {integrity: sha512-Ys9K+ppnJah3QuaRiLxk+jDWOR1MekYQrlytiXxC1RyfbdsZkS5pvKAzCCr031xHixZwpnsYNT5xysdFHQaYsA==} - peerDependencies: - react: '>=15' - - react-textarea-autosize@8.5.3: - resolution: {integrity: sha512-XT1024o2pqCuZSuBt9FwHlaDeNtVrtCXu0Rnz88t1jUGheCLa3PhjE1GH8Ctm2axEtvdCl5SUHYschyQ0L5QHQ==} - engines: {node: '>=10'} - peerDependencies: - react: ^16.8.0 || ^17.0.0 || ^18.0.0 - - react@17.0.2: - resolution: {integrity: sha512-gnhPt75i/dq/z3/6q/0asP78D0u592D5L1pd7M8P+dck6Fu/jJeL6iVVK23fptSUZj8Vjf++7wXA8UNclGQcbA==} - engines: {node: '>=0.10.0'} - - readable-stream@2.3.8: - resolution: {integrity: sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==} - - readable-stream@3.6.2: - resolution: {integrity: sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==} - engines: {node: '>= 6'} - - readdirp@3.6.0: - resolution: {integrity: sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==} - engines: {node: '>=8.10.0'} - - reading-time@1.5.0: - resolution: {integrity: sha512-onYyVhBNr4CmAxFsKS7bz+uTLRakypIe4R+5A824vBSkQy/hB3fZepoVEf8OVAxzLvK+H/jm9TzpI3ETSm64Kg==} - - rechoir@0.6.2: - resolution: {integrity: sha512-HFM8rkZ+i3zrV+4LQjwQ0W+ez98pApMGM3HUrN04j3CqzPOzl9nmP15Y8YXNm8QHGv/eacOVEjqhmWpkRV0NAw==} - engines: {node: '>= 0.10'} - - recursive-readdir@2.2.3: - resolution: {integrity: sha512-8HrF5ZsXk5FAH9dgsx3BlUer73nIhuj+9OrQwEbLTPOBzGkL1lsFCR01am+v+0m2Cmbs1nP12hLDl5FA7EszKA==} - engines: {node: '>=6.0.0'} - - regenerate-unicode-properties@10.1.1: - resolution: {integrity: sha512-X007RyZLsCJVVrjgEFVpLUTZwyOZk3oiL75ZcuYjlIWd6rNJtOjkBwQc5AsRrpbKVkxN6sklw/k/9m2jJYOf8Q==} - engines: {node: '>=4'} - - regenerate@1.4.2: - resolution: {integrity: sha512-zrceR/XhGYU/d/opr2EKO7aRHUeiBI8qjtfHqADTwZd6Szfy16la6kqD0MIUs5z5hx6AaKa+PixpPrR289+I0A==} - - regenerator-runtime@0.14.1: - resolution: {integrity: sha512-dYnhHh0nJoMfnkZs6GmmhFknAGRrLznOu5nc9ML+EJxGvrx6H7teuevqVqCuPcPK//3eDrrjQhehXVx9cnkGdw==} - - regenerator-transform@0.15.2: - resolution: {integrity: sha512-hfMp2BoF0qOk3uc5V20ALGDS2ddjQaLrdl7xrGXvAIow7qeWRM2VA2HuCHkUKk9slq3VwEwLNK3DFBqDfPGYtg==} - - regexp.prototype.flags@1.5.2: - resolution: {integrity: sha512-NcDiDkTLuPR+++OCKB0nWafEmhg/Da8aUPLPMQbK+bxKKCm1/S5he+AqYa4PlMCVBalb4/yxIRub6qkEx5yJbw==} - engines: {node: '>= 0.4'} - - regexpu-core@5.3.2: - resolution: {integrity: sha512-RAM5FlZz+Lhmo7db9L298p2vHP5ZywrVXmVXpmAD9GuL5MPH6t9ROw1iA/wfHkQ76Qe7AaPF0nGuim96/IrQMQ==} - engines: {node: '>=4'} - - registry-auth-token@4.2.2: - resolution: {integrity: sha512-PC5ZysNb42zpFME6D/XlIgtNGdTl8bBOCw90xQLVMpzuuubJKYDWFAEuUNc+Cn8Z8724tg2SDhDRrkVEsqfDMg==} - engines: {node: '>=6.0.0'} - - registry-url@5.1.0: - resolution: {integrity: sha512-8acYXXTI0AkQv6RAOjE3vOaIXZkT9wo4LOFbBKYQEEnnMNBpKqdUrI6S4NT0KPIo/WVvJ5tE/X5LF/TQUf0ekw==} - engines: {node: '>=8'} - - regjsparser@0.9.1: - resolution: {integrity: sha512-dQUtn90WanSNl+7mQKcXAgZxvUe7Z0SqXlgzv0za4LwiUhyzBC58yQO3liFoUgu8GiJVInAhJjkj1N0EtQ5nkQ==} - hasBin: true - - relateurl@0.2.7: - resolution: {integrity: sha512-G08Dxvm4iDN3MLM0EsP62EDV9IuhXPR6blNz6Utcp7zyV3tr4HVNINt6MpaRWbxoOHT3Q7YN2P+jaHX8vUbgog==} - engines: {node: '>= 0.10'} - - remark-emoji@2.2.0: - resolution: {integrity: sha512-P3cj9s5ggsUvWw5fS2uzCHJMGuXYRb0NnZqYlNecewXt8QBU9n5vW3DUUKOhepS8F9CwdMx9B8a3i7pqFWAI5w==} - - remark-footnotes@2.0.0: - resolution: {integrity: sha512-3Clt8ZMH75Ayjp9q4CorNeyjwIxHFcTkaektplKGl2A1jNGEUey8cKL0ZC5vJwfcD5GFGsNLImLG/NGzWIzoMQ==} - - remark-mdx@1.6.22: - resolution: {integrity: sha512-phMHBJgeV76uyFkH4rvzCftLfKCr2RZuF+/gmVcaKrpsihyzmhXjA0BEMDaPTXG5y8qZOKPVo83NAOX01LPnOQ==} - - remark-parse@8.0.3: - resolution: {integrity: sha512-E1K9+QLGgggHxCQtLt++uXltxEprmWzNfg+MxpfHsZlrddKzZ/hZyWHDbK3/Ap8HJQqYJRXP+jHczdL6q6i85Q==} - - remark-squeeze-paragraphs@4.0.0: - resolution: {integrity: sha512-8qRqmL9F4nuLPIgl92XUuxI3pFxize+F1H0e/W3llTk0UsjJaj01+RrirkMw7P21RKe4X6goQhYRSvNWX+70Rw==} - - renderkid@3.0.0: - resolution: {integrity: sha512-q/7VIQA8lmM1hF+jn+sFSPWGlMkSAeNYcPLmDQx2zzuiDfaLrOmumR8iaUKlenFgh0XRPIUeSPlH3A+AW3Z5pg==} - - repeat-string@1.6.1: - resolution: {integrity: sha512-PV0dzCYDNfRi1jCDbJzpW7jNNDRuCOG/jI5ctQcGKt/clZD+YcPS3yIlWuTJMmESC8aevCFmWJy5wjAFgNqN6w==} - engines: {node: '>=0.10'} - - require-from-string@2.0.2: - resolution: {integrity: sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==} - engines: {node: '>=0.10.0'} - - require-like@0.1.2: - resolution: {integrity: sha512-oyrU88skkMtDdauHDuKVrgR+zuItqr6/c//FXzvmxRGMexSDc6hNvJInGW3LL46n+8b50RykrvwSUIIQH2LQ5A==} - - requires-port@1.0.0: - resolution: {integrity: sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ==} - - resolve-from@4.0.0: - resolution: {integrity: sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==} - engines: {node: '>=4'} - - resolve-pathname@3.0.0: - resolution: {integrity: sha512-C7rARubxI8bXFNB/hqcp/4iUeIXJhJZvFPFPiSPRnhU5UPxzMFIl+2E6yY6c4k9giDJAhtV+enfA+G89N6Csng==} - - resolve@1.22.8: - resolution: {integrity: sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw==} - hasBin: true - - responselike@1.0.2: - resolution: {integrity: sha512-/Fpe5guzJk1gPqdJLJR5u7eG/gNY4nImjbRDaVWVMRhne55TCmj2i9Q+54PBRfatRC8v/rIiv9BN0pMd9OV5EQ==} - - retry@0.13.1: - resolution: {integrity: sha512-XQBQ3I8W1Cge0Seh+6gjj03LbmRFWuoszgK9ooCpwYIrhhoO80pfq4cUkU5DkknwfOfFteRwlZ56PYOGYyFWdg==} - engines: {node: '>= 4'} - - reusify@1.0.4: - resolution: {integrity: sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==} - engines: {iojs: '>=1.0.0', node: '>=0.10.0'} - - rimraf@3.0.2: - resolution: {integrity: sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==} - deprecated: Rimraf versions prior to v4 are no longer supported - hasBin: true - - rtl-detect@1.1.2: - resolution: {integrity: sha512-PGMBq03+TTG/p/cRB7HCLKJ1MgDIi07+QU1faSjiYRfmY5UsAttV9Hs08jDAHVwcOwmVLcSJkpwyfXszVjWfIQ==} - - rtlcss@3.5.0: - resolution: {integrity: sha512-wzgMaMFHQTnyi9YOwsx9LjOxYXJPzS8sYnFaKm6R5ysvTkwzHiB0vxnbHwchHQT65PTdBjDG21/kQBWI7q9O7A==} - hasBin: true - - run-con@1.2.12: - resolution: {integrity: sha512-5257ILMYIF4RztL9uoZ7V9Q97zHtNHn5bN3NobeAnzB1P3ASLgg8qocM2u+R18ttp+VEM78N2LK8XcNVtnSRrg==} - hasBin: true - - run-parallel@1.2.0: - resolution: {integrity: sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==} - - rxjs@7.8.1: - resolution: {integrity: sha512-AA3TVj+0A2iuIoQkWEK/tqFjBq2j+6PO6Y0zJcvzLAFhEFIO3HL0vls9hWLncZbAAbK0mar7oZ4V079I/qPMxg==} - - safe-array-concat@1.1.2: - resolution: {integrity: sha512-vj6RsCsWBCf19jIeHEfkRMw8DPiBb+DMXklQ/1SGDHOMlHdPUkZXFQ2YdplS23zESTijAcurb1aSgJA3AgMu1Q==} - engines: {node: '>=0.4'} - - safe-buffer@5.1.2: - resolution: {integrity: sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==} - - safe-buffer@5.2.1: - resolution: {integrity: sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==} - - safe-regex-test@1.0.3: - resolution: {integrity: sha512-CdASjNJPvRa7roO6Ra/gLYBTzYzzPyyBXxIMdGW3USQLyjWEls2RgW5UBTXaQVp+OrpeCK3bLem8smtmheoRuw==} - engines: {node: '>= 0.4'} - - safer-buffer@2.1.2: - resolution: {integrity: sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==} - - sax@1.2.4: - resolution: {integrity: sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==} - - sax@1.4.1: - resolution: {integrity: sha512-+aWOz7yVScEGoKNd4PA10LZ8sk0A/z5+nXQG5giUO5rprX9jgYsTdov9qCchZiPIZezbZH+jRut8nPodFAX4Jg==} - - scheduler@0.20.2: - resolution: {integrity: sha512-2eWfGgAqqWFGqtdMmcL5zCMK1U8KlXv8SQFGglL3CEtd0aDVDWgeF/YoCmvln55m5zSk3J/20hTaSBeSObsQDQ==} - - schema-utils@2.7.0: - resolution: {integrity: sha512-0ilKFI6QQF5nxDZLFn2dMjvc4hjg/Wkg7rHd3jK6/A4a1Hl9VFdQWvgB1UMGoU94pad1P/8N7fMcEnLnSiju8A==} - engines: {node: '>= 8.9.0'} - - schema-utils@2.7.1: - resolution: {integrity: sha512-SHiNtMOUGWBQJwzISiVYKu82GiV4QYGePp3odlY1tuKO7gPtphAT5R/py0fA6xtbgLL/RvtJZnU9b8s0F1q0Xg==} - engines: {node: '>= 8.9.0'} - - schema-utils@3.3.0: - resolution: {integrity: sha512-pN/yOAvcC+5rQ5nERGuwrjLlYvLTbCibnZ1I7B1LaiAz9BRBlE9GMgE/eqV30P7aJQUf7Ddimy/RsbYO/GrVGg==} - engines: {node: '>= 10.13.0'} - - schema-utils@4.2.0: - resolution: {integrity: sha512-L0jRsrPpjdckP3oPug3/VxNKt2trR8TcabrM6FOAAlvC/9Phcmm+cuAgTlxBqdBR1WJx7Naj9WHw+aOmheSVbw==} - engines: {node: '>= 12.13.0'} - - search-insights@2.17.0: - resolution: {integrity: sha512-AskayU3QNsXQzSL6v4LTYST7NNfs2HWyHHB+sdORP9chsytAhro5XRfToAMI/LAVYgNbzowVZTMfBRodgbUHKg==} - - section-matter@1.0.0: - resolution: {integrity: sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==} - engines: {node: '>=4'} - - select-hose@2.0.0: - resolution: {integrity: sha512-mEugaLK+YfkijB4fx0e6kImuJdCIt2LxCRcbEYPqRGCs4F2ogyfZU5IAZRdjCP8JPq2AtdNoC/Dux63d9Kiryg==} - - selfsigned@2.4.1: - resolution: {integrity: sha512-th5B4L2U+eGLq1TVh7zNRGBapioSORUeymIydxgFpwww9d2qyKvtuPU2jJuHvYAwwqi2Y596QBL3eEqcPEYL8Q==} - engines: {node: '>=10'} - - semver-diff@3.1.1: - resolution: {integrity: sha512-GX0Ix/CJcHyB8c4ykpHGIAvLyOwOobtM/8d+TQkAd81/bEjgPHrfba41Vpesr7jX/t8Uh+R3EX9eAS5be+jQYg==} - engines: {node: '>=8'} - - semver@5.7.2: - resolution: {integrity: sha512-cBznnQ9KjJqU67B52RMC65CMarK2600WFnbkcaiwWq3xy/5haFJlshgnpjovMVJ+Hff49d8GEn0b87C5pDQ10g==} - hasBin: true - - semver@6.3.1: - resolution: {integrity: sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==} - hasBin: true - - semver@7.6.3: - resolution: {integrity: sha512-oVekP1cKtI+CTDvHWYFUcMtsK/00wmAEfyqKfNdARm8u1wNVhSgaX7A8d4UuIlUI5e84iEwOhs7ZPYRmzU9U6A==} - engines: {node: '>=10'} - hasBin: true - - send@0.18.0: - resolution: {integrity: sha512-qqWzuOjSFOuqPjFe4NOsMLafToQQwBSOEpS+FwEt3A2V3vKubTquT3vmLTQpFgMXp8AlFWFuP1qKaJZOtPpVXg==} - engines: {node: '>= 0.8.0'} - - serialize-javascript@6.0.2: - resolution: {integrity: sha512-Saa1xPByTTq2gdeFZYLLo+RFE35NHZkAbqZeWNd3BpzppeVisAqpDjcp8dyf6uIvEqJRd46jemmyA4iFIeVk8g==} - - serve-handler@6.1.5: - resolution: {integrity: sha512-ijPFle6Hwe8zfmBxJdE+5fta53fdIY0lHISJvuikXB3VYFafRjMRpOffSPvCYsbKyBA7pvy9oYr/BT1O3EArlg==} - - serve-index@1.9.1: - resolution: {integrity: sha512-pXHfKNP4qujrtteMrSBb0rc8HJ9Ms/GrXwcUtUtD5s4ewDJI8bT3Cz2zTVRMKtri49pLx2e0Ya8ziP5Ya2pZZw==} - engines: {node: '>= 0.8.0'} - - serve-static@1.15.0: - resolution: {integrity: sha512-XGuRDNjXUijsUL0vl6nSD7cwURuzEgglbOaFuZM9g3kwDXOWVTck0jLzjPzGD+TazWbboZYu52/9/XPdUgne9g==} - engines: {node: '>= 0.8.0'} - - set-function-length@1.2.2: - resolution: {integrity: sha512-pgRc4hJ4/sNjWCSS9AmnS40x3bNMDTknHgL5UaMBTMyJnU90EgWh1Rz+MC9eFu4BuN/UwZjKQuY/1v3rM7HMfg==} - engines: {node: '>= 0.4'} - - set-function-name@2.0.2: - resolution: {integrity: sha512-7PGFlmtwsEADb0WYyvCMa1t+yke6daIG4Wirafur5kcf+MhUnPms1UeR0CKQdTZD81yESwMHbtn+TR+dMviakQ==} - engines: {node: '>= 0.4'} - - setimmediate@1.0.5: - resolution: {integrity: sha512-MATJdZp8sLqDl/68LfQmbP8zKPLQNV6BIZoIgrscFDQ+RsvK/BxeDQOgyxKKoh0y/8h3BqVFnCqQ/gd+reiIXA==} - - setprototypeof@1.1.0: - resolution: {integrity: sha512-BvE/TwpZX4FXExxOxZyRGQQv651MSwmWKZGqvmPcRIjDqWub67kTKuIMx43cZZrS/cBBzwBcNDWoFxt2XEFIpQ==} - - setprototypeof@1.2.0: - resolution: {integrity: sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw==} - - shallow-clone@3.0.1: - resolution: {integrity: sha512-/6KqX+GVUdqPuPPd2LxDDxzX6CAbjJehAAOKlNpqqUpAqPM6HeL8f+o3a+JsyGjn2lv0WY8UsTgUJjU9Ok55NA==} - engines: {node: '>=8'} - - shallowequal@1.1.0: - resolution: {integrity: sha512-y0m1JoUZSlPAjXVtPPW70aZWfIL/dSP7AFkRnniLCrK/8MDKog3TySTBmckD+RObVxH0v4Tox67+F14PdED2oQ==} - - shebang-command@2.0.0: - resolution: {integrity: sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==} - engines: {node: '>=8'} - - shebang-regex@3.0.0: - resolution: {integrity: sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==} - engines: {node: '>=8'} - - shell-quote@1.8.1: - resolution: {integrity: sha512-6j1W9l1iAs/4xYBI1SYOVZyFcCis9b4KCLQ8fgAGG07QvzaRLVVRQvAy85yNmmZSjYjg4MWh4gNvlPujU/5LpA==} - - shelljs@0.8.5: - resolution: {integrity: sha512-TiwcRcrkhHvbrZbnRcFYMLl30Dfov3HKqzp5tO5b4pt6G/SezKcYhmDg15zXVBswHmctSAQKznqNW2LO5tTDow==} - engines: {node: '>=4'} - hasBin: true - - side-channel@1.0.6: - resolution: {integrity: sha512-fDW/EZ6Q9RiO8eFG8Hj+7u/oW+XrPTIChwCOM2+th2A6OblDtYYIpve9m+KvI9Z4C9qSEXlaGR6bTEYHReuglA==} - engines: {node: '>= 0.4'} - - signal-exit@3.0.7: - resolution: {integrity: sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==} - - signal-exit@4.1.0: - resolution: {integrity: sha512-bzyZ1e88w9O1iNJbKnOlvYTrWPDl46O1bG0D3XInv+9tkPrxrN8jUUTiFlDkkmKWgn1M6CfIA13SuGqOa9Korw==} - engines: {node: '>=14'} - - sirv@2.0.4: - resolution: {integrity: sha512-94Bdh3cC2PKrbgSOUqTiGPWVZeSiXfKOVZNJniWoqrWrRkB1CJzBU3NEbiTsPcYy1lDsANA/THzS+9WBiy5nfQ==} - engines: {node: '>= 10'} - - sisteransi@1.0.5: - resolution: {integrity: sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==} - - sitemap@7.1.2: - resolution: {integrity: sha512-ARCqzHJ0p4gWt+j7NlU5eDlIO9+Rkr/JhPFZKKQ1l5GCus7rJH4UdrlVAh0xC/gDS/Qir2UMxqYNHtsKr2rpCw==} - engines: {node: '>=12.0.0', npm: '>=5.6.0'} - hasBin: true - - slash@3.0.0: - resolution: {integrity: sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==} - engines: {node: '>=8'} - - slash@4.0.0: - resolution: {integrity: sha512-3dOsAHXXUkQTpOYcoAxLIorMTp4gIQr5IW3iVb7A7lFIp0VHhnynm9izx6TssdrIcVIESAlVjtnO2K8bg+Coew==} - engines: {node: '>=12'} - - sockjs@0.3.24: - resolution: {integrity: sha512-GJgLTZ7vYb/JtPSSZ10hsOYIvEYsjbNU+zPdIHcUaWVNUEPivzxku31865sSSud0Da0W4lEeOPlmw93zLQchuQ==} - - sort-css-media-queries@2.1.0: - resolution: {integrity: sha512-IeWvo8NkNiY2vVYdPa27MCQiR0MN0M80johAYFVxWWXQ44KU84WNxjslwBHmc/7ZL2ccwkM7/e6S5aiKZXm7jA==} - engines: {node: '>= 6.3.0'} - - source-map-js@1.2.0: - resolution: {integrity: sha512-itJW8lvSA0TXEphiRoawsCksnlf8SyvmFzIhltqAHluXd88pkCd+cXJVHTDwdCr0IzwptSm035IHQktUu1QUMg==} - engines: {node: '>=0.10.0'} - - source-map-support@0.5.21: - resolution: {integrity: sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==} - - source-map@0.5.7: - resolution: {integrity: sha512-LbrmJOMUSdEVxIKvdcJzQC+nQhe8FUZQTXQy6+I75skNgn3OoQ0DZA8YnFa7gp8tqtL3KPf1kmo0R5DoApeSGQ==} - engines: {node: '>=0.10.0'} - - source-map@0.6.1: - resolution: {integrity: sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==} - engines: {node: '>=0.10.0'} - - space-separated-tokens@1.1.5: - resolution: {integrity: sha512-q/JSVd1Lptzhf5bkYm4ob4iWPjx0KiRe3sRFBNrVqbJkFaBm5vbbowy1mymoPNLRa52+oadOhJ+K49wsSeSjTA==} - - spdy-transport@3.0.0: - resolution: {integrity: sha512-hsLVFE5SjA6TCisWeJXFKniGGOpBgMLmerfO2aCyCU5s7nJ/rpAepqmFifv/GCbSbueEeAJJnmSQ2rKC/g8Fcw==} - - spdy@4.0.2: - resolution: {integrity: sha512-r46gZQZQV+Kl9oItvl1JZZqJKGr+oEkB08A6BzkiR7593/7IbtuncXHd2YoYeTsG4157ZssMu9KYvUHLcjcDoA==} - engines: {node: '>=6.0.0'} - - sprintf-js@1.0.3: - resolution: {integrity: sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==} - - stable@0.1.8: - resolution: {integrity: sha512-ji9qxRnOVfcuLDySj9qzhGSEFVobyt1kIOSkj1qZzYLzq7Tos/oUUWvotUPQLlrsidqsK6tBH89Bc9kL5zHA6w==} - deprecated: 'Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility' - - state-toggle@1.0.3: - resolution: {integrity: sha512-d/5Z4/2iiCnHw6Xzghyhb+GcmF89bxwgXG60wjIiZaxnymbyOmI8Hk4VqHXiVVp6u2ysaskFfXg3ekCj4WNftQ==} - - statuses@1.5.0: - resolution: {integrity: sha512-OpZ3zP+jT1PI7I8nemJX4AKmAX070ZkYPVWV/AaKTJl+tXCTGyVdC1a4SL8RUQYEwk/f34ZX8UTykN68FwrqAA==} - engines: {node: '>= 0.6'} - - statuses@2.0.1: - resolution: {integrity: sha512-RwNA9Z/7PrK06rYLIzFMlaF+l73iwpzsqRIFgbMLbTcLD6cOao82TaWefPXQvB2fOC4AjuYSEndS7N/mTCbkdQ==} - engines: {node: '>= 0.8'} - - std-env@3.7.0: - resolution: {integrity: sha512-JPbdCEQLj1w5GilpiHAx3qJvFndqybBysA3qUOnznweH4QbNYUsW/ea8QzSrnh0vNsezMMw5bcVool8lM0gwzg==} - - string-width@4.2.3: - resolution: {integrity: sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==} - engines: {node: '>=8'} - - string-width@5.1.2: - resolution: {integrity: sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==} - engines: {node: '>=12'} - - string.prototype.trim@1.2.9: - resolution: {integrity: sha512-klHuCNxiMZ8MlsOihJhJEBJAiMVqU3Z2nEXWfWnIqjN0gEFS9J9+IxKozWWtQGcgoa1WUZzLjKPTr4ZHNFTFxw==} - engines: {node: '>= 0.4'} - - string.prototype.trimend@1.0.8: - resolution: {integrity: sha512-p73uL5VCHCO2BZZ6krwwQE3kCzM7NKmis8S//xEC6fQonchbum4eP6kR4DLEjQFO3Wnj3Fuo8NM0kOSjVdHjZQ==} - - string.prototype.trimstart@1.0.8: - resolution: {integrity: sha512-UXSH262CSZY1tfu3G3Secr6uGLCFVPMhIqHjlgCUtCCcgihYc/xKs9djMTMUOb2j1mVSeU8EU6NWc/iQKU6Gfg==} - engines: {node: '>= 0.4'} - - string_decoder@1.1.1: - resolution: {integrity: sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==} - - string_decoder@1.3.0: - resolution: {integrity: sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==} - - stringify-object@3.3.0: - resolution: {integrity: sha512-rHqiFh1elqCQ9WPLIC8I0Q/g/wj5J1eMkyoiD6eoQApWHP0FtlK7rqnhmabL5VUY9JQCcqwwvlOaSuutekgyrw==} - engines: {node: '>=4'} - - strip-ansi@6.0.1: - resolution: {integrity: sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==} - engines: {node: '>=8'} - - strip-ansi@7.1.0: - resolution: {integrity: sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ==} - engines: {node: '>=12'} - - strip-bom-string@1.0.0: - resolution: {integrity: sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g==} - engines: {node: '>=0.10.0'} - - strip-final-newline@2.0.0: - resolution: {integrity: sha512-BrpvfNAE3dcvq7ll3xVumzjKjZQ5tI1sEUIKr3Uoks0XUl45St3FlatVqef9prk4jRDzhW6WZg+3bk93y6pLjA==} - engines: {node: '>=6'} - - strip-json-comments@2.0.1: - resolution: {integrity: sha512-4gB8na07fecVVkOI6Rs4e7T6NOTki5EmL7TUduTs6bu3EdnSycntVJ4re8kgZA+wx9IueI2Y11bfbgwtzuE0KQ==} - engines: {node: '>=0.10.0'} - - strip-json-comments@3.1.1: - resolution: {integrity: sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==} - engines: {node: '>=8'} - - style-to-object@0.3.0: - resolution: {integrity: sha512-CzFnRRXhzWIdItT3OmF8SQfWyahHhjq3HwcMNCNLn+N7klOOqPjMeG/4JSu77D7ypZdGvSzvkrbyeTMizz2VrA==} - - stylehacks@5.1.1: - resolution: {integrity: sha512-sBpcd5Hx7G6seo7b1LkpttvTz7ikD0LlH5RmdcBNb6fFR0Fl7LQwHDFr300q4cwUqi+IYrFGmsIHieMBfnN/Bw==} - engines: {node: ^10 || ^12 || >=14.0} - peerDependencies: - postcss: ^8.2.15 - - supports-color@5.5.0: - resolution: {integrity: sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==} - engines: {node: '>=4'} - - supports-color@7.2.0: - resolution: {integrity: sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==} - engines: {node: '>=8'} - - supports-color@8.1.1: - resolution: {integrity: sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==} - engines: {node: '>=10'} - - supports-preserve-symlinks-flag@1.0.0: - resolution: {integrity: sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==} - engines: {node: '>= 0.4'} - - svg-parser@2.0.4: - resolution: {integrity: sha512-e4hG1hRwoOdRb37cIMSgzNsxyzKfayW6VOflrwvR+/bzrkyxY/31WkbgnQpgtrNp1SdpJvpUAGTa/ZoiPNDuRQ==} - - svgo@1.3.2: - resolution: {integrity: sha512-yhy/sQYxR5BkC98CY7o31VGsg014AKLEPxdfhora76l36hD9Rdy5NZA/Ocn6yayNPgSamYdtX2rFJdcv07AYVw==} - engines: {node: '>=4.0.0'} - deprecated: This SVGO version is no longer supported. Upgrade to v2.x.x. - hasBin: true - - svgo@2.8.0: - resolution: {integrity: sha512-+N/Q9kV1+F+UeWYoSiULYo4xYSDQlTgb+ayMobAXPwMnLvop7oxKMo9OzIrX5x3eS4L4f2UHhc9axXwY8DpChg==} - engines: {node: '>=10.13.0'} - hasBin: true - - swc-loader@0.2.6: - resolution: {integrity: sha512-9Zi9UP2YmDpgmQVbyOPJClY0dwf58JDyDMQ7uRc4krmc72twNI2fvlBWHLqVekBpPc7h5NJkGVT1zNDxFrqhvg==} - peerDependencies: - '@swc/core': ^1.2.147 - webpack: '>=2' - - tapable@1.1.3: - resolution: {integrity: sha512-4WK/bYZmj8xLr+HUCODHGF1ZFzsYffasLUgEiMBY4fgtltdO6B4WJtlSbPaDTLpYTcGVwM2qLnFTICEcNxs3kA==} - engines: {node: '>=6'} - - tapable@2.2.1: - resolution: {integrity: sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ==} - engines: {node: '>=6'} - - tar@4.4.19: - resolution: {integrity: sha512-a20gEsvHnWe0ygBY8JbxoM4w3SJdhc7ZAuxkLqh+nvNQN2IOt0B5lLgM490X5Hl8FF0dl0tOf2ewFYAlIFgzVA==} - engines: {node: '>=4.5'} - - terser-webpack-plugin@5.3.10: - resolution: {integrity: sha512-BKFPWlPDndPs+NGGCr1U59t0XScL5317Y0UReNrHaw9/FwhPENlq6bfgs+4yPfyP51vqC1bQ4rp1EfXW5ZSH9w==} - engines: {node: '>= 10.13.0'} - peerDependencies: - '@swc/core': '*' - esbuild: '*' - uglify-js: '*' - webpack: ^5.1.0 - peerDependenciesMeta: - '@swc/core': - optional: true - esbuild: - optional: true - uglify-js: - optional: true - - terser@5.31.6: - resolution: {integrity: sha512-PQ4DAriWzKj+qgehQ7LK5bQqCFNMmlhjR2PFFLuqGCpuCAauxemVBWwWOxo3UIwWQx8+Pr61Df++r76wDmkQBg==} - engines: {node: '>=10'} - hasBin: true - - text-table@0.2.0: - resolution: {integrity: sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==} - - thunky@1.1.0: - resolution: {integrity: sha512-eHY7nBftgThBqOyHGVN+l8gF0BucP09fMo0oO/Lb0w1OF80dJv+lDVpXG60WMQvkcxAkNybKsrEIE3ZtKGmPrA==} - - tiny-invariant@1.3.3: - resolution: {integrity: sha512-+FbBPE1o9QAYvviau/qC5SE3caw21q3xkvWKBtja5vgqOWIHHJ3ioaq1VPfn/Szqctz2bU/oYeKd9/z5BL+PVg==} - - tiny-warning@1.0.3: - resolution: {integrity: sha512-lBN9zLN/oAf68o3zNXYrdCt1kP8WsiGW8Oo2ka41b2IM5JL/S1CTyX1rW0mb/zSuJun0ZUrDxx4sqvYS2FWzPA==} - - to-fast-properties@2.0.0: - resolution: {integrity: sha512-/OaKK0xYrs3DmxRYqL/yDc+FxFUVYhDlXMhRmv3z915w2HF1tnN1omB354j8VUGO/hbRzyD6Y3sA7v7GS/ceog==} - engines: {node: '>=4'} - - to-readable-stream@1.0.0: - resolution: {integrity: sha512-Iq25XBt6zD5npPhlLVXGFN3/gyR2/qODcKNNyTMd4vbm39HUaOiAM4PMq0eMVC/Tkxz+Zjdsc55g9yyz+Yq00Q==} - engines: {node: '>=6'} - - to-regex-range@5.0.1: - resolution: {integrity: sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==} - engines: {node: '>=8.0'} - - toidentifier@1.0.1: - resolution: {integrity: sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA==} - engines: {node: '>=0.6'} - - totalist@3.0.1: - resolution: {integrity: sha512-sf4i37nQ2LBx4m3wB74y+ubopq6W/dIzXg0FDGjsYnZHVa1Da8FH853wlL2gtUhg+xJXjfk3kUZS3BRoQeoQBQ==} - engines: {node: '>=6'} - - tr46@0.0.3: - resolution: {integrity: sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw==} - - trim-trailing-lines@1.1.4: - resolution: {integrity: sha512-rjUWSqnfTNrjbB9NQWfPMH/xRK1deHeGsHoVfpxJ++XeYXE0d6B1En37AHfw3jtfTU7dzMzZL2jjpe8Qb5gLIQ==} - - trim@0.0.1: - resolution: {integrity: sha512-YzQV+TZg4AxpKxaTHK3c3D+kRDCGVEE7LemdlQZoQXn0iennk10RsIoY6ikzAqJTc9Xjl9C1/waHom/J86ziAQ==} - deprecated: Use String.prototype.trim() instead - - trough@1.0.5: - resolution: {integrity: sha512-rvuRbTarPXmMb79SmzEp8aqXNKcK+y0XaB298IXueQ8I2PsrATcPBCSPyK/dDNa2iWOhKlfNnOjdAOTBU/nkFA==} - - tslib@2.7.0: - resolution: {integrity: sha512-gLXCKdN1/j47AiHiOkJN69hJmcbGTHI0ImLmbYLHykhgeN0jVGola9yVjFgzCUklsZQMW55o+dW7IXv3RCXDzA==} - - type-fest@0.20.2: - resolution: {integrity: sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ==} - engines: {node: '>=10'} - - type-fest@2.19.0: - resolution: {integrity: sha512-RAH822pAdBgcNMAfWnCBU3CFZcfZ/i1eZjwFU/dsLKumyuuP3niueg2UAukXYF0E2AAoc82ZSSf9J0WQBinzHA==} - engines: {node: '>=12.20'} - - type-is@1.6.18: - resolution: {integrity: sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g==} - engines: {node: '>= 0.6'} - - typed-array-buffer@1.0.2: - resolution: {integrity: sha512-gEymJYKZtKXzzBzM4jqa9w6Q1Jjm7x2d+sh19AdsD4wqnMPDYyvwpsIc2Q/835kHuo3BEQ7CjelGhfTsoBb2MQ==} - engines: {node: '>= 0.4'} - - typed-array-byte-length@1.0.1: - resolution: {integrity: sha512-3iMJ9q0ao7WE9tWcaYKIptkNBuOIcZCCT0d4MRvuuH88fEoEH62IuQe0OtraD3ebQEoTRk8XCBoknUNc1Y67pw==} - engines: {node: '>= 0.4'} - - typed-array-byte-offset@1.0.2: - resolution: {integrity: sha512-Ous0vodHa56FviZucS2E63zkgtgrACj7omjwd/8lTEMEPFFyjfixMZ1ZXenpgCFBBt4EC1J2XsyVS2gkG0eTFA==} - engines: {node: '>= 0.4'} - - typed-array-length@1.0.6: - resolution: {integrity: sha512-/OxDN6OtAk5KBpGb28T+HZc2M+ADtvRxXrKKbUwtsLgdoxgX13hyy7ek6bFRl5+aBs2yZzB0c4CnQfAtVypW/g==} - engines: {node: '>= 0.4'} - - typedarray-to-buffer@3.1.5: - resolution: {integrity: sha512-zdu8XMNEDepKKR+XYOXAVPtWui0ly0NtohUscw+UmaHiAWT8hrV1rr//H6V+0DvJ3OQ19S979M0laLfX8rm82Q==} - - typescript@5.5.4: - resolution: {integrity: sha512-Mtq29sKDAEYP7aljRgtPOpTvOfbwRWlS6dPRzwjdE+C0R4brX/GUyhHSecbHMFLNBLcJIPt9nl9yG5TZ1weH+Q==} - engines: {node: '>=14.17'} - hasBin: true - - typesense-docsearch-css@0.3.0: - resolution: {integrity: sha512-+/t9Jz5dwH52Xpk9ikpJaQZs+McX/a4aY+8Iw+IiD9yu9+JJddEA5RYjBgkcQ140gUtp9L213z/V0g2bC3B/hw==} - - typesense-docsearch-react@0.2.3: - resolution: {integrity: sha512-2eODhYFk3KLhwEF+shzcTsiB0zU8GefPFZGzNlGdwdUJiUxjh8SgS7VtylXGdKQZxh33wbWN4wr94CG2WxcIIw==} - peerDependencies: - '@types/react': '>= 16.8.0 < 19.0.0' - react: '>= 16.8.0 < 19.0.0' - react-dom: '>= 16.8.0 < 19.0.0' - - typesense-instantsearch-adapter@2.8.0: - resolution: {integrity: sha512-2q4QVpHoUV0ncf1XOqIC0dufOTkFRxQ0mHzg//H3WK02ZYqdNNPCAacZODhQlltl1cNJdTI8Y4uuGVd6fJuGzw==} - engines: {node: '>=16'} - peerDependencies: - '@babel/runtime': ^7.17.2 - - typesense@1.8.2: - resolution: {integrity: sha512-aBpePjA99Qvo+OP2pJwMpvga4Jrm1Y2oV5NsrWXBxlqUDNEUCPZBIksPv2Hq0jxQxHhLLyJVbjXjByXsvpCDVA==} - engines: {node: '>=18'} - peerDependencies: - '@babel/runtime': ^7.23.2 - - ua-parser-js@1.0.38: - resolution: {integrity: sha512-Aq5ppTOfvrCMgAPneW1HfWj66Xi7XL+/mIy996R1/CLS/rcyJQm6QZdsKrUeivDFQ+Oc9Wyuwor8Ze8peEoUoQ==} - - uc.micro@1.0.6: - resolution: {integrity: sha512-8Y75pvTYkLJW2hWQHXxoqRgV7qb9B+9vFEtidML+7koHUFapnVJAZ6cKs+Qjz5Aw3aZWHMC6u0wJE3At+nSGwA==} - - unbox-primitive@1.0.2: - resolution: {integrity: sha512-61pPlCD9h51VoreyJ0BReideM3MDKMKnh6+V9L08331ipq6Q8OFXZYiqP6n/tbHx4s5I9uRhcye6BrbkizkBDw==} - - undici-types@6.19.8: - resolution: {integrity: sha512-ve2KP6f/JnbPBFyobGHuerC9g1FYGn/F8n1LWTwNxCEzd6IfqTwUQcNXgEtmmQ6DlRrC1hrSrBnCZPokRrDHjw==} - - undici@6.19.8: - resolution: {integrity: sha512-U8uCCl2x9TK3WANvmBavymRzxbfFYG+tAu+fgx3zxQy3qdagQqBLwJVrdyO1TBfUXvfKveMKJZhpvUYoOjM+4g==} - engines: {node: '>=18.17'} - - unherit@1.1.3: - resolution: {integrity: sha512-Ft16BJcnapDKp0+J/rqFC3Rrk6Y/Ng4nzsC028k2jdDII/rdZ7Wd3pPT/6+vIIxRagwRc9K0IUX0Ra4fKvw+WQ==} - - unicode-canonical-property-names-ecmascript@2.0.0: - resolution: {integrity: sha512-yY5PpDlfVIU5+y/BSCxAJRBIS1Zc2dDG3Ujq+sR0U+JjUevW2JhocOF+soROYDSaAezOzOKuyyixhD6mBknSmQ==} - engines: {node: '>=4'} - - unicode-match-property-ecmascript@2.0.0: - resolution: {integrity: sha512-5kaZCrbp5mmbz5ulBkDkbY0SsPOjKqVS35VpL9ulMPfSl0J0Xsm+9Evphv9CoIZFwre7aJoa94AY6seMKGVN5Q==} - engines: {node: '>=4'} - - unicode-match-property-value-ecmascript@2.1.0: - resolution: {integrity: sha512-qxkjQt6qjg/mYscYMC0XKRn3Rh0wFPlfxB0xkt9CfyTvpX1Ra0+rAmdX2QyAobptSEvuy4RtpPRui6XkV+8wjA==} - engines: {node: '>=4'} - - unicode-property-aliases-ecmascript@2.1.0: - resolution: {integrity: sha512-6t3foTQI9qne+OZoVQB/8x8rk2k1eVy1gRXhV3oFQ5T6R1dqQ1xtin3XqSlx3+ATBkliTaR/hHyJBm+LVPNM8w==} - engines: {node: '>=4'} - - unified@9.2.0: - resolution: {integrity: sha512-vx2Z0vY+a3YoTj8+pttM3tiJHCwY5UFbYdiWrwBEbHmK8pvsPj2rtAX2BFfgXen8T39CJWblWRDT4L5WGXtDdg==} - - unified@9.2.2: - resolution: {integrity: sha512-Sg7j110mtefBD+qunSLO1lqOEKdrwBFBrR6Qd8f4uwkhWNlbkaqwHse6e7QvD3AP/MNoJdEDLaf8OxYyoWgorQ==} - - unique-string@2.0.0: - resolution: {integrity: sha512-uNaeirEPvpZWSgzwsPGtU2zVSTrn/8L5q/IexZmH0eH6SA73CmAA5U4GwORTxQAZs95TAXLNqeLoPPNO5gZfWg==} - engines: {node: '>=8'} - - unist-builder@2.0.3: - resolution: {integrity: sha512-f98yt5pnlMWlzP539tPc4grGMsFaQQlP/vM396b00jngsiINumNmsY8rkXjfoi1c6QaM8nQ3vaGDuoKWbe/1Uw==} - - unist-util-generated@1.1.6: - resolution: {integrity: sha512-cln2Mm1/CZzN5ttGK7vkoGw+RZ8VcUH6BtGbq98DDtRGquAAOXig1mrBQYelOwMXYS8rK+vZDyyojSjp7JX+Lg==} - - unist-util-is@4.1.0: - resolution: {integrity: sha512-ZOQSsnce92GrxSqlnEEseX0gi7GH9zTJZ0p9dtu87WRb/37mMPO2Ilx1s/t9vBHrFhbgweUwb+t7cIn5dxPhZg==} - - unist-util-position@3.1.0: - resolution: {integrity: sha512-w+PkwCbYSFw8vpgWD0v7zRCl1FpY3fjDSQ3/N/wNd9Ffa4gPi8+4keqt99N3XW6F99t/mUzp2xAhNmfKWp95QA==} - - unist-util-remove-position@2.0.1: - resolution: {integrity: sha512-fDZsLYIe2uT+oGFnuZmy73K6ZxOPG/Qcm+w7jbEjaFcJgbQ6cqjs/eSPzXhsmGpAsWPkqZM9pYjww5QTn3LHMA==} - - unist-util-remove@2.1.0: - resolution: {integrity: sha512-J8NYPyBm4baYLdCbjmf1bhPu45Cr1MWTm77qd9istEkzWpnN6O9tMsEbB2JhNnBCqGENRqEWomQ+He6au0B27Q==} - - unist-util-stringify-position@2.0.3: - resolution: {integrity: sha512-3faScn5I+hy9VleOq/qNbAd6pAx7iH5jYBMS9I1HgQVijz/4mv5Bvw5iw1sC/90CODiKo81G/ps8AJrISn687g==} - - unist-util-visit-parents@3.1.1: - resolution: {integrity: sha512-1KROIZWo6bcMrZEwiH2UrXDyalAa0uqzWCxCJj6lPOvTve2WkfgCytoDTPaMnodXh1WrXOq0haVYHj99ynJlsg==} - - unist-util-visit@2.0.3: - resolution: {integrity: sha512-iJ4/RczbJMkD0712mGktuGpm/U4By4FfDonL7N/9tATGIF4imikjOuagyMY53tnZq3NP6BcmlrHhEKAfGWjh7Q==} - - universalify@2.0.1: - resolution: {integrity: sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==} - engines: {node: '>= 10.0.0'} - - unpipe@1.0.0: - resolution: {integrity: sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ==} - engines: {node: '>= 0.8'} - - unquote@1.1.1: - resolution: {integrity: sha512-vRCqFv6UhXpWxZPyGDh/F3ZpNv8/qo7w6iufLpQg9aKnQ71qM4B5KiI7Mia9COcjEhrO9LueHpMYjYzsWH3OIg==} - - update-browserslist-db@1.1.0: - resolution: {integrity: sha512-EdRAaAyk2cUE1wOf2DkEhzxqOQvFOoRJFNS6NeyJ01Gp2beMRpBAINjM2iDXE3KCuKhwnvHIQCJm6ThL2Z+HzQ==} - hasBin: true - peerDependencies: - browserslist: '>= 4.21.0' - - update-notifier@5.1.0: - resolution: {integrity: sha512-ItnICHbeMh9GqUy31hFPrD1kcuZ3rpxDZbf4KUDavXwS0bW5m7SLbDQpGX3UYr072cbrF5hFUs3r5tUsPwjfHw==} - engines: {node: '>=10'} - - uri-js@4.4.1: - resolution: {integrity: sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==} - - url-loader@4.1.1: - resolution: {integrity: sha512-3BTV812+AVHHOJQO8O5MkWgZ5aosP7GnROJwvzLS9hWDj00lZ6Z0wNak423Lp9PBZN05N+Jk/N5Si8jRAlGyWA==} - engines: {node: '>= 10.13.0'} - peerDependencies: - file-loader: '*' - webpack: ^4.0.0 || ^5.0.0 - peerDependenciesMeta: - file-loader: - optional: true - - url-parse-lax@3.0.0: - resolution: {integrity: sha512-NjFKA0DidqPa5ciFcSrXnAltTtzz84ogy+NebPvfEgAck0+TNg4UJ4IN+fB7zRZfbgUf0syOo9MDxFkDSMuFaQ==} - engines: {node: '>=4'} - - use-composed-ref@1.3.0: - resolution: {integrity: sha512-GLMG0Jc/jiKov/3Ulid1wbv3r54K9HlMW29IWcDFPEqFkSO2nS0MuefWgMJpeHQ9YJeXDL3ZUF+P3jdXlZX/cQ==} - peerDependencies: - react: ^16.8.0 || ^17.0.0 || ^18.0.0 - - use-isomorphic-layout-effect@1.1.2: - resolution: {integrity: sha512-49L8yCO3iGT/ZF9QttjwLF/ZD9Iwto5LnH5LmEdk/6cFmXddqi2ulF0edxTwjj+7mqvpVVGQWvbXZdn32wRSHA==} - peerDependencies: - '@types/react': '*' - react: ^16.8.0 || ^17.0.0 || ^18.0.0 - peerDependenciesMeta: - '@types/react': - optional: true - - use-latest@1.2.1: - resolution: {integrity: sha512-xA+AVm/Wlg3e2P/JiItTziwS7FK92LWrDB0p+hgXloIMuVCeJJ8v6f0eeHyPZaJrM+usM1FkFfbNCrJGs8A/zw==} - peerDependencies: - '@types/react': '*' - react: ^16.8.0 || ^17.0.0 || ^18.0.0 - peerDependenciesMeta: - '@types/react': - optional: true - - util-deprecate@1.0.2: - resolution: {integrity: sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==} - - util.promisify@1.0.1: - resolution: {integrity: sha512-g9JpC/3He3bm38zsLupWryXHoEcS22YHthuPQSJdMy6KNrzIRzWqcsHzD/WUnqe45whVou4VIsPew37DoXWNrA==} - - utila@0.4.0: - resolution: {integrity: sha512-Z0DbgELS9/L/75wZbro8xAnT50pBVFQZ+hUEueGDU5FN51YSCYM+jdxsfCiHjwNP/4LCDD0i/graKpeBnOXKRA==} - - utility-types@3.11.0: - resolution: {integrity: sha512-6Z7Ma2aVEWisaL6TvBCy7P8rm2LQoPv6dJ7ecIaIixHcwfbJ0x7mWdbcwlIM5IGQxPZSFYeqRCqlOOeKoJYMkw==} - engines: {node: '>= 4'} - - utils-merge@1.0.1: - resolution: {integrity: sha512-pMZTvIkT1d+TFGvDOqodOclx0QWkkgi6Tdoa8gC8ffGAAqz9pzPTZWAybbsHHoED/ztMtkv/VoYTYyShUn81hA==} - engines: {node: '>= 0.4.0'} - - uuid@8.3.2: - resolution: {integrity: sha512-+NYs2QeMWy+GWFOEm9xnn6HCDp0l7QBD7ml8zLUmJ+93Q5NF0NocErnwkTkXVFNiX3/fpC6afS8Dhb/gz7R7eg==} - hasBin: true - - value-equal@1.0.1: - resolution: {integrity: sha512-NOJ6JZCAWr0zlxZt+xqCHNTEKOsrks2HQd4MqhP1qy4z1SkbEP467eNx6TgDKXMvUOb+OENfJCZwM+16n7fRfw==} - - vary@1.1.2: - resolution: {integrity: sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg==} - engines: {node: '>= 0.8'} - - vfile-location@3.2.0: - resolution: {integrity: sha512-aLEIZKv/oxuCDZ8lkJGhuhztf/BW4M+iHdCwglA/eWc+vtuRFJj8EtgceYFX4LRjOhCAAiNHsKGssC6onJ+jbA==} - - vfile-message@2.0.4: - resolution: {integrity: sha512-DjssxRGkMvifUOJre00juHoP9DPWuzjxKuMDrhNbk2TdaYYBNMStsNhEOt3idrtI12VQYM/1+iM0KOzXi4pxwQ==} - - vfile@4.2.1: - resolution: {integrity: sha512-O6AE4OskCG5S1emQ/4gl8zK586RqA3srz3nfK/Viy0UPToBc5Trp9BVFb1u0CjsKrAWwnpr4ifM/KBXPWwJbCA==} - - wait-on@6.0.1: - resolution: {integrity: sha512-zht+KASY3usTY5u2LgaNqn/Cd8MukxLGjdcZxT2ns5QzDmTFc4XoWBgC+C/na+sMRZTuVygQoMYwdcVjHnYIVw==} - engines: {node: '>=10.0.0'} - hasBin: true - - watchpack@2.4.2: - resolution: {integrity: sha512-TnbFSbcOCcDgjZ4piURLCbJ3nJhznVh9kw6F6iokjiFPl8ONxe9A6nMDVXDiNbrSfLILs6vB07F7wLBrwPYzJw==} - engines: {node: '>=10.13.0'} - - wbuf@1.7.3: - resolution: {integrity: sha512-O84QOnr0icsbFGLS0O3bI5FswxzRr8/gHwWkDlQFskhSPryQXvrTMxjxGP4+iWYoauLoBvfDpkrOauZ+0iZpDA==} - - web-namespaces@1.1.4: - resolution: {integrity: sha512-wYxSGajtmoP4WxfejAPIr4l0fVh+jeMXZb08wNc0tMg6xsfZXj3cECqIK0G7ZAqUq0PP8WlMDtaOGVBTAWztNw==} - - webidl-conversions@3.0.1: - resolution: {integrity: sha512-2JAn3z8AR6rjK8Sm8orRC0h/bcl/DqL7tRPdGZ4I1CjdF+EaMLmYxBHyXuKL849eucPFhvBoxMsflfOb8kxaeQ==} - - webpack-bundle-analyzer@4.10.2: - resolution: {integrity: sha512-vJptkMm9pk5si4Bv922ZbKLV8UTT4zib4FPgXMhgzUny0bfDDkLXAVQs3ly3fS4/TN9ROFtb0NFrm04UXFE/Vw==} - engines: {node: '>= 10.13.0'} - hasBin: true - - webpack-dev-middleware@5.3.4: - resolution: {integrity: sha512-BVdTqhhs+0IfoeAf7EoH5WE+exCmqGerHfDM0IL096Px60Tq2Mn9MAbnaGUe6HiMa41KMCYF19gyzZmBcq/o4Q==} - engines: {node: '>= 12.13.0'} - peerDependencies: - webpack: ^4.0.0 || ^5.0.0 - - webpack-dev-server@4.15.2: - resolution: {integrity: sha512-0XavAZbNJ5sDrCbkpWL8mia0o5WPOd2YGtxrEiZkBK9FjLppIUK2TgxK6qGD2P3hUXTJNNPVibrerKcx5WkR1g==} - engines: {node: '>= 12.13.0'} - hasBin: true - peerDependencies: - webpack: ^4.37.0 || ^5.0.0 - webpack-cli: '*' - peerDependenciesMeta: - webpack: - optional: true - webpack-cli: - optional: true - - webpack-merge@5.10.0: - resolution: {integrity: sha512-+4zXKdx7UnO+1jaN4l2lHVD+mFvnlZQP/6ljaJVb4SZiwIKeUnrT5l0gkT8z+n4hKpC+jpOv6O9R+gLtag7pSA==} - engines: {node: '>=10.0.0'} - - webpack-sources@3.2.3: - resolution: {integrity: sha512-/DyMEOrDgLKKIG0fmvtz+4dUX/3Ghozwgm6iPp8KRhvn+eQf9+Q7GWxVNMk3+uCPWfdXYC4ExGBckIXdFEfH1w==} - engines: {node: '>=10.13.0'} - - webpack@5.94.0: - resolution: {integrity: sha512-KcsGn50VT+06JH/iunZJedYGUJS5FGjow8wb9c0v5n1Om8O1g4L6LjtfxwlXIATopoQu+vOXXa7gYisWxCoPyg==} - engines: {node: '>=10.13.0'} - hasBin: true - peerDependencies: - webpack-cli: '*' - peerDependenciesMeta: - webpack-cli: - optional: true - - webpackbar@5.0.2: - resolution: {integrity: sha512-BmFJo7veBDgQzfWXl/wwYXr/VFus0614qZ8i9znqcl9fnEdiVkdbi0TedLQ6xAK92HZHDJ0QmyQ0fmuZPAgCYQ==} - engines: {node: '>=12'} - peerDependencies: - webpack: 3 || 4 || 5 - - websocket-driver@0.7.4: - resolution: {integrity: sha512-b17KeDIQVjvb0ssuSDF2cYXSg2iztliJ4B9WdsuB6J952qCPKmnVq4DyW5motImXHDC1cBT/1UezrJVsKw5zjg==} - engines: {node: '>=0.8.0'} - - websocket-extensions@0.1.4: - resolution: {integrity: sha512-OqedPIGOfsDlo31UNwYbCFMSaO9m9G/0faIHj5/dZFDMFqPTcx6UwqyOy3COEaEOg/9VsGIpdqn62W5KhoKSpg==} - engines: {node: '>=0.8.0'} - - whatwg-encoding@3.1.1: - resolution: {integrity: sha512-6qN4hJdMwfYBtE3YBTTHhoeuUrDBPZmbQaxWAqSALV/MeEnR5z1xd8UKud2RAkFoPkmB+hli1TZSnyi84xz1vQ==} - engines: {node: '>=18'} - - whatwg-mimetype@4.0.0: - resolution: {integrity: sha512-QaKxh0eNIi2mE9p2vEdzfagOKHCcj1pJ56EEHGQOVxp8r9/iszLUUV7v89x9O1p/T+NlTM5W7jW6+cz4Fq1YVg==} - engines: {node: '>=18'} - - whatwg-url@5.0.0: - resolution: {integrity: sha512-saE57nupxk6v3HY35+jzBwYa0rKSy0XR8JSxZPwgLr7ys0IBzhGviA1/TUGJLmSVqs8pb9AnvICXEuOHLprYTw==} - - which-boxed-primitive@1.0.2: - resolution: {integrity: sha512-bwZdv0AKLpplFY2KZRX6TvyuN7ojjr7lwkg6ml0roIy9YeuSr7JS372qlNW18UQYzgYK9ziGcerWqZOmEn9VNg==} - - which-typed-array@1.1.15: - resolution: {integrity: sha512-oV0jmFtUky6CXfkqehVvBP/LSWJ2sy4vWMioiENyJLePrBO/yKyV9OyJySfAKosh+RYkIl5zJCNZ8/4JncrpdA==} - engines: {node: '>= 0.4'} - - which@1.3.1: - resolution: {integrity: sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==} - hasBin: true - - which@2.0.2: - resolution: {integrity: sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==} - engines: {node: '>= 8'} - hasBin: true - - widest-line@3.1.0: - resolution: {integrity: sha512-NsmoXalsWVDMGupxZ5R08ka9flZjjiLvHVAWYOKtiKM8ujtZWr9cRffak+uSE48+Ob8ObalXpwyeUiyDD6QFgg==} - engines: {node: '>=8'} - - widest-line@4.0.1: - resolution: {integrity: sha512-o0cyEG0e8GPzT4iGHphIOh0cJOV8fivsXxddQasHPHfoZf1ZexrfeA21w2NaEN1RHE+fXlfISmOE8R9N3u3Qig==} - engines: {node: '>=12'} - - wildcard@2.0.1: - resolution: {integrity: sha512-CC1bOL87PIWSBhDcTrdeLo6eGT7mCFtrg0uIJtqJUFyK+eJnzl8A1niH56uu7KMa5XFrtiV+AQuHO3n7DsHnLQ==} - - wrap-ansi@7.0.0: - resolution: {integrity: sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==} - engines: {node: '>=10'} - - wrap-ansi@8.1.0: - resolution: {integrity: sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ==} - engines: {node: '>=12'} - - wrappy@1.0.2: - resolution: {integrity: sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==} - - write-file-atomic@3.0.3: - resolution: {integrity: sha512-AvHcyZ5JnSfq3ioSyjrBkH9yW4m7Ayk8/9My/DD9onKeu/94fwrMocemO2QAJFAlnnDN+ZDS+ZjAR5ua1/PV/Q==} - - ws@7.5.10: - resolution: {integrity: sha512-+dbF1tHwZpXcbOJdVOkzLDxZP1ailvSxM6ZweXTegylPny803bFhA+vqBYw4s31NSAk4S2Qz+AKXK9a4wkdjcQ==} - engines: {node: '>=8.3.0'} - peerDependencies: - bufferutil: ^4.0.1 - utf-8-validate: ^5.0.2 - peerDependenciesMeta: - bufferutil: - optional: true - utf-8-validate: - optional: true - - ws@8.18.0: - resolution: {integrity: sha512-8VbfWfHLbbwu3+N6OKsOMpBdT4kXPDDB9cJk2bJ6mh9ucxdlnNvH1e+roYkKmN9Nxw2yjz7VzeO9oOz2zJ04Pw==} - engines: {node: '>=10.0.0'} - peerDependencies: - bufferutil: ^4.0.1 - utf-8-validate: '>=5.0.2' - peerDependenciesMeta: - bufferutil: - optional: true - utf-8-validate: - optional: true - - xdg-basedir@4.0.0: - resolution: {integrity: sha512-PSNhEJDejZYV7h50BohL09Er9VaIefr2LMAf3OEmpCkjOi34eYyQYAXUTjEQtZJTKcF0E2UKTh+osDLsgNim9Q==} - engines: {node: '>=8'} - - xml-js@1.6.11: - resolution: {integrity: sha512-7rVi2KMfwfWFl+GpPg6m80IVMWXLRjO+PxTq7V2CDhoGak0wzYzFgUY2m4XJ47OGdXd8eLE8EmwfAmdjw7lC1g==} - hasBin: true - - xtend@4.0.2: - resolution: {integrity: sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==} - engines: {node: '>=0.4'} - - yallist@3.1.1: - resolution: {integrity: sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==} - - yaml@1.10.2: - resolution: {integrity: sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg==} - engines: {node: '>= 6'} - - yauzl@2.10.0: - resolution: {integrity: sha512-p4a9I6X6nu6IhoGmBqAcbJy1mlC4j27vEPZX9F4L4/vZT3Lyq1VkFHw/V/PUcB9Buo+DG3iHkT0x3Qya58zc3g==} - - yocto-queue@0.1.0: - resolution: {integrity: sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==} - engines: {node: '>=10'} - - zwitch@1.0.5: - resolution: {integrity: sha512-V50KMwwzqJV0NpZIZFwfOD5/lyny3WlSzRiXgA0G7VUnRlqttta1L6UQIHzd6EuBY/cHGfwTIck7w1yH6Q5zUw==} +dependencies: + '@crowdin/cli': + specifier: 3.13.0 + version: 3.13.0 + '@docusaurus/core': + specifier: 2.2.0 + version: 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) + '@docusaurus/preset-classic': + specifier: 2.2.0 + version: 2.2.0(@algolia/client-search@4.24.0)(@swc/core@1.7.18)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(search-insights@2.17.0)(typescript@5.5.4) + '@mdx-js/react': + specifier: ^1.6.21 + version: 1.6.22(react@17.0.2) + '@svgr/webpack': + specifier: ^5.5.0 + version: 5.5.0 + '@swc/core': + specifier: ^1.7.18 + version: 1.7.18 + clsx: + specifier: ^1.1.1 + version: 1.2.1 + docusaurus-theme-search-typesense: + specifier: ^0.8.0 + version: 0.8.0(@algolia/client-search@4.24.0)(@babel/runtime@7.25.4)(@docusaurus/core@2.2.0)(@docusaurus/theme-common@2.2.0)(@swc/core@1.7.18)(@types/react@18.3.4)(algoliasearch@4.24.0)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) + file-loader: + specifier: ^6.2.0 + version: 6.2.0(webpack@5.94.0) + prism-react-renderer: + specifier: ^1.2.1 + version: 1.3.5(react@17.0.2) + react: + specifier: ^17.0.1 + version: 17.0.2 + react-dom: + specifier: ^17.0.1 + version: 17.0.2(react@17.0.2) + swc-loader: + specifier: ^0.2.6 + version: 0.2.6(@swc/core@1.7.18)(webpack@5.94.0) + url-loader: + specifier: ^4.1.1 + version: 4.1.1(file-loader@6.2.0)(webpack@5.94.0) + +devDependencies: + markdownlint: + specifier: ^0.29.0 + version: 0.29.0 + markdownlint-cli: + specifier: ^0.35.0 + version: 0.35.0 -snapshots: +packages: - '@algolia/autocomplete-core@1.7.1': + /@algolia/autocomplete-core@1.7.1: + resolution: {integrity: sha512-eiZw+fxMzNQn01S8dA/hcCpoWCOCwcIIEUtHHdzN5TGB3IpzLbuhqFeTfh2OUhhgkE8Uo17+wH+QJ/wYyQmmzg==} dependencies: '@algolia/autocomplete-shared': 1.7.1 + dev: false - '@algolia/autocomplete-core@1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.0)': + /@algolia/autocomplete-core@1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.0): + resolution: {integrity: sha512-009HdfugtGCdC4JdXUbVJClA0q0zh24yyePn+KUGk3rP7j8FEe/m5Yo/z65gn6nP/cM39PxpzqKrL7A6fP6PPw==} dependencies: '@algolia/autocomplete-plugin-algolia-insights': 1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.0) '@algolia/autocomplete-shared': 1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) @@ -5024,83 +73,128 @@ snapshots: - '@algolia/client-search' - algoliasearch - search-insights + dev: false - '@algolia/autocomplete-plugin-algolia-insights@1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.0)': + /@algolia/autocomplete-plugin-algolia-insights@1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.0): + resolution: {integrity: sha512-a/yTUkcO/Vyy+JffmAnTWbr4/90cLzw+CC3bRbhnULr/EM0fGNvM13oQQ14f2moLMcVDyAx/leczLlAOovhSZg==} + peerDependencies: + search-insights: '>= 1 < 3' dependencies: '@algolia/autocomplete-shared': 1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) search-insights: 2.17.0 transitivePeerDependencies: - '@algolia/client-search' - algoliasearch + dev: false - '@algolia/autocomplete-preset-algolia@1.7.1(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)': + /@algolia/autocomplete-preset-algolia@1.7.1(@algolia/client-search@4.24.0)(algoliasearch@4.24.0): + resolution: {integrity: sha512-pJwmIxeJCymU1M6cGujnaIYcY3QPOVYZOXhFkWVM7IxKzy272BwCvMFMyc5NpG/QmiObBxjo7myd060OeTNJXg==} + peerDependencies: + '@algolia/client-search': ^4.9.1 + algoliasearch: ^4.9.1 dependencies: '@algolia/autocomplete-shared': 1.7.1 '@algolia/client-search': 4.24.0 algoliasearch: 4.24.0 + dev: false - '@algolia/autocomplete-preset-algolia@1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)': + /@algolia/autocomplete-preset-algolia@1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0): + resolution: {integrity: sha512-d4qlt6YmrLMYy95n5TB52wtNDr6EgAIPH81dvvvW8UmuWRgxEtY0NJiPwl/h95JtG2vmRM804M0DSwMCNZlzRA==} + peerDependencies: + '@algolia/client-search': '>= 4.9.1 < 6' + algoliasearch: '>= 4.9.1 < 6' dependencies: '@algolia/autocomplete-shared': 1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) '@algolia/client-search': 4.24.0 algoliasearch: 4.24.0 + dev: false - '@algolia/autocomplete-shared@1.7.1': {} + /@algolia/autocomplete-shared@1.7.1: + resolution: {integrity: sha512-eTmGVqY3GeyBTT8IWiB2K5EuURAqhnumfktAEoHxfDY2o7vg2rSnO16ZtIG0fMgt3py28Vwgq42/bVEuaQV7pg==} + dev: false - '@algolia/autocomplete-shared@1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)': + /@algolia/autocomplete-shared@1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0): + resolution: {integrity: sha512-Wnm9E4Ye6Rl6sTTqjoymD+l8DjSTHsHboVRYrKgEt8Q7UHm9nYbqhN/i0fhUYA3OAEH7WA8x3jfpnmJm3rKvaQ==} + peerDependencies: + '@algolia/client-search': '>= 4.9.1 < 6' + algoliasearch: '>= 4.9.1 < 6' dependencies: '@algolia/client-search': 4.24.0 algoliasearch: 4.24.0 + dev: false - '@algolia/cache-browser-local-storage@4.24.0': + /@algolia/cache-browser-local-storage@4.24.0: + resolution: {integrity: sha512-t63W9BnoXVrGy9iYHBgObNXqYXM3tYXCjDSHeNwnsc324r4o5UiVKUiAB4THQ5z9U5hTj6qUvwg/Ez43ZD85ww==} dependencies: '@algolia/cache-common': 4.24.0 + dev: false - '@algolia/cache-common@4.24.0': {} + /@algolia/cache-common@4.24.0: + resolution: {integrity: sha512-emi+v+DmVLpMGhp0V9q9h5CdkURsNmFC+cOS6uK9ndeJm9J4TiqSvPYVu+THUP8P/S08rxf5x2P+p3CfID0Y4g==} + dev: false - '@algolia/cache-in-memory@4.24.0': + /@algolia/cache-in-memory@4.24.0: + resolution: {integrity: sha512-gDrt2so19jW26jY3/MkFg5mEypFIPbPoXsQGQWAi6TrCPsNOSEYepBMPlucqWigsmEy/prp5ug2jy/N3PVG/8w==} dependencies: '@algolia/cache-common': 4.24.0 + dev: false - '@algolia/client-account@4.24.0': + /@algolia/client-account@4.24.0: + resolution: {integrity: sha512-adcvyJ3KjPZFDybxlqnf+5KgxJtBjwTPTeyG2aOyoJvx0Y8dUQAEOEVOJ/GBxX0WWNbmaSrhDURMhc+QeevDsA==} dependencies: '@algolia/client-common': 4.24.0 '@algolia/client-search': 4.24.0 '@algolia/transporter': 4.24.0 + dev: false - '@algolia/client-analytics@4.24.0': + /@algolia/client-analytics@4.24.0: + resolution: {integrity: sha512-y8jOZt1OjwWU4N2qr8G4AxXAzaa8DBvyHTWlHzX/7Me1LX8OayfgHexqrsL4vSBcoMmVw2XnVW9MhL+Y2ZDJXg==} dependencies: '@algolia/client-common': 4.24.0 '@algolia/client-search': 4.24.0 '@algolia/requester-common': 4.24.0 '@algolia/transporter': 4.24.0 + dev: false - '@algolia/client-common@4.24.0': + /@algolia/client-common@4.24.0: + resolution: {integrity: sha512-bc2ROsNL6w6rqpl5jj/UywlIYC21TwSSoFHKl01lYirGMW+9Eek6r02Tocg4gZ8HAw3iBvu6XQiM3BEbmEMoiA==} dependencies: '@algolia/requester-common': 4.24.0 '@algolia/transporter': 4.24.0 + dev: false - '@algolia/client-personalization@4.24.0': + /@algolia/client-personalization@4.24.0: + resolution: {integrity: sha512-l5FRFm/yngztweU0HdUzz1rC4yoWCFo3IF+dVIVTfEPg906eZg5BOd1k0K6rZx5JzyyoP4LdmOikfkfGsKVE9w==} dependencies: '@algolia/client-common': 4.24.0 '@algolia/requester-common': 4.24.0 '@algolia/transporter': 4.24.0 + dev: false - '@algolia/client-search@4.24.0': + /@algolia/client-search@4.24.0: + resolution: {integrity: sha512-uRW6EpNapmLAD0mW47OXqTP8eiIx5F6qN9/x/7HHO6owL3N1IXqydGwW5nhDFBrV+ldouro2W1VX3XlcUXEFCA==} dependencies: '@algolia/client-common': 4.24.0 '@algolia/requester-common': 4.24.0 '@algolia/transporter': 4.24.0 + dev: false - '@algolia/events@4.0.1': {} + /@algolia/events@4.0.1: + resolution: {integrity: sha512-FQzvOCgoFXAbf5Y6mYozw2aj5KCJoA3m4heImceldzPSMbdyS4atVjJzXKMsfX3wnZTFYwkkt8/z8UesLHlSBQ==} + dev: false - '@algolia/logger-common@4.24.0': {} + /@algolia/logger-common@4.24.0: + resolution: {integrity: sha512-LLUNjkahj9KtKYrQhFKCzMx0BY3RnNP4FEtO+sBybCjJ73E8jNdaKJ/Dd8A/VA4imVHP5tADZ8pn5B8Ga/wTMA==} + dev: false - '@algolia/logger-console@4.24.0': + /@algolia/logger-console@4.24.0: + resolution: {integrity: sha512-X4C8IoHgHfiUROfoRCV+lzSy+LHMgkoEEU1BbKcsfnV0i0S20zyy0NLww9dwVHUWNfPPxdMU+/wKmLGYf96yTg==} dependencies: '@algolia/logger-common': 4.24.0 + dev: false - '@algolia/recommend@4.24.0': + /@algolia/recommend@4.24.0: + resolution: {integrity: sha512-P9kcgerfVBpfYHDfVZDvvdJv0lEoCvzNlOy2nykyt5bK8TyieYyiD0lguIJdRZZYGre03WIAFf14pgE+V+IBlw==} dependencies: '@algolia/cache-browser-local-storage': 4.24.0 '@algolia/cache-common': 4.24.0 @@ -5113,36 +207,56 @@ snapshots: '@algolia/requester-common': 4.24.0 '@algolia/requester-node-http': 4.24.0 '@algolia/transporter': 4.24.0 + dev: false - '@algolia/requester-browser-xhr@4.24.0': + /@algolia/requester-browser-xhr@4.24.0: + resolution: {integrity: sha512-Z2NxZMb6+nVXSjF13YpjYTdvV3032YTBSGm2vnYvYPA6mMxzM3v5rsCiSspndn9rzIW4Qp1lPHBvuoKJV6jnAA==} dependencies: '@algolia/requester-common': 4.24.0 + dev: false - '@algolia/requester-common@4.24.0': {} + /@algolia/requester-common@4.24.0: + resolution: {integrity: sha512-k3CXJ2OVnvgE3HMwcojpvY6d9kgKMPRxs/kVohrwF5WMr2fnqojnycZkxPoEg+bXm8fi5BBfFmOqgYztRtHsQA==} + dev: false - '@algolia/requester-node-http@4.24.0': + /@algolia/requester-node-http@4.24.0: + resolution: {integrity: sha512-JF18yTjNOVYvU/L3UosRcvbPMGT9B+/GQWNWnenIImglzNVGpyzChkXLnrSf6uxwVNO6ESGu6oN8MqcGQcjQJw==} dependencies: '@algolia/requester-common': 4.24.0 + dev: false - '@algolia/transporter@4.24.0': + /@algolia/transporter@4.24.0: + resolution: {integrity: sha512-86nI7w6NzWxd1Zp9q3413dRshDqAzSbsQjhcDhPIatEFiZrL1/TjnHL8S7jVKFePlIMzDsZWXAXwXzcok9c5oA==} dependencies: '@algolia/cache-common': 4.24.0 '@algolia/logger-common': 4.24.0 '@algolia/requester-common': 4.24.0 + dev: false - '@ampproject/remapping@2.3.0': + /@ampproject/remapping@2.3.0: + resolution: {integrity: sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw==} + engines: {node: '>=6.0.0'} dependencies: '@jridgewell/gen-mapping': 0.3.5 '@jridgewell/trace-mapping': 0.3.25 + dev: false - '@babel/code-frame@7.24.7': + /@babel/code-frame@7.24.7: + resolution: {integrity: sha512-BcYH1CVJBO9tvyIZ2jVeXgSIMvGZ2FDRvDdOIVQyuklNKSsx+eppDEBq/g47Ayw+RqNFE+URvOShmf+f/qwAlA==} + engines: {node: '>=6.9.0'} dependencies: '@babel/highlight': 7.24.7 picocolors: 1.0.1 + dev: false - '@babel/compat-data@7.25.4': {} + /@babel/compat-data@7.25.4: + resolution: {integrity: sha512-+LGRog6RAsCJrrrg/IO6LGmpphNe5DiK30dGjCoxxeGv49B10/3XYGxPsAwrDlMFcFEvdAUavDT8r9k/hSyQqQ==} + engines: {node: '>=6.9.0'} + dev: false - '@babel/core@7.12.9': + /@babel/core@7.12.9: + resolution: {integrity: sha512-gTXYh3M5wb7FRXQy+FErKFAv90BnlOuNn1QkCK2lREoPAjrQCO49+HVSrFoe5uakFAF5eenS75KbO2vQiLrTMQ==} + engines: {node: '>=6.9.0'} dependencies: '@babel/code-frame': 7.24.7 '@babel/generator': 7.25.5 @@ -5162,8 +276,11 @@ snapshots: source-map: 0.5.7 transitivePeerDependencies: - supports-color + dev: false - '@babel/core@7.25.2': + /@babel/core@7.25.2: + resolution: {integrity: sha512-BBt3opiCOxUr9euZ5/ro/Xv8/V7yJ5bjYMqG/C1YAo8MIKAnumZalCN+msbci3Pigy4lIQfPUpfMM27HMGaYEA==} + engines: {node: '>=6.9.0'} dependencies: '@ampproject/remapping': 2.3.0 '@babel/code-frame': 7.24.7 @@ -5182,34 +299,51 @@ snapshots: semver: 6.3.1 transitivePeerDependencies: - supports-color + dev: false - '@babel/generator@7.25.5': + /@babel/generator@7.25.5: + resolution: {integrity: sha512-abd43wyLfbWoxC6ahM8xTkqLpGB2iWBVyuKC9/srhFunCd1SDNrV1s72bBpK4hLj8KLzHBBcOblvLQZBNw9r3w==} + engines: {node: '>=6.9.0'} dependencies: '@babel/types': 7.25.4 '@jridgewell/gen-mapping': 0.3.5 '@jridgewell/trace-mapping': 0.3.25 jsesc: 2.5.2 + dev: false - '@babel/helper-annotate-as-pure@7.24.7': + /@babel/helper-annotate-as-pure@7.24.7: + resolution: {integrity: sha512-BaDeOonYvhdKw+JoMVkAixAAJzG2jVPIwWoKBPdYuY9b452e2rPuI9QPYh3KpofZ3pW2akOmwZLOiOsHMiqRAg==} + engines: {node: '>=6.9.0'} dependencies: '@babel/types': 7.25.4 + dev: false - '@babel/helper-builder-binary-assignment-operator-visitor@7.24.7': + /@babel/helper-builder-binary-assignment-operator-visitor@7.24.7: + resolution: {integrity: sha512-xZeCVVdwb4MsDBkkyZ64tReWYrLRHlMN72vP7Bdm3OUOuyFZExhsHUUnuWnm2/XOlAJzR0LfPpB56WXZn0X/lA==} + engines: {node: '>=6.9.0'} dependencies: '@babel/traverse': 7.25.4 '@babel/types': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-compilation-targets@7.25.2': + /@babel/helper-compilation-targets@7.25.2: + resolution: {integrity: sha512-U2U5LsSaZ7TAt3cfaymQ8WHh0pxvdHoEk6HVpaexxixjyEquMh0L0YNJNM6CTGKMXV1iksi0iZkGw4AcFkPaaw==} + engines: {node: '>=6.9.0'} dependencies: '@babel/compat-data': 7.25.4 '@babel/helper-validator-option': 7.24.8 browserslist: 4.23.3 lru-cache: 5.1.1 semver: 6.3.1 + dev: false - '@babel/helper-create-class-features-plugin@7.25.4(@babel/core@7.25.2)': + /@babel/helper-create-class-features-plugin@7.25.4(@babel/core@7.25.2): + resolution: {integrity: sha512-ro/bFs3/84MDgDmMwbcHgDa8/E6J3QKNTk4xJJnVeFtGE+tL0K26E3pNxhYz2b67fJpt7Aphw5XcploKXuCvCQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-annotate-as-pure': 7.24.7 @@ -5221,15 +355,24 @@ snapshots: semver: 6.3.1 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-create-regexp-features-plugin@7.25.2(@babel/core@7.25.2)': + /@babel/helper-create-regexp-features-plugin@7.25.2(@babel/core@7.25.2): + resolution: {integrity: sha512-+wqVGP+DFmqwFD3EH6TMTfUNeqDehV3E/dl+Sd54eaXqm17tEUNbEIn4sVivVowbvUpOtIGxdo3GoXyDH9N/9g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-annotate-as-pure': 7.24.7 regexpu-core: 5.3.2 semver: 6.3.1 + dev: false - '@babel/helper-define-polyfill-provider@0.6.2(@babel/core@7.25.2)': + /@babel/helper-define-polyfill-provider@0.6.2(@babel/core@7.25.2): + resolution: {integrity: sha512-LV76g+C502biUK6AyZ3LK10vDpDyCzZnhZFXkH1L75zHPj68+qc8Zfpx2th+gzwA2MzyK+1g/3EPl62yFnVttQ==} + peerDependencies: + '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-compilation-targets': 7.25.2 @@ -5239,22 +382,33 @@ snapshots: resolve: 1.22.8 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-member-expression-to-functions@7.24.8': + /@babel/helper-member-expression-to-functions@7.24.8: + resolution: {integrity: sha512-LABppdt+Lp/RlBxqrh4qgf1oEH/WxdzQNDJIu5gC/W1GyvPVrOBiItmmM8wan2fm4oYqFuFfkXmlGpLQhPY8CA==} + engines: {node: '>=6.9.0'} dependencies: '@babel/traverse': 7.25.4 '@babel/types': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-module-imports@7.24.7': + /@babel/helper-module-imports@7.24.7: + resolution: {integrity: sha512-8AyH3C+74cgCVVXow/myrynrAGv+nTVg5vKu2nZph9x7RcRwzmh0VFallJuFTZ9mx6u4eSdXZfcOzSqTUm0HCA==} + engines: {node: '>=6.9.0'} dependencies: '@babel/traverse': 7.25.4 '@babel/types': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-module-transforms@7.25.2(@babel/core@7.12.9)': + /@babel/helper-module-transforms@7.25.2(@babel/core@7.12.9): + resolution: {integrity: sha512-BjyRAbix6j/wv83ftcVJmBt72QtHI56C7JXZoG2xATiLpmoC7dpd8WnkikExHDVPpi/3qCmO6WY1EaXOluiecQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.12.9 '@babel/helper-module-imports': 7.24.7 @@ -5263,8 +417,13 @@ snapshots: '@babel/traverse': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-module-transforms@7.25.2(@babel/core@7.25.2)': + /@babel/helper-module-transforms@7.25.2(@babel/core@7.25.2): + resolution: {integrity: sha512-BjyRAbix6j/wv83ftcVJmBt72QtHI56C7JXZoG2xATiLpmoC7dpd8WnkikExHDVPpi/3qCmO6WY1EaXOluiecQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-module-imports': 7.24.7 @@ -5273,16 +432,29 @@ snapshots: '@babel/traverse': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-optimise-call-expression@7.24.7': + /@babel/helper-optimise-call-expression@7.24.7: + resolution: {integrity: sha512-jKiTsW2xmWwxT1ixIdfXUZp+P5yURx2suzLZr5Hi64rURpDYdMW0pv+Uf17EYk2Rd428Lx4tLsnjGJzYKDM/6A==} + engines: {node: '>=6.9.0'} dependencies: '@babel/types': 7.25.4 + dev: false - '@babel/helper-plugin-utils@7.10.4': {} + /@babel/helper-plugin-utils@7.10.4: + resolution: {integrity: sha512-O4KCvQA6lLiMU9l2eawBPMf1xPP8xPfB3iEQw150hOVTqj/rfXz0ThTb4HEzqQfs2Bmo5Ay8BzxfzVtBrr9dVg==} + dev: false - '@babel/helper-plugin-utils@7.24.8': {} + /@babel/helper-plugin-utils@7.24.8: + resolution: {integrity: sha512-FFWx5142D8h2Mgr/iPVGH5G7w6jDn4jUSpZTyDnQO0Yn7Ks2Kuz6Pci8H6MPCoUJegd/UZQ3tAvfLCxQSnWWwg==} + engines: {node: '>=6.9.0'} + dev: false - '@babel/helper-remap-async-to-generator@7.25.0(@babel/core@7.25.2)': + /@babel/helper-remap-async-to-generator@7.25.0(@babel/core@7.25.2): + resolution: {integrity: sha512-NhavI2eWEIz/H9dbrG0TuOicDhNexze43i5z7lEqwYm0WEZVTwnPpA0EafUTP7+6/W79HWIP2cTe3Z5NiSTVpw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-annotate-as-pure': 7.24.7 @@ -5290,8 +462,13 @@ snapshots: '@babel/traverse': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-replace-supers@7.25.0(@babel/core@7.25.2)': + /@babel/helper-replace-supers@7.25.0(@babel/core@7.25.2): + resolution: {integrity: sha512-q688zIvQVYtZu+i2PsdIu/uWGRpfxzr5WESsfpShfZECkO+d2o+WROWezCi/Q6kJ0tfPa5+pUGUlfx2HhrA3Bg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-member-expression-to-functions': 7.24.8 @@ -5299,70 +476,118 @@ snapshots: '@babel/traverse': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-simple-access@7.24.7': + /@babel/helper-simple-access@7.24.7: + resolution: {integrity: sha512-zBAIvbCMh5Ts+b86r/CjU+4XGYIs+R1j951gxI3KmmxBMhCg4oQMsv6ZXQ64XOm/cvzfU1FmoCyt6+owc5QMYg==} + engines: {node: '>=6.9.0'} dependencies: '@babel/traverse': 7.25.4 '@babel/types': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-skip-transparent-expression-wrappers@7.24.7': + /@babel/helper-skip-transparent-expression-wrappers@7.24.7: + resolution: {integrity: sha512-IO+DLT3LQUElMbpzlatRASEyQtfhSE0+m465v++3jyyXeBTBUjtVZg28/gHeV5mrTJqvEKhKroBGAvhW+qPHiQ==} + engines: {node: '>=6.9.0'} dependencies: '@babel/traverse': 7.25.4 '@babel/types': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helper-string-parser@7.24.8': {} + /@babel/helper-string-parser@7.24.8: + resolution: {integrity: sha512-pO9KhhRcuUyGnJWwyEgnRJTSIZHiT+vMD0kPeD+so0l7mxkMT19g3pjY9GTnHySck/hDzq+dtW/4VgnMkippsQ==} + engines: {node: '>=6.9.0'} + dev: false - '@babel/helper-validator-identifier@7.24.7': {} + /@babel/helper-validator-identifier@7.24.7: + resolution: {integrity: sha512-rR+PBcQ1SMQDDyF6X0wxtG8QyLCgUB0eRAGguqRLfkCA87l7yAP7ehq8SNj96OOGTO8OBV70KhuFYcIkHXOg0w==} + engines: {node: '>=6.9.0'} + dev: false - '@babel/helper-validator-option@7.24.8': {} + /@babel/helper-validator-option@7.24.8: + resolution: {integrity: sha512-xb8t9tD1MHLungh/AIoWYN+gVHaB9kwlu8gffXGSt3FFEIT7RjS+xWbc2vUD1UTZdIpKj/ab3rdqJ7ufngyi2Q==} + engines: {node: '>=6.9.0'} + dev: false - '@babel/helper-wrap-function@7.25.0': + /@babel/helper-wrap-function@7.25.0: + resolution: {integrity: sha512-s6Q1ebqutSiZnEjaofc/UKDyC4SbzV5n5SrA2Gq8UawLycr3i04f1dX4OzoQVnexm6aOCh37SQNYlJ/8Ku+PMQ==} + engines: {node: '>=6.9.0'} dependencies: '@babel/template': 7.25.0 '@babel/traverse': 7.25.4 '@babel/types': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/helpers@7.25.0': + /@babel/helpers@7.25.0: + resolution: {integrity: sha512-MjgLZ42aCm0oGjJj8CtSM3DB8NOOf8h2l7DCTePJs29u+v7yO/RBX9nShlKMgFnRks/Q4tBAe7Hxnov9VkGwLw==} + engines: {node: '>=6.9.0'} dependencies: '@babel/template': 7.25.0 '@babel/types': 7.25.4 + dev: false - '@babel/highlight@7.24.7': + /@babel/highlight@7.24.7: + resolution: {integrity: sha512-EStJpq4OuY8xYfhGVXngigBJRWxftKX9ksiGDnmlY3o7B/V7KIAc9X4oiK87uPJSc/vs5L869bem5fhZa8caZw==} + engines: {node: '>=6.9.0'} dependencies: '@babel/helper-validator-identifier': 7.24.7 chalk: 2.4.2 js-tokens: 4.0.0 picocolors: 1.0.1 + dev: false - '@babel/parser@7.25.4': + /@babel/parser@7.25.4: + resolution: {integrity: sha512-nq+eWrOgdtu3jG5Os4TQP3x3cLA8hR8TvJNjD8vnPa20WGycimcparWnLK4jJhElTK6SDyuJo1weMKO/5LpmLA==} + engines: {node: '>=6.0.0'} + hasBin: true dependencies: '@babel/types': 7.25.4 + dev: false - '@babel/plugin-bugfix-firefox-class-in-computed-class-key@7.25.3(@babel/core@7.25.2)': + /@babel/plugin-bugfix-firefox-class-in-computed-class-key@7.25.3(@babel/core@7.25.2): + resolution: {integrity: sha512-wUrcsxZg6rqBXG05HG1FPYgsP6EvwF4WpBbxIpWIIYnH8wG0gzx3yZY3dtEHas4sTAOGkbTsc9EGPxwff8lRoA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/traverse': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-bugfix-safari-class-field-initializer-scope@7.25.0(@babel/core@7.25.2)': + /@babel/plugin-bugfix-safari-class-field-initializer-scope@7.25.0(@babel/core@7.25.2): + resolution: {integrity: sha512-Bm4bH2qsX880b/3ziJ8KD711LT7z4u8CFudmjqle65AZj/HNUFhEf90dqYv6O86buWvSBmeQDjv0Tn2aF/bIBA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@7.25.0(@babel/core@7.25.2)': + /@babel/plugin-bugfix-safari-id-destructuring-collision-in-function-expression@7.25.0(@babel/core@7.25.2): + resolution: {integrity: sha512-lXwdNZtTmeVOOFtwM/WDe7yg1PL8sYhRk/XH0FzbR2HDQ0xC+EnQ/JHeoMYSavtU115tnUk0q9CDyq8si+LMAA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-bugfix-v8-spread-parameters-in-optional-chaining@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-+izXIbke1T33mY4MSNnrqhPXDz01WYhEf3yF5NbnUtkiNnm+XBZJl3kNfoK6NKmYlz/D07+l2GWVK/QfDkNCuQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.13.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 @@ -5370,143 +595,264 @@ snapshots: '@babel/plugin-transform-optional-chaining': 7.24.8(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@7.25.0(@babel/core@7.25.2)': + /@babel/plugin-bugfix-v8-static-class-fields-redefine-readonly@7.25.0(@babel/core@7.25.2): + resolution: {integrity: sha512-tggFrk1AIShG/RUQbEwt2Tr/E+ObkfwrPjR6BjbRvsx24+PSjK8zrq0GWPNCjo8qpRx4DuJzlcvWJqlm+0h3kw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/traverse': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-proposal-object-rest-spread@7.12.1(@babel/core@7.12.9)': + /@babel/plugin-proposal-object-rest-spread@7.12.1(@babel/core@7.12.9): + resolution: {integrity: sha512-s6SowJIjzlhx8o7lsFx5zmY4At6CTtDvgNQDdPzkBQucle58A6b/TTeEBYtyDgmcXjUTM+vE8YOGHZzzbc/ioA==} + deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead. + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.12.9 '@babel/helper-plugin-utils': 7.24.8 '@babel/plugin-syntax-object-rest-spread': 7.8.3(@babel/core@7.12.9) '@babel/plugin-transform-parameters': 7.24.7(@babel/core@7.12.9) + dev: false - '@babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2(@babel/core@7.25.2)': + /@babel/plugin-proposal-private-property-in-object@7.21.0-placeholder-for-preset-env.2(@babel/core@7.25.2): + resolution: {integrity: sha512-SOSkfJDddaM7mak6cPEpswyTRnuRltl429hMraQEglW+OkovnCzsiszTmsrlY//qLFjCpQDFRvjdm2wA5pPm9w==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 + dev: false - '@babel/plugin-syntax-async-generators@7.8.4(@babel/core@7.25.2)': + /@babel/plugin-syntax-async-generators@7.8.4(@babel/core@7.25.2): + resolution: {integrity: sha512-tycmZxkGfZaxhMRbXlPXuVFpdWlXpir2W4AMhSJgRKzk/eDlIXOhb2LHWoLpDF7TEHylV5zNhykX6KAgHJmTNw==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-class-properties@7.12.13(@babel/core@7.25.2)': + /@babel/plugin-syntax-class-properties@7.12.13(@babel/core@7.25.2): + resolution: {integrity: sha512-fm4idjKla0YahUNgFNLCB0qySdsoPiZP3iQE3rky0mBUtMZ23yDJ9SJdg6dXTSDnulOVqiF3Hgr9nbXvXTQZYA==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-class-static-block@7.14.5(@babel/core@7.25.2)': + /@babel/plugin-syntax-class-static-block@7.14.5(@babel/core@7.25.2): + resolution: {integrity: sha512-b+YyPmr6ldyNnM6sqYeMWE+bgJcJpO6yS4QD7ymxgH34GBPNDM/THBh8iunyvKIZztiwLH4CJZ0RxTk9emgpjw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-dynamic-import@7.8.3(@babel/core@7.25.2)': + /@babel/plugin-syntax-dynamic-import@7.8.3(@babel/core@7.25.2): + resolution: {integrity: sha512-5gdGbFon+PszYzqs83S3E5mpi7/y/8M9eC90MRTZfduQOYW76ig6SOSPNe41IG5LoP3FGBn2N0RjVDSQiS94kQ==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-export-namespace-from@7.8.3(@babel/core@7.25.2)': + /@babel/plugin-syntax-export-namespace-from@7.8.3(@babel/core@7.25.2): + resolution: {integrity: sha512-MXf5laXo6c1IbEbegDmzGPwGNTsHZmEy6QGznu5Sh2UCWvueywb2ee+CCE4zQiZstxU9BMoQO9i6zUFSY0Kj0Q==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-import-assertions@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-syntax-import-assertions@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-Ec3NRUMoi8gskrkBe3fNmEQfxDvY8bgfQpz6jlk/41kX9eUjvpyqWU7PBP/pLAvMaSQjbMNKJmvX57jP+M6bPg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-import-attributes@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-syntax-import-attributes@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-hbX+lKKeUMGihnK8nvKqmXBInriT3GVjzXKFriV3YC6APGxMbP8RZNFwy91+hocLXq90Mta+HshoB31802bb8A==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-import-meta@7.10.4(@babel/core@7.25.2)': + /@babel/plugin-syntax-import-meta@7.10.4(@babel/core@7.25.2): + resolution: {integrity: sha512-Yqfm+XDx0+Prh3VSeEQCPU81yC+JWZ2pDPFSS4ZdpfZhp4MkFMaDC1UqseovEKwSUpnIL7+vK+Clp7bfh0iD7g==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-json-strings@7.8.3(@babel/core@7.25.2)': + /@babel/plugin-syntax-json-strings@7.8.3(@babel/core@7.25.2): + resolution: {integrity: sha512-lY6kdGpWHvjoe2vk4WrAapEuBR69EMxZl+RoGRhrFGNYVK8mOPAW8VfbT/ZgrFbXlDNiiaxQnAtgVCZ6jv30EA==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-jsx@7.12.1(@babel/core@7.12.9)': + /@babel/plugin-syntax-jsx@7.12.1(@babel/core@7.12.9): + resolution: {integrity: sha512-1yRi7yAtB0ETgxdY9ti/p2TivUxJkTdhu/ZbF9MshVGqOx1TdB3b7xCXs49Fupgg50N45KcAsRP/ZqWjs9SRjg==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.12.9 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-jsx@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-syntax-jsx@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-6ddciUPe/mpMnOKv/U+RSd2vvVy+Yw/JfBB0ZHYjEZt9NLHmCUylNYlsbqCCS1Bffjlb0fCwC9Vqz+sBz6PsiQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-logical-assignment-operators@7.10.4(@babel/core@7.25.2)': + /@babel/plugin-syntax-logical-assignment-operators@7.10.4(@babel/core@7.25.2): + resolution: {integrity: sha512-d8waShlpFDinQ5MtvGU9xDAOzKH47+FFoney2baFIoMr952hKOLp1HR7VszoZvOsV/4+RRszNY7D17ba0te0ig==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-nullish-coalescing-operator@7.8.3(@babel/core@7.25.2)': + /@babel/plugin-syntax-nullish-coalescing-operator@7.8.3(@babel/core@7.25.2): + resolution: {integrity: sha512-aSff4zPII1u2QD7y+F8oDsz19ew4IGEJg9SVW+bqwpwtfFleiQDMdzA/R+UlWDzfnHFCxxleFT0PMIrR36XLNQ==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-numeric-separator@7.10.4(@babel/core@7.25.2)': + /@babel/plugin-syntax-numeric-separator@7.10.4(@babel/core@7.25.2): + resolution: {integrity: sha512-9H6YdfkcK/uOnY/K7/aA2xpzaAgkQn37yzWUMRK7OaPOqOpGS1+n0H5hxT9AUw9EsSjPW8SVyMJwYRtWs3X3ug==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-object-rest-spread@7.8.3(@babel/core@7.12.9)': + /@babel/plugin-syntax-object-rest-spread@7.8.3(@babel/core@7.12.9): + resolution: {integrity: sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.12.9 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-object-rest-spread@7.8.3(@babel/core@7.25.2)': + /@babel/plugin-syntax-object-rest-spread@7.8.3(@babel/core@7.25.2): + resolution: {integrity: sha512-XoqMijGZb9y3y2XskN+P1wUGiVwWZ5JmoDRwx5+3GmEplNyVM2s2Dg8ILFQm8rWM48orGy5YpI5Bl8U1y7ydlA==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-optional-catch-binding@7.8.3(@babel/core@7.25.2)': + /@babel/plugin-syntax-optional-catch-binding@7.8.3(@babel/core@7.25.2): + resolution: {integrity: sha512-6VPD0Pc1lpTqw0aKoeRTMiB+kWhAoT24PA+ksWSBrFtl5SIRVpZlwN3NNPQjehA2E/91FV3RjLWoVTglWcSV3Q==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-optional-chaining@7.8.3(@babel/core@7.25.2)': + /@babel/plugin-syntax-optional-chaining@7.8.3(@babel/core@7.25.2): + resolution: {integrity: sha512-KoK9ErH1MBlCPxV0VANkXW2/dw4vlbGDrFgz8bmUsBGYkFRcbRwMh6cIJubdPrkxRwuGdtCk0v/wPTKbQgBjkg==} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-private-property-in-object@7.14.5(@babel/core@7.25.2)': + /@babel/plugin-syntax-private-property-in-object@7.14.5(@babel/core@7.25.2): + resolution: {integrity: sha512-0wVnp9dxJ72ZUJDV27ZfbSj6iHLoytYZmh3rFcxNnvsJF3ktkzLDZPy/mA17HGsaQT3/DQsWYX1f1QGWkCoVUg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-top-level-await@7.14.5(@babel/core@7.25.2)': + /@babel/plugin-syntax-top-level-await@7.14.5(@babel/core@7.25.2): + resolution: {integrity: sha512-hx++upLv5U1rgYfwe1xBQUhRmU41NEvpUvrp8jkrSCdvGSnM5/qdRMtylJ6PG5OFkBaHkbTAKTnd3/YyESRHFw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-typescript@7.25.4(@babel/core@7.25.2)': + /@babel/plugin-syntax-typescript@7.25.4(@babel/core@7.25.2): + resolution: {integrity: sha512-uMOCoHVU52BsSWxPOMVv5qKRdeSlPuImUCB2dlPuBSU+W2/ROE7/Zg8F2Kepbk+8yBa68LlRKxO+xgEVWorsDg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-syntax-unicode-sets-regex@7.18.6(@babel/core@7.25.2)': + /@babel/plugin-syntax-unicode-sets-regex@7.18.6(@babel/core@7.25.2): + resolution: {integrity: sha512-727YkEAPwSIQTv5im8QHz3upqp92JTWhidIC81Tdx4VJYIte/VndKf1qKrfnnhPLiPghStWfvC/iFaMCQu7Nqg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-regexp-features-plugin': 7.25.2(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-arrow-functions@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-arrow-functions@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-Dt9LQs6iEY++gXUwY03DNFat5C2NbO48jj+j/bSAz6b3HgPs39qcPiYt77fDObIcFwj3/C2ICX9YMwGflUoSHQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-async-generator-functions@7.25.4(@babel/core@7.25.2)': + /@babel/plugin-transform-async-generator-functions@7.25.4(@babel/core@7.25.2): + resolution: {integrity: sha512-jz8cV2XDDTqjKPwVPJBIjORVEmSGYhdRa8e5k5+vN+uwcjSrSxUaebBRa4ko1jqNF2uxyg8G6XYk30Jv285xzg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 @@ -5515,8 +861,13 @@ snapshots: '@babel/traverse': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-async-to-generator@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-async-to-generator@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-SQY01PcJfmQ+4Ash7NE+rpbLFbmqA2GPIgqzxfFTL4t1FKRq4zTms/7htKpoCUI9OcFYgzqfmCdH53s6/jn5fA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-module-imports': 7.24.7 @@ -5524,26 +875,46 @@ snapshots: '@babel/helper-remap-async-to-generator': 7.25.0(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-block-scoped-functions@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-block-scoped-functions@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-yO7RAz6EsVQDaBH18IDJcMB1HnrUn2FJ/Jslc/WtPPWcjhpUJXU/rjbwmluzp7v/ZzWcEhTMXELnnsz8djWDwQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-block-scoping@7.25.0(@babel/core@7.25.2)': + /@babel/plugin-transform-block-scoping@7.25.0(@babel/core@7.25.2): + resolution: {integrity: sha512-yBQjYoOjXlFv9nlXb3f1casSHOZkWr29NX+zChVanLg5Nc157CrbEX9D7hxxtTpuFy7Q0YzmmWfJxzvps4kXrQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-class-properties@7.25.4(@babel/core@7.25.2)': + /@babel/plugin-transform-class-properties@7.25.4(@babel/core@7.25.2): + resolution: {integrity: sha512-nZeZHyCWPfjkdU5pA/uHiTaDAFUEqkpzf1YoQT2NeSynCGYq9rxfyI3XpQbfx/a0hSnFH6TGlEXvae5Vi7GD8g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-class-features-plugin': 7.25.4(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-class-static-block@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-class-static-block@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-HMXK3WbBPpZQufbMG4B46A90PkuuhN9vBCb5T8+VAHqvAqvcLi+2cKoukcpmUYkszLhScU3l1iudhrks3DggRQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.12.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-class-features-plugin': 7.25.4(@babel/core@7.25.2) @@ -5551,8 +922,13 @@ snapshots: '@babel/plugin-syntax-class-static-block': 7.14.5(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-classes@7.25.4(@babel/core@7.25.2)': + /@babel/plugin-transform-classes@7.25.4(@babel/core@7.25.2): + resolution: {integrity: sha512-oexUfaQle2pF/b6E0dwsxQtAol9TLSO88kQvym6HHBWFliV2lGdrPieX+WgMRLSJDVzdYywk7jXbLPuO2KLTLg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-annotate-as-pure': 7.24.7 @@ -5563,64 +939,114 @@ snapshots: globals: 11.12.0 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-computed-properties@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-computed-properties@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-25cS7v+707Gu6Ds2oY6tCkUwsJ9YIDbggd9+cu9jzzDgiNq7hR/8dkzxWfKWnTic26vsI3EsCXNd4iEB6e8esQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/template': 7.25.0 + dev: false - '@babel/plugin-transform-destructuring@7.24.8(@babel/core@7.25.2)': + /@babel/plugin-transform-destructuring@7.24.8(@babel/core@7.25.2): + resolution: {integrity: sha512-36e87mfY8TnRxc7yc6M9g9gOB7rKgSahqkIKwLpz4Ppk2+zC2Cy1is0uwtuSG6AE4zlTOUa+7JGz9jCJGLqQFQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-dotall-regex@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-dotall-regex@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-ZOA3W+1RRTSWvyqcMJDLqbchh7U4NRGqwRfFSVbOLS/ePIP4vHB5e8T8eXcuqyN1QkgKyj5wuW0lcS85v4CrSw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-regexp-features-plugin': 7.25.2(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-duplicate-keys@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-duplicate-keys@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-JdYfXyCRihAe46jUIliuL2/s0x0wObgwwiGxw/UbgJBr20gQBThrokO4nYKgWkD7uBaqM7+9x5TU7NkExZJyzw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-duplicate-named-capturing-groups-regex@7.25.0(@babel/core@7.25.2)': + /@babel/plugin-transform-duplicate-named-capturing-groups-regex@7.25.0(@babel/core@7.25.2): + resolution: {integrity: sha512-YLpb4LlYSc3sCUa35un84poXoraOiQucUTTu8X1j18JV+gNa8E0nyUf/CjZ171IRGr4jEguF+vzJU66QZhn29g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-regexp-features-plugin': 7.25.2(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-dynamic-import@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-dynamic-import@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-sc3X26PhZQDb3JhORmakcbvkeInvxz+A8oda99lj7J60QRuPZvNAk9wQlTBS1ZynelDrDmTU4pw1tyc5d5ZMUg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/plugin-syntax-dynamic-import': 7.8.3(@babel/core@7.25.2) + dev: false - '@babel/plugin-transform-exponentiation-operator@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-exponentiation-operator@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-Rqe/vSc9OYgDajNIK35u7ot+KeCoetqQYFXM4Epf7M7ez3lWlOjrDjrwMei6caCVhfdw+mIKD4cgdGNy5JQotQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-builder-binary-assignment-operator-visitor': 7.24.7 '@babel/helper-plugin-utils': 7.24.8 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-export-namespace-from@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-export-namespace-from@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-v0K9uNYsPL3oXZ/7F9NNIbAj2jv1whUEtyA6aujhekLs56R++JDQuzRcP2/z4WX5Vg/c5lE9uWZA0/iUoFhLTA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/plugin-syntax-export-namespace-from': 7.8.3(@babel/core@7.25.2) + dev: false - '@babel/plugin-transform-for-of@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-for-of@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-wo9ogrDG1ITTTBsy46oGiN1dS9A7MROBTcYsfS8DtsImMkHk9JXJ3EWQM6X2SUw4x80uGPlwj0o00Uoc6nEE3g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/helper-skip-transparent-expression-wrappers': 7.24.7 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-function-name@7.25.1(@babel/core@7.25.2)': + /@babel/plugin-transform-function-name@7.25.1(@babel/core@7.25.2): + resolution: {integrity: sha512-TVVJVdW9RKMNgJJlLtHsKDTydjZAbwIsn6ySBPQaEAUU5+gVvlJt/9nRmqVbsV/IBanRjzWoaAQKLoamWVOUuA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-compilation-targets': 7.25.2 @@ -5628,38 +1054,68 @@ snapshots: '@babel/traverse': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-json-strings@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-json-strings@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-2yFnBGDvRuxAaE/f0vfBKvtnvvqU8tGpMHqMNpTN2oWMKIR3NqFkjaAgGwawhqK/pIN2T3XdjGPdaG0vDhOBGw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/plugin-syntax-json-strings': 7.8.3(@babel/core@7.25.2) + dev: false - '@babel/plugin-transform-literals@7.25.2(@babel/core@7.25.2)': + /@babel/plugin-transform-literals@7.25.2(@babel/core@7.25.2): + resolution: {integrity: sha512-HQI+HcTbm9ur3Z2DkO+jgESMAMcYLuN/A7NRw9juzxAezN9AvqvUTnpKP/9kkYANz6u7dFlAyOu44ejuGySlfw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-logical-assignment-operators@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-logical-assignment-operators@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-4D2tpwlQ1odXmTEIFWy9ELJcZHqrStlzK/dAOWYyxX3zT0iXQB6banjgeOJQXzEc4S0E0a5A+hahxPaEFYftsw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/plugin-syntax-logical-assignment-operators': 7.10.4(@babel/core@7.25.2) + dev: false - '@babel/plugin-transform-member-expression-literals@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-member-expression-literals@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-T/hRC1uqrzXMKLQ6UCwMT85S3EvqaBXDGf0FaMf4446Qx9vKwlghvee0+uuZcDUCZU5RuNi4781UQ7R308zzBw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-modules-amd@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-modules-amd@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-9+pB1qxV3vs/8Hdmz/CulFB8w2tuu6EB94JZFsjdqxQokwGa9Unap7Bo2gGBGIvPmDIVvQrom7r5m/TCDMURhg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-module-transforms': 7.25.2(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-modules-commonjs@7.24.8(@babel/core@7.25.2)': + /@babel/plugin-transform-modules-commonjs@7.24.8(@babel/core@7.25.2): + resolution: {integrity: sha512-WHsk9H8XxRs3JXKWFiqtQebdh9b/pTk4EgueygFzYlTKAg0Ud985mSevdNjdXdFBATSKVJGQXP1tv6aGbssLKA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-module-transforms': 7.25.2(@babel/core@7.25.2) @@ -5667,8 +1123,13 @@ snapshots: '@babel/helper-simple-access': 7.24.7 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-modules-systemjs@7.25.0(@babel/core@7.25.2)': + /@babel/plugin-transform-modules-systemjs@7.25.0(@babel/core@7.25.2): + resolution: {integrity: sha512-YPJfjQPDXxyQWg/0+jHKj1llnY5f/R6a0p/vP4lPymxLu7Lvl4k2WMitqi08yxwQcCVUUdG9LCUj4TNEgAp3Jw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-module-transforms': 7.25.2(@babel/core@7.25.2) @@ -5677,61 +1138,106 @@ snapshots: '@babel/traverse': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-modules-umd@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-modules-umd@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-3aytQvqJ/h9z4g8AsKPLvD4Zqi2qT+L3j7XoFFu1XBlZWEl2/1kWnhmAbxpLgPrHSY0M6UA02jyTiwUVtiKR6A==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-module-transforms': 7.25.2(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-named-capturing-groups-regex@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-named-capturing-groups-regex@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-/jr7h/EWeJtk1U/uz2jlsCioHkZk1JJZVcc8oQsJ1dUlaJD83f4/6Zeh2aHt9BIFokHIsSeDfhUmju0+1GPd6g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-regexp-features-plugin': 7.25.2(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-new-target@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-new-target@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-RNKwfRIXg4Ls/8mMTza5oPF5RkOW8Wy/WgMAp1/F1yZ8mMbtwXW+HDoJiOsagWrAhI5f57Vncrmr9XeT4CVapA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-nullish-coalescing-operator@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-nullish-coalescing-operator@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-Ts7xQVk1OEocqzm8rHMXHlxvsfZ0cEF2yomUqpKENHWMF4zKk175Y4q8H5knJes6PgYad50uuRmt3UJuhBw8pQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/plugin-syntax-nullish-coalescing-operator': 7.8.3(@babel/core@7.25.2) + dev: false - '@babel/plugin-transform-numeric-separator@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-numeric-separator@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-e6q1TiVUzvH9KRvicuxdBTUj4AdKSRwzIyFFnfnezpCfP2/7Qmbb8qbU2j7GODbl4JMkblitCQjKYUaX/qkkwA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/plugin-syntax-numeric-separator': 7.10.4(@babel/core@7.25.2) + dev: false - '@babel/plugin-transform-object-rest-spread@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-object-rest-spread@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-4QrHAr0aXQCEFni2q4DqKLD31n2DL+RxcwnNjDFkSG0eNQ/xCavnRkfCUjsyqGC2OviNJvZOF/mQqZBw7i2C5Q==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-compilation-targets': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/plugin-syntax-object-rest-spread': 7.8.3(@babel/core@7.25.2) '@babel/plugin-transform-parameters': 7.24.7(@babel/core@7.25.2) + dev: false - '@babel/plugin-transform-object-super@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-object-super@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-A/vVLwN6lBrMFmMDmPPz0jnE6ZGx7Jq7d6sT/Ev4H65RER6pZ+kczlf1DthF5N0qaPHBsI7UXiE8Zy66nmAovg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/helper-replace-supers': 7.25.0(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-optional-catch-binding@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-optional-catch-binding@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-uLEndKqP5BfBbC/5jTwPxLh9kqPWWgzN/f8w6UwAIirAEqiIVJWWY312X72Eub09g5KF9+Zn7+hT7sDxmhRuKA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/plugin-syntax-optional-catch-binding': 7.8.3(@babel/core@7.25.2) + dev: false - '@babel/plugin-transform-optional-chaining@7.24.8(@babel/core@7.25.2)': + /@babel/plugin-transform-optional-chaining@7.24.8(@babel/core@7.25.2): + resolution: {integrity: sha512-5cTOLSMs9eypEy8JUVvIKOu6NgvbJMnpG62VpIHrTmROdQ+L5mDAaI40g25k5vXti55JWNX5jCkq3HZxXBQANw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 @@ -5739,26 +1245,46 @@ snapshots: '@babel/plugin-syntax-optional-chaining': 7.8.3(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-parameters@7.24.7(@babel/core@7.12.9)': + /@babel/plugin-transform-parameters@7.24.7(@babel/core@7.12.9): + resolution: {integrity: sha512-yGWW5Rr+sQOhK0Ot8hjDJuxU3XLRQGflvT4lhlSY0DFvdb3TwKaY26CJzHtYllU0vT9j58hc37ndFPsqT1SrzA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.12.9 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-parameters@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-parameters@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-yGWW5Rr+sQOhK0Ot8hjDJuxU3XLRQGflvT4lhlSY0DFvdb3TwKaY26CJzHtYllU0vT9j58hc37ndFPsqT1SrzA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-private-methods@7.25.4(@babel/core@7.25.2)': + /@babel/plugin-transform-private-methods@7.25.4(@babel/core@7.25.2): + resolution: {integrity: sha512-ao8BG7E2b/URaUQGqN3Tlsg+M3KlHY6rJ1O1gXAEUnZoyNQnvKyH87Kfg+FoxSeyWUB8ISZZsC91C44ZuBFytw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-class-features-plugin': 7.25.4(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-private-property-in-object@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-private-property-in-object@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-9z76mxwnwFxMyxZWEgdgECQglF2Q7cFLm0kMf8pGwt+GSJsY0cONKj/UuO4bOH0w/uAel3ekS4ra5CEAyJRmDA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-annotate-as-pure': 7.24.7 @@ -5767,30 +1293,55 @@ snapshots: '@babel/plugin-syntax-private-property-in-object': 7.14.5(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-property-literals@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-property-literals@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-EMi4MLQSHfd2nrCqQEWxFdha2gBCqU4ZcCng4WBGZ5CJL4bBRW0ptdqqDdeirGZcpALazVVNJqRmsO8/+oNCBA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-react-constant-elements@7.25.1(@babel/core@7.25.2)': + /@babel/plugin-transform-react-constant-elements@7.25.1(@babel/core@7.25.2): + resolution: {integrity: sha512-SLV/giH/V4SmloZ6Dt40HjTGTAIkxn33TVIHxNGNvo8ezMhrxBkzisj4op1KZYPIOHFLqhv60OHvX+YRu4xbmQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-react-display-name@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-react-display-name@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-H/Snz9PFxKsS1JLI4dJLtnJgCJRoo0AUm3chP6NYr+9En1JMKloheEiLIhlp5MDVznWo+H3AAC1Mc8lmUEpsgg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-react-jsx-development@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-react-jsx-development@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-QG9EnzoGn+Qar7rxuW+ZOsbWOt56FvvI93xInqsZDC5fsekx1AlIO4KIJ5M+D0p0SqSH156EpmZyXq630B8OlQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/plugin-transform-react-jsx': 7.25.2(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-react-jsx@7.25.2(@babel/core@7.25.2)': + /@babel/plugin-transform-react-jsx@7.25.2(@babel/core@7.25.2): + resolution: {integrity: sha512-KQsqEAVBpU82NM/B/N9j9WOdphom1SZH3R+2V7INrQUH+V9EBFwZsEJl8eBIVeQE62FxJCc70jzEZwqU7RcVqA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-annotate-as-pure': 7.24.7 @@ -5800,25 +1351,45 @@ snapshots: '@babel/types': 7.25.4 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-react-pure-annotations@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-react-pure-annotations@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-PLgBVk3fzbmEjBJ/u8kFzOqS9tUeDjiaWud/rRym/yjCo/M9cASPlnrd2ZmmZpQT40fOOrvR8jh+n8jikrOhNA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-annotate-as-pure': 7.24.7 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-regenerator@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-regenerator@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-lq3fvXPdimDrlg6LWBoqj+r/DEWgONuwjuOuQCSYgRroXDH/IdM1C0IZf59fL5cHLpjEH/O6opIRBbqv7ELnuA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 regenerator-transform: 0.15.2 + dev: false - '@babel/plugin-transform-reserved-words@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-reserved-words@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-0DUq0pHcPKbjFZCfTss/pGkYMfy3vFWydkUBd9r0GHpIyfs2eCDENvqadMycRS9wZCXR41wucAfJHJmwA0UmoQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-runtime@7.25.4(@babel/core@7.25.2)': + /@babel/plugin-transform-runtime@7.25.4(@babel/core@7.25.2): + resolution: {integrity: sha512-8hsyG+KUYGY0coX6KUCDancA0Vw225KJ2HJO0yCNr1vq5r+lJTleDaJf0K7iOhjw4SWhu03TMBzYTJ9krmzULQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-module-imports': 7.24.7 @@ -5829,36 +1400,66 @@ snapshots: semver: 6.3.1 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-shorthand-properties@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-shorthand-properties@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-KsDsevZMDsigzbA09+vacnLpmPH4aWjcZjXdyFKGzpplxhbeB4wYtury3vglQkg6KM/xEPKt73eCjPPf1PgXBA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-spread@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-spread@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-x96oO0I09dgMDxJaANcRyD4ellXFLLiWhuwDxKZX5g2rWP1bTPkBSwCYv96VDXVT1bD9aPj8tppr5ITIh8hBng==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/helper-skip-transparent-expression-wrappers': 7.24.7 transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-sticky-regex@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-sticky-regex@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-kHPSIJc9v24zEml5geKg9Mjx5ULpfncj0wRpYtxbvKyTtHCYDkVE3aHQ03FrpEo4gEe2vrJJS1Y9CJTaThA52g==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-template-literals@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-template-literals@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-AfDTQmClklHCOLxtGoP7HkeMw56k1/bTQjwsfhL6pppo/M4TOBSq+jjBUBLmV/4oeFg4GWMavIl44ZeCtmmZTw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-typeof-symbol@7.24.8(@babel/core@7.25.2)': + /@babel/plugin-transform-typeof-symbol@7.24.8(@babel/core@7.25.2): + resolution: {integrity: sha512-adNTUpDCVnmAE58VEqKlAA6ZBlNkMnWD0ZcW76lyNFN3MJniyGFZfNwERVk8Ap56MCnXztmDr19T4mPTztcuaw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-typescript@7.25.2(@babel/core@7.25.2)': + /@babel/plugin-transform-typescript@7.25.2(@babel/core@7.25.2): + resolution: {integrity: sha512-lBwRvjSmqiMYe/pS0+1gggjJleUJi7NzjvQ1Fkqtt69hBa/0t1YuW/MLQMAPixfwaQOHUXsd6jeU3Z+vdGv3+A==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-annotate-as-pure': 7.24.7 @@ -5868,31 +1469,56 @@ snapshots: '@babel/plugin-syntax-typescript': 7.25.4(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/plugin-transform-unicode-escapes@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-unicode-escapes@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-U3ap1gm5+4edc2Q/P+9VrBNhGkfnf+8ZqppY71Bo/pzZmXhhLdqgaUl6cuB07O1+AQJtCLfaOmswiNbSQ9ivhw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-unicode-property-regex@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-unicode-property-regex@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-uH2O4OV5M9FZYQrwc7NdVmMxQJOCCzFeYudlZSzUAHRFeOujQefa92E74TQDVskNHCzOXoigEuoyzHDhaEaK5w==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-regexp-features-plugin': 7.25.2(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-unicode-regex@7.24.7(@babel/core@7.25.2)': + /@babel/plugin-transform-unicode-regex@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-hlQ96MBZSAXUq7ltkjtu3FJCCSMx/j629ns3hA3pXnBXjanNP0LHi+JpPeA81zaWgVK1VGH95Xuy7u0RyQ8kMg==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-regexp-features-plugin': 7.25.2(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/plugin-transform-unicode-sets-regex@7.25.4(@babel/core@7.25.2)': + /@babel/plugin-transform-unicode-sets-regex@7.25.4(@babel/core@7.25.2): + resolution: {integrity: sha512-qesBxiWkgN1Q+31xUE9RcMk79eOXXDCv6tfyGMRSs4RGlioSg2WVyQAm07k726cSE56pa+Kb0y9epX2qaXzTvA==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-create-regexp-features-plugin': 7.25.2(@babel/core@7.25.2) '@babel/helper-plugin-utils': 7.24.8 + dev: false - '@babel/preset-env@7.25.4(@babel/core@7.25.2)': + /@babel/preset-env@7.25.4(@babel/core@7.25.2): + resolution: {integrity: sha512-W9Gyo+KmcxjGahtt3t9fb14vFRWvPpu5pT6GBlovAK6BTBcxgjfVMSQCfJl4oi35ODrxP6xx2Wr8LNST57Mraw==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/compat-data': 7.25.4 '@babel/core': 7.25.2 @@ -5980,15 +1606,24 @@ snapshots: semver: 6.3.1 transitivePeerDependencies: - supports-color + dev: false - '@babel/preset-modules@0.1.6-no-external-plugins(@babel/core@7.25.2)': + /@babel/preset-modules@0.1.6-no-external-plugins(@babel/core@7.25.2): + resolution: {integrity: sha512-HrcgcIESLm9aIR842yhJ5RWan/gebQUJ6E/E5+rf0y9o6oj7w0Br+sWuL6kEQ/o/AdfvR1Je9jG18/gnpwjEyA==} + peerDependencies: + '@babel/core': ^7.0.0-0 || ^8.0.0-0 <8.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 '@babel/types': 7.25.4 esutils: 2.0.3 + dev: false - '@babel/preset-react@7.24.7(@babel/core@7.25.2)': + /@babel/preset-react@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-AAH4lEkpmzFWrGVlHaxJB7RLH21uPQ9+He+eFLWHmF9IuFQVugz8eAsamaW0DXRrTfco5zj1wWtpdcXJUOfsag==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 @@ -5999,8 +1634,13 @@ snapshots: '@babel/plugin-transform-react-pure-annotations': 7.24.7(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/preset-typescript@7.24.7(@babel/core@7.25.2)': + /@babel/preset-typescript@7.24.7(@babel/core@7.25.2): + resolution: {integrity: sha512-SyXRe3OdWwIwalxDg5UtJnJQO+YPcTfwiIY2B0Xlddh9o7jpWLvv8X1RthIeDOxQ+O1ML5BLPCONToObyVQVuQ==} + engines: {node: '>=6.9.0'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@babel/helper-plugin-utils': 7.24.8 @@ -6010,25 +1650,39 @@ snapshots: '@babel/plugin-transform-typescript': 7.25.2(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - '@babel/regjsgen@0.8.0': {} + /@babel/regjsgen@0.8.0: + resolution: {integrity: sha512-x/rqGMdzj+fWZvCOYForTghzbtqPDZ5gPwaoNGHdgDfF2QA/XZbCBp4Moo5scrkAMPhB7z26XM/AaHuIJdgauA==} + dev: false - '@babel/runtime-corejs3@7.25.0': + /@babel/runtime-corejs3@7.25.0: + resolution: {integrity: sha512-BOehWE7MgQ8W8Qn0CQnMtg2tHPHPulcS/5AVpFvs2KCK1ET+0WqZqPvnpRpFN81gYoFopdIEJX9Sgjw3ZBccPg==} + engines: {node: '>=6.9.0'} dependencies: core-js-pure: 3.38.1 regenerator-runtime: 0.14.1 + dev: false - '@babel/runtime@7.25.4': + /@babel/runtime@7.25.4: + resolution: {integrity: sha512-DSgLeL/FNcpXuzav5wfYvHCGvynXkJbn3Zvc3823AEe9nPwW9IK4UoCSS5yGymmQzN0pCPvivtgS6/8U2kkm1w==} + engines: {node: '>=6.9.0'} dependencies: regenerator-runtime: 0.14.1 + dev: false - '@babel/template@7.25.0': + /@babel/template@7.25.0: + resolution: {integrity: sha512-aOOgh1/5XzKvg1jvVz7AVrx2piJ2XBi227DHmbY6y+bM9H2FlN+IfecYu4Xl0cNiiVejlsCri89LUsbj8vJD9Q==} + engines: {node: '>=6.9.0'} dependencies: '@babel/code-frame': 7.24.7 '@babel/parser': 7.25.4 '@babel/types': 7.25.4 + dev: false - '@babel/traverse@7.25.4': + /@babel/traverse@7.25.4: + resolution: {integrity: sha512-VJ4XsrD+nOvlXyLzmLzUs/0qjFS4sK30te5yEFlvbbUNEgKaVb2BHZUpAL+ttLPQAHNrsI3zZisbfha5Cvr8vg==} + engines: {node: '>=6.9.0'} dependencies: '@babel/code-frame': 7.24.7 '@babel/generator': 7.25.5 @@ -6039,17 +1693,27 @@ snapshots: globals: 11.12.0 transitivePeerDependencies: - supports-color + dev: false - '@babel/types@7.25.4': + /@babel/types@7.25.4: + resolution: {integrity: sha512-zQ1ijeeCXVEh+aNL0RlmkPkG8HUiDcU2pzQQFjtbntgAczRASFzj4H+6+bV+dy1ntKR14I/DypeuRG1uma98iQ==} + engines: {node: '>=6.9.0'} dependencies: '@babel/helper-string-parser': 7.24.8 '@babel/helper-validator-identifier': 7.24.7 to-fast-properties: 2.0.0 + dev: false - '@colors/colors@1.5.0': + /@colors/colors@1.5.0: + resolution: {integrity: sha512-ooWCrlZP11i8GImSjTHYHLkvFDP48nS4+204nGb1RiX/WXYHmJA2III9/e2DWVabCESdW7hBAEzHRqUn9OUVvQ==} + engines: {node: '>=0.1.90'} + requiresBuild: true + dev: false optional: true - '@crowdin/cli@3.13.0': + /@crowdin/cli@3.13.0: + resolution: {integrity: sha512-4YY1XSJyFdIADMX3U11WtkhL9wVWU/KCBEB6N360ybZVOWKE6G2/ERmWmYs8N1kXO6eoM2UUOp4qb8LmJ9UGTg==} + hasBin: true dependencies: command-exists-promise: 2.0.2 node-fetch: 2.6.7 @@ -6058,12 +1722,33 @@ snapshots: yauzl: 2.10.0 transitivePeerDependencies: - encoding + dev: false - '@discoveryjs/json-ext@0.5.7': {} + /@discoveryjs/json-ext@0.5.7: + resolution: {integrity: sha512-dBVuXR082gk3jsFp7Rd/JI4kytwGHecnCoTtXFb7DB6CNHp4rg5k1bhg0nWdLGLnOV71lmDzGQaLMy8iPLY0pw==} + engines: {node: '>=10.0.0'} + dev: false - '@docsearch/css@3.6.1': {} + /@docsearch/css@3.6.1: + resolution: {integrity: sha512-VtVb5DS+0hRIprU2CO6ZQjK2Zg4QU5HrDM1+ix6rT0umsYvFvatMAnf97NHZlVWDaaLlx7GRfR/7FikANiM2Fg==} + dev: false - '@docsearch/react@3.6.1(@algolia/client-search@4.24.0)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(search-insights@2.17.0)': + /@docsearch/react@3.6.1(@algolia/client-search@4.24.0)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(search-insights@2.17.0): + resolution: {integrity: sha512-qXZkEPvybVhSXj0K7U3bXc233tk5e8PfhoZ6MhPOiik/qUQxYC+Dn9DnoS7CxHQQhHfCvTiN0eY9M12oRghEXw==} + peerDependencies: + '@types/react': '>= 16.8.0 < 19.0.0' + react: '>= 16.8.0 < 19.0.0' + react-dom: '>= 16.8.0 < 19.0.0' + search-insights: '>= 1 < 3' + peerDependenciesMeta: + '@types/react': + optional: true + react: + optional: true + react-dom: + optional: true + search-insights: + optional: true dependencies: '@algolia/autocomplete-core': 1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0)(search-insights@2.17.0) '@algolia/autocomplete-preset-algolia': 1.9.3(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) @@ -6075,8 +1760,15 @@ snapshots: search-insights: 2.17.0 transitivePeerDependencies: - '@algolia/client-search' + dev: false - '@docusaurus/core@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/core@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-Vd6XOluKQqzG12fEs9prJgDtyn6DPok9vmUWDR2E6/nV5Fl9SVkhEQOBxwObjk3kQh7OY7vguFaLh0jqdApWsA==} + engines: {node: '>=16.14'} + hasBin: true + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@babel/core': 7.25.2 '@babel/generator': 7.25.5 @@ -6132,7 +1824,7 @@ snapshots: react-dev-utils: 12.0.1(typescript@5.5.4)(webpack@5.94.0) react-dom: 17.0.2(react@17.0.2) react-helmet-async: 1.3.0(react-dom@17.0.2)(react@17.0.2) - react-loadable: '@docusaurus/react-loadable@5.5.2(react@17.0.2)' + react-loadable: /@docusaurus/react-loadable@5.5.2(react@17.0.2) react-loadable-ssr-addon-v5-slorber: 1.0.1(@docusaurus/react-loadable@5.5.2)(webpack@5.94.0) react-router: 5.3.4(react@17.0.2) react-router-config: 5.1.1(react-router@5.3.4)(react@17.0.2) @@ -6169,20 +1861,32 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/cssnano-preset@2.2.0': + /@docusaurus/cssnano-preset@2.2.0: + resolution: {integrity: sha512-mAAwCo4n66TMWBH1kXnHVZsakW9VAXJzTO4yZukuL3ro4F+JtkMwKfh42EG75K/J/YIFQG5I/Bzy0UH/hFxaTg==} + engines: {node: '>=16.14'} dependencies: cssnano-preset-advanced: 5.3.10(postcss@8.4.41) postcss: 8.4.41 postcss-sort-media-queries: 4.4.1(postcss@8.4.41) tslib: 2.7.0 + dev: false - '@docusaurus/logger@2.2.0': + /@docusaurus/logger@2.2.0: + resolution: {integrity: sha512-DF3j1cA5y2nNsu/vk8AG7xwpZu6f5MKkPPMaaIbgXLnWGfm6+wkOeW7kNrxnM95YOhKUkJUophX69nGUnLsm0A==} + engines: {node: '>=16.14'} dependencies: chalk: 4.1.2 tslib: 2.7.0 + dev: false - '@docusaurus/mdx-loader@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)': + /@docusaurus/mdx-loader@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2): + resolution: {integrity: sha512-X2bzo3T0jW0VhUU+XdQofcEeozXOTmKQMvc8tUnWRdTnCvj4XEcBVdC3g+/jftceluiwSTNRAX4VBOJdNt18jA==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@babel/parser': 7.25.4 '@babel/traverse': 7.25.4 @@ -6210,8 +1914,13 @@ snapshots: - supports-color - uglify-js - webpack-cli + dev: false - '@docusaurus/module-type-aliases@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)': + /@docusaurus/module-type-aliases@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2): + resolution: {integrity: sha512-wDGW4IHKoOr9YuJgy7uYuKWrDrSpsUSDHLZnWQYM9fN7D5EpSmYHjFruUpKWVyxLpD/Wh0rW8hYZwdjJIQUQCQ==} + peerDependencies: + react: '*' + react-dom: '*' dependencies: '@docusaurus/react-loadable': 5.5.2(react@17.0.2) '@docusaurus/types': 2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) @@ -6222,14 +1931,20 @@ snapshots: react: 17.0.2 react-dom: 17.0.2(react@17.0.2) react-helmet-async: 2.0.5(react@17.0.2) - react-loadable: '@docusaurus/react-loadable@5.5.2(react@17.0.2)' + react-loadable: /@docusaurus/react-loadable@5.5.2(react@17.0.2) transitivePeerDependencies: - '@swc/core' - esbuild - uglify-js - webpack-cli + dev: false - '@docusaurus/plugin-content-blog@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/plugin-content-blog@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-0mWBinEh0a5J2+8ZJXJXbrCk1tSTNf7Nm4tYAl5h2/xx+PvH/Bnu0V+7mMljYm/1QlDYALNIIaT/JcoZQFUN3w==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/logger': 2.2.0 @@ -6266,8 +1981,14 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/plugin-content-docs@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/plugin-content-docs@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-BOazBR0XjzsHE+2K1wpNxz5QZmrJgmm3+0Re0EVPYFGW8qndCWGNtXW/0lGKhecVPML8yyFeAmnUCIs7xM2wPw==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/logger': 2.2.0 @@ -6304,8 +2025,14 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/plugin-content-pages@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/plugin-content-pages@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-+OTK3FQHk5WMvdelz8v19PbEbx+CNT6VSpx7nVOvMNs5yJCKvmqBJBQ2ZSxROxhVDYn+CZOlmyrC56NSXzHf6g==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/mdx-loader': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) @@ -6334,8 +2061,14 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/plugin-debug@2.2.0(@swc/core@1.7.18)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/plugin-debug@2.2.0(@swc/core@1.7.18)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-p9vOep8+7OVl6r/NREEYxf4HMAjV8JMYJ7Bos5fCFO0Wyi9AZEo0sCTliRd7R8+dlJXZEgcngSdxAUo/Q+CJow==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/types': 2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) @@ -6364,8 +2097,14 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/plugin-google-analytics@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/plugin-google-analytics@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-+eZVVxVeEnV5nVQJdey9ZsfyEVMls6VyWTIj8SmX0k5EbqGvnIfET+J2pYEuKQnDIHxy+syRMoRM6AHXdHYGIg==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/types': 2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) @@ -6390,8 +2129,14 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/plugin-google-gtag@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/plugin-google-gtag@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-6SOgczP/dYdkqUMGTRqgxAS1eTp6MnJDAQMy8VCF1QKbWZmlkx4agHDexihqmYyCujTYHqDAhm1hV26EET54NQ==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/types': 2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) @@ -6416,8 +2161,14 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/plugin-sitemap@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/plugin-sitemap@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-0jAmyRDN/aI265CbWZNZuQpFqiZuo+5otk2MylU9iVrz/4J7gSc+ZJ9cy4EHrEsW7PV8s1w18hIEsmcA1YgkKg==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/logger': 2.2.0 @@ -6447,8 +2198,14 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/preset-classic@2.2.0(@algolia/client-search@4.24.0)(@swc/core@1.7.18)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(search-insights@2.17.0)(typescript@5.5.4)': + /@docusaurus/preset-classic@2.2.0(@algolia/client-search@4.24.0)(@swc/core@1.7.18)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(search-insights@2.17.0)(typescript@5.5.4): + resolution: {integrity: sha512-yKIWPGNx7BT8v2wjFIWvYrS+nvN04W+UameSFf8lEiJk6pss0kL6SG2MRvyULiI3BDxH+tj6qe02ncpSPGwumg==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/plugin-content-blog': 2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) @@ -6485,14 +2242,24 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/react-loadable@5.5.2(react@17.0.2)': + /@docusaurus/react-loadable@5.5.2(react@17.0.2): + resolution: {integrity: sha512-A3dYjdBGuy0IGT+wyLIGIKLRE+sAk1iNk0f1HjNDysO7u8lhL4N3VEm+FAubmJbAztn94F7MxBTPmnixbiyFdQ==} + peerDependencies: + react: '*' dependencies: '@types/react': 18.3.4 prop-types: 15.8.1 react: 17.0.2 + dev: false - '@docusaurus/theme-classic@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/theme-classic@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-kjbg/qJPwZ6H1CU/i9d4l/LcFgnuzeiGgMQlt6yPqKo0SOJIBMPuz7Rnu3r/WWbZFPi//o8acclacOzmXdUUEg==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/mdx-loader': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) @@ -6538,8 +2305,14 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/theme-common@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4)': + /@docusaurus/theme-common@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-R8BnDjYoN90DCL75gP7qYQfSjyitXuP9TdzgsKDmSFPNyrdE3twtPNa2dIN+h+p/pr+PagfxwWbd6dn722A1Dw==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docusaurus/mdx-loader': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) '@docusaurus/module-type-aliases': 2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) @@ -6575,8 +2348,14 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/theme-search-algolia@2.2.0(@algolia/client-search@4.24.0)(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(search-insights@2.17.0)(typescript@5.5.4)': + /@docusaurus/theme-search-algolia@2.2.0(@algolia/client-search@4.24.0)(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(search-insights@2.17.0)(typescript@5.5.4): + resolution: {integrity: sha512-2h38B0tqlxgR2FZ9LpAkGrpDWVdXZ7vltfmTdX+4RsDs3A7khiNsmZB+x/x6sA4+G2V2CvrsPMlsYBy5X+cY1w==} + engines: {node: '>=16.14'} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@docsearch/react': 3.6.1(@algolia/client-search@4.24.0)(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2)(search-insights@2.17.0) '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) @@ -6617,13 +2396,21 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - '@docusaurus/theme-translations@2.2.0': + /@docusaurus/theme-translations@2.2.0: + resolution: {integrity: sha512-3T140AG11OjJrtKlY4pMZ5BzbGRDjNs2co5hJ6uYJG1bVWlhcaFGqkaZ5lCgKflaNHD7UHBHU9Ec5f69jTdd6w==} + engines: {node: '>=16.14'} dependencies: fs-extra: 10.1.0 tslib: 2.7.0 + dev: false - '@docusaurus/types@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)': + /@docusaurus/types@2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2): + resolution: {integrity: sha512-b6xxyoexfbRNRI8gjblzVOnLr4peCJhGbYGPpJ3LFqpi5nsFfoK4mmDLvWdeah0B7gmJeXabN7nQkFoqeSdmOw==} + peerDependencies: + react: ^16.8.4 || ^17.0.0 + react-dom: ^16.8.4 || ^17.0.0 dependencies: '@types/history': 4.7.11 '@types/react': 18.3.4 @@ -6640,13 +2427,24 @@ snapshots: - esbuild - uglify-js - webpack-cli + dev: false - '@docusaurus/utils-common@2.2.0(@docusaurus/types@2.2.0)': + /@docusaurus/utils-common@2.2.0(@docusaurus/types@2.2.0): + resolution: {integrity: sha512-qebnerHp+cyovdUseDQyYFvMW1n1nv61zGe5JJfoNQUnjKuApch3IVsz+/lZ9a38pId8kqehC1Ao2bW/s0ntDA==} + engines: {node: '>=16.14'} + peerDependencies: + '@docusaurus/types': '*' + peerDependenciesMeta: + '@docusaurus/types': + optional: true dependencies: '@docusaurus/types': 2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) tslib: 2.7.0 + dev: false - '@docusaurus/utils-validation@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)': + /@docusaurus/utils-validation@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18): + resolution: {integrity: sha512-I1hcsG3yoCkasOL5qQAYAfnmVoLei7apugT6m4crQjmDGxq+UkiRrq55UqmDDyZlac/6ax/JC0p+usZ6W4nVyg==} + engines: {node: '>=16.14'} dependencies: '@docusaurus/logger': 2.2.0 '@docusaurus/utils': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18) @@ -6660,8 +2458,16 @@ snapshots: - supports-color - uglify-js - webpack-cli + dev: false - '@docusaurus/utils@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)': + /@docusaurus/utils@2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18): + resolution: {integrity: sha512-oNk3cjvx7Tt1Lgh/aeZAmFpGV2pDr5nHKrBVx6hTkzGhrnMuQqLt6UPlQjdYQ3QHXwyF/ZtZMO1D5Pfi0lu7SA==} + engines: {node: '>=16.14'} + peerDependencies: + '@docusaurus/types': '*' + peerDependenciesMeta: + '@docusaurus/types': + optional: true dependencies: '@docusaurus/logger': 2.2.0 '@docusaurus/types': 2.2.0(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2) @@ -6685,27 +2491,40 @@ snapshots: - supports-color - uglify-js - webpack-cli + dev: false - '@hapi/hoek@9.3.0': {} + /@hapi/hoek@9.3.0: + resolution: {integrity: sha512-/c6rf4UJlmHlC9b5BaNvzAcFv7HZ2QHaV0D4/HNlBdvFnvQq8RI4kYdhyPCl7Xj+oWvTWQ8ujhqS53LIgAe6KQ==} + dev: false - '@hapi/topo@5.1.0': + /@hapi/topo@5.1.0: + resolution: {integrity: sha512-foQZKJig7Ob0BMAYBfcJk8d77QtOe7Wo4ox7ff1lQYoNNAb6jwcY1ncdoy2e9wQZzvNy7ODZCYJkK8kzmcAnAg==} dependencies: '@hapi/hoek': 9.3.0 + dev: false - '@isaacs/cliui@8.0.2': + /@isaacs/cliui@8.0.2: + resolution: {integrity: sha512-O8jcjabXaleOG9DQ0+ARXWZBTfnP4WNAqzuiJK7ll44AmxGKv/J2M4TPjxjY3znBCfvBXFzucm1twdyFybFqEA==} + engines: {node: '>=12'} dependencies: string-width: 5.1.2 - string-width-cjs: string-width@4.2.3 + string-width-cjs: /string-width@4.2.3 strip-ansi: 7.1.0 - strip-ansi-cjs: strip-ansi@6.0.1 + strip-ansi-cjs: /strip-ansi@6.0.1 wrap-ansi: 8.1.0 - wrap-ansi-cjs: wrap-ansi@7.0.0 + wrap-ansi-cjs: /wrap-ansi@7.0.0 + dev: true - '@jest/schemas@29.6.3': + /@jest/schemas@29.6.3: + resolution: {integrity: sha512-mo5j5X+jIZmJQveBKeS/clAueipV7KgiX1vMgCxam1RNYiqE1w62n0/tJJnHtjW8ZHcQco5gY85jA3mi0L+nSA==} + engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} dependencies: '@sinclair/typebox': 0.27.8 + dev: false - '@jest/types@29.6.3': + /@jest/types@29.6.3: + resolution: {integrity: sha512-u3UPsIilWKOM3F9CXtrG8LEJmNxwoCQC/XVj4IKYXvvpx7QIi/Kg1LI5uDmDpKlac62NUtX7eLjRh+jVZcLOzw==} + engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} dependencies: '@jest/schemas': 29.6.3 '@types/istanbul-lib-coverage': 2.0.6 @@ -6713,32 +2532,51 @@ snapshots: '@types/node': 22.5.0 '@types/yargs': 17.0.33 chalk: 4.1.2 + dev: false - '@jridgewell/gen-mapping@0.3.5': + /@jridgewell/gen-mapping@0.3.5: + resolution: {integrity: sha512-IzL8ZoEDIBRWEzlCcRhOaCupYyN5gdIK+Q6fbFdPDg6HqX6jpkItn7DFIpW9LQzXG6Df9sA7+OKnq0qlz/GaQg==} + engines: {node: '>=6.0.0'} dependencies: '@jridgewell/set-array': 1.2.1 '@jridgewell/sourcemap-codec': 1.5.0 '@jridgewell/trace-mapping': 0.3.25 + dev: false - '@jridgewell/resolve-uri@3.1.2': {} + /@jridgewell/resolve-uri@3.1.2: + resolution: {integrity: sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==} + engines: {node: '>=6.0.0'} + dev: false - '@jridgewell/set-array@1.2.1': {} + /@jridgewell/set-array@1.2.1: + resolution: {integrity: sha512-R8gLRTZeyp03ymzP/6Lil/28tGeGEzhx1q2k703KGWRAI1VdvPIXdG70VJc2pAMw3NA6JKL5hhFu1sJX0Mnn/A==} + engines: {node: '>=6.0.0'} + dev: false - '@jridgewell/source-map@0.3.6': + /@jridgewell/source-map@0.3.6: + resolution: {integrity: sha512-1ZJTZebgqllO79ue2bm3rIGud/bOe0pP5BjSRCRxxYkEZS8STV7zN84UBbiYu7jy+eCKSnVIUgoWWE/tt+shMQ==} dependencies: '@jridgewell/gen-mapping': 0.3.5 '@jridgewell/trace-mapping': 0.3.25 + dev: false - '@jridgewell/sourcemap-codec@1.5.0': {} + /@jridgewell/sourcemap-codec@1.5.0: + resolution: {integrity: sha512-gv3ZRaISU3fjPAgNsriBRqGWQL6quFx04YMPW/zD8XMLsU32mhCCbfbO6KZFLjvYpCZ8zyDEgqsgf+PwPaM7GQ==} + dev: false - '@jridgewell/trace-mapping@0.3.25': + /@jridgewell/trace-mapping@0.3.25: + resolution: {integrity: sha512-vNk6aEwybGtawWmy/PzwnGDOjCkLWSD2wqvjGGAgOAwCGWySYXfYoxt00IJkTF+8Lb57DwOb3Aa0o9CApepiYQ==} dependencies: '@jridgewell/resolve-uri': 3.1.2 '@jridgewell/sourcemap-codec': 1.5.0 + dev: false - '@leichtgewicht/ip-codec@2.0.5': {} + /@leichtgewicht/ip-codec@2.0.5: + resolution: {integrity: sha512-Vo+PSpZG2/fmgmiNzYK9qWRh8h/CHrwD0mo1h1DzL4yzHNSfWYujGTYsWGreD000gcgmZ7K4Ys6Tx9TxtsKdDw==} + dev: false - '@mdx-js/mdx@1.6.22': + /@mdx-js/mdx@1.6.22: + resolution: {integrity: sha512-AMxuLxPz2j5/6TpF/XSdKpQP1NlG0z11dFOlq+2IP/lSgl11GY8ji6S/rgsViN/L0BDvHvUMruRb7ub+24LUYA==} dependencies: '@babel/core': 7.12.9 '@babel/plugin-syntax-jsx': 7.12.1(@babel/core@7.12.9) @@ -6761,97 +2599,199 @@ snapshots: unist-util-visit: 2.0.3 transitivePeerDependencies: - supports-color + dev: false - '@mdx-js/react@1.6.22(react@17.0.2)': + /@mdx-js/react@1.6.22(react@17.0.2): + resolution: {integrity: sha512-TDoPum4SHdfPiGSAaRBw7ECyI8VaHpK8GJugbJIJuqyh6kzw9ZLJZW3HGL3NNrJGxcAixUvqROm+YuQOo5eXtg==} + peerDependencies: + react: ^16.13.1 || ^17.0.0 dependencies: react: 17.0.2 + dev: false - '@mdx-js/util@1.6.22': {} + /@mdx-js/util@1.6.22: + resolution: {integrity: sha512-H1rQc1ZOHANWBvPcW+JpGwr+juXSxM8Q8YCkm3GhZd8REu1fHR3z99CErO1p9pkcfcxZnMdIZdIsXkOHY0NilA==} + dev: false - '@nodelib/fs.scandir@2.1.5': + /@nodelib/fs.scandir@2.1.5: + resolution: {integrity: sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==} + engines: {node: '>= 8'} dependencies: '@nodelib/fs.stat': 2.0.5 run-parallel: 1.2.0 + dev: false - '@nodelib/fs.stat@2.0.5': {} + /@nodelib/fs.stat@2.0.5: + resolution: {integrity: sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==} + engines: {node: '>= 8'} + dev: false - '@nodelib/fs.walk@1.2.8': + /@nodelib/fs.walk@1.2.8: + resolution: {integrity: sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==} + engines: {node: '>= 8'} dependencies: '@nodelib/fs.scandir': 2.1.5 fastq: 1.17.1 + dev: false - '@pkgjs/parseargs@0.11.0': + /@pkgjs/parseargs@0.11.0: + resolution: {integrity: sha512-+1VkjdD0QBLPodGrJUeqarH8VAIvQODIbwh9XpP5Syisf7YoQgsJKPNFoqqLQlu+VQ/tVSshMR6loPMn8U+dPg==} + engines: {node: '>=14'} + requiresBuild: true + dev: true optional: true - '@polka/url@1.0.0-next.25': {} + /@polka/url@1.0.0-next.25: + resolution: {integrity: sha512-j7P6Rgr3mmtdkeDGTe0E/aYyWEWVtc5yFXtHCRHs28/jptDEWfaVOc5T7cblqy1XKPPfCxJc/8DwQ5YgLOZOVQ==} + dev: false - '@sideway/address@4.1.5': + /@sideway/address@4.1.5: + resolution: {integrity: sha512-IqO/DUQHUkPeixNQ8n0JA6102hT9CmaljNTPmQ1u8MEhBo/R4Q8eKLN/vGZxuebwOroDB4cbpjheD4+/sKFK4Q==} dependencies: '@hapi/hoek': 9.3.0 + dev: false - '@sideway/formula@3.0.1': {} + /@sideway/formula@3.0.1: + resolution: {integrity: sha512-/poHZJJVjx3L+zVD6g9KgHfYnb443oi7wLu/XKojDviHy6HOEOA6z1Trk5aR1dGcmPenJEgb2sK2I80LeS3MIg==} + dev: false - '@sideway/pinpoint@2.0.0': {} + /@sideway/pinpoint@2.0.0: + resolution: {integrity: sha512-RNiOoTPkptFtSVzQevY/yWtZwf/RxyVnPy/OcA9HBM3MlGDnBEYL5B41H0MTn0Uec8Hi+2qUtTfG2WWZBmMejQ==} + dev: false - '@sinclair/typebox@0.27.8': {} + /@sinclair/typebox@0.27.8: + resolution: {integrity: sha512-+Fj43pSMwJs4KRrH/938Uf+uAELIgVBmQzg/q1YG10djyfA3TnrU8N8XzqCh/okZdszqBQTZf96idMfE5lnwTA==} + dev: false - '@sindresorhus/is@0.14.0': {} + /@sindresorhus/is@0.14.0: + resolution: {integrity: sha512-9NET910DNaIPngYnLLPeg+Ogzqsi9uM4mSboU5y6p8S5DzMTVEsJZrawi+BoDNUVBa2DhJqQYUFvMDfgU062LQ==} + engines: {node: '>=6'} + dev: false - '@slorber/static-site-generator-webpack-plugin@4.0.7': + /@slorber/static-site-generator-webpack-plugin@4.0.7: + resolution: {integrity: sha512-Ug7x6z5lwrz0WqdnNFOMYrDQNTPAprvHLSh6+/fmml3qUiz6l5eq+2MzLKWtn/q5K5NpSiFsZTP/fck/3vjSxA==} + engines: {node: '>=14'} dependencies: eval: 0.1.8 p-map: 4.0.0 webpack-sources: 3.2.3 + dev: false - '@svgr/babel-plugin-add-jsx-attribute@5.4.0': {} + /@svgr/babel-plugin-add-jsx-attribute@5.4.0: + resolution: {integrity: sha512-ZFf2gs/8/6B8PnSofI0inYXr2SDNTDScPXhN7k5EqD4aZ3gi6u+rbmZHVB8IM3wDyx8ntKACZbtXSm7oZGRqVg==} + engines: {node: '>=10'} + dev: false - '@svgr/babel-plugin-add-jsx-attribute@6.5.1(@babel/core@7.25.2)': + /@svgr/babel-plugin-add-jsx-attribute@6.5.1(@babel/core@7.25.2): + resolution: {integrity: sha512-9PYGcXrAxitycIjRmZB+Q0JaN07GZIWaTBIGQzfaZv+qr1n8X1XUEJ5rZ/vx6OVD9RRYlrNnXWExQXcmZeD/BQ==} + engines: {node: '>=10'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 + dev: false - '@svgr/babel-plugin-remove-jsx-attribute@5.4.0': {} + /@svgr/babel-plugin-remove-jsx-attribute@5.4.0: + resolution: {integrity: sha512-yaS4o2PgUtwLFGTKbsiAy6D0o3ugcUhWK0Z45umJ66EPWunAz9fuFw2gJuje6wqQvQWOTJvIahUwndOXb7QCPg==} + engines: {node: '>=10'} + dev: false - '@svgr/babel-plugin-remove-jsx-attribute@8.0.0(@babel/core@7.25.2)': + /@svgr/babel-plugin-remove-jsx-attribute@8.0.0(@babel/core@7.25.2): + resolution: {integrity: sha512-BcCkm/STipKvbCl6b7QFrMh/vx00vIP63k2eM66MfHJzPr6O2U0jYEViXkHJWqXqQYjdeA9cuCl5KWmlwjDvbA==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 + dev: false - '@svgr/babel-plugin-remove-jsx-empty-expression@5.0.1': {} + /@svgr/babel-plugin-remove-jsx-empty-expression@5.0.1: + resolution: {integrity: sha512-LA72+88A11ND/yFIMzyuLRSMJ+tRKeYKeQ+mR3DcAZ5I4h5CPWN9AHyUzJbWSYp/u2u0xhmgOe0+E41+GjEueA==} + engines: {node: '>=10'} + dev: false - '@svgr/babel-plugin-remove-jsx-empty-expression@8.0.0(@babel/core@7.25.2)': + /@svgr/babel-plugin-remove-jsx-empty-expression@8.0.0(@babel/core@7.25.2): + resolution: {integrity: sha512-5BcGCBfBxB5+XSDSWnhTThfI9jcO5f0Ai2V24gZpG+wXF14BzwxxdDb4g6trdOux0rhibGs385BeFMSmxtS3uA==} + engines: {node: '>=14'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 + dev: false - '@svgr/babel-plugin-replace-jsx-attribute-value@5.0.1': {} + /@svgr/babel-plugin-replace-jsx-attribute-value@5.0.1: + resolution: {integrity: sha512-PoiE6ZD2Eiy5mK+fjHqwGOS+IXX0wq/YDtNyIgOrc6ejFnxN4b13pRpiIPbtPwHEc+NT2KCjteAcq33/F1Y9KQ==} + engines: {node: '>=10'} + dev: false - '@svgr/babel-plugin-replace-jsx-attribute-value@6.5.1(@babel/core@7.25.2)': + /@svgr/babel-plugin-replace-jsx-attribute-value@6.5.1(@babel/core@7.25.2): + resolution: {integrity: sha512-8DPaVVE3fd5JKuIC29dqyMB54sA6mfgki2H2+swh+zNJoynC8pMPzOkidqHOSc6Wj032fhl8Z0TVn1GiPpAiJg==} + engines: {node: '>=10'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 + dev: false - '@svgr/babel-plugin-svg-dynamic-title@5.4.0': {} + /@svgr/babel-plugin-svg-dynamic-title@5.4.0: + resolution: {integrity: sha512-zSOZH8PdZOpuG1ZVx/cLVePB2ibo3WPpqo7gFIjLV9a0QsuQAzJiwwqmuEdTaW2pegyBE17Uu15mOgOcgabQZg==} + engines: {node: '>=10'} + dev: false - '@svgr/babel-plugin-svg-dynamic-title@6.5.1(@babel/core@7.25.2)': + /@svgr/babel-plugin-svg-dynamic-title@6.5.1(@babel/core@7.25.2): + resolution: {integrity: sha512-FwOEi0Il72iAzlkaHrlemVurgSQRDFbk0OC8dSvD5fSBPHltNh7JtLsxmZUhjYBZo2PpcU/RJvvi6Q0l7O7ogw==} + engines: {node: '>=10'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 + dev: false - '@svgr/babel-plugin-svg-em-dimensions@5.4.0': {} + /@svgr/babel-plugin-svg-em-dimensions@5.4.0: + resolution: {integrity: sha512-cPzDbDA5oT/sPXDCUYoVXEmm3VIoAWAPT6mSPTJNbQaBNUuEKVKyGH93oDY4e42PYHRW67N5alJx/eEol20abw==} + engines: {node: '>=10'} + dev: false - '@svgr/babel-plugin-svg-em-dimensions@6.5.1(@babel/core@7.25.2)': + /@svgr/babel-plugin-svg-em-dimensions@6.5.1(@babel/core@7.25.2): + resolution: {integrity: sha512-gWGsiwjb4tw+ITOJ86ndY/DZZ6cuXMNE/SjcDRg+HLuCmwpcjOktwRF9WgAiycTqJD/QXqL2f8IzE2Rzh7aVXA==} + engines: {node: '>=10'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 + dev: false - '@svgr/babel-plugin-transform-react-native-svg@5.4.0': {} + /@svgr/babel-plugin-transform-react-native-svg@5.4.0: + resolution: {integrity: sha512-3eYP/SaopZ41GHwXma7Rmxcv9uRslRDTY1estspeB1w1ueZWd/tPlMfEOoccYpEMZU3jD4OU7YitnXcF5hLW2Q==} + engines: {node: '>=10'} + dev: false - '@svgr/babel-plugin-transform-react-native-svg@6.5.1(@babel/core@7.25.2)': + /@svgr/babel-plugin-transform-react-native-svg@6.5.1(@babel/core@7.25.2): + resolution: {integrity: sha512-2jT3nTayyYP7kI6aGutkyfJ7UMGtuguD72OjeGLwVNyfPRBD8zQthlvL+fAbAKk5n9ZNcvFkp/b1lZ7VsYqVJg==} + engines: {node: '>=10'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 + dev: false - '@svgr/babel-plugin-transform-svg-component@5.5.0': {} + /@svgr/babel-plugin-transform-svg-component@5.5.0: + resolution: {integrity: sha512-q4jSH1UUvbrsOtlo/tKcgSeiCHRSBdXoIoqX1pgcKK/aU3JD27wmMKwGtpB8qRYUYoyXvfGxUVKchLuR5pB3rQ==} + engines: {node: '>=10'} + dev: false - '@svgr/babel-plugin-transform-svg-component@6.5.1(@babel/core@7.25.2)': + /@svgr/babel-plugin-transform-svg-component@6.5.1(@babel/core@7.25.2): + resolution: {integrity: sha512-a1p6LF5Jt33O3rZoVRBqdxL350oge54iZWHNI6LJB5tQ7EelvD/Mb1mfBiZNAan0dt4i3VArkFRjA4iObuNykQ==} + engines: {node: '>=12'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 + dev: false - '@svgr/babel-preset@5.5.0': + /@svgr/babel-preset@5.5.0: + resolution: {integrity: sha512-4FiXBjvQ+z2j7yASeGPEi8VD/5rrGQk4Xrq3EdJmoZgz/tpqChpo5hgXDvmEauwtvOc52q8ghhZK4Oy7qph4ig==} + engines: {node: '>=10'} dependencies: '@svgr/babel-plugin-add-jsx-attribute': 5.4.0 '@svgr/babel-plugin-remove-jsx-attribute': 5.4.0 @@ -6861,8 +2801,13 @@ snapshots: '@svgr/babel-plugin-svg-em-dimensions': 5.4.0 '@svgr/babel-plugin-transform-react-native-svg': 5.4.0 '@svgr/babel-plugin-transform-svg-component': 5.5.0 + dev: false - '@svgr/babel-preset@6.5.1(@babel/core@7.25.2)': + /@svgr/babel-preset@6.5.1(@babel/core@7.25.2): + resolution: {integrity: sha512-6127fvO/FF2oi5EzSQOAjo1LE3OtNVh11R+/8FXa+mHx1ptAaS4cknIjnUA7e6j6fwGGJ17NzaTJFUwOV2zwCw==} + engines: {node: '>=10'} + peerDependencies: + '@babel/core': ^7.0.0-0 dependencies: '@babel/core': 7.25.2 '@svgr/babel-plugin-add-jsx-attribute': 6.5.1(@babel/core@7.25.2) @@ -6873,16 +2818,22 @@ snapshots: '@svgr/babel-plugin-svg-em-dimensions': 6.5.1(@babel/core@7.25.2) '@svgr/babel-plugin-transform-react-native-svg': 6.5.1(@babel/core@7.25.2) '@svgr/babel-plugin-transform-svg-component': 6.5.1(@babel/core@7.25.2) + dev: false - '@svgr/core@5.5.0': + /@svgr/core@5.5.0: + resolution: {integrity: sha512-q52VOcsJPvV3jO1wkPtzTuKlvX7Y3xIcWRpCMtBF3MrteZJtBfQw/+u0B1BHy5ColpQc1/YVTrPEtSYIMNZlrQ==} + engines: {node: '>=10'} dependencies: '@svgr/plugin-jsx': 5.5.0 camelcase: 6.3.0 cosmiconfig: 7.1.0 transitivePeerDependencies: - supports-color + dev: false - '@svgr/core@6.5.1': + /@svgr/core@6.5.1: + resolution: {integrity: sha512-/xdLSWxK5QkqG524ONSjvg3V/FkNyCv538OIBdQqPNaAta3AsXj/Bd2FbvR87yMbXO2hFSWiAe/Q6IkVPDw+mw==} + engines: {node: '>=10'} dependencies: '@babel/core': 7.25.2 '@svgr/babel-preset': 6.5.1(@babel/core@7.25.2) @@ -6891,17 +2842,26 @@ snapshots: cosmiconfig: 7.1.0 transitivePeerDependencies: - supports-color + dev: false - '@svgr/hast-util-to-babel-ast@5.5.0': + /@svgr/hast-util-to-babel-ast@5.5.0: + resolution: {integrity: sha512-cAaR/CAiZRB8GP32N+1jocovUtvlj0+e65TB50/6Lcime+EA49m/8l+P2ko+XPJ4dw3xaPS3jOL4F2X4KWxoeQ==} + engines: {node: '>=10'} dependencies: '@babel/types': 7.25.4 + dev: false - '@svgr/hast-util-to-babel-ast@6.5.1': + /@svgr/hast-util-to-babel-ast@6.5.1: + resolution: {integrity: sha512-1hnUxxjd83EAxbL4a0JDJoD3Dao3hmjvyvyEV8PzWmLK3B9m9NPlW7GKjFyoWE8nM7HnXzPcmmSyOW8yOddSXw==} + engines: {node: '>=10'} dependencies: '@babel/types': 7.25.4 entities: 4.5.0 + dev: false - '@svgr/plugin-jsx@5.5.0': + /@svgr/plugin-jsx@5.5.0: + resolution: {integrity: sha512-V/wVh33j12hGh05IDg8GpIUXbjAPnTdPTKuP4VNLggnwaHMPNQNae2pRnyTAILWCQdz5GyMqtO488g7CKM8CBA==} + engines: {node: '>=10'} dependencies: '@babel/core': 7.25.2 '@svgr/babel-preset': 5.5.0 @@ -6909,8 +2869,13 @@ snapshots: svg-parser: 2.0.4 transitivePeerDependencies: - supports-color + dev: false - '@svgr/plugin-jsx@6.5.1(@svgr/core@6.5.1)': + /@svgr/plugin-jsx@6.5.1(@svgr/core@6.5.1): + resolution: {integrity: sha512-+UdQxI3jgtSjCykNSlEMuy1jSRQlGC7pqBCPvkG/2dATdWo082zHTTK3uhnAju2/6XpE6B5mZ3z4Z8Ns01S8Gw==} + engines: {node: '>=10'} + peerDependencies: + '@svgr/core': ^6.0.0 dependencies: '@babel/core': 7.25.2 '@svgr/babel-preset': 6.5.1(@babel/core@7.25.2) @@ -6919,21 +2884,32 @@ snapshots: svg-parser: 2.0.4 transitivePeerDependencies: - supports-color + dev: false - '@svgr/plugin-svgo@5.5.0': + /@svgr/plugin-svgo@5.5.0: + resolution: {integrity: sha512-r5swKk46GuQl4RrVejVwpeeJaydoxkdwkM1mBKOgJLBUJPGaLci6ylg/IjhrRsREKDkr4kbMWdgOtbXEh0fyLQ==} + engines: {node: '>=10'} dependencies: cosmiconfig: 7.1.0 deepmerge: 4.3.1 svgo: 1.3.2 + dev: false - '@svgr/plugin-svgo@6.5.1(@svgr/core@6.5.1)': + /@svgr/plugin-svgo@6.5.1(@svgr/core@6.5.1): + resolution: {integrity: sha512-omvZKf8ixP9z6GWgwbtmP9qQMPX4ODXi+wzbVZgomNFsUIlHA1sf4fThdwTWSsZGgvGAG6yE+b/F5gWUkcZ/iQ==} + engines: {node: '>=10'} + peerDependencies: + '@svgr/core': '*' dependencies: '@svgr/core': 6.5.1 cosmiconfig: 7.1.0 deepmerge: 4.3.1 svgo: 2.8.0 + dev: false - '@svgr/webpack@5.5.0': + /@svgr/webpack@5.5.0: + resolution: {integrity: sha512-DOBOK255wfQxguUta2INKkzPj6AIS6iafZYiYmHn6W3pHlycSRRlvWKCfLDG10fXfLWqE3DJHgRUOyJYmARa7g==} + engines: {node: '>=10'} dependencies: '@babel/core': 7.25.2 '@babel/plugin-transform-react-constant-elements': 7.25.1(@babel/core@7.25.2) @@ -6945,8 +2921,11 @@ snapshots: loader-utils: 2.0.4 transitivePeerDependencies: - supports-color + dev: false - '@svgr/webpack@6.5.1': + /@svgr/webpack@6.5.1: + resolution: {integrity: sha512-cQ/AsnBkXPkEK8cLbv4Dm7JGXq2XrumKnL1dRpJD9rIO2fTIlJI9a1uCciYG1F2aUsox/hJQyNGbt3soDxSRkA==} + engines: {node: '>=10'} dependencies: '@babel/core': 7.25.2 '@babel/plugin-transform-react-constant-elements': 7.25.1(@babel/core@7.25.2) @@ -6958,38 +2937,107 @@ snapshots: '@svgr/plugin-svgo': 6.5.1(@svgr/core@6.5.1) transitivePeerDependencies: - supports-color + dev: false - '@swc/core-darwin-arm64@1.7.18': + /@swc/core-darwin-arm64@1.7.18: + resolution: {integrity: sha512-MwLc5U+VGPMZm8MjlFBjEB2wyT1EK0NNJ3tn+ps9fmxdFP+PL8EpMiY1O1F2t1ydy2OzBtZz81sycjM9RieFBg==} + engines: {node: '>=10'} + cpu: [arm64] + os: [darwin] + requiresBuild: true + dev: false optional: true - '@swc/core-darwin-x64@1.7.18': + /@swc/core-darwin-x64@1.7.18: + resolution: {integrity: sha512-IkukOQUw7/14VkHp446OkYGCZEHqZg9pTmTdBawlUyz2JwZMSn2VodCl7aFSdGCsU4Cwni8zKA8CCgkCCAELhw==} + engines: {node: '>=10'} + cpu: [x64] + os: [darwin] + requiresBuild: true + dev: false optional: true - '@swc/core-linux-arm-gnueabihf@1.7.18': + /@swc/core-linux-arm-gnueabihf@1.7.18: + resolution: {integrity: sha512-ATnb6jJaBeXCqrTUawWdoOy7eP9SCI7UMcfXlYIMxX4otKKspLPAEuGA5RaNxlCcj9ObyO0J3YGbtZ6hhD2pjg==} + engines: {node: '>=10'} + cpu: [arm] + os: [linux] + requiresBuild: true + dev: false optional: true - '@swc/core-linux-arm64-gnu@1.7.18': + /@swc/core-linux-arm64-gnu@1.7.18: + resolution: {integrity: sha512-poHtH7zL7lEp9K2inY90lGHJABWxURAOgWNeZqrcR5+jwIe7q5KBisysH09Zf/JNF9+6iNns+U0xgWTNJzBuGA==} + engines: {node: '>=10'} + cpu: [arm64] + os: [linux] + requiresBuild: true + dev: false optional: true - '@swc/core-linux-arm64-musl@1.7.18': + /@swc/core-linux-arm64-musl@1.7.18: + resolution: {integrity: sha512-qnNI1WmcOV7Wz1ZDyK6WrOlzLvJ01rnni8ec950mMHWkLRMP53QvCvhF3S+7gFplWBwWJTOOPPUqJp/PlSxWyQ==} + engines: {node: '>=10'} + cpu: [arm64] + os: [linux] + requiresBuild: true + dev: false optional: true - '@swc/core-linux-x64-gnu@1.7.18': + /@swc/core-linux-x64-gnu@1.7.18: + resolution: {integrity: sha512-x9SCqCLzwtlqtD5At3I1a7Gco+EuXnzrJGoucmkpeQohshHuwa+cskqsXO6u1Dz0jXJEuHbBZB9va1wYYfjgFg==} + engines: {node: '>=10'} + cpu: [x64] + os: [linux] + requiresBuild: true + dev: false optional: true - '@swc/core-linux-x64-musl@1.7.18': + /@swc/core-linux-x64-musl@1.7.18: + resolution: {integrity: sha512-qtj8iOpMMgKjzxTv+islmEY0JBsbd93nka0gzcTTmGZxKtL5jSUsYQvkxwNPZr5M9NU1fgaR3n1vE6lFmtY0IQ==} + engines: {node: '>=10'} + cpu: [x64] + os: [linux] + requiresBuild: true + dev: false optional: true - '@swc/core-win32-arm64-msvc@1.7.18': + /@swc/core-win32-arm64-msvc@1.7.18: + resolution: {integrity: sha512-ltX/Ol9+Qu4SXmISCeuwVgAjSa8nzHTymknpozzVMgjXUoZMoz6lcynfKL1nCh5XLgqh0XNHUKLti5YFF8LrrA==} + engines: {node: '>=10'} + cpu: [arm64] + os: [win32] + requiresBuild: true + dev: false optional: true - '@swc/core-win32-ia32-msvc@1.7.18': + /@swc/core-win32-ia32-msvc@1.7.18: + resolution: {integrity: sha512-RgTcFP3wgyxnQbTCJrlgBJmgpeTXo8t807GU9GxApAXfpLZJ3swJ2GgFUmIJVdLWyffSHF5BEkF3FmF6mtH5AQ==} + engines: {node: '>=10'} + cpu: [ia32] + os: [win32] + requiresBuild: true + dev: false optional: true - '@swc/core-win32-x64-msvc@1.7.18': + /@swc/core-win32-x64-msvc@1.7.18: + resolution: {integrity: sha512-XbZ0wAgzR757+DhQcnv60Y/bK9yuWPhDNRQVFFQVRsowvK3+c6EblyfUSytIidpXgyYFzlprq/9A9ZlO/wvDWw==} + engines: {node: '>=10'} + cpu: [x64] + os: [win32] + requiresBuild: true + dev: false optional: true - '@swc/core@1.7.18': + /@swc/core@1.7.18: + resolution: {integrity: sha512-qL9v5N5S38ijmqiQRvCFUUx2vmxWT/JJ2rswElnyaHkOHuVoAFhBB90Ywj4RKjh3R0zOjhEcemENTyF3q3G6WQ==} + engines: {node: '>=10'} + requiresBuild: true + peerDependencies: + '@swc/helpers': '*' + peerDependenciesMeta: + '@swc/helpers': + optional: true dependencies: '@swc/counter': 0.1.3 '@swc/types': 0.1.12 @@ -7004,211 +3052,329 @@ snapshots: '@swc/core-win32-arm64-msvc': 1.7.18 '@swc/core-win32-ia32-msvc': 1.7.18 '@swc/core-win32-x64-msvc': 1.7.18 + dev: false - '@swc/counter@0.1.3': {} + /@swc/counter@0.1.3: + resolution: {integrity: sha512-e2BR4lsJkkRlKZ/qCHPw9ZaSxc0MVUd7gtbtaB7aMvHeJVYe8sOB8DBZkP2DtISHGSku9sCK6T6cnY0CtXrOCQ==} + dev: false - '@swc/types@0.1.12': + /@swc/types@0.1.12: + resolution: {integrity: sha512-wBJA+SdtkbFhHjTMYH+dEH1y4VpfGdAc2Kw/LK09i9bXd/K6j6PkDcFCEzb6iVfZMkPRrl/q0e3toqTAJdkIVA==} dependencies: '@swc/counter': 0.1.3 + dev: false - '@szmarczak/http-timer@1.1.2': + /@szmarczak/http-timer@1.1.2: + resolution: {integrity: sha512-XIB2XbzHTN6ieIjfIMV9hlVcfPU26s2vafYWQcZHWXHOxiaRZYEDKEwdl129Zyg50+foYV2jCgtrqSA6qNuNSA==} + engines: {node: '>=6'} dependencies: defer-to-connect: 1.1.3 + dev: false - '@trysound/sax@0.2.0': {} + /@trysound/sax@0.2.0: + resolution: {integrity: sha512-L7z9BgrNEcYyUYtF+HaEfiS5ebkh9jXqbszz7pC0hRBPaatV0XjSD3+eHrpqFemQfgwiFF0QPIarnIihIDn7OA==} + engines: {node: '>=10.13.0'} + dev: false - '@types/body-parser@1.19.5': + /@types/body-parser@1.19.5: + resolution: {integrity: sha512-fB3Zu92ucau0iQ0JMCFQE7b/dv8Ot07NI3KaZIkIUNXq82k4eBAqUaneXfleGY9JWskeS9y+u0nXMyspcuQrCg==} dependencies: '@types/connect': 3.4.38 '@types/node': 22.5.0 + dev: false - '@types/bonjour@3.5.13': + /@types/bonjour@3.5.13: + resolution: {integrity: sha512-z9fJ5Im06zvUL548KvYNecEVlA7cVDkGUi6kZusb04mpyEFKCIZJvloCcmpmLaIahDpOQGHaHmG6imtPMmPXGQ==} dependencies: '@types/node': 22.5.0 + dev: false - '@types/connect-history-api-fallback@1.5.4': + /@types/connect-history-api-fallback@1.5.4: + resolution: {integrity: sha512-n6Cr2xS1h4uAulPRdlw6Jl6s1oG8KrVilPN2yUITEs+K48EzMJJ3W1xy8K5eWuFvjp3R74AOIGSmp2UfBJ8HFw==} dependencies: '@types/express-serve-static-core': 4.19.5 '@types/node': 22.5.0 + dev: false - '@types/connect@3.4.38': + /@types/connect@3.4.38: + resolution: {integrity: sha512-K6uROf1LD88uDQqJCktA4yzL1YYAK6NgfsI0v/mTgyPKWsX1CnJ0XPSDhViejru1GcRkLWb8RlzFYJRqGUbaug==} dependencies: '@types/node': 22.5.0 + dev: false - '@types/estree@1.0.5': {} + /@types/estree@1.0.5: + resolution: {integrity: sha512-/kYRxGDLWzHOB7q+wtSUQlFrtcdUccpfy+X+9iMBpHK8QLLhx2wIPYuS5DYtR9Wa/YlZAbIovy7qVdB1Aq6Lyw==} + dev: false - '@types/express-serve-static-core@4.19.5': + /@types/express-serve-static-core@4.19.5: + resolution: {integrity: sha512-y6W03tvrACO72aijJ5uF02FRq5cgDR9lUxddQ8vyF+GvmjJQqbzDcJngEjURc+ZsG31VI3hODNZJ2URj86pzmg==} dependencies: '@types/node': 22.5.0 '@types/qs': 6.9.15 '@types/range-parser': 1.2.7 '@types/send': 0.17.4 + dev: false - '@types/express@4.17.21': + /@types/express@4.17.21: + resolution: {integrity: sha512-ejlPM315qwLpaQlQDTjPdsUFSc6ZsP4AN6AlWnogPjQ7CVi7PYF3YVz+CY3jE2pwYf7E/7HlDAN0rV2GxTG0HQ==} dependencies: '@types/body-parser': 1.19.5 '@types/express-serve-static-core': 4.19.5 '@types/qs': 6.9.15 '@types/serve-static': 1.15.7 + dev: false - '@types/hast@2.3.10': + /@types/hast@2.3.10: + resolution: {integrity: sha512-McWspRw8xx8J9HurkVBfYj0xKoE25tOFlHGdx4MJ5xORQrMGZNqJhVQWaIbm6Oyla5kYOXtDiopzKRJzEOkwJw==} dependencies: '@types/unist': 2.0.11 + dev: false - '@types/history@4.7.11': {} + /@types/history@4.7.11: + resolution: {integrity: sha512-qjDJRrmvBMiTx+jyLxvLfJU7UznFuokDv4f3WRuriHKERccVpFU+8XMQUAbDzoiJCsmexxRExQeMwwCdamSKDA==} + dev: false - '@types/html-minifier-terser@6.1.0': {} + /@types/html-minifier-terser@6.1.0: + resolution: {integrity: sha512-oh/6byDPnL1zeNXFrDXFLyZjkr1MsBG667IM792caf1L2UPOOMf65NFzjUH/ltyfwjAGfs1rsX1eftK0jC/KIg==} + dev: false - '@types/http-errors@2.0.4': {} + /@types/http-errors@2.0.4: + resolution: {integrity: sha512-D0CFMMtydbJAegzOyHjtiKPLlvnm3iTZyZRSZoLq2mRhDdmLfIWOCYPfQJ4cu2erKghU++QvjcUjp/5h7hESpA==} + dev: false - '@types/http-proxy@1.17.15': + /@types/http-proxy@1.17.15: + resolution: {integrity: sha512-25g5atgiVNTIv0LBDTg1H74Hvayx0ajtJPLLcYE3whFv75J0pWNtOBzaXJQgDTmrX1bx5U9YC2w/n65BN1HwRQ==} dependencies: '@types/node': 22.5.0 + dev: false - '@types/istanbul-lib-coverage@2.0.6': {} + /@types/istanbul-lib-coverage@2.0.6: + resolution: {integrity: sha512-2QF/t/auWm0lsy8XtKVPG19v3sSOQlJe/YHZgfjb/KBBHOGSV+J2q/S671rcq9uTBrLAXmZpqJiaQbMT+zNU1w==} + dev: false - '@types/istanbul-lib-report@3.0.3': + /@types/istanbul-lib-report@3.0.3: + resolution: {integrity: sha512-NQn7AHQnk/RSLOxrBbGyJM/aVQ+pjj5HCgasFxc0K/KhoATfQ/47AyUl15I2yBUpihjmas+a+VJBOqecrFH+uA==} dependencies: '@types/istanbul-lib-coverage': 2.0.6 + dev: false - '@types/istanbul-reports@3.0.4': + /@types/istanbul-reports@3.0.4: + resolution: {integrity: sha512-pk2B1NWalF9toCRu6gjBzR69syFjP4Od8WRAX+0mmf9lAjCRicLOWc+ZrxZHx/0XRjotgkF9t6iaMJ+aXcOdZQ==} dependencies: '@types/istanbul-lib-report': 3.0.3 + dev: false - '@types/json-schema@7.0.15': {} + /@types/json-schema@7.0.15: + resolution: {integrity: sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==} + dev: false - '@types/keyv@3.1.4': + /@types/keyv@3.1.4: + resolution: {integrity: sha512-BQ5aZNSCpj7D6K2ksrRCTmKRLEpnPvWDiLPfoGyhZ++8YtiK9d/3DBKPJgry359X/P1PfruyYwvnvwFjuEiEIg==} dependencies: '@types/node': 22.5.0 + dev: false - '@types/mdast@3.0.15': + /@types/mdast@3.0.15: + resolution: {integrity: sha512-LnwD+mUEfxWMa1QpDraczIn6k0Ee3SMicuYSSzS6ZYl2gKS09EClnJYGd8Du6rfc5r/GZEk5o1mRb8TaTj03sQ==} dependencies: '@types/unist': 2.0.11 + dev: false - '@types/mime@1.3.5': {} + /@types/mime@1.3.5: + resolution: {integrity: sha512-/pyBZWSLD2n0dcHE3hq8s8ZvcETHtEuF+3E7XVt0Ig2nvsVQXdghHVcEkIWjy9A0wKfTn97a/PSDYohKIlnP/w==} + dev: false - '@types/node-forge@1.3.11': + /@types/node-forge@1.3.11: + resolution: {integrity: sha512-FQx220y22OKNTqaByeBGqHWYz4cl94tpcxeFdvBo3wjG6XPBuZ0BNgNZRV5J5TFmmcsJ4IzsLkmGRiQbnYsBEQ==} dependencies: '@types/node': 22.5.0 + dev: false - '@types/node@17.0.45': {} + /@types/node@17.0.45: + resolution: {integrity: sha512-w+tIMs3rq2afQdsPJlODhoUEKzFP1ayaoyl1CcnwtIlsVe7K7bA1NGm4s3PraqTLlXnbIN84zuBlxBWo1u9BLw==} + dev: false - '@types/node@22.5.0': + /@types/node@22.5.0: + resolution: {integrity: sha512-DkFrJOe+rfdHTqqMg0bSNlGlQ85hSoh2TPzZyhHsXnMtligRWpxUySiyw8FY14ITt24HVCiQPWxS3KO/QlGmWg==} dependencies: undici-types: 6.19.8 + dev: false - '@types/parse-json@4.0.2': {} + /@types/parse-json@4.0.2: + resolution: {integrity: sha512-dISoDXWWQwUquiKsyZ4Ng+HX2KsPL7LyHKHQwgGFEA3IaKac4Obd+h2a/a6waisAoepJlBcx9paWqjA8/HVjCw==} + dev: false - '@types/parse5@5.0.3': {} + /@types/parse5@5.0.3: + resolution: {integrity: sha512-kUNnecmtkunAoQ3CnjmMkzNU/gtxG8guhi+Fk2U/kOpIKjIMKnXGp4IJCgQJrXSgMsWYimYG4TGjz/UzbGEBTw==} + dev: false - '@types/prop-types@15.7.12': {} + /@types/prop-types@15.7.12: + resolution: {integrity: sha512-5zvhXYtRNRluoE/jAp4GVsSduVUzNWKkOZrCDBWYtE7biZywwdC2AcEzg+cSMLFRfVgeAFqpfNabiPjxFddV1Q==} + dev: false - '@types/q@1.5.8': {} + /@types/q@1.5.8: + resolution: {integrity: sha512-hroOstUScF6zhIi+5+x0dzqrHA1EJi+Irri6b1fxolMTqqHIV/Cg77EtnQcZqZCu8hR3mX2BzIxN4/GzI68Kfw==} + dev: false - '@types/qs@6.9.15': {} + /@types/qs@6.9.15: + resolution: {integrity: sha512-uXHQKES6DQKKCLh441Xv/dwxOq1TVS3JPUMlEqoEglvlhR6Mxnlew/Xq/LRVHpLyk7iK3zODe1qYHIMltO7XGg==} + dev: false - '@types/range-parser@1.2.7': {} + /@types/range-parser@1.2.7: + resolution: {integrity: sha512-hKormJbkJqzQGhziax5PItDUTMAM9uE2XXQmM37dyd4hVM+5aVl7oVxMVUiVQn2oCQFN/LKCZdvSM0pFRqbSmQ==} + dev: false - '@types/react-router-config@5.0.11': + /@types/react-router-config@5.0.11: + resolution: {integrity: sha512-WmSAg7WgqW7m4x8Mt4N6ZyKz0BubSj/2tVUMsAHp+Yd2AMwcSbeFq9WympT19p5heCFmF97R9eD5uUR/t4HEqw==} dependencies: '@types/history': 4.7.11 '@types/react': 18.3.4 '@types/react-router': 5.1.20 + dev: false - '@types/react-router-dom@5.3.3': + /@types/react-router-dom@5.3.3: + resolution: {integrity: sha512-kpqnYK4wcdm5UaWI3fLcELopqLrHgLqNsdpHauzlQktfkHL3npOSwtj1Uz9oKBAzs7lFtVkV8j83voAz2D8fhw==} dependencies: '@types/history': 4.7.11 '@types/react': 18.3.4 '@types/react-router': 5.1.20 + dev: false - '@types/react-router@5.1.20': + /@types/react-router@5.1.20: + resolution: {integrity: sha512-jGjmu/ZqS7FjSH6owMcD5qpq19+1RS9DeVRqfl1FeBMxTDQAGwlMWOcs52NDoXaNKyG3d1cYQFMs9rCrb88o9Q==} dependencies: '@types/history': 4.7.11 '@types/react': 18.3.4 + dev: false - '@types/react@18.3.4': + /@types/react@18.3.4: + resolution: {integrity: sha512-J7W30FTdfCxDDjmfRM+/JqLHBIyl7xUIp9kwK637FGmY7+mkSFSe6L4jpZzhj5QMfLssSDP4/i75AKkrdC7/Jw==} dependencies: '@types/prop-types': 15.7.12 csstype: 3.1.3 + dev: false - '@types/responselike@1.0.3': + /@types/responselike@1.0.3: + resolution: {integrity: sha512-H/+L+UkTV33uf49PH5pCAUBVPNj2nDBXTN+qS1dOwyyg24l3CcicicCA7ca+HMvJBZcFgl5r8e+RR6elsb4Lyw==} dependencies: '@types/node': 22.5.0 + dev: false - '@types/retry@0.12.0': {} + /@types/retry@0.12.0: + resolution: {integrity: sha512-wWKOClTTiizcZhXnPY4wikVAwmdYHp8q6DmC+EJUzAMsycb7HB32Kh9RN4+0gExjmPmZSAQjgURXIGATPegAvA==} + dev: false - '@types/sax@1.2.7': + /@types/sax@1.2.7: + resolution: {integrity: sha512-rO73L89PJxeYM3s3pPPjiPgVVcymqU490g0YO5n5By0k2Erzj6tay/4lr1CHAAU4JyOWd1rpQ8bCf6cZfHU96A==} dependencies: '@types/node': 22.5.0 + dev: false - '@types/send@0.17.4': + /@types/send@0.17.4: + resolution: {integrity: sha512-x2EM6TJOybec7c52BX0ZspPodMsQUd5L6PRwOunVyVUhXiBSKf3AezDL8Dgvgt5o0UfKNfuA0eMLr2wLT4AiBA==} dependencies: '@types/mime': 1.3.5 '@types/node': 22.5.0 + dev: false - '@types/serve-index@1.9.4': + /@types/serve-index@1.9.4: + resolution: {integrity: sha512-qLpGZ/c2fhSs5gnYsQxtDEq3Oy8SXPClIXkW5ghvAvsNuVSA8k+gCONcUCS/UjLEYvYps+e8uBtfgXgvhwfNug==} dependencies: '@types/express': 4.17.21 + dev: false - '@types/serve-static@1.15.7': + /@types/serve-static@1.15.7: + resolution: {integrity: sha512-W8Ym+h8nhuRwaKPaDw34QUkwsGi6Rc4yYqvKFo5rm2FUEhCFbzVWrxXUxuKK8TASjWsysJY0nsmNCGhCOIsrOw==} dependencies: '@types/http-errors': 2.0.4 '@types/node': 22.5.0 '@types/send': 0.17.4 + dev: false - '@types/sockjs@0.3.36': + /@types/sockjs@0.3.36: + resolution: {integrity: sha512-MK9V6NzAS1+Ud7JV9lJLFqW85VbC9dq3LmwZCuBe4wBDgKC0Kj/jd8Xl+nSviU+Qc3+m7umHHyHg//2KSa0a0Q==} dependencies: '@types/node': 22.5.0 + dev: false - '@types/unist@2.0.11': {} + /@types/unist@2.0.11: + resolution: {integrity: sha512-CmBKiL6NNo/OqgmMn95Fk9Whlp2mtvIv+KNpQKN2F4SjvrEesubTRWGYSg+BnWZOnlCaSTU1sMpsBOzgbYhnsA==} + dev: false - '@types/ws@8.5.12': + /@types/ws@8.5.12: + resolution: {integrity: sha512-3tPRkv1EtkDpzlgyKyI8pGsGZAGPEaXeu0DOj5DI25Ja91bdAYddYHbADRYVrZMRbfW+1l5YwXVDKohDJNQxkQ==} dependencies: '@types/node': 22.5.0 + dev: false - '@types/yargs-parser@21.0.3': {} + /@types/yargs-parser@21.0.3: + resolution: {integrity: sha512-I4q9QU9MQv4oEOz4tAHJtNz1cwuLxn2F3xcc2iV5WdqLPpUnj30aUuxt1mAxYTG+oe8CZMV/+6rU4S4gRDzqtQ==} + dev: false - '@types/yargs@17.0.33': + /@types/yargs@17.0.33: + resolution: {integrity: sha512-WpxBCKWPLr4xSsHgz511rFJAM+wS28w2zEO1QDNY5zM/S8ok70NNfztH0xwhqKyaK0OHCbN98LDAZuy1ctxDkA==} dependencies: '@types/yargs-parser': 21.0.3 + dev: false - '@webassemblyjs/ast@1.12.1': + /@webassemblyjs/ast@1.12.1: + resolution: {integrity: sha512-EKfMUOPRRUTy5UII4qJDGPpqfwjOmZ5jeGFwid9mnoqIFK+e0vqoi1qH56JpmZSzEL53jKnNzScdmftJyG5xWg==} dependencies: '@webassemblyjs/helper-numbers': 1.11.6 '@webassemblyjs/helper-wasm-bytecode': 1.11.6 + dev: false - '@webassemblyjs/floating-point-hex-parser@1.11.6': {} + /@webassemblyjs/floating-point-hex-parser@1.11.6: + resolution: {integrity: sha512-ejAj9hfRJ2XMsNHk/v6Fu2dGS+i4UaXBXGemOfQ/JfQ6mdQg/WXtwleQRLLS4OvfDhv8rYnVwH27YJLMyYsxhw==} + dev: false - '@webassemblyjs/helper-api-error@1.11.6': {} + /@webassemblyjs/helper-api-error@1.11.6: + resolution: {integrity: sha512-o0YkoP4pVu4rN8aTJgAyj9hC2Sv5UlkzCHhxqWj8butaLvnpdc2jOwh4ewE6CX0txSfLn/UYaV/pheS2Txg//Q==} + dev: false - '@webassemblyjs/helper-buffer@1.12.1': {} + /@webassemblyjs/helper-buffer@1.12.1: + resolution: {integrity: sha512-nzJwQw99DNDKr9BVCOZcLuJJUlqkJh+kVzVl6Fmq/tI5ZtEyWT1KZMyOXltXLZJmDtvLCDgwsyrkohEtopTXCw==} + dev: false - '@webassemblyjs/helper-numbers@1.11.6': + /@webassemblyjs/helper-numbers@1.11.6: + resolution: {integrity: sha512-vUIhZ8LZoIWHBohiEObxVm6hwP034jwmc9kuq5GdHZH0wiLVLIPcMCdpJzG4C11cHoQ25TFIQj9kaVADVX7N3g==} dependencies: '@webassemblyjs/floating-point-hex-parser': 1.11.6 '@webassemblyjs/helper-api-error': 1.11.6 '@xtuc/long': 4.2.2 + dev: false - '@webassemblyjs/helper-wasm-bytecode@1.11.6': {} + /@webassemblyjs/helper-wasm-bytecode@1.11.6: + resolution: {integrity: sha512-sFFHKwcmBprO9e7Icf0+gddyWYDViL8bpPjJJl0WHxCdETktXdmtWLGVzoHbqUcY4Be1LkNfwTmXOJUFZYSJdA==} + dev: false - '@webassemblyjs/helper-wasm-section@1.12.1': + /@webassemblyjs/helper-wasm-section@1.12.1: + resolution: {integrity: sha512-Jif4vfB6FJlUlSbgEMHUyk1j234GTNG9dBJ4XJdOySoj518Xj0oGsNi59cUQF4RRMS9ouBUxDDdyBVfPTypa5g==} dependencies: '@webassemblyjs/ast': 1.12.1 '@webassemblyjs/helper-buffer': 1.12.1 '@webassemblyjs/helper-wasm-bytecode': 1.11.6 '@webassemblyjs/wasm-gen': 1.12.1 + dev: false - '@webassemblyjs/ieee754@1.11.6': + /@webassemblyjs/ieee754@1.11.6: + resolution: {integrity: sha512-LM4p2csPNvbij6U1f19v6WR56QZ8JcHg3QIJTlSwzFcmx6WSORicYj6I63f9yU1kEUtrpG+kjkiIAkevHpDXrg==} dependencies: '@xtuc/ieee754': 1.2.0 + dev: false - '@webassemblyjs/leb128@1.11.6': + /@webassemblyjs/leb128@1.11.6: + resolution: {integrity: sha512-m7a0FhE67DQXgouf1tbN5XQcdWoNgaAuoULHIfGFIEVKA6tu/edls6XnIlkmS6FrXAquJRPni3ZZKjw6FSPjPQ==} dependencies: '@xtuc/long': 4.2.2 + dev: false - '@webassemblyjs/utf8@1.11.6': {} + /@webassemblyjs/utf8@1.11.6: + resolution: {integrity: sha512-vtXf2wTQ3+up9Zsg8sa2yWiQpzSsMyXj0qViVP6xKGCUT8p8YJ6HqI7l5eCnWx1T/FYdsv07HQs2wTFbbof/RA==} + dev: false - '@webassemblyjs/wasm-edit@1.12.1': + /@webassemblyjs/wasm-edit@1.12.1: + resolution: {integrity: sha512-1DuwbVvADvS5mGnXbE+c9NfA8QRcZ6iKquqjjmR10k6o+zzsRVesil54DKexiowcFCPdr/Q0qaMgB01+SQ1u6g==} dependencies: '@webassemblyjs/ast': 1.12.1 '@webassemblyjs/helper-buffer': 1.12.1 @@ -7218,23 +3384,29 @@ snapshots: '@webassemblyjs/wasm-opt': 1.12.1 '@webassemblyjs/wasm-parser': 1.12.1 '@webassemblyjs/wast-printer': 1.12.1 + dev: false - '@webassemblyjs/wasm-gen@1.12.1': + /@webassemblyjs/wasm-gen@1.12.1: + resolution: {integrity: sha512-TDq4Ojh9fcohAw6OIMXqiIcTq5KUXTGRkVxbSo1hQnSy6lAM5GSdfwWeSxpAo0YzgsgF182E/U0mDNhuA0tW7w==} dependencies: '@webassemblyjs/ast': 1.12.1 '@webassemblyjs/helper-wasm-bytecode': 1.11.6 '@webassemblyjs/ieee754': 1.11.6 '@webassemblyjs/leb128': 1.11.6 '@webassemblyjs/utf8': 1.11.6 + dev: false - '@webassemblyjs/wasm-opt@1.12.1': + /@webassemblyjs/wasm-opt@1.12.1: + resolution: {integrity: sha512-Jg99j/2gG2iaz3hijw857AVYekZe2SAskcqlWIZXjji5WStnOpVoat3gQfT/Q5tb2djnCjBtMocY/Su1GfxPBg==} dependencies: '@webassemblyjs/ast': 1.12.1 '@webassemblyjs/helper-buffer': 1.12.1 '@webassemblyjs/wasm-gen': 1.12.1 '@webassemblyjs/wasm-parser': 1.12.1 + dev: false - '@webassemblyjs/wasm-parser@1.12.1': + /@webassemblyjs/wasm-parser@1.12.1: + resolution: {integrity: sha512-xikIi7c2FHXysxXe3COrVUPSheuBtpcfhbpFj4gmu7KRLYOzANztwUU0IbsqvMqzuNK2+glRGWCEqZo1WCLyAQ==} dependencies: '@webassemblyjs/ast': 1.12.1 '@webassemblyjs/helper-api-error': 1.11.6 @@ -7242,71 +3414,122 @@ snapshots: '@webassemblyjs/ieee754': 1.11.6 '@webassemblyjs/leb128': 1.11.6 '@webassemblyjs/utf8': 1.11.6 + dev: false - '@webassemblyjs/wast-printer@1.12.1': + /@webassemblyjs/wast-printer@1.12.1: + resolution: {integrity: sha512-+X4WAlOisVWQMikjbcvY2e0rwPsKQ9F688lksZhBcPycBBuii3O7m8FACbDMWDojpAqvjIncrG8J0XHKyQfVeA==} dependencies: '@webassemblyjs/ast': 1.12.1 '@xtuc/long': 4.2.2 + dev: false - '@xtuc/ieee754@1.2.0': {} + /@xtuc/ieee754@1.2.0: + resolution: {integrity: sha512-DX8nKgqcGwsc0eJSqYt5lwP4DH5FlHnmuWWBRy7X0NcaGR0ZtuyeESgMwTYVEtxmsNGY+qit4QYT/MIYTOTPeA==} + dev: false - '@xtuc/long@4.2.2': {} + /@xtuc/long@4.2.2: + resolution: {integrity: sha512-NuHqBY1PB/D8xU6s/thBgOAiAP7HOYDQ32+BFZILJ8ivkUkAHQnWfn6WhL79Owj1qmUnoN/YPhktdIoucipkAQ==} + dev: false - accepts@1.3.8: + /accepts@1.3.8: + resolution: {integrity: sha512-PYAthTa2m2VKxuvSD3DPC/Gy+U+sOA1LAuT8mkmRuvw+NACSaeXEQ+NHcVF7rONl6qcaxV3Uuemwawk+7+SJLw==} + engines: {node: '>= 0.6'} dependencies: mime-types: 2.1.35 negotiator: 0.6.3 + dev: false - acorn-import-attributes@1.9.5(acorn@8.12.1): + /acorn-import-attributes@1.9.5(acorn@8.12.1): + resolution: {integrity: sha512-n02Vykv5uA3eHGM/Z2dQrcD56kL8TyDb2p1+0P83PClMnC/nc+anbQRhIOWnSq4Ke/KvDPrY3C9hDtC/A3eHnQ==} + peerDependencies: + acorn: ^8 dependencies: acorn: 8.12.1 + dev: false - acorn-walk@8.3.3: + /acorn-walk@8.3.3: + resolution: {integrity: sha512-MxXdReSRhGO7VlFe1bRG/oI7/mdLV9B9JJT0N8vZOhF7gFRR5l3M8W9G8JxmKV+JC5mGqJ0QvqfSOLsCPa4nUw==} + engines: {node: '>=0.4.0'} dependencies: acorn: 8.12.1 + dev: false - acorn@8.12.1: {} + /acorn@8.12.1: + resolution: {integrity: sha512-tcpGyI9zbizT9JbV6oYE477V6mTlXvvi0T0G3SNIYE2apm/G5huBa1+K89VGeovbg+jycCrfhl3ADxErOuO6Jg==} + engines: {node: '>=0.4.0'} + hasBin: true + dev: false - address@1.2.2: {} + /address@1.2.2: + resolution: {integrity: sha512-4B/qKCfeE/ODUaAUpSwfzazo5x29WD4r3vXiWsB7I2mSDAihwEqKO+g8GELZUQSSAo5e1XTYh3ZVfLyxBc12nA==} + engines: {node: '>= 10.0.0'} + dev: false - aggregate-error@3.1.0: + /aggregate-error@3.1.0: + resolution: {integrity: sha512-4I7Td01quW/RpocfNayFdFVk1qSuoh0E7JrbRJ16nH01HhKFQ88INq9Sd+nd72zqRySlr9BmDA8xlEJ6vJMrYA==} + engines: {node: '>=8'} dependencies: clean-stack: 2.2.0 indent-string: 4.0.0 + dev: false - ajv-formats@2.1.1(ajv@8.17.1): + /ajv-formats@2.1.1(ajv@8.17.1): + resolution: {integrity: sha512-Wx0Kx52hxE7C18hkMEggYlEifqWZtYaRgouJor+WMdPnQyEK13vgEWyVNup7SoeeoLMsr4kf5h6dOW11I15MUA==} + peerDependencies: + ajv: ^8.0.0 + peerDependenciesMeta: + ajv: + optional: true dependencies: ajv: 8.17.1 + dev: false - ajv-keywords@3.5.2(ajv@6.12.6): + /ajv-keywords@3.5.2(ajv@6.12.6): + resolution: {integrity: sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==} + peerDependencies: + ajv: ^6.9.1 dependencies: ajv: 6.12.6 + dev: false - ajv-keywords@5.1.0(ajv@8.17.1): + /ajv-keywords@5.1.0(ajv@8.17.1): + resolution: {integrity: sha512-YCS/JNFAUyr5vAuhk1DWm1CBxRHW9LbJ2ozWeemrIqpbsqKjHVxYPyi5GC0rjZIT5JxJ3virVTS8wk4i/Z+krw==} + peerDependencies: + ajv: ^8.8.2 dependencies: ajv: 8.17.1 fast-deep-equal: 3.1.3 + dev: false - ajv@6.12.6: + /ajv@6.12.6: + resolution: {integrity: sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==} dependencies: fast-deep-equal: 3.1.3 fast-json-stable-stringify: 2.1.0 json-schema-traverse: 0.4.1 uri-js: 4.4.1 + dev: false - ajv@8.17.1: + /ajv@8.17.1: + resolution: {integrity: sha512-B/gBuNg5SiMTrPkC+A2+cW0RszwxYmn6VYxB/inlBStS5nx6xHIt/ehKRhIMhqusl7a8LjQoZnjCs5vhwxOQ1g==} dependencies: fast-deep-equal: 3.1.3 fast-uri: 3.0.1 json-schema-traverse: 1.0.0 require-from-string: 2.0.2 + dev: false - algoliasearch-helper@3.22.4(algoliasearch@4.24.0): + /algoliasearch-helper@3.22.4(algoliasearch@4.24.0): + resolution: {integrity: sha512-fvBCywguW9f+939S6awvRMstqMF1XXcd2qs1r1aGqL/PJ1go/DqN06tWmDVmhCDqBJanm++imletrQWf0G2S1g==} + peerDependencies: + algoliasearch: '>= 3.1 < 6' dependencies: '@algolia/events': 4.0.1 algoliasearch: 4.24.0 + dev: false - algoliasearch@4.24.0: + /algoliasearch@4.24.0: + resolution: {integrity: sha512-bf0QV/9jVejssFBmz2HQLxUadxk574t4iwjCKp5E7NBzwKkrDEhKPISIIjAU/p6K5qDx3qoeh4+26zWN1jmw3g==} dependencies: '@algolia/cache-browser-local-storage': 4.24.0 '@algolia/cache-common': 4.24.0 @@ -7323,50 +3546,86 @@ snapshots: '@algolia/requester-common': 4.24.0 '@algolia/requester-node-http': 4.24.0 '@algolia/transporter': 4.24.0 + dev: false - ansi-align@3.0.1: + /ansi-align@3.0.1: + resolution: {integrity: sha512-IOfwwBF5iczOjp/WeY4YxyjqAFMQoZufdQWDd19SEExbVLNXqvpzSJ/M7Za4/sCPmQ0+GRquoA7bGcINcxew6w==} dependencies: string-width: 4.2.3 + dev: false - ansi-html-community@0.0.8: {} + /ansi-html-community@0.0.8: + resolution: {integrity: sha512-1APHAyr3+PCamwNw3bXCPp4HFLONZt/yIH0sZp0/469KWNTEy+qN5jQ3GVX6DMZ1UXAi34yVwtTeaG/HpBuuzw==} + engines: {'0': node >= 0.8.0} + hasBin: true + dev: false - ansi-regex@5.0.1: {} + /ansi-regex@5.0.1: + resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==} + engines: {node: '>=8'} - ansi-regex@6.0.1: {} + /ansi-regex@6.0.1: + resolution: {integrity: sha512-n5M855fKb2SsfMIiFFoVrABHJC8QtHwVx+mHWP3QcEqBHYienj5dHSgjbxtC0WEZXYt4wcD6zrQElDPhFuZgfA==} + engines: {node: '>=12'} - ansi-styles@3.2.1: + /ansi-styles@3.2.1: + resolution: {integrity: sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==} + engines: {node: '>=4'} dependencies: color-convert: 1.9.3 + dev: false - ansi-styles@4.3.0: + /ansi-styles@4.3.0: + resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==} + engines: {node: '>=8'} dependencies: color-convert: 2.0.1 - ansi-styles@6.2.1: {} + /ansi-styles@6.2.1: + resolution: {integrity: sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==} + engines: {node: '>=12'} - anymatch@3.1.3: + /anymatch@3.1.3: + resolution: {integrity: sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==} + engines: {node: '>= 8'} dependencies: normalize-path: 3.0.0 picomatch: 2.3.1 + dev: false - arg@5.0.2: {} + /arg@5.0.2: + resolution: {integrity: sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==} + dev: false - argparse@1.0.10: + /argparse@1.0.10: + resolution: {integrity: sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==} dependencies: sprintf-js: 1.0.3 + dev: false - argparse@2.0.1: {} + /argparse@2.0.1: + resolution: {integrity: sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==} - array-buffer-byte-length@1.0.1: + /array-buffer-byte-length@1.0.1: + resolution: {integrity: sha512-ahC5W1xgou+KTXix4sAO8Ki12Q+jf4i0+tmk3sC+zgcynshkHxzpXdImBehiUYKKKDwvfFiJl1tZt6ewscS1Mg==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 is-array-buffer: 3.0.4 + dev: false - array-flatten@1.1.1: {} + /array-flatten@1.1.1: + resolution: {integrity: sha512-PCVAQswWemu6UdxsDFFX/+gVeYqKAod3D3UVm91jHwynguOwAvYPhx8nNlM++NqRcK6CxxpUafjmhIdKiHibqg==} + dev: false - array-union@2.1.0: {} + /array-union@2.1.0: + resolution: {integrity: sha512-HGyxoOTYUyCM6stUe6EJgnd4EoewAI7zMdfqO+kGjnlZmBDz/cR5pf8r/cR4Wq60sL/p0IkcjUEEPwS3GFrIyw==} + engines: {node: '>=8'} + dev: false - array.prototype.reduce@1.0.7: + /array.prototype.reduce@1.0.7: + resolution: {integrity: sha512-mzmiUCVwtiD4lgxYP8g7IYy8El8p2CSMePvIbTS7gchKir/L1fgJrk0yDKmAX6mnRQFKNADYIk8nNlTris5H1Q==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 define-properties: 1.2.1 @@ -7375,8 +3634,11 @@ snapshots: es-errors: 1.3.0 es-object-atoms: 1.0.0 is-string: 1.0.7 + dev: false - arraybuffer.prototype.slice@1.0.3: + /arraybuffer.prototype.slice@1.0.3: + resolution: {integrity: sha512-bMxMKAjg13EBSVscxTaYA4mRc5t1UAXa2kXiGTNfZ079HIWXEkKmkgFrh/nJqamaLSrXO5H4WFFkPEaLJWbs3A==} + engines: {node: '>= 0.4'} dependencies: array-buffer-byte-length: 1.0.1 call-bind: 1.0.7 @@ -7386,14 +3648,27 @@ snapshots: get-intrinsic: 1.2.4 is-array-buffer: 3.0.4 is-shared-array-buffer: 1.0.3 + dev: false - asap@2.0.6: {} + /asap@2.0.6: + resolution: {integrity: sha512-BSHWgDSAiKs50o2Re8ppvp3seVHXSRM44cdSsT9FfNEUUZLOGWVCsiWaRPWM1Znn+mqZ1OfVZ3z3DWEzSp7hRA==} + dev: false - asynckit@0.4.0: {} + /asynckit@0.4.0: + resolution: {integrity: sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q==} + dev: false - at-least-node@1.0.0: {} + /at-least-node@1.0.0: + resolution: {integrity: sha512-+q/t7Ekv1EDY2l6Gda6LLiX14rU9TV20Wa3ofeQmwPFZbOMo9DXrLbOjFaaclkXKWidIaopwAObQDqwWtGUjqg==} + engines: {node: '>= 4.0.0'} + dev: false - autoprefixer@10.4.20(postcss@8.4.41): + /autoprefixer@10.4.20(postcss@8.4.41): + resolution: {integrity: sha512-XY25y5xSv/wEoqzDyXXME4AFfkZI0P23z6Fs3YgymDnKJkCGOnkL0iTxCa85UTqaSgfcqyf3UA6+c7wUvx/16g==} + engines: {node: ^10 || ^12 || >=14} + hasBin: true + peerDependencies: + postcss: ^8.1.0 dependencies: browserslist: 4.23.3 caniuse-lite: 1.0.30001653 @@ -7402,26 +3677,39 @@ snapshots: picocolors: 1.0.1 postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - available-typed-arrays@1.0.7: + /available-typed-arrays@1.0.7: + resolution: {integrity: sha512-wvUjBtSGN7+7SjNpq/9M2Tg350UZD3q62IFZLbRAR1bSMlCo1ZaeW+BJ+D090e4hIIZLBcTDWe4Mh4jvUDajzQ==} + engines: {node: '>= 0.4'} dependencies: possible-typed-array-names: 1.0.0 + dev: false - axios@0.25.0: + /axios@0.25.0: + resolution: {integrity: sha512-cD8FOb0tRH3uuEe6+evtAbgJtfxr7ly3fQjYcMcuPlgkwVS9xboaVIpcDV+cYQe+yGykgwZCs1pzjntcGa6l5g==} dependencies: follow-redirects: 1.15.6 transitivePeerDependencies: - debug + dev: false - axios@1.7.5: + /axios@1.7.5: + resolution: {integrity: sha512-fZu86yCo+svH3uqJ/yTdQ0QHpQu5oL+/QE+QPSv6BZSkDAoky9vytxp7u5qk83OJFS3kEBcesWni9WTZAv3tSw==} dependencies: follow-redirects: 1.15.6 form-data: 4.0.0 proxy-from-env: 1.1.0 transitivePeerDependencies: - debug + dev: false - babel-loader@8.3.0(@babel/core@7.25.2)(webpack@5.94.0): + /babel-loader@8.3.0(@babel/core@7.25.2)(webpack@5.94.0): + resolution: {integrity: sha512-H8SvsMF+m9t15HNLMipppzkC+Y2Yq+v3SonZyU70RBL/h1gxPkH08Ot8pEE9Z4Kd+czyWJClmFS8qzIP9OZ04Q==} + engines: {node: '>= 8.9'} + peerDependencies: + '@babel/core': ^7.0.0 + webpack: '>=2' dependencies: '@babel/core': 7.25.2 find-cache-dir: 3.3.2 @@ -7429,22 +3717,34 @@ snapshots: make-dir: 3.1.0 schema-utils: 2.7.1 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - babel-plugin-apply-mdx-type-prop@1.6.22(@babel/core@7.12.9): + /babel-plugin-apply-mdx-type-prop@1.6.22(@babel/core@7.12.9): + resolution: {integrity: sha512-VefL+8o+F/DfK24lPZMtJctrCVOfgbqLAGZSkxwhazQv4VxPg3Za/i40fu22KR2m8eEda+IfSOlPLUSIiLcnCQ==} + peerDependencies: + '@babel/core': ^7.11.6 dependencies: '@babel/core': 7.12.9 '@babel/helper-plugin-utils': 7.10.4 '@mdx-js/util': 1.6.22 + dev: false - babel-plugin-dynamic-import-node@2.3.3: + /babel-plugin-dynamic-import-node@2.3.3: + resolution: {integrity: sha512-jZVI+s9Zg3IqA/kdi0i6UDCybUI3aSBLnglhYbSSjKlV7yF1F/5LWv8MakQmvYpnbJDS6fcBL2KzHSxNCMtWSQ==} dependencies: object.assign: 4.1.5 + dev: false - babel-plugin-extract-import-names@1.6.22: + /babel-plugin-extract-import-names@1.6.22: + resolution: {integrity: sha512-yJ9BsJaISua7d8zNT7oRG1ZLBJCIdZ4PZqmH8qa9N5AK01ifk3fnkc98AXhtzE7UkfCsEumvoQWgoYLhOnJ7jQ==} dependencies: '@babel/helper-plugin-utils': 7.10.4 + dev: false - babel-plugin-polyfill-corejs2@0.4.11(@babel/core@7.25.2): + /babel-plugin-polyfill-corejs2@0.4.11(@babel/core@7.25.2): + resolution: {integrity: sha512-sMEJ27L0gRHShOh5G54uAAPaiCOygY/5ratXuiyb2G46FmlSpc9eFCzYVyDiPxfNbwzA7mYahmjQc5q+CZQ09Q==} + peerDependencies: + '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 dependencies: '@babel/compat-data': 7.25.4 '@babel/core': 7.25.2 @@ -7452,35 +3752,58 @@ snapshots: semver: 6.3.1 transitivePeerDependencies: - supports-color + dev: false - babel-plugin-polyfill-corejs3@0.10.6(@babel/core@7.25.2): + /babel-plugin-polyfill-corejs3@0.10.6(@babel/core@7.25.2): + resolution: {integrity: sha512-b37+KR2i/khY5sKmWNVQAnitvquQbNdWy6lJdsr0kmquCKEEUgMKK4SboVM3HtfnZilfjr4MMQ7vY58FVWDtIA==} + peerDependencies: + '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-define-polyfill-provider': 0.6.2(@babel/core@7.25.2) core-js-compat: 3.38.1 transitivePeerDependencies: - supports-color + dev: false - babel-plugin-polyfill-regenerator@0.6.2(@babel/core@7.25.2): + /babel-plugin-polyfill-regenerator@0.6.2(@babel/core@7.25.2): + resolution: {integrity: sha512-2R25rQZWP63nGwaAswvDazbPXfrM3HwVoBXK6HcqeKrSrL/JqcC/rDcf95l4r7LXLyxDXc8uQDa064GubtCABg==} + peerDependencies: + '@babel/core': ^7.4.0 || ^8.0.0-0 <8.0.0 dependencies: '@babel/core': 7.25.2 '@babel/helper-define-polyfill-provider': 0.6.2(@babel/core@7.25.2) transitivePeerDependencies: - supports-color + dev: false - bail@1.0.5: {} + /bail@1.0.5: + resolution: {integrity: sha512-xFbRxM1tahm08yHBP16MMjVUAvDaBMD38zsM9EMAUN61omwLmKlOpB/Zku5QkjZ8TZ4vn53pj+t518cH0S03RQ==} + dev: false - balanced-match@1.0.2: {} + /balanced-match@1.0.2: + resolution: {integrity: sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==} - base16@1.0.0: {} + /base16@1.0.0: + resolution: {integrity: sha512-pNdYkNPiJUnEhnfXV56+sQy8+AaPcG3POZAUnwr4EeqCUZFz4u2PePbo3e5Gj4ziYPCWGUZT9RHisvJKnwFuBQ==} + dev: false - batch@0.6.1: {} + /batch@0.6.1: + resolution: {integrity: sha512-x+VAiMRL6UPkx+kudNvxTl6hB2XNNCG2r+7wixVfIYwu/2HKRXimwQyaumLjMveWvT2Hkd/cAJw+QBMfJ/EKVw==} + dev: false - big.js@5.2.2: {} + /big.js@5.2.2: + resolution: {integrity: sha512-vyL2OymJxmarO8gxMr0mhChsO9QGwhynfuu4+MHTAW6czfq9humCB7rKpUjDd9YUiDPU4mzpyupFSvOClAwbmQ==} + dev: false - binary-extensions@2.3.0: {} + /binary-extensions@2.3.0: + resolution: {integrity: sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==} + engines: {node: '>=8'} + dev: false - body-parser@1.20.2: + /body-parser@1.20.2: + resolution: {integrity: sha512-ml9pReCu3M61kGlqoTm2umSXTlRTuGTx0bfYj+uIUKKYycG5NtSbeetV3faSU6R7ajOPw0g/J1PvK4qNy7s5bA==} + engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16} dependencies: bytes: 3.1.2 content-type: 1.0.5 @@ -7496,15 +3819,22 @@ snapshots: unpipe: 1.0.0 transitivePeerDependencies: - supports-color + dev: false - bonjour-service@1.2.1: + /bonjour-service@1.2.1: + resolution: {integrity: sha512-oSzCS2zV14bh2kji6vNe7vrpJYCHGvcZnlffFQ1MEoX/WOeQ/teD8SYWKR942OI3INjq8OMNJlbPK5LLLUxFDw==} dependencies: fast-deep-equal: 3.1.3 multicast-dns: 7.2.5 + dev: false - boolbase@1.0.0: {} + /boolbase@1.0.0: + resolution: {integrity: sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==} + dev: false - boxen@5.1.2: + /boxen@5.1.2: + resolution: {integrity: sha512-9gYgQKXx+1nP8mP7CzFyaUARhg7D3n1dF/FnErWmu9l6JvGpNUN278h0aSb+QjoiKSWG+iZ3uHrcqk0qrY9RQQ==} + engines: {node: '>=10'} dependencies: ansi-align: 3.0.1 camelcase: 6.3.0 @@ -7514,8 +3844,11 @@ snapshots: type-fest: 0.20.2 widest-line: 3.1.0 wrap-ansi: 7.0.0 + dev: false - boxen@6.2.1: + /boxen@6.2.1: + resolution: {integrity: sha512-H4PEsJXfFI/Pt8sjDWbHlQPx4zL/bvSQjcilJmaulGt5mLDorHOHpmdXAJcBcmru7PhYSp/cDMWRko4ZUMFkSw==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} dependencies: ansi-align: 3.0.1 camelcase: 6.3.0 @@ -7525,36 +3858,60 @@ snapshots: type-fest: 2.19.0 widest-line: 4.0.1 wrap-ansi: 8.1.0 + dev: false - brace-expansion@1.1.11: + /brace-expansion@1.1.11: + resolution: {integrity: sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==} dependencies: balanced-match: 1.0.2 concat-map: 0.0.1 + dev: false - brace-expansion@2.0.1: + /brace-expansion@2.0.1: + resolution: {integrity: sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==} dependencies: balanced-match: 1.0.2 + dev: true - braces@3.0.3: + /braces@3.0.3: + resolution: {integrity: sha512-yQbXgO/OSZVD2IsiLlro+7Hf6Q18EJrKSEsdoMzKePKXct3gvD8oLcOQdIzGupr5Fj+EDe8gO/lxc1BzfMpxvA==} + engines: {node: '>=8'} dependencies: fill-range: 7.1.1 + dev: false - browserslist@4.23.3: + /browserslist@4.23.3: + resolution: {integrity: sha512-btwCFJVjI4YWDNfau8RhZ+B1Q/VLoUITrm3RlP6y1tYGWIOa+InuYiRGXUBXo8nA1qKmHMyLB/iVQg5TT4eFoA==} + engines: {node: ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7} + hasBin: true dependencies: caniuse-lite: 1.0.30001653 electron-to-chromium: 1.5.13 node-releases: 2.0.18 update-browserslist-db: 1.1.0(browserslist@4.23.3) + dev: false - buffer-crc32@0.2.13: {} + /buffer-crc32@0.2.13: + resolution: {integrity: sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ==} + dev: false - buffer-from@1.1.2: {} + /buffer-from@1.1.2: + resolution: {integrity: sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==} + dev: false - bytes@3.0.0: {} + /bytes@3.0.0: + resolution: {integrity: sha512-pMhOfFDPiv9t5jjIXkHosWmkSyQbvsgEVNkz0ERHbuLh2T/7j4Mqqpz523Fe8MVY89KC6Sh/QfS2sM+SjgFDcw==} + engines: {node: '>= 0.8'} + dev: false - bytes@3.1.2: {} + /bytes@3.1.2: + resolution: {integrity: sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==} + engines: {node: '>= 0.8'} + dev: false - cacheable-request@6.1.0: + /cacheable-request@6.1.0: + resolution: {integrity: sha512-Oj3cAGPCqOZX7Rz64Uny2GYAZNliQSqfbePrgAQ1wKAihYmCUnraBtJtKcGR4xz7wF+LoJC+ssFZvv5BgF9Igg==} + engines: {node: '>=8'} dependencies: clone-response: 1.0.3 get-stream: 5.2.0 @@ -7563,55 +3920,89 @@ snapshots: lowercase-keys: 2.0.0 normalize-url: 4.5.1 responselike: 1.0.2 + dev: false - call-bind@1.0.7: + /call-bind@1.0.7: + resolution: {integrity: sha512-GHTSNSYICQ7scH7sZ+M2rFopRoLh8t2bLSW6BbgrtLsahOIB5iyAVJf9GjWK3cYTDaMj4XdBpM1cA6pIS0Kv2w==} + engines: {node: '>= 0.4'} dependencies: es-define-property: 1.0.0 es-errors: 1.3.0 function-bind: 1.1.2 get-intrinsic: 1.2.4 set-function-length: 1.2.2 + dev: false - callsites@3.1.0: {} + /callsites@3.1.0: + resolution: {integrity: sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==} + engines: {node: '>=6'} + dev: false - camel-case@4.1.2: + /camel-case@4.1.2: + resolution: {integrity: sha512-gxGWBrTT1JuMx6R+o5PTXMmUnhnVzLQ9SNutD4YqKtI6ap897t3tKECYla6gCWEkplXnlNybEkZg9GEGxKFCgw==} dependencies: pascal-case: 3.1.2 tslib: 2.7.0 + dev: false - camelcase-css@2.0.1: {} + /camelcase-css@2.0.1: + resolution: {integrity: sha512-QOSvevhslijgYwRx6Rv7zKdMF8lbRmx+uQGx2+vDc+KI/eBnsy9kit5aj23AgGu3pa4t9AgwbnXWqS+iOY+2aA==} + engines: {node: '>= 6'} + dev: false - camelcase@6.3.0: {} + /camelcase@6.3.0: + resolution: {integrity: sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==} + engines: {node: '>=10'} + dev: false - caniuse-api@3.0.0: + /caniuse-api@3.0.0: + resolution: {integrity: sha512-bsTwuIg/BZZK/vreVTYYbSWoe2F+71P7K5QGEX+pT250DZbfU1MQ5prOKpPR+LL6uWKK3KMwMCAS74QB3Um1uw==} dependencies: browserslist: 4.23.3 caniuse-lite: 1.0.30001653 lodash.memoize: 4.1.2 lodash.uniq: 4.5.0 + dev: false - caniuse-lite@1.0.30001653: {} + /caniuse-lite@1.0.30001653: + resolution: {integrity: sha512-XGWQVB8wFQ2+9NZwZ10GxTYC5hk0Fa+q8cSkr0tgvMhYhMHP/QC+WTgrePMDBWiWc/pV+1ik82Al20XOK25Gcw==} + dev: false - ccount@1.1.0: {} + /ccount@1.1.0: + resolution: {integrity: sha512-vlNK021QdI7PNeiUh/lKkC/mNHHfV0m/Ad5JoI0TYtlBnJAslM/JIkm/tGC88bkLIwO6OQ5uV6ztS6kVAtCDlg==} + dev: false - chalk@2.4.2: + /chalk@2.4.2: + resolution: {integrity: sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==} + engines: {node: '>=4'} dependencies: ansi-styles: 3.2.1 escape-string-regexp: 1.0.5 supports-color: 5.5.0 + dev: false - chalk@4.1.2: + /chalk@4.1.2: + resolution: {integrity: sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==} + engines: {node: '>=10'} dependencies: ansi-styles: 4.3.0 supports-color: 7.2.0 + dev: false - character-entities-legacy@1.1.4: {} + /character-entities-legacy@1.1.4: + resolution: {integrity: sha512-3Xnr+7ZFS1uxeiUDvV02wQ+QDbc55o97tIV5zHScSPJpcLm/r0DFPcoY3tYRp+VZukxuMeKgXYmsXQHO05zQeA==} + dev: false - character-entities@1.2.4: {} + /character-entities@1.2.4: + resolution: {integrity: sha512-iBMyeEHxfVnIakwOuDXpVkc54HijNgCyQB2w0VfGQThle6NXn50zU6V/u+LDhxHcDUPojn6Kpga3PTAD8W1bQw==} + dev: false - character-reference-invalid@1.1.4: {} + /character-reference-invalid@1.1.4: + resolution: {integrity: sha512-mKKUkUbhPpQlCOfIuZkvSEgktjPFIsZKRRbC6KWVEMvlzblj3i3asQv5ODsrwt0N3pHAEvjP8KTQPHkp0+6jOg==} + dev: false - cheerio-select@2.1.0: + /cheerio-select@2.1.0: + resolution: {integrity: sha512-9v9kG0LvzrlcungtnJtpGNxY+fzECQKhK4EGJX2vByejiMX84MFNQw4UxPJl3bFbTMw+Dfs37XaIkCwTZfLh4g==} dependencies: boolbase: 1.0.0 css-select: 5.1.0 @@ -7619,8 +4010,11 @@ snapshots: domelementtype: 2.3.0 domhandler: 5.0.3 domutils: 3.1.0 + dev: false - cheerio@1.0.0: + /cheerio@1.0.0: + resolution: {integrity: sha512-quS9HgjQpdaXOvsZz82Oz7uxtXiy6UIsIQcpBj7HRw2M63Skasm9qlDocAM7jNuaxdhpPU7c4kJN+gA5MCu4ww==} + engines: {node: '>=18.17'} dependencies: cheerio-select: 2.1.0 dom-serializer: 2.0.0 @@ -7633,8 +4027,11 @@ snapshots: parse5-parser-stream: 7.1.2 undici: 6.19.8 whatwg-mimetype: 4.0.0 + dev: false - chokidar@3.6.0: + /chokidar@3.6.0: + resolution: {integrity: sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==} + engines: {node: '>= 8.10.0'} dependencies: anymatch: 3.1.3 braces: 3.0.3 @@ -7645,94 +4042,176 @@ snapshots: readdirp: 3.6.0 optionalDependencies: fsevents: 2.3.3 + dev: false - chownr@1.1.4: {} + /chownr@1.1.4: + resolution: {integrity: sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==} + dev: false - chrome-trace-event@1.0.4: {} + /chrome-trace-event@1.0.4: + resolution: {integrity: sha512-rNjApaLzuwaOTjCiT8lSDdGN1APCiqkChLMJxJPWLunPAt5fy8xgU9/jNOchV84wfIxrA0lRQB7oCT8jrn/wrQ==} + engines: {node: '>=6.0'} + dev: false - ci-info@2.0.0: {} + /ci-info@2.0.0: + resolution: {integrity: sha512-5tK7EtrZ0N+OLFMthtqOj4fI2Jeb88C4CAZPu25LDVUgXJ0A3Js4PMGqrn0JU1W0Mh1/Z8wZzYPxqUrXeBboCQ==} + dev: false - ci-info@3.9.0: {} + /ci-info@3.9.0: + resolution: {integrity: sha512-NIxF55hv4nSqQswkAeiOi1r83xy8JldOFDTWiug55KBu9Jnblncd2U6ViHmYgHf01TPZS77NJBhBMKdWj9HQMQ==} + engines: {node: '>=8'} + dev: false - clean-css@5.3.3: + /clean-css@5.3.3: + resolution: {integrity: sha512-D5J+kHaVb/wKSFcyyV75uCn8fiY4sV38XJoe4CUyGQ+mOU/fMVYUdH1hJC+CJQ5uY3EnW27SbJYS4X8BiLrAFg==} + engines: {node: '>= 10.0'} dependencies: source-map: 0.6.1 + dev: false - clean-stack@2.2.0: {} + /clean-stack@2.2.0: + resolution: {integrity: sha512-4diC9HaTE+KRAMWhDhrGOECgWZxoevMc5TlkObMqNSsVU62PYzXZ/SMTjzyGAFF1YusgxGcSWTEXBhp0CPwQ1A==} + engines: {node: '>=6'} + dev: false - cli-boxes@2.2.1: {} + /cli-boxes@2.2.1: + resolution: {integrity: sha512-y4coMcylgSCdVinjiDBuR8PCC2bLjyGTwEmPb9NHR/QaNU6EUOXcTY/s6VjGMD6ENSEaeQYHCY0GNGS5jfMwPw==} + engines: {node: '>=6'} + dev: false - cli-boxes@3.0.0: {} + /cli-boxes@3.0.0: + resolution: {integrity: sha512-/lzGpEWL/8PfI0BmBOPRwp0c/wFNX1RdUML3jK/RcSBA9T8mZDdQpqYBKtCFTOfQbwPqWEOpjqW+Fnayc0969g==} + engines: {node: '>=10'} + dev: false - cli-table3@0.6.5: + /cli-table3@0.6.5: + resolution: {integrity: sha512-+W/5efTR7y5HRD7gACw9yQjqMVvEMLBHmboM/kPWam+H+Hmyrgjh6YncVKK122YZkXrLudzTuAukUw9FnMf7IQ==} + engines: {node: 10.* || >= 12.*} dependencies: string-width: 4.2.3 optionalDependencies: '@colors/colors': 1.5.0 + dev: false - clone-deep@4.0.1: + /clone-deep@4.0.1: + resolution: {integrity: sha512-neHB9xuzh/wk0dIHweyAXv2aPGZIVk3pLMe+/RNzINf17fe0OG96QroktYAUm7SM1PBnzTabaLboqqxDyMU+SQ==} + engines: {node: '>=6'} dependencies: is-plain-object: 2.0.4 kind-of: 6.0.3 shallow-clone: 3.0.1 + dev: false - clone-response@1.0.3: + /clone-response@1.0.3: + resolution: {integrity: sha512-ROoL94jJH2dUVML2Y/5PEDNaSHgeOdSDicUyS7izcF63G6sTc/FTjLub4b8Il9S8S0beOfYt0TaA5qvFK+w0wA==} dependencies: mimic-response: 1.0.1 + dev: false - clsx@1.2.1: {} + /clsx@1.2.1: + resolution: {integrity: sha512-EcR6r5a8bj6pu3ycsa/E/cKVGuTgZJZdsyUYHOksG/UHIiKfjxzRxYJpyVBwYaQeOvghal9fcc4PidlgzugAQg==} + engines: {node: '>=6'} + dev: false - coa@2.0.2: + /coa@2.0.2: + resolution: {integrity: sha512-q5/jG+YQnSy4nRTV4F7lPepBJZ8qBNJJDBuJdoejDyLXgmL7IEo+Le2JDZudFTFt7mrCqIRaSjws4ygRCTCAXA==} + engines: {node: '>= 4.0'} dependencies: '@types/q': 1.5.8 chalk: 2.4.2 q: 1.5.1 + dev: false - collapse-white-space@1.0.6: {} + /collapse-white-space@1.0.6: + resolution: {integrity: sha512-jEovNnrhMuqyCcjfEJA56v0Xq8SkIoPKDyaHahwo3POf4qcSXqMYuwNcOTzp74vTsR9Tn08z4MxWqAhcekogkQ==} + dev: false - color-convert@1.9.3: + /color-convert@1.9.3: + resolution: {integrity: sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==} dependencies: color-name: 1.1.3 + dev: false - color-convert@2.0.1: + /color-convert@2.0.1: + resolution: {integrity: sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==} + engines: {node: '>=7.0.0'} dependencies: color-name: 1.1.4 - color-name@1.1.3: {} + /color-name@1.1.3: + resolution: {integrity: sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw==} + dev: false - color-name@1.1.4: {} + /color-name@1.1.4: + resolution: {integrity: sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==} - colord@2.9.3: {} + /colord@2.9.3: + resolution: {integrity: sha512-jeC1axXpnb0/2nn/Y1LPuLdgXBLH7aDcHu4KEKfqw3CUhX7ZpfBSlPKyqXE6btIgEzfWtrX3/tyBCaCvXvMkOw==} + dev: false - colorette@2.0.20: {} + /colorette@2.0.20: + resolution: {integrity: sha512-IfEDxwoWIjkeXL1eXcDiow4UbKjhLdq6/EuSVR9GMN7KVH3r9gQ83e73hsz1Nd1T3ijd5xv1wcWRYO+D6kCI2w==} + dev: false - combine-promises@1.2.0: {} + /combine-promises@1.2.0: + resolution: {integrity: sha512-VcQB1ziGD0NXrhKxiwyNbCDmRzs/OShMs2GqW2DlU2A/Sd0nQxE1oWDAE5O0ygSx5mgQOn9eIFh7yKPgFRVkPQ==} + engines: {node: '>=10'} + dev: false - combined-stream@1.0.8: + /combined-stream@1.0.8: + resolution: {integrity: sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==} + engines: {node: '>= 0.8'} dependencies: delayed-stream: 1.0.0 + dev: false - comma-separated-tokens@1.0.8: {} + /comma-separated-tokens@1.0.8: + resolution: {integrity: sha512-GHuDRO12Sypu2cV70d1dkA2EUmXHgntrzbpvOB+Qy+49ypNfGgFQIC2fhhXbnyrJRynDCAARsT7Ou0M6hirpfw==} + dev: false - command-exists-promise@2.0.2: {} + /command-exists-promise@2.0.2: + resolution: {integrity: sha512-T6PB6vdFrwnHXg/I0kivM3DqaCGZLjjYSOe0a5WgFKcz1sOnmOeIjnhQPXVXX3QjVbLyTJ85lJkX6lUpukTzaA==} + engines: {node: '>=6'} + dev: false - commander@11.0.0: {} + /commander@11.0.0: + resolution: {integrity: sha512-9HMlXtt/BNoYr8ooyjjNRdIilOTkVJXB+GhxMTtOKwk0R4j4lS4NpjuqmRxroBfnfTSHQIHQB7wryHhXarNjmQ==} + engines: {node: '>=16'} + dev: true - commander@2.20.3: {} + /commander@2.20.3: + resolution: {integrity: sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==} + dev: false - commander@5.1.0: {} + /commander@5.1.0: + resolution: {integrity: sha512-P0CysNDQ7rtVw4QIQtm+MRxV66vKFSvlsQvGYXZWR3qFU0jlMKHZZZgw8e+8DSah4UDKMqnknRDQz+xuQXQ/Zg==} + engines: {node: '>= 6'} + dev: false - commander@7.2.0: {} + /commander@7.2.0: + resolution: {integrity: sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==} + engines: {node: '>= 10'} + dev: false - commander@8.3.0: {} + /commander@8.3.0: + resolution: {integrity: sha512-OkTL9umf+He2DZkUq8f8J9of7yL6RJKI24dVITBmNfZBmri9zYZQrKkuXiKhyfPSu8tUhnVBB1iKXevvnlR4Ww==} + engines: {node: '>= 12'} + dev: false - commondir@1.0.1: {} + /commondir@1.0.1: + resolution: {integrity: sha512-W9pAhw0ja1Edb5GVdIF1mjZw/ASI0AlShXM83UUGe2DVr5TdAPEA1OA8m/g8zWp9x6On7gqufY+FatDbC3MDQg==} + dev: false - compressible@2.0.18: + /compressible@2.0.18: + resolution: {integrity: sha512-AF3r7P5dWxL8MxyITRMlORQNaOA2IkAFaTr4k7BUumjPtRpGDTZpl0Pb1XCO6JeDCBdp126Cgs9sMxqSjgYyRg==} + engines: {node: '>= 0.6'} dependencies: mime-db: 1.53.0 + dev: false - compression@1.7.4: + /compression@1.7.4: + resolution: {integrity: sha512-jaSIDzP9pZVS4ZfQ+TzvtiWhdpFhE2RDHz8QJkpX9SIpLq88VueF5jJw6t+6CUQcAoA6t+x89MLrWAqpfDE8iQ==} + engines: {node: '>= 0.8.0'} dependencies: accepts: 1.3.8 bytes: 3.0.0 @@ -7743,10 +4222,15 @@ snapshots: vary: 1.1.2 transitivePeerDependencies: - supports-color + dev: false - concat-map@0.0.1: {} + /concat-map@0.0.1: + resolution: {integrity: sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==} + dev: false - configstore@5.0.1: + /configstore@5.0.1: + resolution: {integrity: sha512-aMKprgk5YhBNyH25hj8wGt2+D52Sw1DRRIzqBwLp2Ya9mFmY8KPvvtvmna8SxVR9JMZ4kzMD68N22vlaRpkeFA==} + engines: {node: '>=8'} dependencies: dot-prop: 5.3.0 graceful-fs: 4.2.11 @@ -7754,30 +4238,61 @@ snapshots: unique-string: 2.0.0 write-file-atomic: 3.0.3 xdg-basedir: 4.0.0 + dev: false - connect-history-api-fallback@2.0.0: {} + /connect-history-api-fallback@2.0.0: + resolution: {integrity: sha512-U73+6lQFmfiNPrYbXqr6kZ1i1wiRqXnp2nhMsINseWXO8lDau0LGEffJ8kQi4EjLZympVgRdvqjAgiZ1tgzDDA==} + engines: {node: '>=0.8'} + dev: false - consola@2.15.3: {} + /consola@2.15.3: + resolution: {integrity: sha512-9vAdYbHj6x2fLKC4+oPH0kFzY/orMZyG2Aj+kNylHxKGJ/Ed4dpNyAQYwJOdqO4zdM7XpVHmyejQDcQHrnuXbw==} + dev: false - content-disposition@0.5.2: {} + /content-disposition@0.5.2: + resolution: {integrity: sha512-kRGRZw3bLlFISDBgwTSA1TMBFN6J6GWDeubmDE3AF+3+yXL8hTWv8r5rkLbqYXY4RjPk/EzHnClI3zQf1cFmHA==} + engines: {node: '>= 0.6'} + dev: false - content-disposition@0.5.4: + /content-disposition@0.5.4: + resolution: {integrity: sha512-FveZTNuGw04cxlAiWbzi6zTAL/lhehaWbTtgluJh4/E95DqMwTmha3KZN1aAWA8cFIhHzMZUvLevkw5Rqk+tSQ==} + engines: {node: '>= 0.6'} dependencies: safe-buffer: 5.2.1 + dev: false - content-type@1.0.5: {} + /content-type@1.0.5: + resolution: {integrity: sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==} + engines: {node: '>= 0.6'} + dev: false - convert-source-map@1.9.0: {} + /convert-source-map@1.9.0: + resolution: {integrity: sha512-ASFBup0Mz1uyiIjANan1jzLQami9z1PoYSZCiiYW2FczPbenXc45FZdBZLzOT+r6+iciuEModtmCti+hjaAk0A==} + dev: false - convert-source-map@2.0.0: {} + /convert-source-map@2.0.0: + resolution: {integrity: sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==} + dev: false - cookie-signature@1.0.6: {} + /cookie-signature@1.0.6: + resolution: {integrity: sha512-QADzlaHc8icV8I7vbaJXJwod9HWYp8uCqf1xa4OfNu1T7JVxQIrUgOWtHdNDtPiywmFbiS12VjotIXLrKM3orQ==} + dev: false - cookie@0.6.0: {} + /cookie@0.6.0: + resolution: {integrity: sha512-U71cyTamuh1CRNCfpGY6to28lxvNwPG4Guz/EVjgf3Jmzv0vlDp1atT9eS5dDjMYHucpHbWns6Lwf3BKz6svdw==} + engines: {node: '>= 0.6'} + dev: false - copy-text-to-clipboard@3.2.0: {} + /copy-text-to-clipboard@3.2.0: + resolution: {integrity: sha512-RnJFp1XR/LOBDckxTib5Qjr/PMfkatD0MUCQgdpqS8MdKiNUzBjAQBEN6oUy+jW7LI93BBG3DtMB2KOOKpGs2Q==} + engines: {node: '>=12'} + dev: false - copy-webpack-plugin@11.0.0(webpack@5.94.0): + /copy-webpack-plugin@11.0.0(webpack@5.94.0): + resolution: {integrity: sha512-fX2MWpamkW0hZxMEg0+mYnA40LTosOSa5TqZ9GYIBzyJa9C3QUaMPSE2xAi/buNr8u89SfD9wHSQVBzrRa/SOQ==} + engines: {node: '>= 14.15.0'} + peerDependencies: + webpack: ^5.1.0 dependencies: fast-glob: 3.3.2 glob-parent: 6.0.2 @@ -7786,60 +4301,107 @@ snapshots: schema-utils: 4.2.0 serialize-javascript: 6.0.2 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - core-js-compat@3.38.1: + /core-js-compat@3.38.1: + resolution: {integrity: sha512-JRH6gfXxGmrzF3tZ57lFx97YARxCXPaMzPo6jELZhv88pBH5VXpQ+y0znKGlFnzuaihqhLbefxSJxWJMPtfDzw==} dependencies: browserslist: 4.23.3 + dev: false - core-js-pure@3.38.1: {} + /core-js-pure@3.38.1: + resolution: {integrity: sha512-BY8Etc1FZqdw1glX0XNOq2FDwfrg/VGqoZOZCdaL+UmdaqDwQwYXkMJT4t6In+zfEfOJDcM9T0KdbBeJg8KKCQ==} + requiresBuild: true + dev: false - core-js@3.38.1: {} + /core-js@3.38.1: + resolution: {integrity: sha512-OP35aUorbU3Zvlx7pjsFdu1rGNnD4pgw/CWoYzRY3t2EzoVT7shKHY1dlAy3f41cGIO7ZDPQimhGFTlEYkG/Hw==} + requiresBuild: true + dev: false - core-util-is@1.0.3: {} + /core-util-is@1.0.3: + resolution: {integrity: sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==} + dev: false - cosmiconfig@6.0.0: + /cosmiconfig@6.0.0: + resolution: {integrity: sha512-xb3ZL6+L8b9JLLCx3ZdoZy4+2ECphCMo2PwqgP1tlfVq6M6YReyzBJtvWWtbDSpNr9hn96pkCiZqUcFEc+54Qg==} + engines: {node: '>=8'} dependencies: '@types/parse-json': 4.0.2 import-fresh: 3.3.0 parse-json: 5.2.0 path-type: 4.0.0 yaml: 1.10.2 + dev: false - cosmiconfig@7.1.0: + /cosmiconfig@7.1.0: + resolution: {integrity: sha512-AdmX6xUzdNASswsFtmwSt7Vj8po9IuqXm0UXz7QKPuEUmPB4XyjGfaAr2PSuELMwkRMVH1EpIkX5bTZGRB3eCA==} + engines: {node: '>=10'} dependencies: '@types/parse-json': 4.0.2 import-fresh: 3.3.0 parse-json: 5.2.0 path-type: 4.0.0 yaml: 1.10.2 + dev: false - cosmiconfig@8.3.6(typescript@5.5.4): + /cosmiconfig@8.3.6(typescript@5.5.4): + resolution: {integrity: sha512-kcZ6+W5QzcJ3P1Mt+83OUv/oHFqZHIx8DuxG6eZ5RGMERoLqp4BuGjhHLYGK+Kf5XVkQvqBSmAy/nGWN3qDgEA==} + engines: {node: '>=14'} + peerDependencies: + typescript: '>=4.9.5' + peerDependenciesMeta: + typescript: + optional: true dependencies: import-fresh: 3.3.0 js-yaml: 4.1.0 parse-json: 5.2.0 path-type: 4.0.0 typescript: 5.5.4 + dev: false - cross-fetch@3.1.8: + /cross-fetch@3.1.8: + resolution: {integrity: sha512-cvA+JwZoU0Xq+h6WkMvAUqPEYy92Obet6UdKLfW60qn99ftItKjB5T+BkyWOFWe2pUyfQ+IJHmpOTznqk1M6Kg==} dependencies: node-fetch: 2.7.0 transitivePeerDependencies: - encoding + dev: false - cross-spawn@7.0.3: + /cross-spawn@7.0.3: + resolution: {integrity: sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==} + engines: {node: '>= 8'} dependencies: path-key: 3.1.1 shebang-command: 2.0.0 which: 2.0.2 - crypto-random-string@2.0.0: {} + /crypto-random-string@2.0.0: + resolution: {integrity: sha512-v1plID3y9r/lPhviJ1wrXpLeyUIGAZ2SHNYTEapm7/8A9nLPoyvVp3RK/EPFqn5kEznyWgYZNsRtYYIWbuG8KA==} + engines: {node: '>=8'} + dev: false - css-declaration-sorter@6.4.1(postcss@8.4.41): + /css-declaration-sorter@6.4.1(postcss@8.4.41): + resolution: {integrity: sha512-rtdthzxKuyq6IzqX6jEcIzQF/YqccluefyCYheovBOLhFT/drQA9zj/UbRAa9J7C0o6EG6u3E6g+vKkay7/k3g==} + engines: {node: ^10 || ^12 || >=14} + peerDependencies: + postcss: ^8.0.9 dependencies: postcss: 8.4.41 + dev: false - css-loader@6.11.0(webpack@5.94.0): + /css-loader@6.11.0(webpack@5.94.0): + resolution: {integrity: sha512-CTJ+AEQJjq5NzLga5pE39qdiSV56F8ywCIsqNIRF0r7BDgWsN25aazToqAFg7ZrtA/U016xudB3ffgweORxX7g==} + engines: {node: '>= 12.13.0'} + peerDependencies: + '@rspack/core': 0.x || 1.x + webpack: ^5.0.0 + peerDependenciesMeta: + '@rspack/core': + optional: true + webpack: + optional: true dependencies: icss-utils: 5.1.0(postcss@8.4.41) postcss: 8.4.41 @@ -7850,8 +4412,32 @@ snapshots: postcss-value-parser: 4.2.0 semver: 7.6.3 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - css-minimizer-webpack-plugin@4.2.2(clean-css@5.3.3)(webpack@5.94.0): + /css-minimizer-webpack-plugin@4.2.2(clean-css@5.3.3)(webpack@5.94.0): + resolution: {integrity: sha512-s3Of/4jKfw1Hj9CxEO1E5oXhQAxlayuHO2y/ML+C6I9sQ7FdzfEV6QgMLN3vI+qFsjJGIAFLKtQK7t8BOXAIyA==} + engines: {node: '>= 14.15.0'} + peerDependencies: + '@parcel/css': '*' + '@swc/css': '*' + clean-css: '*' + csso: '*' + esbuild: '*' + lightningcss: '*' + webpack: ^5.0.0 + peerDependenciesMeta: + '@parcel/css': + optional: true + '@swc/css': + optional: true + clean-css: + optional: true + csso: + optional: true + esbuild: + optional: true + lightningcss: + optional: true dependencies: clean-css: 5.3.3 cssnano: 5.1.15(postcss@8.4.41) @@ -7861,49 +4447,78 @@ snapshots: serialize-javascript: 6.0.2 source-map: 0.6.1 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - css-select-base-adapter@0.1.1: {} + /css-select-base-adapter@0.1.1: + resolution: {integrity: sha512-jQVeeRG70QI08vSTwf1jHxp74JoZsr2XSgETae8/xC8ovSnL2WF87GTLO86Sbwdt2lK4Umg4HnnwMO4YF3Ce7w==} + dev: false - css-select@2.1.0: + /css-select@2.1.0: + resolution: {integrity: sha512-Dqk7LQKpwLoH3VovzZnkzegqNSuAziQyNZUcrdDM401iY+R5NkGBXGmtO05/yaXQziALuPogeG0b7UAgjnTJTQ==} dependencies: boolbase: 1.0.0 css-what: 3.4.2 domutils: 1.7.0 nth-check: 1.0.2 + dev: false - css-select@4.3.0: + /css-select@4.3.0: + resolution: {integrity: sha512-wPpOYtnsVontu2mODhA19JrqWxNsfdatRKd64kmpRbQgh1KtItko5sTnEpPdpSaJszTOhEMlF/RPz28qj4HqhQ==} dependencies: boolbase: 1.0.0 css-what: 6.1.0 domhandler: 4.3.1 domutils: 2.8.0 nth-check: 2.1.1 + dev: false - css-select@5.1.0: + /css-select@5.1.0: + resolution: {integrity: sha512-nwoRF1rvRRnnCqqY7updORDsuqKzqYJ28+oSMaJMMgOauh3fvwHqMS7EZpIPqK8GL+g9mKxF1vP/ZjSeNjEVHg==} dependencies: boolbase: 1.0.0 css-what: 6.1.0 domhandler: 5.0.3 domutils: 3.1.0 nth-check: 2.1.1 + dev: false - css-tree@1.0.0-alpha.37: + /css-tree@1.0.0-alpha.37: + resolution: {integrity: sha512-DMxWJg0rnz7UgxKT0Q1HU/L9BeJI0M6ksor0OgqOnF+aRCDWg/N2641HmVyU9KVIu0OVVWOb2IpC9A+BJRnejg==} + engines: {node: '>=8.0.0'} dependencies: mdn-data: 2.0.4 source-map: 0.6.1 + dev: false - css-tree@1.1.3: + /css-tree@1.1.3: + resolution: {integrity: sha512-tRpdppF7TRazZrjJ6v3stzv93qxRcSsFmW6cX0Zm2NVKpxE1WV1HblnghVv9TreireHkqI/VDEsfolRF1p6y7Q==} + engines: {node: '>=8.0.0'} dependencies: mdn-data: 2.0.14 source-map: 0.6.1 + dev: false - css-what@3.4.2: {} + /css-what@3.4.2: + resolution: {integrity: sha512-ACUm3L0/jiZTqfzRM3Hi9Q8eZqd6IK37mMWPLz9PJxkLWllYeRf+EHUSHYEtFop2Eqytaq1FizFVh7XfBnXCDQ==} + engines: {node: '>= 6'} + dev: false - css-what@6.1.0: {} + /css-what@6.1.0: + resolution: {integrity: sha512-HTUrgRJ7r4dsZKU6GjmpfRK1O76h97Z8MfS1G0FozR+oF2kG6Vfe8JE6zwrkbxigziPHinCJ+gCPjA9EaBDtRw==} + engines: {node: '>= 6'} + dev: false - cssesc@3.0.0: {} + /cssesc@3.0.0: + resolution: {integrity: sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==} + engines: {node: '>=4'} + hasBin: true + dev: false - cssnano-preset-advanced@5.3.10(postcss@8.4.41): + /cssnano-preset-advanced@5.3.10(postcss@8.4.41): + resolution: {integrity: sha512-fnYJyCS9jgMU+cmHO1rPSPf9axbQyD7iUhLO5Df6O4G+fKIOMps+ZbU0PdGFejFBBZ3Pftf18fn1eG7MAPUSWQ==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: autoprefixer: 10.4.20(postcss@8.4.41) cssnano-preset-default: 5.2.14(postcss@8.4.41) @@ -7912,8 +4527,13 @@ snapshots: postcss-merge-idents: 5.1.1(postcss@8.4.41) postcss-reduce-idents: 5.2.0(postcss@8.4.41) postcss-zindex: 5.1.0(postcss@8.4.41) + dev: false - cssnano-preset-default@5.2.14(postcss@8.4.41): + /cssnano-preset-default@5.2.14(postcss@8.4.41): + resolution: {integrity: sha512-t0SFesj/ZV2OTylqQVOrFgEh5uanxbO6ZAdeCrNsUQ6fVuXwYTxJPNAGvGTxHbD68ldIJNec7PyYZDBrfDQ+6A==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: css-declaration-sorter: 6.4.1(postcss@8.4.41) cssnano-utils: 3.1.0(postcss@8.4.41) @@ -7945,81 +4565,147 @@ snapshots: postcss-reduce-transforms: 5.1.0(postcss@8.4.41) postcss-svgo: 5.1.0(postcss@8.4.41) postcss-unique-selectors: 5.1.1(postcss@8.4.41) + dev: false - cssnano-utils@3.1.0(postcss@8.4.41): + /cssnano-utils@3.1.0(postcss@8.4.41): + resolution: {integrity: sha512-JQNR19/YZhz4psLX/rQ9M83e3z2Wf/HdJbryzte4a3NSuafyp9w/I4U+hx5C2S9g41qlstH7DEWnZaaj83OuEA==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 + dev: false - cssnano@5.1.15(postcss@8.4.41): + /cssnano@5.1.15(postcss@8.4.41): + resolution: {integrity: sha512-j+BKgDcLDQA+eDifLx0EO4XSA56b7uut3BQFH+wbSaSTuGLuiyTa/wbRYthUXX8LC9mLg+WWKe8h+qJuwTAbHw==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: cssnano-preset-default: 5.2.14(postcss@8.4.41) lilconfig: 2.1.0 postcss: 8.4.41 yaml: 1.10.2 + dev: false - csso@4.2.0: + /csso@4.2.0: + resolution: {integrity: sha512-wvlcdIbf6pwKEk7vHj8/Bkc0B4ylXZruLvOgs9doS5eOsOpuodOV2zJChSpkp+pRpYQLQMeF04nr3Z68Sta9jA==} + engines: {node: '>=8.0.0'} dependencies: css-tree: 1.1.3 + dev: false - csstype@3.1.3: {} + /csstype@3.1.3: + resolution: {integrity: sha512-M1uQkMl8rQK/szD0LNhtqxIPLpimGm8sOBwU7lLnCpSbTyY3yeU1Vc7l4KT5zT4s/yOxHH5O7tIuuLOCnLADRw==} + dev: false - data-view-buffer@1.0.1: + /data-view-buffer@1.0.1: + resolution: {integrity: sha512-0lht7OugA5x3iJLOWFhWK/5ehONdprk0ISXqVFn/NFrDu+cuc8iADFrGQz5BnRK7LLU3JmkbXSxaqX+/mXYtUA==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 es-errors: 1.3.0 is-data-view: 1.0.1 + dev: false - data-view-byte-length@1.0.1: + /data-view-byte-length@1.0.1: + resolution: {integrity: sha512-4J7wRJD3ABAzr8wP+OcIcqq2dlUKp4DVflx++hs5h5ZKydWMI6/D/fAot+yh6g2tHh8fLFTvNOaVN357NvSrOQ==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 es-errors: 1.3.0 is-data-view: 1.0.1 + dev: false - data-view-byte-offset@1.0.0: + /data-view-byte-offset@1.0.0: + resolution: {integrity: sha512-t/Ygsytq+R995EJ5PZlD4Cu56sWa8InXySaViRzw9apusqsOO2bQP+SbYzAhR0pFKoB+43lYy8rWban9JSuXnA==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 es-errors: 1.3.0 is-data-view: 1.0.1 + dev: false - debounce@1.2.1: {} + /debounce@1.2.1: + resolution: {integrity: sha512-XRRe6Glud4rd/ZGQfiV1ruXSfbvfJedlV9Y6zOlP+2K04vBYiJEte6stfFkCP03aMnY5tsipamumUjL14fofug==} + dev: false - debug@2.6.9: + /debug@2.6.9: + resolution: {integrity: sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==} + peerDependencies: + supports-color: '*' + peerDependenciesMeta: + supports-color: + optional: true dependencies: ms: 2.0.0 + dev: false - debug@4.3.6: + /debug@4.3.6: + resolution: {integrity: sha512-O/09Bd4Z1fBrU4VzkhFqVgpPzaGbw6Sm9FEkBT1A/YBXQFGuuSxa1dN2nxgxS34JmKXqYx8CZAwEVoJFImUXIg==} + engines: {node: '>=6.0'} + peerDependencies: + supports-color: '*' + peerDependenciesMeta: + supports-color: + optional: true dependencies: ms: 2.1.2 + dev: false - decompress-response@3.3.0: + /decompress-response@3.3.0: + resolution: {integrity: sha512-BzRPQuY1ip+qDonAOz42gRm/pg9F768C+npV/4JOsxRC2sq+Rlk+Q4ZCAsOhnIaMrgarILY+RMUIvMmmX1qAEA==} + engines: {node: '>=4'} dependencies: mimic-response: 1.0.1 + dev: false - deep-extend@0.6.0: {} + /deep-extend@0.6.0: + resolution: {integrity: sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==} + engines: {node: '>=4.0.0'} - deepmerge@4.3.1: {} + /deepmerge@4.3.1: + resolution: {integrity: sha512-3sUqbMEc77XqpdNO7FRyRog+eW3ph+GYCbj+rK+uYyRMuwsVy0rMiVtPn+QJlKFvWP/1PYpapqYn0Me2knFn+A==} + engines: {node: '>=0.10.0'} + dev: false - default-gateway@6.0.3: + /default-gateway@6.0.3: + resolution: {integrity: sha512-fwSOJsbbNzZ/CUFpqFBqYfYNLj1NbMPm8MMCIzHjC83iSJRBEGmDUxU+WP661BaBQImeC2yHwXtz+P/O9o+XEg==} + engines: {node: '>= 10'} dependencies: execa: 5.1.1 + dev: false - defer-to-connect@1.1.3: {} + /defer-to-connect@1.1.3: + resolution: {integrity: sha512-0ISdNousHvZT2EiFlZeZAHBUvSxmKswVCEf8hW7KWgG4a8MVEu/3Vb6uWYozkjylyCxe0JBIiRB1jV45S70WVQ==} + dev: false - define-data-property@1.1.4: + /define-data-property@1.1.4: + resolution: {integrity: sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A==} + engines: {node: '>= 0.4'} dependencies: es-define-property: 1.0.0 es-errors: 1.3.0 gopd: 1.0.1 + dev: false - define-lazy-prop@2.0.0: {} + /define-lazy-prop@2.0.0: + resolution: {integrity: sha512-Ds09qNh8yw3khSjiJjiUInaGX9xlqZDY7JVryGxdxV7NPeuqQfplOpQ66yJFZut3jLa5zOwkXw1g9EI2uKh4Og==} + engines: {node: '>=8'} + dev: false - define-properties@1.2.1: + /define-properties@1.2.1: + resolution: {integrity: sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==} + engines: {node: '>= 0.4'} dependencies: define-data-property: 1.1.4 has-property-descriptors: 1.0.2 object-keys: 1.1.1 + dev: false - del@6.1.1: + /del@6.1.1: + resolution: {integrity: sha512-ua8BhapfP0JUJKC/zV9yHHDW/rDoDxP4Zhn3AkA6/xT6gY7jYXJiaeyBZznYVujhZZET+UgcbZiQ7sN3WqcImg==} + engines: {node: '>=10'} dependencies: globby: 11.1.0 graceful-fs: 4.2.11 @@ -8029,44 +4715,82 @@ snapshots: p-map: 4.0.0 rimraf: 3.0.2 slash: 3.0.0 + dev: false - delayed-stream@1.0.0: {} + /delayed-stream@1.0.0: + resolution: {integrity: sha512-ZySD7Nf91aLB0RxL4KGrKHBXl7Eds1DAmEdcoVawXnLD7SDhpNgtuII2aAkg7a7QS41jxPSZ17p4VdGnMHk3MQ==} + engines: {node: '>=0.4.0'} + dev: false - depd@1.1.2: {} + /depd@1.1.2: + resolution: {integrity: sha512-7emPTl6Dpo6JRXOXjLRxck+FlLRX5847cLKEn00PLAgc3g2hTZZgr+e4c2v6QpSmLeFP3n5yUo7ft6avBK/5jQ==} + engines: {node: '>= 0.6'} + dev: false - depd@2.0.0: {} + /depd@2.0.0: + resolution: {integrity: sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw==} + engines: {node: '>= 0.8'} + dev: false - destroy@1.2.0: {} + /destroy@1.2.0: + resolution: {integrity: sha512-2sJGJTaXIIaR1w4iJSNoN0hnMY7Gpc/n8D4qSCJw8QqFWXf7cuAgnEHxBpweaVcPevC2l3KpjYCx3NypQQgaJg==} + engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16} + dev: false - detab@2.0.4: + /detab@2.0.4: + resolution: {integrity: sha512-8zdsQA5bIkoRECvCrNKPla84lyoR7DSAyf7p0YgXzBO9PDJx8KntPUay7NS6yp+KdxdVtiE5SpHKtbp2ZQyA9g==} dependencies: repeat-string: 1.6.1 + dev: false - detect-node@2.1.0: {} + /detect-node@2.1.0: + resolution: {integrity: sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g==} + dev: false - detect-port-alt@1.1.6: + /detect-port-alt@1.1.6: + resolution: {integrity: sha512-5tQykt+LqfJFBEYaDITx7S7cR7mJ/zQmLXZ2qt5w04ainYZw6tBf9dBunMjVeVOdYVRUzUOE4HkY5J7+uttb5Q==} + engines: {node: '>= 4.2.1'} + hasBin: true dependencies: address: 1.2.2 debug: 2.6.9 transitivePeerDependencies: - supports-color + dev: false - detect-port@1.6.1: + /detect-port@1.6.1: + resolution: {integrity: sha512-CmnVc+Hek2egPx1PeTFVta2W78xy2K/9Rkf6cC4T59S50tVnzKj+tnx5mmx5lwvCkujZ4uRrpRSuV+IVs3f90Q==} + engines: {node: '>= 4.0.0'} + hasBin: true dependencies: address: 1.2.2 debug: 4.3.6 transitivePeerDependencies: - supports-color + dev: false - dir-glob@3.0.1: + /dir-glob@3.0.1: + resolution: {integrity: sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==} + engines: {node: '>=8'} dependencies: path-type: 4.0.0 + dev: false - dns-packet@5.6.1: + /dns-packet@5.6.1: + resolution: {integrity: sha512-l4gcSouhcgIKRvyy99RNVOgxXiicE+2jZoNmaNmZ6JXiGajBOJAesk1OBlJuM5k2c+eudGdLxDqXuPCKIj6kpw==} + engines: {node: '>=6'} dependencies: '@leichtgewicht/ip-codec': 2.0.5 + dev: false - docusaurus-theme-search-typesense@0.8.0(@algolia/client-search@4.24.0)(@babel/runtime@7.25.4)(@docusaurus/core@2.2.0)(@docusaurus/theme-common@2.2.0)(@swc/core@1.7.18)(@types/react@18.3.4)(algoliasearch@4.24.0)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + /docusaurus-theme-search-typesense@0.8.0(@algolia/client-search@4.24.0)(@babel/runtime@7.25.4)(@docusaurus/core@2.2.0)(@docusaurus/theme-common@2.2.0)(@swc/core@1.7.18)(@types/react@18.3.4)(algoliasearch@4.24.0)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4): + resolution: {integrity: sha512-7cQVHJFtSYg2yT8xhzw6MpudAUZzPjvs51dU3Jwn2WBY+Qek2hHpej9gArd5UaRPffJIZqwBheVCxPpT3kkbdA==} + engines: {node: '>=16.14'} + peerDependencies: + '@docusaurus/core': 2.2.0 + '@docusaurus/theme-common': 2.2.0 + react: ^16.8.4 || ^17.0.2 + react-dom: ^16.8.4 || ^17.0.2 dependencies: '@docusaurus/core': 2.2.0(@docusaurus/types@2.2.0)(@swc/core@1.7.18)(react-dom@17.0.2)(react@17.0.2)(typescript@5.5.4) '@docusaurus/logger': 2.2.0 @@ -8108,111 +4832,179 @@ snapshots: - utf-8-validate - vue-template-compiler - webpack-cli + dev: false - dom-converter@0.2.0: + /dom-converter@0.2.0: + resolution: {integrity: sha512-gd3ypIPfOMr9h5jIKq8E3sHOTCjeirnl0WK5ZdS1AW0Odt0b1PaWaHdJ4Qk4klv+YB9aJBS7mESXjFoDQPu6DA==} dependencies: utila: 0.4.0 + dev: false - dom-serializer@0.2.2: + /dom-serializer@0.2.2: + resolution: {integrity: sha512-2/xPb3ORsQ42nHYiSunXkDjPLBaEj/xTwUO4B7XCZQTRk7EBtTOPaygh10YAAh2OI1Qrp6NWfpAhzswj0ydt9g==} dependencies: domelementtype: 2.3.0 entities: 2.2.0 + dev: false - dom-serializer@1.4.1: + /dom-serializer@1.4.1: + resolution: {integrity: sha512-VHwB3KfrcOOkelEG2ZOfxqLZdfkil8PtJi4P8N2MMXucZq2yLp75ClViUlOVwyoHEDjYU433Aq+5zWP61+RGag==} dependencies: domelementtype: 2.3.0 domhandler: 4.3.1 entities: 2.2.0 + dev: false - dom-serializer@2.0.0: + /dom-serializer@2.0.0: + resolution: {integrity: sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==} dependencies: domelementtype: 2.3.0 domhandler: 5.0.3 entities: 4.5.0 + dev: false - domelementtype@1.3.1: {} + /domelementtype@1.3.1: + resolution: {integrity: sha512-BSKB+TSpMpFI/HOxCNr1O8aMOTZ8hT3pM3GQ0w/mWRmkhEDSFJkkyzz4XQsBV44BChwGkrDfMyjVD0eA2aFV3w==} + dev: false - domelementtype@2.3.0: {} + /domelementtype@2.3.0: + resolution: {integrity: sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==} + dev: false - domhandler@4.3.1: + /domhandler@4.3.1: + resolution: {integrity: sha512-GrwoxYN+uWlzO8uhUXRl0P+kHE4GtVPfYzVLcUxPL7KNdHKj66vvlhiweIHqYYXWlw+T8iLMp42Lm67ghw4WMQ==} + engines: {node: '>= 4'} dependencies: domelementtype: 2.3.0 + dev: false - domhandler@5.0.3: + /domhandler@5.0.3: + resolution: {integrity: sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==} + engines: {node: '>= 4'} dependencies: domelementtype: 2.3.0 + dev: false - domutils@1.7.0: + /domutils@1.7.0: + resolution: {integrity: sha512-Lgd2XcJ/NjEw+7tFvfKxOzCYKZsdct5lczQ2ZaQY8Djz7pfAD3Gbp8ySJWtreII/vDlMVmxwa6pHmdxIYgttDg==} dependencies: dom-serializer: 0.2.2 domelementtype: 1.3.1 + dev: false - domutils@2.8.0: + /domutils@2.8.0: + resolution: {integrity: sha512-w96Cjofp72M5IIhpjgobBimYEfoPjx1Vx0BSX9P30WBdZW2WIKU0T1Bd0kz2eNZ9ikjKgHbEyKx8BB6H1L3h3A==} dependencies: dom-serializer: 1.4.1 domelementtype: 2.3.0 domhandler: 4.3.1 + dev: false - domutils@3.1.0: + /domutils@3.1.0: + resolution: {integrity: sha512-H78uMmQtI2AhgDJjWeQmHwJJ2bLPD3GMmO7Zja/ZZh84wkm+4ut+IUnUdRa8uCGX88DiVx1j6FRe1XfxEgjEZA==} dependencies: dom-serializer: 2.0.0 domelementtype: 2.3.0 domhandler: 5.0.3 + dev: false - dot-case@3.0.4: + /dot-case@3.0.4: + resolution: {integrity: sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==} dependencies: no-case: 3.0.4 tslib: 2.7.0 + dev: false - dot-prop@5.3.0: + /dot-prop@5.3.0: + resolution: {integrity: sha512-QM8q3zDe58hqUqjraQOmzZ1LIH9SWQJTlEKCH4kJ2oQvLZk7RbQXvtDM2XEq3fwkV9CCvvH4LA0AV+ogFsBM2Q==} + engines: {node: '>=8'} dependencies: is-obj: 2.0.0 + dev: false - duplexer3@0.1.5: {} + /duplexer3@0.1.5: + resolution: {integrity: sha512-1A8za6ws41LQgv9HrE/66jyC5yuSjQ3L/KOpFtoBilsAK2iA2wuS5rTt1OCzIvtS2V7nVmedsUU+DGRcjBmOYA==} + dev: false - duplexer@0.1.2: {} + /duplexer@0.1.2: + resolution: {integrity: sha512-jtD6YG370ZCIi/9GTaJKQxWTZD045+4R4hTk/x1UyoqadyJ9x9CgSi1RlVDQF8U2sxLLSnFkCaMihqljHIWgMg==} + dev: false - eastasianwidth@0.2.0: {} + /eastasianwidth@0.2.0: + resolution: {integrity: sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==} - ee-first@1.1.1: {} + /ee-first@1.1.1: + resolution: {integrity: sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==} + dev: false - electron-to-chromium@1.5.13: {} + /electron-to-chromium@1.5.13: + resolution: {integrity: sha512-lbBcvtIJ4J6sS4tb5TLp1b4LyfCdMkwStzXPyAgVgTRAsep4bvrAGaBOP7ZJtQMNJpSQ9SqG4brWOroNaQtm7Q==} + dev: false - emoji-regex@8.0.0: {} + /emoji-regex@8.0.0: + resolution: {integrity: sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==} - emoji-regex@9.2.2: {} + /emoji-regex@9.2.2: + resolution: {integrity: sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==} - emojis-list@3.0.0: {} + /emojis-list@3.0.0: + resolution: {integrity: sha512-/kyM18EfinwXZbno9FyUGeFh87KC8HRQBQGildHZbEuRyWFOmv1U10o9BBp8XVZDVNNuQKyIGIu5ZYAAXJ0V2Q==} + engines: {node: '>= 4'} + dev: false - emoticon@3.2.0: {} + /emoticon@3.2.0: + resolution: {integrity: sha512-SNujglcLTTg+lDAcApPNgEdudaqQFiAbJCqzjNxJkvN9vAwCGi0uu8IUVvx+f16h+V44KCY6Y2yboroc9pilHg==} + dev: false - encodeurl@1.0.2: {} + /encodeurl@1.0.2: + resolution: {integrity: sha512-TPJXq8JqFaVYm2CWmPvnP2Iyo4ZSM7/QKcSmuMLDObfpH5fi7RUGmd/rTDf+rut/saiDiQEeVTNgAmJEdAOx0w==} + engines: {node: '>= 0.8'} + dev: false - encoding-sniffer@0.2.0: + /encoding-sniffer@0.2.0: + resolution: {integrity: sha512-ju7Wq1kg04I3HtiYIOrUrdfdDvkyO9s5XM8QAj/bN61Yo/Vb4vgJxy5vi4Yxk01gWHbrofpPtpxM8bKger9jhg==} dependencies: iconv-lite: 0.6.3 whatwg-encoding: 3.1.1 + dev: false - end-of-stream@1.4.4: + /end-of-stream@1.4.4: + resolution: {integrity: sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q==} dependencies: once: 1.4.0 + dev: false - enhanced-resolve@5.17.1: + /enhanced-resolve@5.17.1: + resolution: {integrity: sha512-LMHl3dXhTcfv8gM4kEzIUeTQ+7fpdA0l2tUf34BddXPkz2A5xJ5L/Pchd5BL6rdccM9QGvu0sWZzK1Z1t4wwyg==} + engines: {node: '>=10.13.0'} dependencies: graceful-fs: 4.2.11 tapable: 2.2.1 + dev: false - entities@2.2.0: {} + /entities@2.2.0: + resolution: {integrity: sha512-p92if5Nz619I0w+akJrLZH0MX0Pb5DX39XOwQTtXSdQQOaYH03S1uIQp4mhOZtAXrxq4ViO67YTiLBo2638o9A==} + dev: false - entities@3.0.1: {} + /entities@3.0.1: + resolution: {integrity: sha512-WiyBqoomrwMdFG1e0kqvASYfnlb0lp8M5o5Fw2OFq1hNZxxcNk8Ik0Xm7LxzBhuidnZB/UtBqVCgUz3kBOP51Q==} + engines: {node: '>=0.12'} + dev: true - entities@4.5.0: {} + /entities@4.5.0: + resolution: {integrity: sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==} + engines: {node: '>=0.12'} + dev: false - error-ex@1.3.2: + /error-ex@1.3.2: + resolution: {integrity: sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==} dependencies: is-arrayish: 0.2.1 + dev: false - es-abstract@1.23.3: + /es-abstract@1.23.3: + resolution: {integrity: sha512-e+HfNH61Bj1X9/jLc5v1owaLYuHdeHHSQlkhCBiTK8rBvKaULl/beGMxwrMXjpYrv4pz22BlY570vVePA2ho4A==} + engines: {node: '>= 0.4'} dependencies: array-buffer-byte-length: 1.0.1 arraybuffer.prototype.slice: 1.0.3 @@ -8260,74 +5052,143 @@ snapshots: typed-array-length: 1.0.6 unbox-primitive: 1.0.2 which-typed-array: 1.1.15 + dev: false - es-array-method-boxes-properly@1.0.0: {} + /es-array-method-boxes-properly@1.0.0: + resolution: {integrity: sha512-wd6JXUmyHmt8T5a2xreUwKcGPq6f1f+WwIJkijUqiGcJz1qqnZgP6XIK+QyIWU5lT7imeNxUll48bziG+TSYcA==} + dev: false - es-define-property@1.0.0: + /es-define-property@1.0.0: + resolution: {integrity: sha512-jxayLKShrEqqzJ0eumQbVhTYQM27CfT1T35+gCgDFoL82JLsXqTJ76zv6A0YLOgEnLUMvLzsDsGIrl8NFpT2gQ==} + engines: {node: '>= 0.4'} dependencies: get-intrinsic: 1.2.4 + dev: false - es-errors@1.3.0: {} + /es-errors@1.3.0: + resolution: {integrity: sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==} + engines: {node: '>= 0.4'} + dev: false - es-module-lexer@1.5.4: {} + /es-module-lexer@1.5.4: + resolution: {integrity: sha512-MVNK56NiMrOwitFB7cqDwq0CQutbw+0BvLshJSse0MUNU+y1FC3bUS/AQg7oUng+/wKrrki7JfmwtVHkVfPLlw==} + dev: false - es-object-atoms@1.0.0: + /es-object-atoms@1.0.0: + resolution: {integrity: sha512-MZ4iQ6JwHOBQjahnjwaC1ZtIBH+2ohjamzAO3oaHcXYup7qxjF2fixyH+Q71voWHeOkI2q/TnJao/KfXYIZWbw==} + engines: {node: '>= 0.4'} dependencies: es-errors: 1.3.0 + dev: false - es-set-tostringtag@2.0.3: + /es-set-tostringtag@2.0.3: + resolution: {integrity: sha512-3T8uNMC3OQTHkFUsFq8r/BwAXLHvU/9O9mE0fBc/MY5iq/8H7ncvO947LmYA6ldWw9Uh8Yhf25zu6n7nML5QWQ==} + engines: {node: '>= 0.4'} dependencies: get-intrinsic: 1.2.4 has-tostringtag: 1.0.2 hasown: 2.0.2 + dev: false - es-to-primitive@1.2.1: + /es-to-primitive@1.2.1: + resolution: {integrity: sha512-QCOllgZJtaUo9miYBcLChTUaHNjJF3PYs1VidD7AwiEj1kYxKeQTctLAezAOH5ZKRH0g2IgPn6KwB4IT8iRpvA==} + engines: {node: '>= 0.4'} dependencies: is-callable: 1.2.7 is-date-object: 1.0.5 is-symbol: 1.0.4 + dev: false - escalade@3.1.2: {} + /escalade@3.1.2: + resolution: {integrity: sha512-ErCHMCae19vR8vQGe50xIsVomy19rg6gFu3+r3jkEO46suLMWBksvVyoGgQV+jOfl84ZSOSlmv6Gxa89PmTGmA==} + engines: {node: '>=6'} + dev: false - escape-goat@2.1.1: {} + /escape-goat@2.1.1: + resolution: {integrity: sha512-8/uIhbG12Csjy2JEW7D9pHbreaVaS/OpN3ycnyvElTdwM5n6GY6W6e2IPemfvGZeUMqZ9A/3GqIZMgKnBhAw/Q==} + engines: {node: '>=8'} + dev: false - escape-html@1.0.3: {} + /escape-html@1.0.3: + resolution: {integrity: sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==} + dev: false - escape-string-regexp@1.0.5: {} + /escape-string-regexp@1.0.5: + resolution: {integrity: sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==} + engines: {node: '>=0.8.0'} + dev: false - escape-string-regexp@4.0.0: {} + /escape-string-regexp@4.0.0: + resolution: {integrity: sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==} + engines: {node: '>=10'} + dev: false - eslint-scope@5.1.1: + /eslint-scope@5.1.1: + resolution: {integrity: sha512-2NxwbF/hZ0KpepYN0cNbo+FN6XoK7GaHlQhgx/hIZl6Va0bF45RQOOwhLIy8lQDbuCiadSLCBnH2CFYquit5bw==} + engines: {node: '>=8.0.0'} dependencies: esrecurse: 4.3.0 estraverse: 4.3.0 + dev: false - esprima@4.0.1: {} + /esprima@4.0.1: + resolution: {integrity: sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==} + engines: {node: '>=4'} + hasBin: true + dev: false - esrecurse@4.3.0: + /esrecurse@4.3.0: + resolution: {integrity: sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==} + engines: {node: '>=4.0'} dependencies: estraverse: 5.3.0 + dev: false - estraverse@4.3.0: {} + /estraverse@4.3.0: + resolution: {integrity: sha512-39nnKffWz8xN1BU/2c79n9nB9HDzo0niYUqx6xyqUnyoAnQyyWpOTdZEeiCch8BBu515t4wp9ZmgVfVhn9EBpw==} + engines: {node: '>=4.0'} + dev: false - estraverse@5.3.0: {} + /estraverse@5.3.0: + resolution: {integrity: sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==} + engines: {node: '>=4.0'} + dev: false - esutils@2.0.3: {} + /esutils@2.0.3: + resolution: {integrity: sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==} + engines: {node: '>=0.10.0'} + dev: false - eta@1.14.2: {} + /eta@1.14.2: + resolution: {integrity: sha512-wZmJAV7EFUG5W8XNXSazIdichnWEhGB1OWg4tnXWPj0CPNUcFdgorGNO6N9p6WBUgoUe4P0OziJYn1+6zxP2aQ==} + engines: {node: '>=6.0.0'} + dev: false - etag@1.8.1: {} + /etag@1.8.1: + resolution: {integrity: sha512-aIL5Fx7mawVa300al2BnEE4iNvo1qETxLrPI/o05L7z6go7fCw1J6EQmbK4FmJ2AS7kgVF/KEZWufBfdClMcPg==} + engines: {node: '>= 0.6'} + dev: false - eval@0.1.8: + /eval@0.1.8: + resolution: {integrity: sha512-EzV94NYKoO09GLXGjXj9JIlXijVck4ONSr5wiCWDvhsvj5jxSrzTmRU/9C1DyB6uToszLs8aifA6NQ7lEQdvFw==} + engines: {node: '>= 0.8'} dependencies: '@types/node': 22.5.0 require-like: 0.1.2 + dev: false - eventemitter3@4.0.7: {} + /eventemitter3@4.0.7: + resolution: {integrity: sha512-8guHBZCwKnFhYdHr2ysuRWErTwhoN2X8XELRlrRwpmfeY2jjuUN4taQMsULKUVo1K4DvZl+0pgfyoysHxvmvEw==} + dev: false - events@3.3.0: {} + /events@3.3.0: + resolution: {integrity: sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==} + engines: {node: '>=0.8.x'} + dev: false - execa@5.1.1: + /execa@5.1.1: + resolution: {integrity: sha512-8uSpZZocAZRBAPIEINJj3Lo9HyGitllczc27Eh5YYojjMFMn8yHMDMaUHE2Jqfq05D/wucwI4JGURyXt1vchyg==} + engines: {node: '>=10'} dependencies: cross-spawn: 7.0.3 get-stream: 6.0.1 @@ -8338,8 +5199,11 @@ snapshots: onetime: 5.1.2 signal-exit: 3.0.7 strip-final-newline: 2.0.0 + dev: false - express@4.19.2: + /express@4.19.2: + resolution: {integrity: sha512-5T6nhjsT+EOMzuck8JjBHARTHfMht0POzlA60WV2pMD3gyXw2LZnZ+ueGdNxG+0calOJcWKbpFcuzLZ91YWq9Q==} + engines: {node: '>= 0.10.0'} dependencies: accepts: 1.3.8 array-flatten: 1.1.1 @@ -8374,48 +5238,75 @@ snapshots: vary: 1.1.2 transitivePeerDependencies: - supports-color + dev: false - extend-shallow@2.0.1: + /extend-shallow@2.0.1: + resolution: {integrity: sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==} + engines: {node: '>=0.10.0'} dependencies: is-extendable: 0.1.1 + dev: false - extend@3.0.2: {} + /extend@3.0.2: + resolution: {integrity: sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==} + dev: false - fast-deep-equal@3.1.3: {} + /fast-deep-equal@3.1.3: + resolution: {integrity: sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==} + dev: false - fast-glob@3.3.2: + /fast-glob@3.3.2: + resolution: {integrity: sha512-oX2ruAFQwf/Orj8m737Y5adxDQO0LAB7/S5MnxCdTNDd4p6BsyIVsv9JQsATbTSq8KHRpLwIHbVlUNatxd+1Ow==} + engines: {node: '>=8.6.0'} dependencies: '@nodelib/fs.stat': 2.0.5 '@nodelib/fs.walk': 1.2.8 glob-parent: 5.1.2 merge2: 1.4.1 micromatch: 4.0.8 + dev: false - fast-json-stable-stringify@2.1.0: {} + /fast-json-stable-stringify@2.1.0: + resolution: {integrity: sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==} + dev: false - fast-uri@3.0.1: {} + /fast-uri@3.0.1: + resolution: {integrity: sha512-MWipKbbYiYI0UC7cl8m/i/IWTqfC8YXsqjzybjddLsFjStroQzsHXkc73JutMvBiXmOvapk+axIl79ig5t55Bw==} + dev: false - fast-url-parser@1.1.3: + /fast-url-parser@1.1.3: + resolution: {integrity: sha512-5jOCVXADYNuRkKFzNJ0dCCewsZiYo0dz8QNYljkOpFC6r2U4OBmKtvm/Tsuh4w1YYdDqDb31a8TVhBJ2OJKdqQ==} dependencies: punycode: 1.4.1 + dev: false - fastq@1.17.1: + /fastq@1.17.1: + resolution: {integrity: sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w==} dependencies: reusify: 1.0.4 + dev: false - faye-websocket@0.11.4: + /faye-websocket@0.11.4: + resolution: {integrity: sha512-CzbClwlXAuiRQAlUyfqPgvPoNKTckTPGfwZV4ZdAhVcP2lh9KUxJg2b5GkE7XbjKQ3YJnQ9z6D9ntLAlB+tP8g==} + engines: {node: '>=0.8.0'} dependencies: websocket-driver: 0.7.4 + dev: false - fbemitter@3.0.0: + /fbemitter@3.0.0: + resolution: {integrity: sha512-KWKaceCwKQU0+HPoop6gn4eOHk50bBv/VxjJtGMfwmJt3D29JpN4H4eisCtIPA+a8GVBam+ldMMpMjJUvpDyHw==} dependencies: fbjs: 3.0.5 transitivePeerDependencies: - encoding + dev: false - fbjs-css-vars@1.0.2: {} + /fbjs-css-vars@1.0.2: + resolution: {integrity: sha512-b2XGFAFdWZWg0phtAWLHCk836A1Xann+I+Dgd3Gk64MHKZO44FfoD1KxyvbSh0qZsIoXQGGlVztIY+oitJPpRQ==} + dev: false - fbjs@3.0.5: + /fbjs@3.0.5: + resolution: {integrity: sha512-ztsSx77JBtkuMrEypfhgc3cI0+0h+svqeie7xHbh1k/IKdcydnvadp/mUaGgjAOXQmQSxsqgaRhS3q9fy+1kxg==} dependencies: cross-fetch: 3.1.8 fbjs-css-vars: 1.0.2 @@ -8426,28 +5317,47 @@ snapshots: ua-parser-js: 1.0.38 transitivePeerDependencies: - encoding + dev: false - fd-slicer@1.1.0: + /fd-slicer@1.1.0: + resolution: {integrity: sha512-cE1qsB/VwyQozZ+q1dGxR8LBYNZeofhEdUNGSMbQD3Gw2lAzX9Zb3uIU6Ebc/Fmyjo9AWWfnn0AUCHqtevs/8g==} dependencies: pend: 1.2.0 + dev: false - feed@4.2.2: + /feed@4.2.2: + resolution: {integrity: sha512-u5/sxGfiMfZNtJ3OvQpXcvotFpYkL0n9u9mM2vkui2nGo8b4wvDkJ8gAkYqbA8QpGyFCv3RK0Z+Iv+9veCS9bQ==} + engines: {node: '>=0.4.0'} dependencies: xml-js: 1.6.11 + dev: false - file-loader@6.2.0(webpack@5.94.0): + /file-loader@6.2.0(webpack@5.94.0): + resolution: {integrity: sha512-qo3glqyTa61Ytg4u73GultjHGjdRyig3tG6lPtyX/jOEJvHif9uB0/OCI2Kif6ctF3caQTW2G5gym21oAsI4pw==} + engines: {node: '>= 10.13.0'} + peerDependencies: + webpack: ^4.0.0 || ^5.0.0 dependencies: loader-utils: 2.0.4 schema-utils: 3.3.0 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - filesize@8.0.7: {} + /filesize@8.0.7: + resolution: {integrity: sha512-pjmC+bkIF8XI7fWaH8KxHcZL3DPybs1roSKP4rKDvy20tAWwIObE4+JIseG2byfGKhud5ZnM4YSGKBz7Sh0ndQ==} + engines: {node: '>= 0.4.0'} + dev: false - fill-range@7.1.1: + /fill-range@7.1.1: + resolution: {integrity: sha512-YsGpe3WHLK8ZYi4tWDg2Jy3ebRz2rXowDxnld4bkQB00cc/1Zw9AWnC0i9ztDJitivtQvaI9KaLyKrc+hBW0yg==} + engines: {node: '>=8'} dependencies: to-regex-range: 5.0.1 + dev: false - finalhandler@1.2.0: + /finalhandler@1.2.0: + resolution: {integrity: sha512-5uXcUVftlQMFnWC9qu/svkWv3GTd2PfUhK/3PLkYNAe7FbqJMt3515HaxE6eRL74GdsriiwujiawdaB1BpEISg==} + engines: {node: '>= 0.8'} dependencies: debug: 2.6.9 encodeurl: 1.0.2 @@ -8458,49 +5368,94 @@ snapshots: unpipe: 1.0.0 transitivePeerDependencies: - supports-color + dev: false - find-cache-dir@3.3.2: + /find-cache-dir@3.3.2: + resolution: {integrity: sha512-wXZV5emFEjrridIgED11OoUKLxiYjAcqot/NJdAkOhlJ+vGzwhOAfcG5OX1jP+S0PcjEn8bdMJv+g2jwQ3Onig==} + engines: {node: '>=8'} dependencies: commondir: 1.0.1 make-dir: 3.1.0 pkg-dir: 4.2.0 + dev: false - find-up@3.0.0: + /find-up@3.0.0: + resolution: {integrity: sha512-1yD6RmLI1XBfxugvORwlck6f75tYL+iR0jqwsOrOxMZyGYqUuDhJ0l4AXdO1iX/FTs9cBAMEk1gWSEx1kSbylg==} + engines: {node: '>=6'} dependencies: locate-path: 3.0.0 + dev: false - find-up@4.1.0: + /find-up@4.1.0: + resolution: {integrity: sha512-PpOwAdQ/YlXQ2vj8a3h8IipDuYRi3wceVQQGYWxNINccq40Anw7BlsEXCMbt1Zt+OLA6Fq9suIpIWD0OsnISlw==} + engines: {node: '>=8'} dependencies: locate-path: 5.0.0 path-exists: 4.0.0 + dev: false - find-up@5.0.0: + /find-up@5.0.0: + resolution: {integrity: sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==} + engines: {node: '>=10'} dependencies: locate-path: 6.0.0 path-exists: 4.0.0 + dev: false - flat@5.0.2: {} + /flat@5.0.2: + resolution: {integrity: sha512-b6suED+5/3rTpUBdG1gupIl8MPFCAMA0QXwmljLhvCUKcUvdE4gWky9zpuGCcXHOsz4J9wPGNWq6OKpmIzz3hQ==} + hasBin: true + dev: false - flux@4.0.4(react@17.0.2): + /flux@4.0.4(react@17.0.2): + resolution: {integrity: sha512-NCj3XlayA2UsapRpM7va6wU1+9rE5FIL7qoMcmxWHRzbp0yujihMBm9BBHZ1MDIk5h5o2Bl6eGiCe8rYELAmYw==} + peerDependencies: + react: ^15.0.2 || ^16.0.0 || ^17.0.0 dependencies: fbemitter: 3.0.0 fbjs: 3.0.5 react: 17.0.2 transitivePeerDependencies: - encoding + dev: false - follow-redirects@1.15.6: {} + /follow-redirects@1.15.6: + resolution: {integrity: sha512-wWN62YITEaOpSK584EZXJafH1AGpO8RVgElfkuXbTOrPX4fIfOyEpW/CsiNd8JdYrAoOvafRTOEnvsO++qCqFA==} + engines: {node: '>=4.0'} + peerDependencies: + debug: '*' + peerDependenciesMeta: + debug: + optional: true + dev: false - for-each@0.3.3: + /for-each@0.3.3: + resolution: {integrity: sha512-jqYfLp7mo9vIyQf8ykW2v7A+2N4QjeCeI5+Dz9XraiO1ign81wjiH7Fb9vSOWvQfNtmSa4H2RoQTrrXivdUZmw==} dependencies: is-callable: 1.2.7 + dev: false - foreground-child@3.3.0: + /foreground-child@3.3.0: + resolution: {integrity: sha512-Ld2g8rrAyMYFXBhEqMz8ZAHBi4J4uS1i/CxGMDnjyFWddMXLVcDp051DZfu+t7+ab7Wv6SMqpWmyFIj5UbfFvg==} + engines: {node: '>=14'} dependencies: cross-spawn: 7.0.3 signal-exit: 4.1.0 + dev: true - fork-ts-checker-webpack-plugin@6.5.3(typescript@5.5.4)(webpack@5.94.0): + /fork-ts-checker-webpack-plugin@6.5.3(typescript@5.5.4)(webpack@5.94.0): + resolution: {integrity: sha512-SbH/l9ikmMWycd5puHJKTkZJKddF4iRLyW3DeZ08HTI7NGyLS38MXd/KGgeWumQO7YNQbW2u/NtPT2YowbPaGQ==} + engines: {node: '>=10', yarn: '>=1.0.0'} + peerDependencies: + eslint: '>= 6' + typescript: '>= 2.7' + vue-template-compiler: '*' + webpack: '>= 4' + peerDependenciesMeta: + eslint: + optional: true + vue-template-compiler: + optional: true dependencies: '@babel/code-frame': 7.24.7 '@types/json-schema': 7.0.15 @@ -8517,105 +5472,180 @@ snapshots: tapable: 1.1.3 typescript: 5.5.4 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - form-data@4.0.0: + /form-data@4.0.0: + resolution: {integrity: sha512-ETEklSGi5t0QMZuiXoA/Q6vcnxcLQP5vdugSpuAyi6SVGi2clPPp+xgEhuMaHC+zGgn31Kd235W35f7Hykkaww==} + engines: {node: '>= 6'} dependencies: asynckit: 0.4.0 combined-stream: 1.0.8 mime-types: 2.1.35 + dev: false - forwarded@0.2.0: {} + /forwarded@0.2.0: + resolution: {integrity: sha512-buRG0fpBtRHSTCOASe6hD258tEubFoRLb4ZNA6NxMVHNw2gOcwHo9wyablzMzOA5z9xA9L1KNjk/Nt6MT9aYow==} + engines: {node: '>= 0.6'} + dev: false - fraction.js@4.3.7: {} + /fraction.js@4.3.7: + resolution: {integrity: sha512-ZsDfxO51wGAXREY55a7la9LScWpwv9RxIrYABrlvOFBlH/ShPnrtsXeuUIfXKKOVicNxQ+o8JTbJvjS4M89yew==} + dev: false - fresh@0.5.2: {} + /fresh@0.5.2: + resolution: {integrity: sha512-zJ2mQYM18rEFOudeV4GShTGIQ7RbzA7ozbU9I/XBpm7kqgMywgmylMwXHxZJmkVoYkna9d2pVXVXPdYTP9ej8Q==} + engines: {node: '>= 0.6'} + dev: false - fs-extra@10.1.0: + /fs-extra@10.1.0: + resolution: {integrity: sha512-oRXApq54ETRj4eMiFzGnHWGy+zo5raudjuxN0b8H7s/RU2oW0Wvsx9O0ACRN/kRq9E8Vu/ReskGB5o3ji+FzHQ==} + engines: {node: '>=12'} dependencies: graceful-fs: 4.2.11 jsonfile: 6.1.0 universalify: 2.0.1 + dev: false - fs-extra@9.1.0: + /fs-extra@9.1.0: + resolution: {integrity: sha512-hcg3ZmepS30/7BSFqRvoo3DOMQu7IjqxO5nCDt+zM9XWjb33Wg7ziNT+Qvqbuc3+gWpzO02JubVyk2G4Zvo1OQ==} + engines: {node: '>=10'} dependencies: at-least-node: 1.0.0 graceful-fs: 4.2.11 jsonfile: 6.1.0 universalify: 2.0.1 + dev: false - fs-minipass@1.2.7: + /fs-minipass@1.2.7: + resolution: {integrity: sha512-GWSSJGFy4e9GUeCcbIkED+bgAoFyj7XF1mV8rma3QW4NIqX9Kyx79N/PF61H5udOV3aY1IaMLs6pGbH71nlCTA==} dependencies: minipass: 2.9.0 + dev: false - fs-monkey@1.0.6: {} + /fs-monkey@1.0.6: + resolution: {integrity: sha512-b1FMfwetIKymC0eioW7mTywihSQE4oLzQn1dB6rZB5fx/3NpNEdAWeCSMB+60/AeT0TCXsxzAlcYVEFCTAksWg==} + dev: false - fs.realpath@1.0.0: {} + /fs.realpath@1.0.0: + resolution: {integrity: sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==} + dev: false - fsevents@2.3.3: + /fsevents@2.3.3: + resolution: {integrity: sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==} + engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0} + os: [darwin] + requiresBuild: true + dev: false optional: true - function-bind@1.1.2: {} + /function-bind@1.1.2: + resolution: {integrity: sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==} + dev: false - function.prototype.name@1.1.6: + /function.prototype.name@1.1.6: + resolution: {integrity: sha512-Z5kx79swU5P27WEayXM1tBi5Ze/lbIyiNgU3qyXUOf9b2rgXYyF9Dy9Cx+IQv/Lc8WCG6L82zwUPpSS9hGehIg==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 define-properties: 1.2.1 es-abstract: 1.23.3 functions-have-names: 1.2.3 + dev: false - functions-have-names@1.2.3: {} + /functions-have-names@1.2.3: + resolution: {integrity: sha512-xckBUXyTIqT97tq2x2AMb+g163b5JFysYk0x4qxNFwbfQkmNZoiRHb6sPzI9/QV33WeuvVYBUIiD4NzNIyqaRQ==} + dev: false - gensync@1.0.0-beta.2: {} + /gensync@1.0.0-beta.2: + resolution: {integrity: sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==} + engines: {node: '>=6.9.0'} + dev: false - get-intrinsic@1.2.4: + /get-intrinsic@1.2.4: + resolution: {integrity: sha512-5uYhsJH8VJBTv7oslg4BznJYhDoRI6waYCxMmCdnTrcCrHA/fCFKoTFz2JKKE0HdDFUF7/oQuhzumXJK7paBRQ==} + engines: {node: '>= 0.4'} dependencies: es-errors: 1.3.0 function-bind: 1.1.2 has-proto: 1.0.3 has-symbols: 1.0.3 hasown: 2.0.2 + dev: false - get-own-enumerable-property-symbols@3.0.2: {} + /get-own-enumerable-property-symbols@3.0.2: + resolution: {integrity: sha512-I0UBV/XOz1XkIJHEUDMZAbzCThU/H8DxmSfmdGcKPnVhu2VfFqr34jr9777IyaTYvxjedWhqVIilEDsCdP5G6g==} + dev: false - get-stdin@9.0.0: {} + /get-stdin@9.0.0: + resolution: {integrity: sha512-dVKBjfWisLAicarI2Sf+JuBE/DghV4UzNAVe9yhEJuzeREd3JhOTE9cUaJTeSa77fsbQUK3pcOpJfM59+VKZaA==} + engines: {node: '>=12'} + dev: true - get-stream@4.1.0: + /get-stream@4.1.0: + resolution: {integrity: sha512-GMat4EJ5161kIy2HevLlr4luNjBgvmj413KaQA7jt4V8B4RDsfpHk7WQ9GVqfYyyx8OS/L66Kox+rJRNklLK7w==} + engines: {node: '>=6'} dependencies: pump: 3.0.0 + dev: false - get-stream@5.2.0: + /get-stream@5.2.0: + resolution: {integrity: sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==} + engines: {node: '>=8'} dependencies: pump: 3.0.0 + dev: false - get-stream@6.0.1: {} + /get-stream@6.0.1: + resolution: {integrity: sha512-ts6Wi+2j3jQjqi70w5AlN8DFnkSwC+MqmxEzdEALB2qXZYV3X/b1CTfgPLGJNMeAWxdPfU8FO1ms3NUfaHCPYg==} + engines: {node: '>=10'} + dev: false - get-symbol-description@1.0.2: + /get-symbol-description@1.0.2: + resolution: {integrity: sha512-g0QYk1dZBxGwk+Ngc+ltRH2IBp2f7zBkBMBJZCDerh6EhlhSR6+9irMCuT/09zD6qkarHUSn529sK/yL4S27mg==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 es-errors: 1.3.0 get-intrinsic: 1.2.4 + dev: false - github-slugger@1.5.0: {} + /github-slugger@1.5.0: + resolution: {integrity: sha512-wIh+gKBI9Nshz2o46B0B3f5k/W+WI9ZAv6y5Dn5WJ5SK1t0TnDimB4WE5rmTD05ZAIn8HALCZVmCsvj0w0v0lw==} + dev: false - glob-parent@5.1.2: + /glob-parent@5.1.2: + resolution: {integrity: sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==} + engines: {node: '>= 6'} dependencies: is-glob: 4.0.3 + dev: false - glob-parent@6.0.2: + /glob-parent@6.0.2: + resolution: {integrity: sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==} + engines: {node: '>=10.13.0'} dependencies: is-glob: 4.0.3 + dev: false - glob-to-regexp@0.4.1: {} + /glob-to-regexp@0.4.1: + resolution: {integrity: sha512-lkX1HJXwyMcprw/5YUZc2s7DrpAiHB21/V+E1rHUrVNokkvB6bqMzT0VfV6/86ZNabt1k14YOIaT7nDvOX3Iiw==} + dev: false - glob@10.2.7: + /glob@10.2.7: + resolution: {integrity: sha512-jTKehsravOJo8IJxUGfZILnkvVJM/MOfHRs8QcXolVef2zNI9Tqyy5+SeuOAZd3upViEZQLyFpQhYiHLrMUNmA==} + engines: {node: '>=16 || 14 >=14.17'} + hasBin: true dependencies: foreground-child: 3.3.0 jackspeak: 2.3.6 minimatch: 9.0.5 minipass: 6.0.2 path-scurry: 1.11.1 + dev: true - glob@7.2.3: + /glob@7.2.3: + resolution: {integrity: sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==} + deprecated: Glob versions prior to v9 are no longer supported dependencies: fs.realpath: 1.0.0 inflight: 1.0.6 @@ -8623,29 +5653,47 @@ snapshots: minimatch: 3.1.2 once: 1.4.0 path-is-absolute: 1.0.1 + dev: false - global-dirs@3.0.1: + /global-dirs@3.0.1: + resolution: {integrity: sha512-NBcGGFbBA9s1VzD41QXDG+3++t9Mn5t1FpLdhESY6oKY4gYTFpX4wO3sqGUa0Srjtbfj3szX0RnemmrVRUdULA==} + engines: {node: '>=10'} dependencies: ini: 2.0.0 + dev: false - global-modules@2.0.0: + /global-modules@2.0.0: + resolution: {integrity: sha512-NGbfmJBp9x8IxyJSd1P+otYK8vonoJactOogrVfFRIAEY1ukil8RSKDz2Yo7wh1oihl51l/r6W4epkeKJHqL8A==} + engines: {node: '>=6'} dependencies: global-prefix: 3.0.0 + dev: false - global-prefix@3.0.0: + /global-prefix@3.0.0: + resolution: {integrity: sha512-awConJSVCHVGND6x3tmMaKcQvwXLhjdkmomy2W+Goaui8YPgYgXJZewhg3fWC+DlfqqQuWg8AwqjGTD2nAPVWg==} + engines: {node: '>=6'} dependencies: ini: 1.3.8 kind-of: 6.0.3 which: 1.3.1 + dev: false - globals@11.12.0: {} + /globals@11.12.0: + resolution: {integrity: sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==} + engines: {node: '>=4'} + dev: false - globalthis@1.0.4: + /globalthis@1.0.4: + resolution: {integrity: sha512-DpLKbNU4WylpxJykQujfCcwYWiV/Jhm50Goo0wrVILAv5jOr9d+H+UR3PhSCD2rCCEIg0uc+G+muBTwD54JhDQ==} + engines: {node: '>= 0.4'} dependencies: define-properties: 1.2.1 gopd: 1.0.1 + dev: false - globby@11.1.0: + /globby@11.1.0: + resolution: {integrity: sha512-jhIXaOzy1sb8IyocaruWSn1TjmnBVs8Ayhcy83rmxNJ8q2uWKCAj3CnJY+KpGSXCueAPc0i05kVvVKtP1t9S3g==} + engines: {node: '>=10'} dependencies: array-union: 2.1.0 dir-glob: 3.0.1 @@ -8653,20 +5701,28 @@ snapshots: ignore: 5.3.2 merge2: 1.4.1 slash: 3.0.0 + dev: false - globby@13.2.2: + /globby@13.2.2: + resolution: {integrity: sha512-Y1zNGV+pzQdh7H39l9zgB4PJqjRNqydvdYCDG4HFXM4XuvSaQQlEc91IU1yALL8gUTDomgBAfz3XJdmUS+oo0w==} + engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0} dependencies: dir-glob: 3.0.1 fast-glob: 3.3.2 ignore: 5.3.2 merge2: 1.4.1 slash: 4.0.0 + dev: false - gopd@1.0.1: + /gopd@1.0.1: + resolution: {integrity: sha512-d65bNlIadxvpb/A2abVdlqKqV563juRnZ1Wtk6s1sIR8uNsXR70xqIzVqxVf1eTqDunwT2MkczEeaezCKTZhwA==} dependencies: get-intrinsic: 1.2.4 + dev: false - got@9.6.0: + /got@9.6.0: + resolution: {integrity: sha512-R7eWptXuGYxwijs0eV+v3o6+XH1IqVK8dJOEecQfTmkncw9AV4dcw/Dhxi8MdlqPthxxpZyizMzyg8RTmEsG+Q==} + engines: {node: '>=8.6'} dependencies: '@sindresorhus/is': 0.14.0 '@szmarczak/http-timer': 1.1.2 @@ -8681,47 +5737,84 @@ snapshots: p-cancelable: 1.1.0 to-readable-stream: 1.0.0 url-parse-lax: 3.0.0 + dev: false - graceful-fs@4.2.11: {} + /graceful-fs@4.2.11: + resolution: {integrity: sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==} + dev: false - gray-matter@4.0.3: + /gray-matter@4.0.3: + resolution: {integrity: sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==} + engines: {node: '>=6.0'} dependencies: js-yaml: 3.14.1 kind-of: 6.0.3 section-matter: 1.0.0 strip-bom-string: 1.0.0 + dev: false - gzip-size@6.0.0: + /gzip-size@6.0.0: + resolution: {integrity: sha512-ax7ZYomf6jqPTQ4+XCpUGyXKHk5WweS+e05MBO4/y3WJ5RkmPXNKvX+bx1behVILVwr6JSQvZAku021CHPXG3Q==} + engines: {node: '>=10'} dependencies: duplexer: 0.1.2 + dev: false - handle-thing@2.0.1: {} + /handle-thing@2.0.1: + resolution: {integrity: sha512-9Qn4yBxelxoh2Ow62nP+Ka/kMnOXRi8BXnRaUwezLNhqelnN49xKz4F/dPP8OYLxLxq6JDtZb2i9XznUQbNPTg==} + dev: false - has-bigints@1.0.2: {} + /has-bigints@1.0.2: + resolution: {integrity: sha512-tSvCKtBr9lkF0Ex0aQiP9N+OpV4zi2r/Nee5VkRDbaqv35RLYMzbwQfFSZZH0kR+Rd6302UJZ2p/bJCEoR3VoQ==} + dev: false - has-flag@3.0.0: {} + /has-flag@3.0.0: + resolution: {integrity: sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==} + engines: {node: '>=4'} + dev: false - has-flag@4.0.0: {} + /has-flag@4.0.0: + resolution: {integrity: sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==} + engines: {node: '>=8'} + dev: false - has-property-descriptors@1.0.2: + /has-property-descriptors@1.0.2: + resolution: {integrity: sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg==} dependencies: es-define-property: 1.0.0 + dev: false - has-proto@1.0.3: {} + /has-proto@1.0.3: + resolution: {integrity: sha512-SJ1amZAJUiZS+PhsVLf5tGydlaVB8EdFpaSO4gmiUKUOxk8qzn5AIy4ZeJUmh22znIdk/uMAUT2pl3FxzVUH+Q==} + engines: {node: '>= 0.4'} + dev: false - has-symbols@1.0.3: {} + /has-symbols@1.0.3: + resolution: {integrity: sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A==} + engines: {node: '>= 0.4'} + dev: false - has-tostringtag@1.0.2: + /has-tostringtag@1.0.2: + resolution: {integrity: sha512-NqADB8VjPFLM2V0VvHUewwwsw0ZWBaIdgo+ieHtK3hasLz4qeCRjYcqfB6AQrBggRKppKF8L52/VqdVsO47Dlw==} + engines: {node: '>= 0.4'} dependencies: has-symbols: 1.0.3 + dev: false - has-yarn@2.1.0: {} + /has-yarn@2.1.0: + resolution: {integrity: sha512-UqBRqi4ju7T+TqGNdqAO0PaSVGsDGJUBQvk9eUWNGRY1CFGDzYhLWoM7JQEemnlvVcv/YEmc2wNW8BC24EnUsw==} + engines: {node: '>=8'} + dev: false - hasown@2.0.2: + /hasown@2.0.2: + resolution: {integrity: sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==} + engines: {node: '>= 0.4'} dependencies: function-bind: 1.1.2 + dev: false - hast-to-hyperscript@9.0.1: + /hast-to-hyperscript@9.0.1: + resolution: {integrity: sha512-zQgLKqF+O2F72S1aa4y2ivxzSlko3MAvxkwG8ehGmNiqd98BIN3JM1rAJPmplEyLmGLO2QZYJtIneOSZ2YbJuA==} dependencies: '@types/unist': 2.0.11 comma-separated-tokens: 1.0.8 @@ -8730,8 +5823,10 @@ snapshots: style-to-object: 0.3.0 unist-util-is: 4.1.0 web-namespaces: 1.1.4 + dev: false - hast-util-from-parse5@6.0.1: + /hast-util-from-parse5@6.0.1: + resolution: {integrity: sha512-jeJUWiN5pSxW12Rh01smtVkZgZr33wBokLzKLwinYOUfSzm1Nl/c3GUGebDyOKjdsRgMvoVbV0VpAcpjF4NrJA==} dependencies: '@types/parse5': 5.0.3 hastscript: 6.0.0 @@ -8739,10 +5834,14 @@ snapshots: vfile: 4.2.1 vfile-location: 3.2.0 web-namespaces: 1.1.4 + dev: false - hast-util-parse-selector@2.2.5: {} + /hast-util-parse-selector@2.2.5: + resolution: {integrity: sha512-7j6mrk/qqkSehsM92wQjdIgWM2/BW61u/53G6xmC8i1OmEdKLHbk419QKQUjz6LglWsfqoiHmyMRkP1BGjecNQ==} + dev: false - hast-util-raw@6.0.1: + /hast-util-raw@6.0.1: + resolution: {integrity: sha512-ZMuiYA+UF7BXBtsTBNcLBF5HzXzkyE6MLzJnL605LKE8GJylNjGc4jjxazAHUtcwT5/CEt6afRKViYB4X66dig==} dependencies: '@types/hast': 2.3.10 hast-util-from-parse5: 6.0.1 @@ -8754,26 +5853,35 @@ snapshots: web-namespaces: 1.1.4 xtend: 4.0.2 zwitch: 1.0.5 + dev: false - hast-util-to-parse5@6.0.0: + /hast-util-to-parse5@6.0.0: + resolution: {integrity: sha512-Lu5m6Lgm/fWuz8eWnrKezHtVY83JeRGaNQ2kn9aJgqaxvVkFCZQBEhgodZUDUvoodgyROHDb3r5IxAEdl6suJQ==} dependencies: hast-to-hyperscript: 9.0.1 property-information: 5.6.0 web-namespaces: 1.1.4 xtend: 4.0.2 zwitch: 1.0.5 + dev: false - hastscript@6.0.0: + /hastscript@6.0.0: + resolution: {integrity: sha512-nDM6bvd7lIqDUiYEiu5Sl/+6ReP0BMk/2f4U/Rooccxkj0P5nm+acM5PrGJ/t5I8qPGiqZSE6hVAwZEdZIvP4w==} dependencies: '@types/hast': 2.3.10 comma-separated-tokens: 1.0.8 hast-util-parse-selector: 2.2.5 property-information: 5.6.0 space-separated-tokens: 1.1.5 + dev: false - he@1.2.0: {} + /he@1.2.0: + resolution: {integrity: sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw==} + hasBin: true + dev: false - history@4.10.1: + /history@4.10.1: + resolution: {integrity: sha512-36nwAD620w12kuzPAsyINPWJqlNbij+hpK1k9XRloDtym8mxzGYl2c17LnV6IAGB2Dmg4tEa7G7DlawS0+qjew==} dependencies: '@babel/runtime': 7.25.4 loose-envify: 1.4.0 @@ -8781,23 +5889,35 @@ snapshots: tiny-invariant: 1.3.3 tiny-warning: 1.0.3 value-equal: 1.0.1 + dev: false - hoist-non-react-statics@3.3.2: + /hoist-non-react-statics@3.3.2: + resolution: {integrity: sha512-/gGivxi8JPKWNm/W0jSmzcMPpfpPLc3dY/6GxhX2hQ9iGj3aDfklV4ET7NjKpSinLpJ5vafa9iiGIEZg10SfBw==} dependencies: react-is: 16.13.1 + dev: false - hpack.js@2.1.6: + /hpack.js@2.1.6: + resolution: {integrity: sha512-zJxVehUdMGIKsRaNt7apO2Gqp0BdqW5yaiGHXXmbpvxgBYVZnAql+BJb4RO5ad2MgpbZKn5G6nMnegrH1FcNYQ==} dependencies: inherits: 2.0.4 obuf: 1.1.2 readable-stream: 2.3.8 wbuf: 1.7.3 + dev: false - html-entities@2.5.2: {} + /html-entities@2.5.2: + resolution: {integrity: sha512-K//PSRMQk4FZ78Kyau+mZurHn3FH0Vwr+H36eE0rPbeYkRRi9YxceYPhuN60UwWorxyKHhqoAJl2OFKa4BVtaA==} + dev: false - html-escaper@2.0.2: {} + /html-escaper@2.0.2: + resolution: {integrity: sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg==} + dev: false - html-minifier-terser@6.1.0: + /html-minifier-terser@6.1.0: + resolution: {integrity: sha512-YXxSlJBZTP7RS3tWnQw74ooKa6L9b9i9QYXY21eUEvhZ3u9XLfv6OnFsQq6RxkhHygsaUMvYsZRV5rU/OVNZxw==} + engines: {node: '>=12'} + hasBin: true dependencies: camel-case: 4.1.2 clean-css: 5.3.3 @@ -8806,12 +5926,28 @@ snapshots: param-case: 3.0.4 relateurl: 0.2.7 terser: 5.31.6 + dev: false - html-tags@3.3.1: {} + /html-tags@3.3.1: + resolution: {integrity: sha512-ztqyC3kLto0e9WbNp0aeP+M3kTt+nbaIveGmUxAtZa+8iFgKLUOD4YKM5j+f3QD89bra7UeumolZHKuOXnTmeQ==} + engines: {node: '>=8'} + dev: false - html-void-elements@1.0.5: {} + /html-void-elements@1.0.5: + resolution: {integrity: sha512-uE/TxKuyNIcx44cIWnjr/rfIATDH7ZaOMmstu0CwhFG1Dunhlp4OC6/NMbhiwoq5BpW0ubi303qnEk/PZj614w==} + dev: false - html-webpack-plugin@5.6.0(webpack@5.94.0): + /html-webpack-plugin@5.6.0(webpack@5.94.0): + resolution: {integrity: sha512-iwaY4wzbe48AfKLZ/Cc8k0L+FKG6oSNRaZ8x5A/T/IVDGyXcbHncM9TdDa93wn0FsSm82FhTKW7f3vS61thXAw==} + engines: {node: '>=10.13.0'} + peerDependencies: + '@rspack/core': 0.x || 1.x + webpack: ^5.20.0 + peerDependenciesMeta: + '@rspack/core': + optional: true + webpack: + optional: true dependencies: '@types/html-minifier-terser': 6.1.0 html-minifier-terser: 6.1.0 @@ -8819,43 +5955,67 @@ snapshots: pretty-error: 4.0.0 tapable: 2.2.1 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - htmlparser2@6.1.0: + /htmlparser2@6.1.0: + resolution: {integrity: sha512-gyyPk6rgonLFEDGoeRgQNaEUvdJ4ktTmmUh/h2t7s+M8oPpIPxgNACWa+6ESR57kXstwqPiCut0V8NRpcwgU7A==} dependencies: domelementtype: 2.3.0 domhandler: 4.3.1 domutils: 2.8.0 entities: 2.2.0 + dev: false - htmlparser2@9.1.0: + /htmlparser2@9.1.0: + resolution: {integrity: sha512-5zfg6mHUoaer/97TxnGpxmbR7zJtPwIYFMZ/H5ucTlPZhKvtum05yiPK3Mgai3a0DyVxv7qYqoweaEd2nrYQzQ==} dependencies: domelementtype: 2.3.0 domhandler: 5.0.3 domutils: 3.1.0 entities: 4.5.0 + dev: false - http-cache-semantics@4.1.1: {} + /http-cache-semantics@4.1.1: + resolution: {integrity: sha512-er295DKPVsV82j5kw1Gjt+ADA/XYHsajl82cGNQG2eyoPkvgUhX+nDIyelzhIWbbsXP39EHcI6l5tYs2FYqYXQ==} + dev: false - http-deceiver@1.2.7: {} + /http-deceiver@1.2.7: + resolution: {integrity: sha512-LmpOGxTfbpgtGVxJrj5k7asXHCgNZp5nLfp+hWc8QQRqtb7fUy6kRY3BO1h9ddF6yIPYUARgxGOwB42DnxIaNw==} + dev: false - http-errors@1.6.3: + /http-errors@1.6.3: + resolution: {integrity: sha512-lks+lVC8dgGyh97jxvxeYTWQFvh4uw4yC12gVl63Cg30sjPX4wuGcdkICVXDAESr6OJGjqGA8Iz5mkeN6zlD7A==} + engines: {node: '>= 0.6'} dependencies: depd: 1.1.2 inherits: 2.0.3 setprototypeof: 1.1.0 statuses: 1.5.0 + dev: false - http-errors@2.0.0: + /http-errors@2.0.0: + resolution: {integrity: sha512-FtwrG/euBzaEjYeRqOgly7G0qviiXoJWnvEH2Z1plBdXgbyjv34pHTSb9zoeHMyDy33+DWy5Wt9Wo+TURtOYSQ==} + engines: {node: '>= 0.8'} dependencies: depd: 2.0.0 inherits: 2.0.4 setprototypeof: 1.2.0 statuses: 2.0.1 toidentifier: 1.0.1 + dev: false - http-parser-js@0.5.8: {} + /http-parser-js@0.5.8: + resolution: {integrity: sha512-SGeBX54F94Wgu5RH3X5jsDtf4eHyRogWX1XGT3b4HuW3tQPM4AaBzoUji/4AAJNXCEOWZ5O0DgZmJw1947gD5Q==} + dev: false - http-proxy-middleware@2.0.6(@types/express@4.17.21): + /http-proxy-middleware@2.0.6(@types/express@4.17.21): + resolution: {integrity: sha512-ya/UeJ6HVBYxrgYotAZo1KvPWlgB48kUJLDePFeneHsVujFaW5WNj2NgWCAE//B1Dl02BIfYlpNgBy8Kf8Rjmw==} + engines: {node: '>=12.0.0'} + peerDependencies: + '@types/express': ^4.17.13 + peerDependenciesMeta: + '@types/express': + optional: true dependencies: '@types/express': 4.17.21 '@types/http-proxy': 1.17.15 @@ -8865,239 +6025,457 @@ snapshots: micromatch: 4.0.8 transitivePeerDependencies: - debug + dev: false - http-proxy@1.18.1: + /http-proxy@1.18.1: + resolution: {integrity: sha512-7mz/721AbnJwIVbnaSv1Cz3Am0ZLT/UBwkC92VlxhXv/k/BBQfM2fXElQNC27BVGr0uwUpplYPQM9LnaBMR5NQ==} + engines: {node: '>=8.0.0'} dependencies: eventemitter3: 4.0.7 follow-redirects: 1.15.6 requires-port: 1.0.0 transitivePeerDependencies: - debug + dev: false - human-signals@2.1.0: {} + /human-signals@2.1.0: + resolution: {integrity: sha512-B4FFZ6q/T2jhhksgkbEW3HBvWIfDW85snkQgawt07S7J5QXTk6BkNV+0yAeZrM5QpMAdYlocGoljn0sJ/WQkFw==} + engines: {node: '>=10.17.0'} + dev: false - iconv-lite@0.4.24: + /iconv-lite@0.4.24: + resolution: {integrity: sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==} + engines: {node: '>=0.10.0'} dependencies: safer-buffer: 2.1.2 + dev: false - iconv-lite@0.6.3: + /iconv-lite@0.6.3: + resolution: {integrity: sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==} + engines: {node: '>=0.10.0'} dependencies: safer-buffer: 2.1.2 + dev: false - icss-utils@5.1.0(postcss@8.4.41): + /icss-utils@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-soFhflCVWLfRNOPU3iv5Z9VUdT44xFRbzjLsEzSr5AQmgqPMTHdU3PMT1Cf1ssx8fLNJDA1juftYl+PUcv3MqA==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 dependencies: postcss: 8.4.41 + dev: false - ignore@5.2.4: {} + /ignore@5.2.4: + resolution: {integrity: sha512-MAb38BcSbH0eHNBxn7ql2NH/kX33OkB3lZ1BNdh7ENeRChHTYsTvWrMubiIAMNS2llXEEgZ1MUOBtXChP3kaFQ==} + engines: {node: '>= 4'} + dev: true - ignore@5.3.2: {} + /ignore@5.3.2: + resolution: {integrity: sha512-hsBTNUqQTDwkWtcdYI2i06Y/nUBEsNEDJKjWdigLvegy8kDuJAS8uRlpkkcQpyEXL0Z/pjDy5HBmMjRCJ2gq+g==} + engines: {node: '>= 4'} + dev: false - image-size@1.1.1: + /image-size@1.1.1: + resolution: {integrity: sha512-541xKlUw6jr/6gGuk92F+mYM5zaFAc5ahphvkqvNe2bQ6gVBkd6bfrmVJ2t4KDAfikAYZyIqTnktX3i6/aQDrQ==} + engines: {node: '>=16.x'} + hasBin: true dependencies: queue: 6.0.2 + dev: false - immer@9.0.21: {} + /immer@9.0.21: + resolution: {integrity: sha512-bc4NBHqOqSfRW7POMkHd51LvClaeMXpm8dx0e8oE2GORbq5aRK7Bxl4FyzVLdGtLmvLKL7BTDBG5ACQm4HWjTA==} + dev: false - import-fresh@3.3.0: + /import-fresh@3.3.0: + resolution: {integrity: sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==} + engines: {node: '>=6'} dependencies: parent-module: 1.0.1 resolve-from: 4.0.0 + dev: false - import-lazy@2.1.0: {} + /import-lazy@2.1.0: + resolution: {integrity: sha512-m7ZEHgtw69qOGw+jwxXkHlrlIPdTGkyh66zXZ1ajZbxkDBNjSY/LGbmjc7h0s2ELsUDTAhFr55TrPSSqJGPG0A==} + engines: {node: '>=4'} + dev: false - imurmurhash@0.1.4: {} + /imurmurhash@0.1.4: + resolution: {integrity: sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==} + engines: {node: '>=0.8.19'} + dev: false - indent-string@4.0.0: {} + /indent-string@4.0.0: + resolution: {integrity: sha512-EdDDZu4A2OyIK7Lr/2zG+w5jmbuk1DVBnEwREQvBzspBJkCEbRa8GxU1lghYcaGJCnRWibjDXlq779X1/y5xwg==} + engines: {node: '>=8'} + dev: false - infima@0.2.0-alpha.42: {} + /infima@0.2.0-alpha.42: + resolution: {integrity: sha512-ift8OXNbQQwtbIt6z16KnSWP7uJ/SysSMFI4F87MNRTicypfl4Pv3E2OGVv6N3nSZFJvA8imYulCBS64iyHYww==} + engines: {node: '>=12'} + dev: false - inflight@1.0.6: + /inflight@1.0.6: + resolution: {integrity: sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==} + deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. dependencies: once: 1.4.0 wrappy: 1.0.2 + dev: false - inherits@2.0.3: {} + /inherits@2.0.3: + resolution: {integrity: sha512-x00IRNXNy63jwGkJmzPigoySHbaqpNuzKbBOmzK+g2OdZpQ9w+sxCN+VSB3ja7IAge2OP2qpfxTjeNcyjmW1uw==} + dev: false - inherits@2.0.4: {} + /inherits@2.0.4: + resolution: {integrity: sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==} + dev: false - ini@1.3.8: {} + /ini@1.3.8: + resolution: {integrity: sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew==} + dev: false - ini@2.0.0: {} + /ini@2.0.0: + resolution: {integrity: sha512-7PnF4oN3CvZF23ADhA5wRaYEQpJ8qygSkbtTXWBeXWXmEVRXK+1ITciHWwHhsjv1TmW0MgacIv6hEi5pX5NQdA==} + engines: {node: '>=10'} + dev: false - ini@3.0.1: {} + /ini@3.0.1: + resolution: {integrity: sha512-it4HyVAUTKBc6m8e1iXWvXSTdndF7HbdN713+kvLrymxTaU4AUBWrJ4vEooP+V7fexnVD3LKcBshjGGPefSMUQ==} + engines: {node: ^12.13.0 || ^14.15.0 || >=16.0.0} + dev: true - inline-style-parser@0.1.1: {} + /inline-style-parser@0.1.1: + resolution: {integrity: sha512-7NXolsK4CAS5+xvdj5OMMbI962hU/wvwoxk+LWR9Ek9bVtyuuYScDN6eS0rUm6TxApFpw7CX1o4uJzcd4AyD3Q==} + dev: false - internal-slot@1.0.7: + /internal-slot@1.0.7: + resolution: {integrity: sha512-NGnrKwXzSms2qUUih/ILZ5JBqNTSa1+ZmP6flaIp6KmSElgE9qdndzS3cqjrDovwFdmwsGsLdeFgB6suw+1e9g==} + engines: {node: '>= 0.4'} dependencies: es-errors: 1.3.0 hasown: 2.0.2 side-channel: 1.0.6 + dev: false - interpret@1.4.0: {} + /interpret@1.4.0: + resolution: {integrity: sha512-agE4QfB2Lkp9uICn7BAqoscw4SZP9kTE2hxiFI3jBPmXJfdqiahTbUuKGsMoN2GtqL9AxhYioAcVvgsb1HvRbA==} + engines: {node: '>= 0.10'} + dev: false - invariant@2.2.4: + /invariant@2.2.4: + resolution: {integrity: sha512-phJfQVBuaJM5raOpJjSfkiD6BpbCE4Ns//LaXl6wGYtUBY83nWS6Rf9tXm2e8VaK60JEjYldbPif/A2B1C2gNA==} dependencies: loose-envify: 1.4.0 + dev: false - ipaddr.js@1.9.1: {} + /ipaddr.js@1.9.1: + resolution: {integrity: sha512-0KI/607xoxSToH7GjN1FfSbLoU0+btTicjsQSWQlh/hZykN8KpmMf7uYwPW3R+akZ6R/w18ZlXSHBYXiYUPO3g==} + engines: {node: '>= 0.10'} + dev: false - ipaddr.js@2.2.0: {} + /ipaddr.js@2.2.0: + resolution: {integrity: sha512-Ag3wB2o37wslZS19hZqorUnrnzSkpOVy+IiiDEiTqNubEYpYuHWIf6K4psgN2ZWKExS4xhVCrRVfb/wfW8fWJA==} + engines: {node: '>= 10'} + dev: false - is-alphabetical@1.0.4: {} + /is-alphabetical@1.0.4: + resolution: {integrity: sha512-DwzsA04LQ10FHTZuL0/grVDk4rFoVH1pjAToYwBrHSxcrBIGQuXrQMtD5U1b0U2XVgKZCTLLP8u2Qxqhy3l2Vg==} + dev: false - is-alphanumerical@1.0.4: + /is-alphanumerical@1.0.4: + resolution: {integrity: sha512-UzoZUr+XfVz3t3v4KyGEniVL9BDRoQtY7tOyrRybkVNjDFWyo1yhXNGrrBTQxp3ib9BLAWs7k2YKBQsFRkZG9A==} dependencies: is-alphabetical: 1.0.4 is-decimal: 1.0.4 + dev: false - is-array-buffer@3.0.4: + /is-array-buffer@3.0.4: + resolution: {integrity: sha512-wcjaerHw0ydZwfhiKbXJWLDY8A7yV7KhjQOpb83hGgGfId/aQa4TOvwyzn2PuswW2gPCYEL/nEAiSVpdOj1lXw==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 get-intrinsic: 1.2.4 + dev: false - is-arrayish@0.2.1: {} + /is-arrayish@0.2.1: + resolution: {integrity: sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg==} + dev: false - is-bigint@1.0.4: + /is-bigint@1.0.4: + resolution: {integrity: sha512-zB9CruMamjym81i2JZ3UMn54PKGsQzsJeo6xvN3HJJ4CAsQNB6iRutp2To77OfCNuoxspsIhzaPoO1zyCEhFOg==} dependencies: has-bigints: 1.0.2 + dev: false - is-binary-path@2.1.0: + /is-binary-path@2.1.0: + resolution: {integrity: sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==} + engines: {node: '>=8'} dependencies: binary-extensions: 2.3.0 + dev: false - is-boolean-object@1.1.2: + /is-boolean-object@1.1.2: + resolution: {integrity: sha512-gDYaKHJmnj4aWxyj6YHyXVpdQawtVLHU5cb+eztPGczf6cjuTdwve5ZIEfgXqH4e57An1D1AKf8CZ3kYrQRqYA==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 has-tostringtag: 1.0.2 + dev: false - is-buffer@2.0.5: {} + /is-buffer@2.0.5: + resolution: {integrity: sha512-i2R6zNFDwgEHJyQUtJEk0XFi1i0dPFn/oqjK3/vPCcDeJvW5NQ83V8QbicfF1SupOaB0h8ntgBC2YiE7dfyctQ==} + engines: {node: '>=4'} + dev: false - is-callable@1.2.7: {} + /is-callable@1.2.7: + resolution: {integrity: sha512-1BC0BVFhS/p0qtw6enp8e+8OD0UrK0oFLztSjNzhcKA3WDuJxxAPXzPuPtKkjEY9UUoEWlX/8fgKeu2S8i9JTA==} + engines: {node: '>= 0.4'} + dev: false - is-ci@2.0.0: + /is-ci@2.0.0: + resolution: {integrity: sha512-YfJT7rkpQB0updsdHLGWrvhBJfcfzNNawYDNIyQXJz0IViGf75O8EBPKSdvw2rF+LGCsX4FZ8tcr3b19LcZq4w==} + hasBin: true dependencies: ci-info: 2.0.0 + dev: false - is-core-module@2.15.1: + /is-core-module@2.15.1: + resolution: {integrity: sha512-z0vtXSwucUJtANQWldhbtbt7BnL0vxiFjIdDLAatwhDYty2bad6s+rijD6Ri4YuYJubLzIJLUidCh09e1djEVQ==} + engines: {node: '>= 0.4'} dependencies: hasown: 2.0.2 + dev: false - is-data-view@1.0.1: + /is-data-view@1.0.1: + resolution: {integrity: sha512-AHkaJrsUVW6wq6JS8y3JnM/GJF/9cf+k20+iDzlSaJrinEo5+7vRiteOSwBhHRiAyQATN1AmY4hwzxJKPmYf+w==} + engines: {node: '>= 0.4'} dependencies: is-typed-array: 1.1.13 + dev: false - is-date-object@1.0.5: + /is-date-object@1.0.5: + resolution: {integrity: sha512-9YQaSxsAiSwcvS33MBk3wTCVnWK+HhF8VZR2jRxehM16QcVOdHqPn4VPHmRK4lSr38n9JriurInLcP90xsYNfQ==} + engines: {node: '>= 0.4'} dependencies: has-tostringtag: 1.0.2 + dev: false - is-decimal@1.0.4: {} + /is-decimal@1.0.4: + resolution: {integrity: sha512-RGdriMmQQvZ2aqaQq3awNA6dCGtKpiDFcOzrTWrDAT2MiWrKQVPmxLGHl7Y2nNu6led0kEyoX0enY0qXYsv9zw==} + dev: false - is-docker@2.2.1: {} + /is-docker@2.2.1: + resolution: {integrity: sha512-F+i2BKsFrH66iaUFc0woD8sLy8getkwTwtOBjvs56Cx4CgJDeKQeqfz8wAYiSb8JOprWhHH5p77PbmYCvvUuXQ==} + engines: {node: '>=8'} + hasBin: true + dev: false - is-extendable@0.1.1: {} + /is-extendable@0.1.1: + resolution: {integrity: sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==} + engines: {node: '>=0.10.0'} + dev: false - is-extglob@2.1.1: {} + /is-extglob@2.1.1: + resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==} + engines: {node: '>=0.10.0'} + dev: false - is-fullwidth-code-point@3.0.0: {} + /is-fullwidth-code-point@3.0.0: + resolution: {integrity: sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==} + engines: {node: '>=8'} - is-glob@4.0.3: + /is-glob@4.0.3: + resolution: {integrity: sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==} + engines: {node: '>=0.10.0'} dependencies: is-extglob: 2.1.1 + dev: false - is-hexadecimal@1.0.4: {} + /is-hexadecimal@1.0.4: + resolution: {integrity: sha512-gyPJuv83bHMpocVYoqof5VDiZveEoGoFL8m3BXNb2VW8Xs+rz9kqO8LOQ5DH6EsuvilT1ApazU0pyl+ytbPtlw==} + dev: false - is-installed-globally@0.4.0: + /is-installed-globally@0.4.0: + resolution: {integrity: sha512-iwGqO3J21aaSkC7jWnHP/difazwS7SFeIqxv6wEtLU8Y5KlzFTjyqcSIT0d8s4+dDhKytsk9PJZ2BkS5eZwQRQ==} + engines: {node: '>=10'} dependencies: global-dirs: 3.0.1 is-path-inside: 3.0.3 + dev: false - is-negative-zero@2.0.3: {} + /is-negative-zero@2.0.3: + resolution: {integrity: sha512-5KoIu2Ngpyek75jXodFvnafB6DJgr3u8uuK0LEZJjrU19DrMD3EVERaR8sjz8CCGgpZvxPl9SuE1GMVPFHx1mw==} + engines: {node: '>= 0.4'} + dev: false - is-npm@5.0.0: {} + /is-npm@5.0.0: + resolution: {integrity: sha512-WW/rQLOazUq+ST/bCAVBp/2oMERWLsR7OrKyt052dNDk4DHcDE0/7QSXITlmi+VBcV13DfIbysG3tZJm5RfdBA==} + engines: {node: '>=10'} + dev: false - is-number-object@1.0.7: + /is-number-object@1.0.7: + resolution: {integrity: sha512-k1U0IRzLMo7ZlYIfzRu23Oh6MiIFasgpb9X76eqfFZAqwH44UI4KTBvBYIZ1dSL9ZzChTB9ShHfLkR4pdW5krQ==} + engines: {node: '>= 0.4'} dependencies: has-tostringtag: 1.0.2 + dev: false - is-number@7.0.0: {} + /is-number@7.0.0: + resolution: {integrity: sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==} + engines: {node: '>=0.12.0'} + dev: false - is-obj@1.0.1: {} + /is-obj@1.0.1: + resolution: {integrity: sha512-l4RyHgRqGN4Y3+9JHVrNqO+tN0rV5My76uW5/nuO4K1b6vw5G8d/cmFjP9tRfEsdhZNt0IFdZuK/c2Vr4Nb+Qg==} + engines: {node: '>=0.10.0'} + dev: false - is-obj@2.0.0: {} + /is-obj@2.0.0: + resolution: {integrity: sha512-drqDG3cbczxxEJRoOXcOjtdp1J/lyp1mNn0xaznRs8+muBhgQcrnbspox5X5fOw0HnMnbfDzvnEMEtqDEJEo8w==} + engines: {node: '>=8'} + dev: false - is-path-cwd@2.2.0: {} + /is-path-cwd@2.2.0: + resolution: {integrity: sha512-w942bTcih8fdJPJmQHFzkS76NEP8Kzzvmw92cXsazb8intwLqPibPPdXf4ANdKV3rYMuuQYGIWtvz9JilB3NFQ==} + engines: {node: '>=6'} + dev: false - is-path-inside@3.0.3: {} + /is-path-inside@3.0.3: + resolution: {integrity: sha512-Fd4gABb+ycGAmKou8eMftCupSir5lRxqf4aD/vd0cD2qc4HL07OjCeuHMr8Ro4CoMaeCKDB0/ECBOVWjTwUvPQ==} + engines: {node: '>=8'} + dev: false - is-plain-obj@2.1.0: {} + /is-plain-obj@2.1.0: + resolution: {integrity: sha512-YWnfyRwxL/+SsrWYfOpUtz5b3YD+nyfkHvjbcanzk8zgyO4ASD67uVMRt8k5bM4lLMDnXfriRhOpemw+NfT1eA==} + engines: {node: '>=8'} + dev: false - is-plain-obj@3.0.0: {} + /is-plain-obj@3.0.0: + resolution: {integrity: sha512-gwsOE28k+23GP1B6vFl1oVh/WOzmawBrKwo5Ev6wMKzPkaXaCDIQKzLnvsA42DRlbVTWorkgTKIviAKCWkfUwA==} + engines: {node: '>=10'} + dev: false - is-plain-object@2.0.4: + /is-plain-object@2.0.4: + resolution: {integrity: sha512-h5PpgXkWitc38BBMYawTYMWJHFZJVnBquFE57xFpjB8pJFiF6gZ+bU+WyI/yqXiFR5mdLsgYNaPe8uao6Uv9Og==} + engines: {node: '>=0.10.0'} dependencies: isobject: 3.0.1 + dev: false - is-regex@1.1.4: + /is-regex@1.1.4: + resolution: {integrity: sha512-kvRdxDsxZjhzUX07ZnLydzS1TU/TJlTUHHY4YLL87e37oUA49DfkLqgy+VjFocowy29cKvcSiu+kIv728jTTVg==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 has-tostringtag: 1.0.2 + dev: false - is-regexp@1.0.0: {} + /is-regexp@1.0.0: + resolution: {integrity: sha512-7zjFAPO4/gwyQAAgRRmqeEeyIICSdmCqa3tsVHMdBzaXXRiqopZL4Cyghg/XulGWrtABTpbnYYzzIRffLkP4oA==} + engines: {node: '>=0.10.0'} + dev: false - is-root@2.1.0: {} + /is-root@2.1.0: + resolution: {integrity: sha512-AGOriNp96vNBd3HtU+RzFEc75FfR5ymiYv8E553I71SCeXBiMsVDUtdio1OEFvrPyLIQ9tVR5RxXIFe5PUFjMg==} + engines: {node: '>=6'} + dev: false - is-shared-array-buffer@1.0.3: + /is-shared-array-buffer@1.0.3: + resolution: {integrity: sha512-nA2hv5XIhLR3uVzDDfCIknerhx8XUKnstuOERPNNIinXG7v9u+ohXF67vxm4TPTEPU6lm61ZkwP3c9PCB97rhg==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 + dev: false - is-stream@2.0.1: {} + /is-stream@2.0.1: + resolution: {integrity: sha512-hFoiJiTl63nn+kstHGBtewWSKnQLpyb155KHheA1l39uvtO9nWIop1p3udqPcUd/xbF1VLMO4n7OI6p7RbngDg==} + engines: {node: '>=8'} + dev: false - is-string@1.0.7: + /is-string@1.0.7: + resolution: {integrity: sha512-tE2UXzivje6ofPW7l23cjDOMa09gb7xlAqG6jG5ej6uPV32TlWP3NKPigtaGeHNu9fohccRYvIiZMfOOnOYUtg==} + engines: {node: '>= 0.4'} dependencies: has-tostringtag: 1.0.2 + dev: false - is-symbol@1.0.4: + /is-symbol@1.0.4: + resolution: {integrity: sha512-C/CPBqKWnvdcxqIARxyOh4v1UUEOCHpgDa0WYgpKDFMszcrPcffg5uhwSgPCLD2WWxmq6isisz87tzT01tuGhg==} + engines: {node: '>= 0.4'} dependencies: has-symbols: 1.0.3 + dev: false - is-typed-array@1.1.13: + /is-typed-array@1.1.13: + resolution: {integrity: sha512-uZ25/bUAlUY5fR4OKT4rZQEBrzQWYV9ZJYGGsUmEJ6thodVJ1HX64ePQ6Z0qPWP+m+Uq6e9UugrE38jeYsDSMw==} + engines: {node: '>= 0.4'} dependencies: which-typed-array: 1.1.15 + dev: false - is-typedarray@1.0.0: {} + /is-typedarray@1.0.0: + resolution: {integrity: sha512-cyA56iCMHAh5CdzjJIa4aohJyeO1YbwLi3Jc35MmRU6poroFjIGZzUzupGiRPOjgHg9TLu43xbpwXk523fMxKA==} + dev: false - is-weakref@1.0.2: + /is-weakref@1.0.2: + resolution: {integrity: sha512-qctsuLZmIQ0+vSSMfoVvyFe2+GSEvnmZ2ezTup1SBse9+twCCeial6EEi3Nc2KFcf6+qz2FBPnjXsk8xhKSaPQ==} dependencies: call-bind: 1.0.7 + dev: false - is-whitespace-character@1.0.4: {} + /is-whitespace-character@1.0.4: + resolution: {integrity: sha512-SDweEzfIZM0SJV0EUga669UTKlmL0Pq8Lno0QDQsPnvECB3IM2aP0gdx5TrU0A01MAPfViaZiI2V1QMZLaKK5w==} + dev: false - is-word-character@1.0.4: {} + /is-word-character@1.0.4: + resolution: {integrity: sha512-5SMO8RVennx3nZrqtKwCGyyetPE9VDba5ugvKLaD4KopPG5kR4mQ7tNt/r7feL5yt5h3lpuBbIUmCOG2eSzXHA==} + dev: false - is-wsl@2.2.0: + /is-wsl@2.2.0: + resolution: {integrity: sha512-fKzAra0rGJUUBwGBgNkHZuToZcn+TtXHpeCgmkMJMMYx1sQDYaCSyjJBSCa2nH1DGm7s3n1oBnohoVTBaN7Lww==} + engines: {node: '>=8'} dependencies: is-docker: 2.2.1 + dev: false - is-yarn-global@0.3.0: {} + /is-yarn-global@0.3.0: + resolution: {integrity: sha512-VjSeb/lHmkoyd8ryPVIKvOCn4D1koMqY+vqyjjUfc3xyKtP4dYOxM44sZrnqQSzSds3xyOrUTLTC9LVCVgLngw==} + dev: false - isarray@0.0.1: {} + /isarray@0.0.1: + resolution: {integrity: sha512-D2S+3GLxWH+uhrNEcoh/fnmYeP8E8/zHl644d/jdA0g2uyXvy3sb0qxotE+ne0LtccHknQzWwZEzhak7oJ0COQ==} + dev: false - isarray@1.0.0: {} + /isarray@1.0.0: + resolution: {integrity: sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==} + dev: false - isarray@2.0.5: {} + /isarray@2.0.5: + resolution: {integrity: sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==} + dev: false - isexe@2.0.0: {} + /isexe@2.0.0: + resolution: {integrity: sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==} - isobject@3.0.1: {} + /isobject@3.0.1: + resolution: {integrity: sha512-WhB9zCku7EGTj/HQQRz5aUQEUeoQZH2bWcltRErOpymJ4boYE6wL9Tbr23krRPSZ+C5zqNSrSw+Cc7sZZ4b7vg==} + engines: {node: '>=0.10.0'} + dev: false - jackspeak@2.3.6: + /jackspeak@2.3.6: + resolution: {integrity: sha512-N3yCS/NegsOBokc8GAdM8UcmfsKiSS8cipheD/nivzr700H+nsMOxJjQnvwOcRYVuFkdH0wGUvW2WbXGmrZGbQ==} + engines: {node: '>=14'} dependencies: '@isaacs/cliui': 8.0.2 optionalDependencies: '@pkgjs/parseargs': 0.11.0 + dev: true - jest-util@29.7.0: + /jest-util@29.7.0: + resolution: {integrity: sha512-z6EbKajIpqGKU56y5KBUgy1dt1ihhQJgWzUlZHArA/+X2ad7Cb5iF+AK1EWVL/Bo7Rz9uurpqw6SiBCefUbCGA==} + engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} dependencies: '@jest/types': 29.6.3 '@types/node': 22.5.0 @@ -9105,160 +6483,284 @@ snapshots: ci-info: 3.9.0 graceful-fs: 4.2.11 picomatch: 2.3.1 + dev: false - jest-worker@27.5.1: + /jest-worker@27.5.1: + resolution: {integrity: sha512-7vuh85V5cdDofPyxn58nrPjBktZo0u9x1g8WtjQol+jZDaE+fhN+cIvTj11GndBnMnyfrUOG1sZQxCdjKh+DKg==} + engines: {node: '>= 10.13.0'} dependencies: '@types/node': 22.5.0 merge-stream: 2.0.0 supports-color: 8.1.1 + dev: false - jest-worker@29.7.0: + /jest-worker@29.7.0: + resolution: {integrity: sha512-eIz2msL/EzL9UFTFFx7jBTkeZfku0yUAyZZZmJ93H2TYEiroIx2PQjEXcwYtYl8zXCxb+PAmA2hLIt/6ZEkPHw==} + engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0} dependencies: '@types/node': 22.5.0 jest-util: 29.7.0 merge-stream: 2.0.0 supports-color: 8.1.1 + dev: false - jiti@1.21.6: {} + /jiti@1.21.6: + resolution: {integrity: sha512-2yTgeWTWzMWkHu6Jp9NKgePDaYHbntiwvYuuJLbbN9vl7DC9DvXKOB2BC3ZZ92D3cvV/aflH0osDfwpHepQ53w==} + hasBin: true + dev: false - joi@17.13.3: + /joi@17.13.3: + resolution: {integrity: sha512-otDA4ldcIx+ZXsKHWmp0YizCweVRZG96J10b0FevjfuncLO1oX59THoAmHkNubYJ+9gWsYsp5k8v4ib6oDv1fA==} dependencies: '@hapi/hoek': 9.3.0 '@hapi/topo': 5.1.0 '@sideway/address': 4.1.5 '@sideway/formula': 3.0.1 '@sideway/pinpoint': 2.0.0 + dev: false - js-tokens@4.0.0: {} + /js-tokens@4.0.0: + resolution: {integrity: sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==} + dev: false - js-yaml@3.14.1: + /js-yaml@3.14.1: + resolution: {integrity: sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==} + hasBin: true dependencies: argparse: 1.0.10 esprima: 4.0.1 + dev: false - js-yaml@4.1.0: + /js-yaml@4.1.0: + resolution: {integrity: sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==} + hasBin: true dependencies: argparse: 2.0.1 - jsesc@0.5.0: {} + /jsesc@0.5.0: + resolution: {integrity: sha512-uZz5UnB7u4T9LvwmFqXii7pZSouaRPorGs5who1Ip7VO0wxanFvBL7GkM6dTHlgX+jhBApRetaWpnDabOeTcnA==} + hasBin: true + dev: false - jsesc@2.5.2: {} + /jsesc@2.5.2: + resolution: {integrity: sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==} + engines: {node: '>=4'} + hasBin: true + dev: false - json-buffer@3.0.0: {} + /json-buffer@3.0.0: + resolution: {integrity: sha512-CuUqjv0FUZIdXkHPI8MezCnFCdaTAacej1TZYulLoAg1h/PhwkdXFN4V/gzY4g+fMBCOV2xF+rp7t2XD2ns/NQ==} + dev: false - json-parse-even-better-errors@2.3.1: {} + /json-parse-even-better-errors@2.3.1: + resolution: {integrity: sha512-xyFwyhro/JEof6Ghe2iz2NcXoj2sloNsWr/XsERDK/oiPCfaNhl5ONfp+jQdAZRQQ0IJWNzH9zIZF7li91kh2w==} + dev: false - json-schema-traverse@0.4.1: {} + /json-schema-traverse@0.4.1: + resolution: {integrity: sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==} + dev: false - json-schema-traverse@1.0.0: {} + /json-schema-traverse@1.0.0: + resolution: {integrity: sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==} + dev: false - json5@2.2.3: {} + /json5@2.2.3: + resolution: {integrity: sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==} + engines: {node: '>=6'} + hasBin: true + dev: false - jsonc-parser@3.2.1: {} + /jsonc-parser@3.2.1: + resolution: {integrity: sha512-AilxAyFOAcK5wA1+LeaySVBrHsGQvUFCDWXKpZjzaL0PqW+xfBOttn8GNtWKFWqneyMZj41MWF9Kl6iPWLwgOA==} + dev: true - jsonfile@6.1.0: + /jsonfile@6.1.0: + resolution: {integrity: sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==} dependencies: universalify: 2.0.1 optionalDependencies: graceful-fs: 4.2.11 + dev: false - keyv@3.1.0: + /keyv@3.1.0: + resolution: {integrity: sha512-9ykJ/46SN/9KPM/sichzQ7OvXyGDYKGTaDlKMGCAlg2UK8KRy4jb0d8sFc+0Tt0YYnThq8X2RZgCg74RPxgcVA==} dependencies: json-buffer: 3.0.0 + dev: false - kind-of@6.0.3: {} + /kind-of@6.0.3: + resolution: {integrity: sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==} + engines: {node: '>=0.10.0'} + dev: false - kleur@3.0.3: {} + /kleur@3.0.3: + resolution: {integrity: sha512-eTIzlVOSUR+JxdDFepEYcBMtZ9Qqdef+rnzWdRZuMbOywu5tO2w2N7rqjoANZ5k9vywhL6Br1VRjUIgTQx4E8w==} + engines: {node: '>=6'} + dev: false - latest-version@5.1.0: + /latest-version@5.1.0: + resolution: {integrity: sha512-weT+r0kTkRQdCdYCNtkMwWXQTMEswKrFBkm4ckQOMVhhqhIMI1UT2hMj+1iigIhgSZm5gTmrRXBNoGUgaTY1xA==} + engines: {node: '>=8'} dependencies: package-json: 6.5.0 + dev: false - launch-editor@2.8.1: + /launch-editor@2.8.1: + resolution: {integrity: sha512-elBx2l/tp9z99X5H/qev8uyDywVh0VXAwEbjk8kJhnc5grOFkGh7aW6q55me9xnYbss261XtnUrysZ+XvGbhQA==} dependencies: picocolors: 1.0.1 shell-quote: 1.8.1 + dev: false - leven@3.1.0: {} + /leven@3.1.0: + resolution: {integrity: sha512-qsda+H8jTaUaN/x5vzW2rzc+8Rw4TAQ/4KjB46IwK5VH+IlVeeeje/EoZRpiXvIqjFgK84QffqPztGI3VBLG1A==} + engines: {node: '>=6'} + dev: false - lilconfig@2.1.0: {} + /lilconfig@2.1.0: + resolution: {integrity: sha512-utWOt/GHzuUxnLKxB6dk81RoOeoNeHgbrXiuGk4yyF5qlRz+iIVWu56E2fqGHFrXz0QNUhLB/8nKqvRH66JKGQ==} + engines: {node: '>=10'} + dev: false - lines-and-columns@1.2.4: {} + /lines-and-columns@1.2.4: + resolution: {integrity: sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==} + dev: false - linkify-it@4.0.1: + /linkify-it@4.0.1: + resolution: {integrity: sha512-C7bfi1UZmoj8+PQx22XyeXCuBlokoyWQL5pWSP+EI6nzRylyThouddufc2c1NDIcP9k5agmN9fLpA7VNJfIiqw==} dependencies: uc.micro: 1.0.6 + dev: true - loader-runner@4.3.0: {} + /loader-runner@4.3.0: + resolution: {integrity: sha512-3R/1M+yS3j5ou80Me59j7F9IMs4PXs3VqRrm0TU3AbKPxlmpoY1TNscJV/oGJXo8qCatFGTfDbY6W6ipGOYXfg==} + engines: {node: '>=6.11.5'} + dev: false - loader-utils@2.0.4: + /loader-utils@2.0.4: + resolution: {integrity: sha512-xXqpXoINfFhgua9xiqD8fPFHgkoq1mmmpE92WlDbm9rNRd/EbRb+Gqf908T2DMfuHjjJlksiK2RbHVOdD/MqSw==} + engines: {node: '>=8.9.0'} dependencies: big.js: 5.2.2 emojis-list: 3.0.0 json5: 2.2.3 + dev: false - loader-utils@3.3.1: {} + /loader-utils@3.3.1: + resolution: {integrity: sha512-FMJTLMXfCLMLfJxcX9PFqX5qD88Z5MRGaZCVzfuqeZSPsyiBzs+pahDQjbIWz2QIzPZz0NX9Zy4FX3lmK6YHIg==} + engines: {node: '>= 12.13.0'} + dev: false - locate-path@3.0.0: + /locate-path@3.0.0: + resolution: {integrity: sha512-7AO748wWnIhNqAuaty2ZWHkQHRSNfPVIsPIfwEOWO22AmaoVrWavlOcMR5nzTLNYvp36X220/maaRsrec1G65A==} + engines: {node: '>=6'} dependencies: p-locate: 3.0.0 path-exists: 3.0.0 + dev: false - locate-path@5.0.0: + /locate-path@5.0.0: + resolution: {integrity: sha512-t7hw9pI+WvuwNJXwk5zVHpyhIqzg2qTlklJOf0mVxGSbe3Fp2VieZcduNYjaLDoy6p9uGpQEGWG87WpMKlNq8g==} + engines: {node: '>=8'} dependencies: p-locate: 4.1.0 + dev: false - locate-path@6.0.0: + /locate-path@6.0.0: + resolution: {integrity: sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==} + engines: {node: '>=10'} dependencies: p-locate: 5.0.0 + dev: false - lodash.curry@4.1.1: {} + /lodash.curry@4.1.1: + resolution: {integrity: sha512-/u14pXGviLaweY5JI0IUzgzF2J6Ne8INyzAZjImcryjgkZ+ebruBxy2/JaOOkTqScddcYtakjhSaeemV8lR0tA==} + dev: false - lodash.debounce@4.0.8: {} + /lodash.debounce@4.0.8: + resolution: {integrity: sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow==} + dev: false - lodash.flow@3.5.0: {} + /lodash.flow@3.5.0: + resolution: {integrity: sha512-ff3BX/tSioo+XojX4MOsOMhJw0nZoUEF011LX8g8d3gvjVbxd89cCio4BCXronjxcTUIJUoqKEUA+n4CqvvRPw==} + dev: false - lodash.memoize@4.1.2: {} + /lodash.memoize@4.1.2: + resolution: {integrity: sha512-t7j+NzmgnQzTAYXcsHYLgimltOV1MXHtlOWf6GjL9Kj8GK5FInw5JotxvbOs+IvV1/Dzo04/fCGfLVs7aXb4Ag==} + dev: false - lodash.uniq@4.5.0: {} + /lodash.uniq@4.5.0: + resolution: {integrity: sha512-xfBaXQd9ryd9dlSDvnvI0lvxfLJlYAZzXomUYzLKtUeOQvOP5piqAWuGtrhWeqaXK9hhoM/iyJc5AV+XfsX3HQ==} + dev: false - lodash@4.17.21: {} + /lodash@4.17.21: + resolution: {integrity: sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==} + dev: false - loglevel@1.9.1: {} + /loglevel@1.9.1: + resolution: {integrity: sha512-hP3I3kCrDIMuRwAwHltphhDM1r8i55H33GgqjXbrisuJhF4kRhW1dNuxsRklp4bXl8DSdLaNLuiL4A/LWRfxvg==} + engines: {node: '>= 0.6.0'} + dev: false - loose-envify@1.4.0: + /loose-envify@1.4.0: + resolution: {integrity: sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==} + hasBin: true dependencies: js-tokens: 4.0.0 + dev: false - lower-case@2.0.2: + /lower-case@2.0.2: + resolution: {integrity: sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==} dependencies: tslib: 2.7.0 + dev: false - lowercase-keys@1.0.1: {} + /lowercase-keys@1.0.1: + resolution: {integrity: sha512-G2Lj61tXDnVFFOi8VZds+SoQjtQC3dgokKdDG2mTm1tx4m50NUHBOZSBwQQHyy0V12A0JTG4icfZQH+xPyh8VA==} + engines: {node: '>=0.10.0'} + dev: false - lowercase-keys@2.0.0: {} + /lowercase-keys@2.0.0: + resolution: {integrity: sha512-tqNXrS78oMOE73NMxK4EMLQsQowWf8jKooH9g7xPavRT706R6bkQJ6DY2Te7QukaZsulxa30wQ7bk0pm4XiHmA==} + engines: {node: '>=8'} + dev: false - lru-cache@10.4.3: {} + /lru-cache@10.4.3: + resolution: {integrity: sha512-JNAzZcXrCt42VGLuYz0zfAzDfAvJWW6AfYlDBQyDV5DClI2m5sAmK+OIO7s59XfsRsWHp02jAJrRadPRGTt6SQ==} + dev: true - lru-cache@5.1.1: + /lru-cache@5.1.1: + resolution: {integrity: sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==} dependencies: yallist: 3.1.1 + dev: false - make-dir@3.1.0: + /make-dir@3.1.0: + resolution: {integrity: sha512-g3FeP20LNwhALb/6Cz6Dd4F2ngze0jz7tbzrD2wAV+o9FeNHe4rL+yK2md0J/fiSf1sa1ADhXqi5+oVwOM/eGw==} + engines: {node: '>=8'} dependencies: semver: 6.3.1 + dev: false - markdown-escapes@1.0.4: {} + /markdown-escapes@1.0.4: + resolution: {integrity: sha512-8z4efJYk43E0upd0NbVXwgSTQs6cT3T06etieCMEg7dRbzCbxUCK/GHlX8mhHRDcp+OLlHkPKsvqQTCvsRl2cg==} + dev: false - markdown-it@13.0.1: + /markdown-it@13.0.1: + resolution: {integrity: sha512-lTlxriVoy2criHP0JKRhO2VDG9c2ypWCsT237eDiLqi09rmbKoUetyGHq2uOIRoRS//kfoJckS0eUzzkDR+k2Q==} + hasBin: true dependencies: argparse: 2.0.1 entities: 3.0.1 linkify-it: 4.0.1 mdurl: 1.0.1 uc.micro: 1.0.6 + dev: true - markdownlint-cli@0.35.0: + /markdownlint-cli@0.35.0: + resolution: {integrity: sha512-lVIIIV1MrUtjoocgDqXLxUCxlRbn7Ve8rsWppfwciUNwLlNS28AhNiyQ3PU7jjj4Qvj+rWTTvwkqg7AcdG988g==} + engines: {node: '>=16'} + hasBin: true dependencies: commander: 11.0.0 get-stdin: 9.0.0 @@ -9269,23 +6771,35 @@ snapshots: markdownlint: 0.29.0 minimatch: 9.0.5 run-con: 1.2.12 + dev: true - markdownlint-micromark@0.1.5: {} + /markdownlint-micromark@0.1.5: + resolution: {integrity: sha512-HvofNU4QCvfUCWnocQP1IAWaqop5wpWrB0mKB6SSh0fcpV0PdmQNS6tdUuFew1utpYlUvYYzz84oDkrD76GB9A==} + engines: {node: '>=16'} + dev: true - markdownlint@0.29.0: + /markdownlint@0.29.0: + resolution: {integrity: sha512-ASAzqpODstu/Qsk0xW5BPgWnK/qjpBQ4e7IpsSvvFXcfYIjanLTdwFRJK1SIEEh0fGSMKXcJf/qhaZYHyME0wA==} + engines: {node: '>=16'} dependencies: markdown-it: 13.0.1 markdownlint-micromark: 0.1.5 + dev: true - mdast-squeeze-paragraphs@4.0.0: + /mdast-squeeze-paragraphs@4.0.0: + resolution: {integrity: sha512-zxdPn69hkQ1rm4J+2Cs2j6wDEv7O17TfXTJ33tl/+JPIoEmtV9t2ZzBM5LPHE8QlHsmVD8t3vPKCyY3oH+H8MQ==} dependencies: unist-util-remove: 2.1.0 + dev: false - mdast-util-definitions@4.0.0: + /mdast-util-definitions@4.0.0: + resolution: {integrity: sha512-k8AJ6aNnUkB7IE+5azR9h81O5EQ/cTDXtWdMq9Kk5KcEW/8ritU5CeLg/9HhOC++nALHBlaogJ5jz0Ybk3kPMQ==} dependencies: unist-util-visit: 2.0.3 + dev: false - mdast-util-to-hast@10.0.1: + /mdast-util-to-hast@10.0.1: + resolution: {integrity: sha512-BW3LM9SEMnjf4HXXVApZMt8gLQWVNXc3jryK0nJu/rOXPOnlkUjmdkDlmxMirpbU9ILncGFIwLH/ubnWBbcdgA==} dependencies: '@types/mdast': 3.0.15 '@types/unist': 2.0.11 @@ -9295,163 +6809,319 @@ snapshots: unist-util-generated: 1.1.6 unist-util-position: 3.1.0 unist-util-visit: 2.0.3 + dev: false - mdast-util-to-string@2.0.0: {} + /mdast-util-to-string@2.0.0: + resolution: {integrity: sha512-AW4DRS3QbBayY/jJmD8437V1Gombjf8RSOUCMFBuo5iHi58AGEgVCKQ+ezHkZZDpAQS75hcBMpLqjpJTjtUL7w==} + dev: false - mdn-data@2.0.14: {} + /mdn-data@2.0.14: + resolution: {integrity: sha512-dn6wd0uw5GsdswPFfsgMp5NSB0/aDe6fK94YJV/AJDYXL6HVLWBsxeq7js7Ad+mU2K9LAlwpk6kN2D5mwCPVow==} + dev: false - mdn-data@2.0.4: {} + /mdn-data@2.0.4: + resolution: {integrity: sha512-iV3XNKw06j5Q7mi6h+9vbx23Tv7JkjEVgKHW4pimwyDGWm0OIQntJJ+u1C6mg6mK1EaTv42XQ7w76yuzH7M2cA==} + dev: false - mdurl@1.0.1: {} + /mdurl@1.0.1: + resolution: {integrity: sha512-/sKlQJCBYVY9Ers9hqzKou4H6V5UWc/M59TH2dvkt+84itfnq7uFOMLpOiOS4ujvHP4etln18fmIxA5R5fll0g==} - media-typer@0.3.0: {} + /media-typer@0.3.0: + resolution: {integrity: sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ==} + engines: {node: '>= 0.6'} + dev: false - memfs@3.5.3: + /memfs@3.5.3: + resolution: {integrity: sha512-UERzLsxzllchadvbPs5aolHh65ISpKpM+ccLbOJ8/vvpBKmAWf+la7dXFy7Mr0ySHbdHrFv5kGFCUHHe6GFEmw==} + engines: {node: '>= 4.0.0'} dependencies: fs-monkey: 1.0.6 + dev: false - merge-descriptors@1.0.1: {} + /merge-descriptors@1.0.1: + resolution: {integrity: sha512-cCi6g3/Zr1iqQi6ySbseM1Xvooa98N0w31jzUYrXPX2xqObmFGHJ0tQ5u74H3mVh7wLouTseZyYIq39g8cNp1w==} + dev: false - merge-stream@2.0.0: {} + /merge-stream@2.0.0: + resolution: {integrity: sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==} + dev: false - merge2@1.4.1: {} + /merge2@1.4.1: + resolution: {integrity: sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==} + engines: {node: '>= 8'} + dev: false - methods@1.1.2: {} + /methods@1.1.2: + resolution: {integrity: sha512-iclAHeNqNm68zFtnZ0e+1L2yUIdvzNoauKU4WBA3VvH/vPFieF7qfRlwUZU+DA9P9bPXIS90ulxoUoCH23sV2w==} + engines: {node: '>= 0.6'} + dev: false - micromatch@4.0.8: + /micromatch@4.0.8: + resolution: {integrity: sha512-PXwfBhYu0hBCPw8Dn0E+WDYb7af3dSLVWKi3HGv84IdF4TyFoC0ysxFd0Goxw7nSv4T/PzEJQxsYsEiFCKo2BA==} + engines: {node: '>=8.6'} dependencies: braces: 3.0.3 picomatch: 2.3.1 + dev: false - mime-db@1.33.0: {} + /mime-db@1.33.0: + resolution: {integrity: sha512-BHJ/EKruNIqJf/QahvxwQZXKygOQ256myeN/Ew+THcAa5q+PjyTTMMeNQC4DZw5AwfvelsUrA6B67NKMqXDbzQ==} + engines: {node: '>= 0.6'} + dev: false - mime-db@1.52.0: {} + /mime-db@1.52.0: + resolution: {integrity: sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==} + engines: {node: '>= 0.6'} + dev: false - mime-db@1.53.0: {} + /mime-db@1.53.0: + resolution: {integrity: sha512-oHlN/w+3MQ3rba9rqFr6V/ypF10LSkdwUysQL7GkXoTgIWeV+tcXGA852TBxH+gsh8UWoyhR1hKcoMJTuWflpg==} + engines: {node: '>= 0.6'} + dev: false - mime-types@2.1.18: + /mime-types@2.1.18: + resolution: {integrity: sha512-lc/aahn+t4/SWV/qcmumYjymLsWfN3ELhpmVuUFjgsORruuZPVSwAQryq+HHGvO/SI2KVX26bx+En+zhM8g8hQ==} + engines: {node: '>= 0.6'} dependencies: mime-db: 1.33.0 + dev: false - mime-types@2.1.35: + /mime-types@2.1.35: + resolution: {integrity: sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==} + engines: {node: '>= 0.6'} dependencies: mime-db: 1.52.0 + dev: false - mime@1.6.0: {} + /mime@1.6.0: + resolution: {integrity: sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==} + engines: {node: '>=4'} + hasBin: true + dev: false - mimic-fn@2.1.0: {} + /mimic-fn@2.1.0: + resolution: {integrity: sha512-OqbOk5oEQeAZ8WXWydlu9HJjz9WVdEIvamMCcXmuqUYjTknH/sqsWvhQ3vgwKFRR1HpjvNBKQ37nbJgYzGqGcg==} + engines: {node: '>=6'} + dev: false - mimic-response@1.0.1: {} + /mimic-response@1.0.1: + resolution: {integrity: sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ==} + engines: {node: '>=4'} + dev: false - mini-css-extract-plugin@2.9.1(webpack@5.94.0): + /mini-css-extract-plugin@2.9.1(webpack@5.94.0): + resolution: {integrity: sha512-+Vyi+GCCOHnrJ2VPS+6aPoXN2k2jgUzDRhTFLjjTBn23qyXJXkjUWQgTL+mXpF5/A8ixLdCc6kWsoeOjKGejKQ==} + engines: {node: '>= 12.13.0'} + peerDependencies: + webpack: ^5.0.0 dependencies: schema-utils: 4.2.0 tapable: 2.2.1 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - minimalistic-assert@1.0.1: {} + /minimalistic-assert@1.0.1: + resolution: {integrity: sha512-UtJcAD4yEaGtjPezWuO9wC4nwUnVH/8/Im3yEHQP4b67cXlD/Qr9hdITCU1xDbSEXg2XKNaP8jsReV7vQd00/A==} + dev: false - minimatch@3.1.2: + /minimatch@3.1.2: + resolution: {integrity: sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==} dependencies: brace-expansion: 1.1.11 + dev: false - minimatch@9.0.5: + /minimatch@9.0.5: + resolution: {integrity: sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==} + engines: {node: '>=16 || 14 >=14.17'} dependencies: brace-expansion: 2.0.1 + dev: true - minimist@1.2.8: {} + /minimist@1.2.8: + resolution: {integrity: sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==} - minipass@2.9.0: + /minipass@2.9.0: + resolution: {integrity: sha512-wxfUjg9WebH+CUDX/CdbRlh5SmfZiy/hpkxaRI16Y9W56Pa75sWgd/rvFilSgrauD9NyFymP/+JFV3KwzIsJeg==} dependencies: safe-buffer: 5.2.1 yallist: 3.1.1 + dev: false - minipass@6.0.2: {} + /minipass@6.0.2: + resolution: {integrity: sha512-MzWSV5nYVT7mVyWCwn2o7JH13w2TBRmmSqSRCKzTw+lmft9X4z+3wjvs06Tzijo5z4W/kahUCDpRXTF+ZrmF/w==} + engines: {node: '>=16 || 14 >=14.17'} + dev: true - minizlib@1.3.3: + /minizlib@1.3.3: + resolution: {integrity: sha512-6ZYMOEnmVsdCeTJVE0W9ZD+pVnE8h9Hma/iOwwRDsdQoePpoX56/8B6z3P9VNwppJuBKNRuFDRNRqRWexT9G9Q==} dependencies: minipass: 2.9.0 + dev: false - mkdirp@0.5.6: + /mkdirp@0.5.6: + resolution: {integrity: sha512-FP+p8RB8OWpF3YZBCrP5gtADmtXApB5AMLn+vdyA+PyxCjrCs00mjyUozssO33cwDeT3wNGdLxJ5M//YqtHAJw==} + hasBin: true dependencies: minimist: 1.2.8 + dev: false - mrmime@2.0.0: {} + /mrmime@2.0.0: + resolution: {integrity: sha512-eu38+hdgojoyq63s+yTpN4XMBdt5l8HhMhc4VKLO9KM5caLIBvUm4thi7fFaxyTmCKeNnXZ5pAlBwCUnhA09uw==} + engines: {node: '>=10'} + dev: false - ms@2.0.0: {} + /ms@2.0.0: + resolution: {integrity: sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==} + dev: false - ms@2.1.2: {} + /ms@2.1.2: + resolution: {integrity: sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==} + dev: false - ms@2.1.3: {} + /ms@2.1.3: + resolution: {integrity: sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==} + dev: false - multicast-dns@7.2.5: + /multicast-dns@7.2.5: + resolution: {integrity: sha512-2eznPJP8z2BFLX50tf0LuODrpINqP1RVIm/CObbTcBRITQgmC/TjcREF1NeTBzIcR5XO/ukWo+YHOjBbFwIupg==} + hasBin: true dependencies: dns-packet: 5.6.1 thunky: 1.1.0 + dev: false - nanoid@3.3.7: {} + /nanoid@3.3.7: + resolution: {integrity: sha512-eSRppjcPIatRIMC1U6UngP8XFcz8MQWGQdt1MTBQ7NaAmvXDfvNxbvWV3x2y6CdEUciCSsDHDQZbhYaB8QEo2g==} + engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1} + hasBin: true + dev: false - negotiator@0.6.3: {} + /negotiator@0.6.3: + resolution: {integrity: sha512-+EUsqGPLsM+j/zdChZjsnX51g4XrHFOIXwfnCVPGlQk/k5giakcKsuxCObBRu6DSm9opw/O6slWbJdghQM4bBg==} + engines: {node: '>= 0.6'} + dev: false - neo-async@2.6.2: {} + /neo-async@2.6.2: + resolution: {integrity: sha512-Yd3UES5mWCSqR+qNT93S3UoYUkqAZ9lLg8a7g9rimsWmYGK8cVToA4/sF3RrshdyV3sAGMXVUmpMYOw+dLpOuw==} + dev: false - no-case@3.0.4: + /no-case@3.0.4: + resolution: {integrity: sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==} dependencies: lower-case: 2.0.2 tslib: 2.7.0 + dev: false - node-emoji@1.11.0: + /node-emoji@1.11.0: + resolution: {integrity: sha512-wo2DpQkQp7Sjm2A0cq+sN7EHKO6Sl0ctXeBdFZrL9T9+UywORbufTcTZxom8YqpLQt/FqNMUkOpkZrJVYSKD3A==} dependencies: lodash: 4.17.21 + dev: false - node-fetch@2.6.7: + /node-fetch@2.6.7: + resolution: {integrity: sha512-ZjMPFEfVx5j+y2yF35Kzx5sF7kDzxuDj6ziH4FFbOp87zKDZNx8yExJIb05OGF4Nlt9IHFIMBkRl41VdvcNdbQ==} + engines: {node: 4.x || >=6.0.0} + peerDependencies: + encoding: ^0.1.0 + peerDependenciesMeta: + encoding: + optional: true dependencies: whatwg-url: 5.0.0 + dev: false - node-fetch@2.7.0: + /node-fetch@2.7.0: + resolution: {integrity: sha512-c4FRfUm/dbcWZ7U+1Wq0AwCyFL+3nt2bEw05wfxSz+DWpWsitgmSgYmy2dQdWyKC1694ELPqMs/YzUSNozLt8A==} + engines: {node: 4.x || >=6.0.0} + peerDependencies: + encoding: ^0.1.0 + peerDependenciesMeta: + encoding: + optional: true dependencies: whatwg-url: 5.0.0 + dev: false - node-forge@1.3.1: {} + /node-forge@1.3.1: + resolution: {integrity: sha512-dPEtOeMvF9VMcYV/1Wb8CPoVAXtp6MKMlcbAt4ddqmGqUJ6fQZFXkNZNkNlfevtNkGtaSoXf/vNNNSvgrdXwtA==} + engines: {node: '>= 6.13.0'} + dev: false - node-releases@2.0.18: {} + /node-releases@2.0.18: + resolution: {integrity: sha512-d9VeXT4SJ7ZeOqGX6R5EM022wpL+eWPooLI+5UpWn2jCT1aosUQEhQP214x33Wkwx3JQMvIm+tIoVOdodFS40g==} + dev: false - normalize-path@3.0.0: {} + /normalize-path@3.0.0: + resolution: {integrity: sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==} + engines: {node: '>=0.10.0'} + dev: false - normalize-range@0.1.2: {} + /normalize-range@0.1.2: + resolution: {integrity: sha512-bdok/XvKII3nUpklnV6P2hxtMNrCboOjAcyBuQnWEhO665FwrSNRxU+AqpsyvO6LgGYPspN+lu5CLtw4jPRKNA==} + engines: {node: '>=0.10.0'} + dev: false - normalize-url@4.5.1: {} + /normalize-url@4.5.1: + resolution: {integrity: sha512-9UZCFRHQdNrfTpGg8+1INIg93B6zE0aXMVFkw1WFwvO4SlZywU6aLg5Of0Ap/PgcbSw4LNxvMWXMeugwMCX0AA==} + engines: {node: '>=8'} + dev: false - normalize-url@6.1.0: {} + /normalize-url@6.1.0: + resolution: {integrity: sha512-DlL+XwOy3NxAQ8xuC0okPgK46iuVNAK01YN7RueYBqqFeGsBjV9XmCAzAdgt+667bCl5kPh9EqKKDwnaPG1I7A==} + engines: {node: '>=10'} + dev: false - npm-run-path@4.0.1: + /npm-run-path@4.0.1: + resolution: {integrity: sha512-S48WzZW777zhNIrn7gxOlISNAqi9ZC/uQFnRdbeIHhZhCA6UqpkOT8T1G7BvfdgP4Er8gF4sUbaS0i7QvIfCWw==} + engines: {node: '>=8'} dependencies: path-key: 3.1.1 + dev: false - nprogress@0.2.0: {} + /nprogress@0.2.0: + resolution: {integrity: sha512-I19aIingLgR1fmhftnbWWO3dXc0hSxqHQHQb3H8m+K3TnEn/iSeTZZOyvKXWqQESMwuUVnatlCnZdLBZZt2VSA==} + dev: false - nth-check@1.0.2: + /nth-check@1.0.2: + resolution: {integrity: sha512-WeBOdju8SnzPN5vTUJYxYUxLeXpCaVP5i5e0LF8fg7WORF2Wd7wFX/pk0tYZk7s8T+J7VLy0Da6J1+wCT0AtHg==} dependencies: boolbase: 1.0.0 + dev: false - nth-check@2.1.1: + /nth-check@2.1.1: + resolution: {integrity: sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==} dependencies: boolbase: 1.0.0 + dev: false - object-assign@4.1.1: {} + /object-assign@4.1.1: + resolution: {integrity: sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==} + engines: {node: '>=0.10.0'} + dev: false - object-inspect@1.13.2: {} + /object-inspect@1.13.2: + resolution: {integrity: sha512-IRZSRuzJiynemAXPYtPe5BoI/RESNYR7TYm50MC5Mqbd3Jmw5y790sErYw3V6SryFJD64b74qQQs9wn5Bg/k3g==} + engines: {node: '>= 0.4'} + dev: false - object-keys@1.1.1: {} + /object-keys@1.1.1: + resolution: {integrity: sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==} + engines: {node: '>= 0.4'} + dev: false - object.assign@4.1.5: + /object.assign@4.1.5: + resolution: {integrity: sha512-byy+U7gp+FVwmyzKPYhW2h5l3crpmGsxl7X2s8y43IgxvG4g3QZ6CffDtsNQy1WsmZpQbO+ybo0AlW7TY6DcBQ==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 define-properties: 1.2.1 has-symbols: 1.0.3 object-keys: 1.1.1 + dev: false - object.getownpropertydescriptors@2.1.8: + /object.getownpropertydescriptors@2.1.8: + resolution: {integrity: sha512-qkHIGe4q0lSYMv0XI4SsBTJz3WaURhLvd0lKSgtVuOsJ2krg4SgMw3PIRQFMp07yi++UR3se2mkcLqsBNpBb/A==} + engines: {node: '>= 0.8'} dependencies: array.prototype.reduce: 1.0.7 call-bind: 1.0.7 @@ -9460,87 +7130,146 @@ snapshots: es-object-atoms: 1.0.0 gopd: 1.0.1 safe-array-concat: 1.1.2 + dev: false - object.values@1.2.0: + /object.values@1.2.0: + resolution: {integrity: sha512-yBYjY9QX2hnRmZHAjG/f13MzmBzxzYgQhFrke06TTyKY5zSTEqkOeukBzIdVA3j3ulu8Qa3MbVFShV7T2RmGtQ==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 define-properties: 1.2.1 es-object-atoms: 1.0.0 + dev: false - obuf@1.1.2: {} + /obuf@1.1.2: + resolution: {integrity: sha512-PX1wu0AmAdPqOL1mWhqmlOd8kOIZQwGZw6rh7uby9fTc5lhaOWFLX3I6R1hrF9k3zUY40e6igsLGkDXK92LJNg==} + dev: false - on-finished@2.4.1: + /on-finished@2.4.1: + resolution: {integrity: sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg==} + engines: {node: '>= 0.8'} dependencies: ee-first: 1.1.1 + dev: false - on-headers@1.0.2: {} + /on-headers@1.0.2: + resolution: {integrity: sha512-pZAE+FJLoyITytdqK0U5s+FIpjN0JP3OzFi/u8Rx+EV5/W+JTWGXG8xFzevE7AjBfDqHv/8vL8qQsIhHnqRkrA==} + engines: {node: '>= 0.8'} + dev: false - once@1.4.0: + /once@1.4.0: + resolution: {integrity: sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==} dependencies: wrappy: 1.0.2 + dev: false - onetime@5.1.2: + /onetime@5.1.2: + resolution: {integrity: sha512-kbpaSSGJTWdAY5KPVeMOKXSrPtr8C8C7wodJbcsd51jRnmD+GZu8Y0VoU6Dm5Z4vWr0Ig/1NKuWRKf7j5aaYSg==} + engines: {node: '>=6'} dependencies: mimic-fn: 2.1.0 + dev: false - open@8.4.2: + /open@8.4.2: + resolution: {integrity: sha512-7x81NCL719oNbsq/3mh+hVrAWmFuEYUqrq/Iw3kUzH8ReypT9QQ0BLoJS7/G9k6N81XjW4qHWtjWwe/9eLy1EQ==} + engines: {node: '>=12'} dependencies: define-lazy-prop: 2.0.0 is-docker: 2.2.1 is-wsl: 2.2.0 + dev: false - opener@1.5.2: {} + /opener@1.5.2: + resolution: {integrity: sha512-ur5UIdyw5Y7yEj9wLzhqXiy6GZ3Mwx0yGI+5sMn2r0N0v3cKJvUmFH5yPP+WXh9e0xfyzyJX95D8l088DNFj7A==} + hasBin: true + dev: false - p-cancelable@1.1.0: {} + /p-cancelable@1.1.0: + resolution: {integrity: sha512-s73XxOZ4zpt1edZYZzvhqFa6uvQc1vwUa0K0BdtIZgQMAJj9IbebH+JkgKZc9h+B05PKHLOTl4ajG1BmNrVZlw==} + engines: {node: '>=6'} + dev: false - p-limit@2.3.0: + /p-limit@2.3.0: + resolution: {integrity: sha512-//88mFWSJx8lxCzwdAABTJL2MyWB12+eIY7MDL2SqLmAkeKU9qxRvWuSyTjm3FUmpBEMuFfckAIqEaVGUDxb6w==} + engines: {node: '>=6'} dependencies: p-try: 2.2.0 + dev: false - p-limit@3.1.0: + /p-limit@3.1.0: + resolution: {integrity: sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==} + engines: {node: '>=10'} dependencies: yocto-queue: 0.1.0 + dev: false - p-locate@3.0.0: + /p-locate@3.0.0: + resolution: {integrity: sha512-x+12w/To+4GFfgJhBEpiDcLozRJGegY+Ei7/z0tSLkMmxGZNybVMSfWj9aJn8Z5Fc7dBUNJOOVgPv2H7IwulSQ==} + engines: {node: '>=6'} dependencies: p-limit: 2.3.0 + dev: false - p-locate@4.1.0: + /p-locate@4.1.0: + resolution: {integrity: sha512-R79ZZ/0wAxKGu3oYMlz8jy/kbhsNrS7SKZ7PxEHBgJ5+F2mtFW2fK2cOtBh1cHYkQsbzFV7I+EoRKe6Yt0oK7A==} + engines: {node: '>=8'} dependencies: p-limit: 2.3.0 + dev: false - p-locate@5.0.0: + /p-locate@5.0.0: + resolution: {integrity: sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==} + engines: {node: '>=10'} dependencies: p-limit: 3.1.0 + dev: false - p-map@4.0.0: + /p-map@4.0.0: + resolution: {integrity: sha512-/bjOqmgETBYB5BoEeGVea8dmvHb2m9GLy1E9W43yeyfP6QQCZGFNa+XRceJEuDB6zqr+gKpIAmlLebMpykw/MQ==} + engines: {node: '>=10'} dependencies: aggregate-error: 3.1.0 + dev: false - p-retry@4.6.2: + /p-retry@4.6.2: + resolution: {integrity: sha512-312Id396EbJdvRONlngUx0NydfrIQ5lsYu0znKVUzVvArzEIt08V1qhtyESbGVd1FGX7UKtiFp5uwKZdM8wIuQ==} + engines: {node: '>=8'} dependencies: '@types/retry': 0.12.0 retry: 0.13.1 + dev: false - p-try@2.2.0: {} + /p-try@2.2.0: + resolution: {integrity: sha512-R4nPAVTAU0B9D35/Gk3uJf/7XYbQcyohSKdvAxIRSNghFl4e71hVoGnBNQz9cWaXxO2I10KTC+3jMdvvoKw6dQ==} + engines: {node: '>=6'} + dev: false - package-json@6.5.0: + /package-json@6.5.0: + resolution: {integrity: sha512-k3bdm2n25tkyxcjSKzB5x8kfVxlMdgsbPr0GkZcwHsLpba6cBjqCt1KlcChKEvxHIcTB1FVMuwoijZ26xex5MQ==} + engines: {node: '>=8'} dependencies: got: 9.6.0 registry-auth-token: 4.2.2 registry-url: 5.1.0 semver: 6.3.1 + dev: false - param-case@3.0.4: + /param-case@3.0.4: + resolution: {integrity: sha512-RXlj7zCYokReqWpOPH9oYivUzLYZ5vAPIfEmCTNViosC78F8F0H9y7T7gG2M39ymgutxF5gcFEsyZQSph9Bp3A==} dependencies: dot-case: 3.0.4 tslib: 2.7.0 + dev: false - parent-module@1.0.1: + /parent-module@1.0.1: + resolution: {integrity: sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==} + engines: {node: '>=6'} dependencies: callsites: 3.1.0 + dev: false - parse-entities@2.0.0: + /parse-entities@2.0.0: + resolution: {integrity: sha512-kkywGpCcRYhqQIchaWqZ875wzpS/bMKhz5HnN3p7wveJTkTtyAB/AlnS0f8DFSqYW1T82t6yEAkEcB+A1I3MbQ==} dependencies: character-entities: 1.2.4 character-entities-legacy: 1.1.4 @@ -9548,123 +7277,229 @@ snapshots: is-alphanumerical: 1.0.4 is-decimal: 1.0.4 is-hexadecimal: 1.0.4 + dev: false - parse-json@5.2.0: + /parse-json@5.2.0: + resolution: {integrity: sha512-ayCKvm/phCGxOkYRSCM82iDwct8/EonSEgCSxWxD7ve6jHggsFl4fZVQBPRNgQoKiuV/odhFrGzQXZwbifC8Rg==} + engines: {node: '>=8'} dependencies: '@babel/code-frame': 7.24.7 error-ex: 1.3.2 json-parse-even-better-errors: 2.3.1 lines-and-columns: 1.2.4 + dev: false - parse-numeric-range@1.3.0: {} + /parse-numeric-range@1.3.0: + resolution: {integrity: sha512-twN+njEipszzlMJd4ONUYgSfZPDxgHhT9Ahed5uTigpQn90FggW4SA/AIPq/6a149fTbE9qBEcSwE3FAEp6wQQ==} + dev: false - parse5-htmlparser2-tree-adapter@7.0.0: + /parse5-htmlparser2-tree-adapter@7.0.0: + resolution: {integrity: sha512-B77tOZrqqfUfnVcOrUvfdLbz4pu4RopLD/4vmu3HUPswwTA8OH0EMW9BlWR2B0RCoiZRAHEUu7IxeP1Pd1UU+g==} dependencies: domhandler: 5.0.3 parse5: 7.1.2 + dev: false - parse5-parser-stream@7.1.2: + /parse5-parser-stream@7.1.2: + resolution: {integrity: sha512-JyeQc9iwFLn5TbvvqACIF/VXG6abODeB3Fwmv/TGdLk2LfbWkaySGY72at4+Ty7EkPZj854u4CrICqNk2qIbow==} dependencies: parse5: 7.1.2 + dev: false - parse5@6.0.1: {} + /parse5@6.0.1: + resolution: {integrity: sha512-Ofn/CTFzRGTTxwpNEs9PP93gXShHcTq255nzRYSKe8AkVpZY7e1fpmTfOyoIvjP5HG7Z2ZM7VS9PPhQGW2pOpw==} + dev: false - parse5@7.1.2: + /parse5@7.1.2: + resolution: {integrity: sha512-Czj1WaSVpaoj0wbhMzLmWD69anp2WH7FXMB9n1Sy8/ZFF9jolSQVMu1Ij5WIyGmcBmhk7EOndpO4mIpihVqAXw==} dependencies: entities: 4.5.0 + dev: false - parseurl@1.3.3: {} + /parseurl@1.3.3: + resolution: {integrity: sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==} + engines: {node: '>= 0.8'} + dev: false - pascal-case@3.1.2: + /pascal-case@3.1.2: + resolution: {integrity: sha512-uWlGT3YSnK9x3BQJaOdcZwrnV6hPpd8jFH1/ucpiLRPh/2zCVJKS19E4GvYHvaCcACn3foXZ0cLB9Wrx1KGe5g==} dependencies: no-case: 3.0.4 tslib: 2.7.0 + dev: false - path-exists@3.0.0: {} + /path-exists@3.0.0: + resolution: {integrity: sha512-bpC7GYwiDYQ4wYLe+FA8lhRjhQCMcQGuSgGGqDkg/QerRWw9CmGRT0iSOVRSZJ29NMLZgIzqaljJ63oaL4NIJQ==} + engines: {node: '>=4'} + dev: false - path-exists@4.0.0: {} + /path-exists@4.0.0: + resolution: {integrity: sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==} + engines: {node: '>=8'} + dev: false - path-is-absolute@1.0.1: {} + /path-is-absolute@1.0.1: + resolution: {integrity: sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==} + engines: {node: '>=0.10.0'} + dev: false - path-is-inside@1.0.2: {} + /path-is-inside@1.0.2: + resolution: {integrity: sha512-DUWJr3+ULp4zXmol/SZkFf3JGsS9/SIv+Y3Rt93/UjPpDpklB5f1er4O3POIbUuUJ3FXgqte2Q7SrU6zAqwk8w==} + dev: false - path-key@3.1.1: {} + /path-key@3.1.1: + resolution: {integrity: sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==} + engines: {node: '>=8'} - path-parse@1.0.7: {} + /path-parse@1.0.7: + resolution: {integrity: sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==} + dev: false - path-scurry@1.11.1: + /path-scurry@1.11.1: + resolution: {integrity: sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==} + engines: {node: '>=16 || 14 >=14.18'} dependencies: lru-cache: 10.4.3 minipass: 6.0.2 + dev: true - path-to-regexp@0.1.7: {} + /path-to-regexp@0.1.7: + resolution: {integrity: sha512-5DFkuoqlv1uYQKxy8omFBeJPQcdoE07Kv2sferDCrAq1ohOU+MSDswDIbnx3YAM60qIOnYa53wBhXW0EbMonrQ==} + dev: false - path-to-regexp@1.8.0: + /path-to-regexp@1.8.0: + resolution: {integrity: sha512-n43JRhlUKUAlibEJhPeir1ncUID16QnEjNpwzNdO3Lm4ywrBpBZ5oLD0I6br9evr1Y9JTqwRtAh7JLoOzAQdVA==} dependencies: isarray: 0.0.1 + dev: false - path-to-regexp@2.2.1: {} + /path-to-regexp@2.2.1: + resolution: {integrity: sha512-gu9bD6Ta5bwGrrU8muHzVOBFFREpp2iRkVfhBJahwJ6p6Xw20SjT0MxLnwkjOibQmGSYhiUnf2FLe7k+jcFmGQ==} + dev: false - path-type@4.0.0: {} + /path-type@4.0.0: + resolution: {integrity: sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==} + engines: {node: '>=8'} + dev: false - pend@1.2.0: {} + /pend@1.2.0: + resolution: {integrity: sha512-F3asv42UuXchdzt+xXqfW1OGlVBe+mxa2mqI0pg5yAHZPvFmY3Y6drSf/GQ1A86WgWEN9Kzh/WrgKa6iGcHXLg==} + dev: false - picocolors@1.0.1: {} + /picocolors@1.0.1: + resolution: {integrity: sha512-anP1Z8qwhkbmu7MFP5iTt+wQKXgwzf7zTyGlcdzabySa9vd0Xt392U0rVmz9poOaBj0uHJKyyo9/upk0HrEQew==} + dev: false - picomatch@2.3.1: {} + /picomatch@2.3.1: + resolution: {integrity: sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==} + engines: {node: '>=8.6'} + dev: false - pkg-dir@4.2.0: + /pkg-dir@4.2.0: + resolution: {integrity: sha512-HRDzbaKjC+AOWVXxAU/x54COGeIv9eb+6CkDSQoNTt4XyWoIJvuPsXizxu/Fr23EiekbtZwmh1IcIG/l/a10GQ==} + engines: {node: '>=8'} dependencies: find-up: 4.1.0 + dev: false - pkg-up@3.1.0: + /pkg-up@3.1.0: + resolution: {integrity: sha512-nDywThFk1i4BQK4twPQ6TA4RT8bDY96yeuCVBWL3ePARCiEKDRSrNGbFIgUJpLp+XeIR65v8ra7WuJOFUBtkMA==} + engines: {node: '>=8'} dependencies: find-up: 3.0.0 + dev: false - possible-typed-array-names@1.0.0: {} + /possible-typed-array-names@1.0.0: + resolution: {integrity: sha512-d7Uw+eZoloe0EHDIYoe+bQ5WXnGMOpmiZFTuMWCwpjzzkL2nTjcKiAk4hh8TjnGye2TwWOk3UXucZ+3rbmBa8Q==} + engines: {node: '>= 0.4'} + dev: false - postcss-calc@8.2.4(postcss@8.4.41): + /postcss-calc@8.2.4(postcss@8.4.41): + resolution: {integrity: sha512-SmWMSJmB8MRnnULldx0lQIyhSNvuDl9HfrZkaqqE/WHAhToYsAvDq+yAsA/kIyINDszOp3Rh0GFoNuH5Ypsm3Q==} + peerDependencies: + postcss: ^8.2.2 dependencies: postcss: 8.4.41 postcss-selector-parser: 6.1.2 postcss-value-parser: 4.2.0 + dev: false - postcss-colormin@5.3.1(postcss@8.4.41): + /postcss-colormin@5.3.1(postcss@8.4.41): + resolution: {integrity: sha512-UsWQG0AqTFQmpBegeLLc1+c3jIqBNB0zlDGRWR+dQ3pRKJL1oeMzyqmH3o2PIfn9MBdNrVPWhDbT769LxCTLJQ==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: browserslist: 4.23.3 caniuse-api: 3.0.0 colord: 2.9.3 postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-convert-values@5.1.3(postcss@8.4.41): + /postcss-convert-values@5.1.3(postcss@8.4.41): + resolution: {integrity: sha512-82pC1xkJZtcJEfiLw6UXnXVXScgtBrjlO5CBmuDQc+dlb88ZYheFsjTn40+zBVi3DkfF7iezO0nJUPLcJK3pvA==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: browserslist: 4.23.3 postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-discard-comments@5.1.2(postcss@8.4.41): + /postcss-discard-comments@5.1.2(postcss@8.4.41): + resolution: {integrity: sha512-+L8208OVbHVF2UQf1iDmRcbdjJkuBF6IS29yBDSiWUIzpYaAhtNl6JYnYm12FnkeCwQqF5LeklOu6rAqgfBZqQ==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 + dev: false - postcss-discard-duplicates@5.1.0(postcss@8.4.41): + /postcss-discard-duplicates@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-zmX3IoSI2aoenxHV6C7plngHWWhUOV3sP1T8y2ifzxzbtnuhk1EdPwm0S1bIUNaJ2eNbWeGLEwzw8huPD67aQw==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 + dev: false - postcss-discard-empty@5.1.1(postcss@8.4.41): + /postcss-discard-empty@5.1.1(postcss@8.4.41): + resolution: {integrity: sha512-zPz4WljiSuLWsI0ir4Mcnr4qQQ5e1Ukc3i7UfE2XcrwKK2LIPIqE5jxMRxO6GbI3cv//ztXDsXwEWT3BHOGh3A==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 + dev: false - postcss-discard-overridden@5.1.0(postcss@8.4.41): + /postcss-discard-overridden@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-21nOL7RqWR1kasIVdKs8HNqQJhFxLsyRfAnUDm4Fe4t4mCWL9OJiHvlHPjcd8zc5Myu89b/7wZDnOSjFgeWRtw==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 + dev: false - postcss-discard-unused@5.1.0(postcss@8.4.41): + /postcss-discard-unused@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-KwLWymI9hbwXmJa0dkrzpRbSJEh0vVUd7r8t0yOGPcfKzyJJxFM8kLyC5Ev9avji6nY95pOp1W6HqIrfT+0VGw==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-selector-parser: 6.1.2 + dev: false - postcss-loader@7.3.4(postcss@8.4.41)(typescript@5.5.4)(webpack@5.94.0): + /postcss-loader@7.3.4(postcss@8.4.41)(typescript@5.5.4)(webpack@5.94.0): + resolution: {integrity: sha512-iW5WTTBSC5BfsBJ9daFMPVrLT36MrNiC6fqOZTTaHjBNX6Pfd5p+hSBqe/fEeNd7pc13QiAyGt7VdGMw4eRC4A==} + engines: {node: '>= 14.15.0'} + peerDependencies: + postcss: ^7.0.0 || ^8.0.1 + webpack: ^5.0.0 dependencies: cosmiconfig: 8.3.6(typescript@5.5.4) jiti: 1.21.6 @@ -9673,273 +7508,503 @@ snapshots: webpack: 5.94.0(@swc/core@1.7.18) transitivePeerDependencies: - typescript + dev: false - postcss-merge-idents@5.1.1(postcss@8.4.41): + /postcss-merge-idents@5.1.1(postcss@8.4.41): + resolution: {integrity: sha512-pCijL1TREiCoog5nQp7wUe+TUonA2tC2sQ54UGeMmryK3UFGIYKqDyjnqd6RcuI4znFn9hWSLNN8xKE/vWcUQw==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: cssnano-utils: 3.1.0(postcss@8.4.41) postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-merge-longhand@5.1.7(postcss@8.4.41): + /postcss-merge-longhand@5.1.7(postcss@8.4.41): + resolution: {integrity: sha512-YCI9gZB+PLNskrK0BB3/2OzPnGhPkBEwmwhfYk1ilBHYVAZB7/tkTHFBAnCrvBBOmeYyMYw3DMjT55SyxMBzjQ==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 stylehacks: 5.1.1(postcss@8.4.41) + dev: false - postcss-merge-rules@5.1.4(postcss@8.4.41): + /postcss-merge-rules@5.1.4(postcss@8.4.41): + resolution: {integrity: sha512-0R2IuYpgU93y9lhVbO/OylTtKMVcHb67zjWIfCiKR9rWL3GUk1677LAqD/BcHizukdZEjT8Ru3oHRoAYoJy44g==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: browserslist: 4.23.3 caniuse-api: 3.0.0 cssnano-utils: 3.1.0(postcss@8.4.41) postcss: 8.4.41 postcss-selector-parser: 6.1.2 + dev: false - postcss-minify-font-values@5.1.0(postcss@8.4.41): + /postcss-minify-font-values@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-el3mYTgx13ZAPPirSVsHqFzl+BBBDrXvbySvPGFnQcTI4iNslrPaFq4muTkLZmKlGk4gyFAYUBMH30+HurREyA==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-minify-gradients@5.1.1(postcss@8.4.41): + /postcss-minify-gradients@5.1.1(postcss@8.4.41): + resolution: {integrity: sha512-VGvXMTpCEo4qHTNSa9A0a3D+dxGFZCYwR6Jokk+/3oB6flu2/PnPXAh2x7x52EkY5xlIHLm+Le8tJxe/7TNhzw==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: colord: 2.9.3 cssnano-utils: 3.1.0(postcss@8.4.41) postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-minify-params@5.1.4(postcss@8.4.41): + /postcss-minify-params@5.1.4(postcss@8.4.41): + resolution: {integrity: sha512-+mePA3MgdmVmv6g+30rn57USjOGSAyuxUmkfiWpzalZ8aiBkdPYjXWtHuwJGm1v5Ojy0Z0LaSYhHaLJQB0P8Jw==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: browserslist: 4.23.3 cssnano-utils: 3.1.0(postcss@8.4.41) postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-minify-selectors@5.2.1(postcss@8.4.41): + /postcss-minify-selectors@5.2.1(postcss@8.4.41): + resolution: {integrity: sha512-nPJu7OjZJTsVUmPdm2TcaiohIwxP+v8ha9NehQ2ye9szv4orirRU3SDdtUmKH+10nzn0bAyOXZ0UEr7OpvLehg==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-selector-parser: 6.1.2 + dev: false - postcss-modules-extract-imports@3.1.0(postcss@8.4.41): + /postcss-modules-extract-imports@3.1.0(postcss@8.4.41): + resolution: {integrity: sha512-k3kNe0aNFQDAZGbin48pL2VNidTF0w4/eASDsxlyspobzU3wZQLOGj7L9gfRe0Jo9/4uud09DsjFNH7winGv8Q==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 dependencies: postcss: 8.4.41 + dev: false - postcss-modules-local-by-default@4.0.5(postcss@8.4.41): + /postcss-modules-local-by-default@4.0.5(postcss@8.4.41): + resolution: {integrity: sha512-6MieY7sIfTK0hYfafw1OMEG+2bg8Q1ocHCpoWLqOKj3JXlKu4G7btkmM/B7lFubYkYWmRSPLZi5chid63ZaZYw==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 dependencies: icss-utils: 5.1.0(postcss@8.4.41) postcss: 8.4.41 postcss-selector-parser: 6.1.2 postcss-value-parser: 4.2.0 + dev: false - postcss-modules-scope@3.2.0(postcss@8.4.41): + /postcss-modules-scope@3.2.0(postcss@8.4.41): + resolution: {integrity: sha512-oq+g1ssrsZOsx9M96c5w8laRmvEu9C3adDSjI8oTcbfkrTE8hx/zfyobUoWIxaKPO8bt6S62kxpw5GqypEw1QQ==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 dependencies: postcss: 8.4.41 postcss-selector-parser: 6.1.2 + dev: false - postcss-modules-values@4.0.0(postcss@8.4.41): + /postcss-modules-values@4.0.0(postcss@8.4.41): + resolution: {integrity: sha512-RDxHkAiEGI78gS2ofyvCsu7iycRv7oqw5xMWn9iMoR0N/7mf9D50ecQqUo5BZ9Zh2vH4bCUR/ktCqbB9m8vJjQ==} + engines: {node: ^10 || ^12 || >= 14} + peerDependencies: + postcss: ^8.1.0 dependencies: icss-utils: 5.1.0(postcss@8.4.41) postcss: 8.4.41 + dev: false - postcss-normalize-charset@5.1.0(postcss@8.4.41): + /postcss-normalize-charset@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-mSgUJ+pd/ldRGVx26p2wz9dNZ7ji6Pn8VWBajMXFf8jk7vUoSrZ2lt/wZR7DtlZYKesmZI680qjr2CeFF2fbUg==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 + dev: false - postcss-normalize-display-values@5.1.0(postcss@8.4.41): + /postcss-normalize-display-values@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-WP4KIM4o2dazQXWmFaqMmcvsKmhdINFblgSeRgn8BJ6vxaMyaJkwAzpPpuvSIoG/rmX3M+IrRZEz2H0glrQNEA==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-normalize-positions@5.1.1(postcss@8.4.41): + /postcss-normalize-positions@5.1.1(postcss@8.4.41): + resolution: {integrity: sha512-6UpCb0G4eofTCQLFVuI3EVNZzBNPiIKcA1AKVka+31fTVySphr3VUgAIULBhxZkKgwLImhzMR2Bw1ORK+37INg==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-normalize-repeat-style@5.1.1(postcss@8.4.41): + /postcss-normalize-repeat-style@5.1.1(postcss@8.4.41): + resolution: {integrity: sha512-mFpLspGWkQtBcWIRFLmewo8aC3ImN2i/J3v8YCFUwDnPu3Xz4rLohDO26lGjwNsQxB3YF0KKRwspGzE2JEuS0g==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-normalize-string@5.1.0(postcss@8.4.41): + /postcss-normalize-string@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-oYiIJOf4T9T1N4i+abeIc7Vgm/xPCGih4bZz5Nm0/ARVJ7K6xrDlLwvwqOydvyL3RHNf8qZk6vo3aatiw/go3w==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-normalize-timing-functions@5.1.0(postcss@8.4.41): + /postcss-normalize-timing-functions@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-DOEkzJ4SAXv5xkHl0Wa9cZLF3WCBhF3o1SKVxKQAa+0pYKlueTpCgvkFAHfk+Y64ezX9+nITGrDZeVGgITJXjg==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-normalize-unicode@5.1.1(postcss@8.4.41): + /postcss-normalize-unicode@5.1.1(postcss@8.4.41): + resolution: {integrity: sha512-qnCL5jzkNUmKVhZoENp1mJiGNPcsJCs1aaRmURmeJGES23Z/ajaln+EPTD+rBeNkSryI+2WTdW+lwcVdOikrpA==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: browserslist: 4.23.3 postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-normalize-url@5.1.0(postcss@8.4.41): + /postcss-normalize-url@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-5upGeDO+PVthOxSmds43ZeMeZfKH+/DKgGRD7TElkkyS46JXAUhMzIKiCa7BabPeIy3AQcTkXwVVN7DbqsiCew==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: normalize-url: 6.1.0 postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-normalize-whitespace@5.1.1(postcss@8.4.41): + /postcss-normalize-whitespace@5.1.1(postcss@8.4.41): + resolution: {integrity: sha512-83ZJ4t3NUDETIHTa3uEg6asWjSBYL5EdkVB0sDncx9ERzOKBVJIUeDO9RyA9Zwtig8El1d79HBp0JEi8wvGQnA==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-ordered-values@5.1.3(postcss@8.4.41): + /postcss-ordered-values@5.1.3(postcss@8.4.41): + resolution: {integrity: sha512-9UO79VUhPwEkzbb3RNpqqghc6lcYej1aveQteWY+4POIwlqkYE21HKWaLDF6lWNuqCobEAyTovVhtI32Rbv2RQ==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: cssnano-utils: 3.1.0(postcss@8.4.41) postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-reduce-idents@5.2.0(postcss@8.4.41): + /postcss-reduce-idents@5.2.0(postcss@8.4.41): + resolution: {integrity: sha512-BTrLjICoSB6gxbc58D5mdBK8OhXRDqud/zodYfdSi52qvDHdMwk+9kB9xsM8yJThH/sZU5A6QVSmMmaN001gIg==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-reduce-initial@5.1.2(postcss@8.4.41): + /postcss-reduce-initial@5.1.2(postcss@8.4.41): + resolution: {integrity: sha512-dE/y2XRaqAi6OvjzD22pjTUQ8eOfc6m/natGHgKFBK9DxFmIm69YmaRVQrGgFlEfc1HePIurY0TmDeROK05rIg==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: browserslist: 4.23.3 caniuse-api: 3.0.0 postcss: 8.4.41 + dev: false - postcss-reduce-transforms@5.1.0(postcss@8.4.41): + /postcss-reduce-transforms@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-2fbdbmgir5AvpW9RLtdONx1QoYG2/EtqpNQbFASDlixBbAYuTcJ0dECwlqNqH7VbaUnEnh8SrxOe2sRIn24XyQ==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 + dev: false - postcss-selector-parser@6.1.2: + /postcss-selector-parser@6.1.2: + resolution: {integrity: sha512-Q8qQfPiZ+THO/3ZrOrO0cJJKfpYCagtMUkXbnEfmgUjwXg6z/WBeOyS9APBBPCTSiDV+s4SwQGu8yFsiMRIudg==} + engines: {node: '>=4'} dependencies: cssesc: 3.0.0 util-deprecate: 1.0.2 + dev: false - postcss-sort-media-queries@4.4.1(postcss@8.4.41): + /postcss-sort-media-queries@4.4.1(postcss@8.4.41): + resolution: {integrity: sha512-QDESFzDDGKgpiIh4GYXsSy6sek2yAwQx1JASl5AxBtU1Lq2JfKBljIPNdil989NcSKRQX1ToiaKphImtBuhXWw==} + engines: {node: '>=10.0.0'} + peerDependencies: + postcss: ^8.4.16 dependencies: postcss: 8.4.41 sort-css-media-queries: 2.1.0 + dev: false - postcss-svgo@5.1.0(postcss@8.4.41): + /postcss-svgo@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-D75KsH1zm5ZrHyxPakAxJWtkyXew5qwS70v56exwvw542d9CRtTo78K0WeFxZB4G7JXKKMbEZtZayTGdIky/eA==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-value-parser: 4.2.0 svgo: 2.8.0 + dev: false - postcss-unique-selectors@5.1.1(postcss@8.4.41): + /postcss-unique-selectors@5.1.1(postcss@8.4.41): + resolution: {integrity: sha512-5JiODlELrz8L2HwxfPnhOWZYWDxVHWL83ufOv84NrcgipI7TaeRsatAhK4Tr2/ZiYldpK/wBvw5BD3qfaK96GA==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 postcss-selector-parser: 6.1.2 + dev: false - postcss-value-parser@4.2.0: {} + /postcss-value-parser@4.2.0: + resolution: {integrity: sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==} + dev: false - postcss-zindex@5.1.0(postcss@8.4.41): + /postcss-zindex@5.1.0(postcss@8.4.41): + resolution: {integrity: sha512-fgFMf0OtVSBR1va1JNHYgMxYk73yhn/qb4uQDq1DLGYolz8gHCyr/sesEuGUaYs58E3ZJRcpoGuPVoB7Meiq9A==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: postcss: 8.4.41 + dev: false - postcss@8.4.41: + /postcss@8.4.41: + resolution: {integrity: sha512-TesUflQ0WKZqAvg52PWL6kHgLKP6xB6heTOdoYM0Wt2UHyxNa4K25EZZMgKns3BH1RLVbZCREPpLY0rhnNoHVQ==} + engines: {node: ^10 || ^12 || >=14} dependencies: nanoid: 3.3.7 picocolors: 1.0.1 source-map-js: 1.2.0 + dev: false - prepend-http@2.0.0: {} + /prepend-http@2.0.0: + resolution: {integrity: sha512-ravE6m9Atw9Z/jjttRUZ+clIXogdghyZAuWJ3qEzjT+jI/dL1ifAqhZeC5VHzQp1MSt1+jxKkFNemj/iO7tVUA==} + engines: {node: '>=4'} + dev: false - pretty-error@4.0.0: + /pretty-error@4.0.0: + resolution: {integrity: sha512-AoJ5YMAcXKYxKhuJGdcvse+Voc6v1RgnsR3nWcYU7q4t6z0Q6T86sv5Zq8VIRbOWWFpvdGE83LtdSMNd+6Y0xw==} dependencies: lodash: 4.17.21 renderkid: 3.0.0 + dev: false - pretty-time@1.1.0: {} + /pretty-time@1.1.0: + resolution: {integrity: sha512-28iF6xPQrP8Oa6uxE6a1biz+lWeTOAPKggvjB8HAs6nVMKZwf5bG++632Dx614hIWgUPkgivRfG+a8uAXGTIbA==} + engines: {node: '>=4'} + dev: false - prism-react-renderer@1.3.5(react@17.0.2): + /prism-react-renderer@1.3.5(react@17.0.2): + resolution: {integrity: sha512-IJ+MSwBWKG+SM3b2SUfdrhC+gu01QkV2KmRQgREThBfSQRoufqRfxfHUxpG1WcaFjP+kojcFyO9Qqtpgt3qLCg==} + peerDependencies: + react: '>=0.14.9' dependencies: react: 17.0.2 + dev: false - prismjs@1.29.0: {} + /prismjs@1.29.0: + resolution: {integrity: sha512-Kx/1w86q/epKcmte75LNrEoT+lX8pBpavuAbvJWRXar7Hz8jrtF+e3vY751p0R8H9HdArwaCTNDDzHg/ScJK1Q==} + engines: {node: '>=6'} + dev: false - process-nextick-args@2.0.1: {} + /process-nextick-args@2.0.1: + resolution: {integrity: sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==} + dev: false - promise@7.3.1: + /promise@7.3.1: + resolution: {integrity: sha512-nolQXZ/4L+bP/UGlkfaIujX9BKxGwmQ9OT4mOt5yvy8iK1h3wqTEJCijzGANTCCl9nWjY41juyAn2K3Q1hLLTg==} dependencies: asap: 2.0.6 + dev: false - prompts@2.4.2: + /prompts@2.4.2: + resolution: {integrity: sha512-NxNv/kLguCA7p3jE8oL2aEBsrJWgAakBpgmgK6lpPWV+WuOmY6r2/zbAVnP+T8bQlA0nzHXSJSJW0Hq7ylaD2Q==} + engines: {node: '>= 6'} dependencies: kleur: 3.0.3 sisteransi: 1.0.5 + dev: false - prop-types@15.8.1: + /prop-types@15.8.1: + resolution: {integrity: sha512-oj87CgZICdulUohogVAR7AjlC0327U4el4L6eAvOqCeudMDVU0NThNaV+b9Df4dXgSP1gXMTnPdhfe/2qDH5cg==} dependencies: loose-envify: 1.4.0 object-assign: 4.1.1 react-is: 16.13.1 + dev: false - property-information@5.6.0: + /property-information@5.6.0: + resolution: {integrity: sha512-YUHSPk+A30YPv+0Qf8i9Mbfe/C0hdPXk1s1jPVToV8pk8BQtpw10ct89Eo7OWkutrwqvT0eicAxlOg3dOAu8JA==} dependencies: xtend: 4.0.2 + dev: false - proxy-addr@2.0.7: + /proxy-addr@2.0.7: + resolution: {integrity: sha512-llQsMLSUDUPT44jdrU/O37qlnifitDP+ZwrmmZcoSKyLKvtZxpyV0n2/bD/N4tBAAZ/gJEdZU7KMraoK1+XYAg==} + engines: {node: '>= 0.10'} dependencies: forwarded: 0.2.0 ipaddr.js: 1.9.1 + dev: false - proxy-from-env@1.1.0: {} + /proxy-from-env@1.1.0: + resolution: {integrity: sha512-D+zkORCbA9f1tdWRK0RaCR3GPv50cMxcrz4X8k5LTSUD1Dkw47mKJEZQNunItRTkWwgtaUSo1RVFRIG9ZXiFYg==} + dev: false - pump@3.0.0: + /pump@3.0.0: + resolution: {integrity: sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==} dependencies: end-of-stream: 1.4.4 once: 1.4.0 + dev: false - punycode@1.4.1: {} + /punycode@1.4.1: + resolution: {integrity: sha512-jmYNElW7yvO7TV33CjSmvSiE2yco3bV2czu/OzDKdMNVZQWfxCblURLhf+47syQRBntjfLdd/H0egrzIG+oaFQ==} + dev: false - punycode@2.3.1: {} + /punycode@2.3.1: + resolution: {integrity: sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==} + engines: {node: '>=6'} + dev: false - pupa@2.1.1: + /pupa@2.1.1: + resolution: {integrity: sha512-l1jNAspIBSFqbT+y+5FosojNpVpF94nlI+wDUpqP9enwOTfHx9f0gh5nB96vl+6yTpsJsypeNrwfzPrKuHB41A==} + engines: {node: '>=8'} dependencies: escape-goat: 2.1.1 + dev: false + + /pure-color@1.3.0: + resolution: {integrity: sha512-QFADYnsVoBMw1srW7OVKEYjG+MbIa49s54w1MA1EDY6r2r/sTcKKYqRX1f4GYvnXP7eN/Pe9HFcX+hwzmrXRHA==} + dev: false - pure-color@1.3.0: {} + /q@1.5.1: + resolution: {integrity: sha512-kV/CThkXo6xyFEZUugw/+pIOywXcDbFYgSct5cT3gqlbkBE1SJdwy6UQoZvodiWF/ckQLZyDE/Bu1M6gVu5lVw==} + engines: {node: '>=0.6.0', teleport: '>=0.2.0'} + deprecated: |- + You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. - q@1.5.1: {} + (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) + dev: false - qs@6.11.0: + /qs@6.11.0: + resolution: {integrity: sha512-MvjoMCJwEarSbUYk5O+nmoSzSutSsTwF85zcHPQ9OrlFoZOYIjaqBAJIqIXjptyD5vThxGq52Xu/MaJzRkIk4Q==} + engines: {node: '>=0.6'} dependencies: side-channel: 1.0.6 + dev: false - queue-microtask@1.2.3: {} + /queue-microtask@1.2.3: + resolution: {integrity: sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==} + dev: false - queue@6.0.2: + /queue@6.0.2: + resolution: {integrity: sha512-iHZWu+q3IdFZFX36ro/lKBkSvfkztY5Y7HMiPlOUjhupPcG2JMfst2KKEpu5XndviX/3UhFbRngUPNKtgvtZiA==} dependencies: inherits: 2.0.4 + dev: false - randombytes@2.1.0: + /randombytes@2.1.0: + resolution: {integrity: sha512-vYl3iOX+4CKUWuxGi9Ukhie6fsqXqS9FE2Zaic4tNFD2N2QQaXOMFbuKK4QmDHC0JO6B1Zp41J0LpT0oR68amQ==} dependencies: safe-buffer: 5.2.1 + dev: false - range-parser@1.2.0: {} + /range-parser@1.2.0: + resolution: {integrity: sha512-kA5WQoNVo4t9lNx2kQNFCxKeBl5IbbSNBl1M/tLkw9WCn+hxNBAW5Qh8gdhs63CJnhjJ2zQWFoqPJP2sK1AV5A==} + engines: {node: '>= 0.6'} + dev: false - range-parser@1.2.1: {} + /range-parser@1.2.1: + resolution: {integrity: sha512-Hrgsx+orqoygnmhFbKaHE6c296J+HTAQXoxEF6gNupROmmGJRoyzfG3ccAveqCBrwr/2yxQ5BVd/GTl5agOwSg==} + engines: {node: '>= 0.6'} + dev: false - raw-body@2.5.2: + /raw-body@2.5.2: + resolution: {integrity: sha512-8zGqypfENjCIqGhgXToC8aB2r7YrBX+AQAfIPs/Mlk+BtPTztOvTS01NRW/3Eh60J+a48lt8qsCzirQ6loCVfA==} + engines: {node: '>= 0.8'} dependencies: bytes: 3.1.2 http-errors: 2.0.0 iconv-lite: 0.4.24 unpipe: 1.0.0 + dev: false - rc@1.2.8: + /rc@1.2.8: + resolution: {integrity: sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==} + hasBin: true dependencies: deep-extend: 0.6.0 ini: 1.3.8 minimist: 1.2.8 strip-json-comments: 2.0.1 + dev: false - react-base16-styling@0.6.0: + /react-base16-styling@0.6.0: + resolution: {integrity: sha512-yvh/7CArceR/jNATXOKDlvTnPKPmGZz7zsenQ3jUwLzHkNUR0CvY3yGYJbWJ/nnxsL8Sgmt5cO3/SILVuPO6TQ==} dependencies: base16: 1.0.0 lodash.curry: 4.1.1 lodash.flow: 3.5.0 pure-color: 1.3.0 + dev: false - react-dev-utils@12.0.1(typescript@5.5.4)(webpack@5.94.0): + /react-dev-utils@12.0.1(typescript@5.5.4)(webpack@5.94.0): + resolution: {integrity: sha512-84Ivxmr17KjUupyqzFode6xKhjwuEJDROWKJy/BthkL7Wn6NJ8h4WE6k/exAv6ImS+0oZLRRW5j/aINMHyeGeQ==} + engines: {node: '>=14'} + peerDependencies: + typescript: '>=2.7' + webpack: '>=4' + peerDependenciesMeta: + typescript: + optional: true dependencies: '@babel/code-frame': 7.24.7 address: 1.2.2 @@ -9971,19 +8036,32 @@ snapshots: - eslint - supports-color - vue-template-compiler + dev: false - react-dom@17.0.2(react@17.0.2): + /react-dom@17.0.2(react@17.0.2): + resolution: {integrity: sha512-s4h96KtLDUQlsENhMn1ar8t2bEa+q/YAtj8pPPdIjPDGBDIVNsrD9aXNWqspUe6AzKCIG0C1HZZLqLV7qpOBGA==} + peerDependencies: + react: 17.0.2 dependencies: loose-envify: 1.4.0 object-assign: 4.1.1 react: 17.0.2 scheduler: 0.20.2 + dev: false - react-error-overlay@6.0.11: {} + /react-error-overlay@6.0.11: + resolution: {integrity: sha512-/6UZ2qgEyH2aqzYZgQPxEnz33NJ2gNsnHA2o5+o4wW9bLM/JYQitNP9xPhsXwC08hMMovfGe/8retsdDsczPRg==} + dev: false - react-fast-compare@3.2.2: {} + /react-fast-compare@3.2.2: + resolution: {integrity: sha512-nsO+KSNgo1SbJqJEYRE9ERzo7YtYbou/OqjSQKxV7jcKox7+usiUVZOAC+XnDOABXggQTno0Y1CpVnuWEc1boQ==} + dev: false - react-helmet-async@1.3.0(react-dom@17.0.2)(react@17.0.2): + /react-helmet-async@1.3.0(react-dom@17.0.2)(react@17.0.2): + resolution: {integrity: sha512-9jZ57/dAn9t3q6hneQS0wukqC2ENOBgMNVEhb/ZG9ZSxUetzVIw4iAmEU38IaVg3QGYauQPhSeUTuIUtFglWpg==} + peerDependencies: + react: ^16.6.0 || ^17.0.0 || ^18.0.0 + react-dom: ^16.6.0 || ^17.0.0 || ^18.0.0 dependencies: '@babel/runtime': 7.25.4 invariant: 2.2.4 @@ -9992,17 +8070,28 @@ snapshots: react-dom: 17.0.2(react@17.0.2) react-fast-compare: 3.2.2 shallowequal: 1.1.0 + dev: false - react-helmet-async@2.0.5(react@17.0.2): + /react-helmet-async@2.0.5(react@17.0.2): + resolution: {integrity: sha512-rYUYHeus+i27MvFE+Jaa4WsyBKGkL6qVgbJvSBoX8mbsWoABJXdEO0bZyi0F6i+4f0NuIb8AvqPMj3iXFHkMwg==} + peerDependencies: + react: ^16.6.0 || ^17.0.0 || ^18.0.0 dependencies: invariant: 2.2.4 react: 17.0.2 react-fast-compare: 3.2.2 shallowequal: 1.1.0 + dev: false - react-is@16.13.1: {} + /react-is@16.13.1: + resolution: {integrity: sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ==} + dev: false - react-json-view@1.21.3(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2): + /react-json-view@1.21.3(@types/react@18.3.4)(react-dom@17.0.2)(react@17.0.2): + resolution: {integrity: sha512-13p8IREj9/x/Ye4WI/JpjhoIwuzEgUAtgJZNBJckfzJt1qyh24BdTm6UQNGnyTq9dapQdrqvquZTo3dz1X6Cjw==} + peerDependencies: + react: ^17.0.0 || ^16.3.0 || ^15.5.4 + react-dom: ^17.0.0 || ^16.3.0 || ^15.5.4 dependencies: flux: 4.0.4(react@17.0.2) react: 17.0.2 @@ -10013,22 +8102,39 @@ snapshots: transitivePeerDependencies: - '@types/react' - encoding + dev: false - react-lifecycles-compat@3.0.4: {} + /react-lifecycles-compat@3.0.4: + resolution: {integrity: sha512-fBASbA6LnOU9dOU2eW7aQ8xmYBSXUIWr+UmF9b1efZBazGNO+rcXT/icdKnYm2pTwcRylVUYwW7H1PHfLekVzA==} + dev: false - react-loadable-ssr-addon-v5-slorber@1.0.1(@docusaurus/react-loadable@5.5.2)(webpack@5.94.0): + /react-loadable-ssr-addon-v5-slorber@1.0.1(@docusaurus/react-loadable@5.5.2)(webpack@5.94.0): + resolution: {integrity: sha512-lq3Lyw1lGku8zUEJPDxsNm1AfYHBrO9Y1+olAYwpUJ2IGFBskM0DMKok97A6LWUpHm+o7IvQBOWu9MLenp9Z+A==} + engines: {node: '>=10.13.0'} + peerDependencies: + react-loadable: '*' + webpack: '>=4.41.1 || 5.x' dependencies: '@babel/runtime': 7.25.4 - react-loadable: '@docusaurus/react-loadable@5.5.2(react@17.0.2)' + react-loadable: /@docusaurus/react-loadable@5.5.2(react@17.0.2) webpack: 5.94.0(@swc/core@1.7.18) + dev: false - react-router-config@5.1.1(react-router@5.3.4)(react@17.0.2): + /react-router-config@5.1.1(react-router@5.3.4)(react@17.0.2): + resolution: {integrity: sha512-DuanZjaD8mQp1ppHjgnnUnyOlqYXZVjnov/JzFhjLEwd3Z4dYjMSnqrEzzGThH47vpCOqPPwJM2FtthLeJ8Pbg==} + peerDependencies: + react: '>=15' + react-router: '>=5' dependencies: '@babel/runtime': 7.25.4 react: 17.0.2 react-router: 5.3.4(react@17.0.2) + dev: false - react-router-dom@5.3.4(react@17.0.2): + /react-router-dom@5.3.4(react@17.0.2): + resolution: {integrity: sha512-m4EqFMHv/Ih4kpcBCONHbkT68KoAeHN4p3lAGoNryfHi0dMy0kCzEZakiKRsvg5wHZ/JLrLW8o8KomWiz/qbYQ==} + peerDependencies: + react: '>=15' dependencies: '@babel/runtime': 7.25.4 history: 4.10.1 @@ -10038,8 +8144,12 @@ snapshots: react-router: 5.3.4(react@17.0.2) tiny-invariant: 1.3.3 tiny-warning: 1.0.3 + dev: false - react-router@5.3.4(react@17.0.2): + /react-router@5.3.4(react@17.0.2): + resolution: {integrity: sha512-Ys9K+ppnJah3QuaRiLxk+jDWOR1MekYQrlytiXxC1RyfbdsZkS5pvKAzCCr031xHixZwpnsYNT5xysdFHQaYsA==} + peerDependencies: + react: '>=15' dependencies: '@babel/runtime': 7.25.4 history: 4.10.1 @@ -10051,8 +8161,13 @@ snapshots: react-is: 16.13.1 tiny-invariant: 1.3.3 tiny-warning: 1.0.3 + dev: false - react-textarea-autosize@8.5.3(@types/react@18.3.4)(react@17.0.2): + /react-textarea-autosize@8.5.3(@types/react@18.3.4)(react@17.0.2): + resolution: {integrity: sha512-XT1024o2pqCuZSuBt9FwHlaDeNtVrtCXu0Rnz88t1jUGheCLa3PhjE1GH8Ctm2axEtvdCl5SUHYschyQ0L5QHQ==} + engines: {node: '>=10'} + peerDependencies: + react: ^16.8.0 || ^17.0.0 || ^18.0.0 dependencies: '@babel/runtime': 7.25.4 react: 17.0.2 @@ -10060,13 +8175,18 @@ snapshots: use-latest: 1.2.1(@types/react@18.3.4)(react@17.0.2) transitivePeerDependencies: - '@types/react' + dev: false - react@17.0.2: + /react@17.0.2: + resolution: {integrity: sha512-gnhPt75i/dq/z3/6q/0asP78D0u592D5L1pd7M8P+dck6Fu/jJeL6iVVK23fptSUZj8Vjf++7wXA8UNclGQcbA==} + engines: {node: '>=0.10.0'} dependencies: loose-envify: 1.4.0 object-assign: 4.1.1 + dev: false - readable-stream@2.3.8: + /readable-stream@2.3.8: + resolution: {integrity: sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==} dependencies: core-util-is: 1.0.3 inherits: 2.0.4 @@ -10075,47 +8195,76 @@ snapshots: safe-buffer: 5.1.2 string_decoder: 1.1.1 util-deprecate: 1.0.2 + dev: false - readable-stream@3.6.2: + /readable-stream@3.6.2: + resolution: {integrity: sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==} + engines: {node: '>= 6'} dependencies: inherits: 2.0.4 string_decoder: 1.3.0 util-deprecate: 1.0.2 + dev: false - readdirp@3.6.0: + /readdirp@3.6.0: + resolution: {integrity: sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==} + engines: {node: '>=8.10.0'} dependencies: picomatch: 2.3.1 + dev: false - reading-time@1.5.0: {} + /reading-time@1.5.0: + resolution: {integrity: sha512-onYyVhBNr4CmAxFsKS7bz+uTLRakypIe4R+5A824vBSkQy/hB3fZepoVEf8OVAxzLvK+H/jm9TzpI3ETSm64Kg==} + dev: false - rechoir@0.6.2: + /rechoir@0.6.2: + resolution: {integrity: sha512-HFM8rkZ+i3zrV+4LQjwQ0W+ez98pApMGM3HUrN04j3CqzPOzl9nmP15Y8YXNm8QHGv/eacOVEjqhmWpkRV0NAw==} + engines: {node: '>= 0.10'} dependencies: resolve: 1.22.8 + dev: false - recursive-readdir@2.2.3: + /recursive-readdir@2.2.3: + resolution: {integrity: sha512-8HrF5ZsXk5FAH9dgsx3BlUer73nIhuj+9OrQwEbLTPOBzGkL1lsFCR01am+v+0m2Cmbs1nP12hLDl5FA7EszKA==} + engines: {node: '>=6.0.0'} dependencies: minimatch: 3.1.2 + dev: false - regenerate-unicode-properties@10.1.1: + /regenerate-unicode-properties@10.1.1: + resolution: {integrity: sha512-X007RyZLsCJVVrjgEFVpLUTZwyOZk3oiL75ZcuYjlIWd6rNJtOjkBwQc5AsRrpbKVkxN6sklw/k/9m2jJYOf8Q==} + engines: {node: '>=4'} dependencies: regenerate: 1.4.2 + dev: false - regenerate@1.4.2: {} + /regenerate@1.4.2: + resolution: {integrity: sha512-zrceR/XhGYU/d/opr2EKO7aRHUeiBI8qjtfHqADTwZd6Szfy16la6kqD0MIUs5z5hx6AaKa+PixpPrR289+I0A==} + dev: false - regenerator-runtime@0.14.1: {} + /regenerator-runtime@0.14.1: + resolution: {integrity: sha512-dYnhHh0nJoMfnkZs6GmmhFknAGRrLznOu5nc9ML+EJxGvrx6H7teuevqVqCuPcPK//3eDrrjQhehXVx9cnkGdw==} + dev: false - regenerator-transform@0.15.2: + /regenerator-transform@0.15.2: + resolution: {integrity: sha512-hfMp2BoF0qOk3uc5V20ALGDS2ddjQaLrdl7xrGXvAIow7qeWRM2VA2HuCHkUKk9slq3VwEwLNK3DFBqDfPGYtg==} dependencies: '@babel/runtime': 7.25.4 + dev: false - regexp.prototype.flags@1.5.2: + /regexp.prototype.flags@1.5.2: + resolution: {integrity: sha512-NcDiDkTLuPR+++OCKB0nWafEmhg/Da8aUPLPMQbK+bxKKCm1/S5he+AqYa4PlMCVBalb4/yxIRub6qkEx5yJbw==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 define-properties: 1.2.1 es-errors: 1.3.0 set-function-name: 2.0.2 + dev: false - regexpu-core@5.3.2: + /regexpu-core@5.3.2: + resolution: {integrity: sha512-RAM5FlZz+Lhmo7db9L298p2vHP5ZywrVXmVXpmAD9GuL5MPH6t9ROw1iA/wfHkQ76Qe7AaPF0nGuim96/IrQMQ==} + engines: {node: '>=4'} dependencies: '@babel/regjsgen': 0.8.0 regenerate: 1.4.2 @@ -10123,30 +8272,48 @@ snapshots: regjsparser: 0.9.1 unicode-match-property-ecmascript: 2.0.0 unicode-match-property-value-ecmascript: 2.1.0 + dev: false - registry-auth-token@4.2.2: + /registry-auth-token@4.2.2: + resolution: {integrity: sha512-PC5ZysNb42zpFME6D/XlIgtNGdTl8bBOCw90xQLVMpzuuubJKYDWFAEuUNc+Cn8Z8724tg2SDhDRrkVEsqfDMg==} + engines: {node: '>=6.0.0'} dependencies: rc: 1.2.8 + dev: false - registry-url@5.1.0: + /registry-url@5.1.0: + resolution: {integrity: sha512-8acYXXTI0AkQv6RAOjE3vOaIXZkT9wo4LOFbBKYQEEnnMNBpKqdUrI6S4NT0KPIo/WVvJ5tE/X5LF/TQUf0ekw==} + engines: {node: '>=8'} dependencies: rc: 1.2.8 + dev: false - regjsparser@0.9.1: + /regjsparser@0.9.1: + resolution: {integrity: sha512-dQUtn90WanSNl+7mQKcXAgZxvUe7Z0SqXlgzv0za4LwiUhyzBC58yQO3liFoUgu8GiJVInAhJjkj1N0EtQ5nkQ==} + hasBin: true dependencies: jsesc: 0.5.0 + dev: false - relateurl@0.2.7: {} + /relateurl@0.2.7: + resolution: {integrity: sha512-G08Dxvm4iDN3MLM0EsP62EDV9IuhXPR6blNz6Utcp7zyV3tr4HVNINt6MpaRWbxoOHT3Q7YN2P+jaHX8vUbgog==} + engines: {node: '>= 0.10'} + dev: false - remark-emoji@2.2.0: + /remark-emoji@2.2.0: + resolution: {integrity: sha512-P3cj9s5ggsUvWw5fS2uzCHJMGuXYRb0NnZqYlNecewXt8QBU9n5vW3DUUKOhepS8F9CwdMx9B8a3i7pqFWAI5w==} dependencies: emoticon: 3.2.0 node-emoji: 1.11.0 unist-util-visit: 2.0.3 + dev: false - remark-footnotes@2.0.0: {} + /remark-footnotes@2.0.0: + resolution: {integrity: sha512-3Clt8ZMH75Ayjp9q4CorNeyjwIxHFcTkaektplKGl2A1jNGEUey8cKL0ZC5vJwfcD5GFGsNLImLG/NGzWIzoMQ==} + dev: false - remark-mdx@1.6.22: + /remark-mdx@1.6.22: + resolution: {integrity: sha512-phMHBJgeV76uyFkH4rvzCftLfKCr2RZuF+/gmVcaKrpsihyzmhXjA0BEMDaPTXG5y8qZOKPVo83NAOX01LPnOQ==} dependencies: '@babel/core': 7.12.9 '@babel/helper-plugin-utils': 7.10.4 @@ -10158,8 +8325,10 @@ snapshots: unified: 9.2.0 transitivePeerDependencies: - supports-color + dev: false - remark-parse@8.0.3: + /remark-parse@8.0.3: + resolution: {integrity: sha512-E1K9+QLGgggHxCQtLt++uXltxEprmWzNfg+MxpfHsZlrddKzZ/hZyWHDbK3/Ap8HJQqYJRXP+jHczdL6q6i85Q==} dependencies: ccount: 1.1.0 collapse-white-space: 1.0.6 @@ -10177,151 +8346,253 @@ snapshots: unist-util-remove-position: 2.0.1 vfile-location: 3.2.0 xtend: 4.0.2 + dev: false - remark-squeeze-paragraphs@4.0.0: + /remark-squeeze-paragraphs@4.0.0: + resolution: {integrity: sha512-8qRqmL9F4nuLPIgl92XUuxI3pFxize+F1H0e/W3llTk0UsjJaj01+RrirkMw7P21RKe4X6goQhYRSvNWX+70Rw==} dependencies: mdast-squeeze-paragraphs: 4.0.0 + dev: false - renderkid@3.0.0: + /renderkid@3.0.0: + resolution: {integrity: sha512-q/7VIQA8lmM1hF+jn+sFSPWGlMkSAeNYcPLmDQx2zzuiDfaLrOmumR8iaUKlenFgh0XRPIUeSPlH3A+AW3Z5pg==} dependencies: css-select: 4.3.0 dom-converter: 0.2.0 htmlparser2: 6.1.0 lodash: 4.17.21 strip-ansi: 6.0.1 + dev: false - repeat-string@1.6.1: {} + /repeat-string@1.6.1: + resolution: {integrity: sha512-PV0dzCYDNfRi1jCDbJzpW7jNNDRuCOG/jI5ctQcGKt/clZD+YcPS3yIlWuTJMmESC8aevCFmWJy5wjAFgNqN6w==} + engines: {node: '>=0.10'} + dev: false - require-from-string@2.0.2: {} + /require-from-string@2.0.2: + resolution: {integrity: sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==} + engines: {node: '>=0.10.0'} + dev: false - require-like@0.1.2: {} + /require-like@0.1.2: + resolution: {integrity: sha512-oyrU88skkMtDdauHDuKVrgR+zuItqr6/c//FXzvmxRGMexSDc6hNvJInGW3LL46n+8b50RykrvwSUIIQH2LQ5A==} + dev: false - requires-port@1.0.0: {} + /requires-port@1.0.0: + resolution: {integrity: sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ==} + dev: false - resolve-from@4.0.0: {} + /resolve-from@4.0.0: + resolution: {integrity: sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==} + engines: {node: '>=4'} + dev: false - resolve-pathname@3.0.0: {} + /resolve-pathname@3.0.0: + resolution: {integrity: sha512-C7rARubxI8bXFNB/hqcp/4iUeIXJhJZvFPFPiSPRnhU5UPxzMFIl+2E6yY6c4k9giDJAhtV+enfA+G89N6Csng==} + dev: false - resolve@1.22.8: + /resolve@1.22.8: + resolution: {integrity: sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw==} + hasBin: true dependencies: is-core-module: 2.15.1 path-parse: 1.0.7 supports-preserve-symlinks-flag: 1.0.0 + dev: false - responselike@1.0.2: + /responselike@1.0.2: + resolution: {integrity: sha512-/Fpe5guzJk1gPqdJLJR5u7eG/gNY4nImjbRDaVWVMRhne55TCmj2i9Q+54PBRfatRC8v/rIiv9BN0pMd9OV5EQ==} dependencies: lowercase-keys: 1.0.1 + dev: false - retry@0.13.1: {} + /retry@0.13.1: + resolution: {integrity: sha512-XQBQ3I8W1Cge0Seh+6gjj03LbmRFWuoszgK9ooCpwYIrhhoO80pfq4cUkU5DkknwfOfFteRwlZ56PYOGYyFWdg==} + engines: {node: '>= 4'} + dev: false - reusify@1.0.4: {} + /reusify@1.0.4: + resolution: {integrity: sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==} + engines: {iojs: '>=1.0.0', node: '>=0.10.0'} + dev: false - rimraf@3.0.2: + /rimraf@3.0.2: + resolution: {integrity: sha512-JZkJMZkAGFFPP2YqXZXPbMlMBgsxzE8ILs4lMIX/2o0L9UBw9O/Y3o6wFw/i9YLapcUJWwqbi3kdxIPdC62TIA==} + deprecated: Rimraf versions prior to v4 are no longer supported + hasBin: true dependencies: glob: 7.2.3 + dev: false - rtl-detect@1.1.2: {} + /rtl-detect@1.1.2: + resolution: {integrity: sha512-PGMBq03+TTG/p/cRB7HCLKJ1MgDIi07+QU1faSjiYRfmY5UsAttV9Hs08jDAHVwcOwmVLcSJkpwyfXszVjWfIQ==} + dev: false - rtlcss@3.5.0: + /rtlcss@3.5.0: + resolution: {integrity: sha512-wzgMaMFHQTnyi9YOwsx9LjOxYXJPzS8sYnFaKm6R5ysvTkwzHiB0vxnbHwchHQT65PTdBjDG21/kQBWI7q9O7A==} + hasBin: true dependencies: find-up: 5.0.0 picocolors: 1.0.1 postcss: 8.4.41 strip-json-comments: 3.1.1 + dev: false - run-con@1.2.12: + /run-con@1.2.12: + resolution: {integrity: sha512-5257ILMYIF4RztL9uoZ7V9Q97zHtNHn5bN3NobeAnzB1P3ASLgg8qocM2u+R18ttp+VEM78N2LK8XcNVtnSRrg==} + hasBin: true dependencies: deep-extend: 0.6.0 ini: 3.0.1 minimist: 1.2.8 strip-json-comments: 3.1.1 + dev: true - run-parallel@1.2.0: + /run-parallel@1.2.0: + resolution: {integrity: sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==} dependencies: queue-microtask: 1.2.3 + dev: false - rxjs@7.8.1: + /rxjs@7.8.1: + resolution: {integrity: sha512-AA3TVj+0A2iuIoQkWEK/tqFjBq2j+6PO6Y0zJcvzLAFhEFIO3HL0vls9hWLncZbAAbK0mar7oZ4V079I/qPMxg==} dependencies: tslib: 2.7.0 + dev: false - safe-array-concat@1.1.2: + /safe-array-concat@1.1.2: + resolution: {integrity: sha512-vj6RsCsWBCf19jIeHEfkRMw8DPiBb+DMXklQ/1SGDHOMlHdPUkZXFQ2YdplS23zESTijAcurb1aSgJA3AgMu1Q==} + engines: {node: '>=0.4'} dependencies: call-bind: 1.0.7 get-intrinsic: 1.2.4 has-symbols: 1.0.3 isarray: 2.0.5 + dev: false - safe-buffer@5.1.2: {} + /safe-buffer@5.1.2: + resolution: {integrity: sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==} + dev: false - safe-buffer@5.2.1: {} + /safe-buffer@5.2.1: + resolution: {integrity: sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==} + dev: false - safe-regex-test@1.0.3: + /safe-regex-test@1.0.3: + resolution: {integrity: sha512-CdASjNJPvRa7roO6Ra/gLYBTzYzzPyyBXxIMdGW3USQLyjWEls2RgW5UBTXaQVp+OrpeCK3bLem8smtmheoRuw==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 es-errors: 1.3.0 is-regex: 1.1.4 + dev: false - safer-buffer@2.1.2: {} + /safer-buffer@2.1.2: + resolution: {integrity: sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==} + dev: false - sax@1.2.4: {} + /sax@1.2.4: + resolution: {integrity: sha512-NqVDv9TpANUjFm0N8uM5GxL36UgKi9/atZw+x7YFnQ8ckwFGKrl4xX4yWtrey3UJm5nP1kUbnYgLopqWNSRhWw==} + dev: false - sax@1.4.1: {} + /sax@1.4.1: + resolution: {integrity: sha512-+aWOz7yVScEGoKNd4PA10LZ8sk0A/z5+nXQG5giUO5rprX9jgYsTdov9qCchZiPIZezbZH+jRut8nPodFAX4Jg==} + dev: false - scheduler@0.20.2: + /scheduler@0.20.2: + resolution: {integrity: sha512-2eWfGgAqqWFGqtdMmcL5zCMK1U8KlXv8SQFGglL3CEtd0aDVDWgeF/YoCmvln55m5zSk3J/20hTaSBeSObsQDQ==} dependencies: loose-envify: 1.4.0 object-assign: 4.1.1 + dev: false - schema-utils@2.7.0: + /schema-utils@2.7.0: + resolution: {integrity: sha512-0ilKFI6QQF5nxDZLFn2dMjvc4hjg/Wkg7rHd3jK6/A4a1Hl9VFdQWvgB1UMGoU94pad1P/8N7fMcEnLnSiju8A==} + engines: {node: '>= 8.9.0'} dependencies: '@types/json-schema': 7.0.15 ajv: 6.12.6 ajv-keywords: 3.5.2(ajv@6.12.6) + dev: false - schema-utils@2.7.1: + /schema-utils@2.7.1: + resolution: {integrity: sha512-SHiNtMOUGWBQJwzISiVYKu82GiV4QYGePp3odlY1tuKO7gPtphAT5R/py0fA6xtbgLL/RvtJZnU9b8s0F1q0Xg==} + engines: {node: '>= 8.9.0'} dependencies: '@types/json-schema': 7.0.15 ajv: 6.12.6 ajv-keywords: 3.5.2(ajv@6.12.6) + dev: false - schema-utils@3.3.0: + /schema-utils@3.3.0: + resolution: {integrity: sha512-pN/yOAvcC+5rQ5nERGuwrjLlYvLTbCibnZ1I7B1LaiAz9BRBlE9GMgE/eqV30P7aJQUf7Ddimy/RsbYO/GrVGg==} + engines: {node: '>= 10.13.0'} dependencies: '@types/json-schema': 7.0.15 ajv: 6.12.6 ajv-keywords: 3.5.2(ajv@6.12.6) + dev: false - schema-utils@4.2.0: + /schema-utils@4.2.0: + resolution: {integrity: sha512-L0jRsrPpjdckP3oPug3/VxNKt2trR8TcabrM6FOAAlvC/9Phcmm+cuAgTlxBqdBR1WJx7Naj9WHw+aOmheSVbw==} + engines: {node: '>= 12.13.0'} dependencies: '@types/json-schema': 7.0.15 ajv: 8.17.1 ajv-formats: 2.1.1(ajv@8.17.1) ajv-keywords: 5.1.0(ajv@8.17.1) + dev: false - search-insights@2.17.0: {} + /search-insights@2.17.0: + resolution: {integrity: sha512-AskayU3QNsXQzSL6v4LTYST7NNfs2HWyHHB+sdORP9chsytAhro5XRfToAMI/LAVYgNbzowVZTMfBRodgbUHKg==} + dev: false - section-matter@1.0.0: + /section-matter@1.0.0: + resolution: {integrity: sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==} + engines: {node: '>=4'} dependencies: extend-shallow: 2.0.1 kind-of: 6.0.3 + dev: false - select-hose@2.0.0: {} + /select-hose@2.0.0: + resolution: {integrity: sha512-mEugaLK+YfkijB4fx0e6kImuJdCIt2LxCRcbEYPqRGCs4F2ogyfZU5IAZRdjCP8JPq2AtdNoC/Dux63d9Kiryg==} + dev: false - selfsigned@2.4.1: + /selfsigned@2.4.1: + resolution: {integrity: sha512-th5B4L2U+eGLq1TVh7zNRGBapioSORUeymIydxgFpwww9d2qyKvtuPU2jJuHvYAwwqi2Y596QBL3eEqcPEYL8Q==} + engines: {node: '>=10'} dependencies: '@types/node-forge': 1.3.11 node-forge: 1.3.1 + dev: false - semver-diff@3.1.1: + /semver-diff@3.1.1: + resolution: {integrity: sha512-GX0Ix/CJcHyB8c4ykpHGIAvLyOwOobtM/8d+TQkAd81/bEjgPHrfba41Vpesr7jX/t8Uh+R3EX9eAS5be+jQYg==} + engines: {node: '>=8'} dependencies: semver: 6.3.1 + dev: false - semver@5.7.2: {} + /semver@5.7.2: + resolution: {integrity: sha512-cBznnQ9KjJqU67B52RMC65CMarK2600WFnbkcaiwWq3xy/5haFJlshgnpjovMVJ+Hff49d8GEn0b87C5pDQ10g==} + hasBin: true + dev: false - semver@6.3.1: {} + /semver@6.3.1: + resolution: {integrity: sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==} + hasBin: true + dev: false - semver@7.6.3: {} + /semver@7.6.3: + resolution: {integrity: sha512-oVekP1cKtI+CTDvHWYFUcMtsK/00wmAEfyqKfNdARm8u1wNVhSgaX7A8d4UuIlUI5e84iEwOhs7ZPYRmzU9U6A==} + engines: {node: '>=10'} + hasBin: true + dev: false - send@0.18.0: + /send@0.18.0: + resolution: {integrity: sha512-qqWzuOjSFOuqPjFe4NOsMLafToQQwBSOEpS+FwEt3A2V3vKubTquT3vmLTQpFgMXp8AlFWFuP1qKaJZOtPpVXg==} + engines: {node: '>= 0.8.0'} dependencies: debug: 2.6.9 depd: 2.0.0 @@ -10338,12 +8609,16 @@ snapshots: statuses: 2.0.1 transitivePeerDependencies: - supports-color + dev: false - serialize-javascript@6.0.2: + /serialize-javascript@6.0.2: + resolution: {integrity: sha512-Saa1xPByTTq2gdeFZYLLo+RFE35NHZkAbqZeWNd3BpzppeVisAqpDjcp8dyf6uIvEqJRd46jemmyA4iFIeVk8g==} dependencies: randombytes: 2.1.0 + dev: false - serve-handler@6.1.5: + /serve-handler@6.1.5: + resolution: {integrity: sha512-ijPFle6Hwe8zfmBxJdE+5fta53fdIY0lHISJvuikXB3VYFafRjMRpOffSPvCYsbKyBA7pvy9oYr/BT1O3EArlg==} dependencies: bytes: 3.0.0 content-disposition: 0.5.2 @@ -10353,8 +8628,11 @@ snapshots: path-is-inside: 1.0.2 path-to-regexp: 2.2.1 range-parser: 1.2.0 + dev: false - serve-index@1.9.1: + /serve-index@1.9.1: + resolution: {integrity: sha512-pXHfKNP4qujrtteMrSBb0rc8HJ9Ms/GrXwcUtUtD5s4ewDJI8bT3Cz2zTVRMKtri49pLx2e0Ya8ziP5Ya2pZZw==} + engines: {node: '>= 0.8.0'} dependencies: accepts: 1.3.8 batch: 0.6.1 @@ -10365,8 +8643,11 @@ snapshots: parseurl: 1.3.3 transitivePeerDependencies: - supports-color + dev: false - serve-static@1.15.0: + /serve-static@1.15.0: + resolution: {integrity: sha512-XGuRDNjXUijsUL0vl6nSD7cwURuzEgglbOaFuZM9g3kwDXOWVTck0jLzjPzGD+TazWbboZYu52/9/XPdUgne9g==} + engines: {node: '>= 0.8.0'} dependencies: encodeurl: 1.0.2 escape-html: 1.0.3 @@ -10374,8 +8655,11 @@ snapshots: send: 0.18.0 transitivePeerDependencies: - supports-color + dev: false - set-function-length@1.2.2: + /set-function-length@1.2.2: + resolution: {integrity: sha512-pgRc4hJ4/sNjWCSS9AmnS40x3bNMDTknHgL5UaMBTMyJnU90EgWh1Rz+MC9eFu4BuN/UwZjKQuY/1v3rM7HMfg==} + engines: {node: '>= 0.4'} dependencies: define-data-property: 1.1.4 es-errors: 1.3.0 @@ -10383,92 +8667,159 @@ snapshots: get-intrinsic: 1.2.4 gopd: 1.0.1 has-property-descriptors: 1.0.2 + dev: false - set-function-name@2.0.2: + /set-function-name@2.0.2: + resolution: {integrity: sha512-7PGFlmtwsEADb0WYyvCMa1t+yke6daIG4Wirafur5kcf+MhUnPms1UeR0CKQdTZD81yESwMHbtn+TR+dMviakQ==} + engines: {node: '>= 0.4'} dependencies: define-data-property: 1.1.4 es-errors: 1.3.0 functions-have-names: 1.2.3 has-property-descriptors: 1.0.2 + dev: false - setimmediate@1.0.5: {} + /setimmediate@1.0.5: + resolution: {integrity: sha512-MATJdZp8sLqDl/68LfQmbP8zKPLQNV6BIZoIgrscFDQ+RsvK/BxeDQOgyxKKoh0y/8h3BqVFnCqQ/gd+reiIXA==} + dev: false - setprototypeof@1.1.0: {} + /setprototypeof@1.1.0: + resolution: {integrity: sha512-BvE/TwpZX4FXExxOxZyRGQQv651MSwmWKZGqvmPcRIjDqWub67kTKuIMx43cZZrS/cBBzwBcNDWoFxt2XEFIpQ==} + dev: false - setprototypeof@1.2.0: {} + /setprototypeof@1.2.0: + resolution: {integrity: sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw==} + dev: false - shallow-clone@3.0.1: + /shallow-clone@3.0.1: + resolution: {integrity: sha512-/6KqX+GVUdqPuPPd2LxDDxzX6CAbjJehAAOKlNpqqUpAqPM6HeL8f+o3a+JsyGjn2lv0WY8UsTgUJjU9Ok55NA==} + engines: {node: '>=8'} dependencies: kind-of: 6.0.3 + dev: false - shallowequal@1.1.0: {} + /shallowequal@1.1.0: + resolution: {integrity: sha512-y0m1JoUZSlPAjXVtPPW70aZWfIL/dSP7AFkRnniLCrK/8MDKog3TySTBmckD+RObVxH0v4Tox67+F14PdED2oQ==} + dev: false - shebang-command@2.0.0: + /shebang-command@2.0.0: + resolution: {integrity: sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==} + engines: {node: '>=8'} dependencies: shebang-regex: 3.0.0 - shebang-regex@3.0.0: {} + /shebang-regex@3.0.0: + resolution: {integrity: sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==} + engines: {node: '>=8'} - shell-quote@1.8.1: {} + /shell-quote@1.8.1: + resolution: {integrity: sha512-6j1W9l1iAs/4xYBI1SYOVZyFcCis9b4KCLQ8fgAGG07QvzaRLVVRQvAy85yNmmZSjYjg4MWh4gNvlPujU/5LpA==} + dev: false - shelljs@0.8.5: + /shelljs@0.8.5: + resolution: {integrity: sha512-TiwcRcrkhHvbrZbnRcFYMLl30Dfov3HKqzp5tO5b4pt6G/SezKcYhmDg15zXVBswHmctSAQKznqNW2LO5tTDow==} + engines: {node: '>=4'} + hasBin: true dependencies: glob: 7.2.3 interpret: 1.4.0 rechoir: 0.6.2 + dev: false - side-channel@1.0.6: + /side-channel@1.0.6: + resolution: {integrity: sha512-fDW/EZ6Q9RiO8eFG8Hj+7u/oW+XrPTIChwCOM2+th2A6OblDtYYIpve9m+KvI9Z4C9qSEXlaGR6bTEYHReuglA==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 es-errors: 1.3.0 get-intrinsic: 1.2.4 object-inspect: 1.13.2 + dev: false - signal-exit@3.0.7: {} + /signal-exit@3.0.7: + resolution: {integrity: sha512-wnD2ZE+l+SPC/uoS0vXeE9L1+0wuaMqKlfz9AMUo38JsyLSBWSFcHR1Rri62LZc12vLr1gb3jl7iwQhgwpAbGQ==} + dev: false - signal-exit@4.1.0: {} + /signal-exit@4.1.0: + resolution: {integrity: sha512-bzyZ1e88w9O1iNJbKnOlvYTrWPDl46O1bG0D3XInv+9tkPrxrN8jUUTiFlDkkmKWgn1M6CfIA13SuGqOa9Korw==} + engines: {node: '>=14'} + dev: true - sirv@2.0.4: + /sirv@2.0.4: + resolution: {integrity: sha512-94Bdh3cC2PKrbgSOUqTiGPWVZeSiXfKOVZNJniWoqrWrRkB1CJzBU3NEbiTsPcYy1lDsANA/THzS+9WBiy5nfQ==} + engines: {node: '>= 10'} dependencies: '@polka/url': 1.0.0-next.25 mrmime: 2.0.0 totalist: 3.0.1 + dev: false - sisteransi@1.0.5: {} + /sisteransi@1.0.5: + resolution: {integrity: sha512-bLGGlR1QxBcynn2d5YmDX4MGjlZvy2MRBDRNHLJ8VI6l6+9FUiyTFNJ0IveOSP0bcXgVDPRcfGqA0pjaqUpfVg==} + dev: false - sitemap@7.1.2: + /sitemap@7.1.2: + resolution: {integrity: sha512-ARCqzHJ0p4gWt+j7NlU5eDlIO9+Rkr/JhPFZKKQ1l5GCus7rJH4UdrlVAh0xC/gDS/Qir2UMxqYNHtsKr2rpCw==} + engines: {node: '>=12.0.0', npm: '>=5.6.0'} + hasBin: true dependencies: '@types/node': 17.0.45 '@types/sax': 1.2.7 arg: 5.0.2 sax: 1.4.1 + dev: false - slash@3.0.0: {} + /slash@3.0.0: + resolution: {integrity: sha512-g9Q1haeby36OSStwb4ntCGGGaKsaVSjQ68fBxoQcutl5fS1vuY18H3wSt3jFyFtrkx+Kz0V1G85A4MyAdDMi2Q==} + engines: {node: '>=8'} + dev: false - slash@4.0.0: {} + /slash@4.0.0: + resolution: {integrity: sha512-3dOsAHXXUkQTpOYcoAxLIorMTp4gIQr5IW3iVb7A7lFIp0VHhnynm9izx6TssdrIcVIESAlVjtnO2K8bg+Coew==} + engines: {node: '>=12'} + dev: false - sockjs@0.3.24: + /sockjs@0.3.24: + resolution: {integrity: sha512-GJgLTZ7vYb/JtPSSZ10hsOYIvEYsjbNU+zPdIHcUaWVNUEPivzxku31865sSSud0Da0W4lEeOPlmw93zLQchuQ==} dependencies: faye-websocket: 0.11.4 uuid: 8.3.2 websocket-driver: 0.7.4 + dev: false - sort-css-media-queries@2.1.0: {} + /sort-css-media-queries@2.1.0: + resolution: {integrity: sha512-IeWvo8NkNiY2vVYdPa27MCQiR0MN0M80johAYFVxWWXQ44KU84WNxjslwBHmc/7ZL2ccwkM7/e6S5aiKZXm7jA==} + engines: {node: '>= 6.3.0'} + dev: false - source-map-js@1.2.0: {} + /source-map-js@1.2.0: + resolution: {integrity: sha512-itJW8lvSA0TXEphiRoawsCksnlf8SyvmFzIhltqAHluXd88pkCd+cXJVHTDwdCr0IzwptSm035IHQktUu1QUMg==} + engines: {node: '>=0.10.0'} + dev: false - source-map-support@0.5.21: + /source-map-support@0.5.21: + resolution: {integrity: sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==} dependencies: buffer-from: 1.1.2 source-map: 0.6.1 + dev: false - source-map@0.5.7: {} + /source-map@0.5.7: + resolution: {integrity: sha512-LbrmJOMUSdEVxIKvdcJzQC+nQhe8FUZQTXQy6+I75skNgn3OoQ0DZA8YnFa7gp8tqtL3KPf1kmo0R5DoApeSGQ==} + engines: {node: '>=0.10.0'} + dev: false - source-map@0.6.1: {} + /source-map@0.6.1: + resolution: {integrity: sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==} + engines: {node: '>=0.10.0'} + dev: false - space-separated-tokens@1.1.5: {} + /space-separated-tokens@1.1.5: + resolution: {integrity: sha512-q/JSVd1Lptzhf5bkYm4ob4iWPjx0KiRe3sRFBNrVqbJkFaBm5vbbowy1mymoPNLRa52+oadOhJ+K49wsSeSjTA==} + dev: false - spdy-transport@3.0.0: + /spdy-transport@3.0.0: + resolution: {integrity: sha512-hsLVFE5SjA6TCisWeJXFKniGGOpBgMLmerfO2aCyCU5s7nJ/rpAepqmFifv/GCbSbueEeAJJnmSQ2rKC/g8Fcw==} dependencies: debug: 4.3.6 detect-node: 2.1.0 @@ -10478,8 +8829,11 @@ snapshots: wbuf: 1.7.3 transitivePeerDependencies: - supports-color + dev: false - spdy@4.0.2: + /spdy@4.0.2: + resolution: {integrity: sha512-r46gZQZQV+Kl9oItvl1JZZqJKGr+oEkB08A6BzkiR7593/7IbtuncXHd2YoYeTsG4157ZssMu9KYvUHLcjcDoA==} + engines: {node: '>=6.0.0'} dependencies: debug: 4.3.6 handle-thing: 2.0.1 @@ -10488,107 +8842,182 @@ snapshots: spdy-transport: 3.0.0 transitivePeerDependencies: - supports-color + dev: false - sprintf-js@1.0.3: {} + /sprintf-js@1.0.3: + resolution: {integrity: sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==} + dev: false - stable@0.1.8: {} + /stable@0.1.8: + resolution: {integrity: sha512-ji9qxRnOVfcuLDySj9qzhGSEFVobyt1kIOSkj1qZzYLzq7Tos/oUUWvotUPQLlrsidqsK6tBH89Bc9kL5zHA6w==} + deprecated: 'Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility' + dev: false - state-toggle@1.0.3: {} + /state-toggle@1.0.3: + resolution: {integrity: sha512-d/5Z4/2iiCnHw6Xzghyhb+GcmF89bxwgXG60wjIiZaxnymbyOmI8Hk4VqHXiVVp6u2ysaskFfXg3ekCj4WNftQ==} + dev: false - statuses@1.5.0: {} + /statuses@1.5.0: + resolution: {integrity: sha512-OpZ3zP+jT1PI7I8nemJX4AKmAX070ZkYPVWV/AaKTJl+tXCTGyVdC1a4SL8RUQYEwk/f34ZX8UTykN68FwrqAA==} + engines: {node: '>= 0.6'} + dev: false - statuses@2.0.1: {} + /statuses@2.0.1: + resolution: {integrity: sha512-RwNA9Z/7PrK06rYLIzFMlaF+l73iwpzsqRIFgbMLbTcLD6cOao82TaWefPXQvB2fOC4AjuYSEndS7N/mTCbkdQ==} + engines: {node: '>= 0.8'} + dev: false - std-env@3.7.0: {} + /std-env@3.7.0: + resolution: {integrity: sha512-JPbdCEQLj1w5GilpiHAx3qJvFndqybBysA3qUOnznweH4QbNYUsW/ea8QzSrnh0vNsezMMw5bcVool8lM0gwzg==} + dev: false - string-width@4.2.3: + /string-width@4.2.3: + resolution: {integrity: sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==} + engines: {node: '>=8'} dependencies: emoji-regex: 8.0.0 is-fullwidth-code-point: 3.0.0 strip-ansi: 6.0.1 - string-width@5.1.2: + /string-width@5.1.2: + resolution: {integrity: sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==} + engines: {node: '>=12'} dependencies: eastasianwidth: 0.2.0 emoji-regex: 9.2.2 strip-ansi: 7.1.0 - string.prototype.trim@1.2.9: + /string.prototype.trim@1.2.9: + resolution: {integrity: sha512-klHuCNxiMZ8MlsOihJhJEBJAiMVqU3Z2nEXWfWnIqjN0gEFS9J9+IxKozWWtQGcgoa1WUZzLjKPTr4ZHNFTFxw==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 define-properties: 1.2.1 es-abstract: 1.23.3 es-object-atoms: 1.0.0 + dev: false - string.prototype.trimend@1.0.8: + /string.prototype.trimend@1.0.8: + resolution: {integrity: sha512-p73uL5VCHCO2BZZ6krwwQE3kCzM7NKmis8S//xEC6fQonchbum4eP6kR4DLEjQFO3Wnj3Fuo8NM0kOSjVdHjZQ==} dependencies: call-bind: 1.0.7 define-properties: 1.2.1 es-object-atoms: 1.0.0 + dev: false - string.prototype.trimstart@1.0.8: + /string.prototype.trimstart@1.0.8: + resolution: {integrity: sha512-UXSH262CSZY1tfu3G3Secr6uGLCFVPMhIqHjlgCUtCCcgihYc/xKs9djMTMUOb2j1mVSeU8EU6NWc/iQKU6Gfg==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 define-properties: 1.2.1 es-object-atoms: 1.0.0 + dev: false - string_decoder@1.1.1: + /string_decoder@1.1.1: + resolution: {integrity: sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==} dependencies: safe-buffer: 5.1.2 + dev: false - string_decoder@1.3.0: + /string_decoder@1.3.0: + resolution: {integrity: sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==} dependencies: safe-buffer: 5.2.1 + dev: false - stringify-object@3.3.0: + /stringify-object@3.3.0: + resolution: {integrity: sha512-rHqiFh1elqCQ9WPLIC8I0Q/g/wj5J1eMkyoiD6eoQApWHP0FtlK7rqnhmabL5VUY9JQCcqwwvlOaSuutekgyrw==} + engines: {node: '>=4'} dependencies: get-own-enumerable-property-symbols: 3.0.2 is-obj: 1.0.1 is-regexp: 1.0.0 + dev: false - strip-ansi@6.0.1: + /strip-ansi@6.0.1: + resolution: {integrity: sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==} + engines: {node: '>=8'} dependencies: ansi-regex: 5.0.1 - strip-ansi@7.1.0: + /strip-ansi@7.1.0: + resolution: {integrity: sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ==} + engines: {node: '>=12'} dependencies: ansi-regex: 6.0.1 - strip-bom-string@1.0.0: {} + /strip-bom-string@1.0.0: + resolution: {integrity: sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g==} + engines: {node: '>=0.10.0'} + dev: false - strip-final-newline@2.0.0: {} + /strip-final-newline@2.0.0: + resolution: {integrity: sha512-BrpvfNAE3dcvq7ll3xVumzjKjZQ5tI1sEUIKr3Uoks0XUl45St3FlatVqef9prk4jRDzhW6WZg+3bk93y6pLjA==} + engines: {node: '>=6'} + dev: false - strip-json-comments@2.0.1: {} + /strip-json-comments@2.0.1: + resolution: {integrity: sha512-4gB8na07fecVVkOI6Rs4e7T6NOTki5EmL7TUduTs6bu3EdnSycntVJ4re8kgZA+wx9IueI2Y11bfbgwtzuE0KQ==} + engines: {node: '>=0.10.0'} + dev: false - strip-json-comments@3.1.1: {} + /strip-json-comments@3.1.1: + resolution: {integrity: sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==} + engines: {node: '>=8'} - style-to-object@0.3.0: + /style-to-object@0.3.0: + resolution: {integrity: sha512-CzFnRRXhzWIdItT3OmF8SQfWyahHhjq3HwcMNCNLn+N7klOOqPjMeG/4JSu77D7ypZdGvSzvkrbyeTMizz2VrA==} dependencies: inline-style-parser: 0.1.1 + dev: false - stylehacks@5.1.1(postcss@8.4.41): + /stylehacks@5.1.1(postcss@8.4.41): + resolution: {integrity: sha512-sBpcd5Hx7G6seo7b1LkpttvTz7ikD0LlH5RmdcBNb6fFR0Fl7LQwHDFr300q4cwUqi+IYrFGmsIHieMBfnN/Bw==} + engines: {node: ^10 || ^12 || >=14.0} + peerDependencies: + postcss: ^8.2.15 dependencies: browserslist: 4.23.3 postcss: 8.4.41 postcss-selector-parser: 6.1.2 + dev: false - supports-color@5.5.0: + /supports-color@5.5.0: + resolution: {integrity: sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==} + engines: {node: '>=4'} dependencies: has-flag: 3.0.0 + dev: false - supports-color@7.2.0: + /supports-color@7.2.0: + resolution: {integrity: sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==} + engines: {node: '>=8'} dependencies: has-flag: 4.0.0 + dev: false - supports-color@8.1.1: + /supports-color@8.1.1: + resolution: {integrity: sha512-MpUEN2OodtUzxvKQl72cUF7RQ5EiHsGvSsVG0ia9c5RbWGL2CI4C7EpPS8UTBIplnlzZiNuV56w+FuNxy3ty2Q==} + engines: {node: '>=10'} dependencies: has-flag: 4.0.0 + dev: false - supports-preserve-symlinks-flag@1.0.0: {} + /supports-preserve-symlinks-flag@1.0.0: + resolution: {integrity: sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==} + engines: {node: '>= 0.4'} + dev: false - svg-parser@2.0.4: {} + /svg-parser@2.0.4: + resolution: {integrity: sha512-e4hG1hRwoOdRb37cIMSgzNsxyzKfayW6VOflrwvR+/bzrkyxY/31WkbgnQpgtrNp1SdpJvpUAGTa/ZoiPNDuRQ==} + dev: false - svgo@1.3.2: + /svgo@1.3.2: + resolution: {integrity: sha512-yhy/sQYxR5BkC98CY7o31VGsg014AKLEPxdfhora76l36hD9Rdy5NZA/Ocn6yayNPgSamYdtX2rFJdcv07AYVw==} + engines: {node: '>=4.0.0'} + deprecated: This SVGO version is no longer supported. Upgrade to v2.x.x. + hasBin: true dependencies: chalk: 2.4.2 coa: 2.0.2 @@ -10603,8 +9032,12 @@ snapshots: stable: 0.1.8 unquote: 1.1.1 util.promisify: 1.0.1 + dev: false - svgo@2.8.0: + /svgo@2.8.0: + resolution: {integrity: sha512-+N/Q9kV1+F+UeWYoSiULYo4xYSDQlTgb+ayMobAXPwMnLvop7oxKMo9OzIrX5x3eS4L4f2UHhc9axXwY8DpChg==} + engines: {node: '>=10.13.0'} + hasBin: true dependencies: '@trysound/sax': 0.2.0 commander: 7.2.0 @@ -10613,18 +9046,32 @@ snapshots: csso: 4.2.0 picocolors: 1.0.1 stable: 0.1.8 + dev: false - swc-loader@0.2.6(@swc/core@1.7.18)(webpack@5.94.0): + /swc-loader@0.2.6(@swc/core@1.7.18)(webpack@5.94.0): + resolution: {integrity: sha512-9Zi9UP2YmDpgmQVbyOPJClY0dwf58JDyDMQ7uRc4krmc72twNI2fvlBWHLqVekBpPc7h5NJkGVT1zNDxFrqhvg==} + peerDependencies: + '@swc/core': ^1.2.147 + webpack: '>=2' dependencies: '@swc/core': 1.7.18 '@swc/counter': 0.1.3 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - tapable@1.1.3: {} + /tapable@1.1.3: + resolution: {integrity: sha512-4WK/bYZmj8xLr+HUCODHGF1ZFzsYffasLUgEiMBY4fgtltdO6B4WJtlSbPaDTLpYTcGVwM2qLnFTICEcNxs3kA==} + engines: {node: '>=6'} + dev: false - tapable@2.2.1: {} + /tapable@2.2.1: + resolution: {integrity: sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ==} + engines: {node: '>=6'} + dev: false - tar@4.4.19: + /tar@4.4.19: + resolution: {integrity: sha512-a20gEsvHnWe0ygBY8JbxoM4w3SJdhc7ZAuxkLqh+nvNQN2IOt0B5lLgM490X5Hl8FF0dl0tOf2ewFYAlIFgzVA==} + engines: {node: '>=4.5'} dependencies: chownr: 1.1.4 fs-minipass: 1.2.7 @@ -10633,8 +9080,23 @@ snapshots: mkdirp: 0.5.6 safe-buffer: 5.2.1 yallist: 3.1.1 + dev: false - terser-webpack-plugin@5.3.10(@swc/core@1.7.18)(webpack@5.94.0): + /terser-webpack-plugin@5.3.10(@swc/core@1.7.18)(webpack@5.94.0): + resolution: {integrity: sha512-BKFPWlPDndPs+NGGCr1U59t0XScL5317Y0UReNrHaw9/FwhPENlq6bfgs+4yPfyP51vqC1bQ4rp1EfXW5ZSH9w==} + engines: {node: '>= 10.13.0'} + peerDependencies: + '@swc/core': '*' + esbuild: '*' + uglify-js: '*' + webpack: ^5.1.0 + peerDependenciesMeta: + '@swc/core': + optional: true + esbuild: + optional: true + uglify-js: + optional: true dependencies: '@jridgewell/trace-mapping': 0.3.25 '@swc/core': 1.7.18 @@ -10643,68 +9105,124 @@ snapshots: serialize-javascript: 6.0.2 terser: 5.31.6 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - terser@5.31.6: + /terser@5.31.6: + resolution: {integrity: sha512-PQ4DAriWzKj+qgehQ7LK5bQqCFNMmlhjR2PFFLuqGCpuCAauxemVBWwWOxo3UIwWQx8+Pr61Df++r76wDmkQBg==} + engines: {node: '>=10'} + hasBin: true dependencies: '@jridgewell/source-map': 0.3.6 acorn: 8.12.1 commander: 2.20.3 source-map-support: 0.5.21 + dev: false - text-table@0.2.0: {} + /text-table@0.2.0: + resolution: {integrity: sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==} + dev: false - thunky@1.1.0: {} + /thunky@1.1.0: + resolution: {integrity: sha512-eHY7nBftgThBqOyHGVN+l8gF0BucP09fMo0oO/Lb0w1OF80dJv+lDVpXG60WMQvkcxAkNybKsrEIE3ZtKGmPrA==} + dev: false - tiny-invariant@1.3.3: {} + /tiny-invariant@1.3.3: + resolution: {integrity: sha512-+FbBPE1o9QAYvviau/qC5SE3caw21q3xkvWKBtja5vgqOWIHHJ3ioaq1VPfn/Szqctz2bU/oYeKd9/z5BL+PVg==} + dev: false - tiny-warning@1.0.3: {} + /tiny-warning@1.0.3: + resolution: {integrity: sha512-lBN9zLN/oAf68o3zNXYrdCt1kP8WsiGW8Oo2ka41b2IM5JL/S1CTyX1rW0mb/zSuJun0ZUrDxx4sqvYS2FWzPA==} + dev: false - to-fast-properties@2.0.0: {} + /to-fast-properties@2.0.0: + resolution: {integrity: sha512-/OaKK0xYrs3DmxRYqL/yDc+FxFUVYhDlXMhRmv3z915w2HF1tnN1omB354j8VUGO/hbRzyD6Y3sA7v7GS/ceog==} + engines: {node: '>=4'} + dev: false - to-readable-stream@1.0.0: {} + /to-readable-stream@1.0.0: + resolution: {integrity: sha512-Iq25XBt6zD5npPhlLVXGFN3/gyR2/qODcKNNyTMd4vbm39HUaOiAM4PMq0eMVC/Tkxz+Zjdsc55g9yyz+Yq00Q==} + engines: {node: '>=6'} + dev: false - to-regex-range@5.0.1: + /to-regex-range@5.0.1: + resolution: {integrity: sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==} + engines: {node: '>=8.0'} dependencies: is-number: 7.0.0 + dev: false - toidentifier@1.0.1: {} + /toidentifier@1.0.1: + resolution: {integrity: sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA==} + engines: {node: '>=0.6'} + dev: false - totalist@3.0.1: {} + /totalist@3.0.1: + resolution: {integrity: sha512-sf4i37nQ2LBx4m3wB74y+ubopq6W/dIzXg0FDGjsYnZHVa1Da8FH853wlL2gtUhg+xJXjfk3kUZS3BRoQeoQBQ==} + engines: {node: '>=6'} + dev: false - tr46@0.0.3: {} + /tr46@0.0.3: + resolution: {integrity: sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw==} + dev: false - trim-trailing-lines@1.1.4: {} + /trim-trailing-lines@1.1.4: + resolution: {integrity: sha512-rjUWSqnfTNrjbB9NQWfPMH/xRK1deHeGsHoVfpxJ++XeYXE0d6B1En37AHfw3jtfTU7dzMzZL2jjpe8Qb5gLIQ==} + dev: false - trim@0.0.1: {} + /trim@0.0.1: + resolution: {integrity: sha512-YzQV+TZg4AxpKxaTHK3c3D+kRDCGVEE7LemdlQZoQXn0iennk10RsIoY6ikzAqJTc9Xjl9C1/waHom/J86ziAQ==} + deprecated: Use String.prototype.trim() instead + dev: false - trough@1.0.5: {} + /trough@1.0.5: + resolution: {integrity: sha512-rvuRbTarPXmMb79SmzEp8aqXNKcK+y0XaB298IXueQ8I2PsrATcPBCSPyK/dDNa2iWOhKlfNnOjdAOTBU/nkFA==} + dev: false - tslib@2.7.0: {} + /tslib@2.7.0: + resolution: {integrity: sha512-gLXCKdN1/j47AiHiOkJN69hJmcbGTHI0ImLmbYLHykhgeN0jVGola9yVjFgzCUklsZQMW55o+dW7IXv3RCXDzA==} + dev: false - type-fest@0.20.2: {} + /type-fest@0.20.2: + resolution: {integrity: sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ==} + engines: {node: '>=10'} + dev: false - type-fest@2.19.0: {} + /type-fest@2.19.0: + resolution: {integrity: sha512-RAH822pAdBgcNMAfWnCBU3CFZcfZ/i1eZjwFU/dsLKumyuuP3niueg2UAukXYF0E2AAoc82ZSSf9J0WQBinzHA==} + engines: {node: '>=12.20'} + dev: false - type-is@1.6.18: + /type-is@1.6.18: + resolution: {integrity: sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g==} + engines: {node: '>= 0.6'} dependencies: media-typer: 0.3.0 mime-types: 2.1.35 + dev: false - typed-array-buffer@1.0.2: + /typed-array-buffer@1.0.2: + resolution: {integrity: sha512-gEymJYKZtKXzzBzM4jqa9w6Q1Jjm7x2d+sh19AdsD4wqnMPDYyvwpsIc2Q/835kHuo3BEQ7CjelGhfTsoBb2MQ==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 es-errors: 1.3.0 is-typed-array: 1.1.13 + dev: false - typed-array-byte-length@1.0.1: + /typed-array-byte-length@1.0.1: + resolution: {integrity: sha512-3iMJ9q0ao7WE9tWcaYKIptkNBuOIcZCCT0d4MRvuuH88fEoEH62IuQe0OtraD3ebQEoTRk8XCBoknUNc1Y67pw==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 for-each: 0.3.3 gopd: 1.0.1 has-proto: 1.0.3 is-typed-array: 1.1.13 + dev: false - typed-array-byte-offset@1.0.2: + /typed-array-byte-offset@1.0.2: + resolution: {integrity: sha512-Ous0vodHa56FviZucS2E63zkgtgrACj7omjwd/8lTEMEPFFyjfixMZ1ZXenpgCFBBt4EC1J2XsyVS2gkG0eTFA==} + engines: {node: '>= 0.4'} dependencies: available-typed-arrays: 1.0.7 call-bind: 1.0.7 @@ -10712,8 +9230,11 @@ snapshots: gopd: 1.0.1 has-proto: 1.0.3 is-typed-array: 1.1.13 + dev: false - typed-array-length@1.0.6: + /typed-array-length@1.0.6: + resolution: {integrity: sha512-/OxDN6OtAk5KBpGb28T+HZc2M+ADtvRxXrKKbUwtsLgdoxgX13hyy7ek6bFRl5+aBs2yZzB0c4CnQfAtVypW/g==} + engines: {node: '>= 0.4'} dependencies: call-bind: 1.0.7 for-each: 0.3.3 @@ -10721,16 +9242,30 @@ snapshots: has-proto: 1.0.3 is-typed-array: 1.1.13 possible-typed-array-names: 1.0.0 + dev: false - typedarray-to-buffer@3.1.5: + /typedarray-to-buffer@3.1.5: + resolution: {integrity: sha512-zdu8XMNEDepKKR+XYOXAVPtWui0ly0NtohUscw+UmaHiAWT8hrV1rr//H6V+0DvJ3OQ19S979M0laLfX8rm82Q==} dependencies: is-typedarray: 1.0.0 + dev: false - typescript@5.5.4: {} + /typescript@5.5.4: + resolution: {integrity: sha512-Mtq29sKDAEYP7aljRgtPOpTvOfbwRWlS6dPRzwjdE+C0R4brX/GUyhHSecbHMFLNBLcJIPt9nl9yG5TZ1weH+Q==} + engines: {node: '>=14.17'} + hasBin: true + dev: false - typesense-docsearch-css@0.3.0: {} + /typesense-docsearch-css@0.3.0: + resolution: {integrity: sha512-+/t9Jz5dwH52Xpk9ikpJaQZs+McX/a4aY+8Iw+IiD9yu9+JJddEA5RYjBgkcQ140gUtp9L213z/V0g2bC3B/hw==} + dev: false - typesense-docsearch-react@0.2.3(@algolia/client-search@4.24.0)(@babel/runtime@7.25.4)(@types/react@18.3.4)(algoliasearch@4.24.0)(react-dom@17.0.2)(react@17.0.2): + /typesense-docsearch-react@0.2.3(@algolia/client-search@4.24.0)(@babel/runtime@7.25.4)(@types/react@18.3.4)(algoliasearch@4.24.0)(react-dom@17.0.2)(react@17.0.2): + resolution: {integrity: sha512-2eODhYFk3KLhwEF+shzcTsiB0zU8GefPFZGzNlGdwdUJiUxjh8SgS7VtylXGdKQZxh33wbWN4wr94CG2WxcIIw==} + peerDependencies: + '@types/react': '>= 16.8.0 < 19.0.0' + react: '>= 16.8.0 < 19.0.0' + react-dom: '>= 16.8.0 < 19.0.0' dependencies: '@algolia/autocomplete-core': 1.7.1 '@algolia/autocomplete-preset-algolia': 1.7.1(@algolia/client-search@4.24.0)(algoliasearch@4.24.0) @@ -10745,54 +9280,92 @@ snapshots: - '@babel/runtime' - algoliasearch - debug + dev: false - typesense-instantsearch-adapter@2.8.0(@babel/runtime@7.25.4): + /typesense-instantsearch-adapter@2.8.0(@babel/runtime@7.25.4): + resolution: {integrity: sha512-2q4QVpHoUV0ncf1XOqIC0dufOTkFRxQ0mHzg//H3WK02ZYqdNNPCAacZODhQlltl1cNJdTI8Y4uuGVd6fJuGzw==} + engines: {node: '>=16'} + requiresBuild: true + peerDependencies: + '@babel/runtime': ^7.17.2 dependencies: '@babel/runtime': 7.25.4 typesense: 1.8.2(@babel/runtime@7.25.4) transitivePeerDependencies: - debug + dev: false - typesense@1.8.2(@babel/runtime@7.25.4): + /typesense@1.8.2(@babel/runtime@7.25.4): + resolution: {integrity: sha512-aBpePjA99Qvo+OP2pJwMpvga4Jrm1Y2oV5NsrWXBxlqUDNEUCPZBIksPv2Hq0jxQxHhLLyJVbjXjByXsvpCDVA==} + engines: {node: '>=18'} + peerDependencies: + '@babel/runtime': ^7.23.2 dependencies: '@babel/runtime': 7.25.4 axios: 1.7.5 loglevel: 1.9.1 transitivePeerDependencies: - debug + dev: false - ua-parser-js@1.0.38: {} + /ua-parser-js@1.0.38: + resolution: {integrity: sha512-Aq5ppTOfvrCMgAPneW1HfWj66Xi7XL+/mIy996R1/CLS/rcyJQm6QZdsKrUeivDFQ+Oc9Wyuwor8Ze8peEoUoQ==} + dev: false - uc.micro@1.0.6: {} + /uc.micro@1.0.6: + resolution: {integrity: sha512-8Y75pvTYkLJW2hWQHXxoqRgV7qb9B+9vFEtidML+7koHUFapnVJAZ6cKs+Qjz5Aw3aZWHMC6u0wJE3At+nSGwA==} + dev: true - unbox-primitive@1.0.2: + /unbox-primitive@1.0.2: + resolution: {integrity: sha512-61pPlCD9h51VoreyJ0BReideM3MDKMKnh6+V9L08331ipq6Q8OFXZYiqP6n/tbHx4s5I9uRhcye6BrbkizkBDw==} dependencies: call-bind: 1.0.7 has-bigints: 1.0.2 has-symbols: 1.0.3 which-boxed-primitive: 1.0.2 + dev: false - undici-types@6.19.8: {} + /undici-types@6.19.8: + resolution: {integrity: sha512-ve2KP6f/JnbPBFyobGHuerC9g1FYGn/F8n1LWTwNxCEzd6IfqTwUQcNXgEtmmQ6DlRrC1hrSrBnCZPokRrDHjw==} + dev: false - undici@6.19.8: {} + /undici@6.19.8: + resolution: {integrity: sha512-U8uCCl2x9TK3WANvmBavymRzxbfFYG+tAu+fgx3zxQy3qdagQqBLwJVrdyO1TBfUXvfKveMKJZhpvUYoOjM+4g==} + engines: {node: '>=18.17'} + dev: false - unherit@1.1.3: + /unherit@1.1.3: + resolution: {integrity: sha512-Ft16BJcnapDKp0+J/rqFC3Rrk6Y/Ng4nzsC028k2jdDII/rdZ7Wd3pPT/6+vIIxRagwRc9K0IUX0Ra4fKvw+WQ==} dependencies: inherits: 2.0.4 xtend: 4.0.2 + dev: false - unicode-canonical-property-names-ecmascript@2.0.0: {} + /unicode-canonical-property-names-ecmascript@2.0.0: + resolution: {integrity: sha512-yY5PpDlfVIU5+y/BSCxAJRBIS1Zc2dDG3Ujq+sR0U+JjUevW2JhocOF+soROYDSaAezOzOKuyyixhD6mBknSmQ==} + engines: {node: '>=4'} + dev: false - unicode-match-property-ecmascript@2.0.0: + /unicode-match-property-ecmascript@2.0.0: + resolution: {integrity: sha512-5kaZCrbp5mmbz5ulBkDkbY0SsPOjKqVS35VpL9ulMPfSl0J0Xsm+9Evphv9CoIZFwre7aJoa94AY6seMKGVN5Q==} + engines: {node: '>=4'} dependencies: unicode-canonical-property-names-ecmascript: 2.0.0 unicode-property-aliases-ecmascript: 2.1.0 + dev: false - unicode-match-property-value-ecmascript@2.1.0: {} + /unicode-match-property-value-ecmascript@2.1.0: + resolution: {integrity: sha512-qxkjQt6qjg/mYscYMC0XKRn3Rh0wFPlfxB0xkt9CfyTvpX1Ra0+rAmdX2QyAobptSEvuy4RtpPRui6XkV+8wjA==} + engines: {node: '>=4'} + dev: false - unicode-property-aliases-ecmascript@2.1.0: {} + /unicode-property-aliases-ecmascript@2.1.0: + resolution: {integrity: sha512-6t3foTQI9qne+OZoVQB/8x8rk2k1eVy1gRXhV3oFQ5T6R1dqQ1xtin3XqSlx3+ATBkliTaR/hHyJBm+LVPNM8w==} + engines: {node: '>=4'} + dev: false - unified@9.2.0: + /unified@9.2.0: + resolution: {integrity: sha512-vx2Z0vY+a3YoTj8+pttM3tiJHCwY5UFbYdiWrwBEbHmK8pvsPj2rtAX2BFfgXen8T39CJWblWRDT4L5WGXtDdg==} dependencies: '@types/unist': 2.0.11 bail: 1.0.5 @@ -10801,8 +9374,10 @@ snapshots: is-plain-obj: 2.1.0 trough: 1.0.5 vfile: 4.2.1 + dev: false - unified@9.2.2: + /unified@9.2.2: + resolution: {integrity: sha512-Sg7j110mtefBD+qunSLO1lqOEKdrwBFBrR6Qd8f4uwkhWNlbkaqwHse6e7QvD3AP/MNoJdEDLaf8OxYyoWgorQ==} dependencies: '@types/unist': 2.0.11 bail: 1.0.5 @@ -10811,55 +9386,92 @@ snapshots: is-plain-obj: 2.1.0 trough: 1.0.5 vfile: 4.2.1 + dev: false - unique-string@2.0.0: + /unique-string@2.0.0: + resolution: {integrity: sha512-uNaeirEPvpZWSgzwsPGtU2zVSTrn/8L5q/IexZmH0eH6SA73CmAA5U4GwORTxQAZs95TAXLNqeLoPPNO5gZfWg==} + engines: {node: '>=8'} dependencies: crypto-random-string: 2.0.0 + dev: false - unist-builder@2.0.3: {} + /unist-builder@2.0.3: + resolution: {integrity: sha512-f98yt5pnlMWlzP539tPc4grGMsFaQQlP/vM396b00jngsiINumNmsY8rkXjfoi1c6QaM8nQ3vaGDuoKWbe/1Uw==} + dev: false - unist-util-generated@1.1.6: {} + /unist-util-generated@1.1.6: + resolution: {integrity: sha512-cln2Mm1/CZzN5ttGK7vkoGw+RZ8VcUH6BtGbq98DDtRGquAAOXig1mrBQYelOwMXYS8rK+vZDyyojSjp7JX+Lg==} + dev: false - unist-util-is@4.1.0: {} + /unist-util-is@4.1.0: + resolution: {integrity: sha512-ZOQSsnce92GrxSqlnEEseX0gi7GH9zTJZ0p9dtu87WRb/37mMPO2Ilx1s/t9vBHrFhbgweUwb+t7cIn5dxPhZg==} + dev: false - unist-util-position@3.1.0: {} + /unist-util-position@3.1.0: + resolution: {integrity: sha512-w+PkwCbYSFw8vpgWD0v7zRCl1FpY3fjDSQ3/N/wNd9Ffa4gPi8+4keqt99N3XW6F99t/mUzp2xAhNmfKWp95QA==} + dev: false - unist-util-remove-position@2.0.1: + /unist-util-remove-position@2.0.1: + resolution: {integrity: sha512-fDZsLYIe2uT+oGFnuZmy73K6ZxOPG/Qcm+w7jbEjaFcJgbQ6cqjs/eSPzXhsmGpAsWPkqZM9pYjww5QTn3LHMA==} dependencies: unist-util-visit: 2.0.3 + dev: false - unist-util-remove@2.1.0: + /unist-util-remove@2.1.0: + resolution: {integrity: sha512-J8NYPyBm4baYLdCbjmf1bhPu45Cr1MWTm77qd9istEkzWpnN6O9tMsEbB2JhNnBCqGENRqEWomQ+He6au0B27Q==} dependencies: unist-util-is: 4.1.0 + dev: false - unist-util-stringify-position@2.0.3: + /unist-util-stringify-position@2.0.3: + resolution: {integrity: sha512-3faScn5I+hy9VleOq/qNbAd6pAx7iH5jYBMS9I1HgQVijz/4mv5Bvw5iw1sC/90CODiKo81G/ps8AJrISn687g==} dependencies: '@types/unist': 2.0.11 + dev: false - unist-util-visit-parents@3.1.1: + /unist-util-visit-parents@3.1.1: + resolution: {integrity: sha512-1KROIZWo6bcMrZEwiH2UrXDyalAa0uqzWCxCJj6lPOvTve2WkfgCytoDTPaMnodXh1WrXOq0haVYHj99ynJlsg==} dependencies: '@types/unist': 2.0.11 unist-util-is: 4.1.0 + dev: false - unist-util-visit@2.0.3: + /unist-util-visit@2.0.3: + resolution: {integrity: sha512-iJ4/RczbJMkD0712mGktuGpm/U4By4FfDonL7N/9tATGIF4imikjOuagyMY53tnZq3NP6BcmlrHhEKAfGWjh7Q==} dependencies: '@types/unist': 2.0.11 unist-util-is: 4.1.0 unist-util-visit-parents: 3.1.1 + dev: false - universalify@2.0.1: {} + /universalify@2.0.1: + resolution: {integrity: sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==} + engines: {node: '>= 10.0.0'} + dev: false - unpipe@1.0.0: {} + /unpipe@1.0.0: + resolution: {integrity: sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ==} + engines: {node: '>= 0.8'} + dev: false - unquote@1.1.1: {} + /unquote@1.1.1: + resolution: {integrity: sha512-vRCqFv6UhXpWxZPyGDh/F3ZpNv8/qo7w6iufLpQg9aKnQ71qM4B5KiI7Mia9COcjEhrO9LueHpMYjYzsWH3OIg==} + dev: false - update-browserslist-db@1.1.0(browserslist@4.23.3): + /update-browserslist-db@1.1.0(browserslist@4.23.3): + resolution: {integrity: sha512-EdRAaAyk2cUE1wOf2DkEhzxqOQvFOoRJFNS6NeyJ01Gp2beMRpBAINjM2iDXE3KCuKhwnvHIQCJm6ThL2Z+HzQ==} + hasBin: true + peerDependencies: + browserslist: '>= 4.21.0' dependencies: browserslist: 4.23.3 escalade: 3.1.2 picocolors: 1.0.1 + dev: false - update-notifier@5.1.0: + /update-notifier@5.1.0: + resolution: {integrity: sha512-ItnICHbeMh9GqUy31hFPrD1kcuZ3rpxDZbf4KUDavXwS0bW5m7SLbDQpGX3UYr072cbrF5hFUs3r5tUsPwjfHw==} + engines: {node: '>=10'} dependencies: boxen: 5.1.2 chalk: 4.1.2 @@ -10875,74 +9487,138 @@ snapshots: semver: 7.6.3 semver-diff: 3.1.1 xdg-basedir: 4.0.0 + dev: false - uri-js@4.4.1: + /uri-js@4.4.1: + resolution: {integrity: sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==} dependencies: punycode: 2.3.1 + dev: false - url-loader@4.1.1(file-loader@6.2.0)(webpack@5.94.0): + /url-loader@4.1.1(file-loader@6.2.0)(webpack@5.94.0): + resolution: {integrity: sha512-3BTV812+AVHHOJQO8O5MkWgZ5aosP7GnROJwvzLS9hWDj00lZ6Z0wNak423Lp9PBZN05N+Jk/N5Si8jRAlGyWA==} + engines: {node: '>= 10.13.0'} + peerDependencies: + file-loader: '*' + webpack: ^4.0.0 || ^5.0.0 + peerDependenciesMeta: + file-loader: + optional: true dependencies: file-loader: 6.2.0(webpack@5.94.0) loader-utils: 2.0.4 mime-types: 2.1.35 schema-utils: 3.3.0 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - url-parse-lax@3.0.0: + /url-parse-lax@3.0.0: + resolution: {integrity: sha512-NjFKA0DidqPa5ciFcSrXnAltTtzz84ogy+NebPvfEgAck0+TNg4UJ4IN+fB7zRZfbgUf0syOo9MDxFkDSMuFaQ==} + engines: {node: '>=4'} dependencies: prepend-http: 2.0.0 + dev: false - use-composed-ref@1.3.0(react@17.0.2): + /use-composed-ref@1.3.0(react@17.0.2): + resolution: {integrity: sha512-GLMG0Jc/jiKov/3Ulid1wbv3r54K9HlMW29IWcDFPEqFkSO2nS0MuefWgMJpeHQ9YJeXDL3ZUF+P3jdXlZX/cQ==} + peerDependencies: + react: ^16.8.0 || ^17.0.0 || ^18.0.0 dependencies: react: 17.0.2 + dev: false - use-isomorphic-layout-effect@1.1.2(@types/react@18.3.4)(react@17.0.2): + /use-isomorphic-layout-effect@1.1.2(@types/react@18.3.4)(react@17.0.2): + resolution: {integrity: sha512-49L8yCO3iGT/ZF9QttjwLF/ZD9Iwto5LnH5LmEdk/6cFmXddqi2ulF0edxTwjj+7mqvpVVGQWvbXZdn32wRSHA==} + peerDependencies: + '@types/react': '*' + react: ^16.8.0 || ^17.0.0 || ^18.0.0 + peerDependenciesMeta: + '@types/react': + optional: true dependencies: '@types/react': 18.3.4 react: 17.0.2 + dev: false - use-latest@1.2.1(@types/react@18.3.4)(react@17.0.2): + /use-latest@1.2.1(@types/react@18.3.4)(react@17.0.2): + resolution: {integrity: sha512-xA+AVm/Wlg3e2P/JiItTziwS7FK92LWrDB0p+hgXloIMuVCeJJ8v6f0eeHyPZaJrM+usM1FkFfbNCrJGs8A/zw==} + peerDependencies: + '@types/react': '*' + react: ^16.8.0 || ^17.0.0 || ^18.0.0 + peerDependenciesMeta: + '@types/react': + optional: true dependencies: '@types/react': 18.3.4 react: 17.0.2 use-isomorphic-layout-effect: 1.1.2(@types/react@18.3.4)(react@17.0.2) + dev: false - util-deprecate@1.0.2: {} + /util-deprecate@1.0.2: + resolution: {integrity: sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==} + dev: false - util.promisify@1.0.1: + /util.promisify@1.0.1: + resolution: {integrity: sha512-g9JpC/3He3bm38zsLupWryXHoEcS22YHthuPQSJdMy6KNrzIRzWqcsHzD/WUnqe45whVou4VIsPew37DoXWNrA==} dependencies: define-properties: 1.2.1 es-abstract: 1.23.3 has-symbols: 1.0.3 object.getownpropertydescriptors: 2.1.8 + dev: false - utila@0.4.0: {} + /utila@0.4.0: + resolution: {integrity: sha512-Z0DbgELS9/L/75wZbro8xAnT50pBVFQZ+hUEueGDU5FN51YSCYM+jdxsfCiHjwNP/4LCDD0i/graKpeBnOXKRA==} + dev: false - utility-types@3.11.0: {} + /utility-types@3.11.0: + resolution: {integrity: sha512-6Z7Ma2aVEWisaL6TvBCy7P8rm2LQoPv6dJ7ecIaIixHcwfbJ0x7mWdbcwlIM5IGQxPZSFYeqRCqlOOeKoJYMkw==} + engines: {node: '>= 4'} + dev: false - utils-merge@1.0.1: {} + /utils-merge@1.0.1: + resolution: {integrity: sha512-pMZTvIkT1d+TFGvDOqodOclx0QWkkgi6Tdoa8gC8ffGAAqz9pzPTZWAybbsHHoED/ztMtkv/VoYTYyShUn81hA==} + engines: {node: '>= 0.4.0'} + dev: false - uuid@8.3.2: {} + /uuid@8.3.2: + resolution: {integrity: sha512-+NYs2QeMWy+GWFOEm9xnn6HCDp0l7QBD7ml8zLUmJ+93Q5NF0NocErnwkTkXVFNiX3/fpC6afS8Dhb/gz7R7eg==} + hasBin: true + dev: false - value-equal@1.0.1: {} + /value-equal@1.0.1: + resolution: {integrity: sha512-NOJ6JZCAWr0zlxZt+xqCHNTEKOsrks2HQd4MqhP1qy4z1SkbEP467eNx6TgDKXMvUOb+OENfJCZwM+16n7fRfw==} + dev: false - vary@1.1.2: {} + /vary@1.1.2: + resolution: {integrity: sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg==} + engines: {node: '>= 0.8'} + dev: false - vfile-location@3.2.0: {} + /vfile-location@3.2.0: + resolution: {integrity: sha512-aLEIZKv/oxuCDZ8lkJGhuhztf/BW4M+iHdCwglA/eWc+vtuRFJj8EtgceYFX4LRjOhCAAiNHsKGssC6onJ+jbA==} + dev: false - vfile-message@2.0.4: + /vfile-message@2.0.4: + resolution: {integrity: sha512-DjssxRGkMvifUOJre00juHoP9DPWuzjxKuMDrhNbk2TdaYYBNMStsNhEOt3idrtI12VQYM/1+iM0KOzXi4pxwQ==} dependencies: '@types/unist': 2.0.11 unist-util-stringify-position: 2.0.3 + dev: false - vfile@4.2.1: + /vfile@4.2.1: + resolution: {integrity: sha512-O6AE4OskCG5S1emQ/4gl8zK586RqA3srz3nfK/Viy0UPToBc5Trp9BVFb1u0CjsKrAWwnpr4ifM/KBXPWwJbCA==} dependencies: '@types/unist': 2.0.11 is-buffer: 2.0.5 unist-util-stringify-position: 2.0.3 vfile-message: 2.0.4 + dev: false - wait-on@6.0.1: + /wait-on@6.0.1: + resolution: {integrity: sha512-zht+KASY3usTY5u2LgaNqn/Cd8MukxLGjdcZxT2ns5QzDmTFc4XoWBgC+C/na+sMRZTuVygQoMYwdcVjHnYIVw==} + engines: {node: '>=10.0.0'} + hasBin: true dependencies: axios: 0.25.0 joi: 17.13.3 @@ -10951,21 +9627,34 @@ snapshots: rxjs: 7.8.1 transitivePeerDependencies: - debug + dev: false - watchpack@2.4.2: + /watchpack@2.4.2: + resolution: {integrity: sha512-TnbFSbcOCcDgjZ4piURLCbJ3nJhznVh9kw6F6iokjiFPl8ONxe9A6nMDVXDiNbrSfLILs6vB07F7wLBrwPYzJw==} + engines: {node: '>=10.13.0'} dependencies: glob-to-regexp: 0.4.1 graceful-fs: 4.2.11 + dev: false - wbuf@1.7.3: + /wbuf@1.7.3: + resolution: {integrity: sha512-O84QOnr0icsbFGLS0O3bI5FswxzRr8/gHwWkDlQFskhSPryQXvrTMxjxGP4+iWYoauLoBvfDpkrOauZ+0iZpDA==} dependencies: minimalistic-assert: 1.0.1 + dev: false - web-namespaces@1.1.4: {} + /web-namespaces@1.1.4: + resolution: {integrity: sha512-wYxSGajtmoP4WxfejAPIr4l0fVh+jeMXZb08wNc0tMg6xsfZXj3cECqIK0G7ZAqUq0PP8WlMDtaOGVBTAWztNw==} + dev: false - webidl-conversions@3.0.1: {} + /webidl-conversions@3.0.1: + resolution: {integrity: sha512-2JAn3z8AR6rjK8Sm8orRC0h/bcl/DqL7tRPdGZ4I1CjdF+EaMLmYxBHyXuKL849eucPFhvBoxMsflfOb8kxaeQ==} + dev: false - webpack-bundle-analyzer@4.10.2: + /webpack-bundle-analyzer@4.10.2: + resolution: {integrity: sha512-vJptkMm9pk5si4Bv922ZbKLV8UTT4zib4FPgXMhgzUny0bfDDkLXAVQs3ly3fS4/TN9ROFtb0NFrm04UXFE/Vw==} + engines: {node: '>= 10.13.0'} + hasBin: true dependencies: '@discoveryjs/json-ext': 0.5.7 acorn: 8.12.1 @@ -10982,8 +9671,13 @@ snapshots: transitivePeerDependencies: - bufferutil - utf-8-validate + dev: false - webpack-dev-middleware@5.3.4(webpack@5.94.0): + /webpack-dev-middleware@5.3.4(webpack@5.94.0): + resolution: {integrity: sha512-BVdTqhhs+0IfoeAf7EoH5WE+exCmqGerHfDM0IL096Px60Tq2Mn9MAbnaGUe6HiMa41KMCYF19gyzZmBcq/o4Q==} + engines: {node: '>= 12.13.0'} + peerDependencies: + webpack: ^4.0.0 || ^5.0.0 dependencies: colorette: 2.0.20 memfs: 3.5.3 @@ -10991,8 +9685,20 @@ snapshots: range-parser: 1.2.1 schema-utils: 4.2.0 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - webpack-dev-server@4.15.2(webpack@5.94.0): + /webpack-dev-server@4.15.2(webpack@5.94.0): + resolution: {integrity: sha512-0XavAZbNJ5sDrCbkpWL8mia0o5WPOd2YGtxrEiZkBK9FjLppIUK2TgxK6qGD2P3hUXTJNNPVibrerKcx5WkR1g==} + engines: {node: '>= 12.13.0'} + hasBin: true + peerDependencies: + webpack: ^4.37.0 || ^5.0.0 + webpack-cli: '*' + peerDependenciesMeta: + webpack: + optional: true + webpack-cli: + optional: true dependencies: '@types/bonjour': 3.5.13 '@types/connect-history-api-fallback': 1.5.4 @@ -11030,16 +9736,31 @@ snapshots: - debug - supports-color - utf-8-validate + dev: false - webpack-merge@5.10.0: + /webpack-merge@5.10.0: + resolution: {integrity: sha512-+4zXKdx7UnO+1jaN4l2lHVD+mFvnlZQP/6ljaJVb4SZiwIKeUnrT5l0gkT8z+n4hKpC+jpOv6O9R+gLtag7pSA==} + engines: {node: '>=10.0.0'} dependencies: clone-deep: 4.0.1 flat: 5.0.2 wildcard: 2.0.1 + dev: false - webpack-sources@3.2.3: {} + /webpack-sources@3.2.3: + resolution: {integrity: sha512-/DyMEOrDgLKKIG0fmvtz+4dUX/3Ghozwgm6iPp8KRhvn+eQf9+Q7GWxVNMk3+uCPWfdXYC4ExGBckIXdFEfH1w==} + engines: {node: '>=10.13.0'} + dev: false - webpack@5.94.0(@swc/core@1.7.18): + /webpack@5.94.0(@swc/core@1.7.18): + resolution: {integrity: sha512-KcsGn50VT+06JH/iunZJedYGUJS5FGjow8wb9c0v5n1Om8O1g4L6LjtfxwlXIATopoQu+vOXXa7gYisWxCoPyg==} + engines: {node: '>=10.13.0'} + hasBin: true + peerDependencies: + webpack-cli: '*' + peerDependenciesMeta: + webpack-cli: + optional: true dependencies: '@types/estree': 1.0.5 '@webassemblyjs/ast': 1.12.1 @@ -11068,110 +9789,200 @@ snapshots: - '@swc/core' - esbuild - uglify-js + dev: false - webpackbar@5.0.2(webpack@5.94.0): + /webpackbar@5.0.2(webpack@5.94.0): + resolution: {integrity: sha512-BmFJo7veBDgQzfWXl/wwYXr/VFus0614qZ8i9znqcl9fnEdiVkdbi0TedLQ6xAK92HZHDJ0QmyQ0fmuZPAgCYQ==} + engines: {node: '>=12'} + peerDependencies: + webpack: 3 || 4 || 5 dependencies: chalk: 4.1.2 consola: 2.15.3 pretty-time: 1.1.0 std-env: 3.7.0 webpack: 5.94.0(@swc/core@1.7.18) + dev: false - websocket-driver@0.7.4: + /websocket-driver@0.7.4: + resolution: {integrity: sha512-b17KeDIQVjvb0ssuSDF2cYXSg2iztliJ4B9WdsuB6J952qCPKmnVq4DyW5motImXHDC1cBT/1UezrJVsKw5zjg==} + engines: {node: '>=0.8.0'} dependencies: http-parser-js: 0.5.8 safe-buffer: 5.2.1 websocket-extensions: 0.1.4 + dev: false - websocket-extensions@0.1.4: {} + /websocket-extensions@0.1.4: + resolution: {integrity: sha512-OqedPIGOfsDlo31UNwYbCFMSaO9m9G/0faIHj5/dZFDMFqPTcx6UwqyOy3COEaEOg/9VsGIpdqn62W5KhoKSpg==} + engines: {node: '>=0.8.0'} + dev: false - whatwg-encoding@3.1.1: + /whatwg-encoding@3.1.1: + resolution: {integrity: sha512-6qN4hJdMwfYBtE3YBTTHhoeuUrDBPZmbQaxWAqSALV/MeEnR5z1xd8UKud2RAkFoPkmB+hli1TZSnyi84xz1vQ==} + engines: {node: '>=18'} dependencies: iconv-lite: 0.6.3 + dev: false - whatwg-mimetype@4.0.0: {} + /whatwg-mimetype@4.0.0: + resolution: {integrity: sha512-QaKxh0eNIi2mE9p2vEdzfagOKHCcj1pJ56EEHGQOVxp8r9/iszLUUV7v89x9O1p/T+NlTM5W7jW6+cz4Fq1YVg==} + engines: {node: '>=18'} + dev: false - whatwg-url@5.0.0: + /whatwg-url@5.0.0: + resolution: {integrity: sha512-saE57nupxk6v3HY35+jzBwYa0rKSy0XR8JSxZPwgLr7ys0IBzhGviA1/TUGJLmSVqs8pb9AnvICXEuOHLprYTw==} dependencies: tr46: 0.0.3 webidl-conversions: 3.0.1 + dev: false - which-boxed-primitive@1.0.2: + /which-boxed-primitive@1.0.2: + resolution: {integrity: sha512-bwZdv0AKLpplFY2KZRX6TvyuN7ojjr7lwkg6ml0roIy9YeuSr7JS372qlNW18UQYzgYK9ziGcerWqZOmEn9VNg==} dependencies: is-bigint: 1.0.4 is-boolean-object: 1.1.2 is-number-object: 1.0.7 is-string: 1.0.7 is-symbol: 1.0.4 + dev: false - which-typed-array@1.1.15: + /which-typed-array@1.1.15: + resolution: {integrity: sha512-oV0jmFtUky6CXfkqehVvBP/LSWJ2sy4vWMioiENyJLePrBO/yKyV9OyJySfAKosh+RYkIl5zJCNZ8/4JncrpdA==} + engines: {node: '>= 0.4'} dependencies: available-typed-arrays: 1.0.7 call-bind: 1.0.7 for-each: 0.3.3 gopd: 1.0.1 has-tostringtag: 1.0.2 + dev: false - which@1.3.1: + /which@1.3.1: + resolution: {integrity: sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==} + hasBin: true dependencies: isexe: 2.0.0 + dev: false - which@2.0.2: + /which@2.0.2: + resolution: {integrity: sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==} + engines: {node: '>= 8'} + hasBin: true dependencies: isexe: 2.0.0 - widest-line@3.1.0: + /widest-line@3.1.0: + resolution: {integrity: sha512-NsmoXalsWVDMGupxZ5R08ka9flZjjiLvHVAWYOKtiKM8ujtZWr9cRffak+uSE48+Ob8ObalXpwyeUiyDD6QFgg==} + engines: {node: '>=8'} dependencies: string-width: 4.2.3 + dev: false - widest-line@4.0.1: + /widest-line@4.0.1: + resolution: {integrity: sha512-o0cyEG0e8GPzT4iGHphIOh0cJOV8fivsXxddQasHPHfoZf1ZexrfeA21w2NaEN1RHE+fXlfISmOE8R9N3u3Qig==} + engines: {node: '>=12'} dependencies: string-width: 5.1.2 + dev: false - wildcard@2.0.1: {} + /wildcard@2.0.1: + resolution: {integrity: sha512-CC1bOL87PIWSBhDcTrdeLo6eGT7mCFtrg0uIJtqJUFyK+eJnzl8A1niH56uu7KMa5XFrtiV+AQuHO3n7DsHnLQ==} + dev: false - wrap-ansi@7.0.0: + /wrap-ansi@7.0.0: + resolution: {integrity: sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==} + engines: {node: '>=10'} dependencies: ansi-styles: 4.3.0 string-width: 4.2.3 strip-ansi: 6.0.1 - wrap-ansi@8.1.0: + /wrap-ansi@8.1.0: + resolution: {integrity: sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ==} + engines: {node: '>=12'} dependencies: ansi-styles: 6.2.1 string-width: 5.1.2 strip-ansi: 7.1.0 - wrappy@1.0.2: {} + /wrappy@1.0.2: + resolution: {integrity: sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==} + dev: false - write-file-atomic@3.0.3: + /write-file-atomic@3.0.3: + resolution: {integrity: sha512-AvHcyZ5JnSfq3ioSyjrBkH9yW4m7Ayk8/9My/DD9onKeu/94fwrMocemO2QAJFAlnnDN+ZDS+ZjAR5ua1/PV/Q==} dependencies: imurmurhash: 0.1.4 is-typedarray: 1.0.0 signal-exit: 3.0.7 typedarray-to-buffer: 3.1.5 + dev: false - ws@7.5.10: {} + /ws@7.5.10: + resolution: {integrity: sha512-+dbF1tHwZpXcbOJdVOkzLDxZP1ailvSxM6ZweXTegylPny803bFhA+vqBYw4s31NSAk4S2Qz+AKXK9a4wkdjcQ==} + engines: {node: '>=8.3.0'} + peerDependencies: + bufferutil: ^4.0.1 + utf-8-validate: ^5.0.2 + peerDependenciesMeta: + bufferutil: + optional: true + utf-8-validate: + optional: true + dev: false - ws@8.18.0: {} + /ws@8.18.0: + resolution: {integrity: sha512-8VbfWfHLbbwu3+N6OKsOMpBdT4kXPDDB9cJk2bJ6mh9ucxdlnNvH1e+roYkKmN9Nxw2yjz7VzeO9oOz2zJ04Pw==} + engines: {node: '>=10.0.0'} + peerDependencies: + bufferutil: ^4.0.1 + utf-8-validate: '>=5.0.2' + peerDependenciesMeta: + bufferutil: + optional: true + utf-8-validate: + optional: true + dev: false - xdg-basedir@4.0.0: {} + /xdg-basedir@4.0.0: + resolution: {integrity: sha512-PSNhEJDejZYV7h50BohL09Er9VaIefr2LMAf3OEmpCkjOi34eYyQYAXUTjEQtZJTKcF0E2UKTh+osDLsgNim9Q==} + engines: {node: '>=8'} + dev: false - xml-js@1.6.11: + /xml-js@1.6.11: + resolution: {integrity: sha512-7rVi2KMfwfWFl+GpPg6m80IVMWXLRjO+PxTq7V2CDhoGak0wzYzFgUY2m4XJ47OGdXd8eLE8EmwfAmdjw7lC1g==} + hasBin: true dependencies: sax: 1.4.1 + dev: false - xtend@4.0.2: {} + /xtend@4.0.2: + resolution: {integrity: sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==} + engines: {node: '>=0.4'} + dev: false - yallist@3.1.1: {} + /yallist@3.1.1: + resolution: {integrity: sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==} + dev: false - yaml@1.10.2: {} + /yaml@1.10.2: + resolution: {integrity: sha512-r3vXyErRCYJ7wg28yvBY5VSoAF8ZvlcW9/BwUzEtUsjvX/DKs24dIkuwjtuprwJJHsbyUbLApepYTR1BN4uHrg==} + engines: {node: '>= 6'} + dev: false - yauzl@2.10.0: + /yauzl@2.10.0: + resolution: {integrity: sha512-p4a9I6X6nu6IhoGmBqAcbJy1mlC4j27vEPZX9F4L4/vZT3Lyq1VkFHw/V/PUcB9Buo+DG3iHkT0x3Qya58zc3g==} dependencies: buffer-crc32: 0.2.13 fd-slicer: 1.1.0 + dev: false - yocto-queue@0.1.0: {} + /yocto-queue@0.1.0: + resolution: {integrity: sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==} + engines: {node: '>=10'} + dev: false - zwitch@1.0.5: {} + /zwitch@1.0.5: + resolution: {integrity: sha512-V50KMwwzqJV0NpZIZFwfOD5/lyny3WlSzRiXgA0G7VUnRlqttta1L6UQIHzd6EuBY/cHGfwTIck7w1yH6Q5zUw==} + dev: false