Farcaster

A lot of complaints recently that Farcaster doesn't have enough "beef".

I'm happy to fight with you.

“A protocol is only as good as the number of independent and thriving clients … on it” 

https://danromero.org/product-led-protocols.html

There’s no third party thriving clients.

Third party client devs’ requests and wishes (like decentralizating channels) have been deprioritized for months and thus they cannot permissionlessly innovate, nor compete meaningfully on many aspects.

Have you changed your mind since writing this @dwr.eth, or is Farcaster no good?

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

Professional client for people who live on Farcaster (/fiids). Available at https://www.fiids.xyz

Senior prompt engineer. Shipped on farcaster: @larrybot, @qdau, @frames, @framesfun, /open-frames, farcasterchannels.com, farcaster.id, @mod, @search, @discove

It’s funny because when I joined Farcaster in October 2022, the whole thriving third-party client ecosystem narrative is what sold me on the protocol. The Warpcast team also dropped the qDAU focus for fake growth, and now they’re circling back, trying to fix the spam and farming issues, but only for their app. Take a look at @fiids, it's a great client but suffers from an outdated solution to the spam problem: the power badge

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

I did not say anything about solving spam at the protocol level in the msg above, although I do think it’s worth exploring. 

What I would do differently: 

If we attempted to onboard users through a partnership, similar to what was done with Coinbase Wallet, and quickly found that it was bringing in low-quality users, I would stop it immediately.

I would discourage memecoin projects from hijacking replies for tipping, and I’d be very cautious about them despite their permissionless nature, if I were concerned about the legal implications for all users on my platform.

As the dominant client, if I decided to introduce features like a power badge, I would do so with input from the community and wouldn’t suddenly abandon it. My goal would be to ensure that all clients can use the same filtering system as ours, maintaining a consistent user experience across platforms.

how could they solve it on the protocol level?

if you want the protocol to remain permissionless the only way is client level filtering as anything else is protocol level -> not permisionless anymore