Can you please switch over to the dev instance at https://master.apis.dev.openstreetmap.org to test your software https://github.com/mdornseif/osm-treewarden while it's still in development?

Seems a bit like wasted effort since it caught the attention of another user who then started to remove name=* tags again. ;)

osm.org/user/ALu68/history

Hello,

you seem to be the only mapper who consistently manages to create changesets with 10001 changes, although the maximum value should really be 10'000 changes, so one less.
In total there are 103 such changesets since Mid-2019, out of which you have created 87.

I'm wondering if you're doing anything special in JOSM, like using single object uploads, maybe?

There could be something we need to double check from an API point of view. Let's see...

Hallo, Der Wilderer. Die Frage von Mateusz bezog sich auf den Knoten osm.org/node/554533381: dort ist ein Tag width=0 zu finden, wobei nicht ganz klar ist, was damit gemeint war.

LGTM: https://dev.overpass-api.de/cs_143218439_achavi.png

So the revert tool works as designed here... will continue the discussion over at Github.

Reported as https://github.com/Zaczero/osm-revert/issues/18

There's something wrong with the revert tool, e.g. osm.org/node/540424027/history lost almost half of its tags, e.g. website. I checked some other nodes, and they all had similar issues.

It seems this changeset has reverted back to a version, which has been vandalized by another user. Example would be osm.org/node/358530861/history : revert brought back #10. However, #9 would be a good version in this case. Maybe this is already being taken care of right now.

Seems like you've reverted to another vandalized version of the data: osm.org/way/210662937/history

Stützpunkte sind da keine verloren gegangen (sieht man hier: https://overpass-turbo.eu/s/1zCU ). Allerdings wurde in diesen Änderungssatz aus dem Weg 309471261 ein geschlossener Weg gemacht (d.h. Anfangs- und Endpunkt sind identisch), so dass im Nordwesten diese langgezogene Linie entsteht.

Follow up: https://community.openstreetmap.org/t/wie-konne-sich-freizeitmapper-vor-der-willkur-kommerzieller-mapper-schutzen/6888

Just wanted to make you aware of the discussion in https://lists.openstreetmap.org/pipermail/talk/2022-September/087752.html

I believe the large scale change in Russia should be related to this changeset. Maybe you could briefly comment if this change is ok, so that the coastline generation can continue as usual.

I think you didn't get my point: even though you've been blocked, you would have still been able to comment on this changeset. Because of a bug I've mentioned earlier, this isn't possible at the moment.

Andy Townsend didn't abuse any DWG powers here. It's nothing more than a bug in the Rails port that still needs to be fixed: https://github.com/openstreetmap/openstreetmap-website/issues/3522#issuecomment-1095464792

That's really the only reason, why you couldn't comment here. Nothing else.

I'm wondering why you keep adding circles like osm.org/way/1026778864 to the map. According to this blog post, you seem to have added similar data all over the world: osm.org/user/%E7%90%89%E7%92%83%E7%99%BE%E5%90%88/diary/399110

Please make sure you're removing those circles before uploading your data to the database.

This link should help to find out what's happening in this cs: https://dev.overpass-api.de/achavi/?changeset=119341145&relations=true

Curious about the HTML code in the description tag: osm.org/way/238048085 - was it really intended this way?

osm.org/node/4800966713 - eine neue Weiche eingetragen für eine railway=platform und einen highway=path.... Hmmm.. interessante "Logik".

Changeset discussions are not a great place for any sort of technical discussion, so I'll keep it brief. https://github.com/mmd-osm/Overpass-API#hourglass-performance has a list of performance topics. However, not all of them are relevant to the topic at hand.