That's probably fair.

But it would be nice if you explained to all these mappers why you are deleting their edits. Most will likely never notice their work is gone, and won't know how to check where it went.

Your changeset comments are also rather misleading; you say you're "fixing old-style multipolygons" but really you are just deleting those that have errors.

Thanks for the heads up. 👍

Hi,
Did you actually check this data before removing it?
I started a multi for an in-progress landcover and even added a note to alert other mappers to its intent.

Hi,
Please be careful doing large edits like this. way/426818887 is a boundary, not a track road, which is quite obvious from any imagery layer.
Thanks

Hi,
In this changeset you added multiple buildings that overlap with your own previously added buildings. Please be more careful when editing.
Thanks,
Will

wrong hashtags

wrong hashtags

Hi avelex,
Please be careful when mass editing things, especially in JOSM. In this changeset you added `parking:lane:both` tags to hundreds of child nodes. This tag is intended ONLY for the roads it applies to, not the nodes making up the road.
If you could correct these changes that would be great.
Let me know if you have any questions.
Thanks,
Will

Hi,
Why are you adding stops at both the intersection and the location of the stop sign? A router going through the intersection will think it has to stop twice.

Hi,
Can you point me to the import page for this? I can't seem to find it.
Thanks

Hi,
thanks for making contributions to the map!
If you ever decide to continue mapping, please take steps to make the data nice before uploading to the server, like squaring buildings or drawing them in shapes actually representative of the structure.
Thanks

Hi Shankar,
Welcome to OSM.
So far, almost all of your changes have been duplicates of already existing highways or waterways. Please don't draw data over what's already in the database and upload it.

Hi,
please double-check your work before submitting.
This road is a duplicate of an existing road that is more correct. You are also using hashtags for tracking a project in Nepal; this is South Africa.
Thanks

A while ago I went through the `payments=` tag (https://taginfo.openstreetmap.org/search?q=payments) and was changing them all to the correct `payment:*=` tag so they could actually be used by consumers. (In hindsight it was probably on large enough scale that I should have announced it somewhere, but I almost cleared the tag from the database.)
And here I did only chang the value to lowercase in order to agree with all the common `payment:*` keys where even brands are expressed in lowercase.

Hi,
Are you sure this is the correct Swan Cleaners EPA Superfund site? From searching it appears to be in Wall Twp.
https://cumulis.epa.gov/supercpad/cursites/csitinfo.cfm?id=0204241

Frankly it seems fine to me; both OSRM and GraphHopper on the main site can route past it just fine.
It could be that the access tag added a couple months after the note was open actually solved it.
I'll close the note, hopefully there's no more problems.
Thanks

Hi anjbe,
Can you verify that there are (or were) actual spikes at the exit to the campground (node/3064367385)?
According to note/381519 routers cannot get out of the campground because of this.
Thanks,
Will

Is way/393262651 still needed as a placeholder?

Hi,
Is this an inn, a bar, or a pub? Please check the wiki pages for amenity=bar and amenity=pub and change this to whichever is more correct. Tagging for things is based on what it is, not what it will be displayed as.
See osm.wiki/Tagging_for_the_renderer
Thanks

Pretty sure this was info pulled straight from teh Googles since the street address is incorrect and only found in that result. It's for a different store of the same company.