Ryan Barrett

Also if Elk is just a web frontend, why does it affect AS2 fetches at all? 🤔

Actual Elk issue: https://github.com/elk-zone/elk/issues/2463

Ooh, App Engine will actually act as an edge cache and cache responses for us! https://cloud.google.com/appengine/docs/standard/how-requests-are-handled?tab=python#response_caching https://issuetracker.google.com/issues/35886021 https://groups.google.com/d/topic/google-appengine/6xAV2Q5x8AU/discussion (old) https://groups.google.com/d/msg/google-appengine/8QgEUBOiNFw/m4O5quSO8q0J (old)

Also, test that the Vary header is respected first: https://issuetracker.google.com/issues/35888786

Fixed by 9c4888b02e63fbce0a4adc92ce5302b8793042be

This didn't seem to work; App Engine doesn't seem to be serving any of our requests from its frontend cache.  

Found the bug, we were serving `Cache-Control: public, max-age: 3600.0`, with float seconds. Oops. Fixed that, and it's working!!!

Nice! Thanks for the info, good to hear that experience. That's how I'd expect to do this too. Also, Bridgy Fed uses threaded WSGI workers, and I think this design...

Understood, and sure, that'd be great! And yes, we'd just use a standard `threading.Lock` here. Sounds like you've already made progress getting set up. Feel free to try, I'm happy...

I noticed something just now that will make this harder. Looking at an AP outbox request that we got 12 times within ~5s, those requests got spread out to multiple...