Content
@
0 reply
0 recast
0 reaction
horsefacts
@horsefacts.eth
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
12 replies
6 recasts
49 reactions
Leo 馃馃帺
@sha25leo.eth
I think we're just one step away from creating a miniapp. By adding fc:frame:button:$idx:app_url within the frame, along with this postMessage, I'll be able to develop web games or more interactive content.
1 reply
0 recast
5 reactions
0xLuo
@0xluo.eth
Perhaps mini apps can already be implemented through composer actions? It's just missing a more convenient entry point for mini apps. https://x.com/0xHaole/status/1812893210479587736
1 reply
0 recast
5 reactions
Leo 馃馃帺
@sha25leo.eth
As long as the frames is used as an entry point for the app, or the actions is used as an entry point, both options are very smooth.
0 reply
0 recast
1 reaction
