Farcaster Devs

Little annoyance with the Mini App Preview Tool on @warpcast for web – I’m using a free ngrok.com account to tunnel my `localhost:5173` app and finding myself pressing “H” in DevTools to manually hide the white `<div>` covering the `<iframe>` so I can click ngrok’s one-time “Visit Site” button. Then I have to refresh the page so the mini-app can actually initialize with the `sdk.actions.ready()` call as intended.

https://warpcast.com/~/developers/mini-apps/preview

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links | opinions are my own

Makes sense.

But now I‘m thinking, just adopting EIP-6963 on both the Farcaster client and the mini-app side could drastically simplify this and remove the need for all this bespoke initialization logic 🤔

Feels like there should be a more automatic / platform-agnostic way to signify mini-app “readiness”, like a simple namespaced JavaScript event?

(Maybe just adopt EIP-6963 since it’s resistant to race conditions and it’s  EIP-1193 provider objects all the way down anyway?)

Feels like there should be a more automatic / platform-agnostic way to signify mini-app “readiness”, like a simple namespaced JavaScript event?

(Maybe just adopt EIP-6963 since it’s resistant to race conditions and it’s  EIP-1193 provider objects all the way down anyway?)

https://warpcast.com/darrylyeo/0x5c60e70a

What’s the cost of importing and initializing `@farcaster/frame-sdk` on every page load if someone were to use my web app outside of a mini-app context? Is there an alternative flow that doesn’t rely on this dependency?

/frontend dev (HTML/CSS)・founder/decentralized data wrangler /blockhead・contributor /ethglobal /walletbeat・hackathon bounty hunter・music maker・dropout・nomad・25

https://warpcast.com/darrylyeo/0x244b7782