frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Mesh LLM: distributed AI computing on iroh

https://www.iroh.computer/blog/mesh-llm
70•tionis•2h ago•19 comments

Show HN: Ant – A JavaScript runtime and ecosystem

https://antjs.org
171•theMackabu•5h ago•76 comments

RISCBoy is an open-source portable games console, designed from scratch

https://github.com/Wren6991/RISCBoy
51•mariuz•3h ago•11 comments

A dock that wakes up reliably

https://fabiensanglard.net/tb4/index.html
9•ingve•32m ago•4 comments

The fine print that follows you out the door: non-compete clauses are spreading

https://oecdecoscope.blog/2026/07/07/the-fine-print-that-follows-you-out-the-door-non-compete-cla...
22•hhs•2h ago•24 comments

Nvidia, CoreWeave, and Nebius: Inside the Circular Financing of the GPU Boom

https://io-fund.com/ai-stocks/nvidia-coreweave-nebius-circular-financing-gpu-boom
152•adletbalzhanov•7h ago•56 comments

Billions of Sketches Reveal Hidden Cultural Variation in Human Concepts

https://arxiv.org/abs/2607.07267
45•Anon84•2d ago•4 comments

We scaled PgBouncer to 4x throughput

https://clickhouse.com/blog/pgbouncer-clickhouse-managed-postgres
175•saisrirampur•9h ago•35 comments

UPI: Anatomy of a Payment Transaction

https://timeseriesofindia.com/economy/reads/upi-architecture/
94•prtk25•8h ago•30 comments

Prefer strict tables in SQLite

https://evanhahn.com/prefer-strict-tables-in-sqlite/
216•ingve•7h ago•105 comments

The early History of the Singular Value Decomposition (1993) [pdf]

https://www.math.ucdavis.edu/~saito/courses/229A/stewart-svd.pdf
88•wolfi1•9h ago•51 comments

Doctors die. It's not like the rest of us, but it should be (2016)

https://archive.cancerworld.net/featured/how-doctors-die/
51•downbad_•2h ago•27 comments

Firefox 12.58% for Desktop Browser Market Share in North America June 2026

https://gs.statcounter.com/browser-market-share/desktop/north-america
14•speckx•15m ago•3 comments

Biff.graph: structure your Clojure codebase as a queryable graph

https://github.com/jacobobryant/biff/tree/v2.x/libs/graph
81•jacobobryant•4d ago•2 comments

Show HN: Orbit – AR satellite tracker, watch 15k+ objects

https://nagylukas.github.io/orbit.html
58•lukas9•8h ago•17 comments

Optimization Solver as a Service

https://www.quicopt.com/developer/getting-started/
13•paddi91•3d ago•9 comments

Show HN: Learn by rebuilding Redis, Git, a database from scratch

https://shipthatcode.com
122•acley•11h ago•35 comments

Weightlifting beats running for blood sugar control, researchers find

https://news.vt.edu/articles/2025/11/research_fralinbiomed_yanweightlifting.html
97•sublinear•2h ago•50 comments

How to Achieve Pruning When Querying by Non-Partitioned Columns in PostgreSQL

https://hakibenita.com/postgresql-partition-pruning
4•theanonymousone•2d ago•1 comments

ZeroFS vs. Amazon S3 Files

https://www.zerofs.net/blog/zerofs-vs-aws-s3-files/
51•cbrewster•7h ago•16 comments

Female US rower completes historic solo journey from California to Hawaii

https://www.theguardian.com/us-news/2026/jul/04/california-hawaii-rowing-solo-journey
251•speckx•8h ago•87 comments

Sixtyfour (YC P25) Is Hiring

https://www.ycombinator.com/companies/sixtyfour/jobs/bIbgQkL-operations-associate-data-samples-cu...
1•HPMOR•8h ago

Show HN: Sqlsure – deterministic semantic checks for AI-generated SQL

https://github.com/sqlsure/sqlsure
10•tejusarora•5h ago•0 comments

How to hide from killer drones

https://www.economist.com/science-and-technology/2026/07/08/how-to-hide-from-killer-drones
101•pseudolus•6h ago•126 comments

Long Covid May Physically Damage the Nerves That Control the Stomach

https://www.ijidonline.com/article/S1201-9712(26)00608-9/fulltext
3•thenerdhead•45m ago•0 comments

Book: RISC-V System-on-Chip Design

https://www.amazon.com/RISC-V-Microprocessor-System-Chip-Design/dp/0323994989
110•xlmnxp•2d ago•47 comments

Show HN: Reame – a CPU inference server that gets faster as it runs

https://github.com/swellweb/reame
36•targetbridge•8h ago•12 comments

Google Search lets creators know more about their reach

https://www.theverge.com/tech/961955/google-search-console-reach-platform-properties
95•herbertl•4d ago•44 comments

Show HN: Earth Game – An offline CLI for turning life goals into quests

https://github.com/skorotkiewicz/earth-game
32•modinfo•8h ago•9 comments

Stop Telling Me to Ask an LLM

https://blog.yaelwrites.com/stop-telling-me-to-ask-an-llm/
158•theorchid•2h ago•83 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?