frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Gaussian Splatting – A$AP Rocky "Helicopter" music video

https://radiancefields.com/a-ap-rocky-releases-helicopter-music-video-featuring-gaussian-splatting
459•ChrisArchitect•8h ago•155 comments

Flux 2 Klein pure C inference

https://github.com/antirez/flux2.c
228•antirez•8h ago•97 comments

A Social Filesystem

https://overreacted.io/a-social-filesystem/
288•icy•18h ago•139 comments

Fil-Qt: A Qt Base build with Fil-C experience

https://git.qt.io/cradam/fil-qt
26•pjmlp•2d ago•8 comments

Using proxies to hide secrets from Claude Code

https://www.joinformal.com/blog/using-proxies-to-hide-secrets-from-claude-code/
26•drewgregory•5d ago•4 comments

Wine 11.0

https://gitlab.winehq.org/wine/wine/-/releases/wine-11.0
235•zdw•4d ago•44 comments

Police Invested Millions in Shadowy Phone-Tracking Software Won't Say How Used

https://www.texasobserver.org/texas-police-invest-tangles-sheriff-surveillance/
230•nobody9999•5h ago•70 comments

Gas Town Decoded

https://www.alilleybrinker.com/mini/gas-town-decoded/
52•alilleybrinker•4d ago•48 comments

Dead Internet Theory

https://kudmitry.com/articles/dead-internet-theory/
79•skwee357•6h ago•93 comments

Sins of the Children

https://asteriskmag.com/issues/07/sins-of-the-children
112•maxall4•9h ago•55 comments

Command-line Tools can be 235x Faster than your Hadoop Cluster (2014)

https://adamdrake.com/command-line-tools-can-be-235x-faster-than-your-hadoop-cluster.html
309•tosh•17h ago•212 comments

Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss

https://getdock.io/
53•yadavrh•5h ago•45 comments

Show HN: Lume 0.2 – Build and Run macOS VMs with unattended setup

https://cua.ai/docs/lume/guide/getting-started/introduction
91•frabonacci•8h ago•23 comments

Poking holes into bytecode with peephole optimisations

https://xnacly.me/posts/2026/purple-garden-first-optimisations/
5•xnacly•4d ago•0 comments

The Cathedral, the Megachurch, and the Bazaar

https://opensourcesecurity.io/2026/01-cathedral-megachurch-bazaar/
129•todsacerdoti•5d ago•113 comments

Breaking the Zimmermann Telegram (2018)

https://medium.com/lapsed-historian/breaking-the-zimmermann-telegram-b34ed1d73614
70•tony-allan•7h ago•4 comments

Predicting OpenAI's ad strategy

https://ossa-ma.github.io/blog/openads
485•calcifer•11h ago•414 comments

Stirling Cycle Machine Analysis

https://ohioopen.library.ohio.edu/opentextbooks/9/
24•akshatjiwan•5h ago•9 comments

A free and open-source rootkit for Linux

https://lwn.net/SubscriberLink/1053099/19c2e8180aeb0438/
166•jwilk•16h ago•35 comments

Cardputer uLisp Machine (2024)

http://www.ulisp.com/show?52G4
34•tosh•3d ago•3 comments

Show HN: Beats, a web-based drum machine

https://beats.lasagna.pizza
38•kinduff•5h ago•11 comments

Prediction: Microsoft will eventually ship a Windows-themed Linux distro

https://gamesbymason.com/blog/2026/microsoft/
66•AndyKelley•2h ago•71 comments

Prediction markets are ushering in a world in which news becomes about gambling

https://www.msn.com/en-us/money/markets/america-is-slow-walking-into-a-polymarket-disaster/ar-AA1...
159•krustyburger•8h ago•167 comments

Overlapping Markup

https://en.wikipedia.org/wiki/Overlapping_markup
57•ripe•15h ago•10 comments

More sustainable epoxy thanks to phosphorus

https://www.empa.ch/web/s604/flamm-hemmendes-epoxidharz-nachhaltiger-machen
79•JeanKage•4d ago•35 comments

ASCII characters are not pixels: a deep dive into ASCII rendering

https://alexharri.com/blog/ascii-rendering
1189•alexharri•1d ago•130 comments

ThinkNext Design

https://thinknextdesign.com/home.html
237•__patchbit__•19h ago•113 comments

Show HN: Xenia – A monospaced font built with a custom Python engine

https://github.com/Loretta1982/xenia
57•xeniafont•15h ago•20 comments

jQuery 4

https://blog.jquery.com/2026/01/17/jquery-4-0-0/
729•OuterVale•21h ago•241 comments

Starting from scratch: Training a 30M Topological Transformer

https://www.tuned.org.uk/posts/013_the_topological_transformer_training_tauformer
123•tuned•14h ago•35 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?