frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Tencent Releases and Open-Sources Tencent Hy4 Preview

https://www.tencent.com/tencent-releases-and-open-sources-tencent-hy4-preview/
46•shenli3514•1h ago•15 comments

vLLM v0.28.0

https://github.com/vllm-project/vllm/releases/tag/v0.28.0
37•mrrrcs•2h ago•8 comments

Tether: iMessage, SMS, etc. on Linux

https://zackbartel.com/blog/2026/08/tether/
213•zackb•5d ago•95 comments

Calibrate Before You Accelerate: Bias Toward Action in a New Role

https://tucker.wales/writing/bias-towards-action/
53•tuckerwales•3h ago•16 comments

Warp builds self-improving agents on Claude

https://claude.com/blog/how-warp-builds-self-improving-agents-on-claude
43•shenli3514•1h ago•38 comments

SQLite as a Document Database (2020)

https://dgl.cx/2020/06/sqlite-json-support
130•lioeters•4d ago•42 comments

DHS is using obscure law to snoop on journalists, non-profits, unions

https://www.theguardian.com/us-news/2026/aug/29/trump-dhs-1509-summons-records-journalists-nonpro...
155•firefax•2h ago•21 comments

Domain-Driven Agents

https://coldtake.dev/blog/domain-driven-agents
9•AlarQ•1h ago•0 comments

Good Culture Is the Biggest Productivity Hack, Not AI

https://newsletter.eng-leadership.com/p/good-culture-is-the-biggest-productivity
143•gpi•3h ago•25 comments

Glacier Mice

https://en.wikipedia.org/wiki/Glacier_mice
216•ostacke•5d ago•45 comments

Sleepwalker: Passive Backdoor with Its Own Command Language

https://r136a1.dev/2026/08/24/sleepwalker-a-passive-backdoor-with-its-own-command-language/
44•defrost•4d ago•5 comments

LLMs are making me lose my savviness

https://pgaleone.eu/ai/2026/08/29/losing-savviness/
12•me2too•2h ago•8 comments

Indirect Calling of Nested Functions on GCC Without Executable Stack

https://uecker.codeberg.page/2026-08-29.html
57•uecker•6h ago•29 comments

Show HN: Typebase – A single-folder back end you write in TypeScript

https://typebase.io
82•andrewww-dev•3d ago•18 comments

Samsung's Processing-in-Memory (PIM)

https://chipsandcheese.com/p/hot-chips-2026-samsungs-processing
225•ingve•14h ago•79 comments

EVE Online moves to Python 3

https://www.eveonline.com/news/view/the-move-to-python-3-begins
249•TylerJaacks•4d ago•129 comments

Quantifying Colour

https://ekunazanu.foo/lab/quantifying-colour/
48•vismit2000•5h ago•3 comments

A better SQL in 11 lines of code

https://prela-lang.org/tutorial/
28•remywang•3h ago•29 comments

Creating the Aetheryte Radio

https://haz.ee/posts/aetheryte-radio.html
55•wonger_•1d ago•12 comments

Kmart Digicam Mod Part 2

https://mason.bearblog.dev/kmart-digicam-mod-part-2/
6•masoniamme•5d ago•0 comments

GrapheneOS project: pixel 11 no longer supports hardware memory tagging (MTE)

https://bsky.app/profile/grapheneos.org/post/3mua32q4ds22e
186•400thecat•5h ago•67 comments

Htmx 4.0

https://four.htmx.org/announcements/2026-08-28-htmx-4.0.0-is-released
790•rmsaksida•1d ago•202 comments

Boot a Virtual iPhone via Apple's Virtualization.framework

https://github.com/Lakr233/vphone-cli
365•hentrep•22h ago•97 comments

Trees for a Changing Climate and Resilient Urban Forest (2022)

https://www.coolboulder.org/news/trees-for-a-changing-climate-resilient-urban-forest
9•mooreds•4h ago•1 comments

Recovering Corrupt Zip Files

https://www.construct.net/en/blogs/ashleys-blog-2/recovering-corrupt-zip-files-1895
8•AshleysBrain•3d ago•0 comments

Nancy Grace Roman Space Telescope

https://science.nasa.gov/mission/roman-space-telescope/
92•JumpCrisscross•5h ago•30 comments

The internet is kind of a predatory cesspit now

https://www.stephendiehl.com/posts/internet_predatory_cesspit/
331•ibobev•2h ago•218 comments

Functional State Machines in Rust: Typestate and Newtype Patterns

https://dl.acm.org/doi/10.1145/3830438.3830958
3•matt_d•2h ago•0 comments

Show HN: Galaxium, an experimental WebGPU space explorer

https://galaxium.app
87•guillaumec•5d ago•29 comments

Hunting Down a Go Runtime Bug on 32-Bit Embedded Systems

https://sigma-star.at/blog/2026/08/go-runtime-netpoll-bug/
100•birdculture•3d ago•12 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?