frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

A Preview of DuckDB v2.0

https://duckdb.org/2026/08/17/duckdb-20-highlights
184•ibotty•2h ago•19 comments

Universal Health Coverage Could Save $1T and 114,000 Lives a Year, Yale Study

https://ysph.yale.edu/news-article/universal-health-coverage-could-save-one-trillion-dollars-and-...
22•karakoram•14m ago•12 comments

AI-Generated GitHub Copilot "Autofix" Allowed Compromise of Snowflake's Jira

https://www.wiz.io/blog/red-agent-snowflake-copilot-cicd-bug
76•galnagli•1h ago•32 comments

GPT 5.6 Sol is the best "vision" model OpenAI ever released

https://blog.roboflow.com/openai-gpt-5-6/
162•plurby•3h ago•91 comments

How to disable or avoid intrusive AI

https://www.librarian.net/notoai/
56•ColinWright•1h ago•15 comments

Incident with Github.com

https://www.githubstatus.com/incidents/zkxwbgr0cnmx
630•kevcampb•2h ago•464 comments

Launch HN: Speko (YC S26) – OpenRouter for Voice AI

10•abdik•27m ago•0 comments

How to put 170 atoms in an atom

https://signoregalilei.com/2026/08/02/how-to-put-170-atoms-in-an-atom/
35•surprisetalk•1h ago•4 comments

GitHub down again? no PR access

248•yodon•2h ago•83 comments

Apple's App Tracking Transparency treated its own apps better than rivals

https://www.bundeskartellamt.de/SharedDocs/Meldung/EN/Pressemitteilungen/2026/08_17_2026_Apple_AT...
151•nyku•1h ago•49 comments

Qwen 3.8 27B is excellent, but it defaults to overthinking things

https://simonwillison.net/2026/Aug/16/qwen-38-27b/
696•bilsbie•16h ago•328 comments

Show HN: Sokoban AI Solver

https://mkornreich.me/projects/sokoban/
34•enjoyyourlife•2h ago•23 comments

How I developed an Am29000 C compiler and web browser

https://nanochess.org/am29000_c_compiler_web_browser.html
20•nanochess•19h ago•0 comments

Olo (Color)

https://en.wikipedia.org/wiki/Olo_(color)
26•inigyou•5d ago•0 comments

Show HN: Learn Flags Quiz

https://flagquizzes.com/
9•artiomyak•1h ago•1 comments

Qwen3.8-27B at 256K on a 24GB RTX PRO 4000 SFF (432 GB/s): 50 tok/s with MTP

https://piszczek.pl/blog/qwen38-27b-256k-50-tps-24gb-gpu
23•pich•1h ago•12 comments

How to ship a database every day

https://turbopuffer.com/blog/control-plane
21•tarunnnp•2h ago•0 comments

Anthropic's 'watermark' text adulteration in Claude is a perversion of writing

https://daringfireball.net/2026/08/anthropics_watermark_text_adulteration_in_claude_is_a_perversi...
580•ropbear•18h ago•516 comments

Mexico Crackdown on Coastal Development Underway

https://yucatanmagazine.com/mexico-crackdown-on-coastal-development/
71•untiledsource•3h ago•13 comments

On A.I. regulation and messaging

https://twitter.com/DarioAmodei/status/2088758816376807762
185•jacquesm•14h ago•377 comments

Show HN: Desktopcolors.com – A museum for solid background colors of classic OS

https://desktopcolors.com
88•vlowrian•8h ago•36 comments

How Go detects struct copies with sync.noCopy

https://func25.dev/posts/go-sync-nocopy/
42•func25•4d ago•41 comments

Cialis is an erectile dysfunction drug. Could it also help you live longer?

https://www.npr.org/2026/08/17/nx-s1-5928263/cialis-viagra-tadalafil-longevity-heart-health
60•brandonb•2h ago•37 comments

A third world engineer responds to “RISC-V: They should have known better”

https://rvembedded.com/blog_post/12/
583•Narishma•23h ago•294 comments

Ask HN: Alternatives to GitHub

162•dhruv3006•2h ago•108 comments

Linear algebra done right

https://linear.axler.net/
178•the-mitr•10h ago•64 comments

The only known trebuchet casualty in history

https://arstechnica.com/science/2026/08/meet-the-only-known-trebuchet-casualty-in-history/
24•Tomte•1h ago•4 comments

Claude: System Prompts

https://platform.claude.com/docs/en/release-notes/system-prompts
726•tosh•1d ago•276 comments

Reticulum – Decentralized Mesh Network

https://reticulum.network/
186•sudo_cowsay•16h ago•64 comments

Judge relying wholly on AI in order is covered by judicial immunity, court rules

https://reason.com/volokh/2026/08/17/judges-allegedly-relying-wholly-on-ai-in-order-is-covered-by...
17•delichon•1h 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?