frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The Lost Treasure of Sid Meier's Pirates

https://remapradio.com/articles/the-lost-treasure-of-sid-meiers-pirates/
11•spankibalt•41m ago•0 comments

We Rebuilt the Linux MicroVM Stack on Apple Silicon

https://encore.dev/blog/firecracker-apple-silicon
23•signa11•1h ago•1 comments

The August 17 outage

https://github.blog/news-insights/company-news/the-august-17-outage-and-the-work-ahead/
483•0xedb•12h ago•550 comments

I like 'em thick: an apology to my English teachers

https://www.experimental-history.com/p/i-like-em-thick
703•Ariarule•2d ago•291 comments

HTML Can Do That

https://chrisburnell.com/html-can-do-that/
759•encyclopedism•1d ago•184 comments

The Religious Experience of Philip K. Dick by R. Crumb (1986)

https://philipdick.com/resources/miscellaneous/the-religious-experience-of-philip-k-dick-by-r-cru...
25•wise_blood•2h ago•9 comments

Version Control for Everything

https://tyoverby.com/posts/version-control-for-everything-else/
23•evakhoury•3d ago•11 comments

Malicious Rust crate Arrayref runs a build-time payload

https://safedep.io/arrayref-proc-macro1-rust-build-time-malware/
478•abhisek•18h ago•409 comments

Ox Alpha

https://openrouter.ai/stealth/ox-alpha
124•mtokmak06•8h ago•94 comments

I should have loved biology (2020)

https://jsomers.net/i-should-have-loved-biology/
262•tyre•14h ago•101 comments

Japan tried to build an operating system for the world, the US intervened

https://www.xda-developers.com/japan-tried-build-operating-system-entire-world-us-government-inte...
79•rdmuser•2h ago•37 comments

Show HN: Huzzah – a novel approach to coding with AI

https://www.danielvaughn.dev/posts/huzzah/
291•danielvaughn•12h ago•154 comments

Why aren't smart people happier? (2022)

https://www.experimental-history.com/p/why-arent-smart-people-happier
158•rafaelc•13h ago•220 comments

CIA funding helped keep NeXT afloat in the 80s

https://www.wsj.com/tech/steve-jobs-apple-next-cia-161b65f9?st=NWWds1&reflink=desktopwebshare_per...
392•EwanG•1d ago•239 comments

Launch HN: Vendo (YC S26) – Let users build features on top of your product

https://github.com/runvendo/vendo
34•yousefh409•16h ago•18 comments

Captain Zilog

https://www.zilog.com/captain_zilog/
47•rbanffy•3d ago•6 comments

Make a 6-Tesla-class high-temperature superconducting dipole magnet at 4.2 K

https://journals.aps.org/prab/abstract/10.1103/4nhs-bkwh
37•supermagnet•6d ago•9 comments

Codex on AWS bedrock bug causing 10x charges

https://github.com/openai/codex/issues/37674
128•TheP1000•4h ago•39 comments

Seed: Minimal, self-modifying agent harness

https://github.com/vivekhaldar/seed
13•gandalfgeek•2h ago•1 comments

Vomit: Clean up Claude 5's token output with a separate LLM

https://github.com/zachahn/vomit
243•Bluestein•16h ago•241 comments

Show HN: Argentic – An L402 Lightning toll booth for AI scraping agents

https://Argentic.network
5•Ag0146•1h ago•2 comments

Linux 7.2

https://www.igalia.com/2026/08/19/Linux-72-Released.html
243•mariuz•16h ago•92 comments

AliExpress runs silent WebAudio fingerprinting that breaks Bluetooth multipoint

https://blog.laserphile.com/2026/08/aliexpress-webpage-keeping-multipoint.html
954•emctech•21h ago•298 comments

I Ported Moonshine to JavaScript

https://petewarden.com/2026/08/15/why-i-ported-moonshine-to-javascript/
4•jreynar•5d ago•1 comments

Git at any scale

https://cursor.com/blog/git-at-any-scale
329•meetpateltech•2d ago•102 comments

Stop Anthropomorphizing Intermediate Tokens as Reasoning/Thinking Traces (2025)

https://arxiv.org/abs/2504.09762
225•nunodonato•1d ago•151 comments

Anti-AI fonts are useless and harmful

https://blog.yaros.ae/anti-ai-fonts-are-useless-and-harmful/
153•speckx•16h ago•110 comments

Speeding Up (Small) Ruby Hashes

https://byroot.github.io/ruby/performance/2026/08/13/speeding-up-ruby-hashes.html
49•arto•1w ago•0 comments

AI companies destroy physical books – let's scan rare books before it's too late

https://annas-archive.gl/blog/physical-destruction.html
295•Cider9986•5h ago•215 comments

SpacetimeDB: a short technical review

https://strn.cat/posts/spacetime/
88•hurrrr•12h ago•17 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?