PSA

socket error in frames.js today?

is due to farcaster nemes hub downtime

you can pass a custom hub url to the second argument of ‘getFrameMessage’ and ‘validateFrameMessage’

here’s an option

https://hub.freefarcasterhub.com:3281

Building open source via @frames, /open-frames to help Farcaster and decentralized social win. a16z CSX23. Side proj: farcasterchannels.com farcaster.id @search

If times do not ask your best part, invent other times. cit. Baolian book II vv 16-17 Head of Engineering @outlierventures, former @consensys

hey @df does it work https://warpcast.com/~/developers/frames ?

In the console:
Uncaught (in promise) Farcaster API Error: postFakeCastFrameAction 400 - Failed to post fake frame action: write EPROTO ...

First frame load correctly.

Good to know! Just spent two hours trying to debug this issue. Wondering what I was doing wrong. FYI @poppunkonchain

i'm using an older version of framesjs (0.0.4) - so i had to set a FRAME_HUB_HTTP_URL env variable

btw, i couldn't get it to work with the freefarcasterhub. in the end i used https://hub.pinata.cloud 

(thanks to https://www.pinata.cloud/farcaster)

Wonder if there is any downside to removing the signature validation for a frame that's only for fetching and displaying an NFT.