Content
@
https://warpcast.com/~/channel/frames-v2
0 reply
0 recast
0 reaction
artlu 🎩
@artlu
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)
3 replies
0 recast
4 reactions
Tony D’Addeo
@deodad
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
1 reply
0 recast
1 reaction
artlu 🎩
@artlu
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
1 reply
0 recast
1 reaction
Tony D’Addeo
@deodad
Yea all fair. Some of the challenges are intrinsic to the model which as you point out is closer to a PWA But also think there’s a lot of low hanging fruit in terms of docs and “defaults” for developers For instance, Next is kind of a horrible default since their model is to always set everything max-age and then when you deploy a new version they manually bust their CDN cache. But anyone who’s seen the image or downstream CDNs like Warpcast get broken by this model. It’s confusing as hell
0 reply
0 recast
1 reaction
