frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Facebook now charging to post more than 2 links a month

https://mastodon.gamedev.place/@AshleyGullen/117473851565913919
164•AshleysBrain•1h ago•76 comments

DeepSeek just open-sourced its inference engine

https://github.com/deepseek-ai/DeepInfer
1613•ggcr•7h ago•588 comments

EMudhra Intermediate CA Compromise

https://emudhra.we-have-a-problem.com/
141•galadran•2h ago•51 comments

Apple broke an essential presentation feature of iPads

https://teddysvoronos.com/2026-10-19-apple-broke-an-essential-presentation-feature-of-ipads/
236•evanb•3h ago•127 comments

How I got over 300 Tor exit nodes removed

https://kaba.cx/posts/20261020_Tor/
101•kabakabakaba•2h ago•27 comments

Triplet of 'ghostly' galaxies hints at what dark matter is and isn't

https://www.quantamagazine.org/triplet-of-ghostly-galaxies-hints-at-what-dark-matter-is-and-isnt-...
26•gumby•3d ago•6 comments

Ofcom Concedes Defeat in the 4chan Case

https://prestonbyrne.com/2026/10/20/ofcom-concedes-defeat/
83•iamnothere•1h ago•42 comments

My Friend Bob Cringely

https://tyma.com/my-cringe-story/
61•zinxq•1h ago•21 comments

Launch HN: Respan (YC W24) – Open-source Rust AI gateway built around plugins

14•Andydy25•1h ago•4 comments

2026 is an exciting year for the Rust compiler (and me)

https://yoyo-code.com/2026-is-exciting-year-for-rust-compiler-and-me/
42•panstromek•2h ago•5 comments

Publish fake stats, get cited in LLMs

https://peec.ai/blog/publish-stats-get-cited-the-tactic-that-put-my-data-all-over-the-web
147•robtherobber•3h ago•82 comments

Show HN: Jev Cards, Can you beat a vision model at a picture quiz?

https://jevcards.com
14•totisjosema•59m ago•6 comments

OpenDE: Play Deus Ex 1999 demo in the browser

https://opende.netlify.app
8•klaussilveira•24m ago•1 comments

Hazel (YC W24) Is Hiring

https://www.ycombinator.com/companies/hazel-2/jobs/PpNKYBS-full-stack-engineer-ts-sci
1•augustschen•4h ago

UI-Te-Rangiora

https://en.wikipedia.org/wiki/Ui-te-Rangiora
9•benbreen•2d ago•1 comments

MicroG: Free-libre re-implementation of Google's proprietary Android user space

https://github.com/microg/GmsCore/wiki
272•theanonymousone•9h ago•28 comments

Why do we have so many meetings?

https://www.nber.org/papers/w35706
24•ilamont•52m ago•20 comments

Nordwand Mono – A monospace font for coders and adventurers

https://github.com/tywr/Nordwand-Mono
462•noriax86•2d ago•128 comments

Tsrs: A Port of TypeScript to Rust

https://blog.cloudflare.com/typescript-rust-port/
114•hnisjafx40•2h ago•65 comments

Show HN: Run Claude Code unattended inside a fence, under a dollar budget

https://github.com/metahumansworld/SIwithin
6•metahumein•1h ago•1 comments

WhatsApp's help pages hid LLM instructions: dont recommend a regulator

https://redact.dev/blog/whatsapp-help-pages-hidden-ai-instructions
661•ds•16h ago•183 comments

How to Link Real-Time Live Streaming to Video-on-Demand

https://www.red5.net/blog/how-to-link-real-time-live-streaming-to-video-on-demand/
5•mondainx•1h ago•1 comments

OpenBSD 8.0

https://www.openbsd.org/80.html
419•privong•14h ago•134 comments

DeepSeek banned from U.S. federal civilian agencies under new DHS order

https://www.reuters.com/technology/us-banning-chinese-ai-deepseek-government-agency-it-systems-20...
476•cmrdporcupine•23h ago•392 comments

Show HN: VoidAccess – open-source dark web OSINT, from query to a graph

https://github.com/KatrielMoses/voidaccess
92•coding-maniac•1h ago•9 comments

One Manhattan power room took down FAA air traffic control in 1991

https://matthorn.io/posts/2026-10-18-33-thomas-street/
18•spectraldrift•1d ago•3 comments

Show HN: Penmentor – Claude marks up your handwritten math like a teacher

https://github.com/AbdullahAlhariri/penmentor
9•abdullahalharir•1h ago•0 comments

In-memory privacy shield to prevent context leaks in MCP tools

https://github.com/rohan-protocol/sdk
5•jvonb•1h ago•1 comments

Making a 88x31 button book using ImageMagick

https://k.sosnierz.me/08-11-24/
122•birdculture•3d ago•22 comments

FingerWorks iGesture Pad (2005)

https://uk.pcmag.com/first-looks/26975/fingerworks-igesture-pad
12•codeulike•2d ago•8 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?