this post was submitted on 08 Sep 2025
119 points (96.1% liked)
Selfhosted
59973 readers
442 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
HTTP 1.1 is more than good enough for serving a static website.
There is zero question about it. It will be absolutely fine for some dude's static website over a residential internet connection.
Same? HTTP/1.1 ran the entire internet for 20 years and is used by a ton of sites. It's fine for a personal website.
Although I agree with the implied sentiment that "the Perfect is the enemy of the Good Enough" (especially for low-profile personal web-presence) and that naval-gazing about protocols can become a counterproductive rabbit-hole, sometimes it can also be risky to oversimplify in the other direction without at least parenthesizing the caveats too. For example this "HTTP/1.1 must die" site points out how desync attacks make HTTP/1.1 robustness a bit of a game of Whack-a-Mole. For certain sites (even some personal sites) this can occasionally matter.
Obviously someone who has never actually tested 1.1 vs 2 vs 3 lmao