Thanks, Eggie, I understand how it can happen. I'm just curious if experienced users/maintainers tried to solve the issue by preventing such changes from being automatically applied without additional review. It should be a fairly easy to implement automated check, e.g. check the length of the longest side of a rectangle formed by the points in a changeset and if it is more than 10/100km - put the change on hold or reject it with an error message.

Being new to OSM, I've noticed this change as it affects such a big area, and I'm curious whether it would make sense to restrict merging changes that span area larger than certain threshold and enforce a review by someone else before they are merged?