An increase in the ability of individuals and small groups to accomplish tasks/work through the combination of rapid improvements in technological tools and access to global networks -- has enabled small groups to radically increase their productivity in conflict. For example, if a small group disrupts a system or a network by attacking systempunkts, it can amplify the results of its attacks to achieve as much as a 1,400,000 percent return on investment.
Open source warfare is an organizational method by which a large collection of small, violent, superempowered groups can work together to take on much larger foes (usually hierarchies). It is also a method of organization that can be applied to non-violent struggles. It enables:
* High rates of innovation.
* Increased survivability among the participant groups.
* More frequent attacks and an ability to swarm targets.
Here are some suggestions (this is but one of many methods based on recent history, I'm sure that over time a better method will emerge) for building an open source insurgency:
A) The Plausible Promise.
The idea that holds the open source insurgency together. The plausible promise is composed of:
* An enemy. The enemy serves as the target of attacks. This enemy can either be either received or manufactured (any group or organization that can be depicted as a threat). The enemy can be any group that currently holds and exerts power: invader, the government, a company, an ethnic group, or a private organization.
* A goal. This objective animates the group. Because of the diversity of the groups and individuals that join together in an open source insurgency, the only goal that works is simple and extremely high level. More complex goal setting is impossible, since it will fracture/fork the insurgency.
* A demonstration. Viability. An attack that demonstrates that its possible to win against the enemy. It deflates any aura of invincibility that the enemy may currently enjoy. The demonstration serves as a rallying cry for the insurgency.
B) The Foco.
Every open source insurgency is ignited by a small founding group, a foco in guerrilla parlance. The foco sets the original goal and conducts the operation that provides the insurgency with its demonstration of viability. It's important to understand that in order to grow an open source insurgency, the founding group or individuals must follow a simple path:
* Relinquish. Give up any control over the insurgency gained during its early phases. In practice, this means giving up control of how the goal is achieved, who may participate, how to communicate, etc. The only control that remains is the power of example and respect gained through being effective.
* Resist (temptation). Stay small. Don't grow to a size that makes the original group easy for the enemy to target (very few new members). Further, don't establish a formal collection of groups, a hierarchy of control, or set forth a complex agenda. This will only serve to alienate and fragment/fork the insurgency. In some cases, it will make the foco a target of the insurgency itself. It will also slow any advancement on the objective since it limits potential pathways/innovation.
* Share. Provide resources, ideas, information, knowledge, recruits, etc. with other groups and individuals that join the insurgency. Share everything possible that doesn't directly compromise the foco's integrity (operational security and viability). Expect sharing in return.