There’s a call to action for solidarity and mutual aid with Cooperation Jackson at the end of chapter one of Jackson Rising.
What’s exciting is that with the 3rd and 4th industrial revolutions, there’s a chance I can give that solidarity from across the globe. It could be financial, technical, informational, it could be microtasking on some problem.
It reminds me of Walkaway, where the remote network springs into action when a group needs their help. We rise up.
Great to see reuse and recycling flagged as key parts of the Jackson plan, part of a deemphasis of production/consumption. Even tool libraries get a mention! I’d like to see repair get more of an explicit mention too.
Places bypassed by capital might provide the best opportunity for alternative economies.
“the weak and relatively sparse concentration of capital in Mississippi creates a degree of “breathing room” on the margins and within the cracks of the capitalist system that a project like ours can maneuver and experiment within in the quest to build a viable anti-capitalist alternative.”
Makes me think cities like London are probably lost causes for now.
Loving the first chapter of Jackson Rising. Straight-up practical details on bootstrapping a solidarity economy, from people that are doing it, and doing it in pretty adverse conditions.
Voting closed, and the next book for the social.coop reading group will be Jackson Rising: The Struggle for Economic Democracy and Black Self-Determination in Jackson, Mississippi.
“Jackson Rising is a chronicle of one of the most dynamic, but under-documented experiments in radical social transformation taking place in the United States.”
Looking forward to learning about Cooperation Jackson.
And with that, I’ll pass the hosting baton on to @Matt_Noyes. Cheers!
Apropos retoot:
I’ve seen a few posts recently about FOSS burnout, where the act of maintenance becomes a heavy burden.
Like you could potentially argue that the ‘free rider’ problem (noting that I don’t like that term…) in FOSS could be people leaving poorly specified bug reports, angry comments when something doesn’t work, etc. Using up developer-time/energy, which is a subtractible resource, even if the end product isn’t.
So there would be a need for governance rules to mitigate that.
HELL™ by Darren Cullen.
https://www.spellingmistakescostlives.com/businesshell
“All the business people are sent to Hell but they end up taking the place over and running it for profit, industrialising the torture process and making everything much more efficient and terrible.”