Mailshade and Trocker compared
Trocker is a direct multi-webmail competitor and should not be described as a basic three-client blocker. Its current Chrome Web Store listing says it blocks known trackers in all webmails, adds enhanced visual and heuristic handling in Gmail, Yahoo Mail and Outlook.com, attempts to bypass tracked links, and publishes its source under Apache-2.0. The same listing documents a Manifest V3 limitation involving unknown trackers and webmail image proxies, while Outlook may be limited to known tracking services. Mailshade 1.1.0 declares six opt-in webmail integrations, reviewed endpoint declarativeNetRequest blocking, local tracker detection history and supported tracking-link warnings. Mailshade requests access per enabled inbox; Trocker's manifest declares broad host access for universal known-tracker blocking. These differences are supported by primary sources. Blocking recall, benign-content precision and the usable-result assessment remain pending until both pinned versions complete the same run.
Comparison record
Facts reviewed on .
- Test date
- Not yet tested; no performance winner is claimed.
- Methodology
- Read the published method
Versions in scope
Method and current result
Each pinned extension must run in a clean Chrome profile against the same versioned pixel, link and benign-content fixtures before comparative performance is stated.
Official sources establish current versions and design claims; blocking recall, false positives and an overall result remain pending a shared reproducible run.
Claim evidence
- [verified] Trocker 3.4.1 claims known-tracker blocking across webmails and enhanced handling in Gmail, Yahoo and Outlook.com. source 1
- [verified] Trocker publishes its source under Apache-2.0. Mailshade makes AGPL-3.0-or-later source archives and checksums available; each archive must be matched to the exact tested package version. source 1, source 2
- [pending] Relative protection efficacy, benign-content breakage and usable coverage remain unmeasured on the shared corpus.
Sources
- Mailshade Chrome Web Store listing, Mailshade; accessed .
- Mailshade source archives and checksums, Mailshade; accessed .
- Trocker Chrome Web Store listing, Trocker; accessed .
- Trocker source repository, Trocker; accessed .
What Trocker documents
Trocker's current listing describes known-tracker blocking across webmail pages and enhanced behavior in Gmail, Yahoo Mail and Outlook.com. It exposes detected trackers, uses heuristics in supported webmails, attempts to bypass tracked links, supports custom tracker lists and publishes source under Apache-2.0.
What Mailshade documents
Mailshade uses opt-in host permissions for six named webmail integrations, reviewed endpoint DNR rules, local sender-level detection history and a direct-or-original choice for recognized tracking redirects. Mailshade also makes AGPL-3.0-or-later source archives and checksums available; reviewers must match an archive to the exact tested package version.
Meaningful design differences
- Host scope: Mailshade is opt-in per supported inbox; Trocker uses broader host access to apply its known tracker list widely.
- Enhanced clients: Trocker names Gmail, Yahoo and Outlook.com for its richest UI and heuristics. Mailshade names six dedicated adapters.
- Reporting: Trocker reports live blocked or exposed statistics; Mailshade adds local per-sender history.
- Unknown trackers: both products face Manifest V3 constraints, so a controlled network test is needed.
No winner yet
Feature lists do not settle blocking recall or false positives. The comparison remains pending until the shared fixtures are run in isolated profiles and the raw observations are published.
FAQ
Does Trocker work outside Gmail, Outlook and Yahoo?
Its official listing says known trackers are blocked in all webmails, while enhanced visual and heuristic capabilities are available in Gmail, Yahoo and Outlook.com. That is broader than the earlier wording on this site.
Is Trocker open source?
Yes. Trocker's official repository is licensed under Apache-2.0. Mailshade makes AGPL-3.0-or-later source archives and checksums available; reviewers must match an archive to the exact tested package version.
Does Trocker handle tracking links?
Its official listing says it tries to bypass tracked links and otherwise warns the user. Mailshade also documents a direct-or-original choice for supported tracking redirects.
Which blocker handles unknown trackers better?
That remains pending. Trocker documents different Manifest V3 behavior by webmail, and Mailshade combines reviewed endpoint blocking with DOM detection. Only the shared network corpus can support a comparison.
Why are host permissions part of the comparison?
They reflect a real design trade-off. Broad access can apply known rules widely, while opt-in per-client access limits scope. Permission design does not by itself determine blocking efficacy.