frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

East Germany balloon escape

https://en.wikipedia.org/wiki/East_Germany_balloon_escape
353•robertvc•10h ago•118 comments

Cloudflare acquires Astro

https://astro.build/blog/joining-cloudflare/
743•todotask2•13h ago•334 comments

FLUX.2 [Klein]: Towards Interactive Visual Intelligence

https://bfl.ai/blog/flux2-klein-towards-interactive-visual-intelligence
53•GaggiX•3h ago•9 comments

LLM Structured Outputs Handbook

https://nanonets.com/cookbooks/structured-llm-outputs
150•vitaelabitur•1d ago•26 comments

6-Day and IP Address Certificates Are Generally Available

https://letsencrypt.org/2026/01/15/6day-and-ip-general-availability
359•jaas•11h ago•210 comments

Cursor's latest “browser experiment” implied success without evidence

https://embedding-shapes.github.io/cursor-implied-success-without-evidence/
434•embedding-shape•12h ago•182 comments

Michelangelo's first painting, created when he was 12 or 13

https://www.openculture.com/2026/01/discover-michelangelos-first-painting.html
319•bookofjoe•13h ago•162 comments

Releasing rainbow tables to accelerate Net-NTLMv1 protocol deprecation

https://cloud.google.com/blog/topics/threat-intelligence/net-ntlmv1-deprecation-rainbow-tables
91•linolevan•5h ago•56 comments

High-Level Is the Goal

https://bvisness.me/high-level/
26•tobr•1d ago•5 comments

Just the Browser

https://justthebrowser.com/
511•cl3misch•15h ago•241 comments

Dell UltraSharp 52 Thunderbolt Hub Monitor

https://www.dell.com/en-us/shop/dell-ultrasharp-52-thunderbolt-hub-monitor-u5226kw/apd/210-bthw/m...
159•cebert•10h ago•214 comments

Lock-Picking Robot

https://github.com/etinaude/Lock-Picking-Robot
272•p44v9n•4d ago•123 comments

Patching the Wii News Channel to serve local news (2025)

https://raulnegron.me/2025/wii-news-pr/
63•todsacerdoti•14h ago•16 comments

STFU

https://github.com/Pankajtanwarbanna/stfu
693•tanelpoder•9h ago•449 comments

Reading across books with Claude Code

https://pieterma.es/syntopic-reading-claude/
72•gmays•8h ago•22 comments

Keifu – A TUI for navigating commit graphs with color and clarity

https://github.com/trasta298/keifu
15•indigodaddy•2h ago•2 comments

Why DuckDB is my first choice for data processing

https://www.robinlinacre.com/recommend_duckdb/
229•tosh•16h ago•85 comments

Elasticsearch was never a database

https://www.paradedb.com/blog/elasticsearch-was-never-a-database
113•jamesgresql•5d ago•82 comments

Install.md: A standard for LLM-executable installation

https://www.mintlify.com/blog/install-md-standard-for-llm-executable-installation
43•npmipg•5h ago•62 comments

HTTP RateLimit Headers

https://dotat.at/@/2026-01-13-http-ratelimit.html
35•zdw•2d ago•11 comments

Experts Warn of Growing Parrot Crisis in Canada

https://www.ctvnews.ca/ottawa/video/2026/01/06/experts-warn-of-growing-parrot-crisis-in-canada/
17•debo_•4d ago•2 comments

Emoji Use in the Electronic Health Record is Increasing

https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2843883
59•giuliomagnifico•9h ago•55 comments

Justice Dept. launches criminal investigation of Minnesota governor

https://www.washingtonpost.com/national-security/2026/01/16/trump-minnesota-walz-frey-criminal-in...
31•perihelions•1h ago•4 comments

Launch HN: Indy (YC S21) – A support app designed for ADHD brains

https://www.shimmer.care/indy-redirect
69•christalwang•11h ago•75 comments

Slop is everywhere for those with eyes to see

https://www.fromjason.xyz/p/notebook/slop-is-everywhere-for-those-with-eyes-to-see/
220•speckx•7h ago•109 comments

Dev-owned testing: Why it fails in practice and succeeds in theory

https://dl.acm.org/doi/10.1145/3780063.3780066
115•rbanffy•13h ago•143 comments

Zep AI (Agent Context Engineering, YC W24) Is Hiring Forward Deployed Engineers

https://www.ycombinator.com/companies/zep-ai/jobs/
1•roseway4•10h ago

Re: Mix: open-source repairable blender

https://github.com/openfunkHQ/reMix
15•rishikeshs•4h ago•6 comments

Read_once(), Write_once(), but Not for Rust

https://lwn.net/SubscriberLink/1053142/8ec93e58d5d3cc06/
116•todsacerdoti•12h ago•34 comments

psc: The ps utility, with an eBPF twist and container context

https://github.com/loresuso/psc
87•tanelpoder•14h ago•27 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?