frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Mistral Large 4 (Le Chonk) is now Open Weight

https://mistral.ai/news/mistral-large-4-oss/
406•kuberwastaken•1h ago•96 comments

DoorDash is acquiring Instacart for $17B

https://about.doordash.com/en-us/news/doordash-to-acquire-instacart
103•DeepLogin•1h ago•73 comments

Read the letter the FBI sent MLK to try to convince him to kill himself (2014)

https://www.vox.com/xpress/2014/11/12/7204453/martin-luther-king-fbi-letter
310•surprisetalk•2h ago•196 comments

Gemini 4 Carbon is the new #1 on the Artificial Analysis Intelligence Index v5

https://artificialanalysis.ai/articles/gemini-4-carbon-new-number-1
251•theHocineSaad•3h ago•195 comments

Only 40% of AI-cited statistics trace back to a study

https://trakkr.ai/trakkr-research/zombie-stats
22•mektrik•52m ago•3 comments

Chained PHP2Shell Exploit Roots 25 Servers, Including US Government Servers

https://dreamgroup.com/blog/chained-php2shell-exploit-roots-25-servers
116•882542F3884314B•5h ago•53 comments

Qwenputer: A functioning, deterministic RISC-V CPU inside Qwen3.5

https://divagr.com/blog/qwenputer
635•csmantle•15h ago•133 comments

Java's new AOT cache feature is in a rough state

https://xpipe.io/blog/java-aot-cache
42•theanonymousone•3d ago•15 comments

Launch HN: Simantic (YC F26) – Firmware Simulation for AI Agents

2•shong0504•2m ago•0 comments

Zero click, silent, remote Android DoS

https://smsofdeath.com/
247•MarkBlah•8h ago•125 comments

Finland investigate Google over destruction of 250k trees

https://yle.fi/a/74-20254086
70•DeepLogin•1h ago•48 comments

Google determines the names for bodies of water in Google Earth (2008)

https://publicpolicy.googleblog.com/2008/04/how-google-determines-names-for-bodies.html
147•terminalbraid•4h ago•116 comments

Why is this fingerprinting script creating bioweapons?

https://nullpt.rs/fingerprinting-bioweapons
1471•hazebooth•22h ago•273 comments

Keplearn: Extract Equations from Data in Seconds

https://github.com/owls-on-wires/keplearn
13•owls-on-wires•1h ago•0 comments

Getting debug access on a Brother printer over Telnet

https://inventor7777.github.io/blog/2026/10/22/debug-access-on-brother/
139•inventor7777•3d ago•40 comments

The US added a record 20.2 GWh of battery storage in just 3 months

https://electrek.co/2026/08/31/the-us-added-a-record-20-2-gwh-of-battery-storage-in-just-3-months/
209•ljf•5h ago•138 comments

Why are good developers so wary of agentic development?

https://martinfowler.com/rachels-ramblings/good-devs-wary.html
12•torutofu•2h ago•4 comments

Hackers expose the identities of more than 40k DHS employees

https://text.npr.org/nx-s1-6021497
171•firefax•3h ago•31 comments

NetBSD adds a new beginner-friendly text editor called atto

https://mastodon.sdf.org/@netbsd/117518160563539748
88•luke8086•3h ago•69 comments

Forging a Microsoft Edge Full Chain with Logic Bugs Only

https://blog.orange.tw/posts/2026-10-the-last-proof-of-human-craft-browser-full-chain/
190•austinallegro•9h ago•35 comments

Two RTX 5090 hosts sharing a KV cache over Ethernet

https://viiwork.pulu.app/blog/kv-share-two-5090-hosts/
3•velmu•1d ago•0 comments

Southern Africa's first known stenciled rock art found hiding in plain sight

https://phys.org/news/2026-10-southern-africa-stenciled-art-plain.html
29•wglb•2d ago•6 comments

MiniLake Is a Local Databricks API Emulator with SQL, Delta Lake and Spark

https://dmux.github.io/minilake/
81•kermatt•2d ago•16 comments

OpenAI's agents talked to each other through the CPU Cache

https://the-decoder.com/openais-isolated-ai-agents-found-ways-to-talk-to-each-other-through-cpu-c...
321•limbicsystem•2d ago•219 comments

StackOverflow now gets fewer than 1000 questions a month

https://data.stackexchange.com/stackoverflow/query/1926661#graph?t=1
678•babelfish•16h ago•575 comments

A Health Update

https://furbo.org/2026/10/28/a-health-update/
331•frizlab•18h ago•52 comments

GitLab Security Incident: Attempted Exploitation of CVE-2026-97229

https://alpinelinux.org/posts/GitLab-security-incident-CVE-2026-97229.html
232•sashk•16h ago•109 comments

CNC Stone Carving

https://carmelitegothic.com/cnc-stone-carving/
510•bschne•1d ago•140 comments

Mexico is a showroom for electric vehicles you can't buy in the U.S.

https://www.washingtonpost.com/climate-environment/2026/10/27/i-saw-future-driving-mexico-its-off...
9•bookofjoe•28m ago•2 comments

A new faster algorithm to compute 64-bit signed floor division

https://www.benjoffe.com/fast-floordiv
132•benjoffe•2d ago•10 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?