Content
@
0 reply
20 recasts
20 reactions
ncitron.eth
@ncitron.eth
Should Farcaster decouple clients from algorithms and moderation? We could design a common api specification that allows algorithm providers to be plugged in to any existing client. The main thing against this I think is that it's not clear to me whether the algorithm is actually the main product a client provides.
4 replies
2 recasts
38 reactions
Dan Romero
@dwr.eth
It wouldn't be performant without a lot of work. Modern consumer apps use machine learning and the algo needs to be fast. If it's not fast and supplying a lot of content, people churn.
3 replies
0 recast
32 reactions
ncitron.eth
@ncitron.eth
Yeah but the warpcast algo feed is generated quickly? I'm sure this took a bit of engineering effort but I imagine others can do it. The reason I think this would be valuable is that building a good algo is probably one of the hardest things to do when building a client, so standardized algo services would be nice for clients bootstrapping.
2 replies
0 recast
3 reactions
Dan Romero
@dwr.eth
@slokh how hard was getting a performant feed? iirc, you said that's a lot of work. @ncitron.eth others can do it, but a) a lot of work b) infrastructure is expensive / requires sophistication to maintain and scale
2 replies
0 recast
0 reaction
Kartik
@slokh
we never did an algo feed, we just used openrank / neynar, primarily because it would have been a lot of work/expensive to do a good algo feed which wasn't worth spending our time on
0 reply
0 recast
2 reactions
ncitron.eth
@ncitron.eth
Yeah but isn't this a big reason why clients might prefer to buy a feed from an algo provider as opposed to designing it themselves? Just like clients tend to buy network access from Neynar instead of setting up hub infra and tooling themselves.
1 reply
0 recast
2 reactions
