I think the point the author is trying to make is more so about these mini networks on their own LAN, which their family uses. (And maybe dreaming of a neighbourhood utility LAN as a middle ground between LAN in your house and WAN as just a trunk to a big ISP node) The full quote is
- A Raspberry Pi 3B+ with a 3 gigabyte hard drive setup as a "server" (makes this site available on my home network[9])
- I publish this site via GitHub Pages service for public Internet access (I have the least expensive subscription for this)
...
[9] I can view my personal web on my home network from my phone, tablet and computers. So can the rest of my family.
As the author of a content management system I made with the idea to democratize internet content creation, I've had a lot of the same thoughts that the author brings up here. I've always thought that even learning Markdown was a bridge to far when it comes to empowering non-technical users however. In my experience it's best just to supply tooling similar to Word where you have buttons for things like lists and bolding. Using Markdown as the format itself is something I will agree with though.
Another thought I had is that local AI could most definitely play a part in helping non-technical users create the kind of content they want. If your CMS gives you a GPT-like chat window that allows a non-technical user to restyle the page as they like, or do things like make mass edits - then I think that is something that could help some of the issues mentioned here.
It's definitely an approach. I do think in true democratization of the internet, teaching people some tech is inevitable. We just can't have equal access if we retain the classes of user and maker as completely distinct.
The only way we own a web of our own is to develop much more of a culture of leaving smallish machines online all the time. Imagine something like Tor or BitTorrent, but everyone has a very simple way of running their own node for content hosting.
That always-on device? To get critical mass, instead of just the nerds, you'd need it to ship with devices which are always-on, like routers/gateways, smart TV's. Then you're back to being at the mercy of centralized companies who also don't love patching their security vulnerabilities.
(1) Security. An always-on, externally accessible device will always be a target for breaking in. You want the device to be bulletproof, and to have defense in depth, so that breaking into one service does not affect anything else. Something like Proxmox that works on low-end hardware and is as easy to administer as a mobile phone would do. We are somehow far from this yet. A very limited thing like a static site may be made both easy and bulletproof though.
(2) Connectivity providers should allow that. Most home routers don't get a static IP, or even a globally routable IPv4 at all. Or even a stable IPv6. This complicates the DNS setup, and without DNS such resources are basically invisible.
From the pure resilience POV, it seems more important to keep control of your domain, and have an automated way to deploy your site / app on whatever new host, which is regularly tested. Then use free or cheap DNS and VM hosting of convenience. It takes some technical chops, but can likely be simplified and made relatively error-proof with a concerted effort.
If I'm reading the implication right, you're having a pretty terrible idea. Glossing over what running a server would do to your battery, it would never work because of the routing issues you'll run into.
With IPv6 it would theoretically be possible, but currently with ipv4 and NATs everywhere, your website would almost never be reachable, even with fancy workarounds like dynDNS
This guy has been around long enough to know about NNTP, which is the original distributed people-focused web, but talks about how HTML is some kind of barrier to entry.
It's not about ease of publishing. The issue is what people get in return for publishing. Until you can design a platform that gives top creators as much money+attention as commercial platforms, you'll see a drain of top creators and their viewers to commercial platforms.
I think this mostly misses the biggest reason why writers would choose big tech platforms or other big platforms: discovery and aggregation. If you want to speak to be heard and not just for its own sake, then you want to go where the people are hanging out and where they could actually find your content.
This is like talking about how book authors don't need Amazon when you have a printer and glue at home.
I agree with the point that big companies have persuaded people that only they can offer ease of publishing content. most of my friends publish on Facebook, X, Instagram etc.
I have tried to get them to publish markdown sites using GitHub pages, but the pain of having to git commit and do it via desktop was the blocker.
So I recently made them a mobile app called JekyllPress [0] with which they can publish their posts similar to WordPress mobile app. And now a bunch of them regularly publish on GitHub pages. I think with more tools to simplify the publishing process, more people will start using GitHub pages (my app still requires some painful onboarding like creating a repo, enabling GitHub pages and getting PAT, no oAuth as I don't have any server).
It’s not really covered, but p2p technology combined with every phone in the world (and a little wishful thinking) could make for some neat applications.
I kind of resonate with a lot of things in the article. My own personal view is that we should make hosting stuff vastly simpler; that's one of the goals of my project, at least my attempt (self promo)
Thanks cap'n-py. Yeah, I love Sandstorm. My goal is to be more portable, lighter, and a 'download binary and run' kind of tool. There are also other attempts around what I call the 'packaging with Docker' approach (Coolify, etc.), which are more attempts at packaging existing apps. But my approach—the platform—gives a bunch of stuff you can use to make apps faster, but you have to bend to its idiosyncrasies. In turn, you do not need a beefy home lab to run it (not everyone is a tinkerer). It's more focused, so it will be easier for the end user running it than for the developer.
I think the main issue with federated apps is the identity and moderation. Without identity verification is hard to moderate so you end up with closed systems where some big CO does the moderation at an acceptable level
The current wave of AI agents is diminishing the value of identity as a DDOS or content-moderation signal. The formula until now included bot = bad, but unless your service wants to exclude everyone using OpenClaw and friends, that's no longer a valid heuristic.
If identity is no longer a strong signal, then the internet must move away from CAPTCHAs and logins and reputation, and focus more on the proposed content or action instead. Which might not be so bad. After all, if I read a thought-provoking, original, enriching comment on HN, do I really care if it was actually written by a dog?
One more half thought: what if the solution to the Sybil problem is deciding that it's not a problem? Go ahead and spin up your bot network, join the party. If we can design systems that assign zero value to uniqueness and require originality or creativity for a contribution to matter, then successful Sybil "attacks" are no longer attacks, but free work donated by the attacker.
> if I read a thought-provoking, original, enriching comment on HN, do I really care if it was actually written by a dog?
I would rather just read the thought as it was originally expressed by a human somewhere in the AI's training data, rather than a version of it that's been laundered through AI and deployed according to the separate, hidden intent of the AI's operator.
Unfortunately the transparency of the IP stack means that unless u want whole world to know where u live via one DNS query, you'd need to use a service to proxy back to urself. And if ur paying for remote compute anyways, you could probably just host ur stuff there. Any machine that can proxy traffic back to you is just as capable of hosting ur static stuff there.
I mean, you do have a point, and I'll quite agree with it. The only way of monetizing your writing is to use Substack or Medium, or whatever.
Yet your approach is appallingly low on the other side of the spectrum. I've been in IT for the past 25 years. I have yet to see a non-IT person who knows what dedicated IP is. If you are not publishing it on the internet, then what's the point?
I've seen plenty of companies where the owner just had a read-only shared drive, where people can rummage thru a pack of PDFs. This' was all fine with that.
You have to understand, manage and work with the complexities of the tools, and offer tools quite enough for the task. It's alright to offer what you do to an engineer who has a spare Pi and a couple of days to kill. But it's quite useless for anyone else to adopt.
Co-ownership of the hardware is a social not technical problem. Think of questions of trust, responsibility, who has power, who and how contributes, how decisions are made, etc, etc
I personally think the trend we witnessed with clawdbot where people ran to buy mac minis or other ways of self hosting ai agents is going to be a huge wind in the sails for generally hosting things at home.
> Simple to use software that empowers us to both read and write hypertext4 and syndicated content
Simple to use software... this would be grand!
> Raspberry Pi OS (a Linux distribution based on Debian GNU Linux)
Is this simple? I would contend that it is not. Why do I tell people "buy apple products" as a matter of course? Because they have decent security, great ease of use, and support is an Apple Store away.
They still manage to screw things up.
Look at the emergence of docker as an install method for software on linux. We sing the praises of this as means of software distribution and installation... and yet it's functionally un-usable by normal (read: non technical) people.
> I publish this site via GitHub Pages service for public Internet access
A whole post about not needing big corporations to publish things online, and then they use Microsoft to publish this thing online...
I think the point the author is trying to make is more so about these mini networks on their own LAN, which their family uses. (And maybe dreaming of a neighbourhood utility LAN as a middle ground between LAN in your house and WAN as just a trunk to a big ISP node) The full quote is
Yes, but that person owns their website, its content, and the address it lives at. They can publish anything they want, in any format they want.
Hosting on GitHub is merely a convenience; they can up and leave anytime.
As the author of a content management system I made with the idea to democratize internet content creation, I've had a lot of the same thoughts that the author brings up here. I've always thought that even learning Markdown was a bridge to far when it comes to empowering non-technical users however. In my experience it's best just to supply tooling similar to Word where you have buttons for things like lists and bolding. Using Markdown as the format itself is something I will agree with though.
Another thought I had is that local AI could most definitely play a part in helping non-technical users create the kind of content they want. If your CMS gives you a GPT-like chat window that allows a non-technical user to restyle the page as they like, or do things like make mass edits - then I think that is something that could help some of the issues mentioned here.
It's definitely an approach. I do think in true democratization of the internet, teaching people some tech is inevitable. We just can't have equal access if we retain the classes of user and maker as completely distinct.
The only way we own a web of our own is to develop much more of a culture of leaving smallish machines online all the time. Imagine something like Tor or BitTorrent, but everyone has a very simple way of running their own node for content hosting.
That always-on device? To get critical mass, instead of just the nerds, you'd need it to ship with devices which are always-on, like routers/gateways, smart TV's. Then you're back to being at the mercy of centralized companies who also don't love patching their security vulnerabilities.
This is very right. There are two obstacles.
(1) Security. An always-on, externally accessible device will always be a target for breaking in. You want the device to be bulletproof, and to have defense in depth, so that breaking into one service does not affect anything else. Something like Proxmox that works on low-end hardware and is as easy to administer as a mobile phone would do. We are somehow far from this yet. A very limited thing like a static site may be made both easy and bulletproof though.
(2) Connectivity providers should allow that. Most home routers don't get a static IP, or even a globally routable IPv4 at all. Or even a stable IPv6. This complicates the DNS setup, and without DNS such resources are basically invisible.
From the pure resilience POV, it seems more important to keep control of your domain, and have an automated way to deploy your site / app on whatever new host, which is regularly tested. Then use free or cheap DNS and VM hosting of convenience. It takes some technical chops, but can likely be simplified and made relatively error-proof with a concerted effort.
if only we all had a little device that was always on and and connected….
If I'm reading the implication right, you're having a pretty terrible idea. Glossing over what running a server would do to your battery, it would never work because of the routing issues you'll run into.
With IPv6 it would theoretically be possible, but currently with ipv4 and NATs everywhere, your website would almost never be reachable, even with fancy workarounds like dynDNS
This guy has been around long enough to know about NNTP, which is the original distributed people-focused web, but talks about how HTML is some kind of barrier to entry.
HTTP requires always-on + always-discoverable infrastructure
It's all over the place.
I don't wanna brag but this is pretty much the premise behind my soon-to-be-published scifi novel:
https://inkican.com/mesh-middle-grade-scifi-thriller/
It's not about ease of publishing. The issue is what people get in return for publishing. Until you can design a platform that gives top creators as much money+attention as commercial platforms, you'll see a drain of top creators and their viewers to commercial platforms.
I think this mostly misses the biggest reason why writers would choose big tech platforms or other big platforms: discovery and aggregation. If you want to speak to be heard and not just for its own sake, then you want to go where the people are hanging out and where they could actually find your content.
This is like talking about how book authors don't need Amazon when you have a printer and glue at home.
I agree with the point that big companies have persuaded people that only they can offer ease of publishing content. most of my friends publish on Facebook, X, Instagram etc.
I have tried to get them to publish markdown sites using GitHub pages, but the pain of having to git commit and do it via desktop was the blocker.
So I recently made them a mobile app called JekyllPress [0] with which they can publish their posts similar to WordPress mobile app. And now a bunch of them regularly publish on GitHub pages. I think with more tools to simplify the publishing process, more people will start using GitHub pages (my app still requires some painful onboarding like creating a repo, enabling GitHub pages and getting PAT, no oAuth as I don't have any server).
[0] https://www.gapp.in/projects/jekyllpress/
Isn’t publishing on Github Pages still posting to a corporate centrally owned entity and not a solution to the problem described?
It’s not really covered, but p2p technology combined with every phone in the world (and a little wishful thinking) could make for some neat applications.
I kind of resonate with a lot of things in the article. My own personal view is that we should make hosting stuff vastly simpler; that's one of the goals of my project, at least my attempt (self promo)
https://github.com/blue-monads/potatoverse
Potatoverse is a great name :)) BTW do you remember Sandstorm.io?
Thanks cap'n-py. Yeah, I love Sandstorm. My goal is to be more portable, lighter, and a 'download binary and run' kind of tool. There are also other attempts around what I call the 'packaging with Docker' approach (Coolify, etc.), which are more attempts at packaging existing apps. But my approach—the platform—gives a bunch of stuff you can use to make apps faster, but you have to bend to its idiosyncrasies. In turn, you do not need a beefy home lab to run it (not everyone is a tinkerer). It's more focused, so it will be easier for the end user running it than for the developer.
I think the main issue with federated apps is the identity and moderation. Without identity verification is hard to moderate so you end up with closed systems where some big CO does the moderation at an acceptable level
This is only half a thought.
The current wave of AI agents is diminishing the value of identity as a DDOS or content-moderation signal. The formula until now included bot = bad, but unless your service wants to exclude everyone using OpenClaw and friends, that's no longer a valid heuristic.
If identity is no longer a strong signal, then the internet must move away from CAPTCHAs and logins and reputation, and focus more on the proposed content or action instead. Which might not be so bad. After all, if I read a thought-provoking, original, enriching comment on HN, do I really care if it was actually written by a dog?
We might finally be getting close to https://xkcd.com/810/.
One more half thought: what if the solution to the Sybil problem is deciding that it's not a problem? Go ahead and spin up your bot network, join the party. If we can design systems that assign zero value to uniqueness and require originality or creativity for a contribution to matter, then successful Sybil "attacks" are no longer attacks, but free work donated by the attacker.
> if I read a thought-provoking, original, enriching comment on HN, do I really care if it was actually written by a dog?
I would rather just read the thought as it was originally expressed by a human somewhere in the AI's training data, rather than a version of it that's been laundered through AI and deployed according to the separate, hidden intent of the AI's operator.
Unfortunately the transparency of the IP stack means that unless u want whole world to know where u live via one DNS query, you'd need to use a service to proxy back to urself. And if ur paying for remote compute anyways, you could probably just host ur stuff there. Any machine that can proxy traffic back to you is just as capable of hosting ur static stuff there.
It only gives a pretty rough estimation, not a street address. I don't think many self-hosters have run into issue w/ this.
I mean, you do have a point, and I'll quite agree with it. The only way of monetizing your writing is to use Substack or Medium, or whatever.
Yet your approach is appallingly low on the other side of the spectrum. I've been in IT for the past 25 years. I have yet to see a non-IT person who knows what dedicated IP is. If you are not publishing it on the internet, then what's the point?
I've seen plenty of companies where the owner just had a read-only shared drive, where people can rummage thru a pack of PDFs. This' was all fine with that.
You have to understand, manage and work with the complexities of the tools, and offer tools quite enough for the task. It's alright to offer what you do to an engineer who has a spare Pi and a couple of days to kill. But it's quite useless for anyone else to adopt.
I like how it's not mobile friendly.
Co-ownership of the hardware is a social not technical problem. Think of questions of trust, responsibility, who has power, who and how contributes, how decisions are made, etc, etc
I personally think the trend we witnessed with clawdbot where people ran to buy mac minis or other ways of self hosting ai agents is going to be a huge wind in the sails for generally hosting things at home.
> Simple to use software that empowers us to both read and write hypertext4 and syndicated content
Simple to use software... this would be grand!
> Raspberry Pi OS (a Linux distribution based on Debian GNU Linux)
Is this simple? I would contend that it is not. Why do I tell people "buy apple products" as a matter of course? Because they have decent security, great ease of use, and support is an Apple Store away.
They still manage to screw things up.
Look at the emergence of docker as an install method for software on linux. We sing the praises of this as means of software distribution and installation... and yet it's functionally un-usable by normal (read: non technical) people.
Usability needs to make a comeback.
> great ease of use
Apple stuff is a nightmare of dark patterns and user-hostile idiocy.
Maybe it's easy if you have Stockholm syndrome and have internalized all the arcane gestures, icons and bug avoidance patterns.
The average normie has no clue, though. (This is borne from experience, I have like 8 iPhones in the immediate family among children and seniors.)
Who is this we, kemosabe?