How about limit new accounts?

So, when I suggested the idea of a working group, I looked up the process for that. According to the wiki, a process was proposed, but not ever put into place, but seems like a reasonable place to start: Working groups/Proposing a new working group - OpenStreetMap Wiki

I agree with you though on approach. Part of what made me open this thread is I’d had similar thoughts on the style of account limits (similar to what Discourse itself does with permissions), and wonder if some combination of that plus wikipedia-like moderation (temporarily lock specific tag values, temporarily lock specific geographies) will end up being useful, along with an API that reports current locks so editors can warn users before they prepare changes. But the specifics matter a lot and need hashing out, as the rest of this thread shows.

I’d be curious what the people on the affected teams think of the idea of a working group - is there someone on the teams who has time to participate and thinks it’s a good route forward? I don’t want to propose it officially if it’s going to take time away and they’d rather continue informal coordination, but the discussions I’ve seen on this have seemed inconclusive at determining tools to develop because the number of considerations is large and crosses groups - as a result it feels like our admins lack tools necessary for the scale of the problem and it will just get worse.

Current measures does not helps a lot - map is in damaged state for several days already.
Is it possible to temporary ban IPs from which accounts were registered as an emergency measure?

I think that it might help to clarify what you mean by a “damaged state”. As of now (6:28 UTC on 25/8/2023) there absolutely are issues, and if you zoom in and look at the history you’ll see that reverts are in progress.

As of midnight last night, I’m not aware of any outstanding data issues. There absolutely were cached tiles in the CDN with old data visible, and other data consumers would have similar issues, but I think that the efforts to revert vandalism had largely caught up with the actual vandalism at that time - unless of course you know different.

Has a limit on the rate at which (new) accounts can comment been considered yet? I feel like putting some limits on that is sensible.

Situations like this, where a number of bot accounts send hundreds (well, thousands) of messages in just a few minutes are kinda ridiculous.


Oh, yeah, when I read this part I couldn’t process it (being late at night and so) but then I opened up @SomeoneElse’s link and that vandalism goes much worse than I thought. Of course, it doesn’t help that there are actual supporters of this vandalim (not just @BaboucheVerte but also @Anti1982 as given here, possibly @darkonus for liking the former’s post*), it’s a quite sad situation especially for something minor.

*Yeah, I know I too “liked” Babouche’s post but I accidentally kicked on liked instead of angry and by the time I noticed it, Discourse doesn’t allow me to change it.


(extra characters added to make > 10)

Oh, it’s at it again… I had the same effect from some reverts, but I had maybe 15 comments on every changset… not THIS…

yes and yes

I was asking yesterday about progress and got info that progress is happening at this moment the recommended action is to not bother person working on it (plus some ideas for even less direct action).

if you want you can ask for help: many mail clients (Gmail, Claws Mail etc) have support for mass deletion and filtering rules.

But we would need to know how you access mail.

See also rate-limit changeset comments · Issue #4196 · openstreetmap/openstreetmap-website · GitHub

1 Like

Whaaaat ? Where have you read that I was for this vandalism ? Ты дурак или что ? I strongly thank all the people fighting against the vandalism of removing name:ru ! (And I did add afew name:ru in Uzbekistan so you’re totally wrong). I was just responding when he was saying “you can’t talk with people full of hatred” meaning ukrainians. They’re not, Russians are.

I think that this vandalism just come from stupid trolls, it wouldn’t make any sense for ukrainians sympathysant to do so (whereas it would make sense from Russian one, to try to provethere is russophobia).

I mean vandalised names persists on the map for several hours here and there in last several days. This problem could not be solved with reverts. It is necessary to log IP on registration and temporary ban this IP if account do any harm - this is a simplest thing we could do for a moment until some account restrictions will be invented.

For example, this changeset is not reverted yet Changeset: 140348052 | OpenStreetMap .
By the way, is it safe to modify geometry of vandalised objects? Does it complicates revert process?

For some obvious and smaller changes we “only” need someone to implement change to GitHub - openstreetmap/openstreetmap-website: The Rails application that powers OpenStreetMap

So either one of current contributors will write patch (it is happening already from info I got). This does not require working group or board approval.

If you are familiar with Ruby on Rails: see Please help with pull requests! · Issue #3815 · openstreetmap/openstreetmap-website · GitHub - help would be highly welcome

For some large scale changes more would be needed. For example OSMF could hire someone to implement this like this (or help with review of open pull requests or do similar tasks), but right now are funds are too limited for this (one of reasons for fundraising).


this was checked as a solution, attacker is using VPN

Have you tried clearing browser cache?

From trying myself a revert requires reversal of edited nodes/ways vandalised top down from the edit stack

I am downloading this area with JOSM.

I think it would be ok if some VPN and proxy services IPs would be banned. Most of users would not suffer from this.

Would it be useful to block IP ranges used by vandals?

Editing vandalised objects complicates revert process and is highly not recommended.

mostly reverted, I am now looking through some trickier objects

Then, if you are not reverting it, it is helpful to report all such encountered objects (unless reverts are already happening right now). works quite nicely (though some vandals use tricks to make reverts more annoying).

And report any such unblocked accounts to DWG for blocking.

I see that Changesets by NorthCrab | OpenStreetMap is running reverts again.

Doing it in way that blocks more vandals than real users is ranging between tricky and impossible.

1 Like

All this efforts are ineffective - they will win.
IPs they could use for registration accounts are vpn-services, proxy-services, bot-nets and tor. This amount is limited, it is ok to ban them. If registration IP is logged already, this should be the simpliest solution.

I think registration of new users should be deactivated temporarily until some other mechanisms are in place that prevent automated account generation.

We have no idea how big the damage is. There could be much more than just the name and name:ru vandalism. Currently, the vandalism we see is executed pretty obvious and “stupid”. But this could change in the future.

1 Like

in Moscow, unfortunately, we have thousands and thousands of damaged objects now, and it’s not cash, I checked this: