Full-stack digital product consultant @ BoundCorp.net - Regenfrogs.xyz - goldmongers.xyz - Reno NV

This feels like it’s getting unnecessarily personal (Google and then get back to me), so will try to keep it focused on the issues.

1. What current problem does Hub implementation diversity solve?

2. Shuttle is open source. We built it with feedback from folks like Neynar and Airstack. DCs and channel creation will be decentralized after we stop iterating on the core surface area. We don’t want to have many breaking changes for protocol primitives. 

3. Long casts were a backward compatible change. If it was breaking we would have moved slower. We also reach out to the developers in the ecosystem that regularly attend the open dev calls, have clients with a large number of active signers and anyone who reaches out to us.

4…

re 2. 

Shuttle is open source yes, but we still need to implement an app using it to replicate all the data

Since the schema is pretty much standard (old replicator) and the team already has an implementation (for WC), its not clear why the app implementation is not open sourced

Working on open-sourcing our implementation to replicate standard schema

building /wildcardclub

(prev. @alliance, @ycombinator, @0xppl)

The app can be versioned, each change is opt in explicitly

Yes absolutely, this is much lower priority. 

We’ll open source our bit for reference.. this was just about preventing repetitive work.

DCs >> channels >> everything else

Sounds messy. 

fwiw, we've asked other client developers and open sourcing tends to be much lower on the priority stack relative to growth, DCs, frames, channels, etc.

I mean you seem more interested in DCs than open source Warpcast?