Alexis Madrigal, a senior editor of the Atlantic, has made a pretty slick contribution to the theory of open source protest. How?
He detailed what an API (an application program interface) for the Occupy movement would look like. I put it up a summary of the API on MiiU as an example for others to use/modify in future movements. Feel free to put your own variants up.
What the Occupy API actually is
For those of you that aren't computer geeks, here's what the API represents.
- An open source protest movement doesn't develop according to any central plan, because it's not led in a traditional way. In contrast, it develops through the efforts of lots of small contributors. Leaders come and go.
- What do these contributors provide? They produce and demonstrate small innovations. Basically, they tinker, and put their innovations into practice.
- The innovations that work or achieve results are shared by coverage in the press or online communications (the scientific name for this process is called stigmergy).
- The list of innovations that have gained some level of acceptance across a large part of the open source protest is what Alex is calling its API.
Anyway, hope that helped you makes sense of it.
NOTE: The handy way to get up to speed with open source protest/warfare is to read my book Brave New War. If you want to dive into a quantitative model of open source warfare/protest, some friends of mine did a scientific study that made the cover of the prestigious science magazine, Nature.