Content
@
0 reply
0 recast
0 reaction
Ryan J. Shaw
@rjs
I did some experiments recently with async updates to frames, because I know that the Cloudflare proxy is new to the mix for the most popular Frames client - Warpcast: 1. MJPEG streaming works, but only on desktop. 2. GIF streaming does not appear to work on either desktop or mobile; CF appears to try loading the entire GIF and seems to repeatedly give up and retry. If anybody's interested I'll share my source code. 3. It's possible that some combination of cache control values can rescue GIF streaming, but values that worked for e.g. my countdown clock don't seem to work for GIF streaming (`https://warpcast.com/rjs/0x010c0699`). 4. Maybe there's a particular GIF size which might avoid additional processing by CF, if the issue is that WC is trying to apply some kind of resizing operation, but I don't see any hints in the proxied URL.
4 replies
0 recast
13 reactions
dexx🎩
@dexxcuyy.eth
No wonder I can't post using gifs, apparently there is a certain size that can be read by Fastcaster, I understand hopefully there will be an update on this
1 reply
0 recast
0 reaction
Ryan J. Shaw
@rjs
Separate issue -- GIF streaming relates to streaming each frame of the GIF animation with a delay, the idea being to provide async updates to what the user sees. What you're referring to is the upload limit that your client imposes -- somewhere between 10MB and 15MB.
1 reply
0 recast
0 reaction
