There are one-click-setup IndieWeb entry points. The most prominent is micro.blog which gives you a personal blog/site with all the latest IndieWeb goodness and costs $5/month.
But most people interested in the IndieWeb these days are devs, i.e. nerds, and want to roll things themselves, which is why IndieWeb-related blog posts can feel like tech soup.
This is something IW members would gladly see change! Adoption by non-nerds is something the IW cares about. David Shanske[2], for instance, has spent much time in the last decade on Wordpress plugins that gives you much of of the IW tools out of the box [3].
Finally, you don't need to use all of the tech to be "doing IndieWeb". Having your own domain is the first and most important step. Then maybe you[4] try making a few pages: raw HTML, generated from Markdown, Django, whatever. Then you can add Microformats. Then maybe add a script to send WebMentions, or use a free hosted service to do it for you. Then branch out in whatever direction you choose. At all of these stages, your site is still IndieWeb.
[1] I'm not as active in IW circles as I was a few years ago but still consider myself part of it: my personal site has microformats, I use Micropub to update it, etc.
[2] david.shanske.com
[3] https://profiles.wordpress.org/dshanske/#content-plugins
[4] Generic "you".
Because it's anti-platform and pro-ownership, content is secondary to the means of distribution. It's why it is bound to be a tech-heavy sub-culture and never a real alternative to big platforms.
I am sad about local groups and forums, but that is not something that IndieWeb is trying to solve.
The other problem is businesses that have retired to Instagram. which I find baffling.
How does having their own place away from the “unwashed masses” relate to overturning the big platforms?
- people with their own websites
- privacy activists and /or anti-capitalists
- almost everybody on the planet
The second group is especially loud. Which is normal, silent activism doesn’t really make sense.I seriously doubt that people who clamor for the death of Facebook and the likes do it so that indie web is full of macha latte labubu car tastings and supplement and gambling shills.
Mailinglists are great, because more and more people do no longer know how to use email or follow the instructions to sign up for a mailinglist, so many interesting people tend to gather around the lists.
Meanwhile there are also plenty of tech folks that have zero empathy or interest in quality that can easily get past any technical barrier you put in front of them, like the more talented folks at companies like Anthropic or Meta.
Making things difficult to set up tech wise doesn't select for intelligence or skill or creativity, it selects for people that work in tech as their day job.
I think the IndieWeb is at this early stage. The adoption for a broader audience will come naturally (if this survives), but for now - let them cook
Second of all, how long is IndieWeb supposed to cook for before it's supposed to be ready for a broader audience? This is no shade on the IW folks if they like what they're building. But if what they're building is supposed to catch on somewhat, what's the path supposed to be? The project seems to be 15 years old already: https://indieweb.org/IndieWebCamps#
If something is important for me I can waste hours setting it up and running.
If it is something new to me, if it doesn’t work out of the box I most likely will just move on.
The trick is the economics here. A one-click solution is great, but right now the indieweb solves an ideological but not a hard _user_ problem. There isn't enough "there" there to either justify investment or get enough customers to cover the costs of a service.
The closest is micro.blog, which is a genuinely great service that bakes in this tech under the hood. But the tradeoff is that you can't run it on your own infra; it's a centralized service that is compatible with the protocols but isn't quite a genuinely indieweb tool.
I've wondered if there might be something around providing better tools for logging an agent's activities, or for publishing from a sensor / server / etc, but that's all speculation. Without a genuine hard user need, it's hard to imagine how this would work as a turnkey service.
Part of the Indieweb philosophy, like Libre software, is to "scratch your own itch" - no one's paying you. You do the stuff that's interesting to you. It's not a business. The point is not to take over the market.
The planet needs fewer marketing pinheads, not more. I would like it if we passed various laws that killed off a lot of the marketing pinheads, basically eliminating their jobs one way or another, and encouraged more people to create the things they want, rather than submit to the things that are popular.
The pinheads rarely create much of substance and mostly just sit around strategizing all day on how to rent seek. They have a lot of free time and money they can use to lobby the government and make it worse. They dress this all up as capitalism though it isn't really. We should strike back.
No, you don't understand, it's bad because it does not provide ""value""
there’s nothing wrong with building software for yourself. but if your stated goal is giving everyone ownership over their online identity, then usability stops being marketing and starts becoming part of the mission.
good ux isn’t selling out. it’s removing accidental complexity so more people can benefit from the ideas. otherwise you’re not building an alternative to big platforms, you’re building a club for people who enjoy configuring web servers.
This is essentially DNS, every single step of the way. Hosting wouldn't be hard if ISPs weren't so hostile with carrier-grade NATs, if HTTP/S wouldn't rely on DNS primarily, if legitimization were using actually mTLS instead... and all of the things usually break because of DNS and (lack of) proper standardization.
DNS in its current form is such a shitshow of RFCs overriding RFCs overriding RFCs...and not a single moment was spent on the configuration of DNS, or a protocol to request a domain, or a protocol to authenticate a domain, or a protocol to host something for a domain, ...
/nerdrage
I find it all the more appealing with that barrier to entry because I miss the internet that this community is nostalgically trying to replicate and reproduce.
Oh, no?
Its not one click, but is massively simple and building up tooling around it to make it easier would also be super simple.
(which seems diametrically opposite of IndieWeb: no HTML - iOS/Android is the king, no browsers, no desktop, no terminal, no GitHub, gated App Stores, rich media, videos is the king)
It does keep indieweb for the few and not the many.
use Cloudflare.
whatever critisism is just "IndieWeb decides not to do so".
not admiting own mistakes also goes hand-in-hand with it.
overall, recipe for disaster.
do you see difference between history of edits and internal documentation about the public website and public website itself? or sources to build website vs website itself? it is nuts not to see distinction of that.
github repo != public webpage. this is nuts.
They, if you're lucky, may have "davethepublumber.co.uk" and then "dave6969@gmail.com" printed on the side
Or at least they won't enjoy it.
Physical activity is enjoyable for most people, whereas mental is painful.
Some examples of that exist for sure.
If it's turnkey it can't be "self". Even if you could buy a magic hosting box to put in your home network, you would be dependent on its support.
>If you want to put content UX first, you need to do exactly that, with a one-click solution that gets users up and running instantly.
You clearly don't understand the IndieWeb movement, which consists of amateurs and professionals who are motivated to go the extra mile and learn this stuff. The reason the Internet is the way it is in 2026 is precisely because we’ve eliminated all friction and have cultivated the dumbest possible user.