FIP: Opportunity For Another Curator (Imported) #7
Replies: 3 comments
-
|
vrypan The downside is that it's client-specific but on the plus side, it's really easy for clients to implement. @CassOnMars If you refer to content discovery, this is up to each miniapp, and depends on what they want to do. An algorithmic one, may filter what your social circle interacted with. A filtering one, may just filter the snapchain feed for keywords. A "why did X unfollow" one could find the last cast posted before X unfollowed. A "first cast" miniapp may look for the first cast new users post after they sign up. We already have so many miniapps, that identify different signals: Trending tokens by clout, top posts, bangers, etc. Buoy, WDIM, Cura, Banger, all the tipping apps, could have their own feeds, and users would get a modular feed, they can tailor to their taste. No social app has something like this today. If you mean how users will discover the right miniapp, well, it's not a solved problem, but I think word of mouth is a good starting point. |
Beta Was this translation helpful? Give feedback.
-
|
allemanfredi For these reasons, I would remove the requirement that a curator must also be an active Snapchain node runner and instead rely on reputation. Inefficient feeds will naturally fall out of use, while efficient ones will be adopted. @CassOnMars |
Beta Was this translation helpful? Give feedback.
-
|
vrypan |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
Tastemaking is the dirty secret of growing a social media platform. It isn't easy, it isn't cheap, and it isn't decentralized (yet). The costs of quality feed generation is expensive, resulting in client teams building their own, and having to deal with the inherent costs of doing so. This can be achieved instead as an independent feature of the protocol, allowing curation to live as a protocol primitive rather than an ad-hoc externality of building a farcaster client, enabling the client diversity to grow and amplify each other instead of competing.
High Level Solution
Add a new message type, Curation, which enables tastemakers of any kind (algorithmic, manual, simple like "reply bumping"), which users on the protocol can create, that provides a choice for clients to surface to users:
The idea is that feeds are standardized in a url (e.g. a compliant feed must have a common url shape), and should be open source and scrutinizable (but not mandatory). A basic requirement to add on is that a curator must also be an active snapchain node runner, otherwise it suggests feed generation will be outdated or at least late.
Notes
This is an incomplete draft proposal, a full LOE will be added soon.
Beta Was this translation helpful? Give feedback.
All reactions