HackerURLs

一次又一次被重新发现的经典。

同一个链接,相隔一年以上,一次又一次被人重新发现、再次冲上 Hacker News 首页。能经受住这种时间检验的,大多是值得一读再读的文章。每篇附中文标题,讨论最热的那些再加上中文导读和高赞评论翻译。

从名人堂开始
  • 4,700+篇经过时间检验的经典

Hall of fame

名人堂

在经典库里看全部精选

上首页次数最多、而且有中文导读的 30 篇。时间轴上每个黑点是一次上首页,空心点是一次没冲上去的投稿。

  1. 正在载入经典…

Archive

经典库

按第一次上首页的年份分布,点柱子筛选。

排序

    About

    这些经典是怎么挑出来的

    1. 01

      合并同一个链接

      读取 Hacker News 自 2006 年以来的全部链接投稿,把 http/https、www、跟踪参数等写法不同的同一篇文章合并成一条。

    2. 02

      只留经得起时间的

      同一链接至少两次拿到 50 分以上(约等于上首页),而且两次相隔一年以上;再由 AI 剔除状态页、产品首页和新闻事件。

    3. 03

      写导读、译评论

      上首页次数最多的 2,000 篇配上中文导读、"为什么经久不衰",并精选翻译 HN 高赞评论。导读由 AI 生成,可能有误。

    互联网与文化interconnected.org

    我希望我的 Web 服务器就在房间角落

    I wish my web server were in the corner of my room

    2次上首页
    3年跨度
    706累计得分
    535条评论

    2022 — 2025,它一次次回到首页

    黑点是上首页(≥ 50 分)的那次投稿,空心点是没冲上去的投稿,点越大分数越高。

    导读

    这是 Matt Webb(interconnected.org)的一篇随笔:他希望自己的网站跑在房间角落里的一台小机器上,而不是托管在某个遥远的数据中心——服务器作为一件有实体、有存在感的家当,让「我的网站」重新变得可触摸、可拥有。文中也坦率列出了这样做的现实顾虑(断电断网、流量突增、速度、家庭网络被攻破),以及为什么这种自托管的小型个人网络值得向往。

    为什么经久不衰:它触到了很多人对「早期互联网」的怀念:网站是属于自己的一台机器、一个房间、一个人,评论区十几年后仍在用亲身经历回应这份乡愁。

    关键词 自托管个人网站家庭服务器独立网络

    HN 评论精选

    有实战经验的自托管者逐条回应文中顾虑:可靠性、带宽、性能与安全都有可行解法。

    作为一个在房间角落托管了多个网站和邮件服务的人说几句:如果想要「踢掉网线也可靠」,那还是得在家庭之外有一台备用主机;担心流量突增的话,如果你不提供音视频这类媒体文件,DSL 或移动数据就够了——按当前页面 100KB 计算,1MiB/s 上传可以支撑每秒 10 个访客。想要快?它现在在 DigitalOcean 上并不快(TLS 2 秒、HTML 12 秒……总共 27 秒),只会更好。建议用比树莓派更强的机器,我自己用一台旧笔记本,性能足够,而且不用渲染 GUI。至于怕家里网络被黑:装自动安全更新、给管理后台加基础认证、别托管你不信任的代码。

    lucb1e查看英文原文

    Speaking as someone who hosts multiple websites, email, etc. in the corner of a room > [it should] be reliable if I kick a cable out of the wall Right, if you want it to be reliable but also be able to cut its cables, then you will need a secondary host outside the home. > or in the unlikely event that I get a bunch of traffic. Are you serving media (music or video of more than a few seconds)? If not: DSL or mobile data (if your data cap allows) is fine for HN front page. Judging by the current page weighing 100KB, you can have 10 visitors every second at 1 MiB/s upload. (HN reaches that rate only in spikes, even at a top three position.) > I’d also like it to be quick! It's currently not quick at DigitalOcean (2 seconds for TLS setup, 12 seconds for HTML, 8 seconds for JavaScript, etc... 27 seconds total). It can only get better! I can recommend something beefier than a raspberry pi, though, or at least than than the pi 1-3 speeds that I'm used to. I personally use an old laptop which is plenty fast for, well, anything you'd also ask of a daily driver, except it now doesn't need to render a GUI which speeds things up a lot. They can peak up to 100W depending on the model, but are usually very low power when nothing is being asked of them. > Oh, and I don’t want to have my home network hacked. Then install unattended-upgrades, put admin panels (phpmyadmin, wp-admin) behind basic authentication, don't host things you don't trust (random code written by 'someone on the internet' that has never been tested by anyone), put it in a VLAN if you want to be extra cautious, and you'll be fine. It never hurts to keep your phone and other systems on the LAN up-to-date anyhow so they should be secure as well, even if someone does get in.

    技术上完全可行,缺的是把自托管整合成像装 App 一样简单的产品体验。

    那么 2022 年实际该怎么做?坦白说,我们让用户失望了。自托管本该和装一个手机 App 一样简单、一样安全,你不该需要懂 DNS、TLS、NAT、HTTP、TCP、UDP;域名的购买和使用不该比电话号码更难;应用该跑在 Windows/Mac/Linux 上默认安全的虚拟机沙箱里;对外暴露应该只是一次 OAuth 式的授权,把某个应用绑到某个子域名上,证书自动从 Let's Encrypt 获取并保存在本地做端到端加密。这些技术都已存在,只是没人把它们粘成一个真正好用的产品,目前几乎所有方案都面向开发者而非自托管用户。

    anderspitman查看英文原文

    > So… practically: how to achieve this in 2022? I'll paraphrase myself from a few days ago[0]: The reality is that we've let you down. Self-hosting shouldn't be any more complicated or less secure than installing an app on your phone. You shouldn't need to understand DNS, TLS, NAT, HTTP, TCP, UDP, etc, etc. Domain names shouldn't be any more difficult to buy or use than phone numbers. Apps should be sandboxed in KVM/WHPX/HVP-accelerated virtual machines that run on Windows, Mac, and Linux and are secure-by-default. Tunneling out to the public internet should be a quick OAuth flow that lets you connect a given app to a specific subdomain, with TLS certs automatically obtained from Let's Encrypt and stored locally for end-to-end encryption. The technology exists to do all of these things, but no one has taken the time to glue it all together in a truly good UX (we're working on it). Pretty much every solution in this space is targeted at the developer market, not self-hosters. [0]: https://news.ycombinator.com/item?id=33098471

    自托管的小站曾成为一个班级真正的社交空间,这是中心化平台给不了的。

    高中时我在自己房间跑了一个 phpbb 论坛。当时学校刚推行「一人一笔记本」,机器全被锁死、好玩的网站基本都被封,唯独我的站没被封,因为 IT 不知道它的存在。于是大家都跑来聊天,我们还架了 IRC 服务器,现实中不同圈子的人在这里成了朋友。有一次上课本该做作业,全班却都在 IRC 上,教室安静得诡异,有人发了句「谁来说一句 penis」,整个教室毫无征兆地同时爆笑,老师一脸茫然。那是 15 岁、瞎折腾电脑的好时光。

    rozap查看英文原文

    I hosted a phpbb board out of my room during high school. Our school board had just done the "one laptop per kid" thing, and the machines were all locked down and most of the fun sites were blocked, but not my site, because IT didn't know about it. So everyone went there to chat. We had an IRC server. People became friends that otherwise were in different cliques irl. One time we were supposed to be doing work during class, but everyone was on IRC chatting. The classroom was completely silent. Somebody wrote "somebody say penis" in the channel and the whole classroom started laughing at the same time, for seemingly no reason. The teacher was confused, it was a good time to be a 15 year old dorking around with computers.

    2025 年的现状:家庭自托管确实可行,但要接受 IP 变动和 98% 的可用性。

    没错,我的网站(还很粗糙)就跑在公寓角落的一台树莓派 5 上。偶尔 IP 变了,我得更新 DNS,再告诉朋友用 IP 连我的 Minecraft 服务器。可用性大概 98%,差不多是 GitHub 级别的保障。

    hnuser123456查看英文原文

    Yep, my website (very WIP) is hosted on an RPi 5 in the corner of my apartment, and every once in a while my IP changes and I have to update DNS and tell my friends to connect to the minecraft server by IP. I'm probably around 98% uptime, so github levels of assurance.

    历次讨论

    同类还值得读

    1. 如今电脑上几乎所有操作在感知上都比 1983 年更慢(2017)

      Almost everything on computers is perceptually slower than it was in 1983 (2017)

      2017 年的推文串认为,尽管计算机硬件比 1983 年快得多,日常操作的感知速度却常常更慢:启动、界面响应和网络应用被层层抽象、动画、后台检查与网络依赖拖累。

      互联网与文化上首页 5 次 · 2017–2020twitter.com
    2. 网站肥胖危机

      The Website Obesity Crisis

      Maciej Cegłowski(idlewords)的经典演讲文稿《网站肥胖症危机》,批评现代网页越来越臃肿:动辄数 MB 的 JavaScript、追踪脚本和广告,把本可以轻…

      互联网与文化上首页 5 次 · 2016–2021idlewords.com编辑精选
    3. 亚马逊那本标价 23,698,655.93 美元的苍蝇书

      Amazon’s $23,698,655.93 book about flies

      博文讲的是亚马逊上一本关于果蝇的二手书被标到 23,698,655.93 美元。

      互联网与文化上首页 5 次 · 2011–2022michaeleisen.org
    4. 浏览器 User-Agent 字符串的历史

      History of the browser user-agent string (2008)

      2008 年的经典文章用戏谑的“创世纪”口吻,讲述浏览器 User-Agent 字符串如何从简单的标识演变成层层叠加的伪装:浏览器为了绕过按 UA 分发的网站检测,纷纷把自己伪装…

      互联网与文化上首页 5 次 · 2012–2022webaim.org编辑精选
    5. 最后的问题——艾萨克·阿西莫夫

      The Last Question - Isaac Asimov

      阿西莫夫最著名的短篇科幻小说《最后的问题》的在线全文。

      互联网与文化上首页 5 次 · 2009–2019multivax.com编辑精选

    打赏支持

    打赏二维码

    觉得有用,请作者喝杯咖啡。

    WeChat

    关注向阳乔木

    微信公众号「向阳乔木推荐看」

    微信公众号「向阳乔木推荐看」二维码

    微信扫一扫;在微信里打开本页时,长按二维码识别。