Arguably #fediverse is NOT based on an open standard.
It's based on 'guidance towards an open standard' via the incomplete #ActivityPub spec, sprinkled with what fediverse devs have added over time via post-facto interoperability in what's effectively a Big ball of mud anti-pattern. These extra's are to be discovered on-the-fly, and being app-specific, need to be maintained constantly in another anti-pattern I dubbed Whack-a-mole programming.
We can do better. We can rise above the app-centricness of the fedi, make a paradigm shift that helps increase evolution speed and rate of innovation and sees people's needs be better served..
https://coding.social/blog/prosocial-web
For that to happen major social challenges need to be tackled, like coordinating and collaborating well in a good grassroots standardization process.
I posed the concept of a Grassroots open standard, where services encapsulate their design, and the standardization process is a fedi-native service itself.
https://coding.social/blog/grassroots-evolution