8 replies
2 recasts
31 reactions
1 reply
0 recast
3 reactions
1 reply
0 recast
1 reaction
1 reply
0 recast
1 reaction
1 reply
0 recast
1 reaction
1 reply
0 recast
1 reaction
There's still a missing piece in my mental model. Can you help me understand better?
Right now, the frame's entrypoint the image at is broken on warpcast/fine on recaster. If I cast again, it will work again. This is consistent with my mental model of how Warpcast caches cast content.
Inside the user flow, there should be no caching, only proxying (?). These dynamic images get generated as part of an interactive flow. Why are they broken in Warpcast, and not broken elsewhere?
Practical question 1 (on me to answer, not on you): if I upgrade frog, will my old cast magically get better? I am more interested in resurrecting the old cast than a fresh new one, tbh. That feels more credible, less bait-and-switchy.
Practical question 2: will Frames V2 have similar dependencies and/or fragility that I can design around? It seems ... for the dynamic OG image displayed on the landing page, maybe yes maybe no? Inside the flow, no? because the interaction all happens in my own sandbox? 1 reply
0 recast
1 reaction