frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The art and engineering of Sega CD Silpheed

https://fabiensanglard.net/silpheed/index.html
76•ibobev•1h ago•11 comments

Apple's new SpeechAnalyzer API, benchmarked against Whisper and its predecessor

https://get-inscribe.com/blog/apple-speech-api-benchmark.html
10•get-inscribe•16m ago•2 comments

A voxel Tokyo in real Japan time – ride the Yamanote line and study Japanese

https://jivx.com/densha
220•momentmaker•5h ago•24 comments

Grok uploaded my user directory to xAI's servers

https://twitter.com/a_green_being/status/2076598897779020159
378•tnolet•2h ago•191 comments

LAPD lets contract with surveillance giant Flock expire

https://techcrunch.com/2026/07/13/lapd-lets-contract-with-surveillance-giant-flock-expire-citing-...
81•forks•1h ago•28 comments

Grok CLI uploaded the whole home directory to GCS

https://twitter.com/i/status/2076598897779020159
231•denysvitali•2h ago•84 comments

Show HN: DOM-docx – HTML to native, editable Word docs (MIT)

https://github.com/floodtide/dom-docx
83•fishbone•4h ago•23 comments

Precursor

https://blog.cloudflare.com/introducing-precursor/
93•AznHisoka•1h ago•83 comments

DOGE is done. What happened to its records?

https://www.ms.now/opinion/doge-government-efficiency-records-job-cuts-elon-musk-foia
77•ndsipa_pomu•26m ago•13 comments

The 'absolute magic' of Morse code that still connects people globally

https://www.bbc.com/news/articles/cwye0dlzgejo
63•austinallegro•5d ago•24 comments

The Graph That Should Be Front-Page News

https://www.lyrebirddreaming.com/post/the-graph-that-should-be-front-page-news
437•rakel_rakel•10h ago•238 comments

Backtrack-Free Cursive

https://mmapped.blog/posts/52-backtrack-free-cursive
196•dmit•10h ago•85 comments

Show HN: Clawk – Give coding agents a disposable Linux VM, not your laptop

https://github.com/clawkwork/clawk
95•celrenheit•2h ago•102 comments

Cursed circuits #6: reverse avalanche oscillator

https://lcamtuf.substack.com/p/cursed-circuits-6-reverse-avalanche
35•surprisetalk•4d ago•7 comments

Counting ArXiv Delays

https://fi-le.net/arxiv/
5•fi-le•3d ago•0 comments

GhostLock, a stack-UAF that has existed in all Linux distributions for 15 years

https://nebusec.ai/research/ionstack-part-2/
354•ranger_danger•4d ago•163 comments

The social physics of conversation: Communication patterns matter

https://andiroberts.com/citizenship/the-social-physics-of-conversation-citizenship-leadership
128•kiyanwang•5d ago•27 comments

Interrail: 6,379Km and 13 Countries over 7 weeks

https://shkspr.mobi/blog/2026/07/another-ridiculous-interrail-holiday-6379km-and-13-countries-ove...
170•coinfused•8h ago•113 comments

Zig Creator Calls Spade a Spade, Anthropic Blows Smoke

https://raymyers.org/post/zed-creator-calls-spade-a-spade/
1120•crowdhailer•7h ago•567 comments

Cyberpunk Comics, Manga and Graphic Novels

https://shellzine.net/cyberpunk-comics/
268•zdw•17h ago•115 comments

DMS 1.5 "The Wolverine" Released

https://danklinux.com/blog/v1-5-release
10•sonixier•4d ago•4 comments

Frieve Vinyl Explained – Microscopic stylus/groove physics simulation

https://frieve-a.github.io/sound_toolbox/vinyl_explained/vinyl_explained.html
61•XzetaU8•4d ago•8 comments

Tiny Emulators

https://floooh.github.io/tiny8bit-preview/index.html
318•naves•19h ago•28 comments

Benchmarking 15 "E-Waste" GPUs with Modern Workloads

https://esologic.com/benchmarking-tesla-gpus/
5•eso_logic•2h ago•1 comments

Control the Ideas, Not the Code

https://antirez.com/news/169
163•surprisetalk•4h ago•121 comments

Beavis Ultrasound PnP ISA Sound Card Replica

https://github.com/schlae/BeavisUltrasound
88•mariuz•11h ago•32 comments

So you want to learn physics (second edition, 2021)

https://www.susanrigetti.com/physics
291•azhenley•5d ago•58 comments

How to read more books

https://scotto.me/blog/2026-07-12-how-to-read-more-books/
491•silcoon•1d ago•258 comments

Wikipedia escapes Category 1 designation under the UK Online Safety Act for now

https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2026-07-13/Special_report
6•hn_acker•23m ago•2 comments

Go-Flavored Concurrency in C

https://antonz.org/concurrency-in-c/
6•ibobev•26m ago•0 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?