- Issue created by @ressa
- 🇩🇰Denmark Steven Snedker
This would also benefit the External Link Preview Module immensely.
Yet with all the awful specious invoicing companies out there, local caching could mean a lot of Drupal sites losing a lot of money and a lot of sleep. We're at an impasse at Make a local image copy for GDPR 📌 Make a local image copy for GDPR Active (read and shudder).
Wayback Filter could branch out and support way smaller archive sites like Archive.today or Ghost Archive. There may be a few other OKish candidates on the List of web archiving initiatives. Autosubmit the URL where feasible.
But with only 14 users → , half of them me, and archive.org in ok health, I haven't spent any time on it. With only one user ever (!), Wayback Submit to Archive.org → will never be updated.
But back to the orignal question: caching sites?
No. Having Drupal sites caching (storing and publishing) third party sites locally is sadly way too risky.