frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Terminal Phone – E2EE Walkie Talkie from the Command Line

https://gitlab.com/here_forawhile/terminalphone
63•smalltorch•1h ago•16 comments

Google API keys weren't secrets, but then Gemini changed the rules

https://trufflesecurity.com/blog/google-api-keys-werent-secrets-but-then-gemini-changed-the-rules
785•hiisthisthingon•16h ago•158 comments

You Want to Visit the UK? You Better Have a Google Play or App Store Account

https://www.heltweg.org/posts/you-want-to-visit-the-uk-you-better-have-a-google-play-or-app-store...
98•rhazn•1h ago•116 comments

Jimi Hendrix was a systems engineer

https://spectrum.ieee.org/jimi-hendrix-systems-engineer
527•tintinnabula•16h ago•164 comments

Tell HN: YC companies scrape GitHub activity, send spam emails to users

95•miki123211•2h ago•32 comments

The Physics and Economics of Moving 44 Tonnes at 56mph

https://www.mikeayles.com/blog/heavy-haulage-basics/
11•mikeayles•2d ago•2 comments

Hightouch (YC S19) Is Hiring

https://hightouch.com/careers#open-positions
1•joshwget•25m ago

How will OpenAI compete?

https://www.ben-evans.com/benedictevans/2026/2/19/how-will-openai-compete-nkg2x
287•iamskeole•13h ago•385 comments

Banned in California

https://www.bannedincalifornia.org/
200•pie_flavor•13h ago•225 comments

First Website (1992)

https://info.cern.ch
240•shrikaranhanda•13h ago•68 comments

Making MCP cheaper via CLI

https://kanyilmaz.me/2026/02/23/cli-vs-mcp.html
243•thellimist•15h ago•98 comments

Windows 11 Notepad to support Markdown

https://blogs.windows.com/windows-insider/2026/01/21/notepad-and-paint-updates-begin-rolling-out-...
302•andreynering•19h ago•452 comments

Artist who “paints” portraits on glass by hitting it with a hammer

https://simonbergerart.com
189•cs702•3d ago•82 comments

Men in their 50s may be aging faster due to toxic 'forever chemicals'

https://www.cnn.com/2026/02/26/health/forever-chemicals-aging-men-wellness
14•jb1991•29m ago•2 comments

Bus stop balancing is fast, cheap, and effective

https://worksinprogress.co/issue/the-united-states-needs-fewer-bus-stops/
372•surprisetalk•19h ago•540 comments

Large-Scale Online Deanonymization with LLMs

https://simonlermen.substack.com/p/large-scale-online-deanonymization
287•DalasNoin•1d ago•204 comments

RAM now represents 35 percent of bill of materials for HP PCs

https://arstechnica.com/gadgets/2026/02/ram-now-represents-35-percent-of-bill-of-materials-for-hp...
294•jnord•9h ago•224 comments

Out of Light Adjust Share: Caravaggio, La Tour, and the Art of Attention

https://harpers.org/archive/2026/03/out-of-light-nicole-krauss-caravaggio-georges-de-la-tour/
22•prismatic•3d ago•1 comments

Show HN: Respectify – A comment moderator that teaches people to argue better

https://respectify.org/
181•vintagedave•22h ago•166 comments

The First Fully General Computer Action Model

https://si.inc/posts/fdm1/
264•nee1r•2d ago•69 comments

A 26-Gram Butterfly-Inspired Robot Achieving Autonomous Tailless Flight

https://arxiv.org/abs/2602.06811
15•Terretta•3d ago•3 comments

Show HN: Modern Reimplementation of the Speck Molecule Renderer

https://github.com/vangelov/modern-speck
7•vlad_angelov•4d ago•0 comments

Tech companies shouldn't be bullied into doing surveillance

https://www.eff.org/deeplinks/2026/02/tech-companies-shouldnt-be-bullied-doing-surveillance
317•pseudolus•11h ago•104 comments

Writers and Their Day Jobs

https://lithub.com/the-work-behind-the-writing-on-writers-and-their-day-jobs/
39•simplegeek•4d ago•11 comments

The Om Programming Language

https://www.om-language.com/
276•tosh•18h ago•77 comments

Technical Excellence Is Not Enough

https://raccoon.land/posts/technical-excellence-is-not-enough/
4•bo0tzz•2h ago•0 comments

Dissecting the CPU-memory relationship in garbage collection (OpenJDK 26)

https://norlinder.nu/posts/GC-Cost-CPU-vs-Memory/
100•jonasn•1d ago•27 comments

What Pressure Does to an Athlete's Body

https://www.theatlantic.com/culture/2026/02/pressure-olympics-malinin-shiffrin/686097/
41•bookofjoe•4d ago•9 comments

An autopsy of AI-generated 3D slop

https://aircada.com/blog/ai-vs-human-3d-ecommerce
84•sech8420•15h ago•48 comments

GNU Texmacs

https://www.texmacs.org/tmweb/home/welcome.en.html
175•remywang•20h ago•48 comments
Open in hackernews

A kernel developer plays with Home Assistant

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

Comments

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

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

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