frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Outages reported at Bank of America, Chase, U.S. Bank, Wells Fargo and Zelle

https://apnews.com/article/bank-outage-chase-wells-fargo-truist-50fee2693c22f597fa6ca51a97ef2cda
599•samk3nny•3h ago•459 comments

BugMeNot Has Closed

https://www.bugmenot.com/
76•lode•35m ago•37 comments

Rust changed me as a developer

https://blog.startifact.com/posts/how-rust-changed-me/
67•speckx•1h ago•26 comments

Grazing sheep in fields with solar arrays

https://news.cornell.edu/stories/2026/10/sheep-grazing-solar-fields-offers-farmers-economic-ecolo...
169•PaulHoule•4h ago•140 comments

Jiff 1.0: A datetime library for Rust

https://burntsushi.net/jiff/
252•burntsushi•5h ago•54 comments

Carnegie Mellon is putting computer science courses on YouTube for free

https://www.cs.cmu.edu/learn/
37•pcompeau•1h ago•7 comments

Frame – 31.5" color ePaper display

https://trmnl.com/blog/introducing-frame
224•geerlingguy•5h ago•144 comments

Spamhaus new email sender requirements in November

https://www.spamhaus.org/sender-guidelines/
7•computer23•19m ago•3 comments

Launch HN: Axonnic (YC F26) – Sleeves that track fingers and estimate force

21•arshpatankar•1h ago•5 comments

Squircles

https://linebender.org/wiki/curves/squircle/
67•raphlinus•14h ago•24 comments

Chemistry Is Geometry

https://chillphysicsenjoyer.substack.com/p/chemistry-is-actually-geometry
17•sebg•1h ago•3 comments

How to Intercept HTTP/3 Traffic: QUIC and Qpack

https://interceptsuite.com/blog/intercept-http3-traffic-quic-qpack-explained/
35•anof-cyber•2h ago•3 comments

Optimizely Compromised

https://amirulcyber.com/2026/11/16/optimjack-optimizely-skimmer/
23•martinald•58m ago•3 comments

The Secret ThinkPad Powerbutton Code to Bring Dead Laptops Back to Life (2007)

https://masnick.com/posts/the-secret-thinkpad-powerbutton-code-to-bring-dead-laptops-back-to-life/
279•sammatilda•10h ago•111 comments

Michael Mann's 'Heat' Copyright Fight Turns on a Deal with Himself

https://copyrightlately.com/michael-mann-heat-copyright-termination/
62•speckx•4h ago•22 comments

My Quest to push native Three.js quality match AAA Game Engines

https://ben3d.ca/blog/building-the-aaa-lighting-pipeline-in-threejs
36•bhouston•59m ago•7 comments

OpenCode Browse

https://opencode.ai/product/browse
8•mfiguiere•46m ago•1 comments

Microsoft blames monster email outage on software defect introduced in July fix

https://www.theregister.com/saas/2026/11/16/microsoft-blames-monster-email-outage-on-software-def...
139•Bender•8h ago•94 comments

Giant Roadside Attractions Face Mounting Costs and an Uncertain Future

https://www.nytimes.com/2026/11/08/world/canada/roadside-attractions-giant-dinosaur.html
27•bookofjoe•6d ago•32 comments

How to make almost anything

https://pub.cba.mit.edu/863.26/site/
810•o4c•16h ago•137 comments

Many of Amazon’s Black Friday and Cyber Monday “deals” offered no savings

http://groundworkcollaborative.org/news/amazons-decoy-deals-groundwork-investigation-reveals-near...
749•DeepLogin•8h ago•463 comments

Jolt – Clojure that speaks C

https://jolt-lang.net/
69•michaelsbradley•5h ago•18 comments

Comcast's "fiber-powered Wi-Fi" is cable, AT&T says in false advertising case

https://arstechnica.com/tech-policy/2026/11/comcast-falsely-advertises-cable-internet-as-fiber-po...
37•jaredwiener•1h ago•26 comments

Software is breaking down at a systemic level

https://www.breck-mckye.com/blog/2026/11/software-is-breaking-down-at-a-systemic-level/
289•zero_shift•3h ago•172 comments

OpenAI: Strengthening the fight against online child sexual abuse

https://openai.com/index/strengthening-online-child-safety/
74•rossant•3h ago•143 comments

Aristotle Expands into Rust

https://www.harmonic.fun/news/aristotle-rust-verification/
80•maufl•4h ago•44 comments

The origins of the placenta

https://www.caltech.edu/about/news/uncovering-the-hidden-origins-of-the-placenta
15•gmays•3d ago•3 comments

Caltech professor no longer grades homework's because everyone uses AI

https://www.businessinsider.com/ai-math-class-university-homework-caltech-careers-2026-11
35•ishanz•1h ago•31 comments

Nvidia was in trouble before the Jensen Huang mess

https://www.wired.com/story/nvidia-was-already-in-trouble-before-the-jensen-huang-mess/
216•Brajeshwar•6h ago•206 comments

OOS – an open operating system for the Rigol Scopes

https://www.eevblog.com/forum/testgear/oos-an-open-operating-system-for-the-rigol-scopes/
122•qwezxcrty•3d ago•36 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?