> All of these things have one thing in common: distrust. Some movements come from the distrust of governments or taxation, others come from the distrust of central services.
How about resiliency? Participation from community members? It's not always distrust that drives decentralization.
I think James C. Scott's book, Seeing Like a State is worth mentioning, since it discusses the failure of centralization in more ways than simply distrust. Here's a long-form essay summarizing the highlights: https://www.ribbonfarm.com/2010/07/26/a-big-little-idea-call...
This isn't really a new idea. In building architecture, Christopher Alexander spent a lifetime writing about this. You can see some of the highlights in his keynote speech to OOPSLA '96: http://www.patternlanguage.com/archive/ieee.html ... His ideas enable end users (residents) to be able to change their built environment while still maintaining a cohesive architectural design. Sadly, his groundbreaking ideas on pattern languages became watered down into HOA design regulations; software engineers did not heed what he talked about in that keynote; and Human Computing Interaction design dropped end-user-customizable software (like Hypercard) in favor of designs that favored aggregators, because it is more profitable (not necessarily more resilient, or better for society)
How about resiliency? Participation from community members? It's not always distrust that drives decentralization.
I think James C. Scott's book, Seeing Like a State is worth mentioning, since it discusses the failure of centralization in more ways than simply distrust. Here's a long-form essay summarizing the highlights: https://www.ribbonfarm.com/2010/07/26/a-big-little-idea-call...
This isn't really a new idea. In building architecture, Christopher Alexander spent a lifetime writing about this. You can see some of the highlights in his keynote speech to OOPSLA '96: http://www.patternlanguage.com/archive/ieee.html ... His ideas enable end users (residents) to be able to change their built environment while still maintaining a cohesive architectural design. Sadly, his groundbreaking ideas on pattern languages became watered down into HOA design regulations; software engineers did not heed what he talked about in that keynote; and Human Computing Interaction design dropped end-user-customizable software (like Hypercard) in favor of designs that favored aggregators, because it is more profitable (not necessarily more resilient, or better for society)