frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Resizing windows on macOS Tahoe – the saga continues

https://noheger.at/blog/2026/02/12/resizing-windows-on-macos-tahoe-the-saga-continues/
504•erickhill•9h ago•222 comments

MinIO repository is no longer maintained

https://github.com/minio/minio/commit/7aac2a2c5b7c882e68c1ce017d8256be2feea27f
26•psvmcc•1h ago•3 comments

MMAcevedo aka Lena by qntm

https://qntm.org/mmacevedo
59•stickynotememo•3h ago•29 comments

GPT‑5.3‑Codex‑Spark

https://openai.com/index/introducing-gpt-5-3-codex-spark/
714•meetpateltech•14h ago•294 comments

Gemini 3 Deep Think

https://blog.google/innovation-and-ai/models-and-research/gemini-models/gemini-3-deep-think/
832•tosh•15h ago•532 comments

Skip the Tips: A game to select "No Tip" but dark patterns try to stop you

https://skipthe.tips/
295•randycupertino•7h ago•184 comments

Ring owners are returning their cameras

https://www.msn.com/en-us/lifestyle/shopping/ring-owners-are-returning-their-cameras-here-s-how-m...
85•c420•2h ago•58 comments

An AI agent published a hit piece on me

https://theshamblog.com/an-ai-agent-published-a-hit-piece-on-me/
1761•scottshambaugh•16h ago•711 comments

AWS Adds support for nested virtualization

https://github.com/aws/aws-sdk-go-v2/commit/3dca5e45d5ad05460b93410087833cbaa624754e
189•sitole•8h ago•67 comments

Asimov (YC W26) Is Hiring

1•lningthou•1h ago

Tell HN: Ralph Giles has died (Xiph.org| Rust@Mozilla | Ghostscript)

184•ffworld•9h ago•6 comments

We interfaced single-threaded C++ with multi-threaded Rust

https://antithesis.com/blog/2026/rust_cpp/
14•lukastyrychtr•5d ago•1 comments

Polis: Open-source platform for large-scale civic deliberation

https://pol.is/home2
244•mefengl•14h ago•87 comments

My Grandma Was a Fed – Lessons from Digitizing Hours of Childhood

https://sampatt.com/blog/2025-12-13-my-grandma-was-a-fed-lessons-from-digitizing-hundreds-of-hour...
126•SamPatt•4d ago•36 comments

Improving 15 LLMs at Coding in One Afternoon. Only the Harness Changed

http://blog.can.ac/2026/02/12/the-harness-problem/
660•kachapopopow•19h ago•251 comments

Ruby Newbie Is Joining the Ruby Users Forum

https://www.rubyforum.org/tag/getting-started
8•jvrc•3d ago•1 comments

Ring cancels its partnership with Flock Safety after surveillance backlash

https://www.theverge.com/news/878447/ring-flock-partnership-canceled
388•c420•9h ago•205 comments

Beginning fully autonomous operations with the 6th-generation Waymo driver

https://waymo.com/blog/2026/02/ro-on-6th-gen-waymo-driver
204•ra7•16h ago•217 comments

Japan's Dododo Land, the most irritating place on Earth

https://soranews24.com/2026/02/07/take-a-trip-to-japans-dododo-land-the-most-irritating-place-on-...
60•zdw•5d ago•15 comments

Major European payment processor can't send email to Google Workspace users

https://atha.io/blog/2026-02-12-viva
508•thatha7777•18h ago•351 comments

Recoverable and Irrecoverable Decisions

https://herbertlui.net/recoverable-and-irrecoverable-decisions/
61•herbertl•9h ago•18 comments

Launch HN: Omnara (YC S25) – Run Claude Code and Codex from anywhere

115•kmansm27•15h ago•136 comments

Apache Arrow is 10 years old

https://arrow.apache.org/blog/2026/02/12/arrow-anniversary/
216•tosh•19h ago•61 comments

Evaluating Multilingual, Context-Aware Guardrails: A Humanitarian LLM Use Case

https://blog.mozilla.ai/evaluating-multilingual-context-aware-guardrails-evidence-from-a-humanita...
16•benbreen•10h ago•0 comments

The Nature of the Beast

https://cinemasojourns.com/2026/02/07/the-nature-of-the-beast/
6•jjgreen•4d ago•0 comments

Show HN: Sol LeWitt-style instruction-based drawings in the browser

https://intervolz.com/sollewitt/
53•intervolz•2d ago•9 comments

Synthesizer Cartridge for the Atari 2600

https://www.qotile.net/synth.html
24•harel•4d ago•5 comments

Mapping the Moon: The Apollo Transforming Printer

https://blogs.loc.gov/maps/2025/12/mapping-the-moon-the-apollo-transforming-printer/
13•bryanrasmussen•3d ago•2 comments

How to Have a Bad Career – David Patterson (2016) [video]

https://www.youtube.com/watch?v=Rn1w4MRHIhc
79•rombr•13h ago•23 comments

The "Crown of Nobles" Noble Gas Tube Display (2024)

https://theshamblog.com/the-crown-of-nobles-noble-gas-tube-display/
133•Ivoah•20h ago•31 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?