frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Giant trees have no trouble pumping water to top branches

https://news.exeter.ac.uk/faculty-of-environment-science-and-economy/giant-trees-have-no-trouble-...
97•hhs•3h ago•46 comments

Leanstral 1.5: Proof Abundance for All

https://mistral.ai/news/leanstral-1-5/
93•programLyrique•3h ago•28 comments

GLM5.2 on AMD MI355X at 2626 tok/s/node at over 2x lower cost than Blackwell

https://www.wafer.ai/blog/glm52-amd
100•latchkey•4h ago•27 comments

MSI Center – How to gain SYSTEM privileges in seconds

https://mrbruh.com/msicenter/
26•MrBruh•1h ago•7 comments

Steam Controller Auto-Charge – pilot to magnetic charging puck using CV

https://github.com/FossPrime/Steam-Controller-Auto-Charge
73•zdw•3h ago•12 comments

SearXNG: A free internet metasearch engine

https://github.com/searxng/searxng
137•theanonymousone•6h ago•41 comments

The circuit that lets your brain think and see

https://www.engineering.columbia.edu/about/news/circuit-lets-your-brain-think-and-see
41•hhs•3h ago•6 comments

Soatok's Informal Guide to Threat Models

https://soatok.blog/2026/06/30/soatoks-informal-guide-to-threat-models/
32•zdw•1h ago•2 comments

Amsterdam invented the fire department

https://worksinprogress.co/issue/how-amsterdam-invented-the-fire-department/
44•zdw•3h ago•11 comments

Jamesob's guide to running SOTA LLMs locally

https://github.com/jamesob/local-llm
283•livestyle•11h ago•126 comments

Applied Category Theory Course (2018)

https://math.ucr.edu/home/baez/act_course/index.html
59•measurablefunc•5h ago•7 comments

Espionage Against the European Parliament

https://citizenlab.ca/research/member-of-committee-investigating-spyware-hacked-with-pegasus/
276•ledoge•5h ago•67 comments

New serious vulnerabilities spiked around release of Claude Mythos Preview

https://epoch.ai/data-insights/cve-severity-spike
51•cubefox•5h ago•10 comments

Dispersion loss counteracts embedding condensation in small language models

https://chenliu-1996.github.io/projects/LM-Dispersion/
22•E-Reverance•3h ago•5 comments

Costco is the anti-Amazon

https://phenomenalworld.org/analysis/the-anti-amazon/
319•bookofjoe•11h ago•293 comments

Scientists discover guidance system for migratory songbirds

https://news.exeter.ac.uk/faculty-of-environment-science-and-economy/scientists-discover-guidance...
12•bit_economist•2h ago•2 comments

Infracost (YC W21) Is Hiring a Marketing Lead to Shift FinOps Left

https://www.ycombinator.com/companies/infracost/jobs/YTJcFwr-marketing-lead
1•akh•5h ago

We put a Redis server inside our runtime

https://encore.dev/blog/redis-runtime
24•eandre•2d ago•7 comments

Factories are just rooms

https://interconnected.org/home/2026/07/03/factories
200•arbesman•11h ago•78 comments

International chess federation sanctions Kramnik

https://www.fide.com/fide-ethics-disciplinary-commission-issues-a-decision-in-case-involving-gm-v...
128•DarkContinent•9h ago•66 comments

Software, from First Principles

https://fazamhd.com/mental-models/software/
40•faza•5h ago•8 comments

Africans Are Turning to Starlink

https://www.economist.com/middle-east-and-africa/2026/07/02/africans-are-turning-to-starlink
111•bookofjoe•5h ago•117 comments

Hunting a 16-year-old SQLite WAL bug with TLA+

https://ubuntu.com/blog/hunting-a-16-year-old-sqlite-bug-with-tla-is-dqlite-affected
172•peterparker204•3d ago•14 comments

Notes from Building Tinkerfont

https://mighil.com/notes-from-building-tinkerfont
11•surprisetalk•2d ago•0 comments

FreeBSD ate my RAM

https://crocidb.com/post/freebsd-ate-my-ram/
88•theanonymousone•7h ago•38 comments

Show HN: A statically typed, cross-platform, easily bootstrappable build system

https://github.com/rochus-keller/BUSY/
5•Rochus•3d ago•0 comments

Wordgard: In-browser rich-text editor from the creator of ProseMirror

https://wordgard.net/
266•indy•17h ago•90 comments

You can get Unicode working on DOS

https://twitter.com/i/status/2071469740141224272
12•vkaku•2d ago•4 comments

GitFut – Your GitHub stats turned into a World-Cup-style player card

https://gitfut.com
20•redbell•3h ago•9 comments

PostgreSQL and the OOM killer: Why we use strict memory overcommit

https://www.ubicloud.com/blog/postgresql-and-the-oom-killer-why-we-use-strict-memory-overcommit
158•furkansahin•13h ago•86 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?