Side N
9 Billion Requests a Day, Moved Without Rebuilding a File
Which sources back which section of this article, and what its evidence base looks like.
Which sources back which section
| Section | Sources behind it |
|---|---|
| What Happened | Badoiu, The Cloudflare Blog (2026); W3Techs (2026); Cloudflare Changelog (February and March 2026); MDN, “Subresource Integrity”; cdnjs monthly usage reports (2025–2026); cdnjs metadata-worker pull request 7 (2026); cdnjs issue 14305 (2026); the cdnjs/cdnjs repository (2025–2026) |
| Timeline | Prince (2011), Bloom (2019) and Caslin (2020), The Cloudflare Blog; RyotaK (2021); Ganz, Calderon and Sauleau, The Cloudflare Blog (2021); Cloudflare Changelog (2026); cdnjs metadata-worker pull request 6 (2026); cdnjs issues 14305, 14307 and 14309 (2026); Badoiu, The Cloudflare Blog (2026); Kumili, InfoQ (2026); cdnjs api-server pull request 279 (2026); the cdnjs/cdnjs repository (2025–2026) |
| The Argument | Badoiu, The Cloudflare Blog (2026); Cloudflare Changelog (February and March 2026); Kumili, InfoQ (2026) |
| What Others Add | MDN, “Subresource Integrity”; Badoiu, The Cloudflare Blog (2026); cdnjs issue 14305 and metadata-worker pull request 7 (2026); RyotaK (2021); Ganz, Calderon and Sauleau, The Cloudflare Blog (2021); W3Techs (2026); cdnjs monthly usage reports (2025–2026); cdnjs issues 14307 and 14309 (2026); cdnjs api-server pull request 279 (2026); the cdnjs/cdnjs repository (2025–2026) |
| Conclusion | Badoiu, The Cloudflare Blog (2026); Cloudflare Changelog (February 2026); cdnjs monthly usage reports (2025–2026); cdnjs issues 14305, 14307 and 14309 (2026); cdnjs api-server pull request 279 (2026); the cdnjs/cdnjs repository and its GitHub repository record (2026) |
What the evidence base looks like
- 20Sources behind this article
- 5Sections, every one of them sourced
- 20Read in full
- 8From the open-source project’s own public record
| What the source is | How many | How they were read |
|---|---|---|
| The operator’s own account of the migration | 1 | In full, at its own address |
| The operator’s documentation and earlier posts | 6 | All in full, at their own addresses |
| The open-source project’s public record — issues, pull requests, monthly reports, README | 8 | All in full, including every comment on each issue |
| Independent reporting and disclosure | 2 | All in full, at their own addresses |
| Reference works and measurements | 3 | All in full, at their own addresses |
Reliable
Reliable, but with an interestWorth believing and reliableWeak on both, and used with careHonest, but thin
Worth believing