frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Internal files add to evidence of an ExxonMobil climate deception campaign

https://insideclimatenews.org/news/07102026/exxonmobil-climate-deception-new-evidence/
62•gumby•31m ago•16 comments

I paid people to try and follow my README

https://shkspr.mobi/blog/2026/10/i-paid-people-to-try-and-follow-my-readme/
157•edent•3h ago•90 comments

The tilde in your PATH may not be your HOME

https://disconnect3d.pl//2026/10/02/dont-put-tilde-in-your-path/
65•arusekk•2h ago•39 comments

Terence Tao: Math 2.0 [pdf]

https://teorth.github.io/tao-web/slides/math-2-0-caltech-2026.pdf
67•Anon84•1h ago•53 comments

LineageOS 24.0

https://lineageos.org/Changelog-32/
249•timschumi•8h ago•83 comments

Nitter: Update Oct 10th seeking funding and legal help

https://nitter.net
247•ForHackernews•4h ago•107 comments

Valen's Memory Safety: A New Kind of Borrow Checking

https://verdagon.dev/blog/valen-group-borrowing
37•verdagon•2h ago•19 comments

IRCv3

https://ircv3.net/
178•basilikum•4h ago•154 comments

Plumbers, chains, and famous painters: The history of the pipe operator in R

http://adolfoalvarez.cl/blog/2021-09-16-plumbers-chains-and-famous-painters-the-history-of-the-pi...
20•sinnsro•2d ago•2 comments

2D Vehicles

https://patkerr.co.uk/2d-vehicles/
547•Michelangelo11•4d ago•107 comments

Build your own decision model

https://nishtahir.com/build-your-own-decision-model/
394•softwaredoug•16h ago•89 comments

Weave (YC W25) is hiring ML, AI, product, & design engineers

https://jobs.ashbyhq.com/weave-os
1•adchurch•2h ago

The RAM shortage is bringing back DDR4

https://www.theverge.com/games/1009140/ram-shortage-intel-amd-ddr4-comeback
123•1potato•1d ago•111 comments

A city-building game in which the city would prefer you didn't

https://housing.over.pizza/
430•JumpCrisscross•18h ago•146 comments

The Lightbulb Computer

https://lightbulbcomputer.com/
506•oskarth•1d ago•78 comments

Show HN: BetterWispr – Free, open-source dictation for Mac

https://betterwispr.com/
11•kartik017•2h ago•3 comments

Rat's Register Allocator

https://hexrat.cc/pages/blog/2026_10_07
33•mpweiher•1d ago•2 comments

How big is a Git commit?

https://ratfactor.com/cards/git-commit-size
61•theanonymousone•2d ago•24 comments

PSPi 6 – Raspberry Pi in a PSP

https://github.com/othermod/PSPi-Version-6
117•therepanic•14h ago•11 comments

Open-Source Microsoft Office Excel, PowerPoint, and Word Replications

https://www.tomshardware.com/software/microsoft-office/creator-of-free-adobe-clones-unveils-open-...
20•mathgenius•1h ago•6 comments

Rolling the Root Key

https://blog.apnic.net/2026/10/09/rolling-the-root-key-2/
3•speckx•1d ago•0 comments

Retrofitting language models to operate over bytes

https://www.nature.com/articles/s41586-026-11111-4
86•theanonymousone•3d ago•17 comments

Show HN: Happy Hangul Day! An RNN for Generating Korean Handwriting Strokes

https://hangul.ink/blog/hangul-day
74•jbaudanza•2d ago•14 comments

Nix wrote half of my debugger

https://fzakaria.com/2026/10/07/nix-wrote-half-of-my-debugger
218•ingve•2d ago•52 comments

When Ldaxr Doesn't Work: Exclusive Accesses and Cacheability on AArch64

https://joelsiks.com/posts/aarch64-exclusive-access-cacheability/
15•joelsiks•1d ago•2 comments

Five months treating bugs like patients and coding agents like a medical team

https://www.cockroachlabs.com/blog/experiment-running-hospital-code/
172•rafiss•1d ago•74 comments

Talorys – A self-hosted personal AI agent on Cloudflare's free tier

https://github.com/rociiu/talorys
307•rociiu•1d ago•141 comments

Knuth reward check

https://www.thomas-huehn.com/knuth-reward-check/
210•Curiositry•23h ago•76 comments

Mxc: Microsoft Execution Containers version 1.0.0

https://blogs.windows.com/windowsdeveloper/2026/10/07/microsoft-execution-containers-policy-drive...
211•smokel•2d ago•58 comments

3rd Yandex Cloud Data Center Was Hit

https://status.yandex.cloud/en/incidents/2136
350•defly•7h ago•431 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?