Podcasts about scraping

In Part 2 of this powerful series, Jeni Hott and host Dwayne Carrigan dive deep into the mindset and mechanics behind magnetic marketing. Jeni unpacks why traditional strategies fail, how to simplify your sales funnel, and how to shift from desperation to authority in your messaging. She breaks down the types of social media posts that actually convert, explains her timeline-based client targeting strategy, and shares how to create a "content vault" that makes your marketing repeatable and scalable.Jeni also addresses the rise of AI and how business owners can use ChatGPT and custom GPTs to build systems, streamline operations, and reclaim their time—without losing their personal touch.Timestamps:00:00 – Marketing from angst vs. marketing from leadership02:30 – Understanding "objection posts" and sales page content05:00 – FAB (Features, Advantages, Benefits) and storytelling in marketing07:30 – Jeni's “client timeline” strategy vs. the traditional avatar model10:00 – The power of targeting tipping points for high-converting offers12:00 – Why you don't need to convince when you're speaking with conviction13:30 – Building a content vault to reflect customer buying moments15:00 – Creating a seasonal content calendar that predicts conversions16:30 – Should a VA or OBM manage your social content? Yes—if trained well18:30 – The danger of hiring without understanding the basics20:00 – The Time Rich program and its holistic business foundations23:30 – Embracing social media instead of avoiding it26:00 – Staying in your lane and not chasing online trends29:00 – Avoiding distractions: Focus on purpose, not reaction31:00 – AI tools: ChatGPT, Poe, custom GPTs & what's coming next35:00 – Household bots & humanoid robotics on the near horizon38:00 – How to create a custom GPT tailored to your business42:00 – AI learning and the “unconscious competence” advantage45:00 – Singularity and AI as human evolution, not a threat47:00 – Algorithm hacks vs. adding true value to your audience50:00 – Using engagement posts to boost algorithm reach53:00 – How to analyze comments and reels with ChatGPT55:30 – Scraping content and training AI on what's working58:00 – 6 key post types and why simplicity wins in content strategy01:01:00 – Final thoughts: embrace, optimize, empower your teamNotable Quotes:"You don't need to convince when you come from conviction. That's when magic happens.""Most people aren't your ideal client—they're just not far enough along the timeline yet.""Complexity is the enemy of execution. Simplify, then scale.""AI is not going away. You don't need to master it overnight, but you do need to start.""Your people can't help you scale unless you empower them with knowledge and tools."Valuable Resources & Takeaways:Core Post Types Jeni Recommends:Value PostsObjection PostsStory PostsEngagement PostsProblem Awareness PostsAI Tools Mentioned:ChatGPT – Jeni's favorite tool for custom GPT creation and business system building Poe – Alternate AI tool used by many entrepreneursCustom GPTs – Can be trained to match your brand...

In this episode, Jaeden explores the latest updates to Claude, Anthropic's AI tool, which now includes web scraping capabilities. He examines how this new feature impacts users, competitors, and the broader AI landscape, particularly in comparison to tools like ChatGPT and Perplexity. The discussion also dives into the technical side, revealing how Claude is powered by Brave and what this means for the future of AI-driven search and information retrieval.Chapters00:00 Introduction to Claude's New Features02:47 The Evolution of AI Search Capabilities06:00 Impact on Competitors and Market Dynamics08:45 Brave Search Integration and Future ProspectsAI Applied YouTube Channel: https://www.youtube.com/@AI-Applied-PodcastGet on the AI Box Waitlist: ⁠⁠https://AIBox.ai/⁠⁠Conor's AI Course: https://www.ai-mindset.ai/coursesConor's AI Newsletter: https://www.ai-mindset.ai/Jaeden's AI Hustle Community: https://www.skool.com/aihustle/about

Mein heutiger Gast ist Georg Zumann – Tonstudioleiter und Mitbegründer der Innenhofstudios und seit vielen Jahren erfolgreich selbstständig. Wir sprechen über seine Anfänge in der Audiobranche, den Studioalltag und die Frage, wie Studios eigentlich entscheiden, welche Stimmen für welche Kampagnen passen. Ein ehrlicher und spannender Blick hinter die Kulissen des Studioalltags (mit vielen Tips und no go´s für Sprecher:innen) – inklusive Einblicke in aktuelle Entwicklungen, die die Branche gerade bewegen. Nachrichten gerne an: deeptalk@mic-rider.com Website: https://www.mic-rider.com/ Host und Redaktion: Patrick Messe (https://www.patrickmesse.at/) Zu Gast: Georg Zumann (https://innenhofstudios.at/) Bild: Charly Glawischnig (https://www.charlyglawischnig.com/) Ton: Lukas Wurm (https://lukaswurm.com/) Produktion: Mic Rider (https://www.mic-rider.com/)

Citizens Bank is advancing its digital payments strategy in 2025, with a focus on embedded finance and omnichannel capabilities. For example, Citizens is moving from screen scraping to an API-enabled environment, allowing it to use insights from its private banking segment in other segments, such as SMB, mid-market and commercial, Taira Hall, executive vice president and head of enterprise payments at the $217.5 billion Citizens, tells Bank Automation News in this episode of “The Buzz” podcast. “One of the benefits of having an enterprise payments function is … we can look at all of our core payment rails and understand at scale … It's sort of bringing this intertwined aspect to it … making sure that anything we build in one place has connectivity tissue into the rest of the bank,” she says. The bank, she says, is moving forward with its multiyear digital transformation, focusing on: Fintech partnerships; Data and analytics investment; AI deployment; and  Expanded capabilities for existing tools, such as the bank's SMB-focused Cash Flow Essentials payments platform. Learn more from Hall about how Citizens is looking to balance relationship banking with digital innovation in this episode of “The Buzz.” Subscribe to The Buzz Podcast on iTunes or Spotify, or download the episode.

David Restiano, the founder and inventor of Sorsoap, a unique muscle scraping soap designed for use in the shower, integrating physical therapy into daily routines. David shares the story of how he came up with the idea during the COVID-19 pandemic while dealing with soreness from running. He discusses the development process, manufacturing challenges, Shark Tank experience, and the successful marketing strategies that have contributed to the company's growth. David emphasizes the importance of treating customers well and provides insights into his social media marketing approach, particularly on TikTok, which has been pivotal in driving sales. He wraps up by discussing the future plans for Sorsoap, including expanding into retail stores.

What dental care practices are helpful and which are overly hyped? Is it a good idea to use oral exercise devices? What about tongue scraping and flossing? What should we look out for when it comes to toothpaste and mouthwash? Dr. Dominik Nischwitz, author of It's All in Your Mouth, highlights what is best for strong healthy teeth and a beautiful smile. He separates fact from fiction. He goes over how to cultivate a healthy oral microbiome and he also addresses the issue of "leaky gums". And he leaves us with three key questions to ask ourselves to help determine if our health concerns could be related to oral health.   Visit Dr. Dominik's website: DrDomeOfficial.com Join the Weston A. Price Foundation email list HERE Check out our sponsors: Rosita and Hearth and Homestead

Nat and Marc clink glasses and take a moment to reflect and revisit the first 100 episodes Please subscribe, follow, and leave a review. xxx You can find us in all places here; https://podfollow.com/lifewithnat/view INSTA: @natcass1 We're also on Facebook too: https://www.facebook.com/lifewithnatpod A 'Keep It Light Media' Production Sales, advertising, and general enquiries: hello@keepitlightmedia.com SHOW INFO: Life with Nat - it's me! Natalie Cassidy and I'll be chatting away to family, friends and most importantly YOU. I want to pick people's brains on the subjects that I care about- whether that's where all the odd socks go, weight and food or kids on phones. Each week I will be letting you into my life as i chat about my week, share my thoughts on the mundane happenings as well as the serious. I have grown up in the public eye and have never changed because of it. Life with Nat is the podcast for proper people. Come join the community. ♥️ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Hurts More Than the Yank. One pull per nostril. You Get NO Ooga, NO Chaka & NO Lt Yar! Yank It Out Wax Deal. Froggy Peen. A Moment Of Silence For Clare. Getting the Light at both ends. It's Neither A Pap Nor A Smear... DISCUSS! Men are wusses, women are awesome. The moment I said COW! Manipulabubble. Can't talk, more coffee. In the name of 2025. Yank it and be done the first time! LEAVE RICK ASTLEY ALONE and more on this episode of The Morning Stream. Hosted on Acast. See acast.com/privacy for more information.

Hurts More Than the Yank. One pull per nostril. You Get NO Ooga, NO Chaka & NO Lt Yar! Yank It Out Wax Deal. Froggy Peen. A Moment Of Silence For Clare. Getting the Light at both ends. It's Neither A Pap Nor A Smear... DISCUSS! Men are wusses, women are awesome. The moment I said COW! Manipulabubble. Can't talk, more coffee. In the name of 2025. Yank it and be done the first time! LEAVE RICK ASTLEY ALONE and more on this episode of The Morning Stream. Hosted on Acast. See acast.com/privacy for more information.

Think oral health is just about cavities? Think again. Dr. Namrata Patel breaks down how your mouth influences digestion, sleep, & even hormone balance. Get expert insights on holistic dentistry, the dangers of mouth breathing, & how small daily habits can transform your health from the inside out on today's episode on 'Holistic Oral Health Care' Meet our guest Dr. Nammy Patel, DDS, is a holistic dentist dedicated to patient health & environmentally conscious dentistry. Born in India & raised in the U.S., she founded Green Dentistry in 2005, San Francisco's first eco-friendly dental practice. Her LEED-certified office uses safe materials, energy-efficient systems, & sustainable practices to minimize environmental impact. A graduate of USC's School of Dentistry, Dr. Nammy turned down conventional roles to create a practice that prioritizes both health & sustainability. She is also the author of Age With Style & is developing a nonprofit to promote greener dentistry in India Thank you to our partners Outliyr Biohacker's Peak Performance Shop: get exclusive discounts on cutting-edge health, wellness, & performance gear Ultimate Health Optimization Deals: a roundup article of all the best current deals on technology, supplements, systems and more Gain mental clarity, energy, motivation, and focus with the FREE Outliyr Nootropics Mini-Course The simple, guided, and actionable Outliyr Longevity Challenge helps you unlock your longevity potential, slow biological aging, and maximize your healthspan Key takeaways Diagnose diseases like heart attack & diabetes by examining the mouth, according to Ayurvedic practices Mouth breathing leads to sleep apnea & other health issues, while nasal breathing produces beneficial nitric oxide Breathing through the nose aids in converting oxygen to nitric oxide, improving bodily functions & hormone regulation Using mouth tape reduces mouth breathing & improves sleep quality Simple exercises like sticking your tongue out while driving improves tongue health Using coconut oil in the mouth detoxes the body by binding toxins A Waterpik is favored over traditional floss for oral care & works well with hydrogen peroxide or ozonated water The tongue's position impacts breathing & health, with regular exercises maintaining its function   Episode Highlights 6:22 Oral Health & Its Connection to Systemic Health 11:22 Tongue Position & Peak Performance 13:36 DIY Oral Health Practices & Breathing Exercises 26:07 Oil Pulling & Mouthwashing Techniques Links Watch it on YouTube: https://youtu.be/VnjOQrlB3-g  Full episode show notes: mindbodypeak.com/200 Connect with Nick on social media Instagram Twitter YouTube LinkedIn Easy ways to support Subscribe Leave an Apple Podcast review Suggest a guest Do you have questions, thoughts, or feedback for us? Let me know in the show notes above and one of us will get back to you! Be an Outliyr, Nick

KI Anwältin Jeannette Gorzala besucht mich nach knapp einem Jahr zum zweiten Map im Podcast. Wir sprechen über den Status Quo des AI Acts und die Rolle des AI Office bei der Auslegung und Implementierung des Gesetzeswerks. Jeannette berichtet von ihren Eindrücken vom Weltwirtschaftsforum in Davos. Spoiler Alert: die Ernüchterung ist groß. Was letztes Jahr noch als die Lösung für eh alles gefeiert wurde, muss sich langsam aber sicher die Frage der Daseinsberechtigung gefallen lassen. Lässt sich KI überhaupt flächendeckend wirtschaftlich implementieren oder verpufft der Zauber gerade und bis auf ein paar Hobby-Youtuber und TikTok-kanäle hat keiner was davon? Wir sprechen über Effizienz, Ressourcenmanagement (Stichwort seltene Erden) und über Zuverlässigkeit. Nachrichten an: deeptalk@mic-rider.com Website: https://www.mic-rider.com/ Host und Redaktion: Patrick Messe (https://www.patrickmesse.at/) Zu Gast: Jeannette Gorzala (https://www.jeannette-gorzala.com/) Bild: Charly Glawischnig (https://www.charlyglawischnig.com/) Ton: Lukas Wurm (https://lukaswurm.com/) Produktion: Mic Rider (https://www.mic-rider.com/)

This episode covers the next part of chapter 17 from: “The first two years of my course at Scottish Church...” to  “...mixed with ejaculations betraying their astonishment.” Summary: In this short and seemingly simple section of the chapter lies some gold dust, but you have to explore underlying meanings behind the narrative as experienced by Paramahansa Yogananda (and orchestrated by Swami Sri Yukteswar!). We weigh in by sharing our personal experiences and reflections on the importance of faith, perseverance, and balancing spiritual pursuits with academic responsibilities. We also felt it right to include some readings on concepts of success, hard work, and reincarnation, as well as the gleaning on some messages from the book Mejda.  0:00 Prior episode; 3:05 A controversial regularity; 17:15 A lifeline; 27:27 Art of Cramming; 44:15 Scraping through an exam; 59:00 Looking ahead. Links discussed in this episode:  https://en.wikipedia.org/wiki/Scottish_Church_College https://en.wikipedia.org/wiki/List_of_alumni_of_Scottish_Church_College Homework for next episode— Read, absorb and make notes on the last part of chapter 17: “On his return from Puri, Sri Yukteswar...” to end of the chapter (and the long footnote). #autobiographyofayogi  #autobiographylinebyline  #paramahansayogananda Autobiography of a Yogi  awake.minute Self-Realization Fellowship Yogoda Satsanga Society of India #SRF #YSS

Try the YouTube Comments Scraper API from Bright Data today. Get the data you want, fast, and in the format you need, without worrying about scalability or security. More details at https://get.brightdata.com/skyag-web-scraper-youtube-comments Bright Data City: New York Address: 500 7th Ave, 9th Floor Office 9A1234 Website: https://bit.ly/3dd7ti2

Nat and Marc are back behind the microphones with a big talk through the Eastenders Live episode and all the changes that Nat's departure from the show will bring. What's next for Nat? Watch this space! Please subscribe, follow, and leave a review. xxx You can find us in all places here; https://podfollow.com/lifewithnat/view INSTA: @natcass1 We're also on Facebook too: https://www.facebook.com/lifewithnatpod A 'Keep It Light Media' Production Sales, advertising, and general enquiries: hello@keepitlightmedia.com SHOW INFO: Life with Nat - it's me! Natalie Cassidy and I'll be chatting away to family, friends and most importantly YOU. I want to pick people's brains on the subjects that I care about- whether that's where all the odd socks go, weight and food or kids on phones. Each week I will be letting you into my life as i chat about my week, share my thoughts on the mundane happenings as well as the serious. I have grown up in the public eye and have never changed because of it. Life with Nat is the podcast for proper people. Come join the community. ♥️ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Today's episode is with Paul Klein, founder of Browserbase. We talked about building browser infrastructure for AI agents, the future of agent authentication, and their open source framework Stagehand.* [00:00:00] Introductions* [00:04:46] AI-specific challenges in browser infrastructure* [00:07:05] Multimodality in AI-Powered Browsing* [00:12:26] Running headless browsers at scale* [00:18:46] Geolocation when proxying* [00:21:25] CAPTCHAs and Agent Auth* [00:28:21] Building “User take over” functionality* [00:33:43] Stagehand: AI web browsing framework* [00:38:58] OpenAI's Operator and computer use agents* [00:44:44] Surprising use cases of Browserbase* [00:47:18] Future of browser automation and market competition* [00:53:11] Being a solo founderTranscriptAlessio [00:00:04]: Hey everyone, welcome to the Latent Space podcast. This is Alessio, partner and CTO at Decibel Partners, and I'm joined by my co-host Swyx, founder of Smol.ai.swyx [00:00:12]: Hey, and today we are very blessed to have our friends, Paul Klein, for the fourth, the fourth, CEO of Browserbase. Welcome.Paul [00:00:21]: Thanks guys. Yeah, I'm happy to be here. I've been lucky to know both of you for like a couple of years now, I think. So it's just like we're hanging out, you know, with three ginormous microphones in front of our face. It's totally normal hangout.swyx [00:00:34]: Yeah. We've actually mentioned you on the podcast, I think, more often than any other Solaris tenant. Just because like you're one of the, you know, best performing, I think, LLM tool companies that have started up in the last couple of years.Paul [00:00:50]: Yeah, I mean, it's been a whirlwind of a year, like Browserbase is actually pretty close to our first birthday. So we are one years old. And going from, you know, starting a company as a solo founder to... To, you know, having a team of 20 people, you know, a series A, but also being able to support hundreds of AI companies that are building AI applications that go out and automate the web. It's just been like, really cool. It's been happening a little too fast. I think like collectively as an AI industry, let's just take a week off together. I took my first vacation actually two weeks ago, and Operator came out on the first day, and then a week later, DeepSeat came out. And I'm like on vacation trying to chill. I'm like, we got to build with this stuff, right? So it's been a breakneck year. But I'm super happy to be here and like talk more about all the stuff we're seeing. And I'd love to hear kind of what you guys are excited about too, and share with it, you know?swyx [00:01:39]: Where to start? So people, you've done a bunch of podcasts. I think I strongly recommend Jack Bridger's Scaling DevTools, as well as Turner Novak's The Peel. And, you know, I'm sure there's others. So you covered your Twilio story in the past, talked about StreamClub, you got acquired to Mux, and then you left to start Browserbase. So maybe we just start with what is Browserbase? Yeah.Paul [00:02:02]: Browserbase is the web browser for your AI. We're building headless browser infrastructure, which are browsers that run in a server environment that's accessible to developers via APIs and SDKs. It's really hard to run a web browser in the cloud. You guys are probably running Chrome on your computers, and that's using a lot of resources, right? So if you want to run a web browser or thousands of web browsers, you can't just spin up a bunch of lambdas. You actually need to use a secure containerized environment. You have to scale it up and down. It's a stateful system. And that infrastructure is, like, super painful. And I know that firsthand, because at my last company, StreamClub, I was CTO, and I was building our own internal headless browser infrastructure. That's actually why we sold the company, is because Mux really wanted to buy our headless browser infrastructure that we'd built. And it's just a super hard problem. And I actually told my co-founders, I would never start another company unless it was a browser infrastructure company. And it turns out that's really necessary in the age of AI, when AI can actually go out and interact with websites, click on buttons, fill in forms. You need AI to do all of that work in an actual browser running somewhere on a server. And BrowserBase powers that.swyx [00:03:08]: While you're talking about it, it occurred to me, not that you're going to be acquired or anything, but it occurred to me that it would be really funny if you became the Nikita Beer of headless browser companies. You just have one trick, and you make browser companies that get acquired.Paul [00:03:23]: I truly do only have one trick. I'm screwed if it's not for headless browsers. I'm not a Go programmer. You know, I'm in AI grant. You know, browsers is an AI grant. But we were the only company in that AI grant batch that used zero dollars on AI spend. You know, we're purely an infrastructure company. So as much as people want to ask me about reinforcement learning, I might not be the best guy to talk about that. But if you want to ask about headless browser infrastructure at scale, I can talk your ear off. So that's really my area of expertise. And it's a pretty niche thing. Like, nobody has done what we're doing at scale before. So we're happy to be the experts.swyx [00:03:59]: You do have an AI thing, stagehand. We can talk about the sort of core of browser-based first, and then maybe stagehand. Yeah, stagehand is kind of the web browsing framework. Yeah.What is Browserbase? Headless Browser Infrastructure ExplainedAlessio [00:04:10]: Yeah. Yeah. And maybe how you got to browser-based and what problems you saw. So one of the first things I worked on as a software engineer was integration testing. Sauce Labs was kind of like the main thing at the time. And then we had Selenium, we had Playbrite, we had all these different browser things. But it's always been super hard to do. So obviously you've worked on this before. When you started browser-based, what were the challenges? What were the AI-specific challenges that you saw versus, there's kind of like all the usual running browser at scale in the cloud, which has been a problem for years. What are like the AI unique things that you saw that like traditional purchase just didn't cover? Yeah.AI-specific challenges in browser infrastructurePaul [00:04:46]: First and foremost, I think back to like the first thing I did as a developer, like as a kid when I was writing code, I wanted to write code that did stuff for me. You know, I wanted to write code to automate my life. And I do that probably by using curl or beautiful soup to fetch data from a web browser. And I think I still do that now that I'm in the cloud. And the other thing that I think is a huge challenge for me is that you can't just create a web site and parse that data. And we all know that now like, you know, taking HTML and plugging that into an LLM, you can extract insights, you can summarize. So it was very clear that now like dynamic web scraping became very possible with the rise of large language models or a lot easier. And that was like a clear reason why there's been more usage of headless browsers, which are necessary because a lot of modern websites don't expose all of their page content via a simple HTTP request. You know, they actually do require you to run this type of code for a specific time. JavaScript on the page to hydrate this. Airbnb is a great example. You go to airbnb.com. A lot of that content on the page isn't there until after they run the initial hydration. So you can't just scrape it with a curl. You need to have some JavaScript run. And a browser is that JavaScript engine that's going to actually run all those requests on the page. So web data retrieval was definitely one driver of starting BrowserBase and the rise of being able to summarize that within LLM. Also, I was familiar with if I wanted to automate a website, I could write one script and that would work for one website. It was very static and deterministic. But the web is non-deterministic. The web is always changing. And until we had LLMs, there was no way to write scripts that you could write once that would run on any website. That would change with the structure of the website. Click the login button. It could mean something different on many different websites. And LLMs allow us to generate code on the fly to actually control that. So I think that rise of writing the generic automation scripts that can work on many different websites, to me, made it clear that browsers are going to be a lot more useful because now you can automate a lot more things without writing. If you wanted to write a script to book a demo call on 100 websites, previously, you had to write 100 scripts. Now you write one script that uses LLMs to generate that script. That's why we built our web browsing framework, StageHand, which does a lot of that work for you. But those two things, web data collection and then enhanced automation of many different websites, it just felt like big drivers for more browser infrastructure that would be required to power these kinds of features.Alessio [00:07:05]: And was multimodality also a big thing?Paul [00:07:08]: Now you can use the LLMs to look, even though the text in the dome might not be as friendly. Maybe my hot take is I was always kind of like, I didn't think vision would be as big of a driver. For UI automation, I felt like, you know, HTML is structured text and large language models are good with structured text. But it's clear that these computer use models are often vision driven, and they've been really pushing things forward. So definitely being multimodal, like rendering the page is required to take a screenshot to give that to a computer use model to take actions on a website. And it's just another win for browser. But I'll be honest, that wasn't what I was thinking early on. I didn't even think that we'd get here so fast with multimodality. I think we're going to have to get back to multimodal and vision models.swyx [00:07:50]: This is one of those things where I forgot to mention in my intro that I'm an investor in Browserbase. And I remember that when you pitched to me, like a lot of the stuff that we have today, we like wasn't on the original conversation. But I did have my original thesis was something that we've talked about on the podcast before, which is take the GPT store, the custom GPT store, all the every single checkbox and plugin is effectively a startup. And this was the browser one. I think the main hesitation, I think I actually took a while to get back to you. The main hesitation was that there were others. Like you're not the first hit list browser startup. It's not even your first hit list browser startup. There's always a question of like, will you be the category winner in a place where there's a bunch of incumbents, to be honest, that are bigger than you? They're just not targeted at the AI space. They don't have the backing of Nat Friedman. And there's a bunch of like, you're here in Silicon Valley. They're not. I don't know.Paul [00:08:47]: I don't know if that's, that was it, but like, there was a, yeah, I mean, like, I think I tried all the other ones and I was like, really disappointed. Like my background is from working at great developer tools, companies, and nothing had like the Vercel like experience. Um, like our biggest competitor actually is partly owned by private equity and they just jacked up their prices quite a bit. And the dashboard hasn't changed in five years. And I actually used them at my last company and tried them and I was like, oh man, like there really just needs to be something that's like the experience of these great infrastructure companies, like Stripe, like clerk, like Vercel that I use in love, but oriented towards this kind of like more specific category, which is browser infrastructure, which is really technically complex. Like a lot of stuff can go wrong on the internet when you're running a browser. The internet is very vast. There's a lot of different configurations. Like there's still websites that only work with internet explorer out there. How do you handle that when you're running your own browser infrastructure? These are the problems that we have to think about and solve at BrowserBase. And it's, it's certainly a labor of love, but I built this for me, first and foremost, I know it's super cheesy and everyone says that for like their startups, but it really, truly was for me. If you look at like the talks I've done even before BrowserBase, and I'm just like really excited to try and build a category defining infrastructure company. And it's, it's rare to have a new category of infrastructure exists. We're here in the Chroma offices and like, you know, vector databases is a new category of infrastructure. Is it, is it, I mean, we can, we're in their office, so, you know, we can, we can debate that one later. That is one.Multimodality in AI-Powered Browsingswyx [00:10:16]: That's one of the industry debates.Paul [00:10:17]: I guess we go back to the LLMOS talk that Karpathy gave way long ago. And like the browser box was very clearly there and it seemed like the people who were building in this space also agreed that browsers are a core primitive of infrastructure for the LLMOS that's going to exist in the future. And nobody was building something there that I wanted to use. So I had to go build it myself.swyx [00:10:38]: Yeah. I mean, exactly that talk that, that honestly, that diagram, every box is a startup and there's the code box and then there's the. The browser box. I think at some point they will start clashing there. There's always the question of the, are you a point solution or are you the sort of all in one? And I think the point solutions tend to win quickly, but then the only ones have a very tight cohesive experience. Yeah. Let's talk about just the hard problems of browser base you have on your website, which is beautiful. Thank you. Was there an agency that you used for that? Yeah. Herb.paris.Paul [00:11:11]: They're amazing. Herb.paris. Yeah. It's H-E-R-V-E. I highly recommend for developers. Developer tools, founders to work with consumer agencies because they end up building beautiful things and the Parisians know how to build beautiful interfaces. So I got to give prep.swyx [00:11:24]: And chat apps, apparently are, they are very fast. Oh yeah. The Mistral chat. Yeah. Mistral. Yeah.Paul [00:11:31]: Late chat.swyx [00:11:31]: Late chat. And then your videos as well, it was professionally shot, right? The series A video. Yeah.Alessio [00:11:36]: Nico did the videos. He's amazing. Not the initial video that you shot at the new one. First one was Austin.Paul [00:11:41]: Another, another video pretty surprised. But yeah, I mean, like, I think when you think about how you talk about your company. You have to think about the way you present yourself. It's, you know, as a developer, you think you evaluate a company based on like the API reliability and the P 95, but a lot of developers say, is the website good? Is the message clear? Do I like trust this founder? I'm building my whole feature on. So I've tried to nail that as well as like the reliability of the infrastructure. You're right. It's very hard. And there's a lot of kind of foot guns that you run into when running headless browsers at scale. Right.Competing with Existing Headless Browser Solutionsswyx [00:12:10]: So let's pick one. You have eight features here. Seamless integration. Scalability. Fast or speed. Secure. Observable. Stealth. That's interesting. Extensible and developer first. What comes to your mind as like the top two, three hardest ones? Yeah.Running headless browsers at scalePaul [00:12:26]: I think just running headless browsers at scale is like the hardest one. And maybe can I nerd out for a second? Is that okay? I heard this is a technical audience, so I'll talk to the other nerds. Whoa. They were listening. Yeah. They're upset. They're ready. The AGI is angry. Okay. So. So how do you run a browser in the cloud? Let's start with that, right? So let's say you're using a popular browser automation framework like Puppeteer, Playwright, and Selenium. Maybe you've written a code, some code locally on your computer that opens up Google. It finds the search bar and then types in, you know, search for Latent Space and hits the search button. That script works great locally. You can see the little browser open up. You want to take that to production. You want to run the script in a cloud environment. So when your laptop is closed, your browser is doing something. The browser is doing something. Well, I, we use Amazon. You can see the little browser open up. You know, the first thing I'd reach for is probably like some sort of serverless infrastructure. I would probably try and deploy on a Lambda. But Chrome itself is too big to run on a Lambda. It's over 250 megabytes. So you can't easily start it on a Lambda. So you maybe have to use something like Lambda layers to squeeze it in there. Maybe use a different Chromium build that's lighter. And you get it on the Lambda. Great. It works. But it runs super slowly. It's because Lambdas are very like resource limited. They only run like with one vCPU. You can run one process at a time. Remember, Chromium is super beefy. It's barely running on my MacBook Air. I'm still downloading it from a pre-run. Yeah, from the test earlier, right? I'm joking. But it's big, you know? So like Lambda, it just won't work really well. Maybe it'll work, but you need something faster. Your users want something faster. Okay. Well, let's put it on a beefier instance. Let's get an EC2 server running. Let's throw Chromium on there. Great. Okay. I can, that works well with one user. But what if I want to run like 10 Chromium instances, one for each of my users? Okay. Well, I might need two EC2 instances. Maybe 10. All of a sudden, you have multiple EC2 instances. This sounds like a problem for Kubernetes and Docker, right? Now, all of a sudden, you're using ECS or EKS, the Kubernetes or container solutions by Amazon. You're spending up and down containers, and you're spending a whole engineer's time on kind of maintaining this stateful distributed system. Those are some of the worst systems to run because when it's a stateful distributed system, it means that you are bound by the connections to that thing. You have to keep the browser open while someone is working with it, right? That's just a painful architecture to run. And there's all this other little gotchas with Chromium, like Chromium, which is the open source version of Chrome, by the way. You have to install all these fonts. You want emojis working in your browsers because your vision model is looking for the emoji. You need to make sure you have the emoji fonts. You need to make sure you have all the right extensions configured, like, oh, do you want ad blocking? How do you configure that? How do you actually record all these browser sessions? Like it's a headless browser. You can't look at it. So you need to have some sort of observability. Maybe you're recording videos and storing those somewhere. It all kind of adds up to be this just giant monster piece of your project when all you wanted to do was run a lot of browsers in production for this little script to go to google.com and search. And when I see a complex distributed system, I see an opportunity to build a great infrastructure company. And we really abstract that away with Browserbase where our customers can use these existing frameworks, Playwright, Publisher, Selenium, or our own stagehand and connect to our browsers in a serverless-like way. And control them, and then just disconnect when they're done. And they don't have to think about the complex distributed system behind all of that. They just get a browser running anywhere, anytime. Really easy to connect to.swyx [00:15:55]: I'm sure you have questions. My standard question with anything, so essentially you're a serverless browser company, and there's been other serverless things that I'm familiar with in the past, serverless GPUs, serverless website hosting. That's where I come from with Netlify. One question is just like, you promised to spin up thousands of servers. You promised to spin up thousands of browsers in milliseconds. I feel like there's no real solution that does that yet. And I'm just kind of curious how. The only solution I know, which is to kind of keep a kind of warm pool of servers around, which is expensive, but maybe not so expensive because it's just CPUs. So I'm just like, you know. Yeah.Browsers as a Core Primitive in AI InfrastructurePaul [00:16:36]: You nailed it, right? I mean, how do you offer a serverless-like experience with something that is clearly not serverless, right? And the answer is, you need to be able to run... We run many browsers on single nodes. We use Kubernetes at browser base. So we have many pods that are being scheduled. We have to predictably schedule them up or down. Yes, thousands of browsers in milliseconds is the best case scenario. If you hit us with 10,000 requests, you may hit a slower cold start, right? So we've done a lot of work on predictive scaling and being able to kind of route stuff to different regions where we have multiple regions of browser base where we have different pools available. You can also pick the region you want to go to based on like lower latency, round trip, time latency. It's very important with these types of things. There's a lot of requests going over the wire. So for us, like having a VM like Firecracker powering everything under the hood allows us to be super nimble and spin things up or down really quickly with strong multi-tenancy. But in the end, this is like the complex infrastructural challenges that we have to kind of deal with at browser base. And we have a lot more stuff on our roadmap to allow customers to have more levers to pull to exchange, do you want really fast browser startup times or do you want really low costs? And if you're willing to be more flexible on that, we may be able to kind of like work better for your use cases.swyx [00:17:44]: Since you used Firecracker, shouldn't Fargate do that for you or did you have to go lower level than that? We had to go lower level than that.Paul [00:17:51]: I find this a lot with Fargate customers, which is alarming for Fargate. We used to be a giant Fargate customer. Actually, the first version of browser base was ECS and Fargate. And unfortunately, it's a great product. I think we were actually the largest Fargate customer in our region for a little while. No, what? Yeah, seriously. And unfortunately, it's a great product, but I think if you're an infrastructure company, you actually have to have a deeper level of control over these primitives. I think it's the same thing is true with databases. We've used other database providers and I think-swyx [00:18:21]: Yeah, serverless Postgres.Paul [00:18:23]: Shocker. When you're an infrastructure company, you're on the hook if any provider has an outage. And I can't tell my customers like, hey, we went down because so-and-so went down. That's not acceptable. So for us, we've really moved to bringing things internally. It's kind of opposite of what we preach. We tell our customers, don't build this in-house, but then we're like, we build a lot of stuff in-house. But I think it just really depends on what is in the critical path. We try and have deep ownership of that.Alessio [00:18:46]: On the distributed location side, how does that work for the web where you might get sort of different content in different locations, but the customer is expecting, you know, if you're in the US, I'm expecting the US version. But if you're spinning up my browser in France, I might get the French version. Yeah.Paul [00:19:02]: Yeah. That's a good question. Well, generally, like on the localization, there is a thing called locale in the browser. You can set like what your locale is. If you're like in the ENUS browser or not, but some things do IP, IP based routing. And in that case, you may want to have a proxy. Like let's say you're running something in the, in Europe, but you want to make sure you're showing up from the US. You may want to use one of our proxy features so you can turn on proxies to say like, make sure these connections always come from the United States, which is necessary too, because when you're browsing the web, you're coming from like a, you know, data center IP, and that can make things a lot harder to browse web. So we do have kind of like this proxy super network. Yeah. We have a proxy for you based on where you're going, so you can reliably automate the web. But if you get scheduled in Europe, that doesn't happen as much. We try and schedule you as close to, you know, your origin that you're trying to go to. But generally you have control over the regions you can put your browsers in. So you can specify West one or East one or Europe. We only have one region of Europe right now, actually. Yeah.Alessio [00:19:55]: What's harder, the browser or the proxy? I feel like to me, it feels like actually proxying reliably at scale. It's much harder than spending up browsers at scale. I'm curious. It's all hard.Paul [00:20:06]: It's layers of hard, right? Yeah. I think it's different levels of hard. I think the thing with the proxy infrastructure is that we work with many different web proxy providers and some are better than others. Some have good days, some have bad days. And our customers who've built browser infrastructure on their own, they have to go and deal with sketchy actors. Like first they figure out their own browser infrastructure and then they got to go buy a proxy. And it's like you can pay in Bitcoin and it just kind of feels a little sus, right? It's like you're buying drugs when you're trying to get a proxy online. We have like deep relationships with these counterparties. We're able to audit them and say, is this proxy being sourced ethically? Like it's not running on someone's TV somewhere. Is it free range? Yeah. Free range organic proxies, right? Right. We do a level of diligence. We're SOC 2. So we have to understand what is going on here. But then we're able to make sure that like we route around proxy providers not working. There's proxy providers who will just, the proxy will stop working all of a sudden. And then if you don't have redundant proxying on your own browsers, that's hard down for you or you may get some serious impacts there. With us, like we intelligently know, hey, this proxy is not working. Let's go to this one. And you can kind of build a network of multiple providers to really guarantee the best uptime for our customers. Yeah. So you don't own any proxies? We don't own any proxies. You're right. The team has been saying who wants to like take home a little proxy server, but not yet. We're not there yet. You know?swyx [00:21:25]: It's a very mature market. I don't think you should build that yourself. Like you should just be a super customer of them. Yeah. Scraping, I think, is the main use case for that. I guess. Well, that leads us into CAPTCHAs and also off, but let's talk about CAPTCHAs. You had a little spiel that you wanted to talk about CAPTCHA stuff.Challenges of Scaling Browser InfrastructurePaul [00:21:43]: Oh, yeah. I was just, I think a lot of people ask, if you're thinking about proxies, you're thinking about CAPTCHAs too. I think it's the same thing. You can go buy CAPTCHA solvers online, but it's the same buying experience. It's some sketchy website, you have to integrate it. It's not fun to buy these things and you can't really trust that the docs are bad. What Browserbase does is we integrate a bunch of different CAPTCHAs. We do some stuff in-house, but generally we just integrate with a bunch of known vendors and continually monitor and maintain these things and say, is this working or not? Can we route around it or not? These are CAPTCHA solvers. CAPTCHA solvers, yeah. Not CAPTCHA providers, CAPTCHA solvers. Yeah, sorry. CAPTCHA solvers. We really try and make sure all of that works for you. I think as a dev, if I'm buying infrastructure, I want it all to work all the time and it's important for us to provide that experience by making sure everything does work and monitoring it on our own. Yeah. Right now, the world of CAPTCHAs is tricky. I think AI agents in particular are very much ahead of the internet infrastructure. CAPTCHAs are designed to block all types of bots, but there are now good bots and bad bots. I think in the future, CAPTCHAs will be able to identify who a good bot is, hopefully via some sort of KYC. For us, we've been very lucky. We have very little to no known abuse of Browserbase because we really look into who we work with. And for certain types of CAPTCHA solving, we only allow them on certain types of plans because we want to make sure that we can know what people are doing, what their use cases are. And that's really allowed us to try and be an arbiter of good bots, which is our long term goal. I want to build great relationships with people like Cloudflare so we can agree, hey, here are these acceptable bots. We'll identify them for you and make sure we flag when they come to your website. This is a good bot, you know?Alessio [00:23:23]: I see. And Cloudflare said they want to do more of this. So they're going to set by default, if they think you're an AI bot, they're going to reject. I'm curious if you think this is something that is going to be at the browser level or I mean, the DNS level with Cloudflare seems more where it should belong. But I'm curious how you think about it.Paul [00:23:40]: I think the web's going to change. You know, I think that the Internet as we have it right now is going to change. And we all need to just accept that the cat is out of the bag. And instead of kind of like wishing the Internet was like it was in the 2000s, we can have free content line that wouldn't be scraped. It's just it's not going to happen. And instead, we should think about like, one, how can we change? How can we change the models of, you know, information being published online so people can adequately commercialize it? But two, how do we rebuild applications that expect that AI agents are going to log in on their behalf? Those are the things that are going to allow us to kind of like identify good and bad bots. And I think the team at Clerk has been doing a really good job with this on the authentication side. I actually think that auth is the biggest thing that will prevent agents from accessing stuff, not captchas. And I think there will be agent auth in the future. I don't know if it's going to happen from an individual company, but actually authentication providers that have a, you know, hidden login as agent feature, which will then you put in your email, you'll get a push notification, say like, hey, your browser-based agent wants to log into your Airbnb. You can approve that and then the agent can proceed. That really circumvents the need for captchas or logging in as you and sharing your password. I think agent auth is going to be one way we identify good bots going forward. And I think a lot of this captcha solving stuff is really short-term problems as the internet kind of reorients itself around how it's going to work with agents browsing the web, just like people do. Yeah.Managing Distributed Browser Locations and Proxiesswyx [00:24:59]: Stitch recently was on Hacker News for talking about agent experience, AX, which is a thing that Netlify is also trying to clone and coin and talk about. And we've talked about this on our previous episodes before in a sense that I actually think that's like maybe the only part of the tech stack that needs to be kind of reinvented for agents. Everything else can stay the same, CLIs, APIs, whatever. But auth, yeah, we need agent auth. And it's mostly like short-lived, like it should not, it should be a distinct, identity from the human, but paired. I almost think like in the same way that every social network should have your main profile and then your alt accounts or your Finsta, it's almost like, you know, every, every human token should be paired with the agent token and the agent token can go and do stuff on behalf of the human token, but not be presumed to be the human. Yeah.Paul [00:25:48]: It's like, it's, it's actually very similar to OAuth is what I'm thinking. And, you know, Thread from Stitch is an investor, Colin from Clerk, Octaventures, all investors in browser-based because like, I hope they solve this because they'll make browser-based submission more possible. So we don't have to overcome all these hurdles, but I think it will be an OAuth-like flow where an agent will ask to log in as you, you'll approve the scopes. Like it can book an apartment on Airbnb, but it can't like message anybody. And then, you know, the agent will have some sort of like role-based access control within an application. Yeah. I'm excited for that.swyx [00:26:16]: The tricky part is just, there's one, one layer of delegation here, which is like, you're authoring my user's user or something like that. I don't know if that's tricky or not. Does that make sense? Yeah.Paul [00:26:25]: You know, actually at Twilio, I worked on the login identity and access. Management teams, right? So like I built Twilio's login page.swyx [00:26:31]: You were an intern on that team and then you became the lead in two years? Yeah.Paul [00:26:34]: Yeah. I started as an intern in 2016 and then I was the tech lead of that team. How? That's not normal. I didn't have a life. He's not normal. Look at this guy. I didn't have a girlfriend. I just loved my job. I don't know. I applied to 500 internships for my first job and I got rejected from every single one of them except for Twilio and then eventually Amazon. And they took a shot on me and like, I was getting paid money to write code, which was my dream. Yeah. Yeah. I'm very lucky that like this coding thing worked out because I was going to be doing it regardless. And yeah, I was able to kind of spend a lot of time on a team that was growing at a company that was growing. So it informed a lot of this stuff here. I think these are problems that have been solved with like the SAML protocol with SSO. I think it's a really interesting stuff with like WebAuthn, like these different types of authentication, like schemes that you can use to authenticate people. The tooling is all there. It just needs to be tweaked a little bit to work for agents. And I think the fact that there are companies that are already. Providing authentication as a service really sets it up. Well, the thing that's hard is like reinventing the internet for agents. We don't want to rebuild the internet. That's an impossible task. And I think people often say like, well, we'll have this second layer of APIs built for agents. I'm like, we will for the top use cases, but instead of we can just tweak the internet as is, which is on the authentication side, I think we're going to be the dumb ones going forward. Unfortunately, I think AI is going to be able to do a lot of the tasks that we do online, which means that it will be able to go to websites, click buttons on our behalf and log in on our behalf too. So with this kind of like web agent future happening, I think with some small structural changes, like you said, it feels like it could all slot in really nicely with the existing internet.Handling CAPTCHAs and Agent Authenticationswyx [00:28:08]: There's one more thing, which is the, your live view iframe, which lets you take, take control. Yeah. Obviously very key for operator now, but like, was, is there anything interesting technically there or that the people like, well, people always want this.Paul [00:28:21]: It was really hard to build, you know, like, so, okay. Headless browsers, you don't see them, right. They're running. They're running in a cloud somewhere. You can't like look at them. And I just want to really make, it's a weird name. I wish we came up with a better name for this thing, but you can't see them. Right. But customers don't trust AI agents, right. At least the first pass. So what we do with our live view is that, you know, when you use browser base, you can actually embed a live view of the browser running in the cloud for your customer to see it working. And that's what the first reason is the build trust, like, okay, so I have this script. That's going to go automate a website. I can embed it into my web application via an iframe and my customer can watch. I think. And then we added two way communication. So now not only can you watch the browser kind of being operated by AI, if you want to pause and actually click around type within this iframe that's controlling a browser, that's also possible. And this is all thanks to some of the lower level protocol, which is called the Chrome DevTools protocol. It has a API called start screencast, and you can also send mouse clicks and button clicks to a remote browser. And this is all embeddable within iframes. You have a browser within a browser, yo. And then you simulate the screen, the click on the other side. Exactly. And this is really nice often for, like, let's say, a capture that can't be solved. You saw this with Operator, you know, Operator actually uses a different approach. They use VNC. So, you know, you're able to see, like, you're seeing the whole window here. What we're doing is something a little lower level with the Chrome DevTools protocol. It's just PNGs being streamed over the wire. But the same thing is true, right? Like, hey, I'm running a window. Pause. Can you do something in this window? Human. Okay, great. Resume. Like sometimes 2FA tokens. Like if you get that text message, you might need a person to type that in. Web agents need human-in-the-loop type workflows still. You still need a person to interact with the browser. And building a UI to proxy that is kind of hard. You may as well just show them the whole browser and say, hey, can you finish this up for me? And then let the AI proceed on afterwards. Is there a future where I stream my current desktop to browser base? I don't think so. I think we're very much cloud infrastructure. Yeah. You know, but I think a lot of the stuff we're doing, we do want to, like, build tools. Like, you know, we'll talk about the stage and, you know, web agent framework in a second. But, like, there's a case where a lot of people are going desktop first for, you know, consumer use. And I think cloud is doing a lot of this, where I expect to see, you know, MCPs really oriented around the cloud desktop app for a reason, right? Like, I think a lot of these tools are going to run on your computer because it makes... I think it's breaking out. People are putting it on a server. Oh, really? Okay. Well, sweet. We'll see. We'll see that. I was surprised, though, wasn't I? I think that the browser company, too, with Dia Browser, it runs on your machine. You know, it's going to be...swyx [00:30:50]: What is it?Paul [00:30:51]: So, Dia Browser, as far as I understand... I used to use Arc. Yeah. I haven't used Arc. But I'm a big fan of the browser company. I think they're doing a lot of cool stuff in consumer. As far as I understand, it's a browser where you have a sidebar where you can, like, chat with it and it can control the local browser on your machine. So, if you imagine, like, what a consumer web agent is, which it lives alongside your browser, I think Google Chrome has Project Marina, I think. I almost call it Project Marinara for some reason. I don't know why. It's...swyx [00:31:17]: No, I think it's someone really likes the Waterworld. Oh, I see. The classic Kevin Costner. Yeah.Paul [00:31:22]: Okay. Project Marinara is a similar thing to the Dia Browser, in my mind, as far as I understand it. You have a browser that has an AI interface that will take over your mouse and keyboard and control the browser for you. Great for consumer use cases. But if you're building applications that rely on a browser and it's more part of a greater, like, AI app experience, you probably need something that's more like infrastructure, not a consumer app.swyx [00:31:44]: Just because I have explored a little bit in this area, do people want branching? So, I have the state. Of whatever my browser's in. And then I want, like, 100 clones of this state. Do people do that? Or...Paul [00:31:56]: People don't do it currently. Yeah. But it's definitely something we're thinking about. I think the idea of forking a browser is really cool. Technically, kind of hard. We're starting to see this in code execution, where people are, like, forking some, like, code execution, like, processes or forking some tool calls or branching tool calls. Haven't seen it at the browser level yet. But it makes sense. Like, if an AI agent is, like, using a website and it's not sure what path it wants to take to crawl this website. To find the information it's looking for. It would make sense for it to explore both paths in parallel. And that'd be a very, like... A road not taken. Yeah. And hopefully find the right answer. And then say, okay, this was actually the right one. And memorize that. And go there in the future. On the roadmap. For sure. Don't make my roadmap, please. You know?Alessio [00:32:37]: How do you actually do that? Yeah. How do you fork? I feel like the browser is so stateful for so many things.swyx [00:32:42]: Serialize the state. Restore the state. I don't know.Paul [00:32:44]: So, it's one of the reasons why we haven't done it yet. It's hard. You know? Like, to truly fork, it's actually quite difficult. The naive way is to open the same page in a new tab and then, like, hope that it's at the same thing. But if you have a form halfway filled, you may have to, like, take the whole, you know, container. Pause it. All the memory. Duplicate it. Restart it from there. It could be very slow. So, we haven't found a thing. Like, the easy thing to fork is just, like, copy the page object. You know? But I think there needs to be something a little bit more robust there. Yeah.swyx [00:33:12]: So, MorphLabs has this infinite branch thing. Like, wrote a custom fork of Linux or something that let them save the system state and clone it. MorphLabs, hit me up. I'll be a customer. Yeah. That's the only. I think that's the only way to do it. Yeah. Like, unless Chrome has some special API for you. Yeah.Paul [00:33:29]: There's probably something we'll reverse engineer one day. I don't know. Yeah.Alessio [00:33:32]: Let's talk about StageHand, the AI web browsing framework. You have three core components, Observe, Extract, and Act. Pretty clean landing page. What was the idea behind making a framework? Yeah.Stagehand: AI web browsing frameworkPaul [00:33:43]: So, there's three frameworks that are very popular or already exist, right? Puppeteer, Playwright, Selenium. Those are for building hard-coded scripts to control websites. And as soon as I started to play with LLMs plus browsing, I caught myself, you know, code-genning Playwright code to control a website. I would, like, take the DOM. I'd pass it to an LLM. I'd say, can you generate the Playwright code to click the appropriate button here? And it would do that. And I was like, this really should be part of the frameworks themselves. And I became really obsessed with SDKs that take natural language as part of, like, the API input. And that's what StageHand is. StageHand exposes three APIs, and it's a super set of Playwright. So, if you go to a page, you may want to take an action, click on the button, fill in the form, etc. That's what the act command is for. You may want to extract some data. This one takes a natural language, like, extract the winner of the Super Bowl from this page. You can give it a Zod schema, so it returns a structured output. And then maybe you're building an API. You can do an agent loop, and you want to kind of see what actions are possible on this page before taking one. You can do observe. So, you can observe the actions on the page, and it will generate a list of actions. You can guide it, like, give me actions on this page related to buying an item. And you can, like, buy it now, add to cart, view shipping options, and pass that to an LLM, an agent loop, to say, what's the appropriate action given this high-level goal? So, StageHand isn't a web agent. It's a framework for building web agents. And we think that agent loops are actually pretty close to the application layer because every application probably has different goals or different ways it wants to take steps. I don't think I've seen a generic. Maybe you guys are the experts here. I haven't seen, like, a really good AI agent framework here. Everyone kind of has their own special sauce, right? I see a lot of developers building their own agent loops, and they're using tools. And I view StageHand as the browser tool. So, we expose act, extract, observe. Your agent can call these tools. And from that, you don't have to worry about it. You don't have to worry about generating playwright code performantly. You don't have to worry about running it. You can kind of just integrate these three tool calls into your agent loop and reliably automate the web.swyx [00:35:48]: A special shout-out to Anirudh, who I met at your dinner, who I think listens to the pod. Yeah. Hey, Anirudh.Paul [00:35:54]: Anirudh's a man. He's a StageHand guy.swyx [00:35:56]: I mean, the interesting thing about each of these APIs is they're kind of each startup. Like, specifically extract, you know, Firecrawler is extract. There's, like, Expand AI. There's a whole bunch of, like, extract companies. They just focus on extract. I'm curious. Like, I feel like you guys are going to collide at some point. Like, right now, it's friendly. Everyone's in a blue ocean. At some point, it's going to be valuable enough that there's some turf battle here. I don't think you have a dog in a fight. I think you can mock extract to use an external service if they're better at it than you. But it's just an observation that, like, in the same way that I see each option, each checkbox in the side of custom GBTs becoming a startup or each box in the Karpathy chart being a startup. Like, this is also becoming a thing. Yeah.Paul [00:36:41]: I mean, like, so the way StageHand works is that it's MIT-licensed, completely open source. You bring your own API key to your LLM of choice. You could choose your LLM. We don't make any money off of the extract or really. We only really make money if you choose to run it with our browser. You don't have to. You can actually use your own browser, a local browser. You know, StageHand is completely open source for that reason. And, yeah, like, I think if you're building really complex web scraping workflows, I don't know if StageHand is the tool for you. I think it's really more if you're building an AI agent that needs a few general tools or if it's doing a lot of, like, web automation-intensive work. But if you're building a scraping company, StageHand is not your thing. You probably want something that's going to, like, get HTML content, you know, convert that to Markdown, query it. That's not what StageHand does. StageHand is more about reliability. I think we focus a lot on reliability and less so on cost optimization and speed at this point.swyx [00:37:33]: I actually feel like StageHand, so the way that StageHand works, it's like, you know, page.act, click on the quick start. Yeah. It's kind of the integration test for the code that you would have to write anyway, like the Puppeteer code that you have to write anyway. And when the page structure changes, because it always does, then this is still the test. This is still the test that I would have to write. Yeah. So it's kind of like a testing framework that doesn't need implementation detail.Paul [00:37:56]: Well, yeah. I mean, Puppeteer, Playwright, and Slenderman were all designed as testing frameworks, right? Yeah. And now people are, like, hacking them together to automate the web. I would say, and, like, maybe this is, like, me being too specific. But, like, when I write tests, if the page structure changes. Without me knowing, I want that test to fail. So I don't know if, like, AI, like, regenerating that. Like, people are using StageHand for testing. But it's more for, like, usability testing, not, like, testing of, like, does the front end, like, has it changed or not. Okay. But generally where we've seen people, like, really, like, take off is, like, if they're using, you know, something. If they want to build a feature in their application that's kind of like Operator or Deep Research, they're using StageHand to kind of power that tool calling in their own agent loop. Okay. Cool.swyx [00:38:37]: So let's go into Operator, the first big agent launch of the year from OpenAI. Seems like they have a whole bunch scheduled. You were on break and your phone blew up. What's your just general view of computer use agents is what they're calling it. The overall category before we go into Open Operator, just the overall promise of Operator. I will observe that I tried it once. It was okay. And I never tried it again.OpenAI's Operator and computer use agentsPaul [00:38:58]: That tracks with my experience, too. Like, I'm a huge fan of the OpenAI team. Like, I think that I do not view Operator as the company. I'm not a company killer for browser base at all. I think it actually shows people what's possible. I think, like, computer use models make a lot of sense. And I'm actually most excited about computer use models is, like, their ability to, like, really take screenshots and reasoning and output steps. I think that using mouse click or mouse coordinates, I've seen that proved to be less reliable than I would like. And I just wonder if that's the right form factor. What we've done with our framework is anchor it to the DOM itself, anchor it to the actual item. So, like, if it's clicking on something, it's clicking on that thing, you know? Like, it's more accurate. No matter where it is. Yeah, exactly. Because it really ties in nicely. And it can handle, like, the whole viewport in one go, whereas, like, Operator can only handle what it sees. Can you hover? Is hovering a thing that you can do? I don't know if we expose it as a tool directly, but I'm sure there's, like, an API for hovering. Like, move mouse to this position. Yeah, yeah, yeah. I think you can trigger hover, like, via, like, the JavaScript on the DOM itself. But, no, I think, like, when we saw computer use, everyone's eyes lit up because they realized, like, wow, like, AI is going to actually automate work for people. And I think seeing that kind of happen from both of the labs, and I'm sure we're going to see more labs launch computer use models, I'm excited to see all the stuff that people build with it. I think that I'd love to see computer use power, like, controlling a browser on browser base. And I think, like, Open Operator, which was, like, our open source version of OpenAI's Operator, was our first take on, like, how can we integrate these models into browser base? And we handle the infrastructure and let the labs do the models. I don't have a sense that Operator will be released as an API. I don't know. Maybe it will. I'm curious to see how well that works because I think it's going to be really hard for a company like OpenAI to do things like support CAPTCHA solving or, like, have proxies. Like, I think it's hard for them structurally. Imagine this New York Times headline, OpenAI CAPTCHA solving. Like, that would be a pretty bad headline, this New York Times headline. Browser base solves CAPTCHAs. No one cares. No one cares. And, like, our investors are bored. Like, we're all okay with this, you know? We're building this company knowing that the CAPTCHA solving is short-lived until we figure out how to authenticate good bots. I think it's really hard for a company like OpenAI, who has this brand that's so, so good, to balance with, like, the icky parts of web automation, which it can be kind of complex to solve. I'm sure OpenAI knows who to call whenever they need you. Yeah, right. I'm sure they'll have a great partnership.Alessio [00:41:23]: And is Open Operator just, like, a marketing thing for you? Like, how do you think about resource allocation? So, you can spin this up very quickly. And now there's all this, like, open deep research, just open all these things that people are building. We started it, you know. You're the original Open. We're the original Open operator, you know? Is it just, hey, look, this is a demo, but, like, we'll help you build out an actual product for yourself? Like, are you interested in going more of a product route? That's kind of the OpenAI way, right? They started as a model provider and then…Paul [00:41:53]: Yeah, we're not interested in going the product route yet. I view Open Operator as a model provider. It's a reference project, you know? Let's show people how to build these things using the infrastructure and models that are out there. And that's what it is. It's, like, Open Operator is very simple. It's an agent loop. It says, like, take a high-level goal, break it down into steps, use tool calling to accomplish those steps. It takes screenshots and feeds those screenshots into an LLM with the step to generate the right action. It uses stagehand under the hood to actually execute this action. It doesn't use a computer use model. And it, like, has a nice interface using the live view that we talked about, the iframe, to embed that into an application. So I felt like people on launch day wanted to figure out how to build their own version of this. And we turned that around really quickly to show them. And I hope we do that with other things like deep research. We don't have a deep research launch yet. I think David from AOMNI actually has an amazing open deep research that he launched. It has, like, 10K GitHub stars now. So he's crushing that. But I think if people want to build these features natively into their application, they need good reference projects. And I think Open Operator is a good example of that.swyx [00:42:52]: I don't know. Actually, I'm actually pretty bullish on API-driven operator. Because that's the only way that you can sort of, like, once it's reliable enough, obviously. And now we're nowhere near. But, like, give it five years. It'll happen, you know. And then you can sort of spin this up and browsers are working in the background and you don't necessarily have to know. And it just is booking restaurants for you, whatever. I can definitely see that future happening. I had this on the landing page here. This might be a slightly out of order. But, you know, you have, like, sort of three use cases for browser base. Open Operator. Or this is the operator sort of use case. It's kind of like the workflow automation use case. And it completes with UiPath in the sort of RPA category. Would you agree with that? Yeah, I would agree with that. And then there's Agents we talked about already. And web scraping, which I imagine would be the bulk of your workload right now, right?Paul [00:43:40]: No, not at all. I'd say actually, like, the majority is browser automation. We're kind of expensive for web scraping. Like, I think that if you're building a web scraping product, if you need to do occasional web scraping or you have to do web scraping that works every single time, you want to use browser automation. Yeah. You want to use browser-based. But if you're building web scraping workflows, what you should do is have a waterfall. You should have the first request is a curl to the website. See if you can get it without even using a browser. And then the second request may be, like, a scraping-specific API. There's, like, a thousand scraping APIs out there that you can use to try and get data. Scraping B. Scraping B is a great example, right? Yeah. And then, like, if those two don't work, bring out the heavy hitter. Like, browser-based will 100% work, right? It will load the page in a real browser, hydrate it. I see.swyx [00:44:21]: Because a lot of people don't render to JS.swyx [00:44:25]: Yeah, exactly.Paul [00:44:26]: So, I mean, the three big use cases, right? Like, you know, automation, web data collection, and then, you know, if you're building anything agentic that needs, like, a browser tool, you want to use browser-based.Alessio [00:44:35]: Is there any use case that, like, you were super surprised by that people might not even think about? Oh, yeah. Or is it, yeah, anything that you can share? The long tail is crazy. Yeah.Surprising use cases of BrowserbasePaul [00:44:44]: One of the case studies on our website that I think is the most interesting is this company called Benny. So, the way that it works is if you're on food stamps in the United States, you can actually get rebates if you buy certain things. Yeah. You buy some vegetables. You submit your receipt to the government. They'll give you a little rebate back. Say, hey, thanks for buying vegetables. It's good for you. That process of submitting that receipt is very painful. And the way Benny works is you use their app to take a photo of your receipt, and then Benny will go submit that receipt for you and then deposit the money into your account. That's actually using no AI at all. It's all, like, hard-coded scripts. They maintain the scripts. They've been doing a great job. And they build this amazing consumer app. But it's an example of, like, all these, like, tedious workflows that people have to do to kind of go about their business. And they're doing it for the sake of their day-to-day lives. And I had never known about, like, food stamp rebates or the complex forms you have to do to fill them. But the world is powered by millions and millions of tedious forms, visas. You know, Emirate Lighthouse is a customer, right? You know, they do the O1 visa. Millions and millions of forms are taking away humans' time. And I hope that Browserbase can help power software that automates away the web forms that we don't need anymore. Yeah.swyx [00:45:49]: I mean, I'm very supportive of that. I mean, forms. I do think, like, government itself is a big part of it. I think the government itself should embrace AI more to do more sort of human-friendly form filling. Mm-hmm. But I'm not optimistic. I'm not holding my breath. Yeah. We'll see. Okay. I think I'm about to zoom out. I have a little brief thing on computer use, and then we can talk about founder stuff, which is, I tend to think of developer tooling markets in impossible triangles, where everyone starts in a niche, and then they start to branch out. So I already hinted at a little bit of this, right? We mentioned more. We mentioned E2B. We mentioned Firecrawl. And then there's Browserbase. So there's, like, all this stuff of, like, have serverless virtual computer that you give to an agent and let them do stuff with it. And there's various ways of connecting it to the internet. You can just connect to a search API, like SERP API, whatever other, like, EXA is another one. That's what you're searching. You can also have a JSON markdown extractor, which is Firecrawl. Or you can have a virtual browser like Browserbase, or you can have a virtual machine like Morph. And then there's also maybe, like, a virtual sort of code environment, like Code Interpreter. So, like, there's just, like, a bunch of different ways to tackle the problem of give a computer to an agent. And I'm just kind of wondering if you see, like, everyone's just, like, happily coexisting in their respective niches. And as a developer, I just go and pick, like, a shopping basket of one of each. Or do you think that you eventually, people will collide?Future of browser automation and market competitionPaul [00:47:18]: I think that currently it's not a zero-sum market. Like, I think we're talking about... I think we're talking about all of knowledge work that people do that can be automated online. All of these, like, trillions of hours that happen online where people are working. And I think that there's so much software to be built that, like, I tend not to think about how these companies will collide. I just try to solve the problem as best as I can and make this specific piece of infrastructure, which I think is an important primitive, the best I possibly can. And yeah. I think there's players that are actually going to like it. I think there's players that are going to launch, like, over-the-top, you know, platforms, like agent platforms that have all these tools built in, right? Like, who's building the rippling for agent tools that has the search tool, the browser tool, the operating system tool, right? There are some. There are some. There are some, right? And I think in the end, what I have seen as my time as a developer, and I look at all the favorite tools that I have, is that, like, for tools and primitives with sufficient levels of complexity, you need to have a solution that's really bespoke to that primitive, you know? And I am sufficiently convinced that the browser is complex enough to deserve a primitive. Obviously, I have to. I'm the founder of BrowserBase, right? I'm talking my book. But, like, I think maybe I can give you one spicy take against, like, maybe just whole OS running. I think that when I look at computer use when it first came out, I saw that the majority of use cases for computer use were controlling a browser. And do we really need to run an entire operating system just to control a browser? I don't think so. I don't think that's necessary. You know, BrowserBase can run browsers for way cheaper than you can if you're running a full-fledged OS with a GUI, you know, operating system. And I think that's just an advantage of the browser. It is, like, browsers are little OSs, and you can run them very efficiently if you orchestrate it well. And I think that allows us to offer 90% of the, you know, functionality in the platform needed at 10% of the cost of running a full OS. Yeah.Open Operator: Browserbase's Open-Source Alternativeswyx [00:49:16]: I definitely see the logic in that. There's a Mark Andreessen quote. I don't know if you know this one. Where he basically observed that the browser is turning the operating system into a poorly debugged set of device drivers, because most of the apps are moved from the OS to the browser. So you can just run browsers.Paul [00:49:31]: There's a place for OSs, too. Like, I think that there are some applications that only run on Windows operating systems. And Eric from pig.dev in this upcoming YC batch, or last YC batch, like, he's building all run tons of Windows operating systems for you to control with your agent. And like, there's some legacy EHR systems that only run on Internet-controlled systems. Yeah.Paul [00:49:54]: I think that's it. I think, like, there are use cases for specific operating systems for specific legacy software. And like, I'm excited to see what he does with that. I just wanted to give a shout out to the pig.dev website.swyx [00:50:06]: The pigs jump when you click on them. Yeah. That's great.Paul [00:50:08]: Eric, he's the former co-founder of banana.dev, too.swyx [00:50:11]: Oh, that Eric. Yeah. That Eric. Okay. Well, he abandoned bananas for pigs. I hope he doesn't start going around with pigs now.Alessio [00:50:18]: Like he was going around with bananas. A little toy pig. Yeah. Yeah. I love that. What else are we missing? I think we covered a lot of, like, the browser-based product history, but. What do you wish people asked you? Yeah.Paul [00:50:29]: I wish people asked me more about, like, what will the future of software look like? Because I think that's really where I've spent a lot of time about why do browser-based. Like, for me, starting a company is like a means of last resort. Like, you shouldn't start a company unless you absolutely have to. And I remain convinced that the future of software is software that you're going to click a button and it's going to do stuff on your behalf. Right now, software. You click a button and it maybe, like, calls it back an API and, like, computes some numbers. It, like, modifies some text, whatever. But the future of software is software using software. So, I may log into my accounting website for my business, click a button, and it's going to go load up my Gmail, search my emails, find the thing, upload the receipt, and then comment it for me. Right? And it may use it using APIs, maybe a browser. I don't know. I think it's a little bit of both. But that's completely different from how we've built software so far. And that's. I think that future of software has different infrastructure requirements. It's going to require different UIs. It's going to require different pieces of infrastructure. I think the browser infrastructure is one piece that fits into that, along with all the other categories you mentioned. So, I think that it's going to require developers to think differently about how they've built software for, you know

In der neuen Folge Mic Rider Deep Talk spreche ich mit Kurt Paulsen – Universitätsprofessor für Film, Medienexperte und Berater bei Spawning AI. KI und Urheberrecht – zwei Themen, die oft im Konflikt stehen. Doch muss das so sein? Wir reden über das "Do Not Train"-Register, das Künstlern mehr Kontrolle über ihre Werke gibt, und darüber, wie KI-Training fairer gestaltet werden kann. Zum Beispiel mit einem foundation model, das transparent und rechtlich einwandfrei mit seinen Trainingsdaten umgeht. Spawning.ai trainiert gerade ein solches Bildgenerierungsprogramm. Und was hat es eigentlich mit der Website “have I been trained” auf sich? Kurt teilt seine Sicht auf die Zukunft von KI: Wohin führt die Entwicklung? Welche Rolle spielt das Urheberrecht? Und welche Verantwortung tragen Entwickler und Plattformen? Nachrichten an: deeptalk@mic-rider.com Website: https://www.mic-rider.com/ Host und Redaktion: Patrick Messe (https://www.patrickmesse.at/) Zu Gast: Kurt Paulsen (thekurtpaulsen.com) Spawning AI: https://spawning.ai/ Have I been trained: https://haveibeentrained.com/ Bild: Charly Glawischnig (https://www.charlyglawischnig.com/) Ton: Lukas Wurm (https://lukaswurm.com/)

 Did you know Chegg's stock once traded above $113 before AI disrupted its business? The online education company is now suing Google, claiming its AI-powered search results scrape content, reducing traffic to original sources and threatening its survival. Investors reacted sharply, causing Chegg's stock to drop by one-third, while the company warns that unchecked AI could erode the internet's reliability and diversity. 

This week on the show, we dive right into 'Erik's Eating Again.' Erik shares details about his trip to Casa Bonita in Denver, Colorado, a Mexican restaurant with one-of-a-kind features like cliff divers, puppet shows, and more, recently renovated by South Park creators Trey Parker and Matt Stone. The discussion also covers Universal Orlando's accessible layout, Erik's favorite coaster the VelociCoaster, and the surprise speakeasy found during CityWalk's Mardi Gras celebration. We preview our upcoming Disneyland visit, mention local Disney-related spots in LA, and give updates on other network podcasts, including Buena Vista Boys, Scraping the Vault, The Supreme Resort, Bantha Milk Podcast, and PuniPod. We wrap the show with some Disney News! ---------------- Support the show! Come watch us on Twitch! Subscribe to us on YouTube Join everyone over on our Patreon page Visit us on Etsy for the coolest Disney-inspired shirts Come check out the Discord group! Learn more about your ad choices. Visit megaphone.fm/adchoices

¿Qué sucede cuando una empresa recaba datos personales de una web abierta o protegida mediante técnicas de “data scraping”? Hemos tratado varios casos recientes (KASPR-CNIL, Equifax-AEPD, Experian-ICO) con Jorge Cabet, pero no sin antes darnos un paseo entretenido por la historia del web scraping y el solapamiento de disciplinas que esta práctica invoca a ambos lados del charco. Jorge Cabet es Director en el departamento de Corporate e Innovación del despacho Augusta Abogados. Nuestro invitado ha ejercido en distintos despachos internacionales y ha trabajado también para el ente público. Colabora con distintos medios y publica artículos doctrinales además de ejercer la docencia en la Universidad. Referencias: Jorge Cabet (Cinco Días): el caso KASPR: empresas que usan tus datos, una realidad peligrosa de internet Jorge Cabet en LinkedIn Resolución de la AEPD contra EQUIFAX IBÉRICA (1 millón de euros) (EN) El caso de OpenAI reabre el debate sobre web scraping (Cyberscoop) (EN) hiQ Labs vs. LinkedIn (EN) Data scraping: KASPR fined €240,000 (CNIL) (EN) Polish Supervisory Authority issues GDPR fine for data scraping without informing individuals (Inside Privacy) (EN) Tribunal rules on Experian appeal against ICO action (ICO).

Nat and Marc are back in the pod room. Nat's getting nervous about the Eastenders live ep, Marc's getting FOMO, and as always, plenty of cheeky innuendo. Enjoy!! x Please subscribe, follow, and leave a review. xxx You can find us in all places here; https://podfollow.com/lifewithnat/view INSTA: @natcass1 We're also on Facebook now too: https://www.facebook.com/lifewithnatpod A 'Keep It Light Media' Production Sales, advertising, and general enquiries: hello@keepitlightmedia.com SHOW INFO: Life with Nat - it's me! Natalie Cassidy and I'll be chatting away to family, friends and most importantly YOU. I want to pick people's brains on the subjects that I care about- whether that's where all the odd socks go, weight and food or kids on phones. Each week I will be letting you into my life as i chat about my week, share my thoughts on the mundane happenings as well as the serious. I have grown up in the public eye and have never changed because of it. Life with Nat is the podcast for proper people. Come join the community. ♥️ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Hacemos un repaso de las extensiones de chrome que más usamos en nuestro trabajo con Media Buyers0:00 Intro0:08 Miscelánea2:24 Nuestra Semana11:58 PPCCast+14:40 Noticias de la Semana31:32 Tema Principal59:47 Recomendaciones1:03:27 Canción PPCCastURL Episodio: https://ppccast.com/podcast/229-extensiones-para-media-buyersPPCFest: ppcfest.comPPCCast+: ppccast.com/plusPatrocinadoresRaiola Networks: ppccast.com/raiolaData Feed Watch: ppccast.com/datafeedConvertiam: ppccast.com/convertiam

20,000 customers worldwide are already using Bright Data's data collection platform with custom scraper APIs, ready-made datasets, and a global proxy network. The question is, why aren't you? Get started at https://bit.ly/3Dd7Ti2 Bright Data City: New York Address: 500 7th Ave, 9th Floor Office 9A1234 Website: https://bit.ly/3dd7ti2

In this episode, the discussion focuses on the laws of cleaning clothes on Shabbat. It addresses the use of household versus professional clothes presses, with specific rules about loosening or removing clothes from them. It also covers the prohibition of softening certain materials, like scarves or linen, which could be viewed as "cleaning" rather than just softening. The episode touches on the issue of scraping mud off shoes, with guidance on whether it's permitted to do so on different surfaces like walls or beams.

Hoy entrevisto a David Suárez ( https://apralize.com/ ), un joven sevillano de 22 años que transformó un proceso empresarial que tardaba días en una solución de 5 segundos, marcando el inicio de su exitosa carrera en automatización. David comparte cómo el aprendizaje práctico y la resolución de problemas reales le permitieron construir una carrera exitosa en tecnología. Su historia demuestra que la pasión y la determinación pueden superar las rutas tradicionales de educación. En el episodio de hoy David revelará: 1: Cómo abandonó la carrera de Ingeniería Informática para aprender de forma autodidacta 2: Cómo desarrolló expertise en web scraping y automatización de procesos 3: Cómo creó apralize.com/, su propia consultoría de automatización con IA 4: Cómo trabaja con empresas desde PyMEs hasta corporaciones como BMW 5: Cómo utiliza IA avanzada para optimizar soluciones de programación 6: Trading automatizado con IA 7: Cómo contactar con empresas para ofrecer servicios de Web Scraping 8: Cuánto dinero gana 9: Cómo realizar automatizaciones por WhatsApp para hacer seguimiento de clientes 10: Cómo automatizar emails con IA para llegar a potenciales clientes 11: Cómo crear contenido en Redes Sociales en automático programado con Python 12: El futuro de la IA LAS ENTREVISTAS QUE MÁS GUSTAN:

Show notes: (1:21) Dr. Whitman's background and how she transitioned from traditional to functional dentistry (5:00) The biggest mistakes people make with their oral health (10:38) Why mouth breathing is damaging & how to fix it (16:01) The hidden dangers of acidic drinks like diet soda (18:17) What is hydroxyapatite & why it's a game-changer for oral health (28:29) The problem with most toothpaste ingredients (32:13) Tongue scraping, flossing, and, water picking (37:35) How laser dentistry is transforming treatments (40:29) The benefits of red light therapy for oral health (46:40) How to reach Dr. Whitman to find the right holistic or functional dentist (48:51) Oral probiotics: a must-have for a healthy mouth (51:07) Outro   Who is Dr. Staci Whitman?   Doctor Staci Whitman is a Functional Kids' Dentist in North Portland, Oregon. She is the founder of NoPo Kids Dentistry where she takes a whole-body, holistic, and functional approach with her patients. Her dentistry/practice is grounded by science and powered by love.   Doctor Staci attended Tufts University School of Dental Medicine and worked as a general dentist for 2 years before earning a certificate in pediatric dentistry from Oregon Health & Science University (OHSU).    She has always been passionate about children's sleep and airway health, focusing her research in residency on how to improve airway assessments and diagnostic tools in the pediatric population.   In 2019, she founded NoPo Kids Dentistry with a mission to practice a whole-body approach to dentistry. She became a Diplomate of the American Board of Pediatric Dentistry in 2012 and is a Board-Certified Pediatric Dentist and a Fellow of the American Academy of Pediatric Dentistry.   Doctor Staci is an Internationally Certified Health and Wellness Coach from the Institute of Integrative Nutrition and is currently attending the American College of Integrative Dentistry and Medicine and the Institute of Functional Medicine, with expected certification dates in 2022. She dreams of a world without cavities and believes in motivating families to join her as a team, keeping their children healthy and thriving with small, manageable daily changes. Connect with Dr. Whitman: Website: https://doctorstaci.com/ IG: https://www.instagram.com/doctor_staci/   Check out her oral health products: https://fygg.com/ (Use code PEAK15 for 15% off!) Links and Resources: Peak Performance Life Peak Performance on Facebook Peak Performance on Instagram  

Nat and Marc catch up on desserts (of course), where people are listening in the world and Nat leaving Eastenders. Enjoy! X Please subscribe, follow, and leave a review. xxx You can find us in all places here; https://podfollow.com/lifewithnat/view INSTA: @natcass1 We're also on Facebook now too: https://www.facebook.com/lifewithnatpod A 'Keep It Light Media' Production Sales, advertising, and general enquiries: hello@keepitlightmedia.com SHOW INFO: Life with Nat - it's me! Natalie Cassidy and I'll be chatting away to family, friends and most importantly YOU. I want to pick people's brains on the subjects that I care about- whether that's where all the odd socks go, weight and food or kids on phones. Each week I will be letting you into my life as i chat about my week, share my thoughts on the mundane happenings as well as the serious. I have grown up in the public eye and have never changed because of it. Life with Nat is the podcast for proper people. Come join the community. ♥️ Learn more about your ad choices. Visit podcastchoices.com/adchoices

A new father learns the hard way that you don't put your kids on Tik Tok. People continue to attack each other on the 805 Beer Textline. and NPR is hogging all the real radio people's salaries with all of it's tax subsidies.

Support this podcast at — https://redcircle.com/hypnosis-and-relaxation-sound-therapy9715/donationsAdvertising Inquiries: https://redcircle.com/brandsPrivacy & Opt-Out: https://redcircle.com/privacy

All Hail Unicron: Episode 83:  INTRODUCTION   Anybody Get Anything? Movie/Show News (and video games!) Reactive has been deactivated https://news.tfw2005.com/2025/01/08/transformers-reactivate-officially-cancelled-529324 Third party: Iron Warrior TF Prime Bumblebee https://news.tfw2005.com/2025/01/02/iron-warrior-iw-08-transformers-prime-bumblebee-action-figure-color-prototype-529121 More de-tails on De-Fence's take on Legends scale Fall of Cybertron Grimlock https://news.tfw2005.com/2025/01/12/de-fence-df-01-muscle-rex-legends-scale-fall-of-cybertron-grimlock-color-prototype-529455 Official: YoloPark reveals https://news.tfw2005.com/2025/01/06/yolopark-amk-mini-transformers-g1-bayverse-color-prototypes-and-reveals-529221 What'd he say his name was? Megabull! https://news.tfw2005.com/2025/01/06/cyberworld-megabull-possible-first-look-529238 Finally, another MP Beast Wars figure! https://news.tfw2005.com/2025/01/08/mpg-15-masterpiece-rattle-rattrap-possible-first-look-529298 Predaking reveal! https://news.tfw2005.com/2025/01/08/adamas-machina-amt-02-predaking-revealed-529335 An official crossover that harkens back to an unofficial crossover of sorts from G1... https://news.tfw2005.com/2025/01/09/takara-tomy-synergenex-series-macross-7-x-transformers-teaser-image-529366 Hasbro Pulse Asia shuts doors https://news.tfw2005.com/2025/01/09/hasbro-pulse-asia-shutting-down-529371 Age of the Primes Wreck n' Doom 2-pack reveal https://news.tfw2005.com/2025/01/13/transformers-age-of-the-primes-wreck-n-doom-collection-topspin-vs-spinister-2-pack-revealed-529503 Handful of Studio Series reveals https://news.tfw2005.com/2025/01/13/new-studio-series-official-reveals-leader-aoe-optimus-deluxe-aoe-que-more-529510 What's yellow and black and fits on your back? Dort-mund col-lab https://news.tfw2005.com/2025/01/02/transformers-x-borussia-dortmund-collaboration-official-merchandise-529099 questions? Discussion: Email your questions to: Hailunicroncast@gmail.com    Special Shoutouts: Dustmightz for providing the beats for the theme song! Check the Realm of Collectors on Facebook! https://www.facebook.com/groups/realmofcollectors   Everyone who followed us from Shattered Cast Uncut, we are grateful to each and everyone of you for joining us on this journey!   Hosts: T2RX6 http://www.youtube.com/user/T2rx6 Rich “Preordered” H. Oscar Alonso https://www.youtube.com/user/oscarnjboy Robert Duyjuy-sabado-gigante

Guest Experience Coordinator Eric Perez emphasizes the importance of going beyond surface-level efforts in family and spiritual life, encouraging individuals to embrace their role as spiritual leaders by investing deeply in prayer, study, and relationships.

Get automated scraping for large datasets powered by the world's best proxy network. Revolutionize your research with Bright Data! More details at https://bit.ly/3Dd7Ti2 Bright Data City: New York Address: 500 7th Ave, 9th Floor Office 9A1234 Website: https://bit.ly/3dd7ti2

Jason and Laura talk about his "survival" of brunch this weekend. Then on the DeRush-Hour: you're scraping your windshield wrong! (Photo by Chip Somodevilla/Getty Images)

Nat and Marc talk about thermostats and teenage freedom. Thank you so much for your input and we hope you enjoy! X Please subscribe, follow, and leave a review. xxx You can find us in all places here; https://podfollow.com/lifewithnat/view INSTA: @natcass1 We're also on Facebook now too: https://www.facebook.com/lifewithnatpod A 'Keep It Light Media' Production Sales, advertising, and general enquiries: hello@keepitlightmedia.com SHOW INFO: Life with Nat - it's me! Natalie Cassidy and I'll be chatting away to family, friends and most importantly YOU. I want to pick people's brains on the subjects that I care about- whether that's where all the odd socks go, weight and food or kids on phones. Each week I will be letting you into my life as i chat about my week, share my thoughts on the mundane happenings as well as the serious. I have grown up in the public eye and have never changed because of it. Life with Nat is the podcast for proper people. Come join the community. ♥️ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Anna, Dan, and Evan talk about how Dan is already looking to book another vacation before they go on the one currently booked. Anna has more car troubles. Evan has to deal with sick people at work. And they wrap everything up with a ranking of Sucker Punch by Sigrid, Thanks for tuning in to this week's episode! Follow us on social media for the latest updates and additional content. If you enjoyed this episode, please consider writing a review and subscribing. We would greatly appreciate it. Follow Us: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Twitter⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Website

Work with Bright Data - a renowned proxy server and data solutions provider - and experience the next generation of digital marketing tools with its LinkedIn profile web scraping API services. More details at https://get.brightdata.com/skyag-web-scraper-linkedin-profiles Bright Data City: New York Address: 500 7th Ave, 9th Floor Office 9A1234 Website: https://bit.ly/3dd7ti2

I'm back with another Q&A episode! This week, I answer your questions about scraping commercial real estate for leads, selling custom spreadsheets on Etsy, and how to close more deals over the phone. Plus, I share my thoughts on the best type of side hustle to start, whether you should choose e-commerce or a service business, and discuss my framework for starting, holding, and selling businesses. I'll also tackle the question of how to stay motivated when you're already well-off, and offer advice on bookkeeping for all of your new businesses.Timestamps below. Enjoy!---Watch this on YouTube instead here: tkopod.co/p-ytAsk me a question on or off the show here: http://tkopod.co/p-askLearn more about me: http://tkopod.co/p-cjkLearn about my company: http://tkopod.co/p-cofFollow me on Twitter here: http://tkopod.co/p-xFree weekly business ideas newsletter: http://tkopod.co/p-nlShare this podcast: http://tkopod.co/p-allScrape small business data: http://tkopod.co/p-os---00:00 Introduction to Business Ideas and Strategies01:08 Scraping Commercial Real Estate for Grants03:59 Selling Custom Spreadsheets on Etsy11:06 Closing Sales Over the Phone13:54 Choosing Between E-commerce and Service Businesses15:48 Exploring Low-Cost Mattress Stores19:04 Finding Motivation for New Business Ventures22:50 Business Philosophy: Starting, Holding, and Selling28:02 Bookkeeping and Accounting Essentials

Copyright law and artificial intelligence are on a collision course, with major implications for the future of AI development, research, and innovation. In this first episode of The Dynamist's four-part series exploring AI and copyright, we're joined by Professor Pamela Samuelson of Berkeley Law, a pioneering scholar in intellectual property law and a leading voice on copyright in the digital age. FAI Senior Fellow Tim Hwang guest hosts. The conversation covers the wave of recent lawsuits against AI companies, including The New York Times suit against OpenAI and litigation facing Anthropic, NVIDIA, Microsoft, and others. These cases center on two key issues: the legality of using copyrighted materials as training data and the potential for AI models to reproduce copyrighted content. Professor Samuelson breaks down the complex legal landscape, explaining how different types of media (books, music, software) might fare differently under copyright law due to industry structure and existing precedent.Drawing on historical parallels from photocopying to the Betamax case, Professor Samuelson provides crucial context for understanding today's AI copyright battles. She discusses how courts have historically balanced innovation with copyright protection, and what that might mean for AI's future. With several major decisions expected in the coming months, including potential summary judgments, these cases could reshape the AI landscape - particularly for startups and research institutions that lack the resources of major tech companies.

Over the weekend, we had threats of winter weather. With the potential of freezing rain, my wife and I put our wipers up. It's a trick I learned years ago. Pulling them off the windshield meant we didn't have to worry about the wipers sticking to it. Fortunately, there was no ice storm, so it was business as usual. Scraping your windshield is a hassle, especially if you're running late in the morning. But it's always better to be safe than sorry. However, some experts say pulling your blades off the windshield can cause other issues. This new data definitely gives me something to ponder... Click Here To Subscribe Apple PodcastsSpotifyAmazon MusicGoogle PodcastsTuneIniHeartRadioPandoraDeezerBlubrryBullhornCastBoxCastrofyyd.deGaanaiVooxListen NotesmyTuner RadioOvercastOwlTailPlayer.fmPocketCastsPodbayPodbeanPodcast AddictPodcast IndexPodcast RepublicPodchaserPodfanPodtailRadio PublicRadio.comReason.fmRSSRadioVurblWe.foYandex jQuery(document).ready(function($) { 'use strict'; $('#podcast-subscribe-button-13292 .podcast-subscribe-button.modal-677ca15dc8d09').on("click", function() { $("#secondline-psb-subs-modal.modal-677ca15dc8d09.modal.secondline-modal-677ca15dc8d09").modal({ fadeDuration: 250, closeText: '', }); return false; }); });

Episode Description by ChatGP-T (a.k.a. Mr. T) “Hey, you! Yeah, YOU, fool! Stop scrolling and start listening, ‘cause the Supreme Podcasting Champs are back with an episode that's stronger than a chain of gold and sharper than Mr. T's barber!” This week, the Scraping the Vault crew dives headfirst into Be Somebody… or Be Somebody's Fool!—the iconic 1984 motivational masterpiece from none other than me, Mr. T! And let me tell ya, these fools learned some real lessons this time. Here's what went down: They learned how to spell Mother (hint: it's all about love and respect, fool!). They discovered that anger ain't bad if you can “use it, don't lose it.” (Just like my patience with them—barely hangin' on!) And the best way to eat potato salad? Straight off the fingers of Mr. T himself! Yeah, you heard that right. It's delicious, nutritious, and a privilege, fool! But that's not all. The hosts ask the big questions: Is Mr. T's cello playing the greatest metaphor for perseverance ever put on VHS? (Spoiler: Yes, it is!) Can breakdancing truly heal a nation? (Only if you're spinning with the heart of a champion!) Why would Calvin Klein and Gloria Vanderbilt want your name on their jeans? (They wouldn't, fool, so don't wear theirs!) So, grab a bowl of respect, sprinkle on some self-worth, and tune in as these podcasting maniacs unravel my wisdom one absurd segment at a time. But don't get it twisted: if you ain't laughing AND learning, then you better rewind, fool, because the only thing worse than missing this episode is disrespecting your mother. “Scraping the Vault—where fools become champions, one ridiculous episode at a time.” Now quit wasting time! Download it, stream it, or I pity you for missin' out! Peace, respect, and potato salad. Link to SDS....You https://youtu.be/ajGb9B6vCDE?si=5Y4es-WNt_ZKqzne Link to Mr T https://www.youtube.com/watch?v=0Y1abMt1UGw Learn more about your ad choices. Visit megaphone.fm/adchoices

Please subscribe, follow, and leave a review. xxx You can find us in all places here; https://podfollow.com/lifewithnat/view INSTA: @natcass1 We're also on Facebook now too: https://www.facebook.com/lifewithnatpod A 'Keep It Light Media' Production Sales, advertising, and general enquiries: hello@keepitlightmedia.com SHOW INFO: Life with Nat - it's me! Natalie Cassidy and I'll be chatting away to family, friends and most importantly YOU. I want to pick people's brains on the subjects that I care about- whether that's where all the odd socks go, weight and food or kids on phones. Each week I will be letting you into my life as i chat about my week, share my thoughts on the mundane happenings as well as the serious. I have grown up in the public eye and have never changed because of it. Life with Nat is the podcast for proper people. Come join the community. ♥️ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Merry X-Mas! This week we take some very keen advice from some of the toughest men on the planet, we find out what happens when you decorate a douche boat, we see a door dash driver spit in a child's drink, and we watch Santa Clause get arrested. This a holly jolly episode packed with hilarious presents. As always don't forget to follow, like, subscribe, and tell some strangers about us. TikTok: @THEOPENMIKEPODCAST Facebook: FACEBOOK.COM/THEOPENMIKEPODCAST Instagram: @THEOPENMIKEPODCAST Mikey B. Instagram: @MIKEYBTHECOMIC Mikey B. TikTok: @MIKEYBTHECOMIC --- Support this podcast: https://podcasters.spotify.com/pod/show/the-open-mike-podcast/support

Nat and Marc are joined by their eldest daughter Eliza and Marc rates some mince pies and Irish creams. Christmas chat and fun! Enjoy! X Please subscribe, follow, and leave a review. xxx You can find us in all places here; https://podfollow.com/lifewithnat/view INSTA: @natcass1 We're also on Facebook now too: https://www.facebook.com/lifewithnatpod A 'Keep It Light Media' Production Sales, advertising, and general enquiries: hello@keepitlightmedia.com SHOW INFO: Life with Nat - it's me! Natalie Cassidy and I'll be chatting away to family, friends and most importantly YOU. I want to pick people's brains on the subjects that I care about- whether that's where all the odd socks go, weight and food or kids on phones. Each week I will be letting you into my life as i chat about my week, share my thoughts on the mundane happenings as well as the serious. I have grown up in the public eye and have never changed because of it. Life with Nat is the podcast for proper people. Come join the community. ♥️ Learn more about your ad choices. Visit podcastchoices.com/adchoices

In its first leading judgment (decision of November 18, 2024, docket no.: VI ZR 10/24), the German Federal Court of Justice (BGH) dealt with claims for non-material damages pursuant to Art. 82 GDPR following a scraping incident. According to the BGH, a proven loss of control or well-founded fear of misuse of the scraped data by third parties is sufficient to establish non-material damage. The BGH therefore bases its interpretation of the concept of damages on the case law of the CJEU, but does not provide a clear definition and leaves many questions unanswered. Our German data litigation lawyers, Andy Splittgerber, Hannah von Wickede and Johannes Berchtold, discuss this judgment and offer insights for organizations and platforms on what to expect in the future. ----more---- Transcript: Intro: Hello, and welcome to Tech Law Talks, a podcast brought to you by Reed Smith's Emerging Technologies Group. In each episode of this podcast, we will discuss cutting-edge issues on technology, data, and the law. We will provide practical observations on a wide variety of technology and data topics to give you quick and actionable tips to address the issues you are dealing with every day.  Andy: Hello, everyone, and welcome to today's episode of our Reed Smith Tech Law Talks podcast. In today's episode, we'll discuss the recent decision of the German Federal Court of Justice, the FCJ, of November 18, 2024, on compensation payments following a data breach or data scraping. My name is Andy Splittgerber. I'm partner at Reed Smith's Munich office in the Emerging Technologies Department. And I'm here today with Hannah von Wickede from our Frankfurt office. Hannah is also a specialist in data protection and data litigation. And Johannes Berchtold, also from Reed Smith in the Munich office, also from the emerging technologies team and tech litigator. Thanks for taking the time and diving a bit into this breathtaking case law. Just to catch everyone up and bring everyone on the same speed, it was a case decided by the German highest civil court, in an action brought by a user of a social platform who wanted damages after his personal data was scraped by a hacker from that social media network. And that was done through using the telephone number or trying out any kind of numbers through a technical fault probably, and this find a friend function. And through this way, the hackers could download a couple of million data sets from users of that platform, which then could be found in the dark web. And the user then started an action before the civil court claiming for damages. And this case was then referred to the highest court in Germany because of the legal difficulties. Hannah, do you want to briefly summarize the main legal findings and outcomes of this decision?  Hannah: Yes, Andy. So, the FCJ made three important statements, basically. First of all, the FCJ provided its own definition of what a non-material damage under Article 82 GDPR is. They are saying that mere loss of control can constitute a non-material damage under Article 82 GDPR. And if such a loss of the plaintiffs is not verifiable, that also justified fear of personal data being misused can constitute a non-material damage under GDPR. So both is pretty much in line with what the ECJ already has said about non-material damages in the past. And besides that, the FCJ makes also a statement regarding the amount of compensation for non-material damages following from scraping incident. And this is quite interesting because according to the FCJ, the amount of the claim for damages in such cases is around 100 euros. That is not much money. However, FCJ also says both loss of control and reasonable apprehension, also including the negative consequences, must first be proven by the plaintiff.  Andy: So we have an immaterial damage that's important for everyone to know. And the legal basis for the damage claim is Article 82 of the General Data Protection Regulation. So it's not German law, it's European law. And as you'd mentioned, Hannah, there was some ECJ case law in the past on similar cases. Johannes, can you give us a brief summary on what these rulings were about? And on your view, does the FCJ bring new aspects to these cases? Or is it very much in line with the European Court of Justice that already?  Johannes: Yes, the FCJ has quoted ECJ quite broadly here. So there was a little clarification in this regard. So far, it's been unclear whether the loss of control itself constitutes the damage or whether the loss of control is a mere negative consequence that may constitute non-material damage. So now the Federal Court of Justice ruled that the mere loss of control constitutes the direct damage. So there's no need for any particular fear or anxiety to be present for a claim to exist.  Andy: Okay, so it's not. So we read a bit in the press after the decision. Yes, it's very new and interesting judgment, but it's not revolutionary. It stays very close to what the European Court of Justice said already. The loss of control, I still struggle with. I mean, even if it's an immaterial damage, it's a bit difficult to grasp. And I would have hoped FCJ provides some more clarity or guidance on what they mean, because this is the central aspect, the loss of control. Johannes, you have some more details? What does the court say or how can we interpret that?  Johannes: Yeah, Andy, I totally agree. So in the future, discussion will most likely tend to focus on what actually constitutes a loss of control. So the FCJ does not provide any guidance here. However, it can already be said the plaintiff must have had the control over his data to actually lose it. So whether this is the case is particularly questionable if the actual scrape data was public, like in a lot of cases where we have in Germany right here, and or if the data was already included in other leaks, or the plaintiff published the data on another platform, maybe on his website or another social network where the data was freely accessible. So in the end, it will probably depend on the individual case if there was actually a loss of control or not. And we'll just have to wait on more judgments in Germany or in Europe to define loss of control in more detail.  Andy: Yeah, I think that's also a very important aspect of this case that was decided here, that the major cornerstones of the claim were established, they were proven. So it was undisputed that the claimant was a user of the network. It was undisputed that the scraping took place. It was undisputed that the user's data was affected part of the scraping. And then also the user's data was found in the dark web. So we have, in this case, when I say undistributed, it means that the parties did not dispute about it and the court could base their legal reasoning on these facts. In a lot of cases that we see in practice, these cornerstones are not established. They're very often disputed. Often you perhaps you don't even know that the claimant is user of that network. There's always dispute or often dispute around whether or not a scraping or a data breach took place or not. It's also not always the case that data is found in the dark web. I think this, even if the finding in the dark web, for example, is not like a written criteria of the loss of control. I think it definitely is an aspect for the courts to say, yes, there was loss of control because we see that the data was uncontrolled in the dark web. So, and that's a point, I don't know if any of you have views on this, also from the technical side. I mean, how easy and how often do we see that, you know, there is like a tag that it says, okay, the data in the dark web is from this social platform? Often, users are affected by multiple data breaches or scrapings, and then it's not possible to make this causal link between one specific scraping or data breach and then data being found somewhere in the web. Do you think, Hannah or Johannes, that this could be an important aspect in the future when courts determine the loss of control, that they also look into, you know, was there actually, you know, a loss of control?  Hannah: I would say yes, because it was already mentioned that the plaintiffs must first prove that there is a causal damage. And a lot of the plaintiffs are using various databases that list such alleged breaches, data breaches, and the plaintiffs always claim that this would indicate such a causal link. And of course, this is now a decisive point the courts have to handle, as it is a requirement. Before you get to the damage and before you can decide if there was a damage, if there was a loss of control, you have to prove if the plaintiff even was affected. And yeah, that's a challenge and not easy in practice because there's also a lot of case law already about these databases or on those databases that there might not be sufficient proof for the plaintiffs being affected by alleged data breaches or leaks.  Andy: All right. So let's see what's happening also in other countries. I mean, the Article 82, as I said in the beginning, is a European piece of law. So other countries in Europe will have to deal with the same topics. We cannot come up with our German requirements or interpretation of immaterial damages that are rather narrow, I would say. So Hannah, any other indications you see from the European angle that we need to have in mind?  Hannah: Yes, you're right. And yet first it is important that this concept of immaterial damage is EU law, is in accordance with EU law, as this is GDPR. And as Johannes said, the ECJ has always interpreted this damage very broadly. And does also not consider a threshold to be necessary. And I agree with you that it is difficult to set such low requirements for the concept of damage and at the same time not demand materiality or a threshold. And in my opinion, the Federal Court of Justice should perhaps have made a submission here to the ECJ after all because it is not clear what loss of control is. And then without a material threshold, this contributes a lot to legal insecurity for a lot of companies.  Andy: Yeah. Thank you very much, Hannah. So yes, the first takeaway for us definitely is loss of control. That's a major aspect of the decision. Other aspects, other interesting sentences or thoughts we see in the FCJ decision. And one aspect I see or I saw is right at the beginning where the FCJ merges together two events. The scraping and then a noncompliance with data access requests. And that was based in that case on contract, but similar on Article 15, GDPR. So those three events are kind of like merged together as one event, which in my view doesn't make so much sense because they're separated from the event, from the dates, from the actions or non-actions, and also then from the damages from a non-compliance with an Article 15. I think it's much more difficult to argue with a damage loss of control than with a scraping or a data breach. That that's not a major aspect of the decision but I think it was an interesting finding. Any other aspects, Hannah or Johannes, that you saw in the decision worth mentioning here for our audience?  Johannes: Yeah so I think discussion in Germany was really broadly so i think just just maybe two points have been neglected in the discussion so far. First, towards the ending of the reasoning, the court stated that data controllers are not obliged to provide information about unknown recipients. For example, like in scraping cases, controllers often do not know who the scrapers are. So there's no obligation for them to provide any names of scrapers they don't know. That clarification is really helpful in possible litigation. And on the other hand, it's somewhat lost in the discussion that the damages of the 100 euros only come into consideration if the phone number, the user ID, the first name, the last name, the gender, and the workplace are actually affected. So accordingly, if less data, maybe just an email address or a name, or less sensitive data was scraped, the claim for damages can or must even be significantly lower.  Andy: All right. Thanks, Johannes. That's very interesting. So, not only the law of control aspect, but also other aspects in this decision that's worth mentioning and reading if you have the time. Now looking a bit into the future, what's happening next, Johannes? What are your thoughts? I mean, you're involved in some similar litigation as well, as so is Hannah, what do you expect, What's happening to those litigation cases in the future? Any changes? Will we still have law firms suing after social platforms or suing for consumers after social platforms? Or do we expect any changes in that?  Johannes: Yeah, Andy, it's really interesting. In this mass GDPR litigation, you always have to consider the business side, not always just the legal side. So I think the ruling will likely put an end to the mass GDPR litigation as we know it in the past. Because so far, the plaintiffs have mostly appeared just with a legal expenses insurer. So the damages were up to like 5,000 euros and other claims have been asserted. So the value in dispute could be pushed to the edge. So it was like maybe around 20,000 euros in the end. But now it's clear that the potential damages in such scraping structures are more likely to be in the double-digit numbers, like, for example, 100 euros or even less. So as a result, the legal expenses insurers will no longer fund their claims for 5,000 euros. But at the same time, the vast majority of legal expenses insurers have agreed to a deductible of more than 100 euros. So the potential outcome and the risk of litigation are therefore disproportionate. And as a result, the plaintiffs will probably refrain from filing such lawsuits in the future.  Andy: All right. So good news for all insurers in the audience or better watch out for requests for coverage of litigation and see if not the values in this cube are much too high. So we will probably see less of insurance coverage cases, but still, definitely, we expect the same amount or perhaps even more litigation because the number as such, even if it's only 100 euros, seems certainly attractive for users as a so-called low-hanging fruit. And Hannah, before we close our podcast today, again, looking into the future, what is your recommendation or your takeaways to platforms, internet sites, basically everyone, any organization handling data can be affected by data scraping or a data breach. So what is your recommendation or first thoughts? How can those organizations get ready or ideally even avoid such litigation?  Hannah: So at first, Andy, it is very important to clarify that the FCJ judgment is ruled on a specific case in which non-public data was made available to the public as a result of a proven breach of data protection. And that is not the case in general. So you should avoid simply apply this decision to every other case like a template because if other requirements following from the GDPR are missing, the claims will still be unsuccessful. And second, of course, platforms companies have to consider what they publish about their security vulnerabilities and take the best possible precautions to ensure that data is not published on the dark web. And if necessary, companies can transfer the risk of publication to the user simply by adjusting their general terms and conditions.  Andy: Thanks, Hannah. These are interesting aspects and I see a little bit of conflict between the breach notification obligations under Article 33, 34, and then the direction this caseload goes. That will also be very interesting to see. Thank you very much, Hannah and Johannes, for your contribution. That was a really interesting, great discussion. And thank you very much to our audience for listening in. This was today's episode of our EU Reed Smith Tech Law Talks podcast. We thank you very much for listening. Please leave feedback and comments in the comments fields or send us an email. We hope to welcome you soon to our next episode. Have a nice day. Thank you very much. Bye bye.  Outro: Tech Law Talks is a Reed Smith production. Our producers are Ali McCardell and Shannon Ryan. For more information about Reed Smith's emerging technologies practice, please email techlawtalks@reedsmith.com. You can find our podcast on Spotify, Apple Podcasts, Google Podcasts, reedsmith.com, and our social media accounts.  Disclaimer: This podcast is provided for educational purposes. It does not constitute legal advice and is not intended to establish an attorney-client relationship, nor is it intended to suggest or establish standards of care applicable to particular lawyers in any given situation. Prior results do not guarantee a similar outcome. Any views, opinions, or comments made by any external guest speaker are not to be attributed to Reed Smith LLP or its individual lawyers.  All rights reserved.  Transcript is auto-generated.

It's a worrying time when you see Eddie Hearn using the tactics he used to laugh at other promoters for using. But it goes to show how far the pendulum has swung away from Matchroom in the last 3 years. Also....NOBODY ASKED FOR CHISORA V WALLIN!!!!

Scraping fingers down a blackboard, sticking your finger up your nose: there are many things that give people the ick. So, what's your biggest pet peeve?Henry McKean has been out asking the public what annoys them, and joins Seán to discuss.

Nat and Marc are nice and quiet in the home studio. Lots of messages from listeners and a nice way to start the week. Enjoy Please subscribe, follow, and leave a review. xxx You can find us in all places here; https://podfollow.com/lifewithnat/view INSTA: @natcass1 We're also on Facebook now too: https://www.facebook.com/lifewithnatpod A 'Keep It Light Media' Production Sales, advertising, and general enquiries: hello@keepitlightmedia.com SHOW INFO: Life with Nat - it's me! Natalie Cassidy and I'll be chatting away to family, friends and most importantly YOU. I want to pick people's brains on the subjects that I care about- whether that's where all the odd socks go, weight and food or kids on phones. Each week I will be letting you into my life as i chat about my week, share my thoughts on the mundane happenings as well as the serious. I have grown up in the public eye and have never changed because of it. Life with Nat is the podcast for proper people. Come join the community. ♥️ Learn more about your ad choices. Visit podcastchoices.com/adchoices

Nat and Marc pop to their local for a well earnt rest. They have a chat to the locals and friend Brian. Enjoy. X Please subscribe, follow, and leave a review. xxx You can find us in all places here; https://podfollow.com/lifewithnat/view INSTA: @natcass1 We're also on Facebook now too: https://www.facebook.com/lifewithnatpod A 'Keep It Light Media' Production Sales, advertising, and general enquiries: hello@keepitlightmedia.com SHOW INFO: Life with Nat - it's me! Natalie Cassidy and I'll be chatting away to family, friends and most importantly YOU. I want to pick people's brains on the subjects that I care about- whether that's where all the odd socks go, weight and food or kids on phones. Each week I will be letting you into my life as i chat about my week, share my thoughts on the mundane happenings as well as the serious. I have grown up in the public eye and have never changed because of it. Life with Nat is the podcast for proper people. Come join the community. ♥️ Learn more about your ad choices. Visit podcastchoices.com/adchoices

or however the saying goes...as always, follow us on Instagram @tracktalk.pod xoxo

Along with dealing with airport security and disruptive passengers, flight attendants must also battle low wages. Natalie B. Compton, travel reporter for the Washington Post, joins host Krys Boyd to discuss why even though being deemed essential workers, flight attendants struggle with living paycheck-to-paycheck. Plus, we'll hear about the surprising rules that determine how much flight attendants are paid for each flight that don't take into account how much work they actually do. Her article is “‘Barely surviving': Some flight attendants are facing homelessness and hunger.”