SPECIAL SERIES ==> 🚨 Your AI Copy Is Snitching On You <== | BATHROOM Break #121 COLLAB: The Marketing Millennials + Do This, Not That

Partner with Jay: https://www.jayschwedelson.com/contactㅤCheck out Jay Schwedelson's new book: Stupider People Have Done It All net proceeds are donated to The V Foundation for Cancer Research, let's kick cancer's butt: https://www.amazon.com/Stupider-People-Have-Done-Marketing/dp/1637635206ㅤSubscribe to Jay's newsletter for weekly marketing tips and tactics: https://www.jayschwedelson.com/newsletterㅤRegister for GuruConference (FREE + VIRTUAL!) https://www.guruconference.comㅤCheck out Eventastic (FREE + VIRTUAL!) https://www.eventastic.comㅤConnect with Jay on LinkedIn: https://www.linkedin.com/in/schwedelson/Check out Jay's YouTube channel: https://www.youtube.com/@schwedelsonCheck out Jay's Instagram: https://www.instagram.com/jayschwedelson/Ask Jay anything: https://www.jayschwedelson.com/askㅤLeave a comment and follow the show, it really helps us out!ㅤFollow Daniel on LinkedIn and check out The Marketing Millennials podcast for sharp, no-fluff marketing insights. Subscribe to Ari Murray’s newsletter at gotomillions.co for sharp, actionable marketing insights.ㅤCopy, paste, post has been the default AI workflow for a lot of marketers, and it quietly stopped being safe. Jay Schwedelson and Daniel Murray dig into the watermarking wave hitting Claude and ChatGPT, why it now lives inside the writing itself rather than the metadata, and what still slips past detection right now. There is also a beignet incident and a boarding gate betrayal, so stick around for the back half.ㅤBest Moments:(02:25) Why Claude started watermarking images and how EU pressure kicked it off(03:24) The bigger story is a watermark woven into the text, not hidden in metadata(04:01) Treat these tools as a first draft stop, then move the work somewhere else(05:19) The open question of whether AI editing your own writing gets flagged too(06:50) What is actually working right now to keep images from reading as AI(07:57) Yesterday's workaround breaks tomorrow, so keep testing instead of assuming