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.

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

Building /warpcast and /farcaster

— gabrielayuso.com

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

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

I agree text is nicer than images. So to understand you correctly you're proposing introducing text-based frames with markdown support?

Great idea and straightforward to implement if/once farcaster allows text-based frames

Yes.

Ideally clients use a proper markdown renderer to support the spec (might want to decide the base md extensions to support).

Clients are free to handle the content as they please, either render the entire thing or render part of it and add a way to expand, etc.