I Joined the IndieWeb: Reclaiming Control Over Your Content
I joined the IndieWeb, here's what I learned
Curious about the IndieWeb, I explored its principles to escape corporate silos and own my digital identity. By adopting standards like microformats2 and using my own domain, I found a resilient, people-focused alternative to the fragile corporate web. This journey improved my site's UX and taught me that true ownership means keeping your content safe from platform shutdowns.
"Your website is your API."
HN discussion
- IndieWeb is not about rejecting professionalism or using pseudonyms; it is about ensuring your CV, headshot, and professional identity remain under your control rather than locked inside a silo like LinkedIn.
- The movement intentionally maintains high technical friction, such as requiring knowledge of command lines, Docker, or HTML, to filter out users who prioritize convenience over ownership and to avoid the 'dumbest possible user' dynamic.
- Critics argue that RSS is redundant because it duplicates website content and requires maintaining two versions, whereas proponents claim it is essential for automated content discovery compared to manual checking.
- While some view IndieWeb as a niche hobby for tech enthusiasts, others contend that the current internet's lack of barriers has led to a global marketplace of clickbait, making self-selection and gatekeeping necessary for quality.
- Practitioners emphasize that IndieWeb does not require self-hosting on private servers but advocates for managing hosting through public platforms like GitHub Pages to ensure content longevity and independence.