I was wondering, is there a way to prevent such large scale and disruptive vandalism?
I just resolved another dozen notes regarding the fake and abusive streets.
1 Like
Thanks for resolving the notes. If you think that any of them need hiding due to the content, please report them to the DWG so that we can hide them.
Edit: Just for completeness, no related notes have turned up in the DWG’s queue at the time of writing.
Yes, I suspect that that is exactly what happened. To make sure, can you run though the steps above to make sure that no problem data is left? You may find that it disappears as soon as you reload the data.
I’ve been reporting quite a few as well indeed. Apparently plenty of people don’t know this Andy guy and that he might take offense…
Edit: also for completeness, that dozen notes did quote the street names but they were self censored, so I didn’t report any of those.
From where I am,
tile.openstreetmap.org/16/36599/21586.png shows OK,
a.tile.openstreetmap.org/16/36599/21586.png shows vandalized.
No amount of shift-reload will change anything.
The headers are as follows:
HTTP/2 200
server: Apache/2.4.54 (Ubuntu)
strict-transport-security: max-age=31536000; includeSubDomains; preload
etag: “433d2d10a32639d3cc7d86e14ab1b64a”
cache-control: max-age=5448, stale-while-revalidate=604800, stale-if-error=604800
expires: Sat, 13 Apr 2024 11:55:43 GMT
access-control-allow-origin: *
x-tilerender: nidhogg. openstreetmap. org
content-type: image/png
accept-ranges: bytes
age: 2133
date: Sat, 13 Apr 2024 13:48:13 GMT
via: 1.1 varnish
x-served-by: cache-fra-etou8220075-FRA
x-cache: HIT
x-cache-hits: 0
x-timer: S1713016094.657364,VS0,VE1
alt-svc: h3=“:443”;ma=86400,h3-29=“:443”;ma=86400,h3-27=“:443”;ma=86400
content-length: 27508
HTTP/2 200
server: Apache/2.4.54 (Ubuntu)
strict-transport-security: max-age=31536000; includeSubDomains; preload
access-control-allow-origin: *
etag: “1afcec5277cf7764f0872ed501fd880b”
cache-control: max-age=604800, stale-while-revalidate=604800, stale-if-error=604800
expires: Wed, 17 Apr 2024 05:23:14 GMT
x-tilerender: nidhogg. openstreetmap. org
content-type: image/png
accept-ranges: bytes
age: 289541
date: Sat, 13 Apr 2024 13:48:55 GMT
via: 1.1 varnish
x-served-by: cache-fra-etou8220033-FRA
x-cache: HIT
x-cache-hits: 0
x-timer: S1713016135.435605,VS0,VE1
alt-svc: h3=“:443”;ma=86400,h3-29=“:443”;ma=86400,h3-27=“:443”;ma=86400
content-length: 28645
Please note the difference in cache-control/expires headers. It seems we are stuck with vandalized tiles till Wednesday.
I see, but they are still used by many sites (not mine).
It seems a hard refresh for the CDN (sending Pragma: no-cache, Cache-Control: no-cache headers) only works from openstreetmap.org:
I have seen both the edits that got reverted and the edits that were highly likely prompted by the reverts. From what I can fathom about edits No1: Where there was a name:ru attached a name:uk was attached too. From what I know, these places neither have a name:ru nor do they have a name:uk. Both are superfluous as they are mere transliterations of name (name:de in my case) as anybody from :ru or :uk can read the Latin alphabet.
From my local perspective, the reverts of the gratuitous adding of name:uk are fully justified. The principle of parsimony further would justify removing name:ru. Such a mechanical edit might require…
Added roads:
Hello,
Would it be possible to go through the procedure above? I don’t see any added roads - I suspect that the vandalism is being cleared up and you are just seeing a “cache” issue.
Also looks Ok to me, a hard refresh with Ctrl-F5 or Shift-Reload should help?
Looks like it, I could find the “roads” in iD, when trying to revert it.
I have force expire code now live. I will improve it over time.
7 Likes
Hi everyone,
I came here after noticing massive vandalism in the following locations:
…/#map=13/49.6054/11.6283
…/#map=13/49.5496/11.3039
I’m afraid the problem could be much larger…
The vandalism has been repaired. There are still a few map tiles that have not yet been re-rendered and show the lines (streets).
Please clear your browser cache with Shift-F5 / Ctrl-F5 (use the key combinations several times), this will request new, updated map tiles.
Thanks - does that mean that if someone sees a problem now it’s definitely just in local cache?
We’re still getting DWG reports with screenshots coming in - we’d like to be able to say “just do a force refresh and the problem will go away” (but obviously don’t want to say that if that isn’t 100% true).
Hard to say that as regular mapper without access to servers, maybe CDN is still poisoned?
But refreshing browser cache often helps and typical person cannot do more.
Even after OSM CDN cache will be fixed it is possible that they may be using OSM map from somewhere else, not from OSMF hosted tileserver.
This seems to be the current go-to-thread for current abuses. Maybe make the title more understandable for non-technical people as well?
map on osm.org looks wrong (white lines, absuive comments, …) - OSM Standard tile layer hacked?
Or something like that?
1 Like
I’ve edited the title in line with that suggestion.
2 Likes