[openstreetmap/openstreetmap-website] google imagery blacklist entry update (PR #3512)

[hlfan]

Since the main objective here is to disallow unintentional copyright violation (this won’t stop deliberate maneuvering around the blacklist), blocking all Google related imagery could be split in two parts:
1. All data from the domain could be blocked: `".*\.google(apis)?\..*/.*"`, since I couldn't come up with reasonable URLs which would additionally be blocked because of this. Notice that [most links just including "google"](https://www.openstreetmap.org/id#background=custom:https://gibs.earthdata.nasa.gov/wmts/epsg3857/all/VIIRS_SNPP_CorrectedReflectance_TrueColor/default/2022-04-08/GoogleMapsCompatible_Level9/{z}/{y}/{x}.jpg) aren't matched.
2. Additionally, in a second entry, Google's embedded parameters could also be matched: `".*pb=.*(!\d[a-z]\d+){3,}.*"`, which could serve as a failsafe if IP addresses, redirects or other tricks out of scope are used.

This double filter would only let the vt or kh endpoints slip through, if the URL is deliberately crafted excluding the blacklisted domains.
I'm providing variant A (matching domain and parameters, preferred) and variant B (only matching the domain) in reverse order.
So I suggest merging version A, and if someone does find permitted imagery/data matched by these filters they can be reduced to version B or discussed again.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/3512#issuecomment-1094119761
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/3512/c1094119761 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20220409/5ea09fac/attachment.htm>