My Journey into the IndieWeb: Lessons Learned

Driven by a sense of curiosity, I began investigating the #IndieWeb tag that frequently appeared in my Mastodon feed and across various blogs. I soon realized that this wasn't just a vague concept or a simple longing for the primitive nostalgic web of the 1990s.

Instead, I found a vibrant community backed by concrete protocols and a clear ideological framework. As I dove deeper into their wiki, the brilliance of their approach became evident. My excitement grew to the point where I decided to implement their recommended protocols on my own site.

After a period of testing and refinement, the results are in:

• Significant learning experience.
• Noticeable improvements in website UX.
• High level of personal enjoyment during the process.

I've compiled my notes from the last few months into this article. My hope is that this guides others toward a healthier web and satisfies those curious about which specific tools I adopted, which I rejected, and which tips were the most valuable.

---

What Exactly is the IndieWeb?

The IndieWeb describes itself as a "people-focused alternative to the corporate web." Rather than pushing a specific software package or a rigid framework, it provides an ideological foundation that welcomes a variety of projects and methods.

As their mission statement suggests: “we are people-focused instead of project-focused.”

A Brief History

The movement traces back to 2010, when Aaron Parecki and Tantek Çelik attended the Federated Social Web Summit in Portland. They concluded that the web needed fewer complex protocols and more individual creators. This led to:

1. The first IndieWebCamp in 2011 (now a global annual event).
2. The Homebrew Website Club, where enthusiasts meet to tinker with their personal sites.

The Three Core Pillars

The movement is built upon three fundamental commitments:

Essentially, it is a collective of independent site owners fighting against "walled gardens." It doesn't forbid social media; it simply advocates for autonomy.

---

The Enemy: The "Silo"

In the IndieWeb lexicon, the primary antagonist is the silo (or walled garden). This is defined as a centralized, typically for-profit platform that claims rights over your contributions and restricts how you access or move your data.

Common Silo Characteristics:

• Mandatory site-specific accounts.
• Interaction limited to other users within the same ecosystem.
• Restrictive Terms of Service (ToS).
• Barriers to indexing, importing, or exporting content.

The Fragility of Centralization

Silos are inherently unstable. When they collapse, they take your digital history with them. The community maintains a "site-deaths" page—a grim chronology of "incredible journeys" corporate failures.

The Hall of Lost Data:

• GeoCities: Terminated by Yahoo on Oct 26, 2009.
• MySpace: Lost 50 million songs from 14 million artists during a 2019 migration.
• Others: Posterous, FriendFeed, Vine, Yahoo Groups, TinyLetter, Cohost...

Even if a site doesn't "die" abruptly, the web is naturally fragile. A 2024 Pew Research study indicates a high rate of link rot. If we let $P$ represent the probability of a page remaining accessible over a decade:

$P(\text{accessible}) = 1 - 0.38 = 0.62$

This means roughly $38\%$ of pages from 2013 are already gone. The IndieWeb solution? Use any platform you like, but ensure the canonical copy of your work lives on a domain you own.

---

The 11 Guiding Principles

The community adheres to a set of principles designed to combat network fragility:

1. Own your data: Keep your identity, metadata, and content on your own domain.
2. Visible data: Prioritize human readability over machine readability.
3. Make what you need: Build tools for yourself first.

   "If you design for some hypothetical user, they may not actually exist; if you make for yourself, you actually do exist."

4. Use what you make: If you don't rely on your own tools, why should others?
5. Document your stuff: Use your site to log your processes, ideas, and code.
6. Open source your stuff: Share your work to help others join the movement.
7. UX before protocols: Prioritize the user experience, then find the simplest protocol to support it.
8. Modularity: Use small, loosely coupled components to avoid platform lock-in.

   "If human society is able to preserve ancient papyrus, Victorian photographs and dinosaur bones, we should be able to build web technology that doesn't require us to destroy everything we've done every few years in the name of progress."

9. Plurality: Encourage diverse approaches to avoid a new monoculture.
10. (Implicit) Permanence: Focus on long-term stability.
11. (Implicit) Autonomy: Maintain independence from corporate whims.

Implementation Example

To avoid the silo effect, one might use a simple HTML link to point a social media post back to the original source:

<!-- The Canonical Link: Telling the world where the 'real' version lives -->
<link rel="canonical" href="https://yourdomain.com/posts/my-awesome-article">

---

Visual Gallery

Below are some of the inspirations and tools associated with this journey: