frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Scrap (2006)

https://twitter.com/moxie/status/2091218652133732491
330•tosh•9h ago•179 comments

NanoGPT Speedrun Frontier

https://www.primeintellect.ai/research/nanogpt-speedrun
59•stared•5h ago•18 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
208•felineflock•9h ago•69 comments

ElevenLabs, TwelveLabs, ThirteenLabs

https://quantumi.sh/public/labs.html
333•jemoka•12h ago•102 comments

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

https://hister.org/
257•auraham•4d ago•70 comments

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

https://rwwgreene.substack.com/p/i-set-a-trap-for-a-book-marketing
15•rznicolet•9h ago•12 comments

typ.ing

https://typ.ing/
203•bookofjoe•4d ago•59 comments

RF Cafe

https://www.rfcafe.com/
159•gregsadetsky•4d ago•28 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/
123•olalonde•1d ago•44 comments

A Friendly Introduction to Racket

https://geometridae.bearblog.dev/a-friendly-introduction-to-racket/
204•signa11•13h ago•104 comments

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

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

Reading Maps – Journeys from fiction drawn on the real world

https://readingmaps.com/
10•hakkikonu•9h ago•2 comments

NetBSD and my life (2005)

https://mail-index.netbsd.org/netbsd-advocacy/2005/09/10/0000.html
102•gnyeki•8h ago•25 comments

Thinking in Python

https://thinkinginpython.com/
78•pjacotg•9h ago•18 comments

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

https://munderdiffl.in/
260•simonpure•17h ago•115 comments

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

https://www.bbc.com/news/articles/cvgvyy4x2mvo
523•tartoran•21h ago•1290 comments

A week of using Codex more than Claude

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

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

https://marcua.net/minitools/figmimic/
68•speckx•9h ago•7 comments

hdiutil is deprecated in macOS 27 Golden Gate

https://lapcatsoftware.com/articles/2026/8/7.html
169•zdw•8h ago•70 comments

Autolith: A programming agent with a live runtime

https://www.lambda-symbolics.com/autolith
116•vismit2000•2d ago•46 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...
82•paulpauper•1d ago•16 comments

Conway's Game of Life in real life

https://blog.coredump.cx/p/conways-game-of-life-in-real-life
41•surprisetalk•2d ago•10 comments

What's in a PowerPoint File?

https://editide.com/blog/what-is-a-pptx-file/
63•danielochoa0620•3d ago•33 comments

Show HN: OzBrain, a shared brain for knowledge between agents and your team

https://ozbrain.com
81•dariusmonsef•1d ago•48 comments

Z80 – The 1970s Microprocessor Still Alive (2021)

https://www.computer.org/csdl/magazine/mi/2021/06/09623402/1yJTvlRLmhi
120•asdefghyk•17h ago•57 comments

Rust Glancer: Rust LSP using 100x less RAM

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

ProgramBench Vetted: Reverse Engineering from a Runnable Binary

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

A Kantian Critique of "Sorry" by Justin Bieber

https://decodingvibes.com/blog/a-kantian-critique-of-sorry-by-justin-bieber/
199•altmanaltman•14h ago•86 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
61•Anon84•2d ago•34 comments

New MCP Roadmap

https://blog.modelcontextprotocol.io/posts/mcp-roadmap/
175•pentagrama•14h ago•127 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?