<p>Ah, a correction to my reply: I think adding things to the "yellowlist" makes sense for tileservers (as I have previously done) because the PB will then block cookies but allow content. This doesn't help with the cookie issue.</p>

<p>Quoting from the <a href="https://www.eff.org/privacybadger">PB FAQ</a>: "You can [get cookies working again for your site] by posting a specific compliant <a href="https://www.eff.org/dnt-policy">DNT policy</a> to the URL <a href="https://example.com/.well-known/dnt-policy.txt">https://example.com/.well-known/dnt-policy.txt</a>, where "example.com" is all of your DNT-compliant domains." Since OSM is probably compliant with EFF's boilerplate DNT policy, I guess what is needed is for the Data Working Group to confirm that, and then we can simply place that text in the appropriate place.</p>

<p>(Happy to be corrected again, if needed...)</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href="https://github.com/openstreetmap/openstreetmap-website/issues/1032#issuecomment-130450446">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABWnLRYs9l-zUMUUsPvUuH1MhHHddlQaks5om65FgaJpZM4Fqgoa.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/openstreetmap/openstreetmap-website/issues/1032#issuecomment-130450446"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>