frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The time the x86 emulator team found code so bad they fixed it during emulation

https://devblogs.microsoft.com/oldnewthing/20260615-00/?p=112419
175•paulmooreparks•3h ago•45 comments

John Carmack on Fabrice Bellard

https://twitter.com/ID_AA_Carmack/status/2064095424420487226
149•apitman•2h ago•81 comments

A backdoor in a LinkedIn job offer

https://roman.pt/posts/linkedin-backdoor/
1059•lwhsiao•11h ago•198 comments

Banned Book Library in a Wi-Fi Smart Light Bulb

https://www.richardosgood.com/posts/banned-book-library/
343•sohkamyung•9h ago•172 comments

Iroh 1.0

https://www.iroh.computer/blog/v1
1129•chadfowler•16h ago•339 comments

Show HN: Garden of Flowers – an archive of pictorial typography before ASCII art

https://garden-of-flowers.heikkilotvonen.com/
55•california-og•3h ago•11 comments

Ask HN: Has anyone replaced Claude/GPT with a local model for daily coding?

917•cloudking•17h ago•417 comments

TinyWind: A pixel pirate sailing game with real wind physics (380k+ kms sailed)

https://tinywind.io
781•tinywind•15h ago•151 comments

Understanding the rationale behind a rule when trying to circumvent it

https://devblogs.microsoft.com/oldnewthing/20260611-00/?p=112415
3•tosh•19m ago•0 comments

I Love the Computer

https://michaelenger.com/blog/i-love-the-computer/
214•speckx•11h ago•128 comments

I hacked into the worst e-bike and fixed it [video]

https://www.youtube.com/watch?v=hPrtVGimBYs
65•alexis-d•5d ago•26 comments

Humanity isn't ready for the coming intelligence explosion

https://www.economist.com/by-invitation/2026/06/15/humanity-isnt-ready-for-the-coming-intelligenc...
68•andsoitis•5h ago•171 comments

Amazon Announces Multibillion-Dollar Data Center in Missouri

https://www.narracomm.com/amazon-announces-multibillion-dollar-data-center-in-missouri/
102•thelonelyborg•7h ago•88 comments

Why I email complete strangers

https://www.goodinternetmagazine.com/why-i-email-complete-strangers/
138•karakoram•9h ago•59 comments

Cohere's First Model for Developers

https://cohere.com/blog/north-mini-code
75•hmokiguess•4d ago•17 comments

My Homelab AI Dev Platform

https://rsgm.dev/post/ai-dev-platform/
297•rsgm•16h ago•52 comments

Peopleless economy? Not technically impossible

https://gmalandrakis.com/writings/ad-economicum.html
169•l0new0lf-G•10h ago•287 comments

Hetzner Price Adjustment

https://docs.hetzner.com/general/infrastructure-and-availability/price-adjustment/#cloud-servers
413•tuhtah•18h ago•563 comments

The 90-year-old idea behind JEPA models: Canonical Correlation Analysis

https://shonczinner.github.io/posts/embedding-prediction/
47•Anon84•4d ago•7 comments

Fox to buy Roku

https://www.wsj.com/business/deals/fox-roku-deal-f6e564f9
316•thm•19h ago•390 comments

What job interviews taught me about Kubernetes

https://notnotp.com/notes/what-job-interviews-taught-me-about-kubernetes/
166•chmaynard•11h ago•119 comments

Copper transport drug restores memory and clears toxic Alzheimer's proteins

https://www.monash.edu/news/articles/copper-drug-restores-memory-and-clears-toxic-alzheimers-prot...
290•bookofjoe•17h ago•108 comments

What every coder should know about gamma (2016)

https://blog.johnnovak.net/2016/09/21/what-every-coder-should-know-about-gamma/
92•sph•2d ago•27 comments

Salesforce to Acquire Fin (formerly Intercom) for $3.6B

https://www.salesforce.com/news/press-releases/2026/06/15/salesforce-signs-definitive-agreement-t...
301•colesantiago•19h ago•221 comments

The Null Is Always False (Except When It Is True) (2014)

http://daniellakens.blogspot.com/2014/06/the-null-is-always-false-except-when-it.html
5•mkl95•2d ago•0 comments

How TimescaleDB compresses time-series data

https://roszigit.com/en/blog/timescaledb-compression-hypercore
148•lkanwoqwp•14h ago•17 comments

Game Engine White Papers: Commander Keen

https://forgottenbytes.net/commander_keen.html
193•mfiguiere•14h ago•64 comments

Launch HN: Drafted (YC P26) – Models for residential architecture

52•PrimalNick•15h ago•58 comments

Show HN: Veterinarian turned founder, AI lawn diagnosis

https://grassdx.com/
62•andrewbr•13h ago•55 comments

Claude Corps

https://www.anthropic.com/news/claude-corps
123•Mustan•14h ago•81 comments
Open in hackernews

A kernel developer plays with Home Assistant

https://lwn.net/SubscriberLink/1017720/7155ecb9602e9ef2/
138•pabs3•1y ago

Comments

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

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

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