Content
@
0 reply
0 recast
0 reaction
Spencer Perkins
@spencerperkins.eth
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
3 replies
0 recast
6 reactions
Spencer Perkins
@spencerperkins.eth
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)
1 reply
0 recast
2 reactions
Spencer Perkins
@spencerperkins.eth
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.
1 reply
0 recast
2 reactions
Spencer Perkins
@spencerperkins.eth
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.
1 reply
0 recast
1 reaction
Spencer Perkins
@spencerperkins.eth
For anyone interested, rest of the discussion about this happened here: https://warpcast.com/horsefacts.eth/0xcb05a63d
0 reply
0 recast
0 reaction
