frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Jepsen: NATS 2.12.1

https://jepsen.io/analyses/nats-2.12.1
150•aphyr•2h ago•43 comments

Strong earthquake hits northern Japan, tsunami warning issued

https://www3.nhk.or.jp/nhkworld/en/news/20251209_02/
203•lattis•6h ago•103 comments

AMD GPU Debugger

https://thegeeko.me/blog/amd-gpu-debugging/
164•ibobev•5h ago•24 comments

Let's put Tailscale on a jailbroken Kindle

https://tailscale.com/blog/tailscale-jailbroken-kindle
154•Quizzical4230•4h ago•39 comments

Hunting for North Korean Fiber Optic Cables

https://nkinternet.com/2025/12/08/hunting-for-north-korean-fiber-optic-cables/
160•Bezod•4h ago•17 comments

Deep dive on Nvidia circular funding

https://philippeoger.com/pages/deep-dive-into-nvidias-virtuous-cycle
182•jeanloolz•2h ago•110 comments

IBM to acquire Confluent

https://www.confluent.io/blog/ibm-to-acquire-confluent/
279•abd12•7h ago•228 comments

Launch HN: Nia (YC S25) – Give better context to coding agents

https://www.trynia.ai/
67•jellyotsiro•4h ago•55 comments

AI should only run as fast as we can catch up

https://higashi.blog/2025/12/07/ai-verification/
63•yuedongze•3h ago•68 comments

A series of tricks and techniques I learned doing tiny GLSL demos

https://blog.pkh.me/p/48-a-series-of-tricks-and-techniques-i-learned-doing-tiny-glsl-demos.html
91•ibobev•4h ago•5 comments

Microsoft Download Center Archive

https://legacyupdate.net/download-center/
72•luu•3d ago•6 comments

We collected 10k hours of neuro-language data in our basement

https://condu.it/thought/10k-hours
53•nee1r•3h ago•41 comments

Microsoft increases Office 365 and Microsoft 365 license prices

https://office365itpros.com/2025/12/08/microsoft-365-pricing-increase/
162•taubek•7h ago•198 comments

Word spacing

https://en.wikipedia.org/wiki/Word_spacing
24•doener•3d ago•16 comments

Legion Health (YC S21) is hiring a founding engineer (SF, in-person)

1•the_danny_g•4h ago

Show HN: DuckDB for Kafka Stream Processing

https://sql-flow.com/docs/tutorials/intro/
38•dm03514•4h ago•12 comments

Flow: Actor-based language for C++, used by FoundationDB

https://github.com/apple/foundationdb/tree/main/flow
146•SchwKatze•8h ago•39 comments

Paramount launches hostile bid for Warner Bros

https://www.cnbc.com/2025/12/08/paramount-skydance-hostile-bid-wbd-netflix.html
151•gniting•7h ago•128 comments

Trials avoid high risk patients and underestimate drug harms

https://www.nber.org/papers/w34534
13•bikenaga•2h ago•3 comments

GitHub no longer uses Toasts

https://primer.style/accessibility/toasts/
23•samsolomon•1h ago•7 comments

No more O'Reilly subscriptions for me

https://zerokspot.com/weblog/2025/12/05/no-more-oreilly-subscriptions-for-me/
73•speckx•5h ago•74 comments

GitHub Actions has a package manager, and it might be the worst

https://nesbitt.io/2025/12/06/github-actions-package-manager.html
335•robin_reala•13h ago•208 comments

Quanta to publish popular math and physics books by Terence Tao and David Tong

https://www.simonsfoundation.org/2025/12/08/quanta-books-to-publish-popular-math-and-physics-titl...
84•digital55•3h ago•20 comments

Google confirms Android attacks; no fix for most Samsung users

https://www.forbes.com/sites/zakdoffman/2025/12/08/google-confirms-android-attacks-no-fix-for-mos...
112•mohi-kalantari•4h ago•92 comments

Alignment is capability

https://www.off-policy.com/alignment-is-capability/
88•drctnlly_crrct•8h ago•77 comments

Wayland Nvidia

https://kextcache.com/wayland-nvidia-a-definite-2025-guide/
41•breve•4d ago•67 comments

Cancer is surging, bringing a debate about whether to look for it

https://www.nytimes.com/2025/12/08/health/cancer-young-people-deaths.html
33•brandonb•1h ago•16 comments

Uber is turning data about trips and takeout into insights for marketers

https://www.businessinsider.com/uber-ads-launches-intelligence-insights-trips-takeout-data-market...
216•sethops1•6h ago•197 comments

Colors of Growth

https://papers.ssrn.com/sol3/papers.cfm?abstract_id=5804462
47•mhb•8h ago•16 comments

Show HN: Persistent memory for Claude Code sessions

https://github.com/TonyStef/Grov
12•tonyystef•6d ago•5 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•6mo ago

Comments

balloob•6mo 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•6mo ago
Discussion for the other article in the series:

https://news.ycombinator.com/item?id=44011381

tomhow•6mo ago
Comments moved thither. Thanks!
pabs3•6mo ago
They are two different articles, I don't think that was correct.
tomhow•6mo 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•6mo ago
Thanks for the response, guess that makes sense.
pabs3•6mo 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?