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

check this one vrypan

https://github.com/dalechyn/fhub/blob/main/src/Internal/Actions/Warpcast/getFullCastHash.ts

Pls, pls, pls, @v, @deodad, @horsefacts.eth! I know that Product wants short, easy on the eye URLs, but devs are supposed to help devs. :-)

Can you add the fid and hash in the HTTP headers of cast pages, so that we don't have to resort to this type of hacks? Or provide an API endpoint that gets a Warpcast URL and returns the fid and hash?

@dalechyn.eth here makes his app pretend to be twitter, fetches the page, parses the HTML, finds the OG image tag, and extracts the hash from the image URL!!! This can't be the right way.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

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

terminally.online

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

23. Co-founder of @beliefs - @launchtokenbot (beliefs.social). Collaborator at /frogfm.

some kind of cast lookup service by first 4 bytes in Warpcast API could be really nice!

so that a request to a page that shows cast returns cast fid and hash in response headers?

i can tell that in nextjs it's pretty tedious to do

I think the right way to do it, is to have standard HTTP headers. This is something any client can implement, so it would work for Warpcast URLs, and Supercast URLs, and any other client that adds the right headers in their responses.