frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Marfa Public Radio Puts You to Sleep

https://www.marfapublicradio.org/podcast/marfa-public-radio-puts-you-to-sleep
147•reaperducer•4h ago•35 comments

Wayfinder Router: deterministic routing of queries between local and hosted LLM

https://github.com/itsthelore/wayfinder-router
34•handfuloflight•2h ago•1 comments

Show HN: Decomp Academy – Learn to decompile GameCube games into matching C

https://decomp-academy.dev
100•jackpriceburns•5h ago•31 comments

AMD Strix Halo RDMA Cluster Setup Guide

https://github.com/kyuz0/amd-strix-halo-vllm-toolboxes/blob/main/rdma_cluster/setup_guide.md
101•jakogut•6h ago•20 comments

Anonymous GitHub account mass-dropping undisclosed 0-days

https://github.com/bikini/exploitarium
763•binyu•16h ago•299 comments

OpenRA

https://www.openra.net/
653•tosh•18h ago•128 comments

Choosing a Public DNS Resolver

https://evilbit.de/dns-resolver-guide.html
125•pawal•8h ago•40 comments

Bashblog – a single bash script to create blogs

https://github.com/cfenollosa/bashblog
9•ludicrousdispla•2h ago•0 comments

Ford hired AI and sacked humans. It backfired badly

https://www.the-independent.com/tech/ford-ai-automation-human-workers-b3003787.html
127•speckx•3h ago•64 comments

Ancient Tablets Show Markets Worked 4k Years Before Economists Explained Them

https://thedailyeconomy.org/article/ancient-clay-tablets-show-markets-worked-4000-years-before-ec...
37•NaOH•4d ago•26 comments

Fintech Engineering Handbook

https://w.pitula.me/fintech-engineering-handbook/
531•signa11•20h ago•169 comments

The case for physical media ownership

https://dervis.de/physical/
405•cemdervis•19h ago•264 comments

Space Shuttle Endeavour's 20-story vertical display

https://californiasciencecenter.org/about-us/samuel-oschin-air-and-space-center/go-for-stack
44•uticus•1d ago•6 comments

Regular expressions that work "everywhere"

https://www.johndcook.com/blog/2026/06/23/regex-everywhere/
42•ColinWright•2d ago•20 comments

WAL-RUS: a Rust Rewrite of WAL-G for PostgreSQL Backups

https://clickhouse.com/blog/walrus-postgres-backups-in-rust
46•saisrirampur•7h ago•3 comments

The Shape of the System - Engineering for Bounded Cognition

https://shapeofthesystem.com/posts/2026/02/03/bounded-cognition
12•supermatt•1d ago•1 comments

AI learns the “dark art” of RFIC design

https://spectrum.ieee.org/ai-radio-chip-design
223•Brajeshwar•3d ago•145 comments

Turn your site into a place people can bump into each other

https://cauenapier.com/blog/townsquare_release/
205•eustoria•13h ago•86 comments

Asian AI startups launch Mythos-like models

https://techcrunch.com/2026/06/27/asian-ai-startups-launch-mythos-like-models-as-anthropics-expor...
210•bogdiyan•17h ago•160 comments

Enhancing X11 Application Security with LXC

https://dobrowolski.dev/article/enhancing-x11-application-security-with-lxc/
58•shirozuki•9h ago•26 comments

Turning music into a chore is how I became a musician

https://the.scapegoat.dev/turning-music-into-a-chore-is-what-made-me-an-artist/
22•herbertl•5h ago•5 comments

Feds Killed Polestar and Spared Volvo. That Should Terrify You

https://www.thedrive.com/news/feds-killed-polestar-and-spared-volvo-that-should-terrify-you
118•mraniki•4h ago•78 comments

Suspicious Discontinuities (2020)

https://danluu.com/discontinuities/
228•tosh•17h ago•74 comments

Reducing tick density along recreational trails in Ottawa, Canada

https://www.sciencedirect.com/science/article/pii/S1877959X26000476
187•bushwart•3d ago•98 comments

Show HN: Metaspec: The DpANS3R Common Lisp Spec in S-Expr and HTML Format

https://metaspec.dev/#
4•dlowe-net•3d ago•0 comments

DSpark: Speculative decoding accelerates LLM inference [pdf]

https://github.com/deepseek-ai/DeepSpec/blob/main/DSpark_paper.pdf
751•aurenvale•21h ago•314 comments

IP Crawl: Living atlas of open webcams discovered on the public internet

https://ipcrawl.com/
281•arm32•11h ago•139 comments

Post-Mythos Cybersecurity: Keep calm and carry on

https://cephalosec.com/blog/cybersecurity-in-the-post-mythos-era-keep-calm-and-carry-on/
142•Versipelle•16h ago•49 comments

Response to AI slop is from Robin Williams

https://jayacunzo.com/blog/your-move-chief
171•herbertl•5h ago•96 comments

How do you keep Web MIDI from crashing a 1983 synthesizer?

https://knob.monster/how-do-you-keep-web-midi-from-crashing-a-1983-synthesizer
37•halfradaition•3d 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?