The article seems to characterize efficiency solely in the context where it optimizes a process to the detriment of other useful aspects of the process (i.e. removing redundancy makes a system more “efficient” in some sense, while also making it more prone to disruption).
Putting aside the article’s weird definitions, I do like the article’s overall message: grow slow and sustainability rather than as “efficiently” as possible. I can see how the impulses of growth at all costs and short term efficiency gains at the cost of long term stability might be related to certain forms of capitalism, however capitalism is not defined (as in the definitions given in your other comment) by rampant disregard for caution and sustainability, (there are capitalist societies today known for their careful planning and risk management!). Capitalism as a concept is only defined via private ownership of capital, so I think my original comment still stands: capitalism is good, sometimes.
Another way to solve the issue is to have users and communities be instance-independent where the instances only provide storage for communities and users they want to support.