frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Anthropic's original take home assignment open sourced

https://github.com/anthropics/original_performance_takehome
212•myahio•4h ago•88 comments

cURL removes bug bounties

https://etn.se/index.php/nyheter/72808-curl-removes-bug-bounties.html
109•jnord•1h ago•32 comments

Libbbf: Bound Book Format, A high-performance container for comics and manga

https://github.com/ef1500/libbbf
39•zdw•3h ago•15 comments

A 26,000-year astronomical monument hidden in plain sight (2019)

https://longnow.org/ideas/the-26000-year-astronomical-monument-hidden-in-plain-sight/
450•mkmk•13h ago•90 comments

Instabridge has acquired Nova Launcher

https://novalauncher.com/nova-is-here-to-stay
186•KORraN•12h ago•121 comments

Are arrays functions?

https://futhark-lang.org/blog/2026-01-16-are-arrays-functions.html
110•todsacerdoti•2d ago•74 comments

The Agentic AI Handbook: Production-Ready Patterns

https://www.nibzard.com/agentic-handbook
9•SouravInsights•58m ago•2 comments

Infracost (YC W21) Is Hiring Sr Back End Eng (Node.js+SQL) to Shift FinOps Left

https://www.ycombinator.com/companies/infracost/jobs/Sr9rmHs-senior-backend-engineer-node-js-sql
1•akh•47m ago

Which AI Lies Best? A game theory classic designed by John Nash

https://so-long-sucker.vercel.app/
112•lout332•9h ago•50 comments

200 MB RAM FreeBSD Desktop

https://vermaden.wordpress.com/2026/01/18/200-mb-ram-freebsd-desktop/
9•vermaden•2d ago•0 comments

Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs

https://github.com/mastra-ai/mastra
149•calcsam•15h ago•49 comments

California is free of drought for the first time in 25 years

https://www.latimes.com/california/story/2026-01-09/california-has-no-areas-of-dryness-first-time...
354•thnaks•9h ago•175 comments

The GDB JIT Interface

https://bernsteinbear.com/blog/gdb-jit/
25•surprisetalk•4d ago•3 comments

The Unix Pipe Card Game

https://punkx.org/unix-pipe-game/
212•kykeonaut•14h ago•66 comments

IPv6 is not insecure because it lacks a NAT

https://www.johnmaguire.me/blog/ipv6-is-not-insecure-because-it-lacks-nat/
136•johnmaguire•12h ago•204 comments

Unconventional PostgreSQL Optimizations

https://hakibenita.com/postgresql-unconventional-optimizations
331•haki•17h ago•50 comments

The challenges of soft delete

https://atlas9.dev/blog/soft-delete.html
131•buchanae•10h ago•78 comments

Our approach to age prediction

https://openai.com/index/our-approach-to-age-prediction/
93•pretext•12h ago•161 comments

Show HN: Agent Skills Leaderboard

https://skills.sh
75•andrewqu•10h ago•30 comments

Lunar Radio Telescope to Unlock Cosmic Mysteries

https://spectrum.ieee.org/lunar-radio-telescope
36•rbanffy•9h ago•2 comments

Provably unmasking malicious behavior through execution traces

https://arxiv.org/abs/2512.13821
37•PaulHoule•9h ago•5 comments

Building Robust Helm Charts

https://www.willmunn.xyz/devops/helm/kubernetes/2026/01/17/building-robust-helm-charts.html
58•will_munn•1d ago•2 comments

Disaster planning for regular folks (2015)

https://lcamtuf.coredump.cx/prep/index-old.shtml
101•AlphaWeaver•4h ago•60 comments

Maintenance: Of Everything, Part One

https://press.stripe.com/maintenance-part-one
102•mitchbob•12h ago•18 comments

Ask HN: Do you have any evidence that agentic coding works?

195•terabytest•19h ago•182 comments

Proof of Concept to Test Humanoid Robots

https://thehumanoid.ai/humanoid-and-siemens-completed-a-proof-of-concept-to-test-humanoidrobots-i...
12•0xedb•5d ago•14 comments

Who owns Rudolph's nose?

https://creativelawcenter.com/copyright-rudolph-reindeer/
35•ohjeez•7h ago•15 comments

Apples, Trees, and Quasimodes

https://systemstack.dev/2025/09/humane-computing/
43•entaloneralie•3d ago•2 comments

IP Addresses Through 2025

https://www.potaroo.net/ispcol/2026-01/addr2025.html
173•petercooper•17h ago•132 comments

RSS.Social – the latest and best from small sites across the web

https://rss.social/
10•Curiositry•5h ago•1 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?