plurality

Encouraging a  plurality  of projects with a self-motivated incentive to interoperate is a key principle of the indie web, in contrast to monoculture efforts which require or even encourage everyone to install the same software, or use the same online service, in order to interoperate.

Project diversity over monoculture
With IndieWebCamp we've specifically chosen to encourage and embrace a diversity of approaches &amp; implementations. This background makes the IndieWeb stronger and more resilient than any one (often monoculture) approach.

One of the key things we recognize with IndieWebCamp is that no one project is likely to be the answer.

Simultaneous exploration and evolution
We're much more likely to advance the state of the art by encouraging everyone to build what works for them, and then figure out how to interoperate between different coding/implementation approaches. This is what makes IndieWebCamp different (more inclusive) than all other such "open source" efforts out there.

Multiple implementation efforts help to simultaneously explore different parts of the indieweb problem space as we're all choosing to focus on building the particular aspects of what's important in an indie web site for ourselves. Additionally, multiple approaches to the same problems in essence A/B(/C/D/...) test different approaches simultaneously, each of which can then learn from and evolve in response to the others.

This parallel diversity both produces better indie web solutions faster, and allows for the incorporation of new approaches to address new problems, adapting as the needs of an indie web site change over time.