frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Baidu released ERNIE 5.5 Flash Base

https://ernie.baidu.com/release/ernie-5-5-flash-base/
57•pretext•2h ago•33 comments

Residential proxies detected on White House network

https://layer3intel.com/blog/residential-proxies-white-house-network
1106•Rasbora•15h ago•360 comments

Lemmings CSS Animation

https://markblah.github.io/lemmings/
224•MarkBlah•7h ago•48 comments

Awesome repositories are no longer awesome

https://erikgahner.github.io/posts/2026/awesome-repositories-are-no-longer-awesome/
25•erikgahner•44m ago•10 comments

A thousand fewer paths to root

https://openai.com/index/a-thousand-fewer-paths-to-root/
377•dangelosaurus•12h ago•273 comments

Images 2.6

https://openai.com/index/introducing-images-2-6/
322•davidbarker•12h ago•192 comments

Replacing homepage demo media with looping HTML and CSS

https://stepshots.com/css-feature-clips
14•hauju•1d ago•8 comments

Partial Operator Precedence

https://ziglang.org/devlog/2026/#2026-10-24
60•tosh•2d ago•31 comments

Kimi K3.1 Pro model weights are out

https://huggingface.co/moonshotai/Kimi-K3.1-Pro
551•abrarthought•20h ago•155 comments

Ripple-65B Preview: U.S. Open-Weight SOTA on Agentic Coding

https://www.ricursive.com/ripple
305•Philpax•17h ago•109 comments

Altera Announces Agilex 2X, a Complete FPGA and SoC Portfolio

https://www.altera.com/newsroom/agilex-2x
40•gmays•6h ago•13 comments

TextEdit vs. Pages

https://leancrew.com/all-this/2026/10/textedit-vs-pages/
29•surprisetalk•1d ago•7 comments

A new Go API for JSON

https://go.dev/blog/jsonv2
331•olexsmir•18h ago•164 comments

Moment of Ruby: An Argument for Nothing

https://www.aha.io/engineering/articles/moment-of-ruby-an-argument-for-nothing
27•zemptime•2d ago•2 comments

Insects don't swarm at LED lights

https://www.birdsoutsidemywindow.org/2026/11/03/insects-dont-swarm-at-led-lights/
274•speckx•16h ago•133 comments

Spreading Liquid with Three.js

https://mofu-dev.com/en/blog/fluid-foundation/
124•mooreds•2d ago•19 comments

Being a kid making games in the early 2000s

https://jaytholen.net/teengamedev/
26•farmerbb•6h ago•4 comments

OpenSSH 10.6p2 has been released with a workaround for a critical vulnerability

https://hachyderm.io/@damienmiller/117563026759098135
39•Animux•2h ago•11 comments

Conductor is joining Meta

https://www.conductor.build/announcement
184•kenrose•17h ago•201 comments

Ask HN: What's your current AI agentic setup?

363•eggbrain•21h ago•413 comments

Hacking the Xbox 360 Hypervisor Part 3: Bad Update Improvements

https://icode4.coffee/?p=1746
121•muricula•13h ago•12 comments

Future Maintenance of Mbed TLS

https://lists.trustedfirmware.org/archives/list/mbed-tls@lists.trustedfirmware.org/thread/YPIGCB7...
54•jonesjohnson•2d ago•15 comments

AI is forcing us to pay off 40 years of technical debt

https://spectrum.ieee.org/ai-in-cybersecurity-php2shell-vulnerability
1207•pseudolus•1d ago•706 comments

Qualcomm Cloud AI 100 Ultra – 150W AI Accelerator Card with 128GB at 548GB/s

https://www.qualcomm.com/data-center/products/cloud-ai-100-ultra
159•peter_d_sherman•16h ago•60 comments

Show HN: After a decade of reversing, I got co-op working in DOS Wing Commander

https://fireflyk64.github.io/wcmulti/
206•daniel_rh•17h ago•30 comments

Progress on provable inference for large language models

https://www.anthropic.com/research/provable-inference
227•ltononro•18h ago•114 comments

Guerrilla bike lanes: San Francisco makes illicit infrastructure permanent (2016)

https://99percentinvisible.org/article/guerrilla-bike-lanes-san-francisco-makes-illicit-infrastru...
313•zenincognito•20h ago•243 comments

Launch HN: Kino AI (YC S23) – AI media manager and video editor

90•lukeigel•18h ago•34 comments

OpenAI to acquire Pierre Computer Company

https://openai.com/index/openai-to-acquire-pierre/
248•itunpredictable•20h ago•76 comments

A wave of plastic-free coffee pods and machines

https://www.cnn.com/2026/11/02/food/coffee-machine-plastic-free
113•thunderbong•20h ago•132 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?