Frontend

Farcaster Devs

We've revised the draft composer actions spec after implementing the first prototypes.

The main change is using postMessage for form-to-client communication, but we've also added a more detailed tech spec.

I'm very excited about these, but embedded forms open a new security/safety surface that clients need to approach carefully. 

I've heard from a lot of builders eager to create composer actions and appreciate your patience while we work out the right approach. If we get it right, it's a foundation for a whole class of new programmable social primitives.

https://warpcast.notion.site/Draft-Composer-Actions-7f2b8739ee8447cc8a6b518c234b1eeb

Looking for broad feedback on the latest composer actions spec. Embedded content and two way client-app postMessage communication could enable a bunch of new programmable primitives, but it's important to get it right.

Looking for broad feedback on the latest composer actions spec. Embedded content and two way client-app postMessage communication could enable a bunch of new programmable primitives, but it's important to get it right.

https://warpcast.notion.site/Draft-Composer-Actions-7f2b8739ee8447cc8a6b518c234b1eeb

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

terminally.online

Solid implementation

What do you think of being able to incorporate some prompts into the composer actions ?
That way when I write "iOS vs Android" and type on "Poll", it's already filled based on my cast