Open grischard opened 7 months ago
See also the French inspiration: https://lists.openstreetmap.org/pipermail/talk/2020-March/084299.html
Blocked on setting up opentofu
@pnorman is this what we need? https://github.com/openstreetmap/opentofu-fastly
@pnorman is this what we need? https://github.com/openstreetmap/opentofu-fastly
That currently just manages the attribution blocked list, not the config.
The opentofu code there is minimal viable product for managing just the attribution blocks. It can and should be expanded. Easiest method is to expand by resource by resource using imports iteratively building up the full linked config dependency "tree".
Currently, blocked sites get a 403 error, which doesn't get displayed.
We should communicate clearly to sites lacking attribution what the issue is and how they can fix it. In practice, they often don't know what they are doing wrong (did we run into rate limits?) and end up switching to another provider, still with no attribution.
For attribution blocks, we should configure fastly to respond with an uncacheable friendly error image. The HTTP error code needs to be 200 for the image to display in Leaflet.