frames

Announcing... Open Frames

Open Frames is a draft specification for Frames that work anywhere.

If you're interested in bringing Frames to your ecosystem or app, DM us, we'd love to chat.

XMTP is launching Frames support using Open Frames today.

Read more:

Announcing... Open Frames

Open Frames is a draft specification for Frames that work anywhere.

If you're interested in bringing Frames to your ecosystem or app, DM us, we'd love to chat.

XMTP is launching Frames support using Open Frames today.

Read more: https://github.com/open-frames/standard/blob/v0.0.1/README.md

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

It is missing a major thing. Some sort of client identifier is required from the very first frame request from the client side. 

That allows the frame server to render correct tags from the very first frame.

We can change the spec or it can be the very first improvement proposal. Thoughts?

the frame server should render all the tags from what protocols it supports. What problem does your suggestion solve?

do you mean the first GET? how would this work with static html websites? in first POST payload doesn't work because that POST already is signed by a specific protocol

Why extra rendering? Why can't the client app info come from the first payload?