Live data from Hacker News

A simple web we own

rsdoiel.github.io

61–70 of 240 posts

Re: A simple web we own

#61

The irony of this being fully hosted on GitHub should not be lost. A toaster is sufficient to host a mostly static site, a VPS would be far more than sufficient.

You think you "own" a VPS?

Well, you pay for it at least, and hence enter into a contract with the service provider. A free GitHub account is a come-on by Microsoft to enmesh you further in the world of hosted services - the precise thing this manifesto is complaining about

Re: A simple web we own

#62
I really do agree with the sentiment of this guy. I am this guy mentally but what he is saying is so painfully out of touch and completely ignores how people actually use the web today. My bro the web isnt controlled by corps because its to hard to host a web page. Corps have created these extremely far reaching and complex applications and people prefer to use those than browser through statically generated pages. Average man doesnt want to come home and update his page he just wants to open the app on his phone, scroll for a bit and close it.

The problem is in the environment but also the user behavior. Unless you can provide a convincing argument to change both by presenting an actual improvement then its farting in the wind

Re: A simple web we own

#63

I remember a web when practically every ISP allowed you to have a "home page" hosted with them. Your home page was situated in the "public_html" directory of your home directory on their server — hence the name. Then the URL was http://www. /~ I haven't see an URL with a tilde ('~') in it in a long time. Why did ISPs stop with this service? Was it to curb illegal file sharing?

i think Apache sets this up by default or use to. Every user on Linux would get a www, or maybe it was htdocs, folder in their home directory when they were added to the system. Any file you put there is served by Apache at resource /~ which was reading from /home//www on the file system.

There use to be lots and lots of ISPs and so they were small enough to have a single webserver with all their customers setup as users and Apache serving content. They'd also setup FTP on the same server so you could get your html files into your www folder. Software like Dreamweaver had a ftp client built in, so you'd click like a "publish" button and it wold login to FTP and transfer your files.

i would imagine this went away because it got expensive as the customer base grew and ISPs consolidated and it made no money. Other options with php, mysql, and other services cropped up and could offer more and charge for it so I think ISPs just preferred to concentrate on network access and not hosting websites.

Re: A simple web we own

#64
I enjoyed the article, but I’m skeptical of the “democratize via hardware + networking” path. Most people won’t run a Pi, manage updates/backups, or debug home networking, and that’s fine (as you note).

But I do think we’re reaching a turning point on the software side. The barrier to building custom, personalized apps is trending toward 0. I’m not naive enough to think every grandma will suddenly start asking ChatGPT to “build me an app to do XYZ,” but with the right UX it can be implicit. Imagine you tell an assistant: “My doctor says my blood sugar is high. Research tips to reduce it.” -> it not only replies with tips, it also proactively builds a custom app (that you own and control) for tracking your blood sugar (measurements, meals, reminders, charts, etc.). You can edit it by describing changes (“add a weekly trend graph,” “don’t nag me after 8pm,” etc.).

This doesn’t fully solve your Big Co control issue (they own the flagship models today), but open-weight + local options keep improving. I'm hopeful we have a chance to tip the scales back toward co-owner and participant.

Re: A simple web we own

#65

The real barrier was never technical. It was convenience and discovery. Running a Pi at home is trivial for anyone on HN, but the moment you want people to actually find your stuff, you need DNS, a stable IP, and some way to not get buried under the noise. Tailscale and similar overlay networks have made the "accessible from anywhere" part way easier than it used to be. The missing piece is still discovery. RSS was t…

What does “bringing (RSS) back properly” entail in your eyes? It’s still alive. Many sites still use it. Many people still subscribe to those sites. RSS reader apps are still being created to this day.

RSS directories perhaps, instead of relying on search engines.

Re: A simple web we own

#66

I enjoyed the article, but I’m skeptical of the “democratize via hardware + networking” path. Most people won’t run a Pi, manage updates/backups, or debug home networking, and that’s fine (as you note). But I do think we’re reaching a turning point on the software side. The barrier to building custom, personalized apps is trending toward 0. I’m not naive enough to think every grandma will suddenly start asking ChatGP…

"it also proactively builds a custom app"

Does it deploy it as well?

Re: A simple web we own

#67

I enjoyed the article, but I’m skeptical of the “democratize via hardware + networking” path. Most people won’t run a Pi, manage updates/backups, or debug home networking, and that’s fine (as you note). But I do think we’re reaching a turning point on the software side. The barrier to building custom, personalized apps is trending toward 0. I’m not naive enough to think every grandma will suddenly start asking ChatGP…

> You can edit it by describing changes

Even this is hard. Most people don't know what they want, and/or they don't know how to describe it/imagine it. They don't even know what a trend graph is.

They just want someone else to do the mental effort of creating a nice product. Hence iOS > android for most people. They don't want to customise basically anything other than colours.

That's why i predict Lovable/replit etc will not go mainstream. And why chatgpt will just offer you their UIs mainly. Artifacts weren't a big hit

Re: A simple web we own

#68
post #53

Earlier quoted context omitted.

But it is portable. It is essentially markdown files. You can download your repo, compile the Jekyll to static pages and publish them anywhere. When you publish to Facebook, WordPress etc you can't easily get your stuff out. You will have to process them even if they allow you to download your content as a zip folder. The images will be broken. Links between pages won't work etc.

Facebook provides a data export service which gives you a zip file with a web version of all your content. I’m not sure what the difference is then between that and a Github hosted repository of all your content as a webpage.

The main difference is the data structure and the intent of the export. Facebook's tool is built for data compliance and local offline viewing, not web portability. If you open that Facebook zip file, the HTML version is just a massive dump of proprietary markup. To actually migrate those posts to a new blog, you'd have to write a custom scraper just to extract your own text from their messy div tags. If you use their JSON export, you still have to write a custom script to parse their specific schema and remap all the hardcoded local image paths so they work on a live server. With a Github Pages repo, your content is already sitting there as raw, standardized Markdown. You can just take that folder of .md files, drop it into Hugo, 11ty, or any other static site generator, and it just works. No scraping or data-wrangling required.

Re: A simple web we own

#69

I enjoyed the article, but I’m skeptical of the “democratize via hardware + networking” path. Most people won’t run a Pi, manage updates/backups, or debug home networking, and that’s fine (as you note). But I do think we’re reaching a turning point on the software side. The barrier to building custom, personalized apps is trending toward 0. I’m not naive enough to think every grandma will suddenly start asking ChatGP…

> You can edit it by describing changes Even this is hard. Most people don't know what they want, and/or they don't know how to describe it/imagine it. They don't even know what a trend graph is. They just want someone else to do the mental effort of creating a nice product. Hence iOS > android for most people. They don't want to customise basically anything other than colours. That's why i predict Lovable/replit etc…

If you've never worked in a call center, or in a technical support role, it can be hard to understand just how inarticulate people are on average. Even programmers.

...And how much brainpower goes into understanding what people like this are getting at when they speak about things. There's a lot of context and human element to this; I'm skeptical AI will be any good at it in the near future.

Re: A simple web we own

#70

I enjoyed the article, but I’m skeptical of the “democratize via hardware + networking” path. Most people won’t run a Pi, manage updates/backups, or debug home networking, and that’s fine (as you note). But I do think we’re reaching a turning point on the software side. The barrier to building custom, personalized apps is trending toward 0. I’m not naive enough to think every grandma will suddenly start asking ChatGP…

I mean -- my (completely non-technical) mother, after a few hours of my guidance, has started vibe-coding apps and websites for her local community organizations. And, like -- it works.
Post reply on HN