Content
@
0 reply
0 recast
0 reaction
Dekan
@dekanbro
I'm having issues replying to a cast with the naynar api cast endpoint. Using a parent hash does not seem to work (get a success but does not display in warpcast or users notifications). and using a cast URL in the post (shows up as external). Maybe thats the intended behavior but just checking if im missing something
1 reply
1 recast
4 reactions
rish
@rish
setting a url will set the parent of the reply to be that url, that's as intended by the protocol. you should use cast hash. what is the hash of the successful reply? You can see whether - the hash is on the hub using explorer.neynar.com - is on warpcast by creating a url of the format https://warpcast.com/~/conversations/<hash> Whether warpcast shows it or not or creates a notification is a client level decision. You can use another client like supercast, recaster, etc. to see if other clients are showing it
2 replies
0 recast
3 reactions
Dekan
@dekanbro
here is an example https://warpcast.com/iron-blacksmith/0x947f0492148968f2ffed6f17abf1082cabafc4d8, it does show up in the conversation api when i search by hash, but i do not see it on warpcast anywhere.
1 reply
0 recast
0 reaction
rish
@rish
can't speak to what Warpcast is doing but it shows up on Supercast: https://www.supercast.xyz/c/0x947f0492148968f2ffed6f17abf1082cabafc4d8 it's also on the hubs: https://explorer.neynar.com/0x947f0492148968f2ffed6f17abf1082cabafc4d8 so don't think there's any issues on our side
1 reply
0 recast
1 reaction
Dekan
@dekanbro
Ok thanks! Was wondering if it was a warpcast issue. I'll have to try some other clients
0 reply
0 recast
1 reaction
