Farcaster

Wrote my thoughts on the FIP: Frames v2

TLDR; Generally happy with the direction, but I think there's a missed opportunity with actions as they stand, as Frames in v2 won't be able to interact with each other in any way. 
By adding a new type of Frame action that is a limited version of Frames v1 we can get the best of both worlds; performance and expressivity via Frames v2, and safe composability from a limited version of Frames v1.

Wrote my thoughts on the FIP: Frames v2

TLDR; Generally happy with the direction, but I think there's a missed opportunity with actions as they stand, as Frames in v2 won't be able to interact with each other in any way. 
By adding a new type of Frame action that is a limited version of Frames v1 we can get the best of both worlds; performance and expressivity via Frames v2, and safe composability from a limited version of Frames v1.

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

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

worth noting that this FIP makes frames.js as it is obsolete, as well as a bunch of things we've been working on that we were about to release

also reality check; these things are called Frames as well. No longer "App Frames". I don't see a world where Frames v1 are not deprecated by Warpcast within 6 months. These are the replacement, not an addition