frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

MiniMax M3.1 Flash

https://www.minimax.io/blog/minimax-m31f
216•jtg•3h ago•81 comments

Wine ported to OpenBSD

https://marc.info/?l=openbsd-ports&m=179236125692175
402•iamnothere•6h ago•124 comments

Android apps running native on macOS

https://github.com/kksimp/Mac.apk
134•flocked•3h ago•41 comments

I built a drone with only one motor [video]

https://www.youtube.com/watch?v=Ndftcft6XhU
79•hakonjdjohnsen•10h ago•8 comments

It's still ok to enjoy programming

https://chriskiehl.com/article/it-is-still-ok-to-enjoy-programming
263•goostavos•1d ago•252 comments

The reverts will continue until morale improves

http://peter.eisentraut.org/blog/2026/10/09/the-reverts-will-continue-until-morale-improves
24•hans_castorp•1h ago•1 comments

RuneScape Bench: MMOs for Agents [video]

https://www.youtube.com/watch?v=cNm4zyUtWj0
73•evakhoury•1d ago•28 comments

The obscure trust looming over Anthropic's IPO

https://www.wsj.com/tech/ai/anthropic-ipo-private-trust-188f41f7?st=RtdGHg&reflink=desktopwebshar...
85•1vuio0pswjnm7•7h ago•35 comments

The fire retardant in the seafood chain

https://insideclimatenews.org/news/14102026/ethoxyquin-fire-retardant-in-seafood-chain/
36•gumby•2d ago•9 comments

Timestral: Mistral's time-series foundation models

https://mistral.ai/news/timestral/
456•groar•9h ago•85 comments

Evidence (YC S21) Is Hiring Software Engineers

https://evidence.dev/jobs
1•hughess•2h ago

Credit where credit is due

https://thefloatingcontinent.com/blog/credit-is-due/
18•evakhoury•3d ago•3 comments

Mercury 3: Diffusion at scale

https://www.inceptionlabs.ai/blog/introducing-mercury-3
152•cmrdporcupine•2h ago•63 comments

Alternatives to animal testing are finally taking off

https://spectrum.ieee.org/alternatives-to-animal-testing
254•rbanffy•8h ago•78 comments

Galois Finite Fields and the Advanced Encryption Standard (AES)

https://www.cs.uaf.edu/2015/spring/cs463/lecture/03_23_AES.html
54•ankitg12•2d ago•2 comments

Starcraft: Ashfall

https://starcraft-shooter-2026.pages.dev/
122•debo_•18h ago•40 comments

Launch HN: Laminar (YC S24) – We trained a model to catch silent agent failures

31•skull8888888•3h ago•13 comments

Towards Company World Models

https://www.beaconholdings.com/research/towards-company-world-models
9•rafaelc•1h ago•0 comments

Let's Encrypt is adding two additional remote perspectives for domain validation

https://community.letsencrypt.org/t/lets-encrypt-is-adding-two-additional-remote-perspectives-for...
213•gslin•8h ago•68 comments

Maxwell: A new kind of model that sits between code and hardware

https://heymaxwell.ai/
26•laginimaineb•6h ago•10 comments

Plex vulnerabilities being exploited in the wild to drop a cryptominer

http://www.boredhackerblog.info/2026/10/plex-vulnerabilities-being-exploited-in.html
89•mindracer•6h ago•30 comments

The Annotated VT100 Firmware (2022)

https://vt100.net/dec/vt100/rom/
35•Aleksandr_NFA•17h ago•2 comments

Ask HN: How to deal with shipping AI-written code you don't understand?

62•rzk•8h ago•89 comments

Cairn: Open windows into AI-driven cyber operations

https://norforge.com/blog/inside_cairn
17•ragu4u•6h ago•6 comments

Show HN: Open-source early-reading reader with phonics help

https://github.com/finereli/yarareads
13•zoozla•1h ago•1 comments

Integer to String Conversion (2014)

https://tia.mat.br/posts/2014/06/23/integer_to_string_conversion.html
8•jstrieb•20h ago•0 comments

CERN and Mistral sign a statement of intent to establish a strategic partnership

https://home.cern/cern-and-mistral-join-forces-to-accelerate-ai-for-science/
241•kensai•4h ago•44 comments

I no longer care to work on any Ruby gems so I've archived all my repositories

https://po-ru.com/2026/10/18/why-im-no-longer-updating-this-repository
265•phoronixrly•3h ago•234 comments

Chicago O'Hare digs up 50-ton boulder under airfield, asks public for name ideas

https://simpleflying.com/chicago-ohare-digs-up-50-ton-boulder-public-names/
39•Stratoscope•17h ago•40 comments

Pentulive (Puppy Live) [video]

https://yle.fi/t/18-332106/fi
18•NaOH•3h ago•1 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?