📰 Tech Trends Daily — Tuesday, November 17, 2026

🔥 Today’s Focus

Today’s real theme is “one change, total shutdown.” A software bug in JPMorgan’s own on-premises hardware dragged Chase, Wells Fargo, and Truist’s online services down together; a United Airlines system failure caused widespread flight delays; and Microsoft attributed its massive email outage to a defect introduced by a July fix. All three happened inside corporate walls, none were cyberattacks, but they share one premise: these services no longer have any external fallback path. On the same day, HN’s “Software is breaking down at a systemic level” framed the problem as an architectural one — when you push 25% of your traffic onto one cloud provider or one SaaS, “not our problem” becomes the most common explanation and the cheapest excuse.

🤖 AI & Models

  • All AI-generated code should be Open Source — All AI-generated code should be Open Source. 73/28 (Lobsters). The argument: models consumed the entire corpus of human-written code, so their output shouldn’t be privatized; new discussion this round centered on “whether training itself constitutes infringement” and license conflicts.
  • 💬 Comments: One reply corrected the most frequently cited precedent — in Thaler v. Perlmutter, the plaintiff explicitly argued the AI was the sole author and sought to register copyright to the model, which has nothing to do with the common scenario of “a human claiming authorship,” so using it to argue “all AI output is uncopyrightable” is a misuse. Another broke down the distinction between “public” and “open source” point by point: code in the public domain doesn’t mean you can freely use the whole repository — others can still claim copyright over the work as a whole.
  • You won’t win at copyright — you won’t win at copyright. 63/7 (Lobsters). The article argues that pinning anti-AI hopes on copyright will fail, and the comments immediately split: some contend copyright is precisely the only enforceable lever GPL has — without copyright, no open-source license could demand anything of users.
  • OpenAI: Strengthening the fight against online child sexual abuse — Strengthening the fight against online child sexual abuse. 81 points / 176 comments (HN). The official post describes the new detection and reporting pipeline; the comment count far exceeding the score shows the controversy centers on false positives and privacy boundaries, not the measures themselves.
  • Launch HN: Axonnic — Launch HN: Axonnic (YC F26) – Sleeves that track fingers and estimate force. 22 points / 7 comments (HN). The founder’s first product chose hand-input simulation, on the grounds that both rehab training and remote operation lack a cheap hand-sensing layer.

🏢 Outages & Systemic Failures

  • JPMorgan technical issue knocks online banking offline at multiple US banks — Technical issue at JPMorgan Chase triggers online banking delays for US banks. 662 points / 524 comments (HN). Cards declined, branches halted, online banking unreachable — Wells Fargo and Truist were hit too, with three chartered banks going down at the same moment.
  • 💬 Comments: Chase’s spokesperson told the media it was “a software bug in our own on-premises hardware systems, unrelated to a cyberattack” — overturning the “moving to cloud is what breaks” intuition: what failed was the self-hosted part. Someone dug up last month’s Revolut incident postmortem (a Google Cloud outage, recovered in 12 hours) for comparison, concluding that whether self-hosted or managed, the single point of failure remains; the only difference is who gets to explain.
  • United Airlines widespread system outage — United Airlines Widespread System Outage. 80 points / 11 comments (HN); (AP version, 38 points / 6 comments (HN)). The same airline’s outage charted on two outlets separately, with the two versions differing slightly on downtime length and impact scope.
  • Microsoft blames massive email outage on a defect introduced by a July fix — Microsoft blames monster email outage on software defect introduced in July fix. 170 points / 117 comments (HN). The faulty code sat in the system for four months before being triggered — that time lag deserves a note more than the outage itself.
  • Software is breaking down at a systemic level — Software is breaking down at a systemic level. 311 points / 192 comments (HN). The author pins the problem on “an anxious and lazy dependency-first culture”: nobody dares write anything themselves anymore, so everyone’s failure modes get merged by the same batch of libraries.
  • 💬 Comments: The top rebuttal challenges the timeline — cloud commercialization began well over a decade ago, so calling ten years ago a golden age is wrong, but “the arc is right”: the real change is that failure points were consolidated — one cloud plus a dozen SaaS providers now carry a quarter of the internet, leaving no coverage zone when things break. Another reply is more direct: across roughly ten web frameworks he’s used over the past fifteen years, not one got HTTP/1.1 routing, path, and header handling right; pinning versions only guards against poisoning, not patch distribution, and SemVer is untrustworthy in practice.
  • FBI has possession of the router the FAA says caused Friday’s ATC meltdown — FBI has possession of router that the FAA says is behind Friday’s ATC meltdown. 11 points / 4 comments (HN). A device entering the evidence chain means the official narrative has already shifted from “software failure” to “not a software failure.”

🔒 Security & Privacy

  • BugMeNot has shut down — BugMeNot Has Closed. 152 points / 80 comments (HN). The old service for bypassing registration walls via shared accounts is offline; many commenters couldn’t even remember the last time they used it — the registration wall itself lost, beaten by phone numbers and social login.
  • Optimizely compromised: card-skimming script injected into checkout pages — Optimizely Compromised. 54 points / 8 comments (HN). Attackers hung their skimming script on an A/B testing platform — such tools are born with the right to inject JavaScript on every page, making them far more cost-effective skimmer carriers than breaching individual e-commerce sites.
  • Spamhaus publishes new sender requirements from November — Spamhaus new email sender requirements in November. 40 points / 30 comments (HN). For self-hosted mailers, this is yet another hard gate to clear: beyond SPF, DKIM, and DMARC there are list-behavior requirements, and non-compliance lands you straight on the blocklist.
  • How to break into security, Ptacek edition (2012) — How to Break into Security, Ptacek Edition. 42 points / 7 comments (HN). Fourteen-year-old advice charting again; the core still holds — “learn to write code first, then talk offense and defense” — though the hands-on projects it recommended have cycled through a full generation.
  • Universal XSS in uBlock Origin from website-driven element picker — Universal XSS in uBlock Origin from website-driven element picker. 34/0 (Lobsters). The flaw lives in the extension’s own UI channel: a page can influence the blocker’s element-picking flow — the classic “the protection tool itself becomes the entry point” category.
  • NoisyTCP: a side channel in kernel TCP — NoisyTCP. 14/1 (Lobsters). Infers normally invisible connection states via timing noise; worth watching for its actual impact on shared-hosting scenarios.

🛠️ Tools & Infrastructure

  • Frame: a 31.5” color ePaper display — Frame – 31.5” color ePaper display. 245 points / 166 comments (HN). TRMNL’s new product, with a wooden frame built in-house; about 470 units in the first batch, most shipping in early 2027.
  • 💬 Comments: Discussion ran from “why is ePaper still so expensive” all the way to shelf labels — supermarkets in the UK, Canada, Hungary, and the Nordics already use them, prices passed the tipping point long ago, and only large panels remain stuck on patents and capacity. On the technical side, the consensus is this display is passive, burn-in-free, and holds a frame indefinitely, but continuous animation caps out at single-digit frame rates.
  • Jiff 1.0: Rust’s datetime library hits stable — Jiff 1.0: A datetime library for Rust. 272 points / 58 comments (HN); 128/31 (Lobsters). BurntSushi promises long-term support for this release; the truly scarce part is what follows: timezone data, calendar arithmetic, and serialization formats locked in once, no more churn.
  • 💬 Comments: A developer who maintained chrono for about five years commented that he took over precisely because the API was bad, only to find users just wanted stability — every improvement met resistance, and he eventually left from burnout; chrono’s original author replied confirming the burnout and thanking his successor. BurntSushi himself also chimed in to clarify design lineage — directly modeled on JS’s Temporal, not Java 8’s java.time, with the inspired-by section listing it clearly.
  • Migrating a project from GitHub to Codeberg — Migrating from GitHub to Codeberg. 63/18 (Lobsters). The author turned the migration into a checklist, including what simply can’t be moved.
  • 💬 Comments: The practical problems are harder than migration scripts — one commenter was burned by Codeberg’s availability, hitting more downtime than GitHub whenever access was needed; others argue a forge’s core is really the issues, PRs, and landing page, with git a small piece of it — those who only want git could push to any sshd box.
  • OpenCode Browse — OpenCode Browse. 39 points / 17 comments (HN). The coding-agent product line takes a step toward “seeing the web,” making browser sessions a controllable input for agents rather than a casually-granted permission.
  • Intercepting HTTP/3 traffic: QUIC and QPACK explained — How to Intercept HTTP/3 Traffic: QUIC and Qpack. 44 points / 3 comments (HN). Breaks down QUIC’s connection migration, encryption boundaries, and QPACK header compression; a proxy-tool author’s perspective beats the protocol spec.
  • Quality IMAP, Part 1: your mailbox is a database — Quality IMAP, Part 1: Your Mailbox Is A Database. 15/5 (Lobsters). Notes from the Deuxfleurs team’s self-hosted mail project, mapping IMAP semantics onto a relational model — reads like an exercise in demystification.
  • funkycache: caching Python functions in SQLite — funkycache: a Python library to cache functions in SQLite. 8/0 (Lobsters). No Redis, no in-process memory — the cache survives across processes, suited to scripts and single-machine services.
  • beer.drv.drv.drv — beer.drv.drv.drv. 25/6 (Lobsters). Uses Nix’s derivation build process to deconstruct “a bottle of beer” — looks like a joke, but actually explains build graphs clearly.
  • A local mirror for FreeBSD pkgbase — Local Mirror for FreeBSD pkgbase. 5/1 (Lobsters). An essential ops step once the base system is split into packages, still at the DIY stage.
  • Eight years of running DocSpring on Convox — Eight years of running DocSpring on Convox. 6 points / discuss (HN). A small team’s eight-year platform-choice retrospective; the conclusion is that the cost of switching has always exceeded the cost of tolerating it.

💻 Languages & Programming

  • Rust changed me as a developer — Rust changed me as a developer. 120 points / 62 comments (HN); 11/0 (Lobsters). The author reflects on how much his coding habits changed — from “make it run first” to “make the types make sense first” — while admitting these constraints are a liability during prototyping.
  • On leaving Swift for Rust — On Leaving Swift for Rust. 6/5 (Lobsters). The other side of the same transition: moving out of a platform-locked ecosystem with a closed toolchain, in exchange for owning your builds and dependencies.
  • Enabling the Rust parallel frontend on nightly — Enabling the parallel frontend on nightly. 14/0 (Lobsters). Official progress on the long-standing compile-time problem; shipping on nightly first signals the parallelization hasn’t reached harvest between bugs and gains.
  • A survey of memory management in 40 major C projects — Memory management in 40 major C projects, a survey. 57/14 (Lobsters). Tabulates every allocation path, error-handling pattern, and cleanup convention; what you come away with is an empirical distribution, not any single project’s preference.
  • clice v1.0: a language server for modern C++ — clice v1.0 Released: Welcome to Modern C++. 22/11 (Lobsters). A clang-based LSP implementation whose selling point is indexing and completion latency in large codebases — such projects usually die on build-system compatibility.
  • Jolt: Clojure that speaks C — Jolt – Clojure that speaks C. 82 points / 22 comments (HN). Compiles Clojure to C, targeting two things the JVM version can’t give you: small-footprint startup and bare-metal deployment.
  • Announcing Hegel-clj — Announcing Hegel-clj. 36/1 (Lobsters). Kyle Kingsbury ports his property-testing library Hegel to Clojure, carrying his trademark rigor on whether generated test cases should shrink.
  • Programming a language — Programming a language. 13/0 (Lobsters). A complete walkthrough from parsing to evaluation, good as a warm-up before a proper textbook.
  • Aristotle expands formal verification into Rust — Aristotle Expands into Rust. 89 points / 46 comments (HN). Pushing a proof assistant from math papers into real codebases; the math turns out to be the easy part — the hard part is modeling Rust’s ownership and unsafe blocks.
  • Squircles — Squircles. 93 points / 33 comments (HN). Raph Levien takes “rounded rectangles” down to the curvature level, explaining along the way why iOS icon corners feel nicer than CSS ones.
  • Paint in the memory of other programs — Paint in the memory of other programs. 63/6 (Lobsters). The author draws by directly rewriting pixel buffers in other processes’ memory, in code short enough for a lunch-break read.
  • 💬 Comments: Someone followed the links to apl385.c and said the source itself is worth a read; others traced the implementation to the apl385 project’s bundled font page, and the discussion drifted into typeface design.

🔬 Science, Hardware & Retro

  • Carnegie Mellon is putting computer science courses on YouTube for free — Carnegie Mellon is putting computer science courses on YouTube for free. 252 points / 49 comments (HN). Systematic course releases rather than scattered public lectures — for self-learners, this fills in the skeleton of an entire curriculum.
  • The secret ThinkPad powerbutton code to bring dead laptops back to life (2007) — The Secret ThinkPad Powerbutton Code to Bring Dead Laptops Back to Life. 286 points / 112 comments (HN). The old power-drain reset trick charting again.
  • 💬 Comments: A former phone-support agent explained the other half of the mechanism — making you hold it for ten seconds isn’t entirely hardware spec; it’s to ensure the user actually holds it long enough, since the three seconds support suggests often isn’t. One reader tried it and revived a Lenovo laptop that hadn’t booted since being dropped.
  • Grazing sheep under solar panels: farmers’ economic and ecological gains — Grazing sheep in fields with solar arrays. 183 points / 172 comments (HN). Cornell’s research runs the numbers on “solar + grazing” down to the individual farmer, solving mowing costs and sheep feed costs simultaneously.
  • Chemistry is actually geometry — Chemistry Is Geometry. 36 points / 6 comments (HN). Explains bonding, configuration, and reactivity as problems of shape — the kind of article that quietly fixes your high-school chemistry intuition.
  • The hidden origins of the placenta — The origins of the placenta. 19 points / 5 comments (HN). Caltech traces the organ’s evolutionary origins, landing on “the same genetic toolkit borrowed again and again.”
  • Building an AAA-game lighting pipeline in Three.js — My Quest to push native Three.js quality match AAA Game Engines. 60 points / 19 comments (HN). Aligning deferred rendering, shadows, and post-processing against console engines one by one; the author admits the gap lies mainly in tooling, not the API.
  • Improving the Wii U’s Wii Mode — Improving the Wii U’s Wii Mode. 2/0 (Lobsters). Squeezing more performance out of a compatibility layer the vendor no longer maintains — the kind of project filtered by reverse-engineering difficulty.

💰 Companies & Law

  • Nearly a third of Amazon’s Black Friday and Cyber Monday “deals” offer no savings — Many of Amazon’s Black Friday and Cyber Monday “deals” offered no savings. 782 points / 474 comments (HN). Groundwork’s investigation compared historical prices item by item, finding a substantial share of the “discounts” had been sold at the same or lower prices before.
  • 💬 Comments: Discussion quickly shifted from pricing to subscriptions — the top comment says canceling Prime cut impulse spending by hundreds or even over a thousand dollars a year, and the free-shipping-threshold itch can be satisfied by the threshold itself. Someone added an Audible example: searching your own library gets steered toward the for-sale catalog, different editions of the same book lure you into buying again, and purchased audiobooks sometimes show only a “buy again” button.
  • Comcast’s “fiber-powered Wi-Fi” is actually cable, AT&T alleges in false-advertising suit — Comcast’s “fiber-powered Wi-Fi” is cable, AT&T says in false advertising case. 58 points / 49 comments (HN). Suing over marketing wording using the physical medium at the line’s terminus — the two ISPs fighting each other ended up pinning down the technical definition even harder.
  • Michael Mann’s ‘Heat’ copyright fight turns on a deal with himself — Michael Mann’s ‘Heat’ Copyright Fight Turns on a Deal with Himself. 70 points / 31 comments (HN). The director wants his rights back, but the counterparty on that old agreement is also himself — in legal documents, the most expensive thing is often the signature relationship.

🎮 Light & Fun

📌 Chart Unchanged: A Note

Two of the 25 items on Lobsters’ front page overlap with vol-150 with no new developments — the memory management survey of 40 C projects (vdxevp) and clice v1.0 (9haygb) — so they aren’t expanded again this issue. Jiff and the “should AI-generated code be open source” threads also appeared yesterday, but both have substantive new content today (the 1.0 stable release and a new precedent correction in the comments), so they’re re-included.

🧭 Summary

Today’s mood is “auditing”: auditing whether Amazon’s discounts actually exist, auditing why that router entered the evidence chain, auditing how a piece of code sat in the system for four months before detonating. The three must-reads: the comments on the JPMorgan incident (a bug in self-hosted hardware directly overturns the “cloud is what breaks” intuition), the two long replies about consolidated failure points under the systemic-software-breakdown piece, and the Jiff 1.0 discussion — two generations of chrono maintainers explaining across the years that “a stable API is harder to overturn than a correct one” — the most honest passage of the day. The cross-cutting signal is that the cost of speculation is rising: inflated discounts, marketing wording, legacy login methods are all being settled one by one by cheaper automation; meanwhile on the engineering side, things that can be maintained long-term are becoming selling points again — a timezone library that promises not to change, an eight-year-old platform choice, a ten-second power-button hold — all pointing the same direction.