Soft security

As opposed to hard security. Soft security patterns from Meatball Wiki:

Soft Security is like water. It bends under attack, only to rush in from all directions to fill the gaps. It's strong over time yet adaptable to any shape. It seeks to influence and encourage, not control and enforce.

Soft Security is a collective solution, whereas Hard Security is often an individual solution... When Soft Security becomes unilaterally enforced, it fails. This is a chicken and egg statement.

Soft Security follows from the principles of:

From How Wikipedia Works.

One of the paradoxes of Wikipedia is that this system seems like it could never work. In a completely open system run by volunteers, why aren't more limits required? One answer is that Wikipedia uses the principle of soft security in the broadest way. Security is guided by the community, rather than by restricting community actions ahead of time. Everyone active on the site is responsible for security and quality. You, your watchlist, and your alertness to strange actions and odd defects in articles are part of the security system.

What does “soft security” mean? It means that security is largely reactionary, rather than preventative or broadly restrictive on user actions in advance. With a few exceptions, any anonymous editor can change any page on the site at any time. The dangers of such a policy are obvious, but the advantages are perhaps less so: Wikipedia’s security offers a level of adaptability and flexibility that is not possible with traditional security policies and tools.

• Twitter thread: What the decentralized web can learn from Wikipedia?
• Blog post: What the decentralized web can learn from Wikipedia?

Soft security allows for [[permissionless creation is where value comes from | permissionless innovation]].

[[permissionless creation is where value comes from]]