frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Network of Scottish X accounts go dark amid Iran blackout

https://www.heraldscotland.com/news/25759181.network-scottish-x-accounts-go-dark-amid-iran-blackout/
9•TiredOfLife•41m ago•0 comments

Cowork: Claude Code for the rest of your work

https://claude.com/blog/cowork-research-preview
1023•adocomplete•16h ago•451 comments

FOSS in times of war, scarcity and (adversarial) AI [video]

https://fosdem.org/2026/schedule/event/FE7ULY-foss-in-times-of-war-scarcity-and-ai/
31•maelito•2h ago•18 comments

Show HN: An iOS budget app I've been maintaining since 2011

https://primoco.me/en/
19•Priotecs•1h ago•7 comments

Text-Based Web Browsers

https://cssence.com/2026/text-based-web-browsers/
111•pabs3•6h ago•48 comments

TimeCapsuleLLM: LLM trained only on data from 1800-1875

https://github.com/haykgrigo3/TimeCapsuleLLM
628•admp•19h ago•260 comments

U.S. Emissions Jumped in 2025 as Coal Power Rebounded

https://www.nytimes.com/2026/01/13/climate/us-emissions-2025-coal-power.html
76•fleahunter•1h ago•65 comments

Designing an IPv6-native P2P transport – lessons from building I6P

https://theushen.medium.com/designing-an-ipv6-native-p2p-transport-lessons-from-building-i6p-b8ca...
18•TheusHen•3d ago•13 comments

Postal Arbitrage

https://walzr.com/postal-arbitrage
421•The28thDuck•18h ago•212 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/
654•mchro•22h ago•371 comments

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

https://www.youtube.com/watch?v=c0mLhHDcY3I
249•cjaackie•16h ago•228 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/
60•nateb2022•4d ago•5 comments

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

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

Some ecologists fear their field is losing touch with nature

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

Unauthenticated remote code execution in OpenCode

https://cy.md/opencode-rce/
342•CyberShadow•1d ago•112 comments

Date is out, Temporal is in

https://piccalil.li/blog/date-is-out-and-temporal-is-in/
397•alexanderameye•20h ago•162 comments

Deconstructing the LuaJIT Pseudo Memory Leak

https://blog.openresty.com/en/luajit-plus/
7•dgares•3d ago•0 comments

Fabrice Bellard's TS Zip (2024)

https://www.bellard.org/ts_zip/
176•everlier•15h ago•70 comments

LLVM: The bad parts

https://www.npopov.com/2026/01/11/LLVM-The-bad-parts.html
347•vitaut•21h ago•68 comments

Apple picks Gemini to power Siri

https://www.cnbc.com/2026/01/12/apple-google-ai-siri-gemini.html
874•stygiansonic•20h ago•541 comments

The Homepage of Ron Goodwin

http://rongoodwin.co.uk/
4•ocfnash•2h ago•1 comments

Chromium Has Merged JpegXL

https://chromium-review.googlesource.com/c/chromium/src/+/7184969
136•thunderbong•5h ago•35 comments

Show HN: AI in SolidWorks

https://www.trylad.com
166•WillNickols•19h ago•90 comments

Zirgen: Compiler for a Domain-Specific Language

https://github.com/risc0/zirgen
12•0xkato•4d ago•0 comments

Anthropic made a mistake in cutting off third-party clients

https://archaeologist.dev/artifacts/anthropic
315•codesparkle•1d ago•205 comments

Windows 8 Desktop Environment for Linux

https://github.com/er-bharat/Win8DE
204•edent•22h ago•195 comments

F2 (YC S25) Is Hiring

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

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

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

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

https://github.com/finbarr/yolobox
93•Finbarr•17h ago•69 comments

The struggle of resizing windows on macOS Tahoe

https://noheger.at/blog/2026/01/11/the-struggle-of-resizing-windows-on-macos-tahoe/
2654•happosai•1d ago•1137 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•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?