frames-devs

the refreshing of the image cache is for the next time that the frame that is on a given url is shared?

or the image of that frame casted on a given cast? 

if you see this exact same cast in 6 hours:

will you see a different image? or will it only change the next time the frame is shared, in a new cast?

the refreshing of the image cache is for the next time that the frame that is on a given url is shared?

or the image of that frame casted on a given cast? 

if you see this exact same cast in 6 hours:

will you see a different image? or will it only change the next time the frame is shared, in a new cast?

https://pfp-collage-test.vercel.app/api

Mini apps will eat the internet | Latest drop: /clankermon | Building : /large /fctrivia /miniapps /flappycaster /jeeves /source @degentip @playsource /jump

full sack developer intern at /farcards /mintclub warpcast.tools 🔫 my code breaks things :( 


working on infra to displace adtech at /microsub • dance music lover + host of /campfire 🎧

father. meditator. programmer. working on /anky

@undefined @matthewfox @downshift.eth @stephancill you may know the answer to this

the frame image will update whenever it reappears appears in the user's feed because it has a Cache-Control header

where did you see that? im trying to figure why this one isn't refreshing

where did you see that? im trying to figure why this one isn't refreshing 

https://www.vibra.so/stream/jpfraneto

you need to make an endpoint on your server that returns the image and the headers on the image response itself, not the frame metadata

like this?

first image is the response from the server

second image is that being called from the generateMetadata function of the nextjs frontend (I tried implementing framesjs but it felt like an overkill because this is the only part of the frame that is rendered from this app, the rest is a separate frog server)

i would use a tool to fetch the image and inspect the headers to be sure…browser dev tools should do the trick