frames-devs

new farcaster frame spec proposal

"fc:frame:input:button"
"fc:frame:input:button:(icon | text)" 

what
- adds a button with desired icon or text for input

current problems
- 4 buttons are too limited already but also have to be used for validation, navigation, etc.

solution
👆🏻

@horsefacts.eth @dwr.eth @v

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

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

terminally.online

I have two things related to text input.

A disabled parameter to display text only. I use the box to display data only in the Bandit frame, but having the ability to input text is confusing.

Increasing the text length from 32 to 64 characters.

Increasing the timeout by a couple of sec.

full sack developer intern at /farcards /mintclub warpcast.tools 🔫 my code breaks things :( 


I have two things related to text input.

A disabled parameter to display text only. I use the box to display data only in the Bandit frame, but having the ability to input text is confusing.

Increasing the text length from 32 to 64 characters.

Increasing the timeout by a couple of sec.
https://www.frames.baby/bandit

building www.miini.app | /big-list /co /degen-lotto /farcastles | @ed1t @3dit @3d1t @mox1e | collaborative collections: 420, Degen, Ham, Perlvision, Pi

Yeah, can't make the user wait while the image is generating because it should be a very fast frame.

I'm not sure if I understood it fully. In your case, are there 8 pages of settings that you navigate with buttons? What does the text input do?

it's brilliant but feels hacky - do you think the proposed solution can make things better?