Highlight a deep comment subtree on news.ycombinator.com
Select a top comment and its most detailed technical replies.
AI Chrome extension for Hacker News: synthesize technical debates with zero bloat.
Highlight deep technical comment threads, 'Show HN' architecture critiques, and postmortem debates on news.ycombinator.com and synthesize practitioner insights.
Best fit
Best for engineers and founders reading news.ycombinator.com who want fast comment synthesis and reference lookups without ruining HN's minimalist speed.
On-screen walkthrough
How this looks on a real webpage.
Instead of switching tabs and rebuilding context, highlight the exact passage that slowed you down and press your shortcut (default: Ctrl+Shift+X or Cmd+Shift+X on macOS, fully customizable in settings).
1. Highlighted on page (news.ycombinator.com — Comment Subtree on SQLite in Production)
commenter_1: Running SQLite on NVMe with WAL mode and synchronous=NORMAL easily handles 40k writes/sec in a single Go process using two separate connections (1 writer with SetMaxOpenConns(1) + BEGIN IMMEDIATE, N readers). The real operational trap isn't throughput; it's zero-downtime deploys on container orchestrators where two pods briefly mount the volume, plus replication lag during bulk migrations.
Ctrl+Shift+X“Extract the exact production configuration rules and the deployment gotcha from this comment.”
2. Vezz me on-screen answer overlay
1. **SQLite Production Checklist**:
- Set `PRAGMA journal_mode=WAL;` and `PRAGMA synchronous=NORMAL;` on local NVMe.
- Split DB pools into **two connections**: 1 Writer (`SetMaxOpenConns(1)` + `BEGIN IMMEDIATE` to prevent `SQLITE_BUSY` deadlocks) and `N` concurrent Readers.
2. **Operational Gotcha**: Standard rolling container deploys break single-node volume mounts (two pods cannot safely write to the same file), and async replication tools lag during bulk schema migrations.
3. Suggested follow-up questions in thread
- “Why does `BEGIN IMMEDIATE` prevent `SQLITE_BUSY` deadlocks compared to a default `BEGIN`?”
- “Summarize the counterarguments in the child replies below this comment.”
Step-by-step workflow
How to run this workflow in place.
Press your shortcut for practitioner consensus and war stories
Ask Vezz me to separate concrete production benchmarks and configs from bike-shedding.
Decode obscure CS papers and kernel concepts mentioned in passing
When an HN commenter references 'Lampson's 1983 hints paper' or 'mutex convoy effects', highlight the phrase for an instant explanation.
Key details
Why this approach works better than switching tabs.
Comparison Matrix
Reading Hacker News Threads
Comparing on-demand subtree synthesis with heavy sidebar extensions.
| Method | Strengths | Tradeoffs |
|---|---|---|
| Vezz me on Selected Comment Subtree | Extracting production configs and war stories while keeping HN 100% bloat-free | You highlight the specific subtree you care about |
| Heavy AI sidebar extensions | Persistent chat dock | Injects scripts and floating buttons into HN's ultra-light HTML |
| Reading all 500 comments manually | Complete thread immersion | Takes 30+ minutes when you only needed the top technical consensus |
Frequently asked questions
Common questions about platform guide — hacker news.
Does Vezz me inject anything into news.ycombinator.com?
Nothing at all unless you press your shortcut. When you close the popup with Esc, the page DOM is completely untouched.
Can I compare an article's claims against the top HN comments?
Yes! Read the article, then switch to the HN discussion, highlight the top 5 comments, and ask Vezz me where practitioners disagree with the author.
Does it work on Lobste.rs, Tildes, and hckrnews.com too?
Yes—it works on any site where you can select text in Chrome or Firefox.
Related workflows & guides
Explore connected pages.
Ready to try this workflow on your own reading?
Install Vezz me free, highlight text on any webpage, and press your customizable shortcut (default: Ctrl+Shift+X or Cmd+Shift+X on Mac) to get an answer right beside the source.
