| 10 Jul 2025 |
 emily | so anyone who has been running master before that will have cached 404s for first day everyone is bumping to the new channel revision | 19:00:58 |
 Zhaofeng Li | contributors can try to build locally and trigger the negative caching, which would be bad UX | 19:01:07 |
| Zhaofeng Li | yeah | 19:01:10 |
 Arian | But this is already a problem. Nix caches 404s locally | 19:01:18 |
| emily | it's not a problem across users | 19:01:25 |
| Zhaofeng Li | but this would affect it for everyone | 19:01:29 |
| emily | most users don't try to run master, but some do | 19:01:30 |
| Arian | Aaah I see | 19:01:32 |
| Zhaofeng Li | some Nix hater can even just look at the big in-progress hydra builds, and hit cache.nixos.org with the outpaths | 19:02:18 |
| emily | so even someone testing a build before merging could screw up its caching for the next channel bump | 19:02:19 |
| emily | so definitely needs cache-busting or to be much shorter than 24h I think | 19:02:31 |
| Zhaofeng Li | * some Nix hater can even just look at the big in-progress hydra builds, and hit cache.nixos.org with the outpaths... then laptops everywhere will be building chromium | 19:03:01 |
| Arian | if I'm reading the bill right we currently spend 570 dollars per month on GET requests and only 60 dollars per month on PUT
PUT is charged | 19:08:55 |
| Arian | * if I'm reading the bill right we currently spend 570 dollars per month on GET requests and only 60 dollars per month on PUT
| 19:09:10 |
| Arian | okay so seems not caching 404s is kind of a "feature" | 19:14:14 |
| Arian | because it means we don't need to do cache-busting on channel bumps | 19:14:39 |
