I can think of three reasons that more people don't have personal websites:
1. For non technical users (and there are lots of them) learning enough HTML and figuring out how to put it somewhere accessible is too high of a bar to overcome (forget about updating it ever). It's quicker and easier to just establish a presence on some social media site.
2. For technical users who are capable of setting up a website, it's easier to just go where people already are (i.e. social media).
3. It's anecdotal, but I rarely see anyone browsing the web these days. Most web usage seems to consist of endlessly scrolling through Facebook looking for something to interact with. A link to somewhere else might get clicked on, but the user always goes back to the newsfeed once they're done looking at the link.
There is a proverb: "If the Mountain won’t go to Mohammed, then Mohammed must come to the Mountain"
Most people don't have personal websites because getting an audience of users to a personal website is like asking a mountain to come to you.
Another proverb is: "Meet people where they are at"
There are exceptions to these proverbs but they require exceptional people or exceptional circumstances. The vast majority of people are not trying to be exceptional with respect to the kinds of things they would put on their personal websites. Very few individuals are willing to put the effort into "moving mountains" to build an audience on their own website.
4) tap through sign-up. Maybe type your name or other familiar details.
5) Nothing to do here because it already imported all your contacts, if relevant.
6) Post/message. You did this all from your phone. It was free. Everyone you care about automatically knows you’re there and how to reach you in the app. Tap camera icon to post pictures or video.
If you have trouble with any of it, ask literally anyone for help.
>The question I’ve been wondering lately is, “why don’t most people I meet have personal websites?”
Isn't it obvious? It's simply easier to use a social media platform that makes it easy to publish without having to know how to set up a server or mess with frameworks or code, and that makes it more likely that people will read what you have to say. The utility of personal websites has been replaced by services which solve both the problems of ease of publishing and ease of discovery and networking.
I absolutely loved reading potato.cheap- nice work!
I think there's currently a discoverability problem. I love small websites, blogs, passion projects etc and they give me 1000x more joy than social media posts. But I still don't really know a good way to discover them.
Hacker news is honestly probably the way that I find most small web stuff, I like kagi's "small internet" filter a lot too. But as a whole, the likes of google etc are really geared up towards funneling me into looking at posts in social media sites rather than anything else.
> “why don’t most people I meet have personal websites?”
The bigger question for me is, if it was dead simple and all they had to do was -say- pay $10/mo, would most people actually choose to have a personal website?
I think the issue comes down to most people not seeing enough value to have a personal site to pay for it. And if they don't want to pay, the free DIY options are either a site like Medium or the technical hurdles they have to jump through to get it up and running manually
> The question I’ve been wondering lately is, “why don’t most people I meet have personal websites?”
Because it's still nearly impossible for a non-tech person to create one. Facebook/Tiktok/Instagram offer a lot of what people would want from a personal website for free and give you connections to your friends/family/strangers
> The question I’ve been wondering lately is, “why don’t most people I meet have personal websites?”
The answer from my experience is simple: because most people that I meet are not programmers (at least not in a strict sense), and don't know many programmers.
On the other hand: most programmers and many STEM degree holders that I meet do have their own websites.
It's possible that a social media profile is the new website. Rather than stand alone as a single page, it's often connected to other people and orgs that you may want to be affiliated with, so it comes with its own relevant blogroll.
> The question I’ve been wondering lately is, “why don’t most people I meet have personal websites?”
Roughly in order: Blogging (as a concept), assholes, Google, social media.
I think the first real hit to personal websites was just the concept of blogging. Before blogging was a popular concept there was rarely an expectation someone's website would see constant updates. Just because they shared pictures from their vacation to Spain there was no assumption you found someone's travelogue that would see constant updates. You could "finish" a personal website.
There were of course plenty of sites that would see regular updates but they were free to set that expectation themselves. There's a conceit to blogging that it's something a person just keeps doing. A blog can never be considered complete. All of the organization is temporal and most of the time so is the navigation. If we find a blog that hasn't had updates in some time we've been conditioned to assume it's dead.
A follow on effect to blogging as a concept was the change in web page authoring software. It went from being designed to build a finite website to build continuous stream that is a blog. Organization of sites went from trees to lists. Tags and categories in most blogging software are just filters for temporally sorted lists of posts.
Because the conceit of blogging is constant updates, local first software was insufficient. It gave way to the likes of WordPress that could be accessed remotely so posts could come from anywhere. This helped kill the market for website authoring software.
Then of course came assholes. Even when you'd decide to start a blog, the Web 2.0 features that helped connect you to others like comments and *backs got abused by spammers and malware. Having a blog meant becoming an unpaid administrator and moderator or disabling all dynamic feedback mechanisms. In the worst case assholes turned your blog into a security liability.
Google adjusted their algorithms to favor recent content. This helped destroy the old style home pages because they became invisible to almost everyone. Unless a site had some very specific content that happened to tickle Google's algorithms just right its results would be on the 400th page of search results after a thousand blogspam links.
Finally social media just became the replacement for blogs and homepages. As an end user there's very little administration that needs to be done. Posting is quick and easy and doesn't ask for formalisms like document titles (naming this is often actually hard) on ontologies. The server administration is also handled by professionals so shitheads flooding your "site" don't rack up huge hosting bills. Content hosting is also handled with the same ease as other types of posts.
I'm not saying social media in inherently good or blogging is bad. I just think they contributed to killing the idea of having a home page.
I think Gemini has missed a trick being being deliberately too simple - e.g. no inline images, no tables, no forms, no basic formatting etc.
I know these were deliberately left out for "simplicity" reasons, but then they have a fairly unsimple mechanism for user login/auth that totally undermines their claim for making clients little more than slightly-augmented-terminals, which for me is a smoking gun for these things being missing purely on an ideological basis only and an attempt at controlling how people use it. That's fine, it's their thing and they can do what they want with it.
There is a growing trend of people simply choosing to use XHTML Basic (1). This is a "stripped down" version of HTML originally intended for early phones, PDAs, set top boxes etc - it has the critical missing features of Gemini, but forgoes some of the more "advanced" features of the modern web people have issues with. I'd highly recommend people simply target that instead.
wouldn't it just be better to start a new html5 without JS trend? It can the defector standard for document based web! A lot of modern CSS options to build nav menus now days[1]:
Form submit etc to send network traffics are all available, JS is only needed when you wanna do something cute like network call (AJAX) or change dom elements without refreshing the page. And come up with kluge such as allowing js to change the route with in the domain.
I like the gist and spirit of this, of course, but isn’t this basically impossible in today’s day and age? For instance, if I want to host a small web server running in my closet to serve cat memes to a small number of users, I still am beholden to my ISP who 1) must allow me to host a web server in its TOS and 2) provide me a static address.
I don’t really see any way to get around corporations on the internet, unless I’m missing something.
The easiest choice today is to use either GitHub Pages or Netlify to host your website. You can literally just drag and drop files on their Admin web page and have something immediatelly published online.
If you want to run code instead of just keep a static website, then you may need to get a cheap server from a multitude of companies that offer that (Linode, Digital Ocean, AWS etc) but I find that you can almost always get away with static sites which require next to no work and will stay up as long as those companies are still functioning (or don't shut down the free plan).
I don't know about elsewhere, but I regularly set up small self-hosted web servers at my home (Midwest US) and have never heard a peep from my ISP about it. Some of the aforementioned servers get 25 - 50 unique visits on a high day, and my ISP couldn't care less. I'm not sure they would unless I was calling a lot of traffic, which is not really a huge concern for Small Webbers. We are few and relatively unnoticed by the larger Internet, which is just the way we like it.
2) I have a fixed IPv4 address, and a dynamic IPv6. So far the latter also seems to be fairly stable, and I host my webpages on both IPv4 and IPv6 these days.
My server is a ThinkPad X240 with VMware ESXi which in turn host Ubuntu for SSH, Web, etc... And a Pi-hole VM just to block the "wost" of the internet.
ISPs that allow hosting web services are fairly common, but you're right, if all your local providers forbid it, you're probably out of luck.
For your second point, Dynamic DNS is super useful. I've had a good experience with noip.com/ddns.net, but there are plenty of other options out there.
If anything I think it's easier today than it was 10 or 20 years ago. There are plenty of free static hosts, free tiers on various cloud hosts for interactive sites, and services like ngrok or Cloudflare Tunnels that can safely expose a home server to the internet.
Edit: I’m watching it and it is done in an entertaining style but is a bit loose on some details I know about, such as implying that the IBM PC development was started in the early 1970’s when it was in fact started in 1980. Still worth watching so far.
Edit 2: finished, it is definitely worth watching. It goes into “The Twilight Zone” of a very interesting alternative history. And does a good job reporting on the Gary Kildall / IBM missed deal for their PC OS.
Correct me if I’m wrong, but weren’t slashes typically reserved for flags on Unix and back slashes on dos/windows? If that’s the case then surely the vertices line, pipe symbol |, would be the most visually appropriate? Piping remote data over a network connection and through the local client program to parse seems to be the kind of thing bike shedding was intended for, in agreement but focusing on semantics. It just seems new by safe and only requires reprogramming the kernel for the shell semantics.
# gemeni:|bike.domain.com|shed
Or even better, everything is little endian to allow autocomplete from previous entries by the user in the shell so that once the user hits the domain keyword the shell history parser assumes the user wants to stay on the site
# gemeni:|shed|bike|domain|com
I’m not sure how feasible this as I’ve never written an internet or shell language
Maybe I'm mis-reading the URI spec [0], but it seems that // is required to separate the scheme from the "authority" part when it's present (as it is for my.domain.com).
I am under the impression that an unstated design objective of gemini was preventing eternal september by trading it off for staying an eternal echo chamber tobe inhabited only by people smart enough to write their own client and server software.
It's limited to those that are primarily interested in text (and the occasional image). Which probably prevents it from ever going mainstream (and thus an eternal september). What it's generally sacrificing is interactivity.
That seems like it's shooting more for the early internet. Which, yeah, has quite a bit of overlap with people who can code, but not as much as you're implying. And I do remember quite a few echo chambers on the early internet, but I remember a lot less of them without algorithmic feeds. Just by chance, you'd end up running across a bunch of people who disagree with you on a lot of things.
The article title didn't express what this was about, but it seems seems to be a revival of the old, pre-WWW web, via a new protocol Gemini.
I'm not sure why it's "poor man's" web, other than being minimalistic (text and images only.) I thought the phrase meant something less desirable to use, less capable. But this could be genuinely pleasant!
The problem with most of these discussions is they assume Gemini is a substitute for the web, when it is actually a substitute for Gopher.
Gopher never really went away. A few enthusiasts were keeping it alive. Those enthusiasts realized that Gopher had a number of shortcomings, so Gemini was created to address those shortcomings. It was not created to address the shortcomings of the web. (At least not directly. Indirectly one could argue those enthusiasts kept Gopher alive due to the shortcomings of the web.)
As for styling and inline images: in a sense, Gemini offers styles to a limited degree. Those styles are tied to the structure of the document, while the appearance is left to the software rendering the document. Even though inline images are considered a faux pas, I seem to recall Lagrange offering that feature. Again, we are dealing with the rendering software making the decision rather than the author. Since the end user chooses and configures the rendering software, it is the end user who has control (rather than the author).
I agree that basic styling and in-line images add something, but I like how Gemini strips so much faff out that the prose and links must stand strongly on their own.
I've taken to writing my markdown and other documetns simiarly. Cory Doctorow does something similar.
My feeling is that Gemini's entire purpose is being opinionated and somewhat inconvenient. It purposefully threw the baby out because it didn't want the baby.
Everything Gemini does, you can do it in HTTP. In fact, a subset of HTTP+HTML would be even simpler than Gemini (mostly because of a lack of TLS) and still compatible with all the modern web stack. Simplicity isn't the main goal of Gemini. Exclusiveness is.
Nice little article but I could hardly disagree more with the
headline.
The small web is not for poor men and women. It's for the
rich. Those who are rich in culture, intelligence, curiosity,
engagement...
The existing "web" is for the technologically poor. It's a chavvy,
shallow plastic shit-filled trench, a ghetto where thieves and pimps
run free, and good ideas die like dogs - to somewhat paraphrase Hunter
S. Thompson. I can't see anything of value left there, and cannot
imagine how anyone would equate leaving it behind with being poorer.
If Gemini really wanted to embrace a world of writing then they should've had the elements which HTML lacked, such as a table of contents or bibliography.
surprisetalk|2 years ago
[1] https://potato.cheap
IMO, protocol is largely a distraction from the good stuff.
The question I’ve been wondering lately is, “why don’t most people I meet have personal websites?”
basscomm|2 years ago
1. For non technical users (and there are lots of them) learning enough HTML and figuring out how to put it somewhere accessible is too high of a bar to overcome (forget about updating it ever). It's quicker and easier to just establish a presence on some social media site.
2. For technical users who are capable of setting up a website, it's easier to just go where people already are (i.e. social media).
3. It's anecdotal, but I rarely see anyone browsing the web these days. Most web usage seems to consist of endlessly scrolling through Facebook looking for something to interact with. A link to somewhere else might get clicked on, but the user always goes back to the newsfeed once they're done looking at the link.
zoogeny|2 years ago
Most people don't have personal websites because getting an audience of users to a personal website is like asking a mountain to come to you.
Another proverb is: "Meet people where they are at"
There are exceptions to these proverbs but they require exceptional people or exceptional circumstances. The vast majority of people are not trying to be exceptional with respect to the kinds of things they would put on their personal websites. Very few individuals are willing to put the effort into "moving mountains" to build an audience on their own website.
wharvle|2 years ago
1) search name
2) install app
3) open app
4) tap through sign-up. Maybe type your name or other familiar details.
5) Nothing to do here because it already imported all your contacts, if relevant.
6) Post/message. You did this all from your phone. It was free. Everyone you care about automatically knows you’re there and how to reach you in the app. Tap camera icon to post pictures or video.
If you have trouble with any of it, ask literally anyone for help.
Personal website:
1) ???????
krapp|2 years ago
Isn't it obvious? It's simply easier to use a social media platform that makes it easy to publish without having to know how to set up a server or mess with frameworks or code, and that makes it more likely that people will read what you have to say. The utility of personal websites has been replaced by services which solve both the problems of ease of publishing and ease of discovery and networking.
benrutter|2 years ago
I think there's currently a discoverability problem. I love small websites, blogs, passion projects etc and they give me 1000x more joy than social media posts. But I still don't really know a good way to discover them.
Hacker news is honestly probably the way that I find most small web stuff, I like kagi's "small internet" filter a lot too. But as a whole, the likes of google etc are really geared up towards funneling me into looking at posts in social media sites rather than anything else.
emrah|2 years ago
The bigger question for me is, if it was dead simple and all they had to do was -say- pay $10/mo, would most people actually choose to have a personal website?
I think the issue comes down to most people not seeing enough value to have a personal site to pay for it. And if they don't want to pay, the free DIY options are either a site like Medium or the technical hurdles they have to jump through to get it up and running manually
troupo|2 years ago
Because it's still nearly impossible for a non-tech person to create one. Facebook/Tiktok/Instagram offer a lot of what people would want from a personal website for free and give you connections to your friends/family/strangers
aleph_minus_one|2 years ago
The answer from my experience is simple: because most people that I meet are not programmers (at least not in a strict sense), and don't know many programmers.
On the other hand: most programmers and many STEM degree holders that I meet do have their own websites.
unknown|2 years ago
[deleted]
ArekDymalski|2 years ago
I think that valuable follow-up question would be "Should they have one?"
threatofrain|2 years ago
giantrobot|2 years ago
Roughly in order: Blogging (as a concept), assholes, Google, social media.
I think the first real hit to personal websites was just the concept of blogging. Before blogging was a popular concept there was rarely an expectation someone's website would see constant updates. Just because they shared pictures from their vacation to Spain there was no assumption you found someone's travelogue that would see constant updates. You could "finish" a personal website.
There were of course plenty of sites that would see regular updates but they were free to set that expectation themselves. There's a conceit to blogging that it's something a person just keeps doing. A blog can never be considered complete. All of the organization is temporal and most of the time so is the navigation. If we find a blog that hasn't had updates in some time we've been conditioned to assume it's dead.
A follow on effect to blogging as a concept was the change in web page authoring software. It went from being designed to build a finite website to build continuous stream that is a blog. Organization of sites went from trees to lists. Tags and categories in most blogging software are just filters for temporally sorted lists of posts.
Because the conceit of blogging is constant updates, local first software was insufficient. It gave way to the likes of WordPress that could be accessed remotely so posts could come from anywhere. This helped kill the market for website authoring software.
Then of course came assholes. Even when you'd decide to start a blog, the Web 2.0 features that helped connect you to others like comments and *backs got abused by spammers and malware. Having a blog meant becoming an unpaid administrator and moderator or disabling all dynamic feedback mechanisms. In the worst case assholes turned your blog into a security liability.
Google adjusted their algorithms to favor recent content. This helped destroy the old style home pages because they became invisible to almost everyone. Unless a site had some very specific content that happened to tickle Google's algorithms just right its results would be on the 400th page of search results after a thousand blogspam links.
Finally social media just became the replacement for blogs and homepages. As an end user there's very little administration that needs to be done. Posting is quick and easy and doesn't ask for formalisms like document titles (naming this is often actually hard) on ontologies. The server administration is also handled by professionals so shitheads flooding your "site" don't rack up huge hosting bills. Content hosting is also handled with the same ease as other types of posts.
I'm not saying social media in inherently good or blogging is bad. I just think they contributed to killing the idea of having a home page.
mattlondon|2 years ago
I know these were deliberately left out for "simplicity" reasons, but then they have a fairly unsimple mechanism for user login/auth that totally undermines their claim for making clients little more than slightly-augmented-terminals, which for me is a smoking gun for these things being missing purely on an ideological basis only and an attempt at controlling how people use it. That's fine, it's their thing and they can do what they want with it.
There is a growing trend of people simply choosing to use XHTML Basic (1). This is a "stripped down" version of HTML originally intended for early phones, PDAs, set top boxes etc - it has the critical missing features of Gemini, but forgoes some of the more "advanced" features of the modern web people have issues with. I'd highly recommend people simply target that instead.
1 - https://en.m.wikipedia.org/wiki/XHTML_Basic
krapp|2 years ago
factormeta|2 years ago
Form submit etc to send network traffics are all available, JS is only needed when you wanna do something cute like network call (AJAX) or change dom elements without refreshing the page. And come up with kluge such as allowing js to change the route with in the domain.
Footnotes: 1.https://1stwebdesigner.com/pure-css-navigation-menus/
JohnMakin|2 years ago
I don’t really see any way to get around corporations on the internet, unless I’m missing something.
anamexis|2 years ago
I don't have a static IP, but it only changes on the order of weeks or months. So a dynamic DNS configuration with a 5 minute TTL works fine for me.
I have no idea if web hosting is in my ISP's TOS, and I also don't care.
brabel|2 years ago
If you want to run code instead of just keep a static website, then you may need to get a cheap server from a multitude of companies that offer that (Linode, Digital Ocean, AWS etc) but I find that you can almost always get away with static sites which require next to no work and will stay up as long as those companies are still functioning (or don't shut down the free plan).
0xEF|2 years ago
torh|2 years ago
2) I have a fixed IPv4 address, and a dynamic IPv6. So far the latter also seems to be fairly stable, and I host my webpages on both IPv4 and IPv6 these days.
My server is a ThinkPad X240 with VMware ESXi which in turn host Ubuntu for SSH, Web, etc... And a Pi-hole VM just to block the "wost" of the internet.
jw_cook|2 years ago
For your second point, Dynamic DNS is super useful. I've had a good experience with noip.com/ddns.net, but there are plenty of other options out there.
kej|2 years ago
arkh|2 years ago
> gem:my.domain.com/hello
AlbertoGP|2 years ago
Didn’t know about it, here is the video of that talk in YouTube:
https://www.youtube.com/watch?v=8JOD1AQGqEg
There is a poem-style intro titled “Flatscreens / a song about code” until the talk proper starts at 5’11”:
https://www.youtube.com/watch?v=8JOD1AQGqEg?t=311
Edit: I’m watching it and it is done in an entertaining style but is a bit loose on some details I know about, such as implying that the IBM PC development was started in the early 1970’s when it was in fact started in 1980. Still worth watching so far.
Edit 2: finished, it is definitely worth watching. It goes into “The Twilight Zone” of a very interesting alternative history. And does a good job reporting on the Gary Kildall / IBM missed deal for their PC OS.
guestbest|2 years ago
# gemeni:|bike.domain.com|shed
Or even better, everything is little endian to allow autocomplete from previous entries by the user in the shell so that once the user hits the domain keyword the shell history parser assumes the user wants to stay on the site
# gemeni:|shed|bike|domain|com
I’m not sure how feasible this as I’ve never written an internet or shell language
chatmasta|2 years ago
[0] https://datatracker.ietf.org/doc/html/rfc3986#section-3.2
fabianholzer|2 years ago
Kamq|2 years ago
It's limited to those that are primarily interested in text (and the occasional image). Which probably prevents it from ever going mainstream (and thus an eternal september). What it's generally sacrificing is interactivity.
That seems like it's shooting more for the early internet. Which, yeah, has quite a bit of overlap with people who can code, but not as much as you're implying. And I do remember quite a few echo chambers on the early internet, but I remember a lot less of them without algorithmic feeds. Just by chance, you'd end up running across a bunch of people who disagree with you on a lot of things.
aleph_minus_one|2 years ago
danishbread|2 years ago
I'm not sure why it's "poor man's" web, other than being minimalistic (text and images only.) I thought the phrase meant something less desirable to use, less capable. But this could be genuinely pleasant!
troupo|2 years ago
I will keep repeating that in its quest for simplicity Gemini threw the baby out of with the water.
Basic styling and inline images are invaluable.
II2II|2 years ago
Gopher never really went away. A few enthusiasts were keeping it alive. Those enthusiasts realized that Gopher had a number of shortcomings, so Gemini was created to address those shortcomings. It was not created to address the shortcomings of the web. (At least not directly. Indirectly one could argue those enthusiasts kept Gopher alive due to the shortcomings of the web.)
As for styling and inline images: in a sense, Gemini offers styles to a limited degree. Those styles are tied to the structure of the document, while the appearance is left to the software rendering the document. Even though inline images are considered a faux pas, I seem to recall Lagrange offering that feature. Again, we are dealing with the rendering software making the decision rather than the author. Since the end user chooses and configures the rendering software, it is the end user who has control (rather than the author).
antiframe|2 years ago
I've taken to writing my markdown and other documetns simiarly. Cory Doctorow does something similar.
https://pluralistic.net/2023/12/20/em-oh-you-ess-ee/#sexytim...
We don't need Gemini. We can get the feeling of the Smol Web by just choosing an effective subset of the features of HTML.
GuB-42|2 years ago
Everything Gemini does, you can do it in HTTP. In fact, a subset of HTTP+HTML would be even simpler than Gemini (mostly because of a lack of TLS) and still compatible with all the modern web stack. Simplicity isn't the main goal of Gemini. Exclusiveness is.
nonrandomstring|2 years ago
The small web is not for poor men and women. It's for the rich. Those who are rich in culture, intelligence, curiosity, engagement...
The existing "web" is for the technologically poor. It's a chavvy, shallow plastic shit-filled trench, a ghetto where thieves and pimps run free, and good ideas die like dogs - to somewhat paraphrase Hunter S. Thompson. I can't see anything of value left there, and cannot imagine how anyone would equate leaving it behind with being poorer.
spiritplumber|2 years ago
threatofrain|2 years ago
chwilson|2 years ago
[1]https://github.com/skyjake/lagrange
chrsw|2 years ago
1vuio0pswjnm7|2 years ago