frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Claude: System Prompts

https://platform.claude.com/docs/en/release-notes/system-prompts
355•tosh•5h ago•150 comments

A 3rd World Embedded Engineer Responds to "RISC-V They Should Have Known Better"

https://rvembedded.com/blog_post/12/
59•Narishma•1h ago•17 comments

The AI Credit Resale Economy

https://vectoral.com/blog/who-are-the-token-brokers
143•mlenhard•3h ago•58 comments

St Lucie Nuclear Reactor Unit 1 manually shutdown, 3 control rods drop into core

https://www.wptv.com/news/treasure-coast/region-st-lucie-county/saint-lucie-nuclear-power-plant-u...
89•toomuchtodo•3h ago•55 comments

NIH is ending a key grant for budding clinical researchers

https://www.science.org/content/article/nih-ending-key-grant-budding-clinical-researchers
54•brandonb•2h ago•14 comments

Anton Chekhov played at love most of his life

https://commonreader.wustl.edu/winning-and-losing-at-the-great-game-of-intimacy/
28•lermontov•1d ago•3 comments

GPS and the Lost Art of Getting Lost

https://www.newyorker.com/news/annals-of-inquiry/gps-and-the-lost-art-of-getting-lost
41•karakoram•3h ago•27 comments

Clamiga: Common Lisp for the Amiga

https://nnamgreb.de/blog/Clamiga+-+Common+Lisp+for+the+Amiga
41•emptybits•3d ago•3 comments

Firefox for iOS now has a native adblocker

https://support.mozilla.org/en-US/kb/block-ads-firefox-ios
340•pentagrama•5h ago•137 comments

Archie G. Norcross' Maine Forest Fire Maps (1918–22)

https://publicdomainreview.org/collection/maine-forest-fire-maps/
14•samclemens•3d ago•2 comments

I've built a free, open-source local and remote memory system for agentw and CL

https://www.lorekit.io/blog/give-your-agent-a-memory
3•mthines•32m ago•1 comments

Plastic mechanical computer from 1963: The Digi-Comp 1 [video]

https://www.youtube.com/watch?v=-y8bGBE71yw
9•tobr•22h ago•4 comments

Before Rightmove, there was the Cosmorama

https://www.ianvisits.co.uk/articles/before-rightmove-there-was-the-cosmorama-londons-forgotten-p...
9•brod_ie•5d ago•1 comments

A True Telnet BBS on a Casio Calculator

https://ei3lh.eu/2026/08/16/a-true-telnet-bbs-on-a-casio-calculator/
57•austinallegro•6h ago•7 comments

Tasklet (YC P26) Is Hiring a Head of Design Engineering

https://tasklet.ai/careers/head-of-design-engineering
1•mayop100•5h ago

The deep history behind the Road to Nowhere inside the Great Smoky Mountains

https://www.wunc.org/environment/2026-08-10/road-to-nowhere-great-smoky-mountains
7•yareally•3d ago•2 comments

A SAT Attack on Tarski's High School Algebra Problem

https://arxiv.org/abs/2608.08421
63•matt_d•4d ago•23 comments

Chestnut – eGPU dock with open-source firmware

https://hwbusters.com/news/comma-ai-egpu-dock-runs-open-source-firmware-249-bare-799-with-an-rx-9...
114•txrx0000•2d ago•29 comments

Show HN: A public AI whose memory is shared across all users

https://wildstatic.com/
49•adjohu•5h ago•32 comments

The weekend is 100 years old

https://www.theguardian.com/money/2026/aug/16/the-weekend-is-100-years-old-skiveday-fridays-and-h...
95•lentil_soup•3h ago•58 comments

Research papers using "kidney disappointment" instead of "kidney failure"

https://scholar.google.com/scholar?q=%22kidney+disappointment%22
260•Alifatisk•6h ago•98 comments

Asus Bike Booster

https://www.asus.com/accessories/bike-booster/asus-oxiis/oxiis-intelligent-bike-booster/
565•wiradikusuma•4d ago•393 comments

Asynchronous I/O in DuckDB: Work, Thread, Work

https://duckdb.org/2026/07/31/asynchronous-io
252•pdet•6d ago•27 comments

Superconducting monolayer cuprate with a single CuO2 plane

https://www.nature.com/articles/s41586-026-10857-1
54•sbulaev•3d ago•13 comments

AI Coding Without the Vibes

https://peterbloem.nl/blog/craft-coding
56•riskone•8h ago•29 comments

Cultivating a state of mind where new ideas are born (2023)

https://www.henrikkarlsson.xyz/p/good-ideas
244•felixbraun•21h ago•58 comments

Super El Niño Keeps Growing as New Forecasts Reach Record Territory Ahead Winter

https://www.severe-weather.eu/long-range-2/super-el-nino-growth-accelerating-to-record-strength-f...
385•dgellow•23h ago•267 comments

Does anyone run Postgres without PgBouncer?

https://brandur.org/fragments/postgres-without-pgbouncer
108•abelanger•3d ago•74 comments

Software Engineering fundamentals matter more

https://rhonabwy.com/2026/08/15/software-engineering-fundamentals-matter-more-than-ever/
275•ingve•20h ago•181 comments

Guiding Ships with Moire Patterns (2018)

https://tinkerings.org/2018/03/28/guiding-ships-with-moire-patterns/
103•Eridanus2•17h ago•26 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?