frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

The End of an Athlon

http://www.os2museum.com/wp/the-end-of-an-athlon/
99•userbinator•4h ago•25 comments

To become a better writer, read as much as you can

https://nappertime.com/the-golden-rule-of-becoming-a-better-writer/
161•andsoitis•7h ago•106 comments

JIT Compiling Code in 5μs

https://malisper.me/jit-compiling-code-in-5-us/
71•zX41ZdbW•4h ago•32 comments

MartyPC is a cross-platform emulator of early PCs written in Rust

https://martypc.net/
120•boilerupnc•7h ago•39 comments

Fast and Hard Code

https://lucumr.pocoo.org/2026/8/22/fast-hard-code/
34•tosh•5h ago•6 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
361•felineflock•16h ago•132 comments

The Art and Beauty of Blade Runner (2015)

https://nappertime.com/the-art-of-and-beauty-of-blade-runner/
90•cocacola1•9h ago•35 comments

Scrap (2006)

https://twitter.com/moxie/status/2091218652133732491
376•tosh•16h ago•197 comments

ElevenLabs, TwelveLabs, ThirteenLabs

https://quantumi.sh/public/labs.html
403•jemoka•19h ago•120 comments

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

https://hister.org/
358•auraham•4d ago•82 comments

Doomscrolling at work wastes time, but the real cost is what happens after

https://stories.tamu.edu/news/2026/08/13/doomscrolling-at-work-wastes-time-but-the-real-cost-is-w...
10•giuliomagnifico•1h ago•2 comments

NanoGPT Speedrun Frontier

https://www.primeintellect.ai/research/nanogpt-speedrun
104•stared•12h ago•27 comments

typ.ing

https://typ.ing/
278•bookofjoe•4d ago•91 comments

Thinking in Python

https://thinkinginpython.com/
178•pjacotg•16h ago•35 comments

RF Cafe

https://www.rfcafe.com/
204•gregsadetsky•4d ago•36 comments

I set a trap for a book-marketing scammer (2025)

https://rwwgreene.substack.com/p/i-set-a-trap-for-a-book-marketing
48•rznicolet•16h ago•33 comments

New MCP Roadmap

https://blog.modelcontextprotocol.io/posts/mcp-roadmap/
211•pentagrama•21h ago•133 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/
163•olalonde•1d ago•72 comments

I Dream of Quieter Computing

https://henry.codes/writing/i-dream-of-quieter-computing/
77•Sir_Twist•8h ago•61 comments

NetBSD and my life (2005)

https://mail-index.netbsd.org/netbsd-advocacy/2005/09/10/0000.html
129•gnyeki•15h ago•29 comments

A week of using Codex more than Claude

https://allaboutcoding.ghinda.com/a-week-of-using-codex-more-than-claude/
199•speckx•1d ago•227 comments

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

https://atproto.com/blog/atproto-spaces-alpha
145•grappler•2d ago•18 comments

A Friendly Introduction to Racket

https://geometridae.bearblog.dev/a-friendly-introduction-to-racket/
232•signa11•20h ago•130 comments

Mathematicians will probably become obsolete before anyone else [pdf]

https://olli.unt.edu/handouts/fall24/tk-writing-sample.pdf
55•tiahura•10h ago•24 comments

The Sloppification of Peptides

https://henryaj.substack.com/p/the-sloppification-of-peptides
10•henryaj•1h ago•0 comments

Wi-Fi 8 is the first wireless upgrade in years that isn't chasing speed

https://www.xda-developers.com/wi-fi-8-first-wireless-upgrade-years-isnt-chasing-speed-home-netwo...
107•taubek•4h ago•86 comments

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

https://munderdiffl.in/
281•simonpure•1d ago•121 comments

Show HN: Public Muscriptor Instance (latest, most powerful Audio-to-MIDI model)

https://www.pianoify.net/
45•jardy•1d ago•8 comments

Figmimic – A bookmarklet to copy any webpage into Figma as editable layers

https://marcua.net/minitools/figmimic/
101•speckx•16h ago•13 comments

Z80 – The 1970s Microprocessor Still Alive (2021)

https://www.computer.org/csdl/magazine/mi/2021/06/09623402/1yJTvlRLmhi
140•asdefghyk•1d ago•69 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?