frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

England set to be one of the first countries to eliminate hepatitis C

https://www.bbc.com/news/articles/c75gk620r22o
59•stevekemp•1h ago•28 comments

France to ban unsolicited telemarketing calls

https://www.lemonde.fr/en/france/article/2026/08/06/france-to-ban-unsolicited-telemarketing-calls...
561•aziaziazi•5h ago•312 comments

As AI eats the web, the internet’s collective memory is disappearing

https://thewalrus.ca/google-search-is-dying/
495•awnird•15h ago•569 comments

H3-metal – Native MiniMax-H3 inference for Apple Silicon

https://github.com/antirez/h3.c
347•swyx•12h ago•76 comments

It's time Amazon played by the same rules as everyone else [video]

https://www.youtube.com/watch?v=91DoiansHqk
56•whosgotch•46m ago•19 comments

How to organize Claude Code for product work

https://www.theaithinker.com/p/how-to-organize-claude-code-for-product
21•adamfaik•2h ago•6 comments

Nvidia's Risky Business

https://stratechery.com/2026/nvidias-risky-business/
35•jonbaer•3h ago•2 comments

Immersion lithography saved Moore's Law (2023)

https://www.asml.com/en/company/stories/2023/how-immersion-lithography-saved-moores-law
12•wsgeorge•4d ago•0 comments

More than 10 firms pay up to $100k a month for access to Truth Social posts

https://www.bbc.com/news/articles/ce3q5nxpgk1o
135•whosgotch•3h ago•122 comments

Chicken Scheme 6.0

https://code.call-cc.org/releases/6.0.0/NEWS
236•eatonphil•13h ago•32 comments

Show HN: Needle2: 14MB agentic LLM for phones, wearables, smart home and robots

https://cactuscompute.com/needle
408•HenryNdubuaku•20h ago•150 comments

Mark Zuckerberg attacks 'closed' AI rivals as Meta returns to open models

https://www.ft.com/content/4e3957f8-ea7c-4c46-a3de-cdce8e526878
554•root-parent•23h ago•517 comments

LFM2.5 2.6B model competitive with 4x larger models

https://huggingface.co/LiquidAI/LFM2.5-2.6B
104•nateb2022•6d ago•30 comments

Show HN: Scroll through all 43252003274489856000 Rubik's Cube states

https://everycube.alen.is/
237•Alen123•14h ago•79 comments

Closing Canario Terminal source code

https://rapha.land/closing-canario-terminal-source-code/
26•atan2•5h ago•31 comments

The “mechanical miracle” that ruined Mark Twain’s life

https://resobscura.substack.com/p/the-mechanical-miracle-that-ruined
163•benbreen•5d ago•85 comments

How Claude marks AI-generated content

https://support.claude.com/en/articles/16266773-how-claude-marks-ai-generated-content
263•mfiguiere•16h ago•227 comments

What I learned by putting GitHub Copilot behind a MitM proxy

https://www.lighthousenewsletter.com/p/i-put-github-copilot-behind-a-mitm
14•j0selit0•3h ago•2 comments

Stowaway – Take the window seat on any plane or satellite overhead

https://stowaway.live/
327•thunderbong•4d ago•40 comments

Recycle – Floppydisks

https://www.floppydisk.com/recycle
84•calvinmorrison•11h ago•35 comments

Sonic Pi v5

https://www.patreon.com/samaaron/posts/sonic-pi-v5-166001392
398•samaaron•4d ago•95 comments

Faster floating point math with Rust's new API

https://pythonspeed.com/articles/faster-float-math-rust/
64•subset•5d ago•16 comments

To Save C, We Must Save ABI (2022)

https://thephd.dev/to-save-c-we-must-save-abi-fixing-c-function-abi
93•gurjeet•3d ago•89 comments

The UK's war on anonymity has come to America

https://www.effort.news/uk-lobby
563•slowin•14h ago•592 comments

Rust SIMD on the GPU

https://www.vectorware.com/blog/simd-on-gpu/
200•sagacity•19h ago•96 comments

Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

https://research.meta.ai/blog/introducing-muse-glimmer-open-agentic-model
1139•riordan•1d ago•614 comments

Hollywood and Shanghai Cinema in the 1930s [pdf]

https://docs.lib.purdue.edu/cgi/viewcontent.cgi?article=2225&context=clcweb
6•Bluestein•5d ago•0 comments

Confessions of a Long-Distance Sailor

https://arachnoid.com/lutusp/sailbook.html
139•AntiRush•16h ago•44 comments

Tail-call optimization in C is relatively recent (2025)

https://lwn.net/Articles/1034703/
155•prakashqwerty•1d ago•136 comments

Squeak 6.1

https://squeak.org/release_notes/6.1/
275•fniephaus•1d ago•134 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?