frames

frames-devs

Gonna re share this because I want to see it happen

The interface between the Frame and the client is currently spec'd to be very limited. I think there is an opportunity to open this interface up to also providing "developer legos" by allowing the Frames in v2 to call an action that opens a limited version of Frames v1 (frames v1 without the "POST" action, so it's only 1 step frames). This allows third party programmability at this permissions layer between Frames and Client, enabling Frames to interact with eachother. As it stands, Frames v2 have no way to interface with each other, or any of the existing developer legos via a trusted context. The trickiest part of implementing Frames v1 for clients was the complexity and performance of state transitions between frames. By limiting Frames v1 to "one step Frames", you get the safe composability without adding much complexity.

https://github.com/farcasterxyz/protocol/discussions/205#discussioncomment-11498632

what made frames v1 new and interesting was it enabled cross-website actions. 

Press a subscribe button in a frame on warpcast, get subscribed on paragraph.

Frames v2 don’t do or even leverage this, and are more similar to an embedded browser.

The proposal below leverages the best parts of frames v1 as a cross-app actions authorization modal, without the performance downsides

Building Larry, FOSS via @frames, @framesfun /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id