frames

Not sure signed data in frames should be Farcaster specific

Would like to see params that specify where the signature is coming from (loose address, FID, etc), so web apps decide what’s allowed (probably in their own initial response)

Otherwise expect a lot of redundant “OG” tags to support multiple networks

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

@v / @dwr.eth any thoughts here? also totally understand if the intent at this stage is network capture / growth

yes, intent is for it to be more generalized. this was just fastest to ship first. 

if a more generalized form was available, whats the first thing you'd build with it?

i think it would be mostly for translation layers into existing services like discord or telegram and potentially interop into new services