frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Total Annihilation, rebuilt for modern computers

https://nanolathe.gg
252•jttnr•3h ago•102 comments

The gap in shared understanding of LLM capability is widening

https://twitter.com/karpathy/status/2109361546505966046
40•albertzeyer•1h ago•16 comments

Cartographers of North Korea

https://cartographers-nk.wonyoung.so/
87•edent•2h ago•8 comments

Do You Have Pre-2012 Onion Issues?

https://theonion.com/archivehunt/
163•mooreds•2h ago•15 comments

Chapter 1 of Ways of Seeing by John Berger

https://www.ways-of-seeing.com/ch1
53•rafael859•3h ago•9 comments

Terence Tao: Math 2.0 [pdf]

https://teorth.github.io/tao-web/slides/math-2-0-caltech-2026.pdf
269•Anon84•8h ago•321 comments

NYC's "Click to Cancel" rule is now in effect

https://www.nyc.gov/main/click-to-cancel
253•gregsadetsky•3h ago•113 comments

A Remote Employee Refused 160 Webcam Photos a Day. Her Employer Fired Her

https://www.inc.com/chloe-rosenberg/a-remote-employee-refused-160-webcam-photos-a-day-her-employe...
37•bhrlady•47m ago•11 comments

How to Build Wealth as a Career Person

https://asheradeniyi.com/2026/04/10/how-to-build-wealth-as-a-career-person/
100•doppp•5h ago•103 comments

IRCv3

https://ircv3.net/
309•basilikum•11h ago•266 comments

The Unreasonable Effectiveness of Vex in NixOS

https://blog.kammel.dev/post/nixos_vex/
30•datosh•2h ago•0 comments

apsw: Another Python SQLite Wrapper

https://github.com/rogerbinns/apsw
46•tosh•4h ago•13 comments

LineageOS 24.0

https://lineageos.org/Changelog-32/
387•timschumi•15h ago•163 comments

The tilde in your PATH may not be your HOME

https://disconnect3d.pl//2026/10/02/dont-put-tilde-in-your-path/
190•arusekk•9h ago•131 comments

Show HN: BetterWispr – Free, open-source dictation for Mac

https://betterwispr.com/
127•kartik017•9h ago•78 comments

Akhetonics Photonic Computing: 1,000x Faster CPUs

https://medium.com/@timventura/akhetonics-photonic-computing-1-000x-faster-cpus-b9e91c470079
47•peter_d_sherman•3d ago•33 comments

Safe SIMD in Rust, even on the inside

https://shnatsel.github.io/safe-simd-in-rust-even-on-the-inside/
11•ravenical•1d ago•0 comments

How I reverse engineered a commercial spatial audio effect

http://epestr.com/blog/reverse-engineering-a-commercial-spatial-audio-effect/
77•epestr•6h ago•27 comments

FlowCE: Calculus on your TI-84 Plus CE

https://tommyb3ll.github.io/FlowCE/
8•jgx0•1d ago•3 comments

Valen's Memory Safety: A New Kind of Borrow Checking

https://verdagon.dev/blog/valen-group-borrowing
122•verdagon•9h ago•74 comments

Shape-sensing sheet digitally tracks its own movement as it bends and twists

https://news.mit.edu/2026/shape-sensing-sheet-digitally-tracks-movement-bends-twists-1008
20•bookofjoe•1d ago•0 comments

Playgrnd – tiny tools for making weird, beautiful things

https://www.playgrnd.tools/
43•eustoria•5h ago•8 comments

The RAM shortage is bringing back DDR4

https://www.theverge.com/games/1009140/ram-shortage-intel-amd-ddr4-comeback
260•1potato•1d ago•270 comments

I'm sorry, but you still have to think

https://itsallaboutthebit.com/i-am-sorry-but-you-still-have-to-think/
280•drogus•7h ago•115 comments

A Cray-1 supercomputer replica from 30 "obsolete" Mac Minis

https://arstechnica.com/gadgets/2026/10/a-cray-1-supercomputer-replica-from-30-obsolete-mac-minis/
51•pseudolus•1d ago•22 comments

Weave (YC W25) is hiring ML, AI, product, & design engineers

https://jobs.ashbyhq.com/weave-os
1•adchurch•9h ago

I paid people to try and follow my README

https://shkspr.mobi/blog/2026/10/i-paid-people-to-try-and-follow-my-readme/
349•edent•10h ago•183 comments

Fetching AMD SEV Reports (With Zig)

https://bschaatsbergen.com/posts/zig-sev-guest/
3•peterpanhead•1h ago•0 comments

Scandinavia's first farmers slaughtered hunter-gatherer population, DNA suggests

https://phys.org/news/2024-02-scandinavia-farmers-slaughtered-hunter-population.html
48•optimalsolver•9h ago•74 comments

3rd Yandex Cloud Data Center Was Hit

https://status.yandex.cloud/en/incidents/2136
531•defly•14h ago•637 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?