frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Reasons to Dislike AI Coding

https://www.sicpers.info/2026/10/reasons-to-dislike-ai-coding/
31•signa11•55m ago•33 comments

Sharing AI progress in mathematics

https://openai.com/index/sharing-ai-progress-in-mathematics/
921•OfficialTurkey•11h ago•861 comments

A font recreated from photographs of classic Commodore 64 keycaps

https://github.com/szabadkai/c64-keyboard-font/
18•sohkamyung•52m ago•3 comments

Strands Decider 2B: a small, open-source, decision model

https://strandsagents.com/blog/introducing-strands-decider/
177•gmays•8h ago•45 comments

Decisions API is in public beta

https://developers.openai.com/api/docs/guides/decisions
300•chiefstorm•13h ago•141 comments

The art of defusing a second world war bomb

https://www.theguardian.com/news/ng-interactive/2026/oct/06/it-could-knock-a-whole-street-down-th...
67•sandebert•6h ago•36 comments

Mistral Large 4

https://mistral.ai/news/mistral-large-4/\
1817•Philpax•20h ago•1082 comments

Shaders, WebGPU Components for React, Vue, Svelte, Solid, JavaScript and Framer

https://github.com/shader-effects-inc/shaders
29•jinqueeny•4h ago•13 comments

EmbeddingGemma 2: An open, lightweight multimodal embedding model

https://blog.google/innovation-and-ai/technology/developers-tools/embeddinggemma-2/
331•ilreb•18h ago•35 comments

ESP32-C3 Adblock

https://github.com/M-Abozaid/esp32-c3-adblock
99•jayhoon•8h ago•36 comments

What is Codemode

https://lucumr.pocoo.org/2026/10/6/codemode/
84•Tomte•20h ago•40 comments

The Legend of the Paper Crane

https://mazdastories.com/en_us/inspire/paper-cranes-into-the-fold/
18•vismit2000•2d ago•4 comments

The cost of lies: A Mineserver story

https://www.jeremyreimer.com/rockets-item.lsp?f=true&p=272
112•luu•3d ago•49 comments

La Cueva BBS in Mexico in 1993 (session replay)

https://nanochess.org/la_cueva_bbs.html
52•nanochess•6h ago•13 comments

Tell HN: GitHub refuses to remove cracked copies of my software after a month

246•IvanK_net•15h ago•141 comments

Penguin Mail – open-source Rust email client for Linux with AI

https://penguin-mail.com/
183•kavourias•12h ago•114 comments

Claude Code’s suggested message feature: I think the real customer is the model

https://www.zohaib.cc/blog/smartest-claude-code-feature
201•zed_labs_dev•16h ago•116 comments

Gallery of Processor Cache Effects

https://igoro.com/archive/gallery-of-processor-cache-effects/
12•porridgeraisin•2d ago•0 comments

OpenTPU – An open-source AI accelerator, developed by AI

https://github.com/FeSens/openTPU
289•fsbonetto•17h ago•340 comments

What's Earth's dominant species by mass?

https://signoregalilei.com/2026/09/27/whats-earths-dominant-species-by-mass/
246•surprisetalk•21h ago•181 comments

Treg (OpenRouter for Tools)

https://github.com/superdesigndev/treg
33•trollied•17h ago•6 comments

Show HN: NanoMuse – An open-source AI agent for your phone and computer

https://github.com/nano-muse/nanoMuse
20•ilreb•6h ago•4 comments

AnyPS5: Port PS5 binaries to PC without emulation (87% system libraries mapped)

https://github.com/boykopovar/AnyPS5
262•Fe2O3•10h ago•222 comments

State of Devs 2026

https://2026.stateofdevs.com/en-US/
170•sgdesign•10h ago•87 comments

Hackers obtain counterfeit TLS certificates for Google and other large services

https://arstechnica.com/security/2026/10/hackers-obtain-counterfeit-tls-certificates-for-google-a...
72•colinprince•5h ago•22 comments

When random is not actually random enough

https://ersc.io/blog/when-random-isnt-random-enough
66•steveklabnik•13h ago•31 comments

First Steps into Memory Management in Python

https://tech.daniellbastos.com.br/posts/python-memory-management/
3•shellpipe•1d ago•0 comments

California closed the Montana license plate loophole

https://www.thedrive.com/news/heres-how-california-closed-the-montana-license-plate-loophole
113•speckx•17h ago•280 comments

Sharded, encrypted storage between friends over Yggdrasil

https://github.com/peterretief/yggstore
9•peter_retief•4h ago•3 comments

Benchmark in Milliseconds

https://matklad.github.io/2026/10/05/benchmark-milliseconds.html
142•surprisetalk•1d ago•47 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?