piebro/osm-data huggingface dataset:
NeisBot (2026-01-17 15:30:16+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/4038955735 v2

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Firma czyszcząca tapicerkę meblową w Trójmieście"
---
Na przykład bardziej neutralna i obiektywna wersja Twojego tekstu mogłaby brzmieć: "Firma czyszcząca tapicerkę meblową w Trójmieście"
---
(Auto-translation)

#MapWithoutSpam
pitscheplatsch (2026-01-17 15:33:29+00:00): Has been fixed by https://www.openstreetmap.org/changeset/177194742

Thanks @Szymson
eggie (2026-01-12 18:30:59+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.
Feedback Het adres heb ik verwijderd.
MVG,
Eggie
Namens de OSM Community
CurlingMan13 (2026-01-16 19:04:30+00:00): Reviewed your change as part of regular reviewing.  Changeset looks good!  Thanks for the contribution.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/177146822
mcliquid (2026-01-17 08:18:56+00:00): Hier ist auch einiges im Argen. Siehe dazu auch: https://community.openstreetmap.org/t/why-is-it-ok-that-id-performs-undiscussed-semiautomatic-distributed-mass-edits/139011

website=https://... (falls vorhanden) ?
mobileGEO (2026-01-17 11:56:04+00:00): Danke für den Thread. Da wird wirklich auf einer soliden sozialen Ebene diskutiert. Das wünsche ich mir eines Tages für das Österreich Forum.
Ja; der tag ist provisorisch. Über EveryDoor könnte man den schön eintragen. Aber viele tun das halt nicht. Das ist dann eher was für die Desktop warriors. 
Ein kleiner 'Dorn im Auge', damit jemand mit Erfahrung drüber stolpert und das sieht, was ich eben (noch) nicht sehe. Klarerweise steht da dann noch der Aufwand-Nutzen-Faktor.
Man muss ja wirklich nicht alles erfassen. Aber hin- und wieder kann man ja Anreize geben.

Eines meiner Ziele für 2026 ist jedenfalls die effiziente Nutzung des Forums, um Vorschläge zu unterbreiten. Momentan gleicht mein Ansatz ja eher einer Guerilla Taktik. Und das ist für wirklich niemanden angenehm.
(Bezieht sich auch auf das andere Changeset
https://www.openstreetmap.org/changeset/177145704)

Beste Grüße
Und weiterhin gutes Mapping.
mcliquid (2026-01-18 09:56:03+00:00): Hallo mobileGEO,

danke für deine ausführliche Rückmeldung. Ich möchte aber ein paar Dinge klarstellen, weil wir hier an einem grundsätzlichen Punkt angelangt sind.

OSM ist kein Wunschkonzert und auch kein Parkplatz für provisorische oder bewusst falsche Tags in der Hoffnung, dass „jemand mit Erfahrung drüber stolpert“. Genau dieses Vorgehen widerspricht den Grundprinzipien des Projekts. Daten werden nicht als Anreiz, Dorn im Auge oder Platzhalter erfasst, sondern weil sie korrekt, überprüfbar und sinnvoll nutzbar sind.

Das ungeprüfte Übernehmen von Osmose-Hinweisen ist dabei ein reales Problem. Osmose ist ein QA-Werkzeug, kein Validator der Wahrheit. Nicht alles, was dort angezeigt wird, ist ein Fehler – und nicht alles, was ergänzt werden könnte, sollte auch ergänzt werden. Änderungen ohne inhaltliche Prüfung erzeugen am Ende genau das Gegenteil von Qualität: Datenschrott.

- Wenn eine Bushaltestelle aufgelassen wurde, stellt sich die berechtigte Frage:
- Welchen Mehrwert hat eine unvollständige Adresse?
- Warum ein name=*, wenn das Objekt kein aktives Haupt-Tag mehr hat?

Für wen sollen diese Daten nutzbar sein?

Solche Einträge helfen weder Renderer- noch Router- noch Auswertungs-Usecases und erhöhen nur die Komplexität für alle Nachmapper.

Ich möchte das ausdrücklich klar sagen:
Bewusst falsche, provisorische oder spekulative Tags sind nicht akzeptabel, auch nicht mit guter Absicht. In der Summe bewegt sich dieses Vorgehen gefährlich nahe an dem, was man als Vandalismus bezeichnet – nicht wegen böser Absicht, sondern wegen der Auswirkungen.

Wenn du Dinge verbessern willst, ist das absolut begrüßenswert. Dann aber bitte:

- mit etabliertem Tagging
- mit realen, überprüften Informationen
- und im Zweifel lieber weglassen als andichten

Diskussionen, Vorschläge und auch Lernen über das Forum sind der richtige Weg – „Guerilla-Mapping“ über produktive Daten ist es nicht.

Viele Grüße
mcliquid
Taya_S (2026-01-12 19:29:46+00:00): Hello jowiti,

Could you tell me what the source is of these trees you have added? Additionally, have you followed the import guidelines? https://wiki.openstreetmap.org/wiki/Import/Guidelines

Best regards,
Taya Snijder,
On behalf of the OSMF Data Working Group
trial (2026-01-12 17:55:42+00:00): En fait https://www.openstreetmap.org/way/1392720735 contourne le giratoire en bidirectionnel.
Voie cyclable, semble-t-il sans accès piéton.
" fusion entre trottoir et piste cyblable" c'est une description, pas un nom propre.
Tant qu'à passer dans le coin : la surface est du béton (comme indiqué, je doute), du sol compacté (compacted : argile, sable, gravier lié à l'eau, plus probable) ou un asphalte de couleur ?
Taya_S (2026-01-15 07:45:44+00:00): This changeset has been reverted. Please make sure you comply with the import guidelines first. https://wiki.openstreetmap.org/wiki/Import/Guidelines

https://www.openstreetmap.org/changeset/177247583
rskedgell (2026-01-13 16:14:05+00:00): Welcome to OpenStreetMap.

This was originally mapped as a footway.

Is what you are trying to represent here that it is a footpath between Seymour Place and private parking on Bryanston Mews West, and that it is private access due to the presence of a locked gate?
MaryleboneWestminster (2026-01-13 22:03:52+00:00): Thanks for the help.
Change is because it is not a footway, It is a private parking, with a gate in the middle (currently closed, which corresponds to the Ordnance Survey map).
The alley is used as a private parking by the owner and has bollards on each side as well.
Hope it helps clarify. Feel free to amend if category/description in the modification not done the way it should. Thanks
rskedgell (2026-01-14 00:15:15+00:00): Thanks for getting back to me. I'll edit it in the morning and add a longer explanation of the tagging here.
rskedgell (2026-01-14 00:18:32+00:00): Does it still look like this image taken in Aug 2023?
https://www.mapillary.com/app/user/asturksever?lat=51.51732270866&lng=-0.16214893490196&z=19.20385621742934&pKey=1008262773538406&focus=photo&x=0.7574123031588382&y=0.5627549485123149&zoom=0
MaryleboneWestminster (2026-01-14 11:24:16+00:00): Thanks a lot.

Does not look the same no, here is a picture taken this morning where you can see the chain, the no right of way sign, parking etc:

https://we.tl/t-OroyznI3oB
rskedgell (2026-01-14 11:34:07+00:00): Thanks, that's great! I'm on my way out now, will update later.
rskedgell (2026-01-14 21:39:26+00:00): I've now updated this in https://www.openstreetmap.org/changeset/177237104

A quick summary:
- changed alley to highway=service + service=alley and connected it to Seymour Place
- added a barrier=gate node and barrier=chain way both with access=private
- split the alley at the gate/chain and set the part behind to access=private
- added a private parking area behind the gate/chain
- added the bike hangar

I hope that looks reasonable to you.
MaryleboneWestminster (2026-01-14 21:57:46+00:00): Very nice, thanks for the help. One street corrected at a time!
On to the next. 
keep on the good work.
MaryleboneWestminster (2026-01-14 22:00:30+00:00): Most important bit is that people who plan their walk through this realize it is effectively blocked (the gate and blockage does not seem to appear on my refresh actually)
MaryleboneWestminster (2026-01-14 22:05:04+00:00): for instance this is how it appears on https://footpathmap.co.uk/map/?zoom=19.8&lng=-0.16203&lat=51.51729 now. it will probably be interpreted as open route would think by most people
rskedgell (2026-01-14 23:25:52+00:00): It may take a few weeks before it propagates to routing services which use OSM data. Of the two which I use most often, Komoot can take 1-2 weeks and Strava 2-4 weeks.
MaryleboneWestminster (2026-01-14 23:28:52+00:00): 👍
DressyPear4 (2026-01-12 18:58:56+00:00): A subestação Morro do Chapéu é essa
https://www.openstreetmap.org/way/580267970
Nomes retirados de
https://dadosabertos-aneel.opendata.arcgis.com/search?q=cemig
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/177147814
cassiobaraujo (2026-01-12 19:50:22+00:00): Na verdade, não. Esta é a subestação Morro do Chapéu. A subestação Jangada fica em outro local (-20.0946, -44.0709). Aquela subestação próxima à SE Nova Lima 5 é uma SE industrial, particular.
dzidek23 (2026-01-13 15:29:41+00:00): Hi Josh,
I noticed a couple of things in your changeset that could be improved.
When you draw a swimming pool in someone's garden, let it be IN the garden. Objects can overlap and they do in real life. Swimming pool is in the garden and not wrapped in it.

Other thing is shapes of the gardens. Don't know if you know but in the Background menu, under the Overlays there's OSMUK Cadastral Parcels layer. When selected, it will show you the exact shape of each parcel making drawing gardens and streets much easier.

Cheerio!
Taya_S (2026-01-15 07:45:45+00:00): This changeset has been reverted. Please make sure you comply with the import guidelines first. https://wiki.openstreetmap.org/wiki/Import/Guidelines

https://www.openstreetmap.org/changeset/177247583
JezCrow (2026-01-15 18:16:30+00:00): Hi FINN442,
You're continuing to add some strangely-shaped buildings. You're also connecting them together when in reality some are detached (see west of Scalford Road) and adding multiple buildings for a single house (e.g. way/1466540397 and way/1466540399 )

As Bernard has said on your previous changeset, you can make the corners to be right-angles by using the keyboard shortcut Q (or right-clicking and selecting 'Square'). Also, buildings should be drawn to the footprint, not the roofline - not so easy when the aerial imagery is skewed but there are guides on the wiki.

Help is available should you need it. Happy mapping,
Jez
NeisBot (2026-01-17 15:30:20+00:00): Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language.

⚠️️ Problematic element (limit 1):
https://osm.org/node/13444335759 v3

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Home inspection services"

#MapWithoutSpam
NeisReview (2026-01-25 07:36:46+00:00): 🚫 Text removed by https://osm.org/changeset/177369096
trigpoint (2026-01-12 17:41:09+00:00): This changeset reverts some or all edits made in changesets 176861218, 176863646, 176866703, 176869095, 176871325, 176871908, 176906065, 176906979, 176907705, 176908040, 176909082, 176911432, 176911529, 176912403, 176912442, 176912471, 176912520, 176912568, 176918631, 176920607, 176921326, 176921409, 176922249, 176941984, 176942313, 176944089, 176944260, 176947624, 176951607, 176952520, 176953309, 176956303, 176982778, 176984963, 177029453, 177030346, 177030780, 177031046, 177064423, 177064582, 177065814, 177066915, 177067244.
trigpoint (2026-01-12 17:42:14+00:00): This changeset reverts some or all edits made in changesets 176861218, 176863646, 176866703, 176869095, 176871325, 176871908, 176906065, 176906979, 176907705, 176908040, 176909082, 176911432, 176911529, 176912403, 176912442, 176912471, 176912520, 176912568, 176918631, 176920607, 176921326, 176921409, 176922249, 176941984, 176942313, 176944089, 176944260, 176947624, 176951607, 176952520, 176953309, 176956303, 176982778, 176984963, 177029453, 177030346, 177030780, 177031046, 177064423, 177064582, 177065814, 177066915, 177067244.
NeisBot (2026-01-12 17:48:21+00:00): Hi Zenzor, welcome to OSM!

Thank you for your contributions to the map. I have reviewed your recent edits and noticed that 85% of the changes in this set involve deletions, including:
- 20 building(s)

Could you please confirm if these deletions were intentional or if they occurred by mistake?

Looking forward to your response.

#DeletionsCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177148543
SomeoneElse (2026-01-15 12:24:28+00:00): In at least one example the deletion here is OK and the previous edit by another mapper was dubious.  See https://www.openstreetmap.org/changeset/176332487
pitscheplatsch (2026-01-17 08:12:27+00:00): Thank you for your detailed review, @SomeoneElse
NeatNit (2026-01-21 15:45:00+00:00): I reverted your changesets because they don't follow OpenStreetMap's normal way of mapping bus stops.

https://www.openstreetmap.org/changeset/177528969
trigpoint (2026-01-12 17:53:29+00:00): This changeset reverts some or all edits made in changesets 176861218, 176863646, 176866703, 176869095, 176871325, 176871908, 176906065, 176906979, 176907705, 176908040, 176909082, 176911432, 176911529, 176912403, 176912442, 176912471, 176912520, 176912568, 176918631, 176920607, 176921326, 176921409, 176922249, 176941984, 176942313, 176944089, 176944260, 176947624, 176951607, 176952520, 176953309, 176956303, 176982778, 176984963, 177029453, 177030346, 177030780, 177031046, 177064423, 177064582, 177065814, 177066915, 177067244.
aceman444 (2026-03-21 10:52:53+00:00): Thanks, but next time please use nodes of restaurants that were previously there, e.g. https://www.openstreetmap.org/node/7960889085 for KNESEL.
Cafe bazaar already exists at https://www.openstreetmap.org/node/4856551363 .
The same with Doris cookies at https://www.openstreetmap.org/node/3144490921 . So next time add data to existing objects, do not create duplicates. Fix your tools or processes please.
aceman444 (2026-03-21 11:02:03+00:00): Also please quote the source of your data in each changeset, using the 'source' tag on the changeset or each added object.
NeatNit (2026-01-21 15:45:01+00:00): I reverted your changesets because they don't follow OpenStreetMap's normal way of mapping bus stops.

https://www.openstreetmap.org/changeset/177528969
NeatNit (2026-01-21 15:45:02+00:00): I reverted your changesets because they don't follow OpenStreetMap's normal way of mapping bus stops.

https://www.openstreetmap.org/changeset/177528969
aighes (2026-01-13 00:35:59+00:00): I don't care which key used for the timezones in Germany, but please keep the standard time zone as well as the dst-zone.
mueschel (2026-01-13 08:47:52+00:00): timezone = Europe/Berlin
contains the necessary information for both the standard and dst time.

I'm not aware of any object with an explicitly tagged daylight savings timezone.
JeroenHoek (2026-01-13 09:29:37+00:00): https://wiki.openstreetmap.org/wiki/DE:Any_tags_you_like

Fühlen Sie sich frei, neue Tags zu erfinden!
Frank Peng (2026-01-13 01:50:46+00:00): Can you explain why you have been changing valid service roads and driveways around schools to unclassified roads? I don't think those roads serving this school should be tagged as unclassified roads. Those would probably be better tagged as highway=service.

Are you trying to tag for the router by changing valid service roads and driveways around schools to unclassified roads? If so, then please note that tagging for the router is against OSM good practice. Do not use inaccurate tags or distort data associated with map features to influence routing navigation towards your preferred router. Routing software is consistently improving. If you tag for the router, then it can mislead routers into completely avoiding those roads or paths, or potentially allowing other vehicle categories. Consider trying an alternative option or reporting any issues or improvement suggestions to the different routing projects. Per the "Don't map for the router" section on the OSM Wiki article on good practice, it states:

"Do not use inaccurate tags or distort data to influence routing navigation to your preferences. Familiarize yourself with best practices instead. Since routers are consistently improving, consider trying an alternative option or reporting any issues or improvement suggestions to the different routing projects."
https://wiki.openstreetmap.org/wiki/Good_practice#Don't_map_for_the_router

https://wiki.openstreetmap.org/wiki/Tagging_for_the_router
Frank Peng (2026-01-13 03:56:42+00:00): And since you're part of an organized editing group, it is important that you follow the Organized Editing Guidelines. https://wiki.openstreetmap.org/wiki/Organised_Editing/Guidelines
The Organized Editing Guidelines are found here: https://osmfoundation.org/wiki/Organised_Editing_Guidelines, and under "Possible actions on problematic edits", they state that:

"Problematic edits may be reverted. In cases of severe or repeated problems, individuals and organisations may be banned from editing OpenStreetMap."

However, many, if not all of your edits, have been problematic by damaging or deleting valid map data, retagging roads within school zones and residential areas to unclassified roads when they don't need to be, and adding non-existent roads or other features. Please do not damage or delete valid map data, or add non-existent features on OSM. Please note that if you continue those problematic map edits, then you could be blocked from editing OSM. 

Please take care not to damage valid map data by changing valid administrative or suburb boundaries into roads, and only map features that actually exist on the ground.
Frank Peng (2026-01-13 21:17:41+00:00): Please take care not to damage valid map data by not changing valid administrative or suburb boundaries into roads, and only map features that actually exist on the ground.
Udarian (2026-01-12 19:05:14+00:00): y'all should be extra careful with this stretch of Okeechobee Road (US 27) and its frontage road as there is allot of construction happening and according to FDOT by the end most of the frontage road from HEFT to Fl 826 will have a sidewalk on one side, so while I'm pretty sure that the edits in this changeset are in segment four which will not start construction any time soon and thus are correct its kind of hard to tell as all of the aerial imagery in the area are out of date (including the Miami Dade County one) along this road where construction has been happening. to double check you can use the following custom imagery in the web based editors like Rapid:

https://imageserverintra.miamidade.gov/arcgis/rest/services/Woolpert2025/ImageServer/exportImage?f=image&bbox={bbox}&bboxSR={wkid}&imageSR={wkid}&size={width},{height}+

you can get this working in JOSM, I have but that was a little more complicated, for more info see:

https://imageserverintra.miamidade.gov/arcgis/rest/services/Woolpert2025/ImageServer

the link for the main FDOT website for the Okeechobee construction project is https://www.fdotmiamidade.com/okeechobee . If you have any questions about this please feel free to message me here or through OSM.

Happy Mapping,
Udar.
VLD280 (2026-01-12 20:22:15+00:00): Hi Udar,

Thanks for letting me know about the plans for this road and for sharing the most recent orthoimagery. I'll make sure to take this into account while working in the area. Appreciate the help!

~Isaac (VLD280)
Ltrlg (2026-01-12 21:13:08+00:00): Il s’agit apparemment des identifiants que l’on trouve sur https://carte.fftt.com/. Je ne vois rien qui pourrait indiquer un lien avec la FFT ?
mueschel (2026-01-12 21:28:50+00:00): 'ref:FR:FFT' is already used quite a lot on sport-related POIs, so this looked like a trivial typo. I change it back.
Ltrlg (2026-01-12 21:36:46+00:00): Thank you!
Frans S (2026-01-22 15:53:19+00:00): Hello. Thanks for mapping.
Please do not tag open courtyards as a building. You see both on the inside as well on the outside a shadow.

Check this mapping
https://www.openstreetmap.org/way/1466563095/history#map=19/13.758498/21.605811
Best regards
eggie (2026-01-12 19:22:42+00:00): Dag Tactist..
Wanneer je de weg op construction zet dan routeert het ook niet voor voetgangers.
Meestal voegen we conditional tags toe met een begin en einddatum.
Dan gaat de weg automatisch weer open.

Mvg
eggie
eggie (2026-01-12 19:27:33+00:00): Zomaar een willekeurig voorbeeld.

access:conditional=no @ (2025 Sep 20-2026 Apr 03)
eggie (2026-01-12 19:33:52+00:00): Ik heb het aangepast naar access:conditional
Tactist (2026-01-12 19:38:19+00:00): Goed om te weten! Ik had het 'construction' type van een andere mapper afgekeken, maar dan lijkt een access:conditional in deze situatie beter. Bedankt!
eggie (2026-01-12 19:45:50+00:00): Het voordeel is dat wie eenmalig een kaart download voor z'n gpsr nog steeds een werkende kaart heeft.
OsmAnd gebruikers en gebruikers met ondersteunende routers zullen er ook profijt van hebben.
Voor gebruikers die ondersteuning ontberen zien vast wel de omleidingsborden.
Als iets op een heel andere manier terugkomt en het gaat verder nog vele maanden duren dan kan het wel op construction. Nadeel.. een gemankeerde kaart bij download. 
Groet,
eggie
eggie (2026-01-12 19:51:18+00:00): Volgens Melvin gaat het in februari weer open.
Daarna wellicht het volgende stuk
https://melvin.ndw.nu/public
eggie (2026-01-12 19:52:16+00:00): 
E1497529: Generaal Maczekstraat Breda Weg
Gemeente Breda
12-01-2026 07:00 t/m 27-02-2026 17:00
eggie (2026-01-12 19:53:51+00:00): Voorlopig weer aangepast conform Melvin  Dat is wat de Gemeente Breda zelf doorgeeft.
Tactist (2026-01-12 19:56:02+00:00): Fase 1b (28-2 tot 18-7) bedraagt hetzelfde werkvak plus een uitbreiding met verkeersregelaars. De weg waar deze changeset over gaat is dus afgesloten tot eind Juli.
Tactist (2026-01-12 19:57:01+00:00): De gemeente Breda publiceert de informatie over deze fases naar haar bewoners via https://bereikbaarheid.andes.nl/breda waarin alle fases staan aangegeven. Het einde van de werkzaamheden voor fase 3 is 24 december 2026.
eggie (2026-01-12 20:01:20+00:00): Oke.. up to you. 😀
Je kunt het zelf aanpassen.. dan weet je gelijk ook hoe we dat doen.
Dan mag de Gemeente wel hun zaken beter doorgeven naar Melvin.
Mapse..
eggie
Tactist (2026-01-12 20:08:28+00:00): Gelukt 🙂 bedankt voor de hulp en uitleg
Sanniu (2026-03-22 15:48:42+00:00): Hi, you have renamed part of בן יהודה, but leave house numbers, English name and other street parts intact. Is it deliberate?
Supaplex030 (2026-01-12 20:50:26+00:00): Hallo Henri, ich würde das cycleway:right:separation:left=parking_lane (das du hier gerade bearbeitet hast) gern durch cycleway:right:traffic_mode:left=parking ersetzen; bzw. dann cycleway:right:separation:left=no draus machen (= links vom Radfahrstreifen parken Autos, und es gibt keine physische Barriere dazwischen). "parking" als separation-Value ist inzwischen veraltet; siehe auch https://wiki.openstreetmap.org/wiki/Proposal:Separation#Indication_of_adjacent_traffic_mode

Da spricht vermutlich auch von dir nichts dagegen?

lg, Alex
FMC-Henri (2026-01-16 09:13:35+00:00): Hallo Alex,

darfst du gerne ändern :)

Grüße
Henri
Supaplex030 (2026-01-17 20:11:09+00:00): Done.
gt3400 (2026-05-25 18:07:47+00:00): Ja, der Wegweiser steht nicht genau beim Dianabründl. Das ist bei fast allen ÖTK Wegweisern an Wegknoten so, dass sie nach einem Objekt in der Nähe benannt sind. Dann müssten wir aber bei allen 318 Wegweisern den Zusatz "Wegknoten" ergänzen (eigentlich "Wegpunkt", da der ÖTK sie so nennt).
DerKaiserschmarren (2026-05-26 06:08:56+00:00): Ich habe beim Wegweiser die Position um 5 Meter verschoben, da die Position vorher nicht korrekt war. Am Namen habe ich nichts beanstandet ;)
Steht schließlich auch auf der Tafel.
DerKaiserschmarren (2026-05-26 06:10:18+00:00): Ich tippe mal, du hättest lieber dem Kuhni mit dem Changeset davor schreiben sollen ;)
gt3400 (2026-05-26 08:21:01+00:00): Sorry, in der Tat falsche Baustelle;-)
DerKaiserschmarren (2026-05-26 12:42:21+00:00): Kein Ding :)