frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Stateless MCP has recaptured my interest

https://simonwillison.net/2026/Jul/31/stateless-mcp/
228•tosh•4d ago•118 comments

Helsinki Hacker News Meetup

https://calpaterson.com/helsinki-hn.html
23•calpaterson•1h ago•6 comments

“Gravity is worth asking about”

https://unsung.aresluna.org/gravity-is-worth-asking-about/
91•nozzlegear•6d ago•52 comments

Pi's Minimalism Is Its Advantage

https://earendil.com/posts/pi-autoresearch-and-databricks/
378•luispa•12h ago•160 comments

Mistral's Shieldstral: 3B open-weights model for multimodal moderation

https://mistral.ai/news/shieldstral/
426•riadsila•17h ago•109 comments

Show HN: Simple algorithm and color space to generate diverse skin tones

https://toneyalexander.github.io/inclusive-color-space/
538•automatoney•19h ago•93 comments

Zero-Mem: Zero-Token Memory Operations for LLM Agents

https://arxiv.org/abs/2607.29377
43•theanonymousone•5h ago•9 comments

The Pneumatics of Hero of Alexandria (1851)

https://www.thehopkinthomasproject.com/TheHopkinThomasProject/TimeLine/Wales/Steam/URochesterColl...
32•gregsadetsky•4d ago•2 comments

The software group Palantir paid just £2M in corporation tax in the UK in 2024

https://www.theguardian.com/technology/2026/aug/05/palantir-corporation-tax-uk-2024-accounting-pr...
22•igortru•57m ago•11 comments

IP and DNS Leaks in WebKit Affecting Proxy Browsers and iCloud Private Relay

https://mysk.blog/2026/08/04/webkit-proxy-icloud-private-relay-ip-leak/
116•lapcat•11h ago•16 comments

Show HN: Maple-Preview – Ternary 20B MoE running at 120 tok/s on a iPhone

https://deepgrove.ai/maple-preview
123•edwardbzhang•14h ago•36 comments

In Memory of My Wife, Elise Cawley, with Thanks for 36 Wonderful Years

https://writings.stephenwolfram.com/2026/08/in-memory-of-my-wife-elise-cawley-1961-2026-with-than...
1376•jdcampolargo•15h ago•80 comments

DuckDB – Data power tools for your laptop, now in Clojure (2023)

https://techascent.com/blog/just-ducking-around.html
111•sourdecor•12h ago•17 comments

Rio-vt and librio: Rio's terminal engine, now embeddable

https://rioterm.com/blog/2026/07/27/rio-vt-and-librio
36•vinhnx•1w ago•12 comments

Eight Myths on Software Engineering and GenAI

https://queue.acm.org/detail.cfm?id=3807963
217•tchalla•10h ago•180 comments

Bugtraq is back

https://lists.securityfocus.com/hyperkitty/list/bugtraq@securityfocus.com/thread/CHKLXLA7SJEWLDFH...
49•bashtoni•10h ago•14 comments

Birduino: A card-triggered audio player for [learning] the birds

https://hannahilea.com/blog/birduino/
3•austinallegro•5d ago•0 comments

AI fuels more than half of cybercrime in Africa as scams surge – Interpol

https://www.africanews.com/2026/08/04/ai-fuels-more-than-half-of-cybercrime-in-africa-as-digital-...
247•bookofjoe•12h ago•192 comments

We finally learned to center a div, then browsers added sidebars

https://seg6.space/posts/center-div/
137•seg6•12h ago•116 comments

An SLM trained on $8 ESP32-S3

https://github.com/Carloscodix/qapla
33•pavelai•6h ago•10 comments

There Will Come Soft Rains (1950) [pdf]

https://users.wpi.edu/~zrbutzke/Docs/BradburyStories(1).pdf
388•pmg101•1d ago•402 comments

libexpat now funded by the City of Munich for up to 6 months

https://blog.hartwork.org/posts/libexpat-city-of-munich-open-source-sabbatical/
283•spyc•11h ago•64 comments

Video2NAND – Abusing video codecs for great computational power

https://sharedobject.blog/posts/vp8-combinatorial-logic/
66•firer•2d ago•13 comments

Waymo in Dallas

https://waymo.com/blog/shorts/dallas-open-to-all/
295•xnx•16h ago•525 comments

Colorimeter 3nh CR4501 RAL Hack

https://github.com/hallko1234/cr4501-ral-hack
10•Jimmc414•4d ago•3 comments

Flowise is shutting down

https://flowiseai.com/sunset
50•llmgraph•10h ago•34 comments

Godox Transparent Viewfinder Camera C100

https://www.godox.com/product-e/C100.html
43•routeroff•1d ago•26 comments

Xbox goes down. You can't play games you own on disc

https://birchtree.me/blog/xbox-goes-down-you-cant-play-games-you-own-on-disc/
661•surprisetalk•22h ago•691 comments

Show HN: SIMD Viterbi Decoder in Rust

https://github.com/brian-armstrong/fec
47•brian-armstrong•11h ago•6 comments

Why is it all in the kernel?

https://lawrencecpaulson.github.io//2026/07/30/Collatz.html
40•ibobev•4d ago•12 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?