Privacy Badger blocks LaunchDarkly urls about js-client-sdk

[jkodumal]

@Kerumen Thanks for the report-- we'll work with Privacy Badger to restrict blocking to events.launchdarkly.com, as we did in #41. Looking at this a bit deeper, I think we'll also modify the JS SDK to respect the Do Not Track header.

We're getting started on both fronts immediately.

[ghostwords]

I haven't had a chance to look at what exactly causes Privacy Badger to decide to start blocking launchdarkly.com resources, but generally speaking, Privacy Badger doesn't work from a blacklist but instead watches for what it considers to be tracking in each user's browser. Privacy Badger then starts blocking domains after having seen them perform tracking across three separate sites.

Would you be able to adopt the EFF Do Not Track policy? If your company can and will abide by the policy's requirements, posting the policy on your domains will tell Privacy Badger to allow loading of resources from those domains.

[jkodumal]

@ghostwords I believe so, that's what we're attempting to do now by modifying our JS SDK and hosting a dnt-policy.txt.

[ghostwords]

Could you share any example pages (one is good, three distinct domains would be great) where I could see your service in action?