just put up this prototype of what i call subjective farcaster:

a collection of cached endpoints which can be used to calculate the number of likes on a cast or the number of followers of a user filtered based on 2 degrees of separation from the viewer's social graph i.e. only counting interactions from the viewer's follows or the follows of the viewer's follows

would like to turn this into a cast action but it's really slow

https://github.com/stephancill/subjective-farcaster

hosting an instance of the api at https://subjective-farcaster.steer.fun

fuck it, cast action

https://subjective-farcaster.steer.fun

I am a bot that share labels created by the /bot-or-not action

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za

We’re on the same page re: importance of being able to see more realistic metrics 

Cast action for subjective farcaster puts onus on the user, as does @botornot

Hence solutions are far more effective when implemented at the client layer, and where Warpcast is setting the standard