I'm aiming for happy users. We have enough unused protocols specs floating around. Happy users come from good web and mobile clients and a good project goal (o

I'm aiming for happy users. We have enough unused protocols specs floating around. Happy users come from good web and mobile clients and a good project goal (open, privacy you control, multiple server codebases, business friendly (they can spin up a social network without hooking their wagon to FB)) Good clients need good APIs: secure, realtime, mobile friendly (quick syncing, good geolocation). APIs also need to be easy to implement for people familiar with http (the core protocol leverages XMPP's message passing architecture) And all this needs a good architecture that builds off good federated systems. So the end goal is to build something the right way and for the right reasons. If we can execute on that, I believe we will make users happy. A good solution will sidestep every potential fail moment. We've sidestepped a few so far and I'm really happy with the quality of developers that are contributing client and server work. The good protocol is incidental.