dylan pfp
dylan
@dylsteck.eth
@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
1 reply
0 recast
0 reaction

dylan pfp
dylan
@dylsteck.eth
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.
1 reply
0 recast
0 reaction

dylan pfp
dylan
@dylsteck.eth
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
1 reply
0 recast
0 reaction

dylan pfp
dylan
@dylsteck.eth
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
1 reply
0 recast
0 reaction