frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

“I just chose words carefully”

https://unsung.aresluna.org/i-just-chose-words-carefully/
372•zdw•4h ago•95 comments

Creepy Crawlies

https://people.kernel.org/monsieuricon/creepy-crawlies
963•zdw•1d ago•471 comments

Understanding ChatGPT Work

https://simonwillison.net/2026/Aug/30/understanding-chatgpt-work/
62•gmays•1h ago•23 comments

Matrox: Graphics for Professionals

https://www.abortretry.fail/p/matrox
42•BirAdam•3h ago•7 comments

CobaltC – The Successor to C?

https://strawberry9.github.io/the-wrong-memory/Appendix_06.html
6•SilentLambda•58m ago•5 comments

Haiku R1/beta6 has been released

https://www.haiku-os.org/news/2026-08-26_haiku_r1_beta6
265•metrofun•11h ago•82 comments

Cores in space: The core memory module from a 1980 Spacelab computer

https://www.righto.com/2026/08/spacelab-core-memory.html
87•pwg•7h ago•13 comments

It takes 5 cloud services to hear my doorbell

https://blog.vghaisas.com/rube-goldberg-doorbell/
21•vghaisas•2d ago•5 comments

Show HN: NFC Energy-Harvesting PCB Business Card with an MCU

https://wilsonharper.net/projects/businesscard/
121•WilsonHarper•2d ago•13 comments

Why do I lose my passion and want to do nothing?

33•hanstyle•44m ago•17 comments

Sort branches by last commit date

https://ryangreenberg.com/til/git-branches-by-commit-date/
95•speckx•5d ago•34 comments

How to build a diffusion language model

https://kuleshov-group.github.io/blog/blog/2026/how-to-build-a-diffusion-language-model/
21•volodia•3h ago•2 comments

Continuous Diffusion Language Models (CDLM's)

https://sander.ai/2026/08/24/continuous-dlms.html
67•peter_d_sherman•6h ago•26 comments

Why open source rocks – a new SM750 (Silicon Motion GPU) HDMI Driver

https://github.com/KodeMunkie/sm750hdmifb
82•SillyUsername•8h ago•34 comments

Commercially Available Bike Generators Are Not Sustainable (2011)

https://solar.lowtechmagazine.com/2011/05/bike-powered-electricity-generators-are-not-sustainable/
36•baud147258•4d ago•27 comments

Hacking IKEA Furniture

https://greenlightning.eu/diy/hacking-ikea-furniture/
274•greenlightning•15h ago•187 comments

Relm4 makes developing beautiful cross-platform applications idiomatic

https://relm4.org/
17•Bluestein•4d ago•9 comments

Coordination Headwind: How Organizations Are Like Slime Molds

https://komoroske.com/slime-mold/
136•rzk•11h ago•45 comments

Startup Anti-Patterns

https://www.itamarnovick.com/intro-to-startup-anti-pattern-series/
97•rzk•11h ago•54 comments

Dad’s Custom Atari Peripherals

https://www.goto10retro.com/p/dads-custom-atari-peripherals
108•rbanffy•3d ago•15 comments

Artie (YC S23) Is Hiring Technical AES

https://www.artie.com/careers?ashby_jid=e87b84d2-78b3-41a3-937a-47e83643cdf1
1•j-cheong•10h ago

Flock Safety's controversial CEO just got a taste of his own medicine

https://www.neowin.net/news/the-ceo-of-americas-biggest-surveillance-network-just-got-a-taste-of-...
17•devonnull•40m ago•2 comments

Arbitrary code execution in QubesOS via copy-to-VM error reporting backchannel

https://www.qubes-os.org/news/2026/08/29/qsb-118/
213•vntok•18h ago•84 comments

How would you know whether an ancient culture had zero?

https://www.johndcook.com/blog/2026/08/21/ancient-number-system/
33•ibobev•3d ago•7 comments

SolarWindow launches 0.85 mm-thick, self-adhesive solar film

https://www.pv-magazine.com/2026/08/27/https-www-pv-magazine-com-2026-08-27-solarwindow-launches-...
8•thelastgallon•34m ago•4 comments

Longest Straight Line Paths on Water or Land on the Earth (2018)

https://arxiv.org/abs/1804.07389
195•joebig•19h ago•56 comments

Omarchy: Any User Process Can Escalate to Root

https://0xcc.io/posts/omarchy-root-creds/
450•trap0xcc•11h ago•424 comments

Zig: Pointer Stability for ArrayLists

https://ziglang.org/devlog/2026/#2026-08-27
89•tosh•12h ago•65 comments

Electric rain can eat through metal

https://www.scientificamerican.com/article/electric-rain-can-eat-through-metal/
101•sohkamyung•3d ago•20 comments

Adding a directional cost bias to a TSP heuristic reveals better local optima

https://tsp.uncledroid.app
4•Abhijit8086•6d ago•1 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?