<p></p>
<p>Right. I also think that it’s not feasible to split out parts of an existing permission into a new one.</p>
<p>In theory we could leave the existing permission as is and create <em>two</em> new ones, one for real map changes (rather than “write api” as it is named today), and a second one for cs comments. Then deprecate the current write api permission. The problem with that approach is that it backfires on cgimap’s OAuth handling, so I’d rather wouldn’t want do it.</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/2631#issuecomment-636191710">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLNKYWAOTOKJD3XTFQ3RUAPQJANCNFSM4NFGNPHA">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AAK2OLOZRIHLYXT7H3TB27DRUAPQJA5CNFSM4NFGNPHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEXVYHXQ.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/2631#issuecomment-636191710",
"url": "https://github.com/openstreetmap/openstreetmap-website/issues/2631#issuecomment-636191710",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>