| 8 May 2026 |
 Arian | That sounds really off to me. | 10:10:17 |
| Arian | 
Download 1000065300.jpg | 10:11:44 |
| Arian | Red line is egress bandwidth | 10:11:51 |
| Arian | It's hockey sticking | 10:11:57 |
 jappie | does that mean that the amount of requests for stuff that isn't cached by fastly is growing (perhaps scrapers stumbling upon old derivations)? because I'd assume an uptick in users downloading new-ish derivations would mean more hits in fastly and no noticeable growth in S3 egress | 10:17:43 |
 hexa (signing key rotation when) | I think so | 10:18:23 |
| jappie | how the hell are scrapers discovering old store paths / derivations... the URLs for those contain a hash right? I'd expect that to be really difficult and time-consuming (and useless) to scrape | 10:19:37 |
| Arian | You can dump all of hydras evaluations. Or run evaluations for all historical nixos commits yourself | 10:21:14 |
 leona | can we determine that this is egress via fastly or is someone downloading them directly from AWS? | 10:21:46 |
| Arian | Directly through S3 is only possible when requester pays | 10:22:01 |
| Arian | We don't have anonymous auth enabled on our bucket. You need to provide your iam identity and it gets billed to the caller | 10:22:32 |
| Arian | It would be preferable if scrapers would scrape S3 directly as then it doesn't cost us | 10:22:55 |
| hexa (signing key rotation when) | one obvious fix would be to GC harder, provide fewer targets | 10:24:42 |
| Arian | I'm wondering if I can somehow figure out from S3 the distribution of the age of objects being requested | 10:30:52 |
 emily | is it still true that Fastly doesn't cache paths for long even once built? | 11:10:55 |
