frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Munder Difflin – Agent harness to run an office of your clones

https://munderdiffl.in/
63•simonpure•3h ago•24 comments

Canada suspends trade negotiations with USA and match tariffs dollar for dollar

https://www.pm.gc.ca/en/news/statements/2026/08/21/statement-prime-minister-carney-canada-us-trad...
406•backlit4034•2h ago•277 comments

Z80–The 1970s Microprocessor Still Alive

https://www.computer.org/csdl/magazine/mi/2021/06/09623402/1yJTvlRLmhi
40•asdefghyk•3h ago•20 comments

Rust Glancer: Rust LSP using 100x less RAM

https://rust-glancer.github.io/blog/hello-world/
304•matklad•17h ago•59 comments

Felony Bench

https://www.felonybench.com/
756•colinprince•21h ago•283 comments

Hook, hold, harvest and hide: Meta's alleged strategy laid out in first week

https://www.theguardian.com/technology/2026/aug/22/meta-trial-children-privacy
27•sbulaev•1h ago•1 comments

Kobo can run apps now

https://bandarlabs.github.io/Cobalt/
587•thepoet•20h ago•193 comments

Felony charges for citizen deleting phone data at US Border

https://www.nytimes.com/2026/08/21/us/politics/samuel-tunick-deleted-phone-felony.html
865•floathub•1d ago•988 comments

There's no reason for software to be slow anymore

https://danluu.com/perf-opt/
498•Jach•12h ago•352 comments

I accidentally logged hundreds of thousands of phone calls to military bases

https://lina.sh/blog/hijacking-e164-arpa
585•gavide•23h ago•72 comments

Zig’s io.threaded is neat

https://matklad.github.io/2026/08/06/neat-io-threaded.html
99•chilipepperhott•22h ago•52 comments

Kagi added a setting for removing paywalled links from search results

https://kagi.com/changelog#11296
1169•speckx•23h ago•370 comments

Three important steps in my maturation process

https://thomasdullien.github.io/posts/2026-08-21-three-important-steps-in-my-maturation-process/
168•tdullien•14h ago•78 comments

Stop Making TUIs

https://sockpuppet.org/blog/2026/08/20/stop-making-tuis/
201•underdeserver•1d ago•293 comments

OTel isn’t going well

https://matduggan.com/otel-isnt-going-well-and-i-made-a-spreadsheet-about-it/
151•hn_acker•19h ago•61 comments

Scientists release biggest 2D map of the universe

https://newscenter.lbl.gov/2026/08/10/scientists-release-biggest-2d-map-of-the-universe/
220•NKosmatos•18h ago•59 comments

AI boosted homework scores, then exam scores dropped: study

https://www.economist.com/graphic-detail/2026/08/18/does-ai-stop-children-from-learning
327•dash2•3d ago•335 comments

How Thailand Resisted Colonization

https://worksinprogress.co/issue/how-thailand-resisted-colonization/
47•karakoram•18h ago•11 comments

Galactic Compass 2: now with new augmented reality mode

https://interconnected.org/home/2026/08/21/galactic
19•bobbiechen•19h ago•2 comments

Optimizing meshoptimizer to process billions of triangles in minutes (2025)

https://zeux.io/2025/09/30/billions-of-triangles-in-minutes/
49•corysama•19h ago•0 comments

Claudette: Make Claude stop talking like a BuzzFeed article

https://github.com/adnanakil/nobuzz/blob/main/README.md
305•aakil•22h ago•195 comments

I'm becoming AI-blind

https://cymerys.com/w/im-becoming-ai-blind
411•rcymerys•1d ago•417 comments

People of ACM – Russ Cox

https://www.acm.org/articles/people-of-acm/2026/russ-cox
145•signa11•5d ago•14 comments

New Worlds: We are living in the future of J.G. Ballard or William Gibson

https://precastreinforced.co.uk/2026/08/16/new-worlds/
258•speckx•1d ago•166 comments

Early-life stress leaves a 'scar' inside brain cells in mice

https://medicine.washu.edu/news/how-early-life-stress-leaves-a-scar-inside-brain-cells/
99•gmays•1d ago•49 comments

Everyone says assembly is untyped—everyone is wrong

https://www.gingerbill.org/article/2026/08/20/designing-odins-inline-asm/
101•adamrezich•1d ago•45 comments

A revisit of remote Spectre attacks on Cloudflare Workers

https://blog.cloudflare.com/revisiting-spectre-attacks-on-workers/
63•albertpedersen•2d ago•1 comments

HN: The Good Parts (2016)

https://danluu.com/hn-comments/
62•adletbalzhanov•13h ago•11 comments

The coolest anti-surveillance tools at Defcon [video]

https://www.youtube.com/watch?v=-2uAsJ5EPAw
217•neom•3d ago•37 comments

How we made a text-to-speech model respond in sub-50 ms

https://nari-labs.com/blog/qwen3-tts-speed-cost-frontier/
157•toebee•21h ago•38 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?