Proposal:

Add markdown support to the frame spec.

fc:frame:markdown

The client will render the markdown fully.

The current approach of screenshot essays or  frame servers generating an image results in a poor experience.

html frames
then add css for styling
then add js for interactivity
then fc clients become browsers with social and payments built in

there were talks of doing text/html frames but i guess it fell in priority because generating images didn't turn out to be that difficult with frameworks like satori or frame kits like frog and framejs. although text frames would improve performance.

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

Building /warpcast and /farcaster

— gabrielayuso.com

HTML frames would be interesting but can come with a wider can of worms. Text is much simpler, markdown just provides more formatting optionality without complicating much.

there were talks of doing text/html frames but i guess it fell in priority because generating images didn't turn out to be that difficult with frameworks like satori or frame kits like frog and framejs. although text frames would improve performance.

https://warpcast.com/moe/0xfcec7bdb

Investing in Farcaster

(link to blog with actual URLs below)

Congrats @dwr.eth @v,  grateful to be part of the story.

Instead of screenshot essay or use the "read inline" feature from paragraph frame with one image at a time, the frame could just render the post markdown. Its simpler to put text on meta tag than render images.

https://github.com/o-az
—
https://x.com/awkroot

Instead of screenshot essay or use the "read inline" feature from paragraph frame with one image at a time, the frame could just render the post markdown. Its simpler to put text on meta tag than render images.
https://warpcast.com/gabrielayuso.eth/0x60350f7f
https://warpcast.com/jesse/0x26d5ceaa

Since all frames are pics and buttons (afaik), this then introduces text-based frames?