Yesterday I saw a video by Xin Yao given at a DDD conference formulated a similar paradox to the one we face with decentralization of the fediverse. This is the paradox between the decoupled software systems that engineers want, versus the deeply connected software that managers want to get most businesss value.
The video is well worth a watch, and inspired me to write some notes on..
â Autonomy vs. Connected ecosystems â 
âThe paradox of decentralization is that the more a technology ecosystem decentralizes, the more need there is for cohesive coordination to assure that the foundational technologies can support that decentralization, without the ecosystem falling apart.â
In the diagram above âsoftwareâ can be replaced with fediverse or federated software and âbusiness complexityâ with social network complexity (where it comes to integrating domain-specific solutions from autonomous parties in the decentralized developer ecosystem).
The current fediverse developer ecosystem represents a technosphere that not only does not give due attention to Strategic design (along a shared vision for the âFuture of Social networkingâ), but also has very weak grasp of the social complexity that exists within our ecosystem, which hinders formation of a healthy substrate and grassroots standardization process that solves the decentralization paradox.