frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Houthis 'take control' of key island in global shipping route

https://www.bbc.com/news/live/cmd683p01eljt
137•consumer451•1h ago•97 comments

The Waymo effect: how AI is quietly making research less collaborative

https://www.researchagenda.news/articles/the-waymo-effect.html
249•JohnHammersley•3h ago•195 comments

Logo Programming Language

https://el.media.mit.edu/logo-foundation/what_is_logo/logo_programming.html
55•azhenley•2d ago•15 comments

Ask HN: Can we please limit the AI news flood?

416•cromka•1h ago•216 comments

So you want to use OpenRouter?

https://mmoustafa.com/blog/so-you-want-to-use-openrouter/
399•player85•2d ago•103 comments

Cherenkov Radiation - traveling faster than light

http://www.iaea.org/newscenter/news/what-is-cherenkov-radiation
156•andsoitis•6h ago•79 comments

Re-Engineering YouTube for the Living Room: Bringing "Chrobalt" to RDK

https://www.collabora.com/news-and-blog/news-and-events/re-engineering-youtube-for-the-living-roo...
12•losgehts•1h ago•3 comments

Shopify is moving from React Native back to Swift and Kotlin

https://shopify.engineering/back-to-native
1175•fnthawar2•1d ago•866 comments

Don't let anyone take away your big box of cables

https://blog.jim-nielsen.com/2026/hands-off-my-cables/
679•Brajeshwar•23h ago•411 comments

RTK reports token savings, but our cost benchmarks disagree

https://quesma.com/blog/does-rtk-make-ai-coding-cheaper/
78•michalwarda•3h ago•48 comments

If coding is solved, what now?: Measuring the sloppiness of code

https://earendil.com/posts/measuring-code-sloppiness/
83•doppp•1h ago•100 comments

iPod Classic 6G in QEMU

https://www.reddit.com/r/emulation/s/VL4Au2HGxq
96•dmonterocrespo•3d ago•18 comments

RISC-V Emulator and Linux System from Scratch

https://github.com/WerWolv/riscv-emulator
29•Bluestein•3d ago•2 comments

CSS Curiosities of the Past

https://vale.rocks/posts/css-relics
53•robin_reala•7h ago•31 comments

OpenAI Agents API

https://developers.openai.com/api/docs/guides/agents-api/overview
309•aquir•19h ago•165 comments

Working with Git Worktrees in Magit

https://emacsredux.com/blog/2026/09/02/working-with-git-worktrees-in-magit/
88•srijan4•3d ago•35 comments

Experiment – Projectional Viewer

https://programmingsimplicity.substack.com/p/experiment-projectional-viewer
11•surprisetalk•3d ago•1 comments

An interactive tour of the spanning tree protocol

https://vincent.bernat.ch/en/blog/2026-spanning-tree
54•zdw•3d ago•4 comments

Claude is no longer available for minors

https://support.claude.com/en/articles/15171100-age-assurance-on-claude
257•Muhammad523•4h ago•338 comments

I've operated petabyte-scale ClickHouse clusters for 5 years

https://www.tinybird.co/blog/what-i-learned-operating-clickhouse
4•adastral•3d ago•0 comments

Technique for Manipulating Satellite Photos Now Reveals Ancient Images (2025)

https://spinoff.nasa.gov/Manipulating_Satellite_Photos_Now_Reveals_Ancient_Images
360•gumby•23h ago•62 comments

Mexican student creates an acoustic fire extinguisher to put out fire in seconds

https://www.upsocl.com/en/16-year-old-mexican-student-creates-an-acoustic-fire-extinguisher-that-...
317•rguiscard•14h ago•105 comments

The Deathray: A simple way for an untrusted site to freeze a Mac

https://auberon.xyz/blog/posts/deathray/
248•auberonedu•19h ago•162 comments

New York thoracic surgeon: "For many patients 9/11 is not over"

https://www.statnews.com/2026/09/11/sept-11-25th-anniversary-ground-zero-exposure-cancer-moment-o...
8•EA-3167•51m ago•1 comments

Why Bullshit Jobs Are (Finally) Dying [video]

https://www.youtube.com/watch?v=QecDVkcGPxY
14•mpweiher•1h ago•6 comments

HuggingFace: Security.txt

https://huggingface.co/security.txt
4•yarapavan•28m ago•0 comments

More questions about whether researchers can trust OpenAI with unpublished math

https://mathstodon.xyz/@andreasthom/117240535270608201
842•pred_•1d ago•786 comments

Music Theory for the 21st-Century Classroom

https://musictheory.pugetsound.edu/mt21c/MusicTheory.html
261•aanet•21h ago•125 comments

Nine coding harnesses vs. your laptop

https://nasutton.notion.site/Nine-coding-harnesses-vs-your-laptop-3d139990182b80d59fa3cf500f0450b...
146•nasutton12•16h ago•51 comments

NTSB issues investigative update on B-767 runway excursion accident in Miami

https://www.ntsb.gov:443/news/press-releases/Pages/NR20260909.aspx
134•mckn1ght•17h ago•235 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?