Alexei

As this adds a new input to our learning engine, this should help when cookie learning has been curtailed (#1851) for whatever reason.

Beacons are one of three [transport methods](https://developers.google.com/analytics/devguides/collection/analyticsjs/field-reference#transport) for Google Analytics. I'm very curious to see if Badger will catch Google Analytics in its [pretrained data set](https://github.com/EFForg/badger-sett) with this PR.

If it's just Cloudflare cookies, this sounds like the same issue as https://github.com/EFForg/privacybadger/issues/1493#issuecomment-318712851. As I wrote there, we never migrated Cloudflare-blocked domains, and I wonder if we still should.

Does setting `api.trakt.tv` to "yellow" work around the problem?

This is related to #963.

Privacy Badger sees the `XSRF-TOKEN` session cookie (there is also a far-future `dwCoBrId` cookie) on each Talkyard-powered site, coming from a "comments-for-" `talkyard.net` subdomain, and marks that as a strike...

If Talkyard is able and willing to abide by the [EFF Do Not Track policy](https://www.eff.org/dnt-policy)'s requirements on all `talkyard.net` domains used by external sites, posting the policy on each `talkyard.net`...

Does this make sense? Let me know if you have any questions.

1: It is very possible we overlooked this use case. Privacy Badger treats three different cookies (one per site) set by three different subdomains of the same third-party domain the...

Here is a recently-released privacy study that looks into session-replay scripts: [No boundaries: Exfiltration of personal data by session-replay scripts](https://freedom-to-tinker.com/2017/11/15/no-boundaries-exfiltration-of-personal-data-by-session-replay-scripts/) Edit: [2020 update/paper](https://freedom-to-tinker.com/2020/07/14/can-the-exfiltration-of-personal-data-by-web-trackers-be-stopped/) Edit: [2022 paper](https://homes.esat.kuleuven.be/~asenol/leaky-forms/)