The Hacker News Reading Workflow: 50 Links, Zero Tabs | GoPeek
Workflow<br>Hacker News<br>Productivity
The Hacker News Reading Workflow: 50 Links, Zero Tabs
June 14, 2026<br>6 min read<br>By GoPeek Team
Hacker News front page: 30 links. Comments: 200 more. Tabs opened: zero.
Hacker News is a trap. The front page has 30 links. Each comment thread has 10 to 50 more links — to GitHub repos, blog posts, papers, videos, and tools. A single HN session can expose you to 100 links. And the natural instinct is to open them all.
Open the article. Open the repo. Open the paper. Open the Show HN. Open the related blog post someone linked in comment #47. You now have 20 tabs. You have not finished the front page. And you have definitely not read the comments.
This is not a discipline problem. It is a tool problem. Hacker News is designed for link density. Every headline is a link. Every comment is a link. The site assumes you will click. But your browser treats every click as a commitment — a new tab, a new process, a new context switch. By the time you reach the bottom of the front page, your browser is wheezing and you have forgotten half the headlines.
Here is how to read Hacker News without opening a single new tab.
The Hacker News Tab Problem
Let us be specific about what happens during a normal HN session.
You open the front page. You see a headline about a new Rust framework. You open it. New tab. You read the first paragraph. It mentions a GitHub repo. You open it. New tab. You scan the README. Someone in the comments links to a related blog post. You open it. New tab. You read the blog post. It links to a paper on arXiv. You open it. New tab.
You have not finished the front page. You have not opened the comments. You already have 4 tabs and you are 2 levels deep in a rabbit hole. You go back to HN. You see another headline. You open it. New tab. The cycle repeats.
By the end of a 20-minute HN session, you have 15 tabs. You remember 3 headlines. You have read none of the comment threads in depth. And your browser is using 3GB of RAM to maintain pages you glanced at for 10 seconds each.
The HN trap: Hacker News is designed for discovery, not deep reading. Most links are auditions — you need to see if they are worth your time. But your browser treats every audition as a full commitment. You are casting a thousand actors and giving each one a dressing room.
The GoPeek HN Workflow
The fix is simple. Do not open links. Preview them with GoPeek.
Here is the exact workflow. It works on the front page, in comment threads, and in Ask HN posts.
Step 1: Scan the Front Page with Previews
You are on the HN front page. You see a headline that looks interesting. You hold Shift and hover the link (or long press it). A GoPeek preview opens instantly. You read the first few paragraphs. You decide in 10 seconds: worth reading or not.
If it is not worth reading, you close the preview. No tab was created. No context was lost. You are still on the front page. You move to the next headline.
If it is worth reading, you have two options. You can keep reading in the preview window — it is a full browser, you can scroll, click, and navigate. Or you can open it in a real tab if you know you want to spend 10 minutes on it. But 90% of HN links do not deserve a tab. They deserve a glance.
Front Page Scan: With vs. Without GoPeek
Without GoPeek: You open 8 articles in new tabs to "read later." You read 2 of them. The other 6 sit in your tab bar for 3 days. You close them in a guilt-fueled purge on Friday.
With GoPeek: You preview 8 articles. You read 2 in depth. The other 6 are closed in 10 seconds each. Zero tabs created. Zero guilt. Zero Friday purge.
Step 2: Read Comments Without Losing the Thread
HN comment threads are where the real value lives. But they are also where the real link density lives. A popular thread can have 200 comments, and 50 of them contain external links — to repos, papers, blog posts, and tools.
The normal workflow is painful. You see a comment linking to a GitHub repo. You open it in a new tab. You check the repo. You go back to the comments. You have lost your place. You scroll for 2 minutes to find the comment you were reading. You see another link. You open it. You go back. You have lost your place again.
With GoPeek, you hover the link in the comment. The preview opens. You check the repo. You close the preview. Your eyes are still on the same comment. You keep reading the thread. No scrolling. No searching. No lost context.
Comment Thread: With vs. Without GoPeek
Without GoPeek: You open 5 links from comments in new tabs. You check each one. You go back to the thread 5 times. You lose your place 5 times. You spend 8 minutes scrolling and 4 minutes actually reading. You give up on the thread.
With GoPeek: You preview 5 links from comments. You check each one. You close each preview. You never leave the thread. You read the entire discussion in 10 minutes. You know exactly which links were...