frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Gemini Pro 3 hallucinates the HN front page 10 years from now

https://dosaygo-studio.github.io/hn-front-page-2035/news
609•keepamovin•3h ago•274 comments

PeerTube is recognized as a digital public good by Digital Public Goods Alliance

https://www.digitalpublicgoods.net/r/peertube
111•fsflover•1h ago•16 comments

Mistral Releases Devstral 2 (72.2% SWE-Bench Verified) and Vibe CLI

https://mistral.ai/news/devstral-2-vibe-cli
252•pember•3h ago•91 comments

Handsdown one of the coolest 3D websites

https://bruno-simon.com/
163•razzmataks•2h ago•42 comments

Kaiju – General purpose 3D/2D game engine in Go and Vulkan with built in editor

https://github.com/KaijuEngine/kaiju
101•discomrobertul8•3h ago•41 comments

LLM from scratch, part 28 – training a base model from scratch on an RTX 3090

https://www.gilesthomas.com/2025/12/llm-from-scratch-28-training-a-base-model-from-scratch
376•gpjt•1w ago•86 comments

My favourite small hash table

https://www.corsix.org/content/my-favourite-small-hash-table
61•speckx•3h ago•12 comments

Launch HN: Mentat (YC F24) – Controlling LLMs with Runtime Intervention

https://playground.ctgt.ai
17•cgorlla•2h ago•9 comments

Clearspace (YC W23) Is Hiring a Founding Designer

https://www.ycombinator.com/companies/clearspace/jobs/yamWTLr-founding-designer-at-clearspace
1•roycebranning•1h ago

The Joy of Playing Grandia, on Sega Saturn

https://www.segasaturnshiro.com/2025/11/27/the-joy-of-playing-grandia-on-sega-saturn/
147•tosh•8h ago•85 comments

AWS Trainium3 Deep Dive – A Potential Challenger Approaching

https://newsletter.semianalysis.com/p/aws-trainium3-deep-dive-a-potential
40•Symmetry•4d ago•12 comments

Show HN: AlgoDrill – Interactive drills to stop forgetting LeetCode patterns

https://algodrill.io
120•henwfan•7h ago•78 comments

Transformers know more than they can tell: Learning the Collatz sequence

https://www.arxiv.org/pdf/2511.10811
81•Xcelerate•6d ago•30 comments

Donating the Model Context Protocol and Establishing the Agentic AI Foundation

https://www.anthropic.com/news/donating-the-model-context-protocol-and-establishing-of-the-agenti...
19•meetpateltech•1h ago•6 comments

Constructing the Word's First JPEG XL MD5 Hash Quine

https://stackchk.fail/blog/jxl_hashquine_writeup
74•luispa•1w ago•16 comments

30 Year Anniversary of WarCraft II: Tides of Darkness

https://www.jorsys.org/archive/december_2025.html#newsitem_2025-12-09T07:42:19Z
95•sjoblomj•9h ago•68 comments

Ask HN: Should "I asked $AI, and it said" replies be forbidden in HN guidelines?

344•embedding-shape•2h ago•189 comments

Icons in Menus Everywhere – Send Help

https://blog.jim-nielsen.com/2025/icons-in-menus/
767•ArmageddonIt•22h ago•306 comments

AI needs more power than the grid can deliver – supersonic tech can fix that

https://boomsupersonic.com/flyby/ai-needs-more-power-than-the-grid-can-deliver-supersonic-tech-ca...
27•simonebrunozzi•2h ago•33 comments

Show HN: Detail, a Bug Finder

https://detail.dev/
18•drob•1h ago•6 comments

Oliver Sacks Put Himself into His Case Studies. What Was the Cost?

https://www.newyorker.com/magazine/2025/12/15/oliver-sacks-put-himself-into-his-case-studies-what...
30•barry-cotter•4h ago•11 comments

A deep dive into QEMU: The Tiny Code Generator (TCG), part 1 (2021)

https://airbus-seclab.github.io/qemu_blog/tcg_p1.html
65•costco•1w ago•2 comments

Brent's Encapsulated C Programming Rules (2020)

https://retroscience.net/brents-c-programming-rules.html
55•p2detar•7h ago•27 comments

Epsilon: A WASM virtual machine written in Go

https://github.com/ziggy42/epsilon
126•ziggy42•1w ago•30 comments

ZX Spectrum Next on the Internet: Xberry Pi ESP01 and Pi Zero Upgrades

https://retrogamecoders.com/zx-spectrum-next-on-the-internet-xberry-pi-esp01-and-pi-zero-upgrades/
48•ibobev•7h ago•0 comments

After the Bubble

https://www.tbray.org/ongoing/When/202x/2025/12/07/Thin-Spots-In-the-AI-Bubble
40•savant2•6h ago•24 comments

Kroger acknowledges that its bet on robotics went too far

https://www.grocerydive.com/news/kroger-ocado-close-automated-fulfillment-centers-robotics-grocer...
247•JumpCrisscross•18h ago•275 comments

The universal weight subspace hypothesis

https://arxiv.org/abs/2512.05117
344•lukeplato•18h ago•121 comments

If you're going to vibe code, why not do it in C?

https://stephenramsay.net/posts/vibe-coding.html
73•sramsay•1h ago•81 comments

Animalcules and Their Motors

https://www.asimov.press/p/flagella
6•surprisetalk•6d ago•1 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•6mo ago

Comments

balloob•6mo ago
Founder Home Assistant here. Want to chime in that I always love to see write ups like these to see the great things what people achieve with Home Assistant.

Not everyone might know, but last year we started the Open Home Foundation[1] as a non-profit in Switzerland and I donated Home Assistant to it[2]. It's fully funded by users. There are no investors involved.

We are fully committed to building out a smart home that focuses on local control and privacy. Yes there are rough edges, but we're actively working on it in the open, with progress being released every month.

~Paulus Founder Home Assistant & President Open Home Foundation https://github.com/balloob

[1]: https://www.openhomefoundation.org [2]: https://www.openhomefoundation.org/blog/announcing-the-open-...

pabs3•6mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•6mo ago
Comments moved thither. Thanks!
pabs3•6mo ago
They are two different articles, I don't think that was correct.
tomhow•6mo ago
The problem is we can’t have two closely-related threads (i.e., threads where there is significant subject/discussion overlap) active at once.

When that happens it just gets confusing, because it’s hard for people know which thread to comment in, if the comment they want to make is somewhere in the overlap. And then whichever one they choose to comment in, people who only see the other thread won’t see that comment. Then sometimes, anticipating this, people will copy and paste their comment in both threads (which happened in this case). But then each one gets different replies.

So each thread ends up being incomplete and duplicated all at once, and it all becomes a big confusing mess.

The fact that these two articles were by the same author, had the same title, were published just a week apart and could easily have been published as one, longer article, says to me that merging the threads was the right thing to do.

The other option would have been to bury the second thread and consider another thread about that second article a few months later, but that didn’t seem like the best option, given how much the two articles are so related and continuous.

Edit: Just thought I'd add that a major factor in deciding to merge the threads was this opening to the second part by the author:

The first article in this series provided an overview of Home Assistant, its community, and its capabilities. It was deliberately short on descriptions of interesting things that can be done with Home Assistant, though — the reasons why one might actually want to use this program. In this closing article, we'll look at how Home Assistant was used to solve some real problems.

To me it makes all the difference that the first part is introductory/high-level whilst the second part goes deeper into usage-scenarios. We'd treat it differently if each part went deeply into different aspects on the project.

pabs3•6mo ago
Thanks for the response, guess that makes sense.
pabs3•6mo ago
BTW, on lobste.rs, they can merge threads into one, and all the URLs are shown at the top. That might be a useful change to adopt for HN too?