Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Protocol @ farcaster, solarpunk, paulfletcherhill.com

@dwr.eth and @v brought up the concept of protocol-level embeds coming soon(and @pfh touched on it in a GH discussion I'll link to below)

I'm very bullish on the idea & want to share the details and thoughts I've gathered so far:

https://github.com/farcasterxyz/protocol/discussions/71

https://warpcast.com/dwr/0xae6c55

building /cortex, hacking /farhack, yapping /dylan | dylansteck.com

Another use-case that @dwr.eth mentioned -- which was timely bc/ of the new longcast feature by @jam -- is having a client quickly render long-form content from Jam/Paragraph/Arweave/etc in an instant, kinda like the instant reader view in Telegram

Dan said Google AMP had hoped to be that snappy but they never got there

Some other examples of embeds that @pfh touched on in GitHub discussions are:

- YouTube video
- News article
- Farcaster cast https://i.imgur.com/bjiR5xV.png

What excites me even more is embeds enabling interactions across Farcaster-integrated apps.

What if you could watch an @unlonely clip or RSVP for a stream directly from Warpcast? Or if you could see a graph with data generated from farcaster.network directly in a cast as an embed? 

There are infinite possibilities.

Another thing about embeds that excites me is the potential for a community embed store or schema. 

As @v touched on in this GitHub discussions comment, it would be helpful to create a process for creating embed schemas so that developers have a structure they can work with. https://i.imgur.com/YYcojtK.png

This could be the equivalent of raycast-extensions for Farcaster, something I'm sure many people have been waiting for.

I'm excited to see how this protocol-level feature plays out because of how important I think it is, and I'm going to try and help out however I can, whether that's commenting or creating schemas.

And that's the end of the 🧵!

Also linking to @dwr.eth's tweet about the GitHub discussion below:

https://twitter.com/dwr/status/1644357198699728896

From what I heard in the Clubhouse room last night, each cast has two embeds at the protocol-level. Soon we'll see more native embeds that can let clients show more rich data.

eg. instead of an OpenSea link for a NFT, you input the contract address/token ID/chain ID and the client can present a lot more info.