frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Creepy Crawlies

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

Haiku R1/beta6 has been released

https://www.haiku-os.org/news/2026-08-26_haiku_r1_beta6
99•metrofun•2h ago•22 comments

Coordination Headwind: How Organizations Are Like Slime Molds

https://komoroske.com/slime-mold/
34•rzk•2h ago•14 comments

Hacking IKEA Furniture

https://greenlightning.eu/diy/hacking-ikea-furniture/
184•greenlightning•6h ago•100 comments

Electric rain can eat through metal

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

Omarchy: Any User Process Can Escalate to Root

https://0xcc.io/posts/omarchy-root-creds/
180•trap0xcc•2h ago•162 comments

European Commission Revives Push for Encryption Backdoors in ProtectEU Strategy

https://reclaimthenet.org/eu-protecteu-strategy-encryption-backdoor-law-enforcement
162•nickslaughter02•2h ago•48 comments

Artie (YC S23) Is Hiring Technical AES

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

METR and Redwood Offer Holy %^ Postmortem of the HuggingFace Hack

https://thezvi.wordpress.com/2026/08/29/metr-and-redwood-offer-holy-postmortem-of-the-huggingface...
45•catbird•4h ago•15 comments

Zig: Pointer Stability for ArrayLists

https://ziglang.org/devlog/2026/#2026-08-27
30•tosh•3h ago•3 comments

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

https://www.qubes-os.org/news/2026/08/29/qsb-118/
167•vntok•9h ago•65 comments

Casey Muratori – The Root of the Root of All Evil – BSC 2026 [video]

https://www.youtube.com/watch?v=hpj6r6CjJf8
216•surprisetalk•3d ago•105 comments

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

https://arxiv.org/abs/1804.07389
170•joebig•9h ago•49 comments

Dad's Custom Atari Peripherals – By Jim Trageser

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

When fruit is scarce, these monkeys hunt animals

https://www.smithsonianmag.com/smart-news/when-fruit-is-scarce-these-monkeys-hunt-animals-the-beh...
35•cisc•1d ago•11 comments

Europe's summer drought is so extreme that desertification is a growing threat

https://fortune.com/2026/08/29/europe-summer-drought-desertification-threat-rivers-fish/
117•Brajeshwar•3h ago•120 comments

'They shot all their weapons; they trashed their ships; they ran out of money'

https://www.theguardian.com/us-news/2026/aug/27/trump-iran-war-navy-budget
14•cwwc•35m ago•0 comments

An implementation of Conway's Game of Life for Windows 3.1x and later

https://www.muppetlabs.com/~breadbox/software/windows.html
40•Bluestein•6h ago•7 comments

Synchronisation and SMPTE timecode (time code)

https://www.philrees.co.uk/articles/timecode.htm
4•sublinear•2d ago•0 comments

What my dad taught me about AI coding in the 90s

https://askmike.org/articles/ai-coding-lessons-in-the-90s-from-my-dad/
88•askmike•6d ago•45 comments

Automating Immersive Reading

https://smoores.dev/post/automating_immersive_reading/
59•smoores•6h ago•17 comments

RISC-V is now officially supported by CPython

https://blog.python.org/2026/08/riscv-now-officially-supported/
272•lumpa•5d ago•46 comments

Bug Blindness

https://danluu.com/bug-blind/
350•davidmckenna•17h ago•227 comments

Building my own network stack

https://blog.lyc8503.net/en/post/dn42-2-dnet/
76•uneven9434•8h ago•63 comments

Claude Session URL appended to commit messages and PR descriptions by default

https://github.com/anthropics/claude-code/issues/66504
118•sparsesignal•5h ago•143 comments

Hy4 preview

https://www.tencent.com/tencent-releases-and-open-sources-tencent-hy4-preview/
364•shenli3514•22h ago•230 comments

Orbs

https://ampcode.com/notes/orbs-explained
80•tosh•5d ago•32 comments

JupyterGIS 0.16: a grammar of graphics for maps, and collaborative story maps

https://blog.jupyter.org/jupytergis-0-16-new-visualization-capabilities-collaborative-story-maps-...
84•arjxn-py•5d ago•9 comments

monty-go: Pure-Go wrapper for Pydantic's Monty Python Interpreter

https://github.com/fugue-labs/monty-go
35•networked•6h ago•11 comments

California lawmakers unanimously pass Linux exemption from age-verification law

https://www.tomshardware.com/software/linux/california-lawmakers-unanimously-pass-linux-exemption...
620•shscs911•14h ago•297 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?