Consider extending avatar cache to 1 year
Proposal
Our avatar implementations is immutable (whenever someone updates it's/project/group avatar image we create a new record and delete the old one). That means we will never update an existing image, and therefore there is no value in doing a cache revalidation. We should be serving those from memory when available. This reduces the ammount of requests, makes the page load with the image already there (so the application appears more responsive) but more important, navigating from one page to another will always be perceptibly faster as the images will already be there when any of the commentable components render.