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.

Wait, what's "MM"? 🤔

Ⓜ️ 3.2x cc @gt @betashop.eth

Head of the Moxie Mafia 👾
@moxie_xyz - create and own Creator Coins (fka "fan tokens") -- & soon also: Creator Agents

Full-stack web3 developer, learn more about my projects here: https://github.com/tempe-techie

CEO and Founder of $BLEU

Developing infinite memetics AI Agent @elefant


lebleuelefant.com

Oh, makes sense, not sure how I didn't think of that one. Too many abbreviations 😅

Merkle Manufactory
The legal entity / company behind the development of the
Farcaster protocol and Warcpasct client

Separate / different entities from moxie/airstack