frames-v2

What's the most frustrating thing when building frames right now?

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

- Seems like the sdk requires code to be on the client side instead of the server, that reduces the speed of rendering the frame, which is important for consumer products
- Context data is unauthenticated

🇧🇷🇺🇸-  Book: Making Things Think: https://holloway.com/mtt. Investor in Wander, Carry, Footprint, Merkle Manufactory (Farcaster), Dynamic, Paragraph.

not understanding the first bullet point. gc will you please say more? I'd advocate for moving more to the client side & toss it up on a cdn. is the sdk super heavy & unshakable? Feel like I'm missing something fundamental as the last thing I want as a web3  dev is a backend will lean onhub & onchain as much as possible

Ethereum builder & people connector. Juicebox, Revnet, Defifa & Footy App

devops (another moving part)
centralized (generally speaking)
frame discovery likely via a host app which makes first paint less sensitive to seo (yet I concede slower)

Now your turn to answer a question. See above.