enjoyed this piece from @w1nt3r 

one fun angle to explore for the new frames direction we are exploring: how could we make building dapps easier? some ideas:

- no need for a domain name if primary discover / access mechanism is via Farcaster
- IPFS is suitable for hosting if Farcaster clients are will to pull from IPFS and serve to users from their CDNs
- dapps could assume an Ethereum JSON-RPC Provider will be available if Farcaster clients provide this to frame apps

not a panacea but might be some interesting opportunities to make a difference

enjoyed this piece from @w1nt3r 

one fun angle to explore for the new frames direction we are exploring: how could we make building dapps easier? some ideas:

- no need for a domain name if primary discover / access mechanism is via Farcaster
- IPFS is suitable for hosting if Farcaster clients are will to pull from IPFS and serve to users from their CDNs
- dapps could assume an Ethereum JSON-RPC Provider will be available if Farcaster clients provide this to frame apps

not a panacea but might be some interesting opportunities to make a difference 

https://w1nt3r.mirror.xyz/csZhMabCHXYiUhnQHrje_6da1n0XZGQ7y2QoETkDyPE

You should look closer to what we do with furl.pro.

Example: fc1.furl.pro (hosted on IPFS). Unfortunately, the frame will show a broken image, because I generate a new screenshot every hour but the frame is cached and points to the one generated 2 weeks ago.

Building @warpcast and @farcaster, new dad, like making food

Dad, geek, conversation liquidity provider. vrypan.net (home), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

in your opinion what would be the best  way to have a static url that resolves to an IPFS url?