Content
@
0 reply
0 recast
0 reaction
Tony D’Addeo
@deodad
crowd sourcing ideas for a frame tips, tricks, and pitfalls what do you wish you had found in the docs when working on frames?
3 replies
2 recasts
17 reactions
K
@kijijij
I would have loved to stick to JSON and not HTML so I can deploy frames on AWS / GCP etc without running vercel type app.
1 reply
0 recast
1 reaction
Tony D’Addeo
@deodad
JSON would have some nice benefits and is something we'd consider in a v2 but not seeing how that relates to deploying to Vercel vs AWS / GCP? you can deploy anywhere you can deploy a node app?
1 reply
0 recast
0 reaction
K
@kijijij
I could use API Gateways to return static JSON values ( or from S3 or similar cloud storage ). I believe its possible but did not check. Would be nice that users can upload their images and pin that carousel to their channel / profile.
1 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
Can’t you return html there too? As html file with meta tags
2 replies
0 recast
0 reaction
K
@kijijij
Of course one can return HTML , hand writing JSON vs Meta Tags, JSON is easier. HTML has so much repetition of <meta> ... and then "type", in JSON that's concise and clean. Also you can update or override JSON property way easily because it's object like properties, for HTML that's not the case. I am not insisting or asking to change immediately. HTML was chosen I believe because OG / RDF / OWL parser exists and they can be used to pull first page i.e. GET /frame/URL easily and can be embedded anywhere.
1 reply
0 recast
0 reaction
Samuel ツ
@samuellhuber.eth
we'll get to something like JSON eventually. If you have a specification in mind and want to help us get there faster: open a Discussion: https://github.com/farcasterxyz/protocol/discussions/new?category=fip-stage-1-ideas
0 reply
0 recast
1 reaction
