frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Beam: Reflection's 501B open-weight model

https://reflection.ai/blog/introducing-beam
213•Philpax•3h ago•58 comments

Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates

https://www.vals.ai/blogs/room-temperature-magnetic-semiconductors
119•outlier99•1h ago•96 comments

Dust: Pretraining Transformers Without Backpropagation

https://qlabs.sh/research/dust
35•E-Reverance•1h ago•2 comments

Find the flattest route between any two points in SF

https://flattensf.com/
19•ishan0102•39m ago•4 comments

Web Search API

https://developers.cloudflare.com/changelog/post/2026-10-02-introducing-web-search-api/
448•tosh•11h ago•208 comments

Competitive Programmer's Handbook (2018) [pdf]

https://cses.fi/book/book.pdf
70•vinhnx•2d ago•16 comments

Using Blu-ray M-Disk as Backup of Last Resort

https://smyck.net/2026/10/03/holocron-the-backup-of-last-resort/
16•hukl•1d ago•10 comments

Making a GTK application in Haskell, part 1

https://floreal.tech/blog/2026/making-a-gtk-app-in-haskell-part-1/
118•Vosporos•7h ago•26 comments

A third way of using Linux

https://hisvirusness.com/third-is-the-way
12•speckx•2h ago•13 comments

How to save a life without knowing CPR

https://bookofjoe2.blogspot.com/2026/10/beyondthemedspeak-how-to-save-life.html
52•bookofjoe•3d ago•36 comments

Anthropic reported diary entry to police, woman faces felony charge

https://www.techspot.com/news/114091-florida-woman-used-claude-diary-anthropic-reported-shoot.html
418•emptybits•16h ago•346 comments

Incident with Actions

https://www.githubstatus.com/incidents/3q1yb5m7ltvb
79•hising•2h ago•53 comments

The Future of Mathematics

https://terrytao.wordpress.com/2026/10/05/the-future-of-mathematics/
59•smilelamp•2h ago•26 comments

Linux containers in 500 lines of code (2016)

https://blog.lizzie.io/linux-containers-in-500-loc.html
81•mkornaukhov•8h ago•16 comments

Show HN: Nightwatch – a Mac menu-bar app that tells you when tonight is clear

https://github.com/rsutcliffe/nightwatch
62•delphidolphin•1d ago•9 comments

Apple and a hacker's future

https://stratechery.com/2026/apple-and-a-hackers-future/
175•maguay•12h ago•170 comments

Qualcomm licenses patents on Huawei’s LogicFolding chip tech

https://www.bloomberg.com/news/articles/2026-10-05/qualcomm-licenses-patents-on-huawei-s-logicfol...
166•0xedb•14h ago•104 comments

The lamps in my house

https://arslan.io/2026/10/05/the-lamps-in-my-house/
86•farslan•8h ago•51 comments

The first fully implanted cochlear implant reaches patients

https://spectrum.ieee.org/fully-implantable-cochlear-implant
49•rbanffy•4d ago•50 comments

Norway Eyes Partial Ban of Smart Glasses

https://www.barrons.com/news/norway-eyes-partial-ban-of-smart-glasses-e65dc239
102•pseudolus•4h ago•60 comments

The era of software quality, or the era of ostriches?

https://blogs.gnome.org/mcatanzaro/2026/10/02/the-era-of-software-quality-or-the-era-of-ostriches/
13•vinhnx•2d ago•56 comments

2026 Nobel Prize in Physiology or Medicine: Deisseroth, Hegemann, Nagel

https://www.nobelprize.org/prizes/medicine/2026/summary/
106•lode•12h ago•45 comments

Differences Between `Foldl` and `Foldr`

https://blog.haskell.org/foldl-and-foldr/
123•signa11•4d ago•27 comments

Type Safe Generic Data Structures in C (2025)

https://danielchasehooper.com/posts/typechecked-generic-c-data-structures/
125•AlexeyBrin•2d ago•96 comments

The technology to eradicate mosquito-borne disease exists

https://worksinprogress.co/issue/mosquitoes-are-a-choice/
223•benbreen•1d ago•176 comments

After bankruptcy, he was banned from sports betting sites. Then he found Kalshi

https://www.npr.org/2026/10/02/nx-s1-5981420/kalshi-betting-prediction-markets-gambling-addiction
48•momentmaker•2h ago•38 comments

Our approach to EU text provenance rules

https://openai.com/index/eu-text-provenance/
59•tosh•6h ago•45 comments

Greenvolt begins building 600 MW/2.4 GWh BESS in Poland

https://www.ess-news.com/2026/09/25/greenvolt-begins-building-600-mw-2-4-gwh-bess-in-poland/
50•msalsas•3h ago•29 comments

Martian chaos terrain

https://en.wikipedia.org/wiki/Martian_chaos_terrain
92•tiagod•3d ago•25 comments

Pixel 11 doesn't yet meet the GrapheneOS security standards and may be skipped

https://discuss.grapheneos.org/d/41564-pixel-11-doesnt-yet-meet-the-grapheneos-security-standards...
384•finnlab•9h ago•227 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?