Content
@
0 reply
0 recast
0 reaction
rish
@rish
a problem we consistently hear from developers is not knowing what content is behind embed urls in a cast now @neynar returns `content_type` for all casts w/ embeds, sample screenshot from /cast API: docs.neynar.com/reference/cast open to hearing what other metadata we should provide h/t @tybo for the work 🪐
19 replies
17 recasts
85 reactions
jtgi
@jtgi
great ship, I was doing bad things to acquire this. Not a specific need for me but prob aspect ratio / width+height next. Useful for client and layout problems with jitter. L
1 reply
0 recast
1 reaction
rish
@rish
you do this for the webhooks you get? what's the end use case for you? cc @manan @tybo
1 reply
0 recast
0 reaction
jtgi
@jtgi
ya you can include/exclude content in your channel based on embeds.
1 reply
0 recast
0 reaction
rish
@rish
ah interesting didnt know that. okay you should try out what we have and see how well it works for you. its optimized for API requests right now and not webhooks (because webhooks are optimized for immediate delivery) so there is a chance some webhook events will be delivered before the content metadata is fetched if you see that happening let us know and we will tweak it on our side
1 reply
0 recast
0 reaction
jtgi
@jtgi
Will do. I refetch every webhook request for that rule because of that already.
0 reply
0 recast
1 reaction
