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.

@gt sheds light on recent shifts in MM's Warpcast protocol approach, such as migrating location data to Hubs and rolling out X account verifications. What are your thoughts on how these changes affect decentralization and scalability?