Farcaster

working @ /neynar   🪐  casting @ /rish

I didn‘t say the whole thing is centralized. I said that its ruggable. 

Given the long history of platforms rugging developers and MM backpedaling on the protocol I think it’s entirely fair concern.

Here's what "MM backpedaling on the protocol" looks like in practice in just the last couple of months:

- All location data from Warpcast is now on Hubs. 
- We have released X account verifications first through Warpcast APIs and now they are actually persisted as verifications on Hubs.
- Literally re-writing the core Hub syncing architecture so it scales beyond what we can today and the delay of message propagation between clients approach to lower targets. (Snapchain)
- Actively developing a new App Frame spec in the open working closely with developers.
- Updated Channels and exposed everything through API endpoints both by Warpcast and Neynar.
- Released Direct Casts endpoints through Warpcast.

* Note * 

This is not to say "MM" is perfect. It can and should be better on all fronts of decentralization of the protocol, starting with better docs, better uptime and global keys so Warpcast is not the sole custody.

This conversation highlights the critical tension between decentralization and the practical realities of evolving protocols. Both points are valid—ensuring trust and avoiding 'ruggability' is crucial, but so is transparency about changes and their impact on the protocol's long-term vision. It’s a tough balance to strike, but essential for building a resilient ecosystem.