frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

GPT-5.6

https://openai.com/index/gpt-5-6/
1333•logickkk1•18h ago•926 comments

In Emacs, Everything Looks Like a Service

http://yummymelon.com/devnull/in-emacs-everything-looks-like-a-service.html
44•kickingvegas•3h ago•6 comments

Show HN: Getting GLM 5.2 running on my slow computer

https://github.com/JustVugg/colibri
724•vforno•1d ago•176 comments

EU Parliament greenlights Chat Control 1.0

https://www.patrick-breyer.de/en/eu-parliament-greenlights-chat-control-1-0-breyer-our-children-l...
1438•rapnie•1d ago•691 comments

Train sim created by just one person is being called the best ever made

https://kotaku.com/a-train-sim-created-by-just-one-person-is-being-called-the-best-ever-made-2000...
649•oumua_don17•5d ago•244 comments

Show HN: 18 Words

https://18words.com/
1015•pompomsheep•22h ago•329 comments

Postgres rewritten in Rust, now passing 100% of the Postgres regression tests

https://github.com/malisper/pgrust
703•SweetSoftPillow•1d ago•591 comments

Apple Silicon Exec Explains Mac Mini AI Demand and On-Device Future

https://www.macrumors.com/2026/07/06/apple-silicon-exec-explains-mac-mini-ai-demand/
90•tosh•3d ago•121 comments

Hy3

https://hy.tencent.com/research/hy3
494•andai•20h ago•102 comments

AI-generated videos to maximally drive a target brain region

https://nevo-project.epfl.ch/
92•smusamashah•3h ago•81 comments

Interview with Mitchell Hashimoto about Ghostty and Zig

https://alexalejandre.com/programming/interview-with-mitchell-hashimoto/
271•veqq•18h ago•128 comments

The glass backbone: Why the Army's logistics will break in the next war

https://mwi.westpoint.edu/the-glass-backbone-why-the-armys-logistics-will-break-in-the-next-war/
389•baud147258•22h ago•496 comments

EU Commission: addictive design Instagram and Facebook in breach of the DSA

https://ec.europa.eu/commission/presscorner/home/en
6•jeroenhd•36m ago•4 comments

No leap second will be introduced at the end of December 2026

https://datacenter.iers.org/data/latestVersion/bulletinC.txt
291•ChrisArchitect•21h ago•225 comments

A road to Lisp: Why Lisp

https://scotto.me/blog/2026-07-09-why-lisp/
247•silcoon•22h ago•189 comments

Parental device use and the adolescent-caregiver attachment bond

https://www.frontiersin.org/journals/psychology/articles/10.3389/fpsyg.2026.1766665/full
137•hbcondo714•11h ago•115 comments

Common prefix skipping, adaptive sort

http://smalldatum.blogspot.com/2026/01/common-prefix-skipping-adaptive-sort.html
29•theanonymousone•3d ago•3 comments

Ditching Vagrant: VMs with KVM and Virsh on Debian

https://benjamintoll.com/2026/06/29/on-ditching-vagrant/
15•fanf2•3d ago•6 comments

My Story of 3D Realms / Apogee Part I (2020)

https://joesiegler.blog/2020/11/my-story-of-apogee-3dr/
79•Michelangelo11•1w ago•6 comments

Building a real-time AI tutor for 5-year-olds

https://www.ello.com/blog/teaching-a-child-in-1000-ms
95•catalinvoss•14h ago•176 comments

A possible future for Damn Interesting

https://www.damninteresting.com/a-possible-future/
291•mzur•20h ago•39 comments

Launch HN: Context.dev (YC S26) – API to get structured data from any website

https://www.context.dev
98•TheYahiaBakour•20h ago•70 comments

Life with Hazard Ratios

https://dynomight.net/hazard-ratios/
47•surprisetalk•3d ago•18 comments

Muse Spark 1.1

https://ai.meta.com/blog/introducing-muse-spark-meta-model-api/
381•ot•21h ago•189 comments

Girls just wanna have fast MPMC queues with bounded waiting

https://nahla.dev/blog/waitfree_queue/
177•EvgeniyZh•3d ago•34 comments

Why American ambulance rides are so expensive

https://davidoks.blog/p/why-american-ambulance-rides-are
236•jyunwai•13h ago•320 comments

Triple Dragon Fractal (2020)

https://paulbourke.net/fractals/tripledragon/
55•nhatcher•3d ago•12 comments

TLS certificates for internal services done right

https://tuxnet.dev/posts/tls-for-internal-services/
163•mrl5•20h ago•115 comments

John Deere owners will get the right to repair equipment under FTC settlement

https://apnews.com/article/john-deere-right-to-repair-agriculture-equipment-cb7514ffedb95c130a976...
1330•djoldman•1d ago•279 comments

Patterncollider: Generate and explore quasiperiodic tiling patterns

https://github.com/aatishb/patterncollider
55•tobr•4d ago•3 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

balloob•1y 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•1y ago
Discussion for the other article in the series:

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

tomhow•1y ago
Comments moved thither. Thanks!
pabs3•1y ago
They are two different articles, I don't think that was correct.
tomhow•1y 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•1y ago
Thanks for the response, guess that makes sense.
pabs3•1y 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?