frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

A programming language based on grammatical cases of Turkish

https://github.com/kip-dili/kip
95•nhatcher•3h ago•24 comments

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

https://alexharri.com/blog/ascii-rendering
784•alexharri•13h ago•96 comments

Light Mode InFFFFFFlation

https://willhbr.net/2025/10/20/light-mode-infffffflation/
121•Fudgel•2h ago•70 comments

We put Claude Code in Rollercoaster Tycoon

https://labs.ramp.com/rct
345•iamwil•5d ago•192 comments

Show HN: ChunkHound, a local-first tool for understanding large codebases

https://github.com/chunkhound/chunkhound
33•NadavBenItzhak•3h ago•3 comments

Xous Operating System

https://xous.dev/
44•eustoria•3d ago•14 comments

The Olivetti Company

https://www.abortretry.fail/p/the-olivetti-company
124•rbanffy•6d ago•20 comments

The recurring dream of replacing developers

https://www.caimito.net/en/blog/2025/12/07/the-recurring-dream-of-replacing-developers.html
248•glimshe•9h ago•211 comments

An Elizabethan mansion's secrets for staying warm

https://www.bbc.com/future/article/20260116-an-elizabethan-mansions-secrets-for-staying-warm
101•Tachyooon•7h ago•121 comments

Below the Surface: Archeological Finds from the Amsterdam Noord/Zuid Metro Line

https://belowthesurface.amsterdam/en/vondsten
48•stefanvdw1•6d ago•6 comments

OpenAI could reportedly run out of cash by mid-2027

https://www.tomshardware.com/tech-industry/big-tech/openai-could-reportedly-run-out-of-cash-by-mi...
15•thenaturalist•32m ago•0 comments

Raising money fucked me up

https://blog.yakkomajuri.com/blog/raising-money-fucked-me-up
73•yakkomajuri•5h ago•27 comments

The thing that brought me joy

https://www.stephenlewis.me/blog/the-thing-that-brought-me-joy/
50•monooso•5h ago•20 comments

M8SBC-486 (Homebrew 486 computer)

https://maniek86.xyz/projects/m8sbc_486.php
79•rasz•6d ago•8 comments

Congress Wants to Hand Your Parenting to Big Tech

https://www.eff.org/deeplinks/2026/01/congress-wants-hand-your-parenting-big-tech
67•hn_acker•2h ago•39 comments

Counterfactual evaluation for recommendation systems

https://eugeneyan.com/writing/counterfactual-evaluation/
56•kurinikku•19h ago•4 comments

Show HN: I built a game on my old phone without knowing what I was building

https://www.kikkupico.com/posts/vibe-discovery/
10•kikkupico•2d ago•6 comments

There's no single best way to store information

https://www.quantamagazine.org/why-theres-no-single-best-way-to-store-information-20260116/
68•7777777phil•8h ago•42 comments

East Germany balloon escape

https://en.wikipedia.org/wiki/East_Germany_balloon_escape
680•robertvc•1d ago•282 comments

Common misunderstandings about large software companies

https://philipotoole.com/common-misunderstandings-about-large-software-companies/
57•otoolep•5d ago•28 comments

What are Tithe Maps (2021)

https://mapreading.co.uk/what-are-tithe-maps/
5•thomasjb•5d ago•0 comments

Docker.how – Docker command cheat sheet

https://docker.how/
33•anagogistis•4h ago•10 comments

ClickHouse acquires Langfuse

https://langfuse.com/blog/joining-clickhouse
193•tin7in•15h ago•85 comments

Map To Poster – Create Art of your favourite city

https://github.com/originalankur/maptoposter
216•originalankur•14h ago•53 comments

The Dilbert Afterlife

https://www.astralcodexten.com/p/the-dilbert-afterlife
428•rendall•1d ago•284 comments

Reducing Dependabot Noise

https://nesbitt.io/2026/01/10/16-best-practices-for-reducing-dependabot-noise.html
53•zdw•5d ago•30 comments

Show HN: Streaming gigabyte medical images from S3 without downloading them

https://github.com/PABannier/WSIStreamer
133•el_pa_b•15h ago•43 comments

6-Day and IP Address Certificates Are Generally Available

https://letsencrypt.org/2026/01/15/6day-and-ip-general-availability
481•jaas•1d ago•269 comments

Show HN: I built a tool to assist AI agents to know when a PR is good to go

https://dsifry.github.io/goodtogo/
33•dsifry•14h ago•27 comments

High-Level Is the Goal

https://bvisness.me/high-level/
234•tobr•2d ago•120 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?