frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

GitHub Incident with Git Operations, Pull Requests and Actions

https://www.githubstatus.com/incidents/djlmxz2zd0j7
145•gagan2020•1h ago•109 comments

Navier–Stokes Lost in Translation

https://arxiv.org/abs/2610.08144
43•nill0•1h ago•19 comments

Shipping JPEG XL in Chrome

https://developer.chrome.com/blog/jpeg-xl-in-chrome
325•AshleysBrain•5h ago•194 comments

A font recreated from photographs of classic Commodore 64 keycaps

https://github.com/szabadkai/c64-keyboard-font/
274•sohkamyung•7h ago•49 comments

Animated ASCII Art for Web Pages

https://ascii.rest/
42•turrini•1h ago•6 comments

Nobel Prize in Chemistry 2026 to Henri B. Kagan and Kenso Soai

https://www.nobelprize.org/prizes/chemistry/2026/press-release/
210•sasvari•6h ago•35 comments

Show HN: A walkable 3D art history museum built from Wikipedia

https://artmuseum.artfrompixels.com/
84•jasontr•3h ago•42 comments

AI-assisted proof of optimal packing for 11 squares

https://github.com/Queuingtheorydotcom/11SquaresFormalized
33•bluepeter•2h ago•24 comments

Reverse Engineering of the M-VAVE FM-1 Pocket Synthesizer Firmware

https://github.com/AL-255/FM-1-RE
15•0bytes•1h ago•2 comments

Visa, Mastercard, Major Banks Facing New Litigation over 'Anticompetitive' Fees

https://www.classaction.org/news/visa-mastercard-major-banks-facing-new-litigation-over-anticompe...
24•DeepLogin•1h ago•6 comments

Write Like It's 1866: LLMs Relearn Telegraphese

https://fiveminutesforward.com/post/2026-10-04-telegraph-test/
59•Theory42•4h ago•38 comments

Anti-Patterns in Software Blogging

https://refactoringenglish.com/blog/anti-patterns-software-blogging/
46•ilreb•3h ago•12 comments

Mallet Head Angle

http://www.timberframe-tools.com/tools/mallet-head-angle/
49•frogulis•1d ago•15 comments

Google Playground

https://labs.google/playground
96•trollied•2h ago•71 comments

Across the Globe, People Increasingly Say Social Media Is Harming Democracy

https://www.pewresearch.org/global/2026/10/01/across-the-globe-people-increasingly-say-social-med...
43•karakoram•1h ago•23 comments

Rust's derive often implies inline

https://yossarian.net/til/post/rust-s-derive-often-implies-inline/
80•woodruffw•3d ago•13 comments

Study: Claude, ChatGPT Offer Different Shopping Prices Based on Wealth

https://www.bloomberg.com/news/newsletters/2026-10-07/study-claude-chatgpt-ai-bots-offer-differen...
23•sbulaev•33m ago•1 comments

The Auditor's Opinion

https://www.cringely.com/2026/07/16/the-auditors-opinion/
7•colinprince•2d ago•1 comments

Wood Tape (2004)

http://gamesbyemail.com/WoodTape/Default.htm
31•NaOH•1d ago•4 comments

Paramount, Warner Bros Formally Merge, Form Giant Mountain of Disastrous Debt

https://www.techdirt.com/2026/10/07/paramount-warner-bros-formally-merge-form-giant-mountain-of-d...
21•cdrnsf•29m ago•1 comments

Show HN: Procinsh – A 3D Linux process inspector

https://github.com/akawashiro/procinsh
32•a_kawashiro•3h ago•6 comments

ShinyHunters Extorted Boeing Spin-Off Prior to Arrests

https://krebsonsecurity.com/2026/10/shinyhunters-extorted-boeing-spin-off-prior-to-arrests/
7•speckx•1h ago•0 comments

God of War on PSP, recompiled to WebAssembly and running in the browser

https://github.com/snuri00/psp-web-recomp
42•sn001•5h ago•22 comments

Strands Decider 2B: a small, open-source, decision model

https://strandsagents.com/blog/introducing-strands-decider/
256•gmays•14h ago•71 comments

Show HN: AstroHelm – Use your phone camera to aim a telescope or telephoto lens

https://astrohelm.app/
72•HeavenFox•3d ago•22 comments

Sharing AI progress in mathematics

https://openai.com/index/sharing-ai-progress-in-mathematics/
1140•OfficialTurkey•18h ago•1249 comments

Mistral Large 4

https://mistral.ai/news/mistral-large-4/\
1961•Philpax•1d ago•1170 comments

SynthID Detector

https://synthid.com/
58•ilreb•2h ago•57 comments

Tell HN: GitHub refuses to remove cracked copies of my software after a month

461•IvanK_net•21h ago•249 comments

ESP32-C3 Adblock

https://github.com/M-Abozaid/esp32-c3-adblock
167•jayhoon•15h ago•65 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?