frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Jamesob's guide to running SOTA LLMs locally

https://github.com/jamesob/local-llm
151•livestyle•4h ago•63 comments

Costco is the anti-Amazon

https://phenomenalworld.org/analysis/the-anti-amazon/
77•bookofjoe•4h ago•29 comments

Factories are just rooms

https://interconnected.org/home/2026/07/03/factories
105•arbesman•4h ago•48 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
110•peterparker204•3d ago•6 comments

Show HN: Mcpsnoop – Wireshark for MCP (transparent proxy and live TUI)

https://github.com/kerlenton/mcpsnoop
22•kerlenton•2h ago•4 comments

My dad helped build North America's oat supply chain: Can it be remade?

https://ambrook.com/offrange/perspective/how-we-lost-our-oats
58•surprisetalk•3d ago•25 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
121•furkansahin•6h ago•46 comments

Best Simple System for Now (2025)

https://dannorth.net/blog/best-simple-system-for-now/
55•daan-k•4h ago•11 comments

Valve open-source the Steam Machine e-ink screen so you can make your own

https://www.gamingonlinux.com/2026/07/valve-open-source-the-steam-machine-e-ink-screen-so-you-can...
425•ahlCVA•6h ago•72 comments

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

https://wordgard.net/
202•indy•10h ago•75 comments

Instead of banning AI, I made a classroom contract with my students

https://www.science.org/content/article/instead-banning-ai-i-made-classroom-contract-my-students
25•digital55•5h ago•5 comments

60% Fable cost cut by converting code to images and having the model OCR it

https://github.com/teamchong/pxpipe
112•dimitropoulos•3h ago•40 comments

Half-Baked Product

https://weli.dev/blog/half-baked-product/
1092•weli•11h ago•338 comments

The Fall and Rise of Screwworm

https://www.construction-physics.com/p/the-fall-and-rise-of-screwworm
95•crescit_eundo•6h ago•41 comments

Flexible metaprogramming with Rhombus

https://lwn.net/SubscriberLink/1079001/67840550991151ed/
66•spdegabrielle•1d ago•1 comments

The Life and Times of Maxis, Part 1: SimEverything

https://www.filfre.net/2026/07/the-life-and-times-of-maxis-part-1-simeverything/
77•doppp•3h ago•4 comments

Ask HN: Is anyone experimenting with different ways of using LLMs for coding?

47•yehiaabdelm•13h ago•64 comments

International chess federation sanctions Kramnik

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

Supersonic flight returning to US after half-century ban

https://www.forbes.com/sites/suzannerowankelleher/2026/06/30/faa-supersonic-flight-no-boom/
119•lobbly•2d ago•140 comments

America, 1926: A forgotten 100-year-old report

https://www.derekthompson.org/p/america-1926-an-absurdly-deep-dive
92•momentmaker•4h ago•116 comments

Anatomy of Persistent Memory's 3 Layers: Comparing ContextNest, Mem0 and Zep

https://promptowl.ai/resources/persistent-memory-ai-agents/
21•sparkystacey•5h ago•2 comments

A Cali. farmer is giving away tons of nectarines that he's not allowed to sell

https://apnews.com/article/california-farmer-nectarines-lawsuit-patent-4f7bc8ab185e8b9cbdd6d6ad4f...
4•djoldman•1h ago•0 comments

Closer to Rude Than Snide: An Interview with Leo Robson

https://www.theideasletter.org/essay/closer-to-rude-than-snide/
3•lermontov•3d ago•0 comments

Program-as-Weights: A Programming Paradigm for Fuzzy Functions

https://arxiv.org/abs/2607.02512
40•simonpure•6h ago•4 comments

Show HN: ctx – Search the coding agent history already on your machine

https://github.com/ctxrs/ctx
50•luca-ctx•1d ago•22 comments

Show HN: Bramble – Local-first password manager

https://github.com/flythenimbus/bramble
85•MegagramEnjoyer•1d ago•16 comments

The Safari MCP server for web developers

https://webkit.org/blog/18136/introducing-the-safari-mcp-server-for-web-developers/
234•coloneltcb•17h ago•65 comments

Holes

https://xkcd.com/3266/large/
26•caminanteblanco•1h ago•3 comments

I Wasn't Allowed Prompting ChatGPT During My Chalk Talk: This Is Discrimination

https://inpreparation.substack.com/p/opinion-i-was-not-allowed-to-type
80•theanonymousone•1h ago•50 comments

crustc: entirety of `rustc`, translated to C

https://github.com/FractalFir/crustc
369•Philpax•20h ago•82 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?