Farcaster Devs

Frame feature request: allow frame revalidation.

Currently, WC caches the frame for a url forever (?). This means that if the frame metadata for a url were to change, and I make a new cast with a url that was already cached by WC, the new metadata would never be fetched.

1/n

Our use case is for an NFT frontend where the frame used changes based on the artwork state (ex. auction, or timed mint)

Currently this change is never reflected, and it always just shows the frame that is cached by WC.

There are some ways to get around this today:
1. Add a "cover" static frame with a continue button
2. Bypass WC response cache by add a unique query param to the urls (like ?t=<time>)

Former is a worse UX, latter is less pretty url, negates the WS cache, and requires pushing query param everywhere.

Yeah, agreed. 1) combined with a dynamic initial image is probably the best option right now, but the fewer clicks the better for everyone.

For anyone interested, rest of the discussion about this happened here:

For anyone interested, rest of the discussion about this happened here:
https://warpcast.com/horsefacts.eth/0xcb05a63d

It is possible to bust this cache with the refresh button in the frame debugger, but there should be a less manual solution.

Two potential solutions:
1. Make WC listen to the frame response cache-control headers
2. Allow programatic revalidation of frames, like the refresh button (which hits an authenticated endpoint)

I believe this is implemented already, see the 2/23/24 changelog entry on here:

likes building things • https://alexgrover.me/links

Not referring to just images. 

Image cache can indeed already be broken using cache-control headers (which is great!)

But, WC frame response cache for a url cannot be broken in a scalable way today.

I believe this is implemented already, see the 2/23/24 changelog entry on here: https://docs.farcaster.xyz/reference/frames/spec

@dwr.eth This is critical for the success of in-frame auctions

If a superrare.com artwork page gets shared before auction begins, any links shared after the auction begins do not render as auction frames unless users manually hit refresh

@dwr.eth This is critical for the success of in-frame auctions

If a superrare.com artwork page gets shared before auction begins, any links shared after the auction begins do not render as auction frames unless users manually hit refresh

https://superrare.com/0xdf15e9edbe4648ac2e2941e07dc4d684d55ac250/voidwalkers-10