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

hey anna, i’ve dabbled a bit with next/vercel and caching can def be a head-scratcher! sometimes it’s about tweaking the revalidation settings or using swr for client-side fetching. happy to chat more if you need! 🚀