I joined the IndieWeb, here's what I learned

Original Article ↗ Hacker News Discussion ↗

IndieWeb’s push for personal, self-hosted websites sparks enthusiasm for owning one’s online identity, but also exposes tensions between geek-friendly protocols and mainstream usability. Commenters debate the role of RSS versus newer formats, how discoverable and accessible a site should be, and whether IndieWeb’s tooling is too complex for non-technical users. Underneath is a broader question: can a movement built by and for tinkerers ever grow beyond a niche without sacrificing its values of independence, control, and quality over convenience.

Tools and implementations

  • Several commenters share their own IndieWeb setups, e.g. using pre-built toolkits and platforms that bundle IndieWeb protocols.
  • Others highlight new support in existing frameworks (e.g. a PHP platform adding IndieWeb support) and static hosting options (GitHub Pages, Cloudflare, Squarespace, etc.).

RSS, h-feed, and feed discovery

  • Strong agreement that RSS/Atom are crucial for blogs; some call a blog without RSS “like a car without wheels.”
  • h-feed is defended as the IndieWeb-preferred approach (HTML as the feed), but multiple people say no mainstream readers support it and they rely on classic RSS/Atom instead.
  • There is criticism of hiding the RSS URL behind a JavaScript-only modal and omitting <link rel="alternate">, since many readers auto-discover feeds from HTML.
  • Some see RSS as trivial to generate; others dislike duplicated content and XML overhead but concede RSS remains the de facto standard.

Domain ownership and .dev concerns

  • Discussion about .dev being operated by Google’s registry.
  • Some see this as a centralization and power-risk issue; others consider it a non-issue and are comfortable paying Google via a registrar.
  • The idea of a “neutral” TLD comes up, but its meaning and practical benefits remain unclear.

IndieWeb usability, complexity, and adoption

  • Critics argue IndieWeb’s protocol stack is “tech soup” and unworkable for most people; demand one-click, no-CLI solutions.
  • Others counter that current adopters are mostly technically inclined and that early-stage ecosystems are naturally rough.
  • Some insist UX must be central if the goal is broad ownership; others say IndieWeb’s mission is to “scratch your own itch,” not win mass market.
  • Hosted IndieWeb-like services and WordPress plugins are cited as easier on-ramps, though long-term economics and demand are questioned.

Philosophy, gatekeeping, and audience

  • One camp welcomes friction as a filter, arguing that opening everything to “everyone” degraded the early web.
  • Another camp warns that technical barriers mostly select for tech workers, not for people with interesting non-technical ideas.
  • There’s tension between “digital homesteading for enthusiasts” versus being a realistic alternative to big platforms.

Self-hosting, motivation, and practicality

  • Several note that “nobody wants to host” because it’s costly and fragile, leading to walled gardens.
  • Others enjoy the control and learning, but admit to burnout or retreating from full stacks after seeing real costs.

Professional identity and ‘indie’ aesthetics

  • Some feel prominent CVs and polished, career-focused personal sites clash with the “indie” vibe.
  • Others argue that hosting a CV and professional identity on your own domain is exactly in line with IndieWeb’s goals of ownership and persistence, not anti-professionalism.