<p><a href="https://github.com/zverik" class="user-mention">@Zverik</a> is correct - this PR would allow anyone to make the changes. We run a "default permit" permissions system currently (but see <a href="https://github.com/openstreetmap/openstreetmap-website/issues/1626" class="issue-link js-issue-link" data-error-text="Failed to load issue title" data-id="254033085" data-permission-text="Issue title is private" data-url="https://github.com/openstreetmap/openstreetmap-website/issues/1626">#1626</a> for me wanting to change this). So the PR can't be merged as-is.</p>
<p>I also think it's a good idea to align the terminology, so that we are "redacting" changeset tags. It has implications for dumps, replication and the API too, since if the tags are being redacted they are presumably being done so for a good reason!</p>
<p><a href="https://github.com/woodpeck" class="user-mention">@woodpeck</a> what was your reasoning for this only affecting the website and not the API? First-things-first, or something more fundamental?</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/openstreetmap/openstreetmap-website/pull/1167#issuecomment-349758546">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABWnLS-O3zCDxbYz6UhDkQHm3kRICgajks5s9vN1gaJpZM4Hk1LA">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ABWnLQj3ieejog5EDG5LMczNPER88h2Cks5s9vN1gaJpZM4Hk1LA.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/pull/1167#issuecomment-349758546"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/openstreetmap/openstreetmap-website","title":"openstreetmap/openstreetmap-website","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/openstreetmap/openstreetmap-website"}},"updates":{"snippets":[{"icon":"PERSON","message":"@gravitystorm in #1167: @Zverik is correct - this PR would allow anyone to make the changes. We run a \"default permit\" permissions system currently (but see https://github.com/openstreetmap/openstreetmap-website/issues/1626 for me wanting to change this). So the PR can't be merged as-is.\r\n\r\nI also think it's a good idea to align the terminology, so that we are \"redacting\" changeset tags. It has implications for dumps, replication and the API too, since if the tags are being redacted they are presumably being done so for a good reason! \r\n\r\n@woodpeck what was your reasoning for this only affecting the website and not the API? First-things-first, or something more fundamental?"}],"action":{"name":"View Pull Request","url":"https://github.com/openstreetmap/openstreetmap-website/pull/1167#issuecomment-349758546"}}}</script>