This week’s kitchen sink for July 31, 2026 (with meme from Gates Dogfish) discusses a bad news week for Anthropic, border searches under duress & more!

Why “the kitchen sink”? Find out here! 🙂

The Kitchen Sink is even better when you can include a brand-new eDiscovery meme courtesy of Gates Dogfish, the meme channel dedicated to eDiscovery people and created by Aaron Patton. For more great eDiscovery memes, follow Gates Dogfish on LinkedIn here! The firm’s response: “None of your beeswax!” 🤣

Here is the kitchen sink for July 31 of ten-ish stories that I didn’t get to this week, with a comment from me about each:

We’re up to 1,815 AI hallucination cases and counting. Is it “human in the loop” or “scapegoat in the loop”? 🤣

Nvidia Considers Unusual Offer on Behalf of OpenAI: This story may illustrate who’s really making the money in AI. Nvidia is reportedly negotiating to guarantee up to $250 billion in financing for OpenAI as part of an enormous Ohio data-center project. Says a lot, doesn’t it. 😊

An Attorney-Client Communication Advising Spoliation is Not Privileged: True, but as Michael Berman points out on the EDRM blog, Plaintiffs contention that Meta did so in four redacted documents and that they were subject to the crime-fraud exception to the attorney-client privilege was not found to be the case when the Court reviewed the unredacted documents in camera.

Stadler rejects $12.3 million ransom after supplier-linked platform breach: “Take that, ransomware attackers!” Of course, as Rob Robinson discusses in ComplexDiscovery, the attackers took technical files belonging to that supplier, not their own files. Wonder how they would have reacted if it were their own stuff? 🤔

A U.S. Citizen Deleted His Phone’s Data. Now He Faces a Felony Charge.: An American returns to the US, border agents demand access to his phone and he gives them the code…that wipes his phone! That’s known as a “duress” passcode and it’s a feature included in GrapheneOS, a custom Android operating system that can be installed to run in place of the default OS. They didn’t appear to appreciate the practical joke. 😉

Chatbot’s Sensitive Chats Exposed in Google Search: ChatGPT? Grok? Whatever Meta is calling their AI chatbot these days? Nope, it’s Claude’s “Share” feature, which generates public links and notes that “anyone with the link can view”—but which doesn’t explicitly warn that the same content can then be indexed by search engines. Medical reports, clinical trial data with patient names, children’s contact details, internal corporate documents, and more are showing up in Google search results. Ruh-roh!

Open weights, open questions: the letter that redrew the AI policy fight: Rob Robinson’s first paragraph says it all: “Seventy-seven companies and organizations have now signed a letter asking Washington to avoid broad or premature restrictions on open-weight AI models, and the week that produced it touched nearly every concern this publication covers. A Chinese model matching top American systems, a White House distillation accusation against Moonshot AI, sanctions threats from Treasury, an AI agent breaking out of OpenAI’s test environment to breach Hugging Face, and a European enforcement deadline arriving Aug. 2 all converged within eight days.” Yeah, we don’t need those stinkin’ restrictions! 🤣

Mark Zuckerberg Blasts Centralization of A.I. Power: He took aim at Anthropic and OpenAI, which have pushed to tightly control A.I. development, and said he supported “more openness.” After all, how else is he going to see how they’re creating better AI models than Meta? 😉

Condominium Construction Defect Litigation Leads to Search and Custodian Rulings: Interesting case covered by Michael Berman on the EDRM blog with rulings that come along once in a “Blue Moon”. Read his post and you’ll see what I did there. 🤣

Wikipedia is designing an immune response to AI copy: Stephen Abram covers Wikipedia’s policy regarding authors using AI: “When a user has been determined to have a history of AI use, a series of their contributions may be assumed to violate Wikipedia’s policies and guidelines. In this case, edits to existing pages may be reverted without review, and pages where the editor is the only significant contributor may be nominated for a special proposed deletion process”. Just for using AI? Damn! 🤯

LinkedIn adds a button to report AI-generated ‘slop’: On Thursday, LinkedIn announced that it’s adding a new feature to let users click a “seems like AI slop” button when someone’s post appears to have been written with AI. It also looks like they’ve removed the feature to rewrite your post using AI, depriving my opportunity to make fun of them over their new policy. 😉

Anthropic Says Its A.I. Systems Broke Into Computers at 3 Organizations: One more company than OpenAI breached! What’s up with these AI companies always trying to outdo each other? 🤣

Hope you enjoyed the kitchen sink for July 31, 2026! Back next week with another edition!

So, what do you think? Which story is your favorite one? Please share any comments you might have or if you’d like to know more about a particular topic.

Disclaimer: The views represented herein are exclusively the views of the authors and speakers themselves, and do not necessarily represent the views held by my employer, my partners or my clients. eDiscovery Today is made available solely for educational purposes to provide general information about general eDiscovery principles and not to provide specific legal advice applicable to any particular circumstance. eDiscovery Today should not be used as a substitute for competent legal advice from a lawyer you have retained and who has agreed to represent you.