Goksu Toprak
@gt
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.
3 replies
15 recasts
59 reactions
David Furlong
@df
We’ve been told repeatedly over the year that the strategy is to forgo for a time interoperability of certain things in the name of MM resources towards DAU growth. Yes, there has been some progress on the protocol - but there’s also been new divergence of the client and protocol. in 2023 with the initial push to hubs, MM was intently committed to interoperability & the protocol aspects. This changed with lackluster growth, and it was repeatedly argued that growth was more important than allowing third party developers to build on the new primitives being introduced by warpcast (like channels). Is that not backpedaling?
1 reply
0 recast
0 reaction
David Furlong
@df
I think what may be happening is that since dev day (or cb interest) the backpedaling has stopped/slowed down, and interop is somewhat a prio again. The point is the protocol aspects were sidelined for a time, and no reason this won’t happen again
0 reply
0 recast
0 reaction
