<p>Come to think of it, we should probably focus a bit more on UX and discuss ways on how to guide (new) users without patronizing them too much.</p>
<p>In particular, large scale uploads, or massive moving around of nodes (based on some well meaning clean up effort) could be easily detected in JOSM and combined with other user metrics like number of changesets or day or date of registration. Also, JOSM knows how much time a user spent in an editing session and can figure out, if it's a simply Overpass download, search and replace and upload within 1 minute kind of mechanical upload, which the API would never be able to figure out.</p>
<p>On top, we can present fully localized messages to the user, along with a nice graphical step-by-step guide to go through some checklist or similar, rather than some technical HTTP error message the API would return.</p>
<p>So again, let's focus on the user experience first, think how the user interaction could look like, and what kind of guidance would be reasonable and acceptable.</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/2342?email_source=notifications&email_token=AAK2OLOZCPODWHPWI3UXHSLQDROMJA5CNFSM4IJTW3X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD34ONGY#issuecomment-519628443">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLOMJQ3ZOMSU2O3MXM3QDROMJANCNFSM4IJTW3XQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AAK2OLJQVJSV7HRF5Y4MJATQDROMJA5CNFSM4IJTW3X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD34ONGY.gif" height="1" width="1" alt="" /></p>
"name": "View Issue"
"description": "View this Issue on GitHub",