Frame debugger that accurately tells you why your seemingly well-formed html doesn’t work. Someone ship it.

Writer. Building @pinatacloud. Tinkering with a Farcaster native alternative to GoodReads: https://readcast.xyz \ https://polluterofminds.com

what isn't working for? on my plate to make some improvements to it this weekend

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

Is there any chance of extending the post expiry duration to allow more complex executions?

Trying to build a frame that uses an LLM, and I'm realizing the 5 second timeout is going to be pretty prohibitive for what's possible

tldr right now, best bet is start computation on an initial message & deliver results on a subsequent one

patterns are still being explored but for now 5s seems reasonable both for clients to hold open connections & from UX perspective

see this thread for related discussion

Building frames.sh, contact on Icebreaker: https://app.icebreaker.xyz/profiles/g52RAjVQBB2xlN0rIKg-c 

tldr right now, best bet is start computation on an initial message & deliver results on a subsequent one

patterns are still being explored but for now 5s seems reasonable both for clients to hold open connections & from UX perspective

see this thread for related discussion
https://warpcast.com/gregfromstl/0x56ca8e12

yea something like that could make sense

keep sharing and exploring—frames are new and rapidly evolving, just a matter of balancing complexity and prioritization

I shared some thoughts about this. I thought it would be possible for the client to retry if the response code is other than 200, 302, & 503 to indicate progress. I’m guessing a queue is maintained by WC backend so request resource has a cost in any case.