frames-devs

frog.fm

frog@0.11.4 released with a useful update.

Now you can define a separate image handler and use it in the frame response.

Why?
- Complex images increase the size of the query parameter's `?image` value, and browsers cut it off at an unspecified length, which corrupts the rendering;

more in the thread ⬇️

Big update to Frog to add separate image handler routes, which fixes two common frame challenges:

1) Dynamic initial images. Your initial frame can update to show the state of an auction, the price of a token, etc.

2) Complex layouts. Above a certain size, image rendering would fail when browsers truncated the URL.

I'm eth newbie..just learning
(working on @farcaster)

terminally.online