<p>Are you sure this is the right place to design the JOSM user interface? Is that not something that should be left to the JOSM developers? There's a relationship of course, but I think that we should do this like we did it with the limitation of changeset sizes: The OSM API decides what is acceptable and rejects anything unacceptable with an error message, and it is then the duty of the editors to ideally guide their users so that this error condition is never triggered, or to deal with the error in a suitable fashion should it occur.</p>
<p>Since I'm a JOSM user myself I could certainly sketch a number of possible JOSM UI approaches to get this right, but they would not necessarily apply to other editors that have different UIs - I think that approaching this from a UI perspective is the wrong approach for us in this repository.</p>
<p>We should build a mechanism that lets us reject uploads of "too much in too short time", and we could initially set these limits very high and give editor writes the chance to experiment and adapt their UI if necessary, and then tighten the limits to something sensible. I think that trying to design good UIs for all editors is out of scope here.</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=AAK2OLIX6JSXEVRQFSV62HLQE7RHNA5CNFSM4IJTW3X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4QJWNY#issuecomment-522230583">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AAK2OLMTZAOBZI5RS66NQNTQE7RHNANCNFSM4IJTW3XQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AAK2OLOLWBNHAAQ5G52AY7LQE7RHNA5CNFSM4IJTW3X2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4QJWNY.gif" height="1" width="1" alt="" /></p>
"name": "View Issue"
"description": "View this Issue on GitHub",