arweave

https://arbr.pro/local/farcaster/frame/VLywIGV7bTMmHStgregDvo2dNmEJP3KuL-qRz1sOdLo

A simple "dynamic" frame POC 100% hosted on Arweave, resolved through an AR.IO gateway. Basic Farcaster frame support is coming to gateways after https://github.com/ar-io/ar-io-node/pull/98 is merged!

Farcaster Product Studio @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

🅿️ kay/kay

🎇 C̶̣̑h̵͖͋â̷̟ö̵̪́t̸͉̑i̴̪͝c̸͙͂ ̸͖̍G̵̠̈́ö̸̳́o̴̳̕d̶̨̐

🔄 Writer+Dev

👨‍💻 Editor-in-chief & marketing lead @developerdao

🐘 Arweave Enthusiast

COO @ PDS.inc, building permanent data solutions like ArDrive.io & ar.io on /arweave

Homepage: https://jonniesparkles.ar.io

love this! are there any current guides? will not get to experimentation before weekend/next week :(

We can write a quick guide once the PR is merged.
For this simple frame to work I just uploaded the assets to Arweave, created the frame 2 html pointing image to an ar.io gateway/tx, uploaded frame 2, created frame 1 using the txID for the image and post to frame 2 using /local/farcaster/frame/id endpoint.

Ah, the GW simply has another endpoint just for frames that accepts POST and GET?

What's the reason for "local" in the URL?

Ah, makes sense.

Thanks.

Now static frames are easy 🤩

Was a real struggle without POST and without button targets.

My understanding is that "local" is a convention for "experimental".
@djwhitt can explain in better detail!

You’re right.

“local” was chosen because for now you need to choose a specific ar.io gw to use. In the future when ar:// protocol starts to be accepted you will not be forced to point to a specific gw