The Small Web isn’t about going back to the days of GeoCities. It’s about going forward differently, using modern tech in a non-colonial manner.
It’s not about building clones of Twitter, YouTube, etc. There’s no way anyone can self-host a dozen different services. Instead, it’s about having a single-tenant place on the Web that you own and control without technical knowhow; a place you can add Twitter, YouTube, etc., *features* to.
Not everyone can manage self hosting. Ultimately, the problems come down to modern software being to brittle, having too many bugs, and not being user friendly enough. It's sad because you're right, we shouldn't be paying with our freedom–but the reality is in order for someone to have access to modern services someone needs to be patching/updating/debugging/tweaking and paying.
@awaspnest (That doesn’t mean we built multi-tenant services. It means we build a single-tenant service that can be set up and used without technical knowhow. And then we make it so that the mechanism for doing that can be hosted by anyone with technical knowhow. And further, we make it so they can do so sustainably within the current socioeconomic system and in the better one we hope systems like this will help usher in…)
@awaspnest When it’s ready this will be your experience:
1. Go to small-web.org
2. Choose a name
3. Either pay €10/mo (or maybe, for example, your municipality will give you a code, so enter that instead.)
In under 30 seconds you’re up and running with your own place on the web.
(And anyone with tech knowledge can run their own small-web.org at their own domain. And you can easily move your place from one domain/host to another.)
Very early demo: https://small-tech.org/videos/small-is-beautiful-11/
@amolith @awaspnest Neat! I’m trying to make it as easy as possible for you to do so with Domain and would love your thoughts and feedback when it’s a little further along (it’s going to take me a week to two to create the first version of NodeKit and swap that into Domain so I have a bit of infrastructural yak shaving to do before concentrating on Domain itself again.)
I think this is all good until there's a zero day: Who's doing the updates and patches? Yes you can automate setups, but maintenance? It seems like at that point you're just running a platform with more steps. I really like the concept, I'm just a little pessimistic given my own experiences (as a reasonably skilled computer person) in making generally useful Webservices. Still I'll keep an eye on it.
Also, and maybe I missed this somewhere, but you should copy this toot and put it on your website somewhere. It seems like most links about what you're doing lead to hour-long live streams.
This is my personal Mastodon.