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 (beliefs.social). Collaborator at /frogfm.

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.

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

“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.

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.

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

𝚆𝙾𝚁𝙺𝙸𝙽𝙶 𝙾𝙽: @vision 👁️ ✦  ensdata.net ✦ pugson.net/rfe ✦ 𝙿𝚄𝙶.𝙴𝚃𝙷 ✦ 𝙿𝚁𝙴𝚅: @rainbow 🌈 

Thanks! But I don't want to add more dependencies. Fargo for example, connects directly to hubs, no third party APIs. In order to use Warpcast URLs, it's OK to use warpcast, but adding one more dependency, it's a no-go for me. Could be useful for others!

replace warpcast.com with farcaster.tv 

https://farcaster.tv/vrypan.eth/0x2b0263b4

/grey - terminally online dad & spouse, building products on frontier solutions w frontier people.

Is this at the Warpcast api level or farcaster hub data?

FID and HASH in headers would be very nice (DX).
Great idea @vrypan.eth