frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Taxing Growth

https://www.equitileconversations.com/2459100/episodes/18312924-taxing-growth
16•Incerto•19m ago•3 comments

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

https://dosaygo-studio.github.io/hn-front-page-2035/news
2979•keepamovin•23h ago•853 comments

Revisiting "Let's Build a Compiler"

https://eli.thegreenplace.net/2025/revisiting-lets-build-a-compiler/
157•cui•7h ago•22 comments

Map of All the Buildings in the World

https://gizmodo.com/literally-a-map-showing-all-the-buildings-in-the-world-2000694696
44•dr_dshiv•5d ago•10 comments

Rust in the kernel is no longer experimental

https://lwn.net/Articles/1049831/
713•rascul•11h ago•485 comments

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

https://www.digitalpublicgoods.net/r/peertube
585•fsflover•21h ago•116 comments

Putting email in its place with Emacs and Mu4e

https://eamonnsullivan.co.uk/posts-output/email-setup/2025-12-3-putting-email-in-its-place/
68•eamonnsullivan•6d ago•16 comments

Amazon EC2 M9g Instances

https://aws.amazon.com/ec2/instance-types/m9g/
87•AlexClickHouse•4d ago•27 comments

When a video codec wins an Emmy

https://blog.mozilla.org/en/mozilla/av1-video-codec-wins-emmy/
196•todsacerdoti•4d ago•39 comments

Bruno Simon – 3D Portfolio

https://bruno-simon.com/
655•razzmataks•22h ago•151 comments

Mistral releases Devstral2 and Mistral Vibe CLI

https://mistral.ai/news/devstral-2-vibe-cli
655•pember•23h ago•310 comments

Cloth Simulation

https://cloth.mikail-khan.com/
72•adamch•1w ago•12 comments

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

https://stephenramsay.net/posts/vibe-coding.html
545•sramsay•21h ago•503 comments

Django: what’s new in 6.0

https://adamj.eu/tech/2025/12/03/django-whats-new-6.0/
319•rbanffy•17h ago•98 comments

Running Linux on a RiscPC – why is it so hard?

https://thejpster.org.uk/blog/blog-2025-12-02/
24•zdw•1w ago•7 comments

Pebble Index 01 – External memory for your brain

https://repebble.com/blog/meet-pebble-index-01-external-memory-for-your-brain
523•freshrap6•23h ago•512 comments

Apple Faces Scrutiny as Sanctioned Entities Slip Through App Store Controls

https://www.washingtonpost.com/technology/2025/12/10/us-sanctions-apple-google/
11•7777777phil•43m ago•2 comments

10 Years of Let's Encrypt

https://letsencrypt.org/2025/12/09/10-years
714•SGran•19h ago•296 comments

Are the Three Musketeers allergic to muskets? (2014)

https://www.ox.ac.uk/news/arts-blog/are-three-musketeers-allergic-muskets
46•rolph•8h ago•32 comments

Tech for Small vs. Big Firms

https://lexifina.com/blog/technology-for-firms-big-and-small
4•alansaber•4d ago•3 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...
258•meetpateltech•21h ago•113 comments

Passing the Torch: James Gross on the Next Chapter of Micromobility Industries

https://micromobility.io/news/how-charging-is-reshaping-the-business-of-shared-scooters-and-e-bikes
15•prabinjoel•6d ago•0 comments

Italy's longest-serving barista reflects on six decades behind the counter

https://www.reuters.com/lifestyle/culture-current/anna-possi-six-decades-behind-counter-italys-ba...
228•NaOH•5d ago•130 comments

So you want to speak at software conferences?

https://dylanbeattie.net/2025/12/08/so-you-want-to-speak-at-software-conferences.html
200•speckx•19h ago•101 comments

Writing our own Cheat Engine in Rust

https://lonami.dev/blog/woce-1/
94•hu3•5d ago•14 comments

A supersonic engine core makes the perfect power turbine

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

Cloudflare error page generator

https://github.com/donlon/cloudflare-error-page
71•sawirricardo•12h ago•12 comments

The stack circuitry of the Intel 8087 floating point chip, reverse-engineered

https://www.righto.com/2025/12/8087-stack-circuitry.html
125•elpocko•20h ago•54 comments

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

https://github.com/KaijuEngine/kaiju
201•discomrobertul8•23h ago•91 comments

Linux CVEs, more than you ever wanted to know

http://www.kroah.com/log/blog/2025/12/08/linux-cves-more-than-you-ever-wanted-to-know/
76•voxadam•15h ago•36 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?