Advertise here with Carbon Ads

This site is made possible by member support. ❤️

Big thanks to Arcustech for hosting the site and offering amazing tech support.

When you buy through links on kottke.org, I may earn an affiliate commission. Thanks for supporting the site!

kottke.org. home of fine hypertext products since 1998.

🍔  💀  📸  😭  🕳️  🤠  🎬  🥔

In order for the 2024 indie web revival to work: “We need more tools for it. We need simpler tools for it. And we need to make installing and using them trivially simple.”

Comments  17

Sort by: thread — thread . latest . faves

John Delaney

With Docker, I think a lot of this stuff is there, but docker isn't easy, so we'd need a hosting platform to play ball. What if the hosting platform gave you a list of registered platforms, then attempted to install them for you? Or you provide the host with a github, the host pulls then does a docker-compose up? Someone just needs to come up with a nice hosting service and a somewhat generic protocol for installs, like Docker.

Matt G

Is that really not a thing right now?

Phil Gyford

I think having a GitHub account and even having heard of Docker, never mind understanding what it is or why you might use it, is a level of complication beyond what the article is imagining.

John Delaney

I agree. No need for the user to have heard of docker, but developing a standard deployment deployment pipeline, using, for instance, docker. Then the service can provide presets or a "power user" could point to a repo that follows the installation protocol.

Reply in this thread

Paul Burdick

I agree. I miss the PHP apps of old that were a sub 1MB zip file with all the necessary code included. No package managers and requiring nothing more than a MySQL database. You just uploaded the files, ran the setup script, and were on your way in about 10 minutes.

Meg Hourihan

'"So that next time we say to someone: “You should own your own domain, and publish on your own website,” and they answer with “How?”, we can give an answer that’s more than just: “Install Wordpress.”'

What goes around comes around. Didn't we solve this already in 1999 with Blogger?

Paul Burdick

Indeed. That was hosted though. And those templates!

Jason KottkeMOD

Yeah I think the idea is for people to be as autonomous as possible, without having to rely on software and services controlled by large companies like Google. So that, for instance, someone can set up a Substack-like site/newsletter on their own server, with their own domain, using a locally-run CMSand, crucially, that process is as easy as setting a site/newsletter up through Substack.

Reply in this thread

Justin Michael

I understand and agree with the sentiment, but for many people the, "unzip, upload to the shared hosting they’ve just paid for," steps are going to be just as big a hurdle as running Terminal commands. The linked post treats those parts as trivial, but things like SFTP, inscrutable upload UIs that vary from host to host, file ownership and permission issues, and even navigating a filesystem are significant barriers for tons of folks. Oh, and that "paid for" bit automatically excludes a huge number of people who will not or cannot spend money on something like this.

The answer to making "the tricky technical stuff go away" does not involve people signing up for a traditional shared web hosting account or unzipping and uploading files to it.

Justin Michael

I should clarify that I bring this up not because it's all doom and gloom, but because I want to figure this out! I am optimistic that there is a way to solve this problem, but I want to get a conversation started about how to do it for everyone, not just people comfortable paying for and using shared hosting.

Matt G

I think people are very much capable of doing those things, but the mobile app world has really hidden away so much of how computers and the internet function.

Not everybody is going to do this. But there are a lot of people who are interested enough that they would be willing to put in a modest number of hours to learn the basics.

John Delaney

I think this will take some care on the hosting provider to offer some sort of UI for installation. The hosting provider could provide presets that are tested and work, or allow the user to provide a repo URL and possibly credentials, using a simple form, then the provider pulls the repo and attempts an install. Returns an error if the install doesn't work. I think the stack has matured enough where this idea is non-trivial but doable.

Reply in this thread

Nicolas Magand

I like what Micro.blog is doing, basically making the SSG Hugo available for everyone (but you can't have your own server), but I don't see the other open source static site generators like 11ty, Jekyll, Svelte, Astro offered with a similar easy alternative. I like what Ghost, Bear blog, or the great Blot (and even Tumblr and plenty others) are doing but these are not tools you can use easily with your own server, just like Squarespace, which I think is the point of the article (the developer version of Ghost -- which one can install on a server -- looks more complicated than say Wordpress). Kirby sure looks good, but it's hard to really try before buying. SSGs are really too complicated for most people, from the installation to the documentation (and also publishing via Git commands in a terminal!).

Trent Seigfried

I think Substack's interface is really good for this, but I don't agree with the line they chose in terms of the paradox of tolerance, so I'm hesitant to use it or encourage others to do so. A shame, because I have a lot of long-form researched articles that I would love to share somewhere, but I haven't found the right platform yet.

Jason KottkeMOD

Giles posted a follow-up to his post: More on the easier indie web.

Phil Wells

This is a sticky wicket and I don't want to get myself into trouble, but the "platform tolerance" problem and the "we want the web to be weird again" problem are a little bit at odds. If I have the skills and resources to make a platform that makes it easy enough for the web to be little weirder, but I don't have the skills and resources needed to foster a healthy community and make sure it doesn't let the bad elements in, and if that's something I don't care to inflict upon the world, then I'm not going to get started. The community part, the human part, is always going to be hard. It's relatively easy to challenge developers to build better tools. It's constant work over time to keep those tools out of the hands of world-class jerks.

Andrew Raff

Having more easily accessible tools can mean that not ever thing on the web needs to be a platform or community. The indie web is based more on pulled connections --- e.g. I can link to Jason's site and recommend this post from my blog and share it with whoever wants to see me. The modern social platform is more about pushing data -- Instagram's algorithm suggests Threads or Reels that it think I should see. By not requiring that every thing on the web be part of a larger platform, but that it can be its own site, obviates some of the need for moderation. If I'm not hosting a comments section, I don't need to worry about moderating it.

For example, Substack's might have less of a Nazi opportunity problem if it just hosts newsletters without suggesting other newsletters and posts to readers.

Reply in this thread

Hello! In order to leave a comment, you need to be a current kottke.org member. If you'd like to sign up for a membership to support the site and join the conversation, you can explore your options here.

Existing members can sign in here. If you're a former member, you can renew your membership.

Note: If you are a member and tried to log in, it didn't work, and now you're stuck in a neverending login loop of death, try disabling any ad blockers or extensions that you have installed on your browser...sometimes they can interfere with the Memberful links. Still having trouble? Email me!