frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

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

https://duxlabs.dev/
155•indigodaddy•4h ago•48 comments

Nvidia CEO Jensen Huang's letter to staff about affair

https://www.axios.com/2026/11/08/nvidia-ceo-jensen-huang-affair-email-to-company
184•karimf•1h ago•153 comments

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

65•david927•2h ago•308 comments

Chimera Vocal Synth

https://chimera-vocal-synth.vercel.app/
19•nmstoker•52m ago•6 comments

Declarative Dragging

https://declarative-dragging.github.io/
257•smusamashah•4d ago•30 comments

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

https://ketchup3d.github.io/app/
12•dcoulmbe•53m ago•1 comments

Goldman Sachs is pulling Claude Code from its bankers and traders

https://www.thestateofai.com/news/goldman-sachs-claude-code-traders-bankers
526•TheWiggles•5h ago•320 comments

Outlook.com Is Quietly Rejecting Email from Domains Without DMARC

https://mailroute.net/blog/outlook-rejecting-email-without-dmarc
186•xmddmx•4h ago•151 comments

The Web Is More Than Enough, by Paul Ford

https://ftrain.com/aboard-the-web-is-more-than-enough
39•edward•3h ago•14 comments

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

https://github.com/synchopate/llama-modchip
338•joshcsimmons•13h ago•136 comments

Edward Hopper's Iconic Painting, "Nighthawks

https://lithub.com/the-story-behind-edward-hoppers-iconic-painting-nighthawks/
56•prismatic•4d ago•17 comments

Writing as a thinking tool

http://muratbuffalo.blogspot.com/2026/11/writing-as-thinking-tool.html
255•jruohonen•12h ago•76 comments

Playing with the STM32MP2

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

The History of Djgpp

https://www.delorie.com/djgpp/history.html
28•atan2•5d ago•9 comments

A Little Snitch for Windows

https://packethound.app/
81•BadBoyBubby•6h ago•37 comments

Show HN: Vegetable Gardening for Engineers

https://jrcpl.us/contrib/2020/gardening-for-engineers/
145•jrcplus•4d ago•28 comments

Nvidia Board of Directors Is Investigating Jensen Huang

https://nvidianews.nvidia.com/news/statement-from-nvidia-board-of-directors
320•vincentchau•3h ago•251 comments

How I Fight AI Brain Fry

https://sergeykuhne.com/blog/fighting-ai-brain-fry
120•kyunez•3h ago•108 comments

I'm not a fan of Deno's security model (2024)

https://goldstein.lol/posts/deno-security/
76•maxloh•8h ago•36 comments

Goodbye Claude, hello Pi

https://caleb.software/posts/claude-to-pi.html
669•karagenit•20h ago•423 comments

Porting Android 16 to my blind mother's keypad phone

https://z1x.us/blog/four-hundred-bucks-of-e-waste
143•z1xus•4d ago•42 comments

The Reconstruction of Torn Documents

https://www.bundesarchiv.de/en/stasi-records-archive/the-reconstruction-of-torn-documents/
84•jacquesm•2d ago•48 comments

Starship Flight 15 on 11/13 plans to catch both booster and ship

https://www.spacex.com/launches/starship-flight-15
64•spikels•3h ago•27 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
573•shmulc•1d ago•389 comments

Playing Zork 1 on a CP/M emulator on Linux (2021)

https://kevinboone.me/cpmzork.html
22•linuxkernal•4h ago•12 comments

How to prove equations using diagrams, part 1

https://www.epatters.org/post/e-graphs-1/
58•frostbyte7•10h ago•4 comments

Show HN: SafeScript, a safe version of JavaScript for executing untrusted code

https://github.com/SafeScript/safescript
4•EGreg•2h ago•0 comments

A field guide to CAPTCHA types and how they break

https://github.com/vsmutok/FuckCaptcha
43•vasylsmutok•6h ago•12 comments

Agent memory needs its OpenTelemetry moment

https://www.lorekit.io/blog/open-agent-memory-format
164•mthines•14h ago•102 comments

JIT bitmap text rendering for microcontrollers

https://linebender.org/blog/jit-bitmap-text/
91•dmit•12h ago•17 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?