You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Of interest is its use of a UUID. Is this the first anyone has seen of this tracking mode?
If not, I'm wondering if the heuristics could include a combination rule such as [URI path includes the word "tracker"] && [URI parameter is UUID] to identify something as a likely tracker? Or would this generate too many false positives?
The text was updated successfully, but these errors were encountered:
Trackers always come with random-looking, alphanumeric hashes for sure (although not always in UUID format). The current heuristic seems to catch nearly 100% of the trackers I've seen. Your idea would definitely work for other remaining uncaught trackers (CSS based, header logo embedded or ad trackers). Will think about this one
Just emailed you a tracker from Telstra (Australia's largest telco) which is not caught by existing heuristics:
<img src="https://tapi.telstra.com/presentation/v1/notification-mngmt/delivery-status-tracker?uuid=2bd5aea0-96d2-4f75-910e-99225420a950" style="display:none"/>
[for privacy actual UUID has been replaced with a randomly generated UUID using https://www.uuidgenerator.net/version4]
Of interest is its use of a UUID. Is this the first anyone has seen of this tracking mode?
If not, I'm wondering if the heuristics could include a combination rule such as [URI path includes the word "tracker"] && [URI parameter is UUID] to identify something as a likely tracker? Or would this generate too many false positives?
The text was updated successfully, but these errors were encountered: