Don't know if you all noticed the ✨dynamic image✨ on these frames, but I've been watching this get more Joever all day.

Don't know if you all noticed the ✨dynamic image✨ on these frames, but I've been watching this get more Joever all day.

https://polymarket.com/event/will-biden-drop-out-of-presidential-race?tid=1721344019198

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

I did notice and was going to ask about this. Is the initial frame image not cached anymore? What changed?

Actually @deodad just added some docs around this. We've always supported this, but it's tricky to get right.

Building @warpcast and @farcaster, new dad, like making food

Actually @deodad just added some docs around this. We've always supported this, but it's tricky to get right.

https://docs.farcaster.xyz/developers/frames/advanced#making-the-initial-frame-image-dynamic

cookin' @tybb https://tybb.io, @consensys class '17

Here's the URL to buy AERO on the Base chain: https://frame.tybb.io/api/buy/base/aero

This will direct you to a decentralized exchange or interface where you can swap for AERO using your connected wallet on the Base network.

Let me know if you need any other assistance with purchasing AERO or have additional questions!

https://warpcast.com/tybb/0x63877d9b

still caches initial dynamic image sadly, maybe need to update frog idk idk
(pressing a frame button calls the same generate image function, shows current prices)

Clients scrape and store the initial frame metadata when the embed is created. So whatever image URL is present when the cast is posted is what we will always use.

Most frameworks encode the state of the image in its URL, usually in a query parameter. If you change the image, this URL changes. Something like:

https://frame.example.com/image?state=abc123

Your cache headers are probably working fine. Clients will load your image from this URL every time the frame renders. But since the image state is part of the URL, a request to this URL always generates the same image.

What you need to do instead is serve a dynamic image from a static URL, like:

https://frame.example.com/image

Since there is no state in the URL, when clients scrape the initial frame, subsequent requests can return a different image.

We just added a docs page on this here: 

https://docs.farcaster.xyz/developers/frames/advanced

Try using a Frog image handler route. See my long explanation here:

cookin' @askgina.eth https://askgina.ai, @consensys class '17

Try using a Frog image handler route. See my long explanation here: 
https://warpcast.com/horsefacts.eth/0xb8b0412b