the easiest web3 form builder, trusted by coinbase, farcaster, ens, optimism, alchemy - www.deform.cc

Noticing differences between Warpcast state & protocol state, likely due to shadow-banned users on Warpcast.

I foresee @deform customers being confused about the discrepancy since Warpcast is the de facto client. How would y'all recommend getting Warpcast's version of the state of the world?

can you share the differences you’re experiencing?

for example, my follower & following count from Warpcast vs the protocol data via Neynar are off

observing similar discrepancies with likes/retweets of casts

👨‍💻 /uno and /outside, @unofficial

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

🪐 Building @neynar, join us in /neynar & /nfs | ex-Coinbase | manan19.twitter

working on farcaster infrastructure @ /neynar, neynar.com  🪐   /rish 

best farcaster developers build on neynar.com | /neynar

@neynar @rish @manan @dwr @v do yall have a philosophy on how developers should handle warpcast vs protocol api discrepancies

I build web3's most powerful referral link @deform

Every client will do it’s own interpretation of Farcaster data

Yeah we can provide filtered data already if folks want but there’s no way to align it 1:1 with warpcast since their filtering algorithms aren’t public

Even if you did your own indexing, it would align 1:1 with Warpcast? So the numbers won’t match either way

That makes sense!

Are there any plans on the Neynar roadmap to provide some kind of "filtered" API for data that somehow aligns with i.e. Warpcast client's interpretation of Farcaster data?

Would be especially useful for us to not have to do our own crawling, indexing, reputation building, etc.