There are many opposing forces in the #IndieWeb that can seem like catch-22s, yet help clarify priorities, and balance present pragmatism & future optimism.

* Indie, yet often on corporate infrastructure
* Independent, yet dependent on community
* Own your content¹, yet share publicly, perhaps CC0²
* Control of your design³, yet lack of control elsewhere
* UX freedom & creativity, yet guidance toward common patterns for usability
* Decentralized, yet DNS
* Make what you need, yet open source for others
* Plurality of projects, yet conforming to standards
* Build it yourself, yet use services, software, & libraries built by others

These are a few off the top of my head and implied by the IndieWeb wiki home page and principles¹⁰.

Rather than contradictions, these tensions are a source of inquiry, questions, and conversations.

Each could be expanded into their own discussion or exploration.

Each of them is an axis of sorts, with different “right” answers for different people, depending on what they want, and how much time or other resources they have.

Each makes the most sense when explored in the context of a focus on solving real user needs to participate directly on today’s web.

Each is also a trap for abstract logic, theoretical purity, or dogmatic absolutism, especially when detached from real world goals, constraints, and efforts.

This is day 22 of #100DaysOfIndieWeb #100Days, written after a break. Many double days ahead.

← Day 21: https://tantek.com/2023/022/t2/own-your-notes-domain-migration
→ Day 23: https://tantek.com/2023/027/t4/five-years-websub

¹ https://tantek.com/2023/001/t1/own-your-notes
² https://indieweb.org/IndieWeb:Copyrights
³ https://indieweb.org/design
¹⁰ https://indieweb.org/principles

on (ttk.me t5P31) using BBEdit