frames

That was a quick copy https://reflect.site/g/yoginth/hey-portal-open-graph-spec/cd7225f128274da382f1f516e7e63f15

Senior prompt engineer. Shipped on farcaster: @larrybot, @qdau, @frames, @framesfun, /open-frames, farcasterchannels.com, farcaster.id, @mod, @search, @discove

1000 different custom OG properties incoming

twitter:frame
facebook:frame
...

maybe it could just use idk, JSON-LD schemas instead 😂?

no signatures? they why even bother changing fc to hey, they could have reuse existing frames

now people need to rebuild

BDFL of Quilibrium, Eng @ Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

The open web is dead, long live the open web. ⌐◨-◨

Building Farcaster

Right but this is part of the Lens API. So the client can just exchange a signed message for an API token that can then be used by the Lens API to do the dispatching, etc.

Any action outside the Lens API, such as signing a message for a Frame/Portal, has to be performed by the client which doesn't have the key.

Not necessarily, a Lens profile can set a dispatcher address (most commonly Lens API) so authentication can be handled external to the wallet (access tokens).

I personally don’t set a dispatcher because I want complete self-custody, but it’s an option.

Frames in their current form are extremely simple and built on OpenGraph so it'll be easy for anyone to implement them.

The main issue Lens clients like Hey will have is that they all work with external wallets so they'll require users to sign a msg.

Big problem with Lens UX in general.

Oh my god look at this landing page
https://reflect.app/