frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

GPU Offload in Rust: Portable, Safe, and Fast

https://arxiv.org/abs/2608.13759
114•linggen•4h ago•23 comments

A Preview of DuckDB v2.0

https://duckdb.org/2026/08/17/duckdb-20-highlights
485•ibotty•8h ago•84 comments

AI;DR (AI; Didn't Read)

https://www.rickmanelius.com/p/aidr-ai-didnt-read
406•mooreds•2h ago•243 comments

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

https://www.wiz.io/blog/red-agent-snowflake-copilot-cicd-bug
284•galnagli•7h ago•118 comments

Incident with Github.com

https://www.githubstatus.com/incidents/zkxwbgr0cnmx
463•SpyCoder77•8h ago•839 comments

The Origin of Consciousness (2008)

https://blog.plover.com/brain/Jaynes.html
34•skm•2h ago•19 comments

Sun Clock

https://sunclock.net/
144•Gecko4072•5h ago•43 comments

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

https://blog.roboflow.com/openai-gpt-5-6/
279•plurby•10h ago•146 comments

How to disable or avoid intrusive AI

https://www.librarian.net/notoai/
217•ColinWright•8h ago•118 comments

Olo (Color)

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

Judge sets framework for Nine PBS to retrieve archival data

https://current.org/2026/08/judge-sets-framework-for-nine-pbs-to-retrieve-archival-data/
97•qingcharles•6h ago•41 comments

An update on leaving Gmail for Fastmail

https://moddedbear.com/an-update-on-leaving-gmail-for-fastmail/
69•neogodless•4h ago•47 comments

Roboflow Playground: Try and Compare 30 Computer Vision Models

https://blog.roboflow.com/roboflow-playground/
28•Bluestein•3h ago•3 comments

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

https://speko.ai/
80•abdik•6h ago•50 comments

Intriguing Stories in Computer Science

https://inventwithpython.com/blog/intriguing-stories-in-cs.html
6•gregsadetsky•5d ago•0 comments

Marketers are Addicted to Bad Data (2020)

https://www.jacquescorbytuech.com/writing/marketers-addicted-bad-data
32•zbentley•4d ago•34 comments

A particle made of force: physicists say they've found mysterious 'glueball'

https://www.nature.com/articles/d41586-026-02498-1
76•Brajeshwar•5d ago•3 comments

Ask HN: Alternatives to GitHub

447•dhruv3006•8h ago•285 comments

India has paved the way for charging merchants a fee on UPI transactions

https://www.bbc.com/news/articles/c8xnwqe00v1o
70•monkey_monkey•2h ago•60 comments

A simple fix for LLM tail latency

https://engineering.myhoai.com/posts/a-simple-fix-for-llm-tail-latency/
19•oskrim•3d ago•7 comments

Qwen3.8 27B scores 52 on Artificial Analysis

https://artificialanalysis.ai/models/qwen3-8-27b
254•anana_•4h ago•113 comments

The oldest bar in every state

https://www.businessinsider.com/oldest-bar-every-state
43•NaOH•4d ago•26 comments

We Are Forking dotenvy into dotenv-ng

https://secretspec.dev/blog/we-are-forking-dotenvy-into-dotenv-ng/
30•linggen•4h ago•29 comments

How to put 170 atoms in an atom

https://signoregalilei.com/2026/08/02/how-to-put-170-atoms-in-an-atom/
93•surprisetalk•7h ago•19 comments

Los Puesteros, solitary men who look after ranches and livestock in Patagonia

https://www.newyorker.com/culture/photo-booth/the-lonely-men-at-the-end-of-the-world
90•bookofjoe•3h ago•34 comments

How I developed an Am29000 C compiler and web browser

https://nanochess.org/am29000_c_compiler_web_browser.html
74•nanochess•1d ago•11 comments

On AI regulation and messaging

https://twitter.com/DarioAmodei/status/2088758816376807762
226•jacquesm•20h ago•480 comments

Show HN: Sokoban AI Solver

https://mkornreich.me/projects/sokoban/
64•enjoyyourlife•9h ago•37 comments

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

https://desktopcolors.com
130•vlowrian•14h ago•58 comments

How to ship a database every day

https://turbopuffer.com/blog/control-plane
63•tarunnnp•8h ago•8 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?