Internet Archive As A CDN
Description
The top half is a dark-mode tweet from Phil, handle "@immunda," saying, "Hey @BarclaysUK; maybe don't use @internetarchive as a CDN for your JS assets? \u00af\\_(\u30c4)_/\u00af" Below it is a browser developer-tools Network panel for https://www.barclays.co.uk showing a request URL that starts with "https://web.archive.org/web/20200601165625/" and points to a Barclays JavaScript asset, with "Status Code: 200 OK" and response headers like "content-encoding: gzip" and "content-security-policy." The lower half shows a suited masked figure in front of a dense network-cable/data-center background, captioned "content delivery." The joke is that using an archival service as a production JavaScript delivery path is a spectacularly brittle substitute for an actual CDN, with obvious availability, cache, integrity, and security concerns.
Comments
1Comment deleted
Nothing says enterprise resilience like making archive.org your single point of JavaScript truth.