frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Cowork: Claude Code for the rest of your work

https://claude.com/blog/cowork-research-preview
759•adocomplete•9h ago•370 comments

TimeCapsuleLLM: LLM trained only on data from 1800-1875

https://github.com/haykgrigo3/TimeCapsuleLLM
530•admp•13h ago•219 comments

The Cray-1 Computer System (1977) [pdf]

https://s3data.computerhistory.org/brochures/cray.cray1.1977.102638650.pdf
58•LordGrey•3d ago•32 comments

Postal Arbitrage

https://walzr.com/postal-arbitrage
327•The28thDuck•11h ago•171 comments

The chess bot on Delta Air Lines will destroy you (2024) [video]

https://www.youtube.com/watch?v=c0mLhHDcY3I
191•cjaackie•9h ago•145 comments

Some ecologists fear their field is losing touch with nature

https://www.nature.com/articles/d41586-025-04150-w
79•Growtika•4d ago•35 comments

Floppy disks turn out to be the greatest TV remote for kids

https://blog.smartere.dk/2026/01/floppy-disks-the-best-tv-remote-for-kids/
540•mchro•16h ago•317 comments

PawSense: Catproof Your Computer

http://bitboost.com/pawsense/
15•zdw•1h ago•4 comments

Unauthenticated remote code execution in OpenCode

https://cy.md/opencode-rce/
275•CyberShadow•1d ago•83 comments

Date is out, Temporal is in

https://piccalil.li/blog/date-is-out-and-temporal-is-in/
342•alexanderameye•13h ago•130 comments

Fabrice Bellard's TS Zip (2024)

https://www.bellard.org/ts_zip/
124•everlier•8h ago•51 comments

LLVM: The bad parts

https://www.npopov.com/2026/01/11/LLVM-The-bad-parts.html
308•vitaut•14h ago•57 comments

Apple picks Gemini to power Siri

https://www.cnbc.com/2026/01/12/apple-google-ai-siri-gemini.html
739•stygiansonic•13h ago•432 comments

Show HN: AI in SolidWorks

https://www.trylad.com
142•WillNickols•12h ago•78 comments

A deep dive on agent sandboxes

https://pierce.dev/notes/a-deep-dive-on-agent-sandboxes
14•icyfox•6h ago•1 comments

Show HN: Yolobox – Run AI coding agents with full sudo without nuking home dir

https://github.com/finbarr/yolobox
69•Finbarr•10h ago•54 comments

Why BM25 queries with more terms can be faster (and other scaling surprises)

https://turbopuffer.com/blog/bm25-latency-musings
13•_peregrine_•4d ago•0 comments

Anthropic made a mistake in cutting off third-party clients

https://archaeologist.dev/artifacts/anthropic
250•codesparkle•18h ago•185 comments

F2 (YC S25) Is Hiring

https://www.ycombinator.com/companies/f2/jobs/cJsc7Fe-product-designer
1•arctech•6h ago

Show HN: Agent-of-empires: OpenCode and Claude Code session manager

https://github.com/njbrake/agent-of-empires
75•river_otter•14h ago•22 comments

Implementing a web server in a single printf() call (2014)

https://tinyhack.com/2014/03/12/implementing-a-web-server-in-a-single-printf-call/
8•nateb2022•4d ago•1 comments

Windows 8 Desktop Environment for Linux

https://github.com/er-bharat/Win8DE
164•edent•15h ago•155 comments

Message Queues: A Simple Guide with Analogies (2024)

https://www.cloudamqp.com/blog/message-queues-exaplined-with-analogies.html
86•byt3h3ad•11h ago•25 comments

Google removes AI health summaries after investigation finds dangerous flaws

https://arstechnica.com/ai/2026/01/google-removes-some-ai-health-summaries-after-investigation-fi...
123•barishnamazov•6h ago•72 comments

Show HN: Fall asleep by watching JavaScript load

https://github.com/sarusso/bedtime
58•sarusso•10h ago•18 comments

Ozempic is changing the foods Americans buy

https://news.cornell.edu/stories/2025/12/ozempic-changing-foods-americans-buy
358•giuliomagnifico•16h ago•635 comments

Zen-C: Write like a high-level language, run like C

https://github.com/z-libs/Zen-C
176•simonpure•16h ago•98 comments

The struggle of resizing windows on macOS Tahoe

https://noheger.at/blog/2026/01/11/the-struggle-of-resizing-windows-on-macos-tahoe/
2590•happosai•1d ago•1106 comments

What old tennis players teach us (2017)

https://www.raphkoster.com/2017/09/22/31098/
43•surprisetalk•4d ago•24 comments

Building a 25 Gbit/s workstation for the SCION Association

https://github.com/scionassociation/blog-25gbit-workstation
71•romshark•12h ago•26 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•7mo 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•7mo ago
Thanks for the response, guess that makes sense.
pabs3•7mo 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?