It would be indeed a good way for to deliver cleaner map data, but it won’t take away the almost certain return of the same vandalists afterwards to continue this illogical provoke.
Though, this would have a greater effect if at the same time new anti-vandalism features get implemented (if feasible ones can ever get planned and implemented that is).
That could be necessary one time, but it gives attackers the power to halt the entire process. I think we need a mechanism to allow and process ongoing changes to the database, while holding propagation of potentially unsafe object versions.
I don’t see how this helps. If there is an algorithm, it needs to stop potential harmful edits and release them only after manual review of a trustworthy mapper. Stopping OSM for cleaning up the data will be worse compared to current situation.
It’d be helpful to know (privately, if you prefer) the reason for that.
Especially as this comment looks accurate and not offensive/problematic/aggressive or otherwise problematic.
Yes, some people have weird/evil/confusing goals (at least from our perspective) and will do weird/evil/pointless/insane things. Sometimes it involves vandalising OpenStreetMap, sometimes it involves other acts.
Yes, see also Vandalismus endeckt ?! - #2 by pitscheplatsch
Several mods are reverting or have already reverted …
there are so many accounts doing this its actually insane, apparently its some sort of anti-russian propaganda but if thats the case this is a pretty weird way of spreading consciousness about the war.
If they did, loaded it ATM of my post into JOSM and tried a revert, frozen at step 9 of 46 of the validation cycle, then maxed out on memory as my JOSM is only allowed to use 4GB and it wss at 4.328. I’ll cancel since not wanting to cause a conflict.
I still think this would be a good idea.
How can a user at their first edit upload a changeset that spans over the entire globe with nodes dragged of thousand of km?
Yeah, I’ve witnessed that too (and reported as many accounts as I can). Also considered doing reverting it (since I myself also did reverts) but decided to leave for the experts.
In fact, I was wondering how long it took before someone posts here.
The user who’s way I linked to shows registration today, 17 edits with similar description and not blocked, yet.
Edit: Sorry now 24. 28
I found one clearly vandalistic changeset, Changeset: 152614038 | OpenStreetMap , and reverted it using osm-revert, however it is only one of many: more work will be needed to go back to an actually clean state
Ran your OSM-revert on the CS who’s ways were crossing mine. Easy with this tool, 4.3 seconds. Thanks.
(PS The user now shows having a lifetime block 
)
Yes. Looks like The Blockening has commenced.
Thanks to our team 
(Oh, and to the petty little vandal: If you’re trying to further some kind of cause: this is not helping in any way. Neither Russia nor Ukraine gain anything from these stunts. And if you’re angry about decisions by people here at OSM: Grow up)
Note: anyone that is not an expert at reverting things should not try to revert this.
In this case someone decided to waste a lot of time to setup something relatively tricky to revert. It is not standard case where simply reverting with common tools in standard configuration will work.
I tried to help with reverting and only made things worse. Sorry.
If you are not fully understanding what edits exactly did, do not revert. If you think you do - you may be making the same mistake as me and you should recheck.
If you revert changeset by changeset, without filtering for elements, without checking all changesets - you are definitely making things worse.
(maybe helping in some way is useful, I hope that someone from DWG will post here if that applies)
If anything they effectively behave as pro-Russia troll (pointlessly damaging stuff while insulting something is effectively making other side seem worse). No idea what they actually intended, and there is no point in caring about this.
This was discussed a bit in Maybe rate limit changeset size? · Issue #4805 · openstreetmap/openstreetmap-website · GitHub
If someone would be interested in analysis of one kind or another then potential effects of such change could be estimated.
There is also Allow a limit to be set on expiry of line segments by tomhughes · Pull Request #2185 · osm2pgsql-dev/osm2pgsql · GitHub but it needs even more advanced knowledge to help with it.
@Mateusz_Konieczy You are right; this should be left to the experts to revert. Unfortunatly I read your post after I had made three reverts. I will refrain from further reverting this vandalism-attac.
The reverts I made were:
152619968,
152620037,
152621216.
I hope I did not revert a revert or otherwise destroyed somthing.
Just to reassure people, this latest vandalism is being dealt with. It needs to be done in one go as all the changeset objects are interlinked. As noted above, piecemeal reverts using tools such as Josm’s reverter plugin or https://revert.monicz.dev/ won’t work because they will just restore something to a previously bad state.
Edit: A revert has now fixed most or all of this. If you think that something is still wrong, please go through the checks above before reporting it - you may just be seeing it in your browser cache.
Will the CDN now serve bad tiles till next week? I see some in zoom 14 and 15 in the JOSM editor.
