Content pfp
Content
@
0 reply
4 recasts
4 reactions

Colin pfp
Colin
@colin
I think this is awesome. One of my concerns with Frames was that we'd need to implement a solution multiple times to support Farcaster, XMTP, Lens, [insert-new-frame-protocol-here]. With an open standard, assuming protocols adopt it, this lifts implementation burden greatly.
5 replies
2 recasts
27 reactions

Callum Wanderloots ✨ pfp
Callum Wanderloots ✨
@wanderloots.eth
this is exactly something I was wondering about. I think the more standardized frames become, the more likely they will be implemented in a way that actually stimulates adoption of the underlying protocols. Part of the benefit is that they are so customizable, so the standardizing underlying architecture is +
0 reply
0 recast
0 reaction

Stéphane Zermatten pfp
Stéphane Zermatten
@crypticzed.eth
framing the Internet 🚀 🚀
0 reply
0 recast
0 reaction

jongminkkang🎩 pfp
jongminkkang🎩
@jongminkkang
Good
0 reply
0 recast
0 reaction

Nick Molnar pfp
Nick Molnar
@nickm
We're really focused on getting the developer experience right over the next few weeks, so once you've integrated with Open Frames you can support as many protocols as you want without a million if statements.
0 reply
0 recast
0 reaction

Jawa pfp
Jawa
@jawa
This is so exciting and absolutely the direction I hoped things would head.
1 reply
0 recast
0 reaction