frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

YouTuber Says Cops Visited Him After He Built a Flock-Style Camera to Track Cops

https://gizmodo.com/youtuber-says-cops-paid-him-a-visit-after-he-built-flock-style-camera-to-trac...
113•gumby•41m ago•42 comments

No Man Is an Island

https://borretti.me/article/no-man-is-an-island
156•zetalyrae•1h ago•70 comments

Cloudflare acquires Deno

https://deno.com/blog/cloudflare
948•ilreb•8h ago•502 comments

Triple-A Minesweeper

https://minesweeper.mikelacher.com/
383•robin_reala•5h ago•82 comments

Show HN: Carrier-Explode: iPhone, Pixel and Galaxy carrier settings decoded

https://carrierexplode.com/
135•simplyalec•3h ago•14 comments

Our $445M Series D

https://oxide.computer/blog/our-445m-series-d
529•ahlCVA•8h ago•227 comments

Typesafe AI raises $870M at $7.5B

https://typesafe.ai/blog/series-ai
194•tosh•4h ago•156 comments

Ideas aren't getting harder to find, anyone who tells you otherwise is a coward

https://www.experimental-history.com/p/ideas-arent-getting-harder-to-find
72•rafaelc•3h ago•24 comments

Sorry, I'm in a meeting

https://iminafleeting.com/
670•splintersio•12h ago•215 comments

Pointing AI at archives found a forgotten meteorite, lost rhinos, and more

https://jessewaites.com/blog/post/i-pointed-ai-at-400-years-of-archives/
73•piratebroadcast•10h ago•37 comments

Show HN: Let your AI agents paint big arrows, boxes and text on your screen

https://github.com/franzenzenhofer/big-arrow-on-the-screen
349•franze•10h ago•149 comments

Nobel Peace Prize for 2026 to Navanethem Pillay

https://www.nobelprize.org/prizes/peace/2026/press-release/
406•Anon84•11h ago•208 comments

M7.6 Earthquake in Panama

https://earthquake.usgs.gov/earthquakes/eventpage/us6000u18k/executive
104•gslin•3h ago•33 comments

'Wallace and Gromit,' 90% Alone

https://animationobsessive.substack.com/p/wallace-and-gromit-90-alone
108•vinhnx•7h ago•15 comments

Why isn't the industry freaking out about DeepSeek 4.1 Flash?

https://www.dgt.is/blog/2026-10-07-deepseek-freek-out/
1062•jonotime•1d ago•934 comments

Microsoft-Decision-1, our model for fast decision-making

https://commandline.microsoft.com/microsoft-decision-1-model-foundry/
83•lisajaloza•3h ago•28 comments

Whistle: Speech to Text in 16.9 MB

https://cactuscompute.com/blog/whistle
911•gmays•1d ago•176 comments

Training Text-to-Image Models Without a VAE

https://www.linum.ai/field-notes/pyramid-jit
42•schopra909•3d ago•14 comments

Germany transforms former coal mines into Europe's largest lake landscape

https://www.euronews.com/2026/04/14/almost-like-lake-como-germany-transforms-former-coal-mines-in...
163•ohjeez•6h ago•89 comments

A statement on the Tor Project's relationship with Mullvad

https://blog.torproject.org/on-tor-relationship-with-mullvad/
81•runtimewire•5h ago•174 comments

Show HN: The rarest tech books and docs you've probably never read

https://readrare.com/
21•miletus•4h ago•3 comments

Yes, and

https://htmx.org/essays/yes-and/
714•Michelangelo11•1d ago•281 comments

The reciprocal sum of the prime-prefix-free numbers converges [pdf]

https://jdb19937.github.io/prime-prefix-free/ppf.pdf
16•jdb1729•4d ago•15 comments

You might want to try being less creative

https://blog.bawolf.com/p/you-might-want-to-try-being-less
47•bryantwolf•3h ago•23 comments

Keyboard differences between Windows and Macs

https://unsung.aresluna.org/deeper-dive-keyboard-differences-between-windows-and-macs/
310•sohkamyung•18h ago•253 comments

OpenAI fires three safety researchers for "mishandling research information"

https://techcrunch.com/2026/10/08/fired-openai-safety-researchers-dispute-misconduct-claims-warn-...
282•trakkstar•11h ago•185 comments

MXC - a sandboxed code execution system

https://github.com/microsoft/mxc
165•nreece•15h ago•78 comments

Programming Isn't Special

https://blog.glyph.im/2026/10/programming-isnt-special.html
148•ingve•14h ago•165 comments

Why Are Coding Agents So Dumb?

https://mtlynch.io/why-are-coding-agents-so-dumb/
47•mtlynch•7h ago•20 comments

Theranos.world

https://www.theranos.world/
540•kbyatnal•1d ago•199 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?