frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Elevators

https://john.fun/elevators
477•Jrh0203•3h ago•149 comments

Big Food vs. the People

https://www.lighthousereports.com/investigation/big-food-vs-the-people/
107•jruohonen•2h ago•59 comments

qm

https://github.com/yc-software/qm
35•tosh•51m ago•16 comments

Getting 25 Gbps Thunderbolt Ethernet on My Mac Studio

https://www.jeffgeerling.com/blog/2026/getting-25g-ethernet-mac-thunderbolt/
66•speckx•2h ago•38 comments

Termixer (TUI DJ Mixer)

https://github.com/l00sed/termixer
8•l00sed•28m ago•1 comments

Algorithms on billion-scale graph using 10GB RAM: I love DataFusion

https://semyonsinchenko.github.io/ssinchenko/post/datafusion-graphs-cc-2/
51•speckx•3h ago•11 comments

DeepSeek V4 Flash 0731 Intelligence, Performance and Price Analysis

https://artificialanalysis.ai/models/deepseek-v4-flash
452•theanonymousone•10h ago•242 comments

DeepSeek-V4-Flash Update

https://api-docs.deepseek.com/updates/
597•dnhkng•12h ago•293 comments

The most official water costs $120k a gallon

https://signoregalilei.com/2026/07/26/the-most-official-water-costs-120000-a-gallon/
61•surprisetalk•3h ago•35 comments

Miso (YC S16) is hiring for U.S. expansion

https://www.ycombinator.com/companies/miso/jobs/g2uAlMG-founding-business-lead-u-s-expansion
1•victorology•1h ago

A GTK4 SSH-askpass in Zig

https://xn--gckvb8fzb.com/a-gtk4-ssh-askpass-in-zig/
41•surprisetalk•3h ago•15 comments

How JPEG works: Interactively explore JPEG's lossy compression methods

https://cgjennings.ca/articles/jpeg-compression/
32•at1as•4d ago•3 comments

13 Models and 4 Agents on SWE Tasks: Go, Java, Python, Rust, TS

https://swe-rebench.com
27•ibragim_bad•3h ago•10 comments

The End of an Era

https://hughhowey.com/the-end-of-an-era/
331•harscoat•7h ago•377 comments

Run Kimi K3 using 29 GB of RAM at 0.50 tok/s

https://github.com/sqliteai/waste
46•marcobambini•4h ago•14 comments

The session you cannot take with you

https://earendil.com/posts/session-portability/
700•apitman•15h ago•200 comments

Anti-fraud tools can't keep pace with robocall scammers

https://broadbandbreakfast.com/how-to-fight-back-against-fraudulent-robocalls/
38•dredmorbius•5h ago•45 comments

The C ``Clockwise/Spiral Rule''

https://c-faq.com/decl/spiral.anderson.html
43•etrvic•4h ago•26 comments

Show HN: BitBang – Reach machines behind NAT from a browser, no account

https://github.com/richlegrand/bitbang-cli
39•narragansett•4h ago•8 comments

The Art of Decision-Making (2019)

https://www.newyorker.com/magazine/2019/01/21/the-art-of-decision-making
24•EndXA•3h ago•2 comments

How to Survive an Infestation of Toxic Caterpillars

https://www.newyorker.com/science/elements/how-to-survive-an-infestation-of-toxic-caterpillars
4•littlexsparkee•43m ago•0 comments

Arch Linux disables AUR package adoption

https://lwn.net/Articles/1086489/
89•database64128•4h ago•64 comments

AFC Stands in Solidarity with UEFA and Concacaf to Protect the FIFA World Cup

https://www.the-afc.com/en/more/afc_news.html/news/afc-stands-in-solidarity-with-uefa-and-concaca...
6•smokeeaasd•1h ago•0 comments

Everyone is building LLM routers, we deprecated ours

https://manifest.build/blog/why-we-deprecated-our-llm-router/
5•brunaxLorax•49m ago•1 comments

Google fixed more Chrome bugs in June than over the past two years, thanks to AI

https://blog.google/security/chrome-stronger-with-every-update/
438•Garbage•11h ago•435 comments

Danube's record low levels force shutdown of Hungary's only nuclear plant

https://www.bbc.com/news/articles/cn0nqv05g0do
91•vrganj•11h ago•105 comments

IMAX vs. IMAX 70mm: The difference between these two cinema formats

https://www.engadget.com/2220571/differences-between-imax-70mm/
65•ksec•6d ago•89 comments

Show HN: Slope remade in HTML5 to load instantly on any browser, any device

https://hurtle.site/
17•novlrdotcom•1h ago•5 comments

Investigating three real-world incidents in our cybersecurity evaluations

https://www.anthropic.com/news/investigating-incidents-cybersecurity-evals
212•surprisetalk•19h ago•165 comments

Solving poker in custom WebGPU kernels

https://phulin.me/blog/poker/
55•patrickhulin•1d ago•15 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?