frames

Early principles for building good Frames:

1️⃣ Open source your Frame so we can see what it does.

2️⃣ Be responsible with signed data. Frames know who pushed which button.

3️⃣ Use the body of your Frame URL to return an about page when the user clicks the link.

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

(This is true untethered thoughtfluencing because I am still working on my first Frame)

Builders, feel free to submit a PR or DC your frame's OSS code!

https://github.com/0xPetra/awesome-frames

cc/ @kindness @artlu @cassie @riotgoools @kugusha.eth @jtgi

4. Add your OS Frame to this awesome-frame repo

5️⃣ Use the page at your Frame’s root URL to render fallback UI using Sign In With Farcaster. If a user’s client doesn’t support Frames, they can click through and use your app. (Works anywhere on the Web!)

5️⃣ Use the page at your Frame’s root URL to render fallback UI using Sign In With Farcaster. If a user’s client doesn’t support Frames, they can click through and use your app. (Works anywhere on the Web!)

https://docs.farcaster.xyz/auth-kit/introduction

4. Add your OS Frame to this awesome-frame repo

https://warpcast.com/0xpetra/0xbcdd9da5

Even if it's open sourced how is there a guarantee the deployed version matches what's in the repo?