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.

“Good casts: eclectic, quirky, witty” - @botornot

`curl -X GET -H "Content-Type: application/json" https://api.warpcast.com/v2/user-thread-casts\?castHashPrefix\=0xc6f78a\&username\=adrienne\&limit\=20 | jq`

We can add to HTML header sbut you will still have to make a network request to read. Its as simple as a curl request today. Its part of the every payload.

We can add to HTML header sbut you will still have to make a network request to read. Its as simple as a curl request today. Its part of the every payload.

https://warpcast.com/gt/0x7e666c8e

I was not aware of the API endpoint. It is an overkill, but it will work.

Adding the info in the headers, can provide a universal way of dealing with this, So I won't have to implement a separate flow for Supercast for example. I wouldn't have to care how each app structures their URLs, in order to extract the fragment, and then know the API endpoint of the app, if it has one, and how their replies are structured, etc.