frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

GLM-5.3: Frontier coding with emergent cyber capabilities

https://z.ai/blog/glm-5.3
346•pella•3h ago•131 comments

Gemini 3.7 Flash

https://blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-3-7-fl...
794•thisisauserid•14h ago•424 comments

Accelerating GPT-5.6 Sol Ultrafast

https://www.cerebras.ai/blog/accelerating-gpt-5-6-sol-ultrafast-with-openai
561•pr337h4m•14h ago•233 comments

Hello, me. It's been a while

https://themech.net/2026/08/hello-me-its-been-a-while/
183•somesoftdev•13h ago•87 comments

Show HN: C# Game Engine with its own scripting language and IDE

https://github.com/ArcadeMakerSources/ArcadeMaker
23•am-gm•2d ago•1 comments

Bluesky Protocol Services

https://atproto.com/blog/introducing-bluesky-protocol-services
157•danabramov•8h ago•28 comments

DeepSeek Harness developer preview

https://deepseek.com/harness/en/
642•bjin•19h ago•268 comments

Ruby 4.0 Universal RCE Deserialization Gadget Chain

https://www.elttam.com/blog/ruby-4-0-universal-rce-deserialization-gadget-chain
15•pentestercrab•2h ago•1 comments

Spaghettifying DRAM

https://github.com/xoreaxeaxeax/skitter-creek-bath-salts
599•matt_d•18h ago•154 comments

Mistral OCR 4.1

https://docs.mistral.ai/models/ocr-4-1
324•spelk•15h ago•130 comments

Understanding is the new bottleneck

https://www.geoffreylitt.com/2026/07/02/understanding-is-the-new-bottleneck
302•sebg•13h ago•162 comments

Show HN: Lumabri – Run Moe Models on a P2P Swarm with Colibri

https://github.com/JustVugg/lumabri
5•vforno•7h ago•0 comments

Choose Boring Technology (2015)

https://mcfunley.com/choose-boring-technology
327•tosh•14h ago•164 comments

The Library of Ashurbanipal (2025)

https://www.historytoday.com/archive/feature/library-ashurbanipal
26•samizdis•3d ago•8 comments

Donkey.bas is 45 Years Old – 131 line of Glory

https://donkeybas.com/
227•jkrauska•14h ago•104 comments

NP-overrated

https://gruhn.me/blog/2026-08-13/
202•theanonymousone•12h ago•133 comments

Nine PBS sues Iron Mountain over blocked access to archival data

https://current.org/2026/08/nine-pbs-sues-iron-mountain-over-blocked-access-to-archival-data/
300•vinayakborkar•19h ago•171 comments

Blog about things you don't understand yet

https://www.seangoedecke.com/blog-about-things-you-dont-understand-yet/
92•gfysfm•8h ago•31 comments

How Compaction Works in Pi

https://earendil.com/posts/compaction-in-pi/
155•tosh•14h ago•60 comments

What an Improv Stage Can Teach You About Leading Cross-Cultural Teams in Tokyo

https://www.tokyodev.com/articles/yes-and-what-an-improv-stage-can-teach-you-about-leading-cross-...
3•pwim•1w ago•0 comments

Where did the old web go? We followed 657,607 links to find out

https://0.mk/blog/link-rot
174•tdx•14h ago•157 comments

Single log line is 49KB+ (ext4) / 110KB+ (btrfs) of systemd-journald disk writes

https://github.com/systemd/systemd/issues/40262
204•ValdikSS•13h ago•131 comments

Credibility is the barrier to entry in silicon

https://www.siliconimist.com/p/credibility-is-the-barrier-to-entry
19•johncole•3d ago•7 comments

How Organizations Use AI: Evidence from ChatGPT [pdf]

https://cdn.openai.com/pdf/how-organizations-use-chatgpt.pdf
102•malshe•12h ago•59 comments

Finite State Machines in Forth (1994)

https://www.forth.org/literature/noble.html
73•ofalkaed•5d ago•2 comments

The Legend of the Novell NE2000 [video]

https://www.youtube.com/watch?v=nNXzQ7V1S_k
41•voxadam•4d ago•13 comments

How Gödel's Proof Works (2020)

https://www.quantamagazine.org/how-godels-proof-works-20200714/
101•tzury•12h ago•42 comments

Cave of the Crystals

https://en.wikipedia.org/wiki/Cave_of_the_Crystals
41•ColinWright•5d ago•2 comments

Ordinary Abundance

https://ordinaryabundance.com/
294•yen223•18h ago•151 comments

an ambiguity in C89 which will never be fixed

https://sebsite.pw/w/20260810-c89ambiguity.html
60•runningmike•4d ago•24 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?