frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Just the Browser

https://justthebrowser.com/
202•cl3misch•2h ago•83 comments

Michelangelo's First Painting, Created When He Was Only 12 or 13 Years Old

https://www.openculture.com/2026/01/discover-michelangelos-first-painting.html
23•bookofjoe•49m ago•19 comments

Show HN: I built a text-based business simulator to replace video courses

https://www.core-mba.pro/
41•Core_Dev•12h ago•17 comments

Show HN: The Analog I – Inducing Recursive Self-Modeling in LLMs [pdf]

https://github.com/philMarcus/Birth-of-a-Mind
11•Phil_BoaM•53m ago•3 comments

OpenBSD-current now runs as guest under Apple Hypervisor

https://www.undeadly.org/cgi?action=article;sid=20260115203619
320•gpi•11h ago•34 comments

List of individual trees

https://en.wikipedia.org/wiki/List_of_individual_trees
223•wilson090•14h ago•84 comments

Training my smartwatch to track intelligence

https://dmvaldman.github.io/rooklift/
33•dmvaldman•1d ago•18 comments

Interactive eBPF

https://ebpf.party/
95•samuel246•6h ago•5 comments

Dev-Owned Testing: Why It Fails in Practice and Succeeds in Theory

https://dl.acm.org/doi/10.1145/3780063.3780066
5•rbanffy•54m ago•4 comments

The spectrum of isolation: From bare metal to WebAssembly

https://buildsoftwaresystems.com/post/guide-to-execution-environments/
59•ThierryBuilds•5h ago•19 comments

Apple is fighting for TSMC capacity as Nvidia takes center stage

https://www.culpium.com/p/exclusiveapple-is-fighting-for-tsmc
722•speckx•23h ago•437 comments

Pocket TTS: A high quality TTS that gives your CPU a voice

https://kyutai.org/blog/2026-01-13-pocket-tts
516•pain_perdu•1d ago•120 comments

psc: The ps utility, with an eBPF twist and container context

https://github.com/loresuso/psc
6•tanelpoder•1h ago•1 comments

Cue Does It All, but Can It Literate?

https://xlii.space/cue/cue-does-it-all-but-can-it-literate/
41•xlii•4d ago•11 comments

Briar keeps Iran connected via Bluetooth and Wi-Fi when the internet goes dark

https://briarproject.org/manual/fa/
444•us321•18h ago•261 comments

Show HN: pgwire-replication - pure rust client for Postgres CDC

https://github.com/vnvo/pgwire-replication
17•sacs0ni•5d ago•6 comments

Inside The Internet Archive's Infrastructure

https://hackernoon.com/the-long-now-of-the-web-inside-the-internet-archives-fight-against-forgetting
385•dvrp•2d ago•94 comments

Bringing the Predators to Life in MAME

https://lysiwyg.mataroa.blog/blog/bringing-the-predators-to-life-in-mame/
41•msephton•2d ago•7 comments

pf: Make af-to less magical

https://undeadly.org/cgi?action=article;sid=20260116085115
32•defrost•5h ago•2 comments

Song banned from Swedish charts for being AI creation

https://www.bbc.com/news/articles/cp829jey9z7o
15•breve•1h ago•11 comments

Linux boxes via SSH: suspended when disconected

https://shellbox.dev/
247•messh•18h ago•136 comments

Ask HN: How can we solve the loneliness epidemic?

646•publicdebates•21h ago•1021 comments

Altaid 8800 (2024)

https://sunrise-ev.com/8080.htm
14•exvi•4d ago•2 comments

Claude is good at assembling blocks, but still falls apart at creating them

https://www.approachwithalacrity.com/claude-ne/
278•bblcla•1d ago•202 comments

Show HN: Hc: an agentless, multi-tenant shell history sink

https://github.com/alessandrocarminati/hc
12•acarminati•6h ago•2 comments

My Gripes with Prolog

https://buttondown.com/hillelwayne/archive/my-gripes-with-prolog/
122•azhenley•14h ago•68 comments

Prime chains

https://www.johndcook.com/blog/2026/01/10/prime-chains/
29•ibobev•4d ago•8 comments

Data is the only moat

https://frontierai.substack.com/p/data-is-your-only-moat
180•cgwu•19h ago•40 comments

Show HN: OpenWork – An open-source alternative to Claude Cowork

https://github.com/different-ai/openwork
204•ben_talent•2d ago•44 comments

JuiceFS is a distributed POSIX file system built on top of Redis and S3

https://github.com/juicedata/juicefs
166•tosh•19h ago•96 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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