Listen to Hacker News as a Daily AI Podcast

Hacker News is one of the better signals for tech and startup news, but it moves faster than most people can read it. The frontpage shifts every hour, popular stories pick up hundreds of comments before lunch, and Show HN posts often slip off the front page within a few hours of going live. If you check once or twice a day, you miss most of what happens.

A different approach: every morning, listen to a 15-minute AI-generated digest of HN while you commute or get ready, then open the handful of stories worth reading properly. This article covers how an HN podcast fits next to existing services and DIY projects, and how to set one up with Lisnify.

Why keeping up with Hacker News is hard

The Top 30 reshuffles multiple times a day, so by the time you look in the evening, the morning's lineup is mostly gone. Comment threads regularly run into the hundreds, with the more interesting replies buried under several levels of expansion.

Show HN and Ask HN make it worse in their own way. A Show HN post often gets a few hours on the front page and then disappears. If you check HN once a day at 6 PM, you have probably missed most of the Show HN traffic that landed at 9 AM. Useful Ask HN threads often get traction late and drop before they ever surface in your feed.

Reading also tends to happen at the wrong time. The window when you want to read HN (mid-morning, late evening) is rarely the window when you have an hour free. The window when you do have time (commute, gym, dishes) is the window when reading dense English prose on a phone is least pleasant. The "I'll read it later" pile grows accordingly.

This is not a willpower problem. The premise that you should read everything on HN is what does not scale. A more realistic premise: skim by ear, pick a few, read those properly.

Existing ways to keep up with HN

Several approaches already exist, and they are not strictly competing. Each suits a different reading pattern.

The HN official Top RSS feed at https://news.ycombinator.com/rss is the canonical source. If you already use a feed reader, this gets you the raw frontpage signal. The reading load is unchanged, though. You still have to open and read each link.

hnrss.org is a community-run, third-party service that exposes Show HN, Ask HN, Best, Newest, and filtered variants as RSS. It supports query parameters for points and comment thresholds, so you can build feeds like "newest posts above 100 points." Because it is community-run rather than official, treat it as useful but not load-bearing.

Curated newsletters cover a different lane. Hacker Newsletter ships a weekly editor-picked roundup. Refind sends a daily digest pulled from HN and other sources. Both lean on editorial judgment, which is hard to beat for one careful weekly pass but too coarse if you want daily coverage filtered to your own taste.

Several community-run HN podcast services have appeared over the years, generating audio summaries of the frontpage on a fixed schedule. These are public podcasts: everyone subscribes to the same feed, so the operator's editorial choices are everyone's. If those choices match yours, this is a low-effort win.

DIY and open-source HN podcast projects also exist. People build them as side projects and post them on Show HN with the code on GitHub. Full control over filtering, voice, length, and schedule, at the cost of running the pipeline yourself.

A personal AI podcast, the angle this article takes, sits next to those options rather than replacing any. It is for people who want podcast-shaped consumption with their own filters, without running their own pipeline.

What a personal HN podcast adds

Listening during hands-free time is the obvious benefit. A 10-to-15-minute summary of the morning's HN frontpage fits into a commute or breakfast. None of that time was going to be reading time anyway.

Filtering to your interests, not the platform's, is the less obvious one. Public HN podcast services pick a slice of HN and stick with it. A personal feed lets you build the slice yourself: Top plus Show HN only, or newest posts above 100 points, or Ask HN once a week. Categories you do not care about simply do not show up.

Audio also works well as a triage layer. Listening to summaries of 10 stories and picking the 2 to 3 worth opening is less work than scanning 30 headlines and guessing which links will repay the click. By the time you sit down at a screen, you already know what you want to read.

Podcasts are easy to skip without guilt. Missing a day does not feel like falling behind the way an unread newsletter does, which matters for keeping the habit through busy weeks.

The limits are real. Code snippets, benchmark tables, and diagrams lose information in audio. HN comment threads, often the most interesting part of a story, are not part of the source material that gets summarized (more on this below).

Picking your slice

HN feels different depending on which slice you listen to. Decide what one episode contains before you set anything up.

• Top, daily. Broad tech news, 10 to 15 minutes. Use https://news.ycombinator.com/rss (HN official) or https://hnrss.org/frontpage (community-run). Lisnify caps episodes at 10 stories, so the full Top 30 will not fit in one episode.
• Show HN, daily or weekly. Indie products and side projects from people who launched something. Source: https://hnrss.org/show.
• Ask HN, weekly. Career questions, technical decisions, hiring debates. Source: https://hnrss.org/ask.
• Newest with a points threshold. Catches stories early but skips obvious noise. Example: https://hnrss.org/newest?points=100.
• Best, weekly. Stories that held their score over a few days. Higher signal, less recency. Source: https://hnrss.org/best.
• Comment-count threshold. Stories where the discussion is going somewhere. Configure via hnrss.org query parameters.

Running two or three feeds in parallel works well: "Top 10 daily" plus "Show HN weekly" gives you both the broad view and the indie launch radar without diluting either episode.

Set up an HN podcast with Lisnify

This section walks through the HN-specific decisions. The general RSS-to-podcast setup is in the pillar guide, which is the canonical reference for the steps that apply to any feed.

Pick the HN feed or feeds you want

Choose from the slices above. Start with one Top feed. After a week or two, add Show HN as a separate Show if it earns its place. Treating each slice as its own Show keeps the editorial intent clean per episode.

Create a Show in Lisnify and register the HN feed

In the Sources tab, add the RSS URL you picked. For HN Top, that is https://news.ycombinator.com/rss. For Show HN, https://hnrss.org/show. The pillar guide's "Register a Show and your RSS sources" step covers the mechanics.

Pick a host style that works for HN

HN topics swing wildly between distributed systems, hiring threads, and hardware teardowns, so pick a style that survives the variance. Calm single-host narration handles the mixed bag in a news format. Two-host conversational suits longer episodes built around the Best feed or comment-heavy threads, where you want stories unpacked a bit.

Schedule for your morning routine

The HN frontpage moves, so the generation time fixes the snapshot your episode covers. For commute listening, schedule generation between 5:30 and 6:30 AM in your local time zone. The default schedule timezone is UTC, so set your local zone explicitly. An episode generated at 6 AM reflects the 6 AM frontpage, not the 9 AM one.

Tune story count and script guidelines after the first week

The first week or two surfaces obvious adjustments:

• "Show HN entries should be shorter, just the pitch" - tighten that in the script settings.
• "Flag stories that have a heavy comment thread" - add an instruction (auto-fetching comments is not supported, so this is a flagging instruction, not a summarization one).
• "10 stories is too many, 5 is plenty" - reduce the per-episode count.

Adjust per-episode story count in the Sources tab, and tune opening, per-story, and closing instructions in the Script Settings tab.

Subscribe in your podcast app and triage by ear

Lisnify gives you a private feed URL. Add it to whichever podcast app you already use for everything else.

Once subscribed, the routine is: listen on the way to work, note the two or three stories worth a deeper read, open those at your desk.

Use cases that work well

Pre-standup tech briefing

Engineering managers, staff engineers, CTOs, and product managers all benefit from walking into the day knowing what HN was talking about. A 10-minute Top digest over coffee is usually enough to handle "did you see the thing on HN this morning?" in standup without a scramble.

Commute as triage time

For people who do want to read HN seriously, audio works as a pre-filter. Listening to summaries of 10 stories on a 30-minute commute and deciding "I will read three of these tonight" is more effective than opening HN cold at 9 PM and trying to remember what was on the frontpage that morning.

Show HN watcher for indie hackers and investors

A weekly Show HN episode is a cheap way for indie hackers, founders, angel investors, and product researchers to track what people are launching. You will not catch every project, but the trend signal (which categories are getting busy, which stacks people are pairing) comes through clearly in audio. The handful of products worth a deeper look get opened later.

Caveats: what audio loses, and when to read directly

Code, benchmarks, and diagrams are the obvious lossy cases. A story whose value is "here are the numbers" or "look at this architecture diagram" should be a pointer in the podcast, not a substitute for the original. Use the audio to learn that the story exists; go to the source for the actual claim.

HN comment threads are not in the source material. The HN official RSS and hnrss.org both return story titles and link to the underlying article, and Lisnify summarizes the linked article. Comment threads, where HN's most useful content often lives, are not auto-fetched. Build the habit: when a story sounds interesting, open both the article and the HN thread.

Show HN and Ask HN nuance gets lost in summarization. The way someone introduces their own project, or the specific phrasing of a question, often matters. If you are about to download a Show HN project and try it, read the original post. Same for Ask HN threads where you might want to reply.

Frontpage staleness is real. An episode generated at 6 AM is a snapshot of the 6 AM frontpage. By 6 PM, that frontpage is mostly different. Treat the podcast as "this morning's HN, summarized" rather than "the current state of HN." If you are about to cite something in a meeting, open the live page first.

Where to go from here

The "read everything on HN" premise does not scale. Switching to "skim by ear in the morning, read the two or three that matter at your desk" does. Start with one Top feed, see whether it survives a week or two, then add Show HN or Ask HN as a separate Show if it earns the slot.

If you are still deciding which AI podcast tool fits your job, the NotebookLM alternatives: how Wondercraft, Jellypod, and Lisnify compare write-up walks through NotebookLM, Wondercraft, Jellypod, and Lisnify by use case.

Frequently asked questions

Are HN comment threads included in the podcast?

No. The HN official RSS and the community-run hnrss.org both return story titles and links to the underlying article. Lisnify summarizes the linked article, not the HN comment thread. For stories where the comments are the point, open the HN page directly after listening.

Are Show HN and Ask HN summarized the same way as regular stories?

Mechanically, yes. In practice, treating them differently works better. Show HN is the author pitching their own project, and Ask HN is a community question, so you usually want different framing and depth for each. The cleanest setup is to put Show HN, Ask HN, and Top in separate Shows so you can tune script instructions per format in Script Settings.

The HN frontpage moves by the hour. Does the timing of episode generation matter?

Yes. The episode reflects the frontpage at generation time. An episode generated at 6 AM is about the 6 AM frontpage. If you listen at 6 PM, the live HN site looks different. The fix is framing: treat each episode as "this morning's snapshot" and check the live site before quoting anything in a serious context.

Can I combine HN with other tech sources in the same Show?

Yes. Adding dev.to latest, Lobsters, or specific engineering blogs to the same Show as HN Top produces a unified tech digest. Whether to mix or keep them separate is a taste call. Mixing reduces the number of episodes you maintain; keeping them separate keeps the editorial intent of each Show clearer. The pillar guide has more on running multiple sources.

How is this different from existing HN podcast services?

Several community-run HN podcast services generate audio from the frontpage on a fixed schedule for a public audience. They work well if their editorial choices match yours: same slice, same length, same tone. A personal feed differs in that you choose the slice yourself ("Top plus Show HN only" or "newest above 100 points") and the format is private to you. Both approaches are fine for different cases. If you want zero setup and the public version fits, use that. If the slice or filtering matters, build your own.