--- title: "Daily AI News Podcast" description: "Just days after OpenAI was exposed for ignoring internal safety warnings from leadership, the company fired three researchers who had tipped off external oversight bodies, one of whom was the official-designated safety contact. The same day, Broadcom was reported to be planning to lend Anthropic $42 billion, which Anthropic would then use to lease, that's right, lease Broadcom's own chips. Today we'll also look at two AI copyright lawsuits with opposite rulings, one for and one against the companies, plus even the Pope weighing in on AI-generated art. All coming up right after this." canonical_url: "https://blog.markkulab.net/en/tech-news/ai-daily-podcast-2026-10-02" author: "Mark Ku" author_url: "https://blog.markkulab.net/en/author/mark-ku" site: "Mark Ku's Tech Notes" date_published: "2026-10-02T02:00:00.000Z" category: "Fresh Tech News" tags: ["ai-daily", "podcast", "tech-news", "OpenAI", "Anthropic", "Broadcom", "AI安全", "AI著作權", "ThomsonReuters", "BostonDynamics", "教宗"] language: "en" license: "CC BY 4.0" license_url: "https://creativecommons.org/licenses/by/4.0/" attribution: "when reusing or quoting, credit the author and link back to the original" --- # Daily AI News Podcast > **TL;DR** — OpenAI fired three safety researchers, including its official safety liaison, for reporting internal safety concerns to external oversight bodies just days after leadership ignored safety warnings. Broadcom will lend Anthropic $42 billion to lease Broadcom's own chips, with convertible notes creating acknowledged conflicts of interest. arXiv capped submissions to two papers monthly per author due to AI-assisted writing flooding the platform. ## Opening OpenAI was just exposed for ignoring internal safety warnings from leadership, and two days later fired three researchers who had been blowing the whistle to external oversight bodies, one of whom was even the official safety liaison. On the same day, Broadcom was reported to be lending Anthropic up to $42 billion so Anthropic could use the money to lease, yes, lease Broadcom's own chips. Today we're also looking at two AI copyright lawsuits, one where the company won and one where it lost, and even the Pope weighed in on AI-generated art. We'll cover it all in a moment. ## Today's Top Stories ### 1. OpenAI Fires Three Safety Researchers, One of Whom Was the Official Safety Liaison - **Source**: RTÉ News () - **Summary**: OpenAI fired three alignment researchers, Jasmine Wang, Tomek Korbak, and Mikita Balesni, on the grounds that they shared confidential information with an external AI safety organization. Ironically, Korbak had been specifically assigned by the company to liaise with those very external oversight groups on "rogue agent incidents." The timing is also notable, coming just two days after leadership was reported to have ignored internal safety warnings. - **Most surprising point**: The person tasked with handling whistleblowing got fired for whistleblowing. - **Taiwan perspective**: This is a warning sign for Taiwanese teams working on AI governance or enterprise AI safety frameworks. It shows how easily "internal whistleblower mechanisms" can be sacrificed under commercial pressure, so SOPs shouldn't rely solely on leadership self-restraint. - **Discussion points**: - If even an "official liaison" isn't protected, does cooperation with external oversight bodies still mean anything? - Will this make other AI safety researchers afraid to report issues externally in the future? - Does OpenAI's PR explanation actually line up with the timeline of events? - **Script suggestion**: The most ironic part of this story is that Korbak wasn't some outsider; he was literally the person OpenAI assigned to liaise with external safety organizations. Now he's been fired for "sharing confidential information." Picture it like being sent by your company to talk to an auditor, telling the auditor the truth, and then getting fired for it. And the timing couldn't be more pointed, just two days after reports surfaced that leadership had ignored internal safety warnings. If this kind of move becomes industry standard, nobody is going to want to be the whistleblower anymore, and external oversight mechanisms could end up completely toothless. ### 2. Broadcom to Lend Anthropic Up to $42 Billion, So It Can Lease Broadcom's Own Chips - **Source**: Semafor () - **Summary**: In its IPO prospectus, Anthropic disclosed that Broadcom will provide up to $42 billion in convertible notes, letting Anthropic use the funds to lease Broadcom's own TPU compute resources. That amount represents roughly a third of Anthropic's $125.2 billion, five-year compute spending commitment. The notes can also be converted into Anthropic equity. - **Most surprising point**: A chip supplier is lending money to its own customer, specifically so the customer can lease that supplier's own chips, and Anthropic openly admits in the filing that this creates a "potential conflict of interest." - **Taiwan perspective**: Taiwan's chip supply chain is used to the logic of "orders plus cash." This model of a supplier bundling in financial leverage to lock in a customer is, in a sense, a way to secure order visibility for years to come. It's worth watching for Taiwanese manufacturers as a sign of how financialized the supply chain is becoming. - **Discussion points**: - Could this "vendor financing" model become a standard way for big chipmakers to lock in customers? - Since the convertible notes can turn into equity, Broadcom is essentially also betting on Anthropic's future valuation. - Could this make Anthropic's balance sheet look healthier than it actually is? - **Script suggestion**: Break this deal down and it's actually fascinating. Broadcom leases chips to Anthropic with one hand, then lends Anthropic money to pay for that lease with the other. That loan can convert into Anthropic shares, meaning Broadcom is simultaneously a supplier, a creditor, and possibly a future shareholder. Anthropic itself wrote "potential conflict of interest" in black and white in the prospectus, so credit where it's due for the honesty. This really reflects just how scarce compute capacity has become: chipmakers aren't just selling hardware anymore, they're directly helping customers lever up to lock in orders. ### 3. arXiv Cuts Monthly Submission Limit to Two Papers per Author, Citing a Flood of AI-Assisted Writing - **Source**: arXiv official blog () - **Summary**: The world's largest preprint platform, arXiv, announced that each author can now submit a maximum of two papers per month, with no more than three under review at any given time. The reason: submissions hit 40,363 papers in September alone, nearly double the same period two years ago. That month alone generated about 9,000 support tickets, a surge largely attributed to AI-assisted writing. - **Most surprising point**: Even submissions that get rejected by the system still count toward your monthly quota. - **Taiwan perspective**: Taiwan's academic community has also debated concerns about AI-assisted paper writing inflating output. This restriction essentially puts the brakes on globally first, and it will have a real impact on how Taiwanese grad students and professors rush to post on arXiv before deadlines just to establish a public timestamp. - **Discussion points**: - Could a quota system backfire and encourage people to split papers into smaller pieces just to game the numbers? - Should AI-assisted writing be encouraged or restricted? Is this platform-level fix just a band-aid? - Is it fair that rejected submissions still count toward the quota, especially for researchers who genuinely need to revise and resubmit quickly? - **Script suggestion**: What's interesting about this story is that arXiv became popular precisely because it was open and had almost no submission barriers. Now it's being flooded by papers that AI helped churn out, forcing the platform to impose a quota on itself. Even harsher is that rejected submissions still eat into your quota, so if you submit a weak paper and it gets rejected, you've lost one of your slots for the month. This is really pushing researchers to be more careful before submitting, but it could also hurt people who genuinely need to make quick revisions and resubmit. It's a pretty classic case of "using quantity restrictions to plug a leak, while accidentally damaging quality control." ### 4. Court Rules for the First Time That Training AI on Others' Data Isn't Fair Use, Thomson Reuters Wins Key Lawsuit - **Source**: MediaPost () - **Summary**: The U.S. Court of Appeals for the Third Circuit affirmed that Ross Intelligence, a startup, did not qualify for fair use when it trained its own legal search AI using Westlaw's case summaries. This is the first appellate ruling in the U.S. on whether training AI with copyrighted material counts as fair use. The court's key finding was that the tool Ross built served the same purpose as the original material and directly competed with Thomson Reuters. - **Most surprising point**: The lawsuit has dragged on since 2020, and Ross Intelligence has already gone out of business, yet the ruling only just came out now. - **Taiwan perspective**: Many Taiwanese startups also use other companies' curated databases or knowledge bases to train models. This ruling draws a clear line: if the trained output is meant to directly replace or compete with the original data source, the legal risk rises significantly. Legal teams should treat "does the purpose directly compete" as a key factor in their risk assessment. - **Discussion points**: - How will this "same purpose, direct competition" standard be applied to other AI training lawsuits going forward? - The defendant company went bankrupt before the ruling even came out, which is a brutal timeline for any startup caught in litigation. - Will this embolden more publishers and database companies to sue AI firms? - **Script suggestion**: The most ironic part of this case is that the lawsuit dragged on for six years, and the defendant, Ross Intelligence, had already shut down long before this industry-defining ruling finally arrived. The line the court drew is actually pretty clear: if what your AI does is essentially the same thing as the data you trained it on, and it directly steals that company's business, it's hard to call that fair use. I think this is a concrete warning for any team hoping to train models on industry databases: the question isn't whether you can use someone else's data, it's whether the resulting product happens to hit right where it hurts for the data's original owner. ### 5. Google Beats Penske Media in AI Summary Lawsuit, a Sharp Contrast to the Thomson Reuters Case - **Source**: The Hollywood Reporter () - **Summary**: A federal judge dismissed Penske Media's lawsuit against Google over AI Overviews summarizing Penske's news content, ruling that a publisher's expectation of search traffic has never constituted a contractual relationship. This ruling, coming almost simultaneously with Thomson Reuters' win, makes for a striking contrast: publishers just secured a landmark ruling that "training AI on copyrighted content" isn't fair use, only to immediately lose on the issue that's actually eating into their traffic, AI directly using their content to generate summaries. - **Most surprising point**: In the same week, the publishing industry won the biggest AI copyright precedent in history, yet lost the fight that's actually draining their traffic. - **Taiwan perspective**: For Taiwanese media outlets and content sites, this ruling shows how hard it is to protect traffic through legal means. Rather than betting on lawsuits, it's better to start thinking now about how to build content value that can't be replaced in the age of AI summaries, such as deep analysis or original perspectives. - **Discussion points**: - Will the logic that "expecting traffic isn't a contract" be used to block more similar lawsuits in the future? - How can publishers strike a balance between protecting copyright and competing with AI summaries for traffic? - Does this mean publishers' only remaining leverage is on the "training data" front, with the traffic battle already lost? - **Script suggestion**: Put these two cases side by side and it's a strange picture. Publishers just won the first-ever appellate victory on AI training copyright, and immediately afterward, a judge told them that expecting a search engine to send them traffic isn't some contractual obligation owed to them. In other words, publishers won the fight over training data but lost the fight that's actually taking food off their table. The law is willing to protect "your content can't be used to train a competing product," but it won't protect "your accustomed business model can't be disrupted." For an industry that depends on search traffic, that's a much harsher reminder. ### 6. California Signs 13 AI Bills Banning AI From Firing Employees Alone, But Vetoes Smart Glasses Spy-Camera Bill - **Source**: The Next Web () - **Summary**: California's governor signed a sweeping package of AI bills, including the "No Robo Bosses Act," which bars employers from firing employees based solely on an AI's decision. At the same time, he vetoed SB 1130, which would have made it a misdemeanor to covertly record people using smart glasses and required such devices to show a recording indicator light while filming. The governor's stated reason was that the definition of "wearable recording device" was too broad and could sweep in things like smartwatches. - **Most surprising point**: An algorithm can no longer fire you, but the person standing across from you wearing smart glasses can still secretly record you with no warning light at all. - **Taiwan perspective**: Taiwan currently has fairly limited regulations around wearable devices and privacy. This case is a reminder for lawmakers that a definition written too broadly can ensnare other legitimate devices, while one written too narrowly fails to address the real risk. Taiwan will eventually have to grapple with the same tension over privacy rules for new wearables like smart glasses. - **Discussion points**: - How would the No Robo Bosses Act determine what counts as "solely an AI decision"? Could companies just get a human to rubber-stamp AI decisions as a workaround? - Will the smart glasses spy-camera controversy keep dragging on now that the bill has been vetoed? - Will other states follow California's lead on labor protections while staying more conservative on privacy? - **Script suggestion**: This story has a very vivid contrast. On one hand, the governor made a decisive statement that an algorithm shouldn't be allowed to decide alone whether to fire you, and that direction deserves credit. On the other hand, the bill requiring a recording indicator light on smart glasses got vetoed, on the grounds that the definition was too broad and might accidentally catch devices like smartwatches. The net result is that you now have an extra layer of AI protection at work, but the moment you step outside the office, a stranger wearing smart glasses could be livestreaming you the whole time without you ever knowing. This highlights how lawmakers tend to patch AI-related issues case by case, rather than working from a comprehensive framework. ### 7. Boston Dynamics' New Humanoid Robot Hand Deliberately Drops the Pinky, and Becomes More Dexterous for It - **Source**: The Robot Report () - **Summary**: Atlas has a new four-fingered hand with degrees of freedom increased from seven to thirteen. It can reorient objects within its own palm, recover on its own if an object slips, and even juggle two golf balls with one hand or pull the trigger on a power drill. Interestingly, engineers deliberately chose not to include a fifth finger, reasoning that the added complexity, power draw, and bulk from a pinky simply weren't worth it. - **Most surprising point**: Evolution took millions of years to give humans five fingers, and engineers cut one with a single line in a spec sheet. - **Taiwan perspective**: For Taiwanese suppliers that build robotic arms and grippers for automation, this story is quite practical. It shows that robot design doesn't have to mimic humans; it should instead make trade-offs based on task requirements. This "good enough, not overly biomimetic" philosophy can actually help Taiwan's small and mid-sized automation manufacturers save costs and get products to market more easily. - **Discussion points**: - Does removing one finger really not affect most everyday manipulation tasks? What's the engineering logic behind that call? - How does this trade-off-driven design philosophy contrast with approaches that emphasize full biomimicry? - Will future humanoid robot hands increasingly lean toward "functionally sufficient" rather than "humanlike"? - **Script suggestion**: What's cool about this story isn't that the robot hand got more impressive, it's the trade-off the engineers made. Adding a fifth finger sounds like a no-brainer, since humans have five fingers after all, but Boston Dynamics' team ran the numbers and decided the extra complexity, weight, and power draw just weren't worth it. So they cut the pinky entirely, and still ended up with a lighter hand that can juggle two golf balls and pull a trigger. This pretty much debunks the myth that "a robot has to fully mimic a human." Sometimes the smartest engineering decision is being honest about which features are actually dispensable. ### 8. Pope Leo XIV Publicly Criticizes AI-Generated Art, Says Machine Output Has an "Ontological Difference" From Art - **Source**: TechCrunch () - **Summary**: Pope Leo XIV announced plans to reinforce the Church's collaboration with human artists. According to TechCrunch, he argued that the difference between art and something a machine generates through statistical computation isn't just aesthetic, it's "ontological." In simple terms, he believes AI-generated work lacks that human spark. - **Most surprising point**: The Vatican essentially just issued a theological-grade verdict on diffusion models. - **Taiwan perspective**: Taiwan's creative community has also been debating whether AI-generated images count as "creation." The Pope's remarks echo, to some extent, what many traditional creators have been feeling, but they're also a reminder that this debate won't stay confined to copyright or commercial concerns, it may well extend into deeper questions about what art fundamentally is. - **Discussion points**: - "Ontological difference" sounds very academic; in everyday terms, what is the Pope actually trying to say? - Could a religious institution publicly criticizing AI art shape how the general public perceives AI-generated content? - Does this align with or push back against how museums and galleries are currently treating AI artwork? - **Script suggestion**: This remark from the Pope is a bit surprising at first glance. Most people might say AI-generated images lack soul, which is a fairly emotional way of putting it, but the Pope went straight for "ontological," a philosophical-grade term, elevating the discussion to the level of faith and the meaning of existence itself. In other words, he's not saying AI art doesn't look good, he's saying it's not even the same category of thing to begin with. This really reflects something real: as AI-generated content becomes more widespread, people's anxiety about "what counts as creation" has moved beyond job security and started touching on something much more fundamental, the definition of humanity itself. ## Closing Today we went from OpenAI firing its own people, to Broadcom bankrolling a customer to lease its own chips, to AI copyright lawsuits splitting one win and one loss, and finally even the Vatican weighing in. This episode was basically a microcosm of the entire AI world: money, power, law, and human nature, all playing out on the very same day. I'm Muyan, see you next time. --- ## About this article and its author Originally published on [Mark Ku's Tech Notes](https://blog.markkulab.net/en/tech-news/ai-daily-podcast-2026-10-02) License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) — when reusing or quoting, credit the author and link back to the original ### About the author **[Mark Ku](https://blog.markkulab.net/en/author/mark-ku)** — Software engineer - 10+ years as a software engineer - Built North-American e-commerce and AI SaaS subscription billing ### Free tools built by the author All of these are free to use: - [Free PDF Sign Tool](https://blog.markkulab.net/en/tools/pdf-sign): Online PDF sign tool — draw, type, or upload a signature, then drag, resize, and download. Everything runs in your browser; nothing is uploaded. - [VS Code Refactory](https://blog.markkulab.net/en/tools/refactory): Refactory is a VS Code refactoring extension: 34 actions plus a 37-rule code-smell inspection layer with a Code Health dashboard, across 18 languages, backed by 534 tests. It learns your repo's conventions: where interfaces live, where DI is registered, whether 'use client' belongs. It ranks files by git churn × complexity so you know what to fix first, and hands any smell to the Claude Code already on your machine. Free to use, and your source never leaves your computer. - [DB-Kit Database Manager](https://blog.markkulab.net/en/tools/db-kit): DB-Kit is a lightweight, cross-platform database manager built with Tauri + Rust + React. Manage MySQL, MariaDB, PostgreSQL, SQL Server, Oracle, SQLite, MongoDB, Redis, Kafka, Elasticsearch and RabbitMQ from one consistent interface: passwords encrypted in the OS keychain, SSH tunnels, full CRUD, a visual query builder, stacked multi-statement result sets, cross-connection data transfer, schema & data compare with sync SQL and schema snapshots, Excel / CSV import & export, visualized execution plans, ER diagrams, scheduled backups, SQL stress testing with p50–p99 latency percentiles, a 15-rule SQL review engine, Review & Run (AI review plus per-statement backups and an auto-generated rollback script), Kafka message browsing with monitoring & alerts, a bilingual UI (Traditional Chinese / English), a built-in AI assistant (a local CLI or any Anthropic / OpenAI-compatible API; natural-language SQL, AI review and tuning advice) and the dbk CLI. Free and open source (MIT), with installers for Windows, macOS and Linux. - [VS Code Super Mermaid](https://blog.markkulab.net/en/tools/super-mermaid): Super Mermaid is a VS Code extension for beautiful Mermaid diagrams out of the box: auto-colored live preview, mouse pan & zoom, high-res PNG / SVG export, 21 templates and multiple themes. Free and open source (MIT). - [React Super Mermaid](https://blog.markkulab.net/en/tools/react-super-mermaid): react-super-mermaid is an open-source React component library: render beautiful Mermaid diagrams with a single , with built-in colorful / sketch themes, pan & zoom, in-diagram search, and high-res SVG / PNG export. Lightweight, SSR-safe, fully typed. Free and open source (MIT). - [Jira / Confluence Super Mermaid](https://blog.markkulab.net/en/tools/jira-super-mermaid): An Atlassian Forge app: write Mermaid syntax directly inside a Jira issue or a Confluence page and get flowcharts, sequence diagrams, state machines and Gantt charts. 11 diagram types, SVG / PNG export, light and dark themes, full CJK support. Runs on Atlassian: your diagrams live in your own site and the app calls no third-party service. Free, coming soon to the Atlassian Marketplace. - [Mermaid Live Preview](https://blog.markkulab.net/en/tools/mermaid-preview): Write Mermaid in your browser, see it render instantly, and share the whole diagram as a single link. No sign-up, nothing uploaded to a server, and mermaid.live share links work as-is. - [React Intl Phone Number](https://blog.markkulab.net/en/tools/react-intl-phone-number): react-intl-phone-number is an open-source React component: framework-agnostic and antd-free, with E.164 in/out, a searchable flag / country-code dropdown, configurable validation levels (strict / mobile-strict / loose), themeable CSS, and i18n — phone logic powered by google-libphonenumber. Lightweight and fully typed. Free and open source (MIT). - [Uptime Kuma Cluster](https://blog.markkulab.net/en/tools/uptime-kuma-cluster): Turn single-node Uptime Kuma into a highly available cluster: OpenResty + Lua smart load balancing, shared MariaDB state, health checks and automatic failover, plus cluster-management REST APIs. One Docker Compose command to start. Free and open source (MIT). - [AI Podcast Cut](https://blog.markkulab.net/en/tools/ai-podcast-cut): Drop in a recording and it removes fillers and stutters, levels loudness segment by segment, and sends a second agent to review every cut. Cut points snap to word boundaries and zero crossings, every splice gets a fade, and sentence-end breaths are preserved. Desktop app for Windows, macOS and Linux. MIT licensed; the Windows installer bundles ffmpeg. - [open-pos restaurant POS](https://blog.markkulab.net/en/tools/open-pos): One computer and one receipt printer is enough to open the shop. Your data lives on your own disk, no subscription, no lock-in, MIT licensed. Money is integer New Taiwan dollars with tax split by the statutory formula, so sales + tax always equals the total. Printing goes straight over ESC/POS on TCP 9100, with no vendor driver. Tauri + Rust + SQLite desktop app, v1.0 in development. ### Daily podcasts - [Mark's Tech Insights — Daily AI News](https://blog.markkulab.net/en/category/tech-news): Daily curated AI and tech trends. Catch the latest developments via audio summaries — covering AI applications, software architecture, DevOps, and engineering practice. — RSS: https://blog.markkulab.net/feed.xml - [AI股市蝦聊](https://blog.markkulab.net/en/category/ai-stock-chat): Every trading day, an AI-analyzed take on the Taiwan stock market, delivered as a two-host conversation covering the session and the next-day outlook. — RSS: https://blog.markkulab.net/ai-stock-chat/feed.xml - [開源好物週報](https://blog.markkulab.net/en/category/open-source-weekly): A weekly two-host pick of free open-source tools surfaced from real Hacker News, GitHub, and Reddit buzz — what pain they solve and the fastest way to get started. — RSS: https://blog.markkulab.net/open-source-weekly/feed.xml - [AI 運動週報](https://blog.markkulab.net/en/category/sports-weekly): Two hosts talk NBA, MLB and world sport three times a week — scores, records and the stories behind them, from a Taiwanese fan perspective. — RSS: https://blog.markkulab.net/sports-weekly/feed.xml - [AI 國際新聞快報](https://blog.markkulab.net/en/category/world-news): A daily two-host briefing that makes sense of the past 24 hours in world news — geopolitics, the global economy, conflict and security, disasters and climate — from a Taiwanese perspective, neutral and fully sourced. — RSS: https://blog.markkulab.net/world-news/feed.xml - [地端 AI 實驗室](https://blog.markkulab.net/en/category/local-ai-lab): Twice a week, a two-host look at open-weight models and LoRAs you can actually run on your own machine: what they are for, whether your GPU can handle them, and how they compare — sourced from official model cards. — RSS: https://blog.markkulab.net/local-ai-lab/feed.xml ### Deals - [Saily eSIM](https://blog.markkulab.net/en/saily): Travel eSIM by the NordVPN team，Promo code：KUKU - [NordVPN](https://blog.markkulab.net/en/nordvpn): The world's leading VPN, independently audited - [PremLogin](https://blog.markkulab.net/en/premlogin): Subscription sharing for streaming and AI seats，Promo code：markku666 ### Newsletter [Subscribe to the newsletter](https://blog.markkulab.net/en/subscribe) — Be the first to know about new posts. No spam, unsubscribe anytime.