frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Mistral Large 4

https://docs.mistral.ai/models/mistral-large-4-0
304•Philpax•46m ago•130 comments

Mistral Large 4: "Le Chonk"

https://mistral.ai/news/mistral-large-4/
81•j-bu•35m ago•9 comments

Release of Polars 2.0

https://pola.rs/posts/release-polars-2/
108•simicd•2h ago•17 comments

Nobel Prize in Physics goes to Francis Halzen

https://www.nobelprize.org/prizes/physics/2026/
243•solarist•4h ago•75 comments

Tapo (Rust/Python library) now speaks TP-Link's TPAP protocol

https://mihai.dinculescu.dev/posts/tapo-speaks-tpap/
6•faithraven•6m ago•0 comments

JetBrains reported a net financial loss first time in its tracked history

https://www.helgilibrary.com/companies/jetbrains
212•thw_9a83c•2h ago•232 comments

Mathematics of Geothermal Energy

https://www.ebsco.com/research-starters/power-and-energy/mathematics-geothermal-energy/
9•srameshc•56m ago•2 comments

Gleam doesn't compile to Erlang source anymore

https://gleam.run/news/gleam-doesnt-compile-to-erlang-source-anymore/
119•ingve•5h ago•36 comments

Meta's Muse Is an Adorable Privacy and Security Dumpster Fire

https://www.techdirt.com/2026/10/06/metas-muse-is-an-adorable-privacy-and-security-dumpster-fire/
67•beardyw•1h ago•17 comments

Show HN: Jotbus – a shared encrypted scratchpad for coding agents

https://jotbus.com/
4•shake-n-fries•16m ago•1 comments

Show HN: Parseable, an open observability datalake, handles 100M time-series/min

https://www.parseable.com
4•yashdotrv•30m ago•0 comments

Nature's capacity to 'bounce back' when species are lost is vastly overestimated

https://phys.org/news/2026-10-nature-capacity-species-lost-vastly.html
92•pseudolus•2h ago•33 comments

Beam: Reflection's 501B open-weight model

https://reflection.ai/blog/introducing-beam
486•Philpax•18h ago•158 comments

Find the flattest route between any two points in SF

https://flattensf.com/
244•ishan0102•16h ago•84 comments

World's First enhanced geothermal power plant completed in just 23 months

https://techcrunch.com/2026/10/01/worlds-first-enhanced-geothermal-power-plant-completed-in-just-...
53•hochmartinez•2h ago•9 comments

Dust: Pretraining Transformers Without Backpropagation

https://qlabs.sh/research/dust
236•E-Reverance•16h ago•62 comments

Friendship ended with Deno, now Node is my best friend

https://dbushell.com/2026/10/03/deno-to-node/
234•ibobev•15h ago•149 comments

Accountability mechanisms can be joyful (2024)

https://liquidbrain.net/blog/accountability-and-joy/
60•luu•2d ago•19 comments

Opus 5.5 agents discover two room-temperature magnetic semiconductor candidates

https://www.vals.ai/blogs/room-temperature-magnetic-semiconductors
408•outlier99•17h ago•274 comments

Web Search API

https://developers.cloudflare.com/changelog/post/2026-10-02-introducing-web-search-api/
571•tosh•1d ago•266 comments

Two ARM64-specific compiler optimization bugs, in GCC 15/16 and Rust, hit curl

https://mastodon.social/@bagder/117392573268225646
8•torutofu•55m ago•1 comments

Oracle Triggered the Implosion of the AI Bubble

https://medium.com/predict/what-everyone-had-been-waiting-for-and-fearing-oracle-just-triggered-t...
8•mpweiher•18m ago•4 comments

Resurrecting iChat Audio and Video Conferencing

https://blog.pipetogrep.org/2026/09/11/resurrecting-ichat-audio-and-video-conferencing/
78•thepipetogrep•10h ago•16 comments

Competitive Programmer's Handbook (2018) [pdf]

https://cses.fi/book/book.pdf
246•vinhnx•3d ago•59 comments

ASOS app users receive push notifications apparently sent by hackers

https://www.bbc.co.uk/news/articles/cj62ylzpr6d3o
51•helsinkiandrew•3h ago•30 comments

Testing 12 different Zigbee temperature/humidity sensors

https://smarthomescene.com/reviews/best-selling-zigbee-temperature-sensors-tested/
154•walrus01•2d ago•88 comments

Example.com just launched the biggest redesign in decades

https://www.debugbear.com/blog/example-dot-com-redesign-history
270•jgx0•15h ago•181 comments

Direct retinal projection display for smart glasses using a meta-optic mirror

https://www.tdk.com/en/news_center/press/20261002_01.html
58•bookofjoe•2d ago•21 comments

Using A.I. and machine learning to decode communication of sperm whales

https://blue-continuum.com/the-man-who-listens-to-whales
54•dnetesn•2d ago•38 comments

Screens Aren't Destroying Young Minds. I Should Know

https://humanprogress.org/screens-arent-destroying-young-minds-i-should-know/
3•obscurette•10m ago•0 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?