frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Pre-Release of Polars 2.0

https://pola.rs/posts/announcing-polars-2/
190•komape•4h ago•36 comments

The Browser's Main Thread Is Expensive

https://kciter.so/posts/the-expensive-main-thread/en/
111•kciter•1d ago•34 comments

Muse Spark 1.3

https://developer.meta.com/ai/models/muse-spark/
598•bvaldivielso•15h ago•395 comments

Gemini 3.8 Flash and 3.8 Flash Cyber

https://blog.google/innovation-and-ai/models-and-research/gemini-models/3-8-flash-and-3-8-flash-c...
1044•bratao•20h ago•581 comments

Fish Bad, Sugar Good and Other Medieval Ideas About Food

https://lithub.com/fish-bad-sugar-good-and-other-medieval-ideas-about-food/
15•mooreds•2d ago•1 comments

What I Learned from My Mom (1941-2026)

https://experimentalliving.substack.com/p/what-i-learned-from-my-mom-1941-2026
30•NaOH•4d ago•2 comments

Three schoolgirls in Kinsale pulled up a pea plant covered in warts (2016)

https://scienceblog.com/b-three-schoolgirls-in-kinsale-pulled-up-a-pea-plant-covered-in-warts-and...
70•DamonHD•4h ago•22 comments

Google avoids a breakup of its ad tech business

https://www.nytimes.com/2026/09/02/technology/google-ad-tech-remedies.html
405•donohoe•20h ago•284 comments

Three sites made 215,128 “best software” pages for AI. Perplexity cites them

https://trellner.com/reports/manufactured-sources-behind-ai-recommendations/
436•jakobgreenfeld•21h ago•213 comments

The Computer Museum of America reclamation project

https://computer-museum.org/wp/
52•rbanffy•2d ago•22 comments

Holden's Lightning Flight

https://en.wikipedia.org/wiki/Holden%27s_Lightning_flight
167•ColinWright•2d ago•35 comments

Can I opt out of my input or output data being used for training?

https://help.mistral.ai/en/articles/455207-can-i-opt-out-of-my-input-or-output-data-being-used-fo...
454•teekert•22h ago•207 comments

Fable 5.1 World Modeling

https://github.com/PhiloLabs/fable51-worlds
271•surreal_•15h ago•79 comments

Reverse Engineering Unknown File Formats with ImHex

https://werwolv.net/posts/file_format_reverse_engineering/
213•carlos-menezes•2d ago•38 comments

Higher Multipoles of the Cow

https://arxiv.org/abs/2504.00506
81•MrOrelliOReilly•2d ago•24 comments

Launch HN: RonanRX (YC S26) – Personalized Peptides and GLP-1s

67•lloydarmbrust•12h ago•71 comments

Biggest dark matter detector spots a single weird particle

https://www.science.org/content/article/world-s-biggest-dark-matter-detector-spots-single-weird-p...
306•randycupertino•21h ago•105 comments

Aging brains blend memories together instead of just forgetting them

https://studyfinds.com/aging-brains-blend-memories-together-instead-of-forgetting-them-study-finds/
295•mdp2021•22h ago•119 comments

Wendell Berry has died

https://www.nytimes.com/2026/08/31/us/wendell-berry-dead.html
195•Curiositry•2d ago•99 comments

Qantas Airbus A380 engine failure in 2010 (2023)

https://admiralcloudberg.medium.com/a-matter-of-millimeters-the-story-of-qantas-flight-32-bdaa62d...
148•gumby•16h ago•89 comments

Engineering of the fastest WebAssembly interpreters

https://wasmi-labs.github.io/blog/posts/wasmi-v2.0/
103•herobird•1d ago•8 comments

Exit the Cave

https://turtlespace.blog/p/exit-the-cave
271•akkartik•20h ago•96 comments

Japan halves speed limit to 30km/h on all narrow city streets

https://www.theguardian.com/world/2026/sep/02/japan-new-speed-limit-30kmh-narrow-city-streets
54•haunter•1h ago•48 comments

A Selection of Los Alamos Rolodex Business Cards

https://clui.org/collections/los-alamos-business-cards/selection-cards
175•1970-01-01•2d ago•49 comments

Async Rust vs RTOS showdown (2022)

https://tweedegolf.nl/en/blog/65/async-rust-vs-rtos-showdown/
98•kooi•16h ago•48 comments

We could save petabytes of cache storage with Zstandard and Pingora

https://blog.cloudflare.com/cache-transcoding/
118•torutofu•1d ago•52 comments

Altair Basic Interpreter Source Code (1975) [pdf]

https://images.gatesnotes.com/12514eb8-7b51-008e-41a9-512542cf683b/34d561c8-cf5c-4e69-af47-3782ea...
64•Eridanus2•15h ago•35 comments

Poisson Disk Sampling

https://stripeacross.com/posts/poisson-disk-sampling/
170•vismit2000•21h ago•21 comments

WebLLM: high-performance in-browser LLM inference engine

https://github.com/mlc-ai/web-llm
127•saikatsg•21h ago•21 comments

Quasar 438B: Europe's Leading AI Model

https://multiversecomputing.com/resources/introducing-quasar-438b-europe-s-leading-ai-model
183•amunozo•1d ago•117 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?