The current fediverse is an evolutionary dead-end for 2 reasons:
1. It has painted itself in a small niche of decentralizing typical social media use cases, by means of post-facto interop and the introduction of protocol decay.
2. Lacking a proper grassroots standardization process, and with the primary mechanism for fediverse extension being only post-facto interoperability, there is no way out.
Congratulations to the early adopters, who managed to "cross the chasm" with their own app platforms. It took true grit to become deep #ActivityPub experts, and plug holes needed for your app, but you have made it. Post-facto interop works in your favor now. You are unrestrained to productively add more features in your app, and put them on the fedi wire for others to deal with.
To avoid fedi to become less and less attractive to newcomers, we must now consider:
“Why do we want to grow the open social web, and for whom?” -- @ben
Note btw, that for the most part algorithms are not causing the issue of bad integrations between apps. These are due to the pragmatic nature in which our current app-centric fediverse evolves, i.e. by means of post-facto interoperability. Here app developers focus on getting app features on the wire, and whomever first succeeds in making their new custom protocol extension to become popular, becomes the de-facto standard for that feature. And everyone else should "follow the leader" or push themselves out of mainstream fediverse adoption, into their own app niche.
This is not a sustainable path, and I am among years-long advocates that we should do better in how we collectively evolve the fedi, so that it can truly become the social networking of the future. See also my posts from last week, like: