frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

RIP, Harvest

https://aphyr.com/posts/427-rip-harvest
257•zdw•4h ago•76 comments

KetchUp – Open-source SketchUp alternative built with Rust and WebGPU

https://ketchup3d.github.io/app/
361•dcoulmbe•7h ago•95 comments

Unlocking any car from X brand in most of the world

https://shubs.io/unlocking-any-car-from-x-brand-in-most-of-the-world/
203•infosecau•6h ago•72 comments

Apple capped engineers at a $200 daily AI budget

https://www.stork.ai/newsletter/2026-11-08-apple-capped-engineers-at-a-200-daily-ai-budget#story-1
12•GloVin•49m ago•8 comments

A Critique of GPUI

https://blog.zortax.de/posts/a-critique-of-gpui
55•ByteAtATime•2h ago•23 comments

Chimera Vocal Synth

https://chimera-vocal-synth.vercel.app/
164•nmstoker•7h ago•23 comments

Declarative Dragging

https://declarative-dragging.github.io/
457•smusamashah•4d ago•59 comments

I'm not convinced the AI bubble exists

https://matteoraso.github.io/im-not-convinced-the-ai-bubble-exists.html#im-not-convinced-the-ai-b...
142•matteoraso•6h ago•201 comments

Dux: Free, open-source Wayland desktop shell with file manager and theming

https://duxlabs.dev/
242•indigodaddy•11h ago•76 comments

Nvidia CEO Jensen Huang's letter to staff about affair

https://nvidianews.nvidia.com/news/a-message-to-our-company
501•karimf•7h ago•543 comments

Ask HN: What are you working on? (November 2026)

182•david927•8h ago•618 comments

Outlook.com is rejecting email from domains without DMARC

https://mailroute.net/blog/outlook-rejecting-email-without-dmarc
336•xmddmx•10h ago•254 comments

The Qlobe: Rotating Quine (2010)

http://mamememo.blogspot.com/2010/09/qlobe.html
15•niceguitars•3h ago•0 comments

Ask HN: How do you manage your AI agents' context across clients and projects?

39•Michel_Aventin•1d ago•30 comments

Show HN: JavaScript web apps with WASM layout and GPU rendering in 280 KB

https://github.com/rkaehn/uniform
18•rkaehn•2d ago•4 comments

Branching Beyond Leonardo: The Evolution of Tree Architecture Theory

https://blue-continuum.com/branching-beyond-leonardo
10•dnetesn•2d ago•0 comments

When a language's creator and its owners strongly disagree [pdf]

https://isocpp.org/files/papers/P4454R0.pdf
105•acossta•6h ago•91 comments

Goldman Sachs is pulling Claude Code from its bankers and traders

https://www.thestateofai.com/news/goldman-sachs-claude-code-traders-bankers
695•TheWiggles•12h ago•384 comments

The Web Is More Than Enough, by Paul Ford

https://ftrain.com/aboard-the-web-is-more-than-enough
113•edward•10h ago•63 comments

Llama-modchip: 284B DeepSeek on 64GB RAM, no GPU

https://github.com/synchopate/llama-modchip
402•joshcsimmons•19h ago•180 comments

Show HN: My compact, bio inspired distributed edge detection algorithm

https://github.com/RenderBear/haci
3•RenderBear•4d ago•0 comments

Writing as a thinking tool

http://muratbuffalo.blogspot.com/2026/11/writing-as-thinking-tool.html
322•jruohonen•19h ago•84 comments

Ur-Nammu Founder of the Sumerian Renaissance

https://www.worldhistory.org/Ur-Nammu/
6•Bluestein•1d ago•0 comments

Air holes turn silicon wafers into flat UV focusing mirrors for compact optics

https://phys.org/news/2026-11-air-holes-silicon-wafers-flat.html
42•bookofjoe•1d ago•5 comments

How I Fight AI Brain Fry

https://sergeykuhne.com/blog/fighting-ai-brain-fry
206•kyunez•10h ago•158 comments

A Bit about Email

https://maurycyz.com/misc/email/
17•vinhnx•3h ago•2 comments

Goodbye Claude, hello Pi

https://caleb.software/posts/claude-to-pi.html
728•karagenit•1d ago•450 comments

Playing with the STM32MP2

https://serd.es/2026/11/08/playing-with-stm32mp2.html
53•dverlaeckt80•11h ago•32 comments

JIT bitmap text rendering for microcontrollers

https://linebender.org/blog/jit-bitmap-text/
96•dmit•19h ago•20 comments

Claude Code's "Don't Ask Again" exposes passwords in 1,122 public GitHub files

https://apiiro.com/blog/coding-agents-leaking-secrets-github-dont-ask-again
599•shmulc•1d ago•407 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?