Sorry for a bot edit escaping its supposed borders (adding website tags in Germany)

For start: sorry for accidentally running a bot edit outside Poland that was discussed only with Polish community. Edits were limited to adding/editing website tags. Main problem was that bot was run without required discussion, OSM data should not be damaged.

I noticed (too late) that Mateusz Konieczny - bot account - ATP import | OpenStreetMap performed edits outside Poland/USA, despite that bot edit were not cleared at all outside Poland/USA.

In Germany it resulted in adding or improving 1105 website tags (also, 1400 more across world - also in locations where bot edit was not cleared to run at all).

Root reason was that location was supposed to be limited to a Poland but required check was not actually performed in the final version of code.

Luckily this defect should be independent from data processing, so website tags should be fine and not damaged.

Edits themselves should be not be breaking data and from spot checking they were fine as far as values of website tags are concerned. But edit was not discussed so it should not have happened. I had nice plan to first run more limited edits, figure and fix problems if any and then propose run in areas that are less bot-happy like Germany to make more likely they will be accepted.
I guess that this plan is thoroughly bungled now.

I am thinking right now what I should do with it, probably I will revert these undiscussed bot edits. But it will take some time, as I need to figure how to do it properly without causing any further issues.

Again: sorry.

3 Likes

Mir war auch eine Änderung davon in meiner Nähe aufgefallen. Diese hatte ich aber überprüft und sie war richtig. Von daher: Bevor Du die Änderungen jetzt wieder rückgängig machst, kann man sie sich doch einmal ansehen und dann entscheiden, ob man sie behält.


I had also noticed a edit in my neighbourhood. But I had checked it and it was correct. So before you revert the edits now, you can have a look at them and then decide whether to keep them.

The tricky issue here is that edits (new website values) should be better than previous one, and as far as I checked are.
This part was quite well tested and is quite careful about editing.

So revert would be more on procedural grounds and to make more likely that people will agree once actual bot proposal is made. Not to fix any data damage - revert will make website tags worse.

@Mateusz_Konieczny es betraf nur NKD wie z.B. Node: ‪NKD‬ (‪7289176454‬) | OpenStreetMap?

Das, was ich in meinem Umfeld in Südbrandenburg gesehen habe, da hab ich keine Probleme damit, wenn das bleibt…

Sven

I proposed doing already done import in Proposed imports of website tags for NKD, based on ATP first-party data (this covers part of data)

depending on response I will either perform revert or mark it as accepted and welcome

sorry again for the wrong order

You’ve created chaos! In my opinion, all your bot operations need to be redacted!

…representative of the rest of the rubbish!

See Fehlgeschlagene BOT-Aktion? "ATP-Import" Hä?

Infolge der jüngsten Entwicklungen, siehe Fehlgeschlagene BOT-Aktion? "ATP-Import" Hä? ziehe ich hiermit meine Meinung zurück und fordere einen vollständigen Redact(!!) der Bot-Operation…

wieso reicht ein Revert nicht (??)

2 Likes

Have you read thread linked above one you posted?

what you tried to express here?

??? maybe try writing it in German and let people to read it directly if they know German and let other people to translate with autotranslate

As far as I know redaction is not a correct tool here either way.

Data redaction (distinct from reverting) is reserved for copyright violations, people posting highly problematic content like private personal data. Not for underdiscussed imports where data is not a copyright violation.

(also, vast majority of my bot editing was independently approved in a correct order, messing up this edit does not retroactively invalidate other permissions)

5 Likes

Fixing in Germany should be now completed.

Das hieĂźe dann mit dem letzten Bot-Spam-Kommentar (ich finde da leider keine anderen Worte mehr):

12:46:19 UTC 1795 fehlerhafte/potentiell fehlerhafte Bot-Changesets? Also knapp 1800???

Ich kann da nur noch ungläubig mit dem Kopf schütteln und möchte am liebsten laut schreien! Das werdet ihr aber leider nicht hören… :frowning:

Sowas darf nicht passieren, auf gar keinen Fall, niemals unter keinen Umständen!

sehr entsetzte Grüße…

1 Like

Zum GlĂĽck.

4 Likes

Es ist mittlerweile alles gesagt worden und es ist auch kein weiterer produktiver Erkenntnisgewinn zu erwarten.

Es tut jedem gut, in einem Streit einen Schritt zurück zu treten und sich zu fragen, ob das, was man vertritt, sinnvoll und im Projekt mehrheitsfähig ist oder ob man sich verrennt hat.

Siehe auch Fehlgeschlagene BOT-Aktion? "ATP-Import" Hä? - #43