frames-v2

Feature request: a way to clear all cached info about a frames v2 host.

Pain point: I use a placeholder for minor things like Splash  Background Color. When I go back later to update it, I don't see the change because I've already asked Warpcast to ingest the frame (not the right word, but that's how I experience it during development iterations)

https://SassyHash.artlu.xyz/download

See pinned cast frame for more.

PFP is my Native.fun Print, genart unique hash of wallet txns

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

yes, this is a DX pain point. It takes quite a bit of effort to learn the mental models. In web2, maybe I can just delete my Vercel app or Github repo, and start over. Easy for a beginner with Frames V2 (it me!) to try something, not see any effect, and think I'm on the completely wrong track.

The Frames V2 mental model seems more like Web Workers and PWAs, where I might push a new version and only eventually expect it to get updated on the users' local copy. But at least I can instruct them to delete and reinstall.

And as for Cache-Control headers, good luck if they are set to last forever. This seems analogous to things embedded in casts.

Would it be good developer advice to:
- version your `farcaster.json`
- delete cast and re-cast

challenge is there are many things in many caches

- manifest, easy to refresh in devtools
- frame embedded in casts, as many of these as there are casts, hard to refresh as they are in users feeds
- images, cached based on hosts Cache-Control headers in users browser, Warpcast image CDNs and any upstream CDNs

hamst.art $hamster /hamster 
martinvr.eth 
deploy.degen.eth

thanks, good tip!

my understanding now:
- a frame v2 can have a container which is a cast, or it can have a container which is an installed frame (and maybe some more things in the near future).
- the installed frame container's cache can be refreshed by re-validating the domain signature
- a cast's cache can never be refreshed. but you can always send a new one

- the container is either the `farcaster.json` file, or the frames meta tag inside the html. The meta tag contents do not belong in your web page, even though they live inside the same html file, and hence do not retroactively change casts when you change them. Conceptually, they instantiate a new container each time they are viewed by a client

- the client may choose to cache this for good reasons. Or to simply pass it through, for other good reasons

Did you try to validate the domain signature again from the WC app? That updated it for me

In brave browser for me it’s been working to have the frame url open in its own tab and run the clear cache command to reset it for the warpcast dev page preview stuff. I wish there was just a local testing interface like for v1 frames though.

Also very unrelated but loving Highlander im starting s2 now thanks!