
▲ 3 r/Adguard
For AG for iOS & AG mini for macOS user: enhanced injection timing about recent change of tinyShield build script
I want to share a recent tinyShield build-script change that is especially relevant for AdGuard for iOS and AdGuard mini for macOS users.
Why this was changed
I saw that a single combined userscript could make the impact of issue #38 broader than necessary when Safari-extension environments are involved.
The goal of this update is simple:
- reduce blast radius when a specific domain group has an issue
- keep unaffected domain groups stable
- improve practical injection behavior for Safari-based userscript environments
What changed in the build output
tinyShield now provides grouped Safari-focused script outputs instead of relying on only one combined file for this use case.
Current structure:
- Default script (unchanged for regular users):
- Grouped scripts (for Safari extension users):
- https://cdn.jsdelivr.net/npm/@filteringdev/tinyshield@latest/dist/grouped/<initial>/tinyShield-<domain-group>.user.js
In short, each domain group gets its own script file, and grouped files are arranged under subdirectories by initial character.
Expected effect
- Smaller impact scope when one group is affected
- Easier rollback/switch per domain group
- More predictable operation for AG for iOS and AG mini for macOS Safari-extension users
How to install/apply (AG for iOS / AG mini for macOS)
- Make sure that quoid/userscript (GitHub) is installed.
- Open:
- Enter the relevant <initial>/ subdirectory.
- Choose the matching tinyShield-<domain-group>.user.js file.
- Open that file and quickly verify its metadata @match includes your target website.
- Add that exact grouped URL to your Safari userscript extension (used alongside AdGuard).
- Reload the target website tab.
Note:
- If you are not using Safari-extension style userscript execution, keep using the default URL.
u/piquark6046 — 3 hours ago