Content
@
0 reply
0 recast
0 reaction
JB Rubinovitz ⌐◨-◨
@rubinovitz
I'm having trouble getting frame data for frames where there are multiple cast embeds. It looks like the Warpcast API has the frame data but the Neynar API says the metadata is pending? https://explorer.neynar.com/0x1f44e8b9f2c3a2feac92cc075146b1c5a1f5172e
1 reply
0 recast
1 reaction
JB Rubinovitz ⌐◨-◨
@rubinovitz
It looks like the API populated after I posted this. Now I'm confused
1 reply
0 recast
0 reaction
JB Rubinovitz ⌐◨-◨
@rubinovitz
previous json here https://gist.github.com/rubinovitz/5a5dae7f405b416831f26a95e5634437
1 reply
0 recast
0 reaction
Manan
@manan
@rubinovitz 1. frames metadata is always populated under the "frames" key inside the "cast" object. frame metadata is independent of the embeds object and the pending status under it. 2. cast indexing is instant but the frame crawling is async. this is a deliberate choice because we don't want frame server 404s to affect cast indexing. and so the async frame metadata fetches might lag by a few seconds to few 10s of seconds at times. If there's a lag beyond that, then either we failed to crawl the frame due to a bug on our end or the frame server.
1 reply
0 recast
0 reaction
JB Rubinovitz ⌐◨-◨
@rubinovitz
Got it. It seems like for casts with multiple embeds including a frame neynar isn't indexing the frame for a while, but the Warpcast API does. E.g. another one https://explorer.neynar.com/0x60df24f4c3472b1b9d61857c3d87c7627e3832b4 Don't know how to handle this as a client. Should I be indexing frames myself?
1 reply
0 recast
1 reaction
