Table of Contents
Generative AI and the IndieWeb
The IndieWeb community is explicitly pro-human: its wiki AI policy bans AI-generated content. But in 2026 the movement's infrastructure maintainer disclosed that he had used Claude Code to rebuild the services the community depends on. The debate that followed is the honest fault line: ethics versus craft, and what to do when the alternative to using the tool is letting the service die.
Adapted from The IndieWeb Now Has genAI (and Claude) Built In and The Better Web / The Human Web / The Living Web on brennan.day.
What Happened
In October 2026, Aaron Parecki wrote that he had rebuilt several IndieWeb infrastructure projects with the help of Claude Code. Parecki is not a peripheral figure: he co-organized the first IndieWebCamp in June 2011 and built or maintains webmention.io, Quill, Meetable, indielogin.com, IndieNews, and micropub.rocks, plus contributions to the Webmention, Micropub, and WebSub W3C specifications. Much of the movement's plumbing runs on code one person maintains.
His stated rationale: the services were running on aging stacks and would have had to shut down without the rewrites. “Understanding matters more than tools.” “The code was never the interesting part.” “IndieWeb principle is have fun.”
The Positions
- The pro-human reading: the IndieWeb exists to be a hand-made alternative to the machine web. Using the industry's flagship extractive tool to build its infrastructure severs craft from ethics. indiewebispunk.net is the banner.
- The pragmatic reading: the IndieWeb is also a community of working services that real people depend on, maintained by a near-singular point of failure. If the tool keeps the lights on and the maintainer still understands the system, refusing it on principle means letting the commons collapse.
The tension generalizes the older trust question: is the movement defined by the provenance of its tools or the humanity of its output?
