A place for developers to talk about building on Farcaster.

/dev

it seems like Next will serve resources at static URLs with aggressive cache control headers

subsequent deploys will automatically invalidate these resources in Vercel CDNs, but any downstream CDNs / browsers are “stuck”

this is a big source of confusion for developers using Next to build frames

serving these resources with fingerprints as part of the URL would be preferable

if you’re familiar with Next / Vercel and can confirm / correct / or add nuance to this feedback would be appreciated

related to caching for frames devs which is one of the biggest sources of confusion

if you’re familiar with Next / Vercel and can confirm / correct / or add nuance to this feedback would be appreciated

related to caching for frames devs which is one of the biggest sources of confusion 

https://warpcast.com/deodad/0x0cd2636e

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

found this one

https://github.com/vercel/next.js/discussions/40896

yeah it's aggressive, but you also want it like that to save on function costs

my tactic for optimal resource usage has been -> cache-control + cache bust param + blob storage for og images (free beta)