<p>One area this manifests in is via the diary feature (and corresponding RSS feeds), and we now have the default of review-my-changesets set for newer accounts.</p>
<p>Could we optionally use a (potentially proprietary) captcha on a new diary post; when:</p>
<ul>
<li>There are no reviewed changesets associated with the account</li>
<li>And or an editor hasn't got the cookie/whatever mechanism ID uses to prompt new editors with the tutorial present</li>
</ul>
<p>Options such as <a href="https://github.com/desirepath41/visualCaptcha">https://github.com/desirepath41/visualCaptcha</a> do exist now; even if they aren't maintained at the moment.</p>
<p>With very specific criteria, we could avoid accidentally adding barriers for new editors; and only mildly inconvenience people who jump into editing via JOSM or other editors.</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/issues/1083#issuecomment-489511482">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLK3ND5SRKKXOLUSCLLPT7E4XANCNFSM4BT3FBBQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AAK2OLJFDIH33N6U3AC7DZ3PT7E4XA5CNFSM4BT3FBB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODUWVUOQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/openstreetmap/openstreetmap-website/issues/1083#issuecomment-489511482",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/1083#issuecomment-489511482",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>