This is the output that we got (based on the HN-Companion project) [2]
LLama 4 Scout - https://gist.github.com/annjose/9303af60a38acd5454732e915e33...
Llama 4 Maverick - https://gist.github.com/annjose/4d8425ea3410adab2de4fe9a5785...
Claude 3.7 - https://gist.github.com/annjose/5f838f5c8d105fbbd815c5359f20...
The summary from Scout and Maverick both look good (comparable to Claude), and with this structure, Scout seems to follow the prompt slightly better.
--
[0] - https://gist.github.com/annjose/5145ad3b7e2e400162f4fe784a14...
[1] - https://gist.github.com/annjose/d30386aa5ce81c628a88bd86111a...
You can run it as: node summarize-comments.js <post_id> Example: node summarize-comments.js 43597782
And the summary will be put in the "output" folder.
You need to set the environment variable (in this case OPENROUTER_API_KEY because LLama4 is currently available at OpenRouter).
Been trying the 109b version on Groq and it seems less capable than Gemma 3 27b
Have you thought about automatizing hn-summaries for say what the 5 top posts are at 8 AM EST?
That would be a simple product to test the market. If successful, it could be easily extended to a weekly newsletter summary.
Since HN Homepage stories change throughtout the day, I thought it is better to create the Newsletter based on https://news.ycombinator.com/front
So, you are getting the news a day late, but it will capture the top stories for that day. The newsletter will have high-level summary for each post and a link to get the details for that story from a static site.
What about putting the text version that's used to make the audio somewhere on the page? (or better, on a subpage where there's no audio playback)
But thinking about it a little more, what would the use case for a text version actually look like? I feel like if you're already on HN, navigating somewhere else to get a TLDR would be too much friction. Or are we talking RSS/blog type delivery?
And with Scout I got complete junk output for some reason:
Junk output here: https://gist.github.com/simonw/d01cc991d478939e87487d362a8f8...I'm running it through openrouter, so maybe I got proxied to a broken instance?
I managed to run it through Scout on Groq directly (with the llm-groq plugin) but that had a 2048 limit on output size for some reason:
Result here: https://gist.github.com/simonw/a205c5fc131a1d4e9cd6c432a07fe...I'm a little unimpressed by its instruction following here, the summaries I get from other models are a lot closer to my system prompt. Here's the same thing against Gemini 2.5 Pro for example (massively better): https://gist.github.com/simonw/f21ecc7fb2aa13ff682d4ffa11ddc...