frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

hdiutil is deprecated in macOS 27 Golden Gate

https://lapcatsoftware.com/articles/2026/8/7.html
63•zdw•1h ago•10 comments

Scrap

https://twitter.com/moxie/status/2091218652133732491
82•tosh•1h ago•13 comments

NetBSD and My Life (2005)

https://mail-index.netbsd.org/netbsd-advocacy/2005/09/10/0000.html
26•gnyeki•1h ago•0 comments

ElevenLabs, TwelveLabs, ThirteenLabs

https://quantumi.sh/public/labs.html
223•jemoka•5h ago•73 comments

Hister – A private, full content search index that you control

https://hister.org/
101•auraham•4d ago•37 comments

A Friendly Introduction to Racket

https://geometridae.bearblog.dev/a-friendly-introduction-to-racket/
101•signa11•5h ago•38 comments

typ.ing

https://typ.ing/
75•bookofjoe•4d ago•27 comments

How a Texas student blew the whistle on a rogue AI hacking attempt

https://www.reuters.com/world/how-texas-student-blew-whistle-rogue-ai-hacking-attempt-2026-08-20/
46•olalonde•1d ago•4 comments

RF Cafe

https://www.rfcafe.com/
68•gregsadetsky•3d ago•9 comments

ATProto spaces: A new extension to ATProto that enables non-public data

https://atproto.com/blog/atproto-spaces-alpha
44•grappler•1d ago•6 comments

Munder Difflin – Agent harness to run an office of your clones

https://munderdiffl.in/
225•simonpure•10h ago•102 comments

Guess which of these LLM outputs is watermarked

https://sgoedecke.github.io/watermark-quiz/
31•gfysfm•2d ago•35 comments

Why it might be time to rethink the human family tree

https://nautil.us/why-it-might-be-time-to-rethink-the-human-family-tree-1283985
29•Anon84•2d ago•18 comments

MiniageOS: "Dumbphone" Version of LineageOS

https://github.com/ofdryads/miniageOS
27•ashenke•2d ago•14 comments

Canada will match US tariffs 'dollar for dollar' as trade talks break down

https://www.bbc.com/news/articles/cvgvyy4x2mvo
236•tartoran•13h ago•880 comments

Show HN: Make your logo extra bright on HDR screens

https://www.soverybright.com/
6•telecuda•1h ago•1 comments

Z80 – The 1970s Microprocessor Still Alive (2021)

https://www.computer.org/csdl/magazine/mi/2021/06/09623402/1yJTvlRLmhi
98•asdefghyk•10h ago•49 comments

One night in Uzbekistan: Why was this one data point so influential?

https://statmodeling.stat.columbia.edu/2026/08/20/we-couldnt-reproduce-their-findings-and-realize...
19•paulpauper•1d ago•2 comments

Mythic's analog compute-in-memory architecture

https://www.mythic.ai
28•janandonly•3d ago•2 comments

New MCP Roadmap

https://blog.modelcontextprotocol.io/posts/mcp-roadmap/
146•pentagrama•6h ago•111 comments

The Creation of Abulafia

https://blog.veitheller.de/abulafia.html
18•saulpw•23h ago•2 comments

Belgian car salesman becomes prince after DNA test proves royal parentage

https://www.cnn.com/2026/08/22/europe/prince-belgium-secret-son-scli-intl
70•MilnerRoute•2h ago•43 comments

Anthropic appears to be A/B testing reduced effort levels in Claude Code

https://twitter.com/argofowl/status/2091150597374537729
87•matthieu_bl•3h ago•89 comments

Show HN: terminal-code – VS Code inside the terminal

https://terminal-code.com
28•robpruzan•3d ago•9 comments

Why your local LLM feels dumber than it is

https://forum.level1techs.com/t/why-your-local-llm-feels-dumber-than-it-is/253917
5•felineflock•1h ago•0 comments

Show HN: Anonymous age verification with passkey-powered encryption

https://loginwithone.com/
28•mikeysight•3d ago•14 comments

Rust Glancer: Rust LSP using 100x less RAM

https://rust-glancer.github.io/blog/hello-world/
378•matklad•1d ago•88 comments

ProgramBench Vetted: Reverse Engineering from a Runnable Binary

https://vetto.ai/companies/programbench-vetted.html
15•rigelbm•2d ago•1 comments

Show HN: Rotation via Double Reflection

https://static.laszlokorte.de/rotor-reflect/
45•laszlokorte•1d ago•9 comments

Felony Bench

https://www.felonybench.com/
812•colinprince•1d ago•325 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?