(apologies for English, translate button below)
As @avinet_ua is refusing to work with the community (see discussion above) they’ve been blocked again**. We (the DWG) are happy to revoke that block provided that @avinet_ua agrees to no longer force their automated edits on the Ukrainian community (if they can’t reply here they can email data@openstreetmap.org with a subject of “[Ticket#2023052610000229] Issue #17937 User avinet_ua”).
With regard to reverts - I’ve said in the block message “we will therefore revert changes since your last revert back to the previous status quo” but I haven’t done any yet. If someone locally wants to do that rather than me I have no problems with that (someone local will surely be able to handle conflicts better, with better local knowledge. Changesets since the last block expiry are:
changesets=> select id, num_changes, tags -> 'comment' from osm_changeset where user_name = 'avinet_ua' and created_at > '2023-08-04';
id | num_changes | ?column?
-----------+-------------+----------------------------
139461294 | 279 | -
139462462 | 198 | revert of broken changeset
139461838 | 198 | added name:uk
139462484 | 3901 | revert of broken changeset
139462072 | 3901 | added name:uk
139462517 | 2269 | revert of broken changeset
139462260 | 2269 | added name:uk
139462541 | 4491 | added name:uk
139462564 | 2269 | added name:uk
139462600 | 198 | added name:uk
139462612 | 3901 | added name:uk
139462654 | 159 | added name
139462672 | 182 | added name:uk
139462686 | 7488 | added name:uk
(14 rows)
There appears to have been some rework / undoing previous mistakes in there as well so reverting the changesets 1 by 1 might not be easy.
Edit - see also this other thread.
– Andy, from OSM’s Data Working Group
** The last block was 1 month, and 6 months is the next option we have. As noted above I’ll happily revoke this block should @avinet_ua promise not to do this again.