frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Inverse Parentheses

https://kellett.im/a/inverse-parentheses
16•mighty-fine•49m ago•16 comments

A guide to local coding models

https://www.aiforswes.com/p/you-dont-need-to-spend-100mo-on-claude
407•mpweiher•12h ago•201 comments

Deliberate Internet Shutdowns

https://www.schneier.com/blog/archives/2025/12/deliberate-internet-shutdowns.html
174•WaitWaitWha•3d ago•58 comments

Build Android apps using Rust and Iced

https://github.com/ibaryshnikov/android-iced-example
76•rekireki•7h ago•14 comments

Webb observes exoplanet that may have an exotic helium and carbon atmosphere

https://science.nasa.gov/missions/webb/nasas-webb-observes-exoplanet-whose-composition-defies-exp...
55•taubek•2d ago•11 comments

I'm just having fun

https://jyn.dev/i-m-just-having-fun/
337•lemper•5d ago•115 comments

Show HN: Books mentioned on Hacker News in 2025

https://hackernews-readings-613604506318.us-west1.run.app
441•seinvak•16h ago•160 comments

Disney Imagineering Debuts Next-Generation Robotic Character, Olaf

https://disneyparksblog.com/disney-experiences/robotic-olaf-marks-new-era-of-disney-innovation/
187•ChrisArchitect•11h ago•74 comments

How I protect my Forgejo instance from AI web crawlers

https://her.esy.fun/posts/0031-how-i-protect-my-forgejo-instance-from-ai-web-crawlers/index.html
20•todsacerdoti•18h ago•6 comments

Kernighan's Lever

https://linusakesson.net/programming/kernighans-lever/index.php
54•xk3•2d ago•16 comments

Programming languages used for music

https://timthompson.com/plum/cgi/showlist.cgi?sort=name&concise=yes
13•ofalkaed•1d ago•2 comments

I announced my divorce on Instagram and then AI impersonated me

https://eiratansey.com/2025/12/20/i-announced-my-divorce-on-instagram-and-then-ai-impersonated-me/
7•robin_reala•2h ago•2 comments

Aliasing

https://xania.org/202512/15-aliasing-in-general
27•ibobev•5d ago•2 comments

Functional Flocking Quadtree in ClojureScript

https://www.lbjgruppen.com/en/posts/flocking-quadtrees
34•lbj•5d ago•2 comments

ONNX Runtime and CoreML May Silently Convert Your Model to FP16

https://ym2132.github.io/ONNX_MLProgram_NN_exploration
67•Two_hands•8h ago•12 comments

Making the most of bit arrays in Gleam

https://gearsco.de/blog/bit-array-syntax/
20•crowdhailer•3d ago•1 comments

CO2 batteries that store grid energy take off globally

https://spectrum.ieee.org/co2-battery-energy-storage
235•rbanffy•17h ago•192 comments

More on whether useful quantum computing is “imminent”

https://scottaaronson.blog/?p=9425
85•A_D_E_P_T•12h ago•59 comments

Lightning: Real-time editing for tiled map data

https://felt.com/blog/lightning-tiles
8•hinting•5d ago•1 comments

QBasic64 Phoenix 4.3.0 Released

https://qb64phoenix.com/forum/showthread.php?tid=4244
23•jandeboevrie•1h ago•4 comments

Single-Pass Huffman Coding

https://doisinkidney.com/posts/2018-02-17-single-pass-huffman.html
18•todsacerdoti•6d ago•0 comments

Show HN: Rust/WASM lighting data toolkit – parses legacy formats, generates SVGs

https://eulumdat.icu
23•holg•12h ago•0 comments

Rue: Higher level than Rust, lower level than Go

https://rue-lang.dev/
129•ingve•12h ago•98 comments

Cursed circuits #3: true mathematics

https://lcamtuf.substack.com/p/cursed-circuits-3-true-mathematics
17•zdw•4h ago•2 comments

Show HN: WalletWallet – create Apple passes from anything

https://walletwallet.alen.ro/
372•alentodorov•17h ago•102 comments

I program on the subway

https://www.scd31.com/posts/programming-on-the-subway
219•evankhoury•5d ago•147 comments

Evaluating chain-of-thought monitorability

https://openai.com/index/evaluating-chain-of-thought-monitorability/
52•mfiguiere•3d ago•18 comments

The Going Dark initiative or ProtectEU is a Chat Control 3.0 attempt

https://mastodon.online/@mullvadnet/115742530333573065
550•janandonly•14h ago•186 comments

Exploring Speculative JIT Compilation for Emacs Lisp with Java

https://kyo.iroiro.party/en/posts/juicemacs-exploring-jit-for-elisp/
27•gudzpoz•2d ago•1 comments

The gift card accountability sink

https://www.bitsaboutmoney.com/archive/gift-card-accountability-sink/
90•walterbell•12h ago•73 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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