frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Ghostty's AI Policy

https://github.com/ghostty-org/ghostty/blob/main/AI_POLICY.md
249•mefengl•3h ago•121 comments

What has Docker become?

https://tuananh.net/2026/01/20/what-has-docker-become/
40•tuananh•1h ago•20 comments

I built a light that reacts to radio waves [video]

https://www.youtube.com/watch?v=moBCOEiqiPs
259•codetheweb•8h ago•58 comments

AI is a horse (2024)

https://kconner.com/2024/08/02/ai-is-a-horse.html
110•zdw•3d ago•58 comments

Microsoft Mishandling Example.com

https://tinyapps.org/blog/microsoft-mishandling-example-com.html
6•mrled•38m ago•0 comments

Replacing Protobuf with Rust to go 5 times faster

https://pgdog.dev/blog/replace-protobuf-with-rust
76•whiteros_e•4h ago•50 comments

Booting a PC from a Vinyl Record

https://boginjr.com/it/sw/dev/vinyl-boot/
38•yesturi•3h ago•8 comments

Show HN: isometric.nyc – giant isometric pixel art map of NYC

https://cannoneyed.com/isometric-nyc/
1046•cannoneyed•20h ago•197 comments

GPTZero finds 100 new hallucinations in NeurIPS 2025 accepted papers

https://gptzero.me/news/neurips/
875•segmenta•22h ago•467 comments

The State of Modern AI Text to Speech Systems for Screen Reader Users

https://stuff.interfree.ca/2026/01/05/ai-tts-for-screenreaders.html
30•tuukkao•4h ago•6 comments

Show HN: S2-lite, an open source Stream Store

https://github.com/s2-streamstore/s2
15•shikhar•1d ago•0 comments

Capital One to acquire Brex for $5.15B

https://www.reuters.com/legal/transactional/capital-one-buy-fintech-firm-brex-515-billion-deal-20...
320•personjerry•16h ago•263 comments

Presence in Death

https://rubinmuseum.org/presence-in-death/
12•tock•1h ago•0 comments

Proton Spam and the AI Consent Problem

https://dbushell.com/2026/01/22/proton-spam/
257•dbushell•6h ago•154 comments

Why I Don't Have Fun With Claude Code

https://brennan.io/2026/01/23/claude-code/
28•ingve•3h ago•16 comments

Why does SSH send 100 packets per keystroke?

https://eieio.games/blog/ssh-sends-100-packets-per-keystroke/
532•eieio•18h ago•283 comments

I was banned from Claude for scaffolding a Claude.md file?

https://hugodaniel.com/posts/claude-code-banned-me/
595•hugodan•19h ago•533 comments

Variation on Iota

https://www.toolofthought.com/posts/variation-on-iota
6•aebtebeten•4d ago•1 comments

Show HN: Whosthere: A LAN discovery tool with a modern TUI, written in Go

https://github.com/ramonvermeulen/whosthere
7•rvermeulen98•1h ago•2 comments

Qwen3-TTS family is now open sourced: Voice design, clone, and generation

https://qwen.ai/blog?id=qwen3tts-0115
638•Palmik•23h ago•202 comments

TI-99/4A: Leaning More on the Firmware

https://bumbershootsoft.wordpress.com/2026/01/17/ti-99-4a-leaning-more-heavily-on-the-firmware/
50•ibobev•4d ago•21 comments

Douglas Adams on the English–American cultural divide over "heroes"

https://shreevatsa.net/post/douglas-adams-cultural-divide/
478•speckx•23h ago•481 comments

Your app subscription is now my weekend project

https://rselbach.com/your-sub-is-now-my-weekend-project
415•robteix•4d ago•301 comments

Scaling PostgreSQL to power 800M ChatGPT users

https://openai.com/index/scaling-postgresql/
227•mustaphah•16h ago•101 comments

Bugs Apple Loves

https://www.bugsappleloves.com
768•nhod•11h ago•335 comments

Our collective obsession with boredom: Interview with a boredom lab researcher

https://nautil.us/why-the-do-nothing-challenge-doesnt-do-much-for-you-1262005/
12•akakievich•3d ago•5 comments

Improving the usability of C libraries in Swift

https://www.swift.org/blog/improving-usability-of-c-libraries-in-swift/
127•timsneath•14h ago•22 comments

'Askers' vs. 'Guessers' (2010)

https://www.theatlantic.com/national/2010/05/askers-vs-guessers/340891/
171•BoorishBears•1d ago•119 comments

Writing First, Tooling Second

https://susam.net/writing-first-tooling-second.html
47•blenderob•4d ago•6 comments

Show HN: Txt2plotter – True centerline vectors from Flux.2 for pen plotters

https://github.com/malvarezcastillo/txt2plotter
29•tsanummy•3d ago•7 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?