frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

The Codex App

https://openai.com/index/introducing-the-codex-app/
284•meetpateltech•2h ago•175 comments

Ask HN: Who is hiring? (February 2026)

192•whoishiring•4h ago•239 comments

Hacking Moltbook

https://www.wiz.io/blog/exposed-moltbook-database-reveals-millions-of-api-keys
121•galnagli•4h ago•83 comments

Todd C. Miller – Sudo maintainer for over 30 years

https://www.millert.dev/
179•wodniok•3h ago•101 comments

Advancing AI Benchmarking with Game Arena

https://blog.google/innovation-and-ai/models-and-research/google-deepmind/kaggle-game-arena-updates/
59•salkahfi•2h ago•30 comments

Nano-vLLM: How a vLLM-style inference engine works

https://neutree.ai/blog/nano-vllm-part-1
185•yz-yu•7h ago•23 comments

4x faster network file sync with rclone (vs rsync) (2025)

https://www.jeffgeerling.com/blog/2025/4x-faster-network-file-sync-rclone-vs-rsync/
191•indigodaddy•3d ago•92 comments

The largest number representable in 64 bits

https://tromp.github.io/blog/2026/01/28/largest-number-revised
23•tromp•2h ago•20 comments

Ask HN: Who wants to be hired? (February 2026)

67•whoishiring•4h ago•142 comments

Geologists may have solved mystery of Green River's 'uphill' route

https://phys.org/news/2026-01-geologists-mystery-green-river-uphill.html
114•defrost•7h ago•28 comments

EPA Advances Farmers' Right to Repair

https://www.epa.gov/newsreleases/epa-advances-farmers-right-repair-their-own-equipment-saving-rep...
106•bilsbie•2h ago•38 comments

Why software stocks are getting pummelled

https://www.economist.com/business/2026/02/01/why-software-stocks-are-getting-pummelled
55•petethomas•15h ago•70 comments

Being sane in insane places (1973) [pdf]

https://www.weber.edu/wsuimages/psychology/FacultySites/Horvat/OnBeingSaneInInsanePlaces.PDF
45•dbgrman•3h ago•23 comments

Show HN: PolliticalScience – Anonymous daily polls with 24-hour windows

https://polliticalscience.vote/
14•ps2026•2h ago•13 comments

IsoCoaster – Theme Park Builder

https://iso-coaster.com/
68•duck•3d ago•16 comments

Pretty soon, heat pumps will be able to store and distribute heat as needed

https://www.sintef.no/en/latest-news/2026/pretty-soon-heat-pumps-will-be-able-to-store-and-distri...
69•PaulHoule•1d ago•57 comments

Show HN: Adboost – A browser extension that adds ads to every webpage

https://github.com/surprisetalk/AdBoost
60•surprisetalk•7h ago•82 comments

My fast zero-allocation webserver using OxCaml

https://anil.recoil.org/notes/oxcaml-httpz
121•noelwelsh•10h ago•42 comments

Tomo: A statically typed, imperative language that cross-compiles to C [video]

https://www.youtube.com/watch?v=-vGE0I8RPcc
16•evakhoury•4d ago•9 comments

Waymo seeking about $16B near $110B valuation

https://www.bloomberg.com/news/articles/2026-01-31/waymo-seeking-about-16-billion-near-110-billio...
140•JumpCrisscross•5h ago•186 comments

UK government launches fuel forecourt price API

https://www.gov.uk/guidance/access-the-latest-fuel-prices-and-forecourt-data-via-api-or-email
49•Technolithic•7h ago•71 comments

Claude Code is suddenly everywhere inside Microsoft

https://www.theverge.com/tech/865689/microsoft-claude-code-anthropic-partnership-notepad
289•Anon84•8h ago•415 comments

Parking lots as economic drains

https://progressandpoverty.substack.com/p/stop-incentivizing-surface-parking
91•surprisetalk•2h ago•69 comments

LinkedIn Is Down

https://ctrlv.link/8aQX
7•palakd•21m ago•4 comments

Hypergrowth isn’t always easy

https://tailscale.com/blog/hypergrowth-isnt-always-easy
107•usrme•2d ago•42 comments

Valanza – my Unix way for weight tracking and anlysis

https://github.com/paolomarrone/valanza
20•lallero317•4d ago•6 comments

Apple's MacBook Pro DFU port documentation is wrong

https://lapcatsoftware.com/articles/2026/2/1.html
191•zdw•17h ago•71 comments

Kernighan on Programming

116•chrisjj•4h ago•31 comments

Library of Juggling

https://libraryofjuggling.com/
101•tontony•12h ago•24 comments

Solvingn the Santa Claus concurrency puzzle with a model checker

https://wyounas.github.io/puzzles/concurrency/2026/01/10/how-to-help-santa-claus-concurrently/
14•simplegeek•3d ago•2 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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