frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Mario Meets Pareto

https://www.mayerowitz.io/blog/mario-meets-pareto
39•theanonymousone•1h ago•3 comments

How to Make a Nintendo 64 Game in 2026

https://phoboslab.org/log/2026/08/xibalba64-making-of
216•atan2•1d ago•68 comments

Crime Pays but Botany Doesn't

https://www.crimepaysbutbotanydoesnt.com/reading-list
336•DarkContinent•8h ago•115 comments

Pareto Front

https://en.wikipedia.org/wiki/Pareto_front
62•binyu•1w ago•26 comments

Show HN: Skyline Co-op is like SimTower, but built around democratic socialism

https://intergalacticrobots.app/skyline-coop/
13•geekamongus•1h ago•13 comments

Discovery Loop

https://www.discoveryloop.com/
793•xtreak29•20h ago•495 comments

On non-rooted Android 17, ADB uninstall of system apps fails

https://github.com/Universal-Debloater-Alliance/universal-android-debloater-next-generation/issue...
98•microtonal•6h ago•41 comments

Changes at Google DeepMind: Demis Hassabis from CEO to Chair, Jeff Dean departs

https://blog.google/company-news/inside-google/message-ceo/next-chapter-ai-momentum/
709•colesantiago•20h ago•761 comments

Zed DeltaDB

https://zed.dev/deltadb
461•ahamez•18h ago•250 comments

The title cards in Blade Runner are amazing

https://randsinrepose.com/archives/blade-runner-title-cards/
314•ExMachina73•15h ago•151 comments

Branchless Rust: Making a Filter 4x Faster by Removing an If

https://www.greyblake.com/blog/branchless-rust/
215•greyblake•3d ago•66 comments

Beating GPT-5.6 Sol on retrieval with 100x cheaper open models

https://neon.com/blog/how-castform-neon-beats-frontier-models-on-price-and-efficiency
346•moonikakiss•18h ago•84 comments

Muse Code and Muse Spark 1.2

https://research.meta.ai/blog/introducing-muse-code-and-muse-spark-1-2
273•paulkrush•17h ago•174 comments

Born Against, or why hobby programming communities are against LLM usage

https://blog.fogus.me/llm/born-against.html
305•lladnar•18h ago•321 comments

Cloudflare OS: an open platform for agents, apps, and work

https://blog.cloudflare.com/cloudflare-os/
584•speckx•22h ago•280 comments

Unearthing my 1996 windowed OS in machine code for Am29000 homebrew computer

https://nanochess.org/the_am29000_computer.html
51•nanochess•5d ago•2 comments

Prime Agent: A self-improving RLM agent

https://www.primeintellect.ai/blog/prime-agent
195•Xeophon•15h ago•44 comments

Join Me in Jamverse

https://contraptions.venkateshrao.com/p/join-me-in-jamverse
3•surprisetalk•6d ago•0 comments

Let's all meet up in the Y2K

https://blog.gingerbeardman.com/2026/08/06/lets-all-meet-up-in-the-y2k/
88•msephton•6h ago•53 comments

NVIDIA’s Vera Whitepaper Has a Thread Loose

https://chipsandcheese.com/p/nvidias-vera-whitepaper-has-a-thread
149•pella•15h ago•32 comments

Quantego: A Family of Lego Models of IBM Quantum Computers

https://quantego.org/
41•rbanffy•6d ago•20 comments

Atlassian Rovo Exfiltrates Data, Bypassing Controls

https://www.promptarmor.com/resources/atlassian-rovo-exfiltrates-data
253•hackerBanana•19h ago•101 comments

Celld: Self-hosted, distributed Durable Objects

https://github.com/denoland/celld
237•calvinfo•20h ago•40 comments

GNU Hurd News 2026-Q2

https://www.gnu.org/software/hurd/news/2026-q2.html
191•plaguna•3d ago•129 comments

Morioka Shoten

https://www.takram.com/projects/a-single-room-with-a-single-book-morioka-shoten
22•skogstokig•5d ago•10 comments

Launch HN: HyperProbe (YC S26) – Agents that do read-only debugging in prod

https://www.hyperprobe.co
59•shailendraht•20h ago•42 comments

Decimen Optical Transfer: fountain-coded QR file transfer

https://github.com/bashalarmistalt/decimen-optical-transfer
34•ksec•2d ago•29 comments

I'm switching my phone from Android to Linux

https://runarcn.no/android-to-linux/
372•speckx•17h ago•379 comments

Nashville uses eminent domain to block data center near zoo

https://www.costar.com/article/970809918/nashville-council-approves-eminent-domain-action-to-halt...
268•mapping365•10h ago•331 comments

Position: LLMs Can't Jump

https://openreview.net/challenge?redirect=%2Fforum%3Fid%3DklU4737opt
287•theanonymousone•1d ago•188 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?