Podcasts about ABI

Disturbances from fire and wind to insects and humans play a huge role in forest dynamics through time. Throw in the impacts of climate change, and these dynamics only get more complicated. Understanding how disturbances interact and influence how forests change through time is of great interest to people from all walks of life and that is why people like Dr. Kenneth Anyomi are hard at work studying them. Join us for a deep dive on how disturbances influence forest succession and the lives that depend on it. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Abi and Matt talk about a movie they've already talked about. 

In this episode of TAB Storytellers, Abi and Jen sit down with Emily Bawol, an art teacher, artist, and art therapist at A2 STEAM in Ann Arbor, Michigan. Emily shares how her path through discipline-based art education, art therapy, motherhood, Waldorf, Montessori, Reggio-inspired learning, and project-based education helped her recognize that she was already building a TAB studio before she had the language for it. Together, the trio explores the role of the art teacher in a TAB classroom, especially around idea generation, material exploration, autonomy, and helping young artists trust that their own ideas matter. Emily talks about creating a studio rooted in wonder, where students learn that they are the most important tool in the room, while still building the skills, habits, and confidence they need to bring their ideas to life.For more information about TAB, please visit the TAB website: Teaching for Artistic Behavior. You are also invited to join us on Mighty Networks, an online platform dedicated to everything TAB.Resources:Teaching for Artistic Behavior / TABTAB ResourcesTAB Storytellers PodcastTAB Mighty Networks CommunityEmily Bawol / A2 STEAM Art & DesignA2 STEAM Project-Based LearningAmerican Art Therapy Association: About Art TherapyCASEL: Fundamentals of SELDiscipline-Based Art Education, Getty Virtual LibraryWaldorf Education, Association of Waldorf Schools of North AmericaAmerican Montessori Society: About MontessoriNorth American Reggio Emilia AlliancePBLWorks: What Is Project Based Learning?Melissa Purtee: The Difference Between TAB and Choice and Why It MattersTAB Institute at MassArtJulie Toole, MassArt TAB Institute Faculty ProfileTAB Storytellers S3E5: Meet Julie TooleHarvard Project Zero Thinking RoutinesProject Zero: See, Think, WonderStudio Thinking Books and ResourcesPeter London, No More Secondhand Art, Internet ArchiveSeymour Simmons III: The Value of DrawingArtists Mentioned:Jean-Michel Basquiat, official estate websiteFrida Kahlo Museum / Museo Frida KahloMark Rothko, National Gallery of ArtPablo Picasso, National Gallery of ArtVincent van Gogh, Van Gogh MuseumHere is a link to the lightly edited transcript of this episode. We recognize that there are probably errors and grammatical issues. If anyone with the time or inclination to edit this wants to do so, please email us at ⁠storytellers@teachingforartisticbehaviors.org⁠.

How common or rare are species in an ecosystem? The answer to this might seem simple, but as with everything in nature, it is not. This question can even complicate how we think of habitat conservation and restoration. When we refine and implement scientific tools like species diversity indices, we need to make sure we are applying them correctly. Join me and Dr. Robert Warren as we explore measures of species diversity, the issues with improper use of these tools, and what that can mean in the context of invasive species and restoration. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Only 1% of listeners are clever enough to complete this survey: http://bit.ly/noncensored-surveyThis week, Harriet Langley-Swindon and Producer Martin talk to campaigner and old man Hugh Oldman, about why the government is right to ban under-sixteens from social media; we speak to A Suffragette From 1913 about how she feels about being compared to Palestine Action; and Eshaan Akbar walks us through a Hot & Spicy Takeaway of the Week for as long as the authorities.Thank you to Abi, who signed up to our Patreon this week. She, like all Patreons, will be getting a bonus interview with A Scammer in the middle of the show. Patreons also get every episode early and without adverts, access to the full video of all our interviews, as well as the Patreon-exclusive monthly Time For Questions podcast, where we answer your questions, so get over to Patreon.com/NonCensored and sign up for one or two pounds a week to support the show, and make it possible for us to pay our guests. (If you don't want to subscribe, but do want to give us a one-off amount, all the Patreon-exclusive videos are available for individual sale.)Please follow our social media accounts!Instagram: @noncensoredpodcastTikTok: @noncensoredpodWith thanks to Rosie Holt, Brendan Murphy, Eshaan Akbar, Justin Edwards, Sooz Kempner, John-Luke Roberts, and Ed Morrish.Rosie's sitcom, Crossing The Floor, is available now on BBC Sounds. Her play, Churchill's Urinal, will be on at the Edinburgh Festival Fringe (tickets here), where she will also be doing a new character comedy/stand-up show, The Illegal Aliens Have Landed (tickets here).Brendan is taking a brand new show, Indy, to the Edinburgh Festival Fringe in August. It's a three-man retelling of Indiana Jones, and tickets are available here.Eshaan has started a new, live podcast called The Early Evening Show, every Sunday evening on YouTube, and his latest stand-up special, Fool Moon, is also available on YouTube.Justin is returning to the Edinburgh Festival Fringe for the first time in ages, for just five dates, with his show, Jeremy Lion - My Life!, and tickets are available here.Sooz is also returning to the Edinburgh Festival Fringe, for nine dates, with her show Impostor, and tickets for that are available here.Ed produces produces P.O.V., a scripted sketch show on BBC Sounds which has NonCensored regulars like Davina, Will and Sooz in it. He also produces Sound Heap With John-Luke Roberts, an award-winning improvised sketch show that features many NonCensored regulars like Rosie, Brendan, Will, Sooz and Joz.Show photography is by Karla Gowlett and design is by Chris Barker. Original music is by Paddy Gervers and Rob Sell at Torch and Compass.NonCensored is a Lead Mojo production Hosted on Acast. See acast.com/privacy for more information.

Desde Albacete, España, llega Míriam Abiétar, la talentosa multiinstrumentista, compositora y cantante que da vida a MIR, un proyecto donde la sensibilidad de la formación clásica se encuentra con la fuerza del rock alternativo y el grunge. En esta entrevista exclusiva con Luis Varela para Tiempos de Radio, conversamos sobre el nacimiento de su propuesta artística, su trayectoria musical y la reciente presentación de sus primeros sencillos, “Unspoken” y “I Only Hope To See”, dos canciones que exploran la reconstrucción personal, la liberación emocional y el poder de volver a las propias raíces. Descubre la historia detrás de estas composiciones, sus influencias, el proceso creativo de MIR, la transición del piano clásico a la guitarra eléctrica y los próximos pasos de una artista que transforma experiencias profundas en paisajes sonoros cargados de intensidad, sensibilidad y autenticidad. Dale play y acompáñanos: cuando una canción nace desde lo más profundo, cada acorde tiene una historia que merece ser escuchada. Bandas invitadas: Dead//Betty de Carolina del Norte - USA, Rising Alma de Alemania, Tony Tunait de España, Santino Beltramino de Argentina, Menino Gutto de Brasil y Shirley Valiente de Uruguay. #TiemposDeRadio #MíriamAbiétar #MIR #Albacete #Interview Suscríbete, comparte y comenta, y recuerda, todo en exceso es malo, excepto el rock . Si quieres participar en la siguiente edición, apresúrate y contáctanos en linktr.ee/TiemposdeRadio El único requisito es tu entusiasmo. Tiempos de Radio es un podcast transmitido desde Lima - Perú para Hispanoamérica Radio a través de su señal digital www.hispanoamericaradio.com, Metal Rock Station en Puerto Rico , Radio Dada y Om Radio 97.1 FM en Argentina , Rock Live Radio en Costa Rica , Perfecta Radio en Cincinnati - Ohio, USA y para las principales plataformas de Podcast. Dirección, producción y conducción: Luis Antonio Varela Bohórquez. Copyright de grabación: Todos los derechos de la música utilizada en este podcast pertenecen a los autores, compositores o intérpretes.

Como cada miércoles contamos más sobre nuestra Cultura Canarias, abordamos tradiciones, historia y festividad. En esta oportunidad hablamos con la Federación de Libreas de Tenerife, que este año celebran su VIII Encuentro en el Municipio de El Tanque. Además hablamos con Jonatan Rodríguez de Laboratorio Escénico sobre el trabajo que realizan de Percusión Canaria y en nuestros estudios recibimos al Dr. Angel Nazco, autor del libro "Los Caminos de Francisco de Miranda", prócer venezolano, hijo de canarios; libro que se presenta esta semana en la Casa Venezuela. Nos fuimos a Lanzarote y hablamos con Natalia Delgado, Ruben Valiente y Abián Rodríguez de La Parranda Marinera Los Buches y conversamos sobre este nuevo equipo de trabajo que se incorpora a toda la gestión de esta tradición marinera. Y por otro lado, Eduardo Caballero de la Fundación Francis Naranjo nos invita a la exposición en la Casa de la Cultura de Santa María de Guía; y como cada semana nos vamos a escena con Zálatta Teatro. Todo en La Diez Radio con Joam Walo "poniendo lo canario más d emoda que nunca y apostando por lo nuestro" #programaorigenes #origenes #ladiezradio #joamwalo #capitalradiogc

Today on Beyond the Torch, Todd & Leslie are joined by guest co-host, Scott Ransome, a UK-based Survivor superfan who won a charity eBay bid to co-host and interview a guest and he picked today's guest, Abi-Maria Gomez, the iconic Brazilian-American villain from Survivor: Philippines and Survivor: Cambodia — Second Chances! The conversation covers Abi's unexpected journey to being cast on Survivor (including nearly appearing on Tocantins but being rejected for "not looking Brazilian enough"), her experience playing with a torn ACL throughout Philippines, reflections on being edited as a villain, her views on race and immigrant identity, her complicated relationship with former alliance partner RC, her admiration for Denise Stapley, and candid discussions about Survivor 50 casting disappointments, reality TV opportunities like The Traitors, and fond memories of Survivor legends like Courtney Yates, Amanda Kimmel, and James Clement.Our new Website is live! Check it out at: www.realityaftershow.comJoin our Patreon at RealityPatron.comIf you would like a cameo from Jonny Fairplay order one now! cameo.com/jonnyfairplayCheck us out on Tiktok @fairplaytokBecome a supporter of this podcast: https://www.spreaker.com/podcast/reality-after-show--5448874/support.

Two incredible guests join Nat for this bonus episode.The first is Gabi Field from Great Ormond Street Hospital Charity, speaking today about the importance of the charity's Build it. Beat it. fundraising appeal, which is raising vital funds for a new Children's Cancer Centre at Great Ormond Street Hospital. The second guest is Nat's very dear friend Abi, who some may recognise from episode two of Natalie Cassidy: Caring Together. Abi is also the mother of Joanie's bestie Arianna. Arianna was diagnosed with Neuroblastoma at 5 years old, and Abby has first-hand experience of what it's like to need the medical services GOSH have on offer, knows the pressure of spending lots of time in the building whilst that happens, and knows how important this new building will be to help beat cancer for more children.To support the Build it. Beat it. campaign or find out more about GOSH Charity, visit - www.gosh.orgFollow Arianna's journey www.instagram.com/ariannatherealwonderSolving Kids Cancer charity, which Nat is an ambassador of www.solvingkidscancer.org.ukGet in touch with Nat, buy tickets for upcoming live shows and find the family on Instagram: https://lifewithnatpod.komi.io/ Hosted on Acast. See acast.com/privacy for more information.

Abi Jones joins Ben Sheppard on The RunThrough Podcast to share her journey from the UK to Sydney and the life lessons she learned along the way.What began as a move in search of independence quickly became a crash course in resilience. Abi opens up about arriving in Australia and unexpectedly finding herself homeless on day one, navigating long distance relationships, dealing with loneliness and learning to build a life completely from scratch.Alongside her work as a physiotherapist, Abi talks about growing a social media following by sharing the realities of her life, from moving abroad and adult acne to fitness, rehab and running. She reflects on how running became a huge part of her identity and why stepping outside her comfort zone has changed her outlook on life.Now preparing to move back to the UK, Abi looks back on six transformative months in Australia, the friendships she's made, the challenges she's overcome and why sometimes the bravest thing you can do is take the leap, even when you don't know where you'll land!Run With Us In Australia - https://runthroughaustralia.com/Abi Jones - https://www.instagram.com/absjfit/Ben Sheppard - https://www.instagram.com/bensheppard93/

Connect with Abi: https://www.instagram.com/abistumvoll/I don't bring many women onto BraveCo, but when I do, it's because they have something that men need to hear — something they won't get anywhere else. Abby Stumble is one of my oldest and most trusted friends, and this conversation is one of the most honest ones I've ever had on this podcast. Abby grew up thinking she had a great childhood. She was wrong. A mentally ill, drug-addicted mother. A home full of chaos she internalized as her own failure. Panic attacks, suicidal thoughts, self-hatred, and a body she despised — all without a single clear explanation for why. It wasn't until she was 37 that the real story started to unravel. And what happened next changed everything she thought she knew about herself, her marriage, and what healing actually looks like.We go deep into marriage in this one — specifically what happened when two beautiful train-wrecks decided to build a life together. Abby and Justin's story is a masterclass in how broken attachment cycles play out in real relationships: the avoidant man who disappears, the anxious woman who picks fights just to pull him back, and both of them trauma-bonding through explosions they thought was just how love worked. Sound familiar? We unpack the exact moment their marriage started to change — and it wasn't a big dramatic breakthrough. It was ownership. Honesty without shame. Vulnerability that didn't demand rescue. And I share my own piece of this too, because for years I went home every night feeling like a boy, not a man — isolated, ashamed, and slowly drowning while Lauren watched me disappear. This is the conversation that brings all of that into the open.And then Abby goes somewhere I didn't expect. She tells the story of a season four years ago when she was so sick she couldn't walk ten feet, had lost thirty pounds, and begged Justin — through genuine physical torment — to end her suffering. What she learned in that dark place about present-moment living, nervous system regulation, collecting moments of good, and training your brain to attach to safety instead of pain is some of the most practical, life-changing content I've ever heard. If you're in a hard season right now — with your health, your marriage, your emotions, or your sense of who you are as a man — this episode is for you. Stay Brave.Chapters:00:00 – Welcome to BraveCo09:44 – Growing Up in Chaos19:27 – The Slow Unraveling29:11 – Two Trainwrecks, One Marriage38:54 – Jason's Story48:38 – The Vulnerability Men Fear Most 58:21 – Small Steps, Big Culture1:08:05 – When the Body Breaks Down1:17:48 – Regulating the Nervous System1:27:32 – The Tiny Things, The Future With Hope, and a Prayer Over Every Person ListeningCONNECT WITH BRAVECOJoin Our Free Community for Men (ladies, sign up your man): https://www.braveco.orgFacebook: https://www.facebook.com/braveco.menInstagram: https://www.instagram.com/braveco.men/Shop: https://shop.braveco.org/ABOUT BRAVECO: We live in a time where men are hunting for the truth and looking for the codebook to manhood. At BraveCo, we are on a mission to heal the narrative of masculinity across a generation; fighting the good fight together because every man should feel confident and capable of facing his pain, loving deeply, and leading a life that impacts the world around him.

When you start studying a group of plants, you never know what you are going to find. Sometimes it's important insights into pollination and seed dispersal. Other times it's how the uplift of mountain chains shapes wetlands and rivers. These are the kinds of discoveries that drive Dr. Ana Bedoya to study the riverweeds of the family Podostemaceae. These extreme aquatic plants are fascinating in the own right while also having a lot to teach us about a variety of scientific disciplines. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Fr. Mike touches on King Rehobo'am's last acts and the rise of his son, Abi′jah. He also explains how the mistakes of Israel's leaders show the importance of faith over success. Today's readings are 1 Kings 13, 2 Chronicles 12-13, and Song of Solomon 2. For the complete reading plan, visit ascensionpress.com/bibleinayear. Please note: The Bible contains adult themes that may not be suitable for children - parental discretion is advised.

 Meet Angela Standridge, Director of the Texas Technology Access Program (TTAP) at the University of Texas. The program helps people with disabilities get access to assistive technology so they can live more independently.What is Assistive Technology (AT)? is any device, equipment, software program, or product that helps a person with a disability improve or maintain their ability to function.TTAP makes these tools easy to find and use. They not only have a library of available devices but also provide product demonstrations, 35-day loaner devices, recycled equipment, and information about national loan programs. Angela explains that the tool itself is not the full solution—the real solution is how the person uses it in their own environment to meet their specific needs. Listen in and find out how this amazing program allows those of us with disabilities to live a more independent life.Guest Social Media info - Website: https://ttap.disabilitystudies.utexas.edu/Facebook: https://www.facebook.com/UTTTAP @UTTTAPInsta: https://www.instagram.com/txtechaccess/?hl=en @txtechaccessYouTube : https://www.youtube.com/channel/UCZXFb_pP3efgjRrTT4nMoeQ @texastechnologyaccessprogramBluesky: https://bsky.app/profile/txtechnologyaccess.bsky.social @txtechnologyaccess.bsky.socialSend us Fan MailSupport the showYou can find this episode's transcript here.New episodes drop every other Thursday everywhere you listen to podcasts. 

Abi and Matt are stressed out. 

Kaip praėjo pirmosios socialdemokratų ir demokratų sąjungos “Vardan Lietuvos” derybos dėl koalicijos sudarymo? Abi politinės jėgos kalba, kad Vyriausybės atsinaujinimas turėtų atnešti daugiau rimties ir nebūti tik kosmetinis.Lietuvoje - dar viena duomenų vagystė. Šįkart nukentėjo medikai. Valstybinė akreditavimo sveikatos priežiūros veiklai tarnyba pastebėjo, kad pasisavinta apie 62 tūkstančių įrašų. Sveikatos apsaugos ministrė Marija Jakubauskienė tikina , kad į e-sveikatą įsilaužta nebuvo.Iš antros pensijų pakopos pinigus atsiėmę gyventojai pusę milijardo eurų tuoj pat išsigrynino, ir tai nustebino Lietuvos banką. Per keturis mėnesius iš viso atsiimti beveik 3 milijardai eurų, tačiau didžioji dalis lėšų laikoma bankų sąskaitose.Ved. L. Želnienė

Abi Millar grew up in a charismatic evangelical church where faith once felt vivid, immediate and full of certainty. But as questions about science, belief, heaven and hell began to press in, that certainty slowly unravelled. In this conversation, Tim talks with Abi about what it cost to leave, the freedom and loss that followed, and the spiritual hunger that eventually re-emerged after a long season of atheism. They also talk about some of the practices Abi explores in her book The Spirituality Gap — including yoga, ayahuasca, tarot and meditation — and the tension between scepticism and openness that runs through her journey. Along the way, the conversation touches on rootedness, community, cultural integrity, and the question of whether spirituality can truly flourish without a shared story or tradition. Following the interview, Nomad hosts Tim and Nick reflect on the burden of heaven and hell, the freedom and loss of leaving evangelical faith, and the search for meaning beyond certainty. They also explore what Abi's journey raises about psychedelics, tarot, rootedness, and the limits of highly individual spirituality.Interview starts at 10m 34sBooks, quotes, links →The creation of Nomad's thoughtful, ad-free content is entirely funded by our equally thoughtful and wonderful listeners. By supporting us, you gain access to Nomad's online spaces—like the Beloved Listener Lounge, Enneagram Lounge, and Book Club—as well as bonus episodes such as Nomad Contemplations, Homegrown Conversations, and Nomad Revisited.If you'd like to join our lovely community of supporters, head over to our Patreon page. You might even be rewarded with a Nomad pen or our coveted Beloved Listener mug!If a monthly commitment isn't possible right now, a one-off donation is always deeply appreciated—you can do that here.Looking to connect with others nearby? Check out the Listener Map or join our Nomad Gathering Facebook group.And if you're up for sharing your own story, we regularly post reflections from listeners on our blog—all with the hope of fostering deeper understanding, connection and supportive relationships. If you'd like to share your story on the blog, contact us for more information here.

Recorded live at DX Annual, Abi Noda, co-founder and CEO of DX, joins Brian Houck of Microsoft to share an early look at DX's new research on AI's impact on engineering velocity.Drawing on data from a sample of DX customers, they discuss what companies are actually seeing as AI adoption matures. Most organizations in the study saw pull request throughput increase by 10 to 15 percent—far more modest than the 10x gains often promised in industry headlines.They explore why coding remains only a small part of developer work, where time saved by AI may be going, and the unintended consequences of moving faster, from shifting bottlenecks to “false velocity.” Abi also shares how engineering leaders are applying AI beyond coding and how DX is evolving its measurement framework to account for both human and agent productivity.Where to find Brian Houck: • LinkedIn: https://www.linkedin.com/in/brianhouck/ Where to find Abi Noda:• LinkedIn: https://www.linkedin.com/in/abinoda In this episode, we cover:(00:00) Intro(00:53) What motivated DX's research into AI's impact on engineering velocity(02:36) How DX designed the study and selected companies(04:54) What DX's data reveals about AI's impact on engineering throughput(06:31) Why PR throughput was the most practical metric to publish(08:21) Why AI productivity gains are lower than many leaders expected(10:24) How an all-in culture can amplify AI productivity gains(12:35) Why it's hard to track where AI-generated time savings are going(15:04) Unintended consequences of AI-driven productivity gains(17:12) Why leaders should look beyond coding to the rest of the SDLC(19:43) Cognitive debt and the human costs of AI-assisted development(21:33) How DX's AI measurement framework is evolving(24:42) How to make agents more effectiveReferenced:• DX Core 4 Productivity Framework • DORA, SPACE, and DevEx: Which framework should you use?• Time Warp: The Gap Between Developers' Ideal vs Actual Workweeks in an AI-Driven Era - Microsoft • Research• How Generative and Agentic AI Shift Concern from Technical Debt to Cognitive Debt• Measuring AI code assistants and agents

Plants are habitat. Heck, even a single leaf is habitat. Same goes for plant roots. This is especially true when we consider insects and fungi. But how do these organisms interact? How do they change over gradients of moisture, temperature, space, and time? Why do we consider some parasitic while others are mutualists? The world of ecological interactions is extremely complex but people like Dr. Chris Bivins are taking stabs at trying to gain insights piece by piece. Join us for an wonderfully deep dive on the amazing ways oaks, gall wasps, fungi, and mycoheterotrophic plants live out their mysterious lives together. This episode was produced in part by Chris, Gerald, Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Jesus said “I am the Good Shepherd”. Abi speaks about Jesus the Good Shepherd. John 10-1-21 Abi Steinegger

Discover the unconventional strategies behind building a successful land investment business in this insightful conversation with Abi Asija. From direct mail marketing and owner financing to creating a customer loyalty flywheel, Abi shares the systems, mindset, and relationship-driven approach that helped him scale his business and create long-term success. Learn how focusing on customer experience, rapid response times, continuous improvement, and strategic niche marketing can help entrepreneurs build a sustainable and highly profitable business. Main Topics Abi Asija's journey from corporate IT to land investing and entrepreneurship How to buy and sell raw land in remote desert markets with limited utility Using direct mail and public records to source land deals Building goodwill and increasing customer lifetime value through exceptional service Leveraging referrals, reviews, and relationships to drive business growth The importance of niching down and targeting specific customer avatars Creating systems and processes that support scalability Practical sales strategies, including speed-to-lead, objection handling, and offer creation Hiring principles for building a high-performance team The mindset shift from side hustles to building a real business Continuous improvement as a competitive advantage The role of content marketing, community building, and reputation management Timestamps 00:00 – Introduction and podcast support note 00:30 – Abi Asija's background and transition into land investing 01:29 – Why raw desert land can be a profitable investment 02:28 – Buying tax-delinquent properties and flipping them for profit 03:25 – Using public records and software to streamline acquisitions 04:32 – The economics of direct mail campaigns in land investing 05:19 – Early success stories selling land on eBay and other platforms 06:54 – Understanding buyer motivations and land use cases 07:55 – Land as a long-term investment and speculative asset 09:21 – Challenges of selling raw land and market dynamics 10:07 – Utility companies and rare high-profit land opportunities 11:23 – Building goodwill through owner financing and customer service 12:37 – Growing through referrals and word-of-mouth marketing 14:24 – Over-delivering and strengthening customer relationships 15:08 – Why owner financing creates opportunities for buyers 16:20 – Managing tax risks, foreclosures, and customer retention 17:16 – Treating entrepreneurship as a serious business from day one 18:17 – Building scalable referral and reputation systems 19:36 – Effective upselling strategies and creating multiple offers 20:50 – Why speed-to-lead is critical in sales 22:07 – Scaling operations with offshore support teams 24:26 – Increasing customer lifetime value through systems and offers 26:07 – Continuous improvement and operational excellence 27:55 – Customer-centric lessons from successful business leaders 29:52 – Hiring and developing high-performance teams 32:19 – The power of niche marketing and focused messaging 34:48 – Future plans for scaling and building a lasting legacy 36:03 – The reality of entrepreneurship and hard work 38:22 – Fast response strategies for closing more deals 41:49 – Why relationships outperform cold outreach over time 44:48 – Creating valuable content that attracts ideal customers 55:54 – Solving specific problems through focused content marketing 58:44 – Why niching down is essential for business growth 59:02 – Abi's long-term vision and future goals 60:43 – Balancing growth, scalability, and lifestyle design 62:36 – Community, networking, and lifelong learning 63:40 – How to connect with Abi Asija and access his resources Resources & Links The Land Business by Abi Asija Abi Asija on LinkedIn Honest Wealth Builders YouTube Channel Your Business Website Connect with Abi Asija LinkedIn YouTube Channel Email

Champions Edition im Triathlon-Chat! Nach dem Neuseenman holen Nick und Nils die beiden Gewinner:innen des Pushing-Limits-Clubrennens ans Mikro: Naima und Max. Beide waren nicht nur im Club ganz vorne, sondern haben auch im Gesamtfeld richtig starke Ausrufezeichen gesetzt.In der Folge geht es um ihre ganz unterschiedlichen Wege in den Triathlon: Naima kommt aus dem Radsport und arbeitet heute als Ärztin in der Unfallchirurgie, Max ist erst seit rund dreieinhalb Jahren im Triathlon unterwegs, hat neben Abi, Barista-Job und Lebensumbruch den Sport für sich entdeckt – und fährt inzwischen Zeiten, die selbst Nick und Nils staunen lassen.Natürlich sprechen die vier auch ausführlich über das Rennen: Schwimmen, Pacing, Wattwerte, Laufbeine, die richtige Strategie und das Gefühl, wenn am Ende plötzlich ein richtig großer Tag dabei herauskommt. Dazu gibt's viel Community-Vibe, ehrliche Einblicke, Trainingsgeschichten und die Erkenntnis: In der Pushing-Limits-Bubble schlummern verdammt viele schnelle und spannende Geschichten.Themen der Folge:Neuseenman, Pushing-Limits-Clubrennen, Naima & Max, Race-Recap, Community, Triathlon-Einstieg, Training mit App, Schwimmen, Radfahren, Laufen, Pacing, Krafttraining und die Frage, wie aus ganz normalen Lebenswegen ziemlich außergewöhnliche Leistungen entstehen.Werbung: IncylenceRabattcode: pushinglimitsRabatt: 15% auf alles außer bereits reduzierte ArtikelGültig bis 21.06.26https://incylence.com/collections/laufsockenWerbung: PUSHING LIMITS CLUB30 Tage kostenlos testen

Champions Edition im Triathlon-Chat! Nach dem Neuseenman holen Nick und Nils die beiden Gewinner:innen des Pushing-Limits-Clubrennens ans Mikro: Naima und Max. Beide waren nicht nur im Club ganz vorne, sondern haben auch im Gesamtfeld richtig starke Ausrufezeichen gesetzt. In der Folge geht es um ihre ganz unterschiedlichen Wege in den Triathlon: Naima kommt aus dem Radsport und arbeitet heute als Ärztin in der Unfallchirurgie, Max ist erst seit rund dreieinhalb Jahren im Triathlon unterwegs, hat neben Abi, Barista-Job und Lebensumbruch den Sport für sich entdeckt – und fährt inzwischen Zeiten, die selbst Nick und Nils staunen lassen. Natürlich sprechen die vier auch ausführlich über das Rennen: Schwimmen, Pacing, Wattwerte, Laufbeine, die richtige Strategie und das Gefühl, wenn am Ende plötzlich ein richtig großer Tag dabei herauskommt. Dazu gibt's viel Community-Vibe, ehrliche Einblicke, Trainingsgeschichten und die Erkenntnis: In der Pushing-Limits-Bubble schlummern verdammt viele schnelle und spannende Geschichten. Themen der Folge: Neuseenman, Pushing-Limits-Clubrennen, Naima & Max, Race-Recap, Community, Triathlon-Einstieg, Training mit App, Schwimmen, Radfahren, Laufen, Pacing, Krafttraining und die Frage, wie aus ganz normalen Lebenswegen ziemlich außergewöhnliche Leistungen entstehen.

A bi-weekly news show informing you on the latest in Bitcoin, privacy and open source tech hosted by Ungovernables, Max and Q. AOBFTF with ZachQ eurotripNew Foundation websiteNEWSU.S. Treasury seizes nearly 1B in Iran-linked crypto, Tether freezes 344M USDT on Tron https://bitcoinmagazine.com/news/u-s-treasury-the-united-states-iranThe Mined in America Act would put the Bitcoin network at riskhttps://www.therage.co/mined-in-america-act-bitcoin-at-risk/CVE in Core Lightning: Optech #407 disclosurehttps://bitcoinops.org/en/newsletters/2026/05/29/Introducing Cube: Burak unveils a trustless Bitcoin smart contract L2https://medium.com/cube-bitcoin/introducing-cube-8b3702e470a5Published: May 2026Anonymous plaintiff sues for title to $293 billion in dormant Bitcoinhttps://bitcoinmagazine.com/news/anonymous-plaintiff-seeks-legal-bitcoinPublished: 2026-05-28The U.S. Constitution inscribed on the Bitcoin blockchain via expanded OP_RETURN https://bitcoinmagazine.com/news/someone-inscribed-the-constitution-bitcoinPublished: 2026-05-29RELEASESBitcoin Protocol, Core, Knots, SecurityCore Lightning v26.06rc2 — 2026-05-22Release candidate 2 for CLN 26.06. Documentation and gRPC interface refinements on top of rc1's graceful command, sendamount RPC, and BOLT12 payer-proof support. Routing-node operators should test on a non-production node before adopting.Eclair 0.14.0 — 2026-05-21Significant Lightning release from ACINQ. Final versions of channel splicing, simple taproot channels, and zero-fee commitments all ship in this version. This is the Eclair side of the same protocol work showing up in CLN and LDK. If you run an Eclair routing node, this is the upgrade to track.Hardware Signers and Hardware-Wallet AppsColdcard MK5 launch — 2026-05-29New flagship hardware. Larger Gorilla Glass screen, redesigned buttons, improved NFC, dual secure element architecture retained. Already supported in Bitcoin Safe 2.0.0rc0 from earlier this fortnight.Frostsnap 0.3.0 — 2026-05-27Headline change: deterministic firmware build with cryptographic digest verification. So end users can independently verify the firmware binary matches the source. That is the right direction for any hardware signer carrying real money.Keystone 3 v2.4.4 — 2026-05-26Wallet connection removal, Zcash SLIP39 support added, device verification fixes.Trezor Suite v26.5.1 — 2026-05-27 (FTD re-surfacing)Adds ERC-681 QR code support in the send form. Show editorial: only relevant if you use Trezor for Ethereum-side workflows, not a Bitcoin-only change.Ledger Live Desktop 4.5.0 — 2026-05-21Bridge integration refactoring across desktop and mobile.Ledger Live Mobile 4.6.0 — 2026-05-28Async API updates and bridge resolution improvements.Software WalletsSparrow Wallet 2.5.0 — 2026-05-21Headline feature: Silent Payments receiving wallets, including support for airgapped hardware wallet signers. Adds frigate.2140.dev as a Silent Payments capable public Electrum server, auto-selected when required. Plus a BIP32 derivation fallback when retrieving signing nodes for high-index inputs. This is the biggest privacy upgrade of the fortnight in any consumer-facing Bitcoin wallet, and the airgapped-signer support means Coldcard and similar users get it without going hot.Sparrow Frigate 1.5.3 — 2026-05-30Adds a privacy-preserving hourly aggregate of historical scan stats, locally generated server.features response when the backend returns a method-not-found error, improvements to the hosts field in server.features.Bitcoin Seed Tool 2.3.0 — 2026-05-19 (borderline, in grace)Educational interface redesign with violet accent color and integrated learning features.Nunchuk Android 2.5.2 — 2026-05-27"Bug fixes and improvements," nothing detailed publicly.Liana Business v0.1 — 2026-05-20First alpha of Liana's business product line. Environment variable support for signet testing. New product tier from Wizard Sardine for business-focused multisig with timelocked recovery.Peach Bitcoin 0.69.0 (build 350) — 2026-05-19Encrypted backup of custom payout addresses, restoration guidance, camera permission fix, push notification translations.Lightning, L2, ScalingPhoenix 2.8.0 — 2026-05-22UI fixes on Android: scanning inverted QR codes, a button to use the entire available balance when paying Lightning.Phoenixd 0.8.0 — 2026-05-20Upgraded lightning-kmp dependency to 1.12.0.ZEUS 13.0.2 — 2026-05-21Stable release of the RC chain we previewed last fortnight. New default RGS server at rgs.zeusln.com with 15-minute graph updates instead of 3-hour. Improved clipboard, NFC, UI improvements.Arkade arkd v0.9.6 — 2026-05-26Package and component renaming, CI workflow improvements, golang version bump.Arkade TS SDK @arkade-os/sdk 0.4.32 — 2026-05-29Maintenance bump.Arkade TS SDK @arkade-os/boltz-swap 0.3.37 — 2026-05-29Maintenance bump on the Boltz-swap helper.ThunderHub v0.18.4 — 2026-05-29Native display formatting for trading distribution, better CLTV headroom in route building.Blink Mobile 2.4.49 — 2026-05-30Bug fix: removes ABI-prefixed versionCode overrides.LNbits v1.5.5-rc1 — 2026-05-24Release candidate.Mostro v0.17.4 — 2026-05-22Payout confirmation to winner, solver-directed dispute slash, concurrent taker bonds with first-to-lock wins, MOSTRO_NSEC_PRIVKEY environment variable, Yadio price tolerance fix.Bisq v1.10.1 — 2026-05-30Raises trade amount limits to 0.250 BTC after the v1.10.0 post-exploit reset. Adjusts risk-based reduction factors. Fixes a BSQ swap validation bug.Bisq v1.10.0 — 2026-05-17 (carries over from last fortnight as final tag on cutoff day)The post-incident hardening release we covered last fortnight: trade protocol validation, PGP supply-chain verification, 0.125 BTC initial cap, macOS Apple Silicon support.EcashCashu TS v4.5.1 — 2026-05-23Deprecates the current checkProofsStates method in favour of a v5-compatible one. Wallet builders should plan the migration.Fedimint SDK canary release — 2026-05-27React Native transport: flattened RPC payload, persistent callback. Rolling canary channel.Bitcoin Dev InfrastructureBDK FFI 3.0.0 — 2026-05-29Major version of the BDK language bindings. Anyone shipping a wallet on top of BDK should read the migration notes carefully.Liquid GDK 0.77.4 — 2026-05-27Rate-limiting error handling, Rust dependency updates, UTXO retrieval fixes, build improvements.Self-Hosting and Sovereignty InfraJoinMarket-NG 0.31.1 — 2026-05-30Privacy-critical fix: prevents a Sybil DoS where relayed !hp2 floods could starve a maker's own post-ioauth commitment broadcasts. Also installs whiptail in maker and taker container images so the jm-ng TUI works out of the box. JoinMarket-NG continues to ship hardening on a tight cadence.Tor Browser 15.0.14 — 2026-05-19 (borderline, in grace)Important Firefox security updates rolled in.Mullvad Browser 15.0.14 — 2026-05-19 (borderline, in grace)Firefox 140.11.0esr base, NoScript 13.6.19.1984.Nostr (Bitcoin-relevant)Amethyst 1.11.0 — 2026-05-20Restores Lightning Address and LNURL fields in Edit Profile. Useful: those fields were missing for a stretch and creators relying on zaps as a revenue stream were getting cut off in profile edits.EDUCATIONTFTC retrospective: Why Keonne Rodriguez is in prison for building Samourai Wallet — 2026-05-28Bitcoin Optech Newsletter #407 — 2026-05-29CLN vulnerability disclosure (already in news), transcripts from a May Bitcoin Core developer meeting covering SwiftSync, cluster mempool, Erlay redesign, package relay. Eclair 0.14.0 and CLN 26.06rc2 release context.Bitcoin Optech Newsletter #406 — 2026-05-22BIP322 advances to Complete status with human-readable prefixes and PSBT support. TCP hole punching for Bitcoin nodes behind NATs (we flagged this Delving Bitcoin thread last fortnight). Services section highlights Ibis Wallet (BDK-based with coin control and Tor), LDK Server, Mempool.space taproot visualization.Bitcoin Optech #406 recap podcast — 2026-05-26Discussion of BIP322 updates, TCP hole punching, Ibis Wallet, LDK Server, Mempool.space v3.3.0, peer-observer infrastructure.Bitcoin Optech #405 recap podcast — 2026-05-19Bitcoin Core CVE-2024-52911 discussion and the UTXO-set P2P sharing draft BIP with Fabian Jahr.Rainey's book on financial censorshipMentioned by Gladstein on 2026-05-21 as quoting his work on the war on cash and the blocksize war. Plug in education / further reading.TO DONATE TO ROMAN'S DEFENSE FUND: https://freeromanstorm.com/donateHELP GET SAMOURAI A PARDONSIGN THE PETITION ----> https://www.change.org/p/stand-up-for-freedom-pardon-the-innocent-coders-jailed-for-building-privacy-tools DONATE TO THE FAMILIES ----> https://www.givesendgo.com/billandkeonneSUPPORT ON SOCIAL MEDIA ---> https://billandkeonne.org/VALUE…

Ambicingas palangiškis ėmėsi misijos naujam gyvenimui prikelti Palangos klasika tapusias vietas „Rąžė“ ir „Naglis“. Abi jos – neatsiejama kurorto dalis, savyje slepia begalę per dešimtmečius sukauptų nuotykių ir turtingą istoriją – būtent ją Albertas Martinaitis nori tęsti kuriant čia naująją kurorto kultūrą. Gimęs ir užaugęs prie jūros, verslininkas siekia atskleisti kitokį Palangos veidą bei paversti šias vietas kertiniais miesto kultūros taškais ne tik su istorija, bet ir prasme.

Ambicingas palangiškis ėmėsi misijos naujam gyvenimui prikelti Palangos klasika tapusias vietas „Rąžė“ ir „Naglis“. Abi jos – neatsiejama kurorto dalis, savyje slepia begalę per dešimtmečius sukauptų nuotykių ir turtingą istoriją – būtent ją Albertas Martinaitis nori tęsti kuriant čia naująją kurorto kultūrą. Gimęs ir užaugęs prie jūros verslininkas siekia atskleisti kitokį Palangos veidą bei paversti šias vietas kertiniais miesto kultūros taškais ne tik su istorija, bet ir prasme.Kelių tiesimo ir priežiūros bendrovės pastebi, kad karo ar krizės atveju dalis kelių Baltijos šalyse gali tapti nepravažiuojami karinei technikai, o Lietuvoje apie 100 tiltų gali neatlaikyti sunkiosios karinės technikos. Tai reiškia ne abstrakčią infrastruktūros problemą, o labai konkrečias minutes – kaip greitai juda sąjungininkai, technika, amunicija, kaip vyksta evakuacija ir ar turime alternatyvius maršrutus.Padėti tiems, kuriems pritapti tarp kitų ne visada paprasta - tokį tikslą sau kelia projekto „Leisk man būti“ autoriai. Psichologo Kristijono Žičkaus ir „Vaikų svajonės“ vadovės Ramunės Baltaduonienės padedami jaunuoliai, iškritę iš švietimo sistemos, stojasi ant kojų ir siekia savo tikslų.Tęsime Lietuvos radijo istorijos maršrutą. Šiandien - apie radijo pastatą Sitkūnuose.Išgirsite Švenčionių rajono pakraštyje įsikūrusį Eimutį Valiuką, kuris domisi krašto istorija ir pats rekonstruoja šimtametį namą - jį dengia nendriniu stogu.Ved. Darius Matas.

I'm excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World's Fair! We'll streaming live from MS Build today for a special crossover pod with our friends at No Priors and the one and only Satya Nadella. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, GitHub has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc.This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - growing 1400% in 2026, it marked a new era that was both extremely exciting and challenging for GitHub.While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure:Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story:So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents?Which brings us to the perfect person to answer these questions: GitHub COO Kyle Daigle. In this episode, he joins swyx to unpack what happens when AI doesn't just autocomplete code, but starts changing how companies operate, how open source works, how pull requests get reviewed, and how GitHub itself has to scale. We go deep on GitHub's internal AI workflows: micro-skills, WorkIQ, MCP, Slack, Teams, email, Copilot workflows, the new Copilot desktop app, CLI, cloud agents, and how Kyle uses agents to look backwards across company context before deciding what to do next. Kyle also reflects on GitHub's history building webhooks, APIs, Actions, npm, Dependabot, and Semmle, why the AI era is breaking GitHub in new ways, how Actions became a general-purpose compute layer, and what Copilot becomes after code completion.Full Video PodWe discuss:* Kyle's expanded role across GitHub* How AI got Kyle coding again after years in leadership* Why GitHub rolls out AI through existing workflows instead of forcing new tools* WorkIQ, MCP, Slack, Teams, email, and GitHub as company context* Why massive “mega-skills” are giving way to small, atomic micro-skills* How AI changes summarization, communications, marketing, and analyst work* Why former developers in leadership may have a unique advantage in the AI era* Kyle's “15 agents on Saturday” workflow* How Kyle built an AI-generated executive presentation for CRO/CFO teams* Why AI changes the chief of staff role without removing the human work* GitHub Actions, webhooks, arbitrary code execution, and secure agent compute* The npm acquisition, supply-chain security, 2FA, and token invalidation* Slop forks, vendoring, and whether AI agents change dependency management* What pull requests become when most PRs come from agents* Prompt requests, vouching, AI review, and trust in open source* What counts as a “developer” when AI lowers the barrier to building* GitHub Spark, low-code, and why GitHub refuses to hide the code* 14x commit growth, Actions load, databases, monorepos, and availability* Copilot's evolution from completion to CLI, desktop app, cloud agents, and SDK* Context, memory, rules, and making GitHub “act like Kyle wants it to act”* Ambient AI, OpenClaw, enterprise security, and the new operating system for agents* What swyx should ask Satya Nadella about Microsoft's AI futureKyle Daigle* LinkedIn: https://www.linkedin.com/in/kyledaigle* X: https://x.com/kdaigleTimestamps00:00:00 Introduction00:03:36 Why AI Got Kyle Coding Again00:07:04 Running GitHub with AI: WorkIQ, MCP, Slack, Teams, and Skills00:15:39 The Golden Age for Former Developers in Leadership00:17:31 15 Agents on Saturday and AI-Generated Executive Work00:20:20 How AI Changes the Chief of Staff Role00:21:45 GitHub's History: Actions, npm, Webhooks, and Open Source00:28:45 Slop Forks, Vendoring, and AI Dependency Management00:33:57 Pull Requests, Prompt Requests, and Trust in Agent-Generated Code00:41:21 GitHub Stars, 200M+ Developers, and the New AI Builder Wave00:45:15 GitHub Spark, Low-Code, and Why GitHub Still Shows the Code00:47:38 GitHub's Hardest Era: 14x Growth, Reliability, and Scale00:59:21 Actions as the Compute Layer for CI/CD and Automation01:02:04 The State and Future of GitHub Copilot01:08:24 Ambient AI, Background Agents, and the Future of the SDLC01:13:09 OpenClaw, Enterprise Security, and the New OS for Agents01:18:03 Build Announcements, WorkIQ, FoundryIQ, and Microsoft Context01:21:41 What Should swyx Ask Satya?TranscriptIntroduction: Kyle Daigle's Expanded Role at GitHub and MicrosoftSwyx [00:00:00]: We're here with Kyle Daigle, COO of GitHub. Welcome.Kyle [00:00:07]: Hey, thanks for having me.Swyx [00:00:08]: You're not just CEO of GitHub. People know you as that. You have a new role.Kyle [00:00:11]: So I have an expanded role now. I've been working at GitHub for thirteen years and doing all things developer. Joined as a developer myself. And now, I'm also responsible as the CMO of Developer for Microsoft. And so all the kind of learnings and passion for developers and how we work with them and how we communicate and how we bring our products to market, we're also bringing that expertise to the broader Microsoft ecosystem and helping every developer that uses a Microsoft product or would like to have a sort of similar experience that they've had with GitHub over the years. So it's a different role in some ways, but it's also just building on the experience that I've had at GitHub of just sort of tell the truth, be authentic, show people how to use it and then let the products speak for themselves. Now just doing that with, all of Microsoft.Swyx [00:01:09]: We'll be releasing this in conjunction with Build. You got lots of stuff planned, and we can sort of touch on that whenever it's appropriate. I think one of the interesting things is I rarely meet a COO who's also a CMO. I think you're a very outward facing and you're very confident publicly. That's rare. Do you actually view yourself as COO? What's What is your thing?From GitHub Developer to COO/CMO: Building the Platform and Operating GitHubKyle [00:01:33]: I think for me, it's been funny. The titles have always been, a— have always felt a little strange to me. I joined GitHub as a developer? I wrote so much of theSwyx [00:01:46]: Let's bring that up. You wrote the back ends?Kyle [00:01:48]: I was going through, I was going through, some old photos, when folks were talking about how things were being built or how there was a build GitHub. I built, webhooks and worked with teams building the API, built the platform layer. Anything that integrated with GitHub, up until really twenty eighteen, I built or ran the engineering teams. And that's kind of where my the beginning of my passion always was helping people build things, deliver them to, their customers. And so being a developer, building for developers was always super unique. In a— I think as my role expanded, it became my ability to talk to not just developers, but also enterprise customers or business leaders and have this translation layer. And then through all those years, GitHub has always operated pretty uniquely. Post-pandemic, working remotely was not as novel as it was when GitHub started in two thousand and eight. But all that expertise of running remote teams, doing it well, became this sort of bigger role, ultimately turning into the COO role of how do we operate GitHub in the way that GitHub's always operated after the Microsoft acquisition. And kind of so on from there. So like for me, I think the— I've, I still code. I love coding but the problem has always been, people. It's a much harder problem to both support our own employees, a harder problem to communicate to developers and enterprise buyers what we're building why it matters, ‘cause those are two very different messages. And so getting to work in the mix of COO, CMO, also just being a dev, I think is what's kept me at GitHub for so long.AI Workflows for Leadership: Commits, Retrospectives, and ContextSwyx [00:03:40]: Apparently, you have— your commits have gone up. What's this? What's going on?Kyle [00:03:45]: Rui's called me out pretty aggressively. So I think— as you can imagine, right, you can see my normal era of being a dev In the twenty thirteen, twenty fourteen era, and then moving into management, and then ultimately the COO role. I think what you see there is me, really getting back to coding thanks to AI. I— similar to, attaching problems between how to market and how to operate a business and how to code, I find, building agents and workflows that are connecting very disparate problems to be what's driving this. So that's, some of it's writing software. A lot of it is, connecting a ton of a different data sources to, help me out. But that is completely me really diving in on the AI side in trying out our tools, trying out everyone's tools, But building for me, building for the non-technical leader, though I'm technical and how we're, able to use these tools more than just the simple, call and response that I think a lot of the non-technical, your employers, you have to get— you have to use AI, and so everyone uses, ChatGPT or Copilot or Claude or whatever. To really get into, how is this going to help me out, it— I find that it's not the I need to write a blog post, I need to those simple examples. Helping people find the workflows of, “Okay, I need you to go through all the PRs today. I need you to go through everything that we've posted online. I need you to go through what we did the last three months. Go through all of my Obsidian notes for any mentions of this then go through my transcripts at work.” We use, Teams, so, using WorkIQ, go call that MCP server, grab all the transcripts, go through all the Slack, and then build me out the plan of, what this week's messaging actually was. That's something that was, impossible because for me, I find AI in a what most of this launch here is actually, less building forward. It's actually, a recursive loop backwards. I'm always looking at what had happened first. Go back through the week and tell me what we did, what worked, what didn't work? And then tell me in the next three or four days-What would you tweak based on this sort of like looking backwards and then looking ahead a little bit? I find that to be so much more valuable, especially for like non-technical, because that retrospection is actually LLMs are very good at that. Like finding all the patterns, pulling them out, and then applying that retrospection to just a couple of days or just like a short period of time. Is all a bunch of apps that I've built and launched a bunch of, internal tools. I use the new, GitHub Copilot app, the desktop app with workflows. Every time I crack open my laptop, it's running workflows for me. It's just a ton of different stuff and of course, it all ends up on, it all ends up on GitHub.Swyx [00:06:47]: Of course. That's where, that's where, stuff is hosted. Man, there's so much to ask you. I was going to leave the how do you run a company with AI thing at the end. I have to ask one— double click one thing. You said, you are looking back at the week. You're, you're understanding what happens. When you say we That's three thousand people. How?Rolling Out AI Internally: Skills, CLIs, and Company ContextKyle [00:07:09]: I think when we started rolling out AI internally beyond engineering, right? One of the things that I was really, passionate about is like we have to do this in a way where no one has to change how they work. I don't want to have to teach you a tool. I don't want to have to teach you something new. And so for us, we tried out a few tools. Most of them don't work because I got to get you on board? I got to teach you how to use it. What we've actually ended up doing is we've built like a set of skills internally. We have we each have our set of skills, and we've just been distributing even to the non-technical folks, the CLI. And then effectively, we're just giving it access to like read about everything that we're writing. So that's for us, that's usually GitHub, Teams, Email, and Slack. So Teams for, video chat, generally speaking.Swyx [00:08:03]: Teams and Slack?Kyle [00:08:04]: so we use Teams for video communication, but we don't use it for chat. W-we— GitHub for a long history, right? We're alwaysSwyx [00:08:13]: Also SlackKyle [00:08:14]: Talking about ChatOps and like everything is built into Slack. Like every command, every flow.Swyx [00:08:18]: So even though you have been acquired for I don't know, eight years nowKyle [00:08:22]: we stillSwyx [00:08:23]: You still use Slack?Kyle [00:08:23]: it's a purpose-built tool for us, and I think the reality is that moving off of it would be so bluntly expensive? Simply because all the tooling is, baked in with that paradigm. And they both have their pros and cons but they don't work the same way at all. We still use a bunch of different tools Because it's the purpose-built tools that We need. And thenSwyx [00:08:47]: Well, the same doesn't go for the rest of Microsoft, presumably.Kyle [00:08:50]: like the like various teams like operateSwyx [00:08:53]: They make their own decisionsKyle [00:08:54]: Various ways. I think it just matters what you're trying to what you're trying to do. But we do we do work across kind of every tool that we use, and then by giving everyone access to all of that context and the new WorkIQ MCP server, which is quite cool if you do live in the M365 like world. I can ask it all these backwards-facing questions, and it's incredibly important for our teams that are working remotely. There's a lot of stuff you miss when you're not in an office, and we are spread out all over the world. So most of that is looking back. And then we post, we post either auto-automatically into GitHub issues or discussions, these sorts of like findings or like our industry reports. Like what's happening this morning, today, yesterday. A little automation gets run. We'll use the app. We might use GitHub Actions like with, our agentic workflows just to go do that run, and then we push it into GitHub, and w-we keep having a conversation. So usually for us, it's about that sort of like looking back, looking forward on the non-technical side. And then of course for a lot of those folks, it's also building an app, pushing it to GitHub pages or pushing it somewhere to host it et cetera. But it's just like enabling everyone with that power of it's going to take me a week to figure this out. Instead, we're going “Okay I built a skill. Let's put it into a repo. We'll all share that skill together, and then we'll use the CLI or now the app-” “just to run it.”Micro Skills vs. Mega Skills: How GitHub Uses AI at WorkSwyx [00:10:26]: All right. I think, I think we're going straight into like the team management and productivity thing. I think a lot of people are getting various levels of LLM psychosis. How do you manage the bloat of skills? Like everyone Has their thing, and they're Like trying to promote it to the rest of their peers in their org, right? And obviously, whoever becomes a skill influencer internally becomes like an AI leader, right? Of sorts. I assume you have those.Kyle [00:10:50]: like I think we haveSwyx [00:10:52]: And I assume it's a mess a Yeah.Kyle [00:10:54]: there's like I— like I think the reality is there's two pieces. Like first is I think that we're ending the era of these like massive, beautiful, perfect skills that are just like not any of those things. ‘cause for a while, right every tweet every day is like go download the skills, the perfectly managed thing to do this entire workflow. And I think that like what we've found and what— I was just with my team, this week, and we were talking about the skill side, and we're really talking about these like incredibly micro skills that are just doing one thing for us very well Versus a skill that's going to do I said, that full report. That doesn't really exist on our side anymore. It's usually how do— like a single skill that's going to identify the most important marketing information given any MCP server. Like this is the most important thing. Less about stitch a bunch of tools together and have it produce this mega output because then weeks go by, months go by, things change, and you want to tweakSwyx [00:11:58]: It's brittleKyle [00:11:58]: Your mega skill and you're screwed? You can't do that. And so now we're really just talking about the Legos we're using and just letting the instruction book be something we're all putting together. Whereas I think a lot of AI skills for a while have been that mega instruction book style.Swyx [00:12:15]: I've, thought a lot about Postel's law. I don't know if that's a term that is, means things to folks. It's the idea that you should be liberal in what you accept and strict in what you output, right? And I think that's like a good framing principle for skills. This is my skills, obviously on GitHub. I feel like everyone should have like how like some repos In GitHub are special repos? I feel like we should sort of reify the slash skills and everyone like give it some kind of special presentation. Anyway, so, yeah, this is one of those like download Download anything, transcribe anything, and then you can string together the atomic skills that do one thing well Into like some kind of orchestration skill that calls other skills. I assume, does that match?Kyle [00:12:56]: I like I think so. I think that theSwyx [00:13:00]: Summarize anything.Kyle [00:13:01]: Like I think the- For me, summarizing something for I do communications and PR and analyst relations and marketing and customer activities, and so my summarize everything is very different for each one of those like Contexts. What ‘Cause if I'm summarizing something for an analyst, that's a very different thing than, probably how I'm going to summarize something for like a customer meeting or an engagement. So that's I think like the difference when we're talking about the like the tools I might use on Saturday or the skills I might use on a Saturday when it's just for Kyle. Yeah, those are kind of like they have an atomic actual tool underneath or maybe skill, and then Kyle cares about X. But I think when we're talking about work and enabling the the marketers, communicators there, it's the atomic, this is what good summarization is, and then this is what I care about as for marketing for communications For whatever. And that I think is like the interesting matrix problem when we go from like a developer set of concerns to all kinds of different professions, is that what that word means to me is different than it means to you is different than it means to the analyst or the salesperson, and that's where I think the matrix mess is that we're starting to like still starting to find. It's about these mega skills but they're all just slight permutations, but those permutations are really important. It's the difference between someone reading this and going “Did AI make this?” what Or “This makes total sense, and I would expect this when I'm giving a briefing to Gartner,” or like whatever else.Swyx [00:14:37]: I think the beauty of it maybe is that you don't have to be that careful about what goes in there. It doesn't have to exactly fit as long as it like roughly is contained in there. I used to complain about plugin hell, basically. Like when you have a framework and then you have a hundred things that you need to integrate, everyone does like the GitHub used to be bloated full of these things. And now we don't need them anymore ‘cause now you just use skills.Former Developers in Leadership: AI as a Creation MultiplierKyle [00:15:00]: And like I think the most magical thing is the just that like I can just also crack it open. Like Like yes, I could go like change the how the plugin is coded, or like I could go do that now with AI, but I think there's just something more magical about getting a response back and being “That's not right,” and then you just crack the skill open, you just type English words and it's different. That building block is just, I think very unique. Once I get everyone to kind of understand how to best how to best make those changes to get the most power out of them.Swyx [00:15:36]: Is there a— you have a your peer group that Of people like you. Is there a common framing for Something I'm feeling is, which is true, is that is this a golden age for former developers who are now in leadership? Because you can wield the tools, you would know the right words, you're maybe not too close to the details. Doesn't matter. But like you're more effective than someone who doesn't come from that background.Kyle [00:15:59]: I think that like the secret has always been your ability to identify patterns and solve problems, and I think that for folks that like myself that don't code day to day anymore, that has made me successful as a developer, made me successful as a COO and now CMO. And so now that I have access to get and write code, I'm now applying that sort of like pattern finding and problem solving, and I know enough still about how to then go and say, “Oh, I want to make an app, but I don't want to break into jail or create something that's not going to be able to work or to be deployed scale or whatever.” that ability to apply all that additional business knowledge and still code I think is what makes that so interesting to me. Slightly different than I think some of the other like technical leaders that became business leaders and now are going back to their apps and updating them. Good for them? But I think the more, much more interesting thing is, well, now I have this whole new set of expertise over ten plus years. Why not take that and use that as a developer with these AI tools? So I definitely think that makes me more powerful, but I think that's true for like every dev as well. Most of the dev friends I still have also have some other underlying skill and passion. There's really talented, very kind of linear computer science software devs, absolutely. I just find that the folks that came from a different career, went to school for something else, went off and did this random thing, and then became a software dev, or were a dev, did a random thing, came back. Learning that extra set of information, learning those extra skills, and now having the power of an AI where I can crank up fifteen agents on Saturday while my kids are doing lacrosse, That's like really powerful. And I think it gets me back to that feeling of like creation, and it's very hard to replicate that in most other senses? That first time you build an app and you click it and you show someone that's magical. And so being able to do that not just in code, but across all kinds of different assets that's, that's huge. We were doing we're doing our every year we do our revenue planning. We talk about okay, what is it going to look like for next year? And of course as you imagine, there's, slideshows everywhere talking about what are we going to talk about, what's the narrative, et cetera. And so as you said I'm “Okay, well, I could probably just like build something to build this and then that way I don't have to go build the whole spreadsheet or I have to pass it to my team.” So we went through this process, and I got all the information and used the skills I mentioned. I built like a little app just to make it so I could look at some of the information in a SQLite database, more easily. And I ultimately built this entire presentation without touching any of it and I was “Okay, I'm just going to present this to our CRO, the CFO, their teams,” without mentioning I'd built it with AI. I like built a skill to make it look very much not AI driven. Just not pretty.AI-Generated Presentations, Human Taste, and the Changing Chief of Staff RoleSwyx [00:19:03]: Like a design. Yeah.Kyle [00:19:03]: Not pretty. But just like very clearly not AI. Kind of like don't do anything interesting.Swyx [00:19:08]: That's, yeah, that is valuable.Kyle [00:19:08]: Just go Exactly. We did the whole thing through. It used my notes from Obsidian, it used all the context I mentioned before, the plans, and Never came up once that it was AI generated.Swyx [00:19:20]: It didn't matter.Kyle [00:19:20]: Never once. D It didn't matter. And so now I takeSwyx [00:19:23]: This is a toolKyle [00:19:23]: I can take that tool and go, “Look, I don't want you to go build slideshows.” They're just helping us share information with each other. If this thing can do it With a little bit of crafting from you and then we can look at it together, awesome. There's no value in all that extra work. I think that the ability to, make it look humanly bad and and build a little app to, manipulate the data I think is part of, that upside for devs that are now in leadership roles. Because, the thing that I feel like I said before, this that's all a people, that's all a people problem. I know if you've used a coworker or not to build a slide deck, unless you spent a bunch of time to not do it.Swyx [00:20:07]: I know, but like it was so, I think there's a certain charm to just being blatantly AI. ‘Cause I think that you're well, you're just honest about There may be mistakes here that I cannot vouch for. So how much value is there? But anyway I think, actually the real question I want to ask is, there's a— You were a chief of staff To Thomas. And in the pre-AI world, the that job would've been a chief of staff job of like Can you prep me these slides and all that? And now you do it yourself.Kyle [00:20:35]: I still, I still have a chief of staff. Because, the difference is it's sort of the discussion every time we have some sort of technology evolution is it's not that the jobs the roles don't all go away, they just change? And so yeah, I don't have someone spending all their time building out slides for me and presentations ‘cause I don't need that anymore. But now I need that person that is able to go and find all the different connections between humans in those discussions to help me find out, okay, I should be meeting with this group and this team, and they have an opportunity, and I'm going to be in San Francisco today, I'm going to be in Seattle tomorrow. Those sorts of human connection aspects are still incredibly valuable and has always been a big part of that chief of staff role. But now just like chiefs of staff are not opening up, letters to process, they're doing emails. What It's the same thing. And now they're, they're not building out as many of these presentations because they have the the ability to have a AI take it on for, and share that with me and great. Let's keep moving ‘cause it's allowing us to go faster and make better decisions more quickly.Swyx [00:21:45]: Awesome. Well, so we can dive into more sort of, Productivity insights as you go. I did want to do a little bit of a brief history of colleague and hub. Because, we started here. And then you also involved the NPM acquisition. I did, I do want to touch upon that. And then more recently, I just want to bring up to present day where we're having uptime issues Which transparently we've already Addressed publicly, but we'll, we'll discuss in the pod. Did I miss anything? Like what, any other major highlights? Obviously, it's, it's a lot of years to cover.A Brief History of GitHub: Webhooks, Actions, Acquisitions, and Platform EvolutionKyle [00:22:15]: No the I think one of one highlight was right before the acquisition closed in twenty eighteen, I got to launch the first version of ActionsSwyx [00:22:27]: OhKyle [00:22:27]: At GitHub Universe. So it was OSwyx [00:22:29]: They're that young?Kyle [00:22:30]: It was October of twenty eighteen, I think. Yeah. Yeah.Swyx [00:22:33]: Gee, Jesus.Kyle [00:22:34]: I got to I was the engineering leader on that project and got to launch that. And then, yeah, we did acquisitions of NPM you said, Semmle, Dependabot Pul Panda a whole bunch of things. That was a bigSwyx [00:22:47]: Pul Panda.Kyle [00:22:48]: Abi is doing well.Swyx [00:22:51]: DX. Holy crap.Kyle [00:22:52]: Did well on DX. I and like that was a that was the big shift, after the acquisition. I had to join the sort of business side.Swyx [00:23:00]: So I need to hit you on some of these things ‘cause you were there. Right? And how often do I get to talk to someone who was there? But yeah, Actions. Is that the number one source of security issues on GitHub?Kyle [00:23:11]: Oh, sh I think that the number one source of, security issues is probably like all, the literal code in everyone's like underlying repositories. I would say back further than that is, if you remember I had to show in this graph was this is, I'm, didn't say this before, this is ultimately webhooks.Swyx [00:23:30]: You yeah.Kyle [00:23:31]: Like circa whatever it was.Swyx [00:23:32]: It says Hookshot in there.Kyle [00:23:32]: I forget. Yeah. Yeah, Hookshot's in there. And so like back then, it says GitHub Services. Do you see, it says Hookshot FE for front end, and then it says GitHub Services. GitHub Services back in the old days, right? You we had a repository that was Ruby code, and you could write any Ruby code in there, and then we would execute that On your behalf As a service, and then that way if an if you were trying to integrate with something, it didn't we would run it for you.Swyx [00:23:57]: And of course no containers ‘causeKyle [00:23:58]: No, ‘cause it wasSwyx [00:23:59]: Well, no containersKyle [00:24:00]: Twenty fourteen. And so there was some isolation obviously, but it was mostly the separations on the server level. That's like an example as long as the very old version of Pages, which ran on its own containerization infrastructure, not on Actions.Swyx [00:24:15]: Which like all-time great product.Kyle [00:24:16]: Pages powers the internet at this point to some degree. Those were places where like clearly there were no like issues like to my knowledge. But it was those things where I'm looking at and going “Okay, well we can't be running arbitrary Ruby code,” like on everyone's behalf. Then containerizing all of that up intoUh into actions now where yeah the containerization, is r-really good. The pinning most folks aren't pinning it the like to a particularSwyx [00:24:48]: ImagesKyle [00:24:48]: Sha, et cetera like their workflows, and so that's a big that's a big place Of pain for folks if they're just doing similar to any dependency management, just V1 or newest or latest, I think. But, that journey from that day to “Okay, we're just going to run all this arbitrary code, and, it'll basically be okay,” to now, no, we have, really good containerization. We have a new, underlying, ag-agent, containerization, service. It's like we're using it under the hood. It's through Azure. They recently announced it. The Azure, Dev Compute, but it's, very fast, very fast compute to be able to, spin up your own cloud agents, or whatnot. We're using it under the hood for some parts of the new,Swyx [00:25:36]: Microsoft Dev Box?Kyle [00:25:37]: No. Dev Compute, yeah.Swyx [00:25:41]: Hmm. Not finding it just yet.Kyle [00:25:44]: Oh, it's, it's in there somewhere.Swyx [00:25:46]: All right. Well, we'll cut that out.Kyle [00:25:47]: Sorry. But with, Dev Compute, you can, run, really fast, spin up really, small VMs really quickly, so you're doing a tool callSwyx [00:25:58]: Same conceptKyle [00:25:58]: Just do it containerize exact-exactly. So we're using that so definitely moving that direction to protect us from every every piece of code that we're ultimately running.Swyx [00:26:07]: look, that grows into the full SDLC? Code hosting was just the start and and then it's grown beyond that. Let's talk about NPM may-maybe ‘cause I think that's also, a very major point in the industry. I do think, it was looking for a home. It was, kind of struggling as a business, right? I don't know, I don't know how you would characterize that whole acquisition and how itNPM, Package Security, and Keeping the Internet RunningKyle [00:26:33]: like when we were talking to the team, I think the big thing for the both of us was to find a way to keep NPM, which was basically powering the internet then and way more so now to some degree running. Keep it going keep continuing to scale. It was having scaling problems, if I recall, back at that time. They were doing some rewrites. ItSwyx [00:27:00]: that's cute compared to now.Kyle [00:27:01]: Well, that's the thing is like when I'm talking to folks now, there's there's so many more underlying uses of NPM than there were back when we had them join in with GitHub. But that was ultimately the goal. It was really okay, we used to have pages. We have, the world's code. Let's make sure that we can keep NPM running well for the world. And we put a bunch of time and investment into fixing some of the underlying backend, changes, some of which we talked about some of the manifest work, et cetera. And then now, really trying to bring the the security posture of NPM up to speed. But, it is a unique challenge in that every move that we make to make it more secure will break a lot of people. And security is paramount. And also, we take it very seriously. We're, the any time that we have a problem with GitHub or we make a change that makes us more secure but hurts, there's, a snow day for developers or a really bad fire that they have to go put out. And so we've, have changed the 2FA policies. We've changed the way the tokens work. When we find tokens that have been exposed or potentially, exposed, we invalidate them, andSwyx [00:28:22]: I love that feature in GitHub. Yeah, it's greatKyle [00:28:23]: That creates issues, but, the but that's the thing is we're trying to push the community, forward without necessarily, doing something that is going to break the contract that's been for 15 years or close to it or some amount of years on NPM.Slop Forks, Vendoring, and the Future of Open Source Supply ChainsSwyx [00:28:43]: I think the— So now we're talking about, open source and publishing. And I think there's something here with what people are calling slop forks, which, I think Malta from Vercel is doing. And, part of me thinks, well, the way to get past any vulnerabilities, we just, let's just get rid of the concept of NPM. And we only publish source code. And anytime you want to import it you have your coding agent look at it and then adapt whatever subset you're going to use into your vendor it. But, the AI vendor it. Is that realistic? I don't know. Is it— Will that solve all our security issues? I don't know.Kyle [00:29:24]: I don't think it'll solve I so Mitchell was just talking Mitchell Hashimoto Was just talking about this today, and I think that I-in some ways, it's all all things, old or new again? Yeah, absolutely vendoring everything. Like I do I do remember twenty thirteen, twenty fourteen.Swyx [00:29:42]: This is Yeah. Let's, we must return toKyle [00:29:43]: That's what is We were vendoring everything. We were having actual discussions around, or at least I remember we were “Should we take this full thing?” “Why is this so big? We only need this one file.” And so I do think there's something true there where having either taking only what you need or the dependencies just getting incredibly small over time, I think will help to some degree, but it's not going to solve the fundamental problem, I don't think, because the vulnerabilities in an agent looking at them, there's time and time again, there's a million different ways in which we can convince an agent that this thing is, secure or not and pull it in. Or we can do static code analysis or runtime testing to say whether the code works or not. That is, I think, the step that needs to continue to be, invested in. The question is just on, how much scope. Should it be this enormous project that I'm pulling down, or should it be this piece? Either most companies are running some amount of security checking on the on the packages that they're bringing in or vendoring. That I think won't change. That's like what advanced security does to some degree, Socket does some degree. Like everyone is doing a piece of that. How we each do that like especially when we're talking to enterprise customers, is just like very different. No there's no one wants one single way to do it. And I think that's always been GitHub's, unique position in the world. I talk a lot to maintainers, I talk a lot to folks about this. It's we're— we rarely start like a process and a practice and like push it onto the community. We usually wait for the sort of like RFC process socially or literally, everyone agreeing, and then we'll cement something in. Because otherwise we'reMaintainers, RFCs, Vouching, and the Social Layer of TrustSwyx [00:31:35]: That fits your role in the ecosystem, yeahKyle [00:31:36]: We're GitHub. Yeah, we don't want to shape the whole thing. We want it to be figured out. But like how do you balance that like sort of Role in the industry to keep everything as secure as is possible and make sure that you're you're not going to be compromised as a human, ‘cause that's usually how it all happens. And Not not create a process or lock us into a flow that you're not going to or like Mitchell's not going to or other open source projects aren't going to like. That's always been a tricky balance for us, and I think that's something that we haven't talked about enough is we're not going to be able to fix everything for everyone in a way that everyone is going to like. So tell, help us, tell us what is working. When Mitchell was talking about, the Upvote, the upSwyx [00:32:22]: I was going to bring up his thing. Yeah.Kyle [00:32:23]: I forget what it Yeah. When he's talking to us, I was chatting with him and talking to him about this and I put it on Twitter and we talked to, also over DM, was “We're going to keep working.” but I think the important thing is I do actually want to hear what isn't working for you. And as, be as specific and clear for your project as is possible. And to every piece of credit over the many years that we've known each other through the industry, he's always done that and I appreciate that ‘cause there are places that we need to fix up, and we hear from him, and we'll fix up just like we do all other kinds of maintainers. But that that process between making those types of improvements and being more secure and like creating, I forget what he calls it's not the proof process, not the claims process. Do what I'm talking about? He has that he his projects have a way for you to kind of like,Swyx [00:33:13]: VouchKyle [00:33:13]: Vouch. Thank you. Yeah. He has like the vouch system for saying, “Hey, you should accept my PRs.” That's beenSwyx [00:33:20]: I just built this into GitHub. I don't know.Kyle [00:33:22]: Well, see, but that's the thing is that you say that and like he and his community really likes this and then I'll go talk to other maintainers and other maintainers, globally, and they're “No, this doesn't work for me.” And that is the tension, but also the kind of beauty of GitHub, depending on which way you look at it is we want to help maintainers, so we create all these tools to let you have more control over how much you take in from AI and PRs. But you can also use this. What You can go use this project, and if it takes off and becomes the kind of mostly standard, then yeah, we probably wouldn't enforce it but we would add it in because that's the flow that we tend to do?Swyx [00:34:02]: I hear a lot of people don't know the history of the pull request. And like like that's how, that's something that GitHub standardized basically.Kyle [00:34:08]: Yeah. It was a very messy process Like beforehand, and now the we have the benefit of it being the process? And now we have to go and Figure out the next best process or what adaptations change, or what does a pull request look like when eighty percent of your PRs are just coming from your agents and not From other devs?Swyx [00:34:31]: Do you like the prompt request idea from Peter?Kyle [00:34:34]: like I think that for each like each idea I think has its merits. I'm not, I'm not avoiding saying anything good or bad, but I feel like I've seen a version of we have that we have entire Thomas' store. Take all the assets of what you've built and put that in. I think that's got great ideas. There's all these various permutations of the PR flow, but I think the reason why there's not a single answer is ultimately we're trying to codify trust. We're trying to say “Okay, if Sean reviews this I'm going to trust it because you're Sean or you're the senior dev or you're the whatever.” And right now, when we are working in a flow where an agent writes code and another agent reviews code and then Kyle goes and looks at it the trust is kind of diffuse. And most of the tools that we're talking about are talking more about verification flows. We have more assets to look at, so I can probably say whether this is a good PR or not. But that still doesn't solve, I think, the human problem of I'm looking at a PR and I want to know if I can trust it. And we're still, we still tend to use human signals for that? Mitchell approving it or Kyle approving it or whatever. And so I think that's, I think that's why most of these options haven't really solved it is because, it's a social problem ultimately. It's a it's a human problem to review it and agree. Or you fully trust the tool and you're imbuing that tool with full trust Which I think in some cases that absolutely exists.AI-Generated PRs, Trust, and the Waymo AnalogySwyx [00:36:08]: And so like in the same way that there will be a tipping point in society when we don't allow humans to drive anymore Because machines are measurably better than Than humans. I'm looking for that tipping point, right? Like Mythos is ridiculously expensive. Someday we'll have Mythos on a desktop. I don't know. Will, does that change the equation?Kyle [00:36:30]: I think it's more I took a Waymo here, and I was on my phone and not looking around at all. There are other, self-driving, vehicles that I would not trust while, staring at the road. And I think that trust is something that isSwyx [00:36:48]: Is this a Zoox thing? What is itKyle [00:36:50]: I think that is both. I think that is both. LikeSwyx [00:36:53]: There's Zoox in this robo taxi. That's it. It'sKyle [00:36:56]: Well, depending on what level Of self-driving. But, my point is sort of that I think part of that is I strongly believe that's, a mixture of verifiable proof. Like how many accidents, how much data, and so on, and the human aspect of how I feel when I'm in this car, what it tells me, et cetera. And so that's why I think some of the like Some of these some of our AI tools tend to, imbue me with more of that feeling of trust, even if the data says this is 100% accurate. I feel like it takes more time for us to go, “Should I trust this or not?” And that's in the soft sense of, startups with high agency, weekend projects, and open source. And then there's enterprises and regulated industries and everything else, and that is an even harder problem to go solve because even when it is fully verified, not only do you have to have trust from the humans on the team, you probably have to have trust from multinational,Swyx [00:37:55]: Oh my GodKyle [00:37:55]: Multi governments around the world and regulating agencies. And so that's where I feel like until we tip over to your point on the sort of like human EQ side of it. I feel okay this feels okay I've been proven enough. Then the ball will start to roll a lot faster, where we'll end up getting to the “Okay, we can trust this,” and feel good about it in the Most difficult of cases.Reputation, Sponsors, Stars, and Bot Activity on GitHubSwyx [00:38:18]: If human trust is the thing that matters, I feel like GitHub as the developer social network could maybe do more there. Like vouchers are one system But, we have star counts, and then we have Contributor rights, and that's it. And I feel like there should be more in that space. I don't know if there's any other design decisions there.Kyle [00:38:37]: I think that one of the places that we don't really expose right now in this sort of way is, some degree of like hard trust and support, which would like for me is like sponsors is a good example of that.Swyx [00:38:49]: Ah.Kyle [00:38:49]: It like costs you something. To prove that I believe in your project and I trust you To some degree or I want to support you at the very least.Swyx [00:38:56]: Solve payments for open source. Why not?Kyle [00:38:58]: I think that I think that like as we keep moving forward, right, there's more and more projects where I'm, adding more and more dollars into sponsors personally because I want to like support them, but I also like know of I've probably never met them in person, but, I know of enough of their work that I want to support them. I think the thing that I don't love about stars or commit counts or anything else is ultimately, even with all of the various, abuse and de-spamming and deduplication work that we do or anti-abuse work that we do, these are all, not active social signals. They're passive ones that are ultimately gamifiable. And you may trust me, but another open source maintainer may not. And on what heuristic should you be, trusting me? That I think, is kind of where some of our thinking is right now. What signal from me is most important to you? You— If you can define that potentially, honestly in an agentic workflow that's what we see some of these open source projects do, where you have GitHub actions, and then you have like an agentic workflow that's calling AI, and you're setting these rules. Like if Kyle has submitted and gotten accepted PRs across any given project and has a social handle tied to his account in GitHub, and that social account's older than a certain amount. Really complex measures that matter to you ‘cause most open source projects have that heuristic built into their heads, if not written down in the contributing guidelines. You could take that and then go apply that and then just say, “Oh, we're not going to accept this PR.” Building something that is, I think, malleable to everyone's needs, is a little bit better, rather than going “Hmm, this account's too young.” Because what happens? The attackers just go and go and create a multitude of accounts, and they wait Until it ages up. Needs to have a certain amount of stars. That's how star inflation happens. Need to have a certain amount of reposSwyx [00:40:46]: Oh my God. YeahKyle [00:40:47]: With PRs. They all just create repos and submit PRs to each other, and then they come in and do something nefarious. And so, it's hard. It's hard to find the measure. So I think we're, we're looking more at how can we provide you tools so you can kind of choose what's best for you. And of course, we'll give you some standards. But the trust vector, gets down to I don't know, some version of like human digital ID like everyone's been talking about. Like how do I prove that it's meSwyx [00:41:13]: Give me your eyeballsKyle [00:41:14]: On the internet. Give me your eyeballs. Exactly.Swyx [00:41:18]: The I got to keep moving on Topics, but obviously I can go all day on this stuff because, I've been involved in GitHub and open source My entire professional career. Stars. Very superficial. Everyone knows it. But I think time to one hundred thousand stars is the fastest I've ever seen. Like people just reached that in I don't know, months. And then like at the same time I don't trust it right? Like how many of these are real or bot or like whatever. I don't know how to ask this but like what can we do about it? LikeKyle [00:41:49]: JustSwyx [00:41:49]: Is stars broken? Is stars fine?Kyle [00:41:51]: I think that there's kind of two, there's like two pieces. Obviously we're constantly like trying to find ways in which like your users are producing spam, which would, I would include like be like only doing star gamification. When we find them, we pluck ‘em out and we,Swyx [00:42:08]: But it's like a Whac-A-MoleKyle [00:42:10]: It's a hundred percent like a Whac-A-MoleSwyx [00:42:11]: There's no wayKyle [00:42:11]: Now, powered by AI to be helpful. But I think more so what I'm seeing is, a lot of the like fastest time to X tends to be because we're now inviting so many more people into like software development on GitHub That like the zeitgeist is just swarming? And it'sSwyx [00:42:32]: It's not just developers anymoreKyle [00:42:33]: And it's not you and I. Like like however you want to say like what a developer is it's not just folks who have been coding for a very long time. It's folks that have maybe started coding or only joined in since the AI era. And nowSwyx [00:42:44]: what's the latest Octoverse number? I know eighty million was my lastRem- member that a number of developers on GitHubKyle [00:42:50]: Oh, we're over 200 million now.Swyx [00:42:53]: Okay. Well, so you see?Kyle [00:42:55]: Like over 200 million developers now.Swyx [00:42:56]: But it's not developers, right? It's, it's people with a GitHub account.What Counts as a Developer in the AI Era?Kyle [00:43:00]: So, so this is, this is the biggest debate that I would say, everyone loves to have at GitHub at this point. From my perspective, right, I think that there's, there's clearly a difference between, professional enterprise developer and then developers. But I think that I think that the idea that we should be I don't know, splitting hairs or segmenting developers in the early era of software development is, not worth our not worth the time. SoSwyx [00:43:29]: When you get into gatekeepingKyle [00:43:31]: 100%Swyx [00:43:31]: What is a developer?Kyle [00:43:31]: 100%. ‘Cause I wasn't a developer when I started writing code? I was going toSwyx [00:43:36]: Oh, no. I made— I cloned a thing, seven years before I learned to code. And then I and then I wrote about my learning to code journey, and people Just called me a fraud ‘cause I had a GitHub account. And I'm “Well, no, I just use GitHub, but I don't know-” “I didn't know what I was doing.”Kyle [00:43:49]: I I remember that. I remember those sets of posts, and like that's, that's b******t. So I fight very clearly on the line of, if you create code, if you have an idea and you create it into some way of, I'm, I'm going to run it and use the app right now, you may still use AI in that moment, but that's okay. At some point you're going to do the next thing. You're going to create a big— You're going to have to learn about this database. You're going to fix a bug, whatever. We're all on some same journey, and those people are also hearing about the great new agent skill package or a new CLI tool or a new whatever. And those projects are going up because you want to be a part of this moment, just like I wanted to be a part of the Ruby community when Ruby was popping off when I started becoming a developer, and now I can just click the star button. And so I think that yes, there's clearly some amount of like spamming and game gamification that we're working against, but I really think we're just seeing this whole new cohort of folks that are moving from technology to technology because they're not working on a 20-year-old software application. They're working on a side app that they built on the weekend for their friends or for their new idea or whatever. And that's how you see these enormous charts going up and to the right with With stars.Swyx [00:44:59]: I think something that's remarkable is the persistence or, that GitHub extends to those folks. Usually when I see platforms go into a new audience, they usually have to, have like a second platform with a different name that wraps the main platform. But somehow GitHub has been able to sort of persist and extend, and it's friendly and whatever? So it's, it's nice.Spark, Low-Code, and Always Showing the CodeKyle [00:45:19]: I that's partially why I think as we've tried to move into I don't know, more like low-code-y things. We so we started working on Spark as like a way to, build an app and run it. I think that the reality is that we anytime we try to, kind of put even a veneer on top of it without when we put a veneer on top of something, we still always show you the code. That's kind of like a tenant. We're never going to, hide the code from you ever, because whatSwyx [00:45:52]: Why would you?Kyle [00:45:52]: That's, yeah, that's the whole point? However, I think that what we learned with things like Spark is that really the value of Spark for most devs is, easy runtime. And you may have a runtime or a host that you're going to use for that or you just build something and run it but, the package of making that even more simple isn't really needed for folks that are trying to build software and not just trying to build, an app, which is, slightly different, a slightly different goal. So I want to get you in, I want to get you comfortable. I think the best thing for me as, someone that did not traditionally come into software dev way back, I want anyone to be able to breach that chasm and not be in the I don't know, I feel like we're, we're still in an era of, STEM. I've got a 12-year-old and an eight-year-old, and it's “We got to get ‘em into STEM,”? Over and over. And I like I do, I do the things that good parents do. I was “Oh, you want to do coding?” “Yes, I want to do coding.” Do coding classes. But now they're just not afraid of doing software. And that's, I think, the thing that's honestly kept me at GitHub for so long. Anyone should be able to go and build a thing, just like I can go change a light switch in my house. I'm not going to go into the breaker box ‘cause I'll probably kill myself? But, I can go change that light switch. Everyone should be able to go and say, “This fricking app doesn't do what I want. I want it to work like this.” And that I think, is what's kind of kept us all connected with GitHub through the years and some and during the easiest of times or in the hard times because of that opportunity of, we're the home for all developers, and we want everyone to be able to have that feeling that we've had of, had an idea, I created it and holy s**t here it is.Swyx [00:47:37]: Here it is. All right, I'm going to try to do more spicy questions.GitHub's Hardest Scaling Moment: Growth, Agents, and UptimeKyle [00:47:42]: Great.Swyx [00:47:42]: Is it an easy time now or a hard time?Kyle [00:47:45]: Oh at GitHub? It's a hard time. Like, it's a hard time and also, I was just with my team and I said, “This is also, the best and most exciting time that I think I can remember at GitHub.” BecauseSwyx [00:47:57]: Best of times, worst of times. It's never oneKyle [00:47:59]: ‘cause we've we were talking about Octoverse reports and, usually we do an Octoverse report once a year, and we look at the numbers, and we say, “Oh my goodness.” I was at Universe in October saying, “This was the fastest year of growth that we've ever had,” right? And now we're doing more in a month than we did in a year last year.Swyx [00:48:20]: You're talking about PRs.Kyle [00:48:21]: Commits.Swyx [00:48:21]: Commits, yeah.Kyle [00:48:22]: PRs. Kind of like you name it by roughly every measure that we're looking at, there's some amount of sort of growth that is much bigger, and that is breaking our system in new ways, not old ways. Like webhooks were always notoriously, unreliable over the years?Swyx [00:48:38]: Whose fault is that?Kyle [00:48:39]: not anymore mine, but for a period of time, I'm sure you could pull up a tweet that was “It was me. I'm sorry.” but, now, that got rewritten at a scale level that is still working and is not having problems today. Now what we're finding isn't just the isn't the-The simple stuff that folks are on the sometimes on Twitter or on the internet are “Hey, why is this like this?” Sure. There's absolutely silly problems that we shouldn't exist. But now we're talking about, unique, novel permission problems that happen only at a scale across all different objects or whatever, that now we have to go rewrite this underlying system. And so it's, there are problems that yeah, caught us off guard, which I think I said. Like the growth is astronomical, but also we're making such material progress in that I'm excited once we're once we've kind of like reimagined the underlying foundation layer, or pieces of it at least, what's going to be possible when it's not just all of us and all the new people that are being developers and all of their agents and all the tools like working together. Because that'll still happen in that in that GitHub tool, that GitHub community. But it's a it's a hard day anytime we can't give you what you're looking for. We have the same problem internally. We operate through github. Com. Of course, we have backups when things go down and whatnot for our own operations but we feel it too. If it's not working it's not working for us, and that's kind of like the promise of dogfooding for GitHub. It's always been true. We're using the same tool you're using. We're not using a super secret version. We and so we also need it to be great for us for our customers of course for open source. And now an exponential growth of agents, Doing it too.Swyx [00:50:32]: I wanted to load for audio listeners who maybe haven't seen your tweets, whatever. So one billion commits in twenty-five. Now it's two hundred and seventy-five million per week on pace for fourteen billion this year, if growth remains linear. Is that still the pace? I don't know. It's been aKyle [00:50:48]: it's, it's speedingSwyx [00:50:50]: Roughly.Kyle [00:50:50]: It's still speeding up.Swyx [00:50:51]: It's, it's April, so yeah.Kyle [00:50:51]: Exactly. This was in April.Swyx [00:50:53]: All right. So basically you have fourteen x growth, right? Year on year on year. And I think that's a scaling issue. I think, I'm going to like try to really steel man this thing. People have experienced fourteen x growth. They haven't had your downtime. And that's like— C-can we go dig into that? Why? Like what's the— what broke? What are we doing to fix it? Like just anything for the community to reassure them.Why GitHub Reliability Is Breaking in New WaysKyle [00:51:18]: so there's a Like I was saying, there's a couple different places that we've seen the growth issues. Some of the growth issues, which is why we're t— I was talking about pushing hard on more CPUs is in actions in particular. More tools, more agents, more PRs mean more builds, more builds mean more CPUs. And so we are expanding through not just our data center, but obviously we were talking about moving to Azure and moving to, adding an additional cloud compute because we simply need more CPUs. Not as much GPUs. We definitely need GPUs too, but now CPUs are becoming a factor.Swyx [00:51:53]: It's very CPU heavy.Kyle [00:51:54]: Underneath the hood when it comes to some of the underlying services, we've been breaking up over the years our database infrastructure, so that way we have, more cognitive separation between our the various services. The place that we continue to have pain is in, permissioning. And so right now m-many of our permissioning layers sit into a database that we like internally call MySQL One, and old Hubbers will know what I'm talking about. And so we've been pulling things out of MySQL One for many years, because like and we use we use Vitess and we use other technologies to shard and we do it as one bigSwyx [00:52:31]: Famous thing, PlanetScale was born from this andKyle [00:52:32]: A hundred percent. Sam Old Hubber and friend. And so finding these opportunities to like break this out and then do that globally. The other thing that I think is interesting and both a unique opportunity and tricky is we also run everything I just talked about in a black box container with GitHub Enterprise Server for people that work on-prem. So we take everything I just said, and we also do it on-prem, and we also do all of that and we do it in a data residence setup for customers that need to have their data in a single location. Each of these has the unique characteristic around how we're sort of storing that data in MySQL or in a permissioning setup. That's where some of these outages have oc-occurred, where you're seeing it more like across the board rather than just like the one pieceSwyx [00:53:17]: Filling the databaseKyle [00:53:17]: Isn't quite working. Exactly. And so part of it is that. I think there's been some other places where agents are much more or more projects appear to be moving towards monorepo versus we were going the other direction for many years in the industry. Repos were smaller, but there were more of them, and now we're seeing the opposite. Repos are bigger, and there's, not fewer of them per se ‘cause there's new growth, but, we're just seeing many more big repos. Big repos, big monorepos have always had, a unique performance problem. Because each one, is slightly different if, particularly if the underlying blobs are incredibly big Inside the repos. And so we've done a ton of work that you pro— like most people haven't probably experienced, unless you're in this case of the monorepo. But that Git, infrastructure layer improvement does help the overall, system because, many of the improvements that make monorepos work better make all repo infrastructure work better. And so, I could kind of keep going down the line where it's another thing where we're moving out of, We're changing how we do j I'll just say job queuing for lack of a better, explanation changing the underlying technologies there.Swyx [00:54:32]: I spent two years being a job queuing guy, so.Kyle [00:54:34]: And so it's kind of a little bit of a little bit of piece by piece, and it's mostly because as we were— as it was built, we built everything in a way that assumed, I guess in some ways that the size of the pipe of work was going to remain the same. There's just going to be more people coming through each of those pipes. But instead now in places whereA git push was, generally a certain size for example, is now, no longer true.Swyx [00:55:03]: Oh, yeah.Kyle [00:55:03]: OrSwyx [00:55:05]: I push a thousandKyle [00:55:06]: On the average. 100%Swyx [00:55:06]: A thousand line commits like dailyKyle [00:55:07]: Same thing with PRs. Like PRs same thing. And like we've talked about optimizing that and making changes where, and there were technology choices that did not work there? And it got slow, and it didn't It was not fast. It did not do what the users wanted. And so we've been reeling that all out and going “Okay, that's just not right. Let's stop putting good money after bad and do it the do it the right way or the right way now.” So there's It's a it's a lot of things, not quite when I've experienced scale at GitHub historically, it's almost always two options that we've used. We go vertical scaling, particularly with databases, right? And we go horizontal scaling. Oh, we just have more people using this service. Great. We're going to add more servers, and we rack them in our data center, or we use it in a cloud. And now we're sort of in a like diagonal, where like vertical doesn't really work anymore. Horizontal isn't work either because we're all We all have some CPU or GPU constraints in the world now, and now we have to go in and like crack open services that have been running for 10 or 15 years and go, “Okay, the rules of this service have legitimately changed, and now we have to rewrite them.” None of this is an excuse. This is like we're We have to do the work. We have to make it better.Swyx [00:56:22]: actually as an infra guy, I'm “This is like one of the most fascinating scaling challenges I've ever seen.”Kyle [00:56:26]: That's that's, that's the thing that's the thing that it's hard for Like when we weren't talking about it publicly, and I was like I came out, and I was “Hey, I just want to explain what's going on.” Part of it comes from a very old GitHub ethos, which is it's our it's our uptime. It's down. W What I know you're a developer, so you're, you're inclined to want to understand more what's going on. But at the same time us going “Hey, this service didn't, perform the way we expected, and now we have to go change it,” we weren't We're not trying to hide anything from you i

Four years?! Somehow we've been talking about Tolkien long enough to celebrate another podcast birthday, and this year we're marking the occasion with a special bonus episode! Join us as we share our first-ever reactions to The Lord of the Rings: The War of the Rohirrim—the moments we loved, the things that surprised us, and a few thoughts that may or may not change after future rewatches. Fair warning: we intentionally recorded before diving into timelines, lore deep-dives, or research, so these are our completely unfiltered first impressions. Then the celebration continues with a Tolkien-themed game of Jeopardy! Play along with us and see if you can beat our scores. Bonus points if you immediately knew the answer to Abi's tricky question that we absolutely could not remember in the moment. Thank you for spending the last four years journeying through Middle-earth with us—we couldn't have done it without you!P.S. Ashley would like the record to show that she is aware that Thengel was Théoden's father, not his grandfather. (He was Éowyn's grandfather, which is where the wires got crossed.) Sorry! Nobody's perfect.https://linktr.ee/sistersoftheshirepodcasthttps://www.instagram.com/sistersoftheshirepodcast/https://www.patreon.com/sistersoftheshirepodcasthttps://open.spotify.com/show/1HIhmdeX6761vi7RyOjl8f?si=_qwdGdP7SbmAP2RWlji54w

Hannah Mooney welcomes return guests Abi and Jared from Our Theatre Company's Educating Rita back to That's the Ticket.

Latvijas Transportlīdzekļu apdrošinātāju biroja veiktajā aptaujā atklājies, ka gandrīz puse autovadītāju nezina, kā pareizi rīkoties pēc ceļu satiksmes negadījuma. Kāda būtu pareiza rīcība pēc avārijas, skaidrojam raidījumā Kā labāk dzīvot. Plašāk stāsta Latvijas Transportlīdzekļu apdrošinātāju biroja IT daļas vadītājs Agris Daukste un satiksmes eksperts Oskars Irbītis. Oskars Irbītis norāda, ka nokļūšana negadījumā, par laimi, nav ikdienišķs pasākums cilvēkiem, ko papildina apjums, stress. Tāpēc saprast, kā pareizi noformēt saskaņoto paziņojumu par negadījumu bieži vien ir diezgan lielas problēmas.  "Vislielākās grūtības cilvēkiem sagādā, kad ir jāaizpilda saskaņotais paziņojums. Mani novērojumi, izskatot arī sūdzības, ka cilvēki jauc elementārām lietas un jēdzienus, piemēram, kas īsti ir apdzīšana un kas ir iebraukšana blakus joslā. Liela nesaprašana ir par dažādu manevru atšifrēšanu. Ja saskaņotajā paziņojumā kāds ir izdomājis apzīmēt vairāk par trīs ķeksīšiem, tas nozīmē, ka kaut kas nav saprasts," norāda Oskars Irbītis. "99% gadījumu būs jāatzīmē tikai viens ķeksītis, viena situācija, ko atlasām no attiecīgā saraksta. Ļoti daudzos gadījumos nevajadzēs atķeksēt nevienu ķeksīti cilvēkam, kurš vienkārši brauc taisni. Dažas elementāras lietas, kas sagādā milzīgas grūtības. Tāpēc mans uzskats - par to ir jārunā, jārunā, jārunā un vēlreiz jārunā," atzīst Oskars Irbītis. Abi viesi mudina nepieciešamības gadījumā lejplādēt Latvijas Transportlīdzekļu apdrošinātāju biroja lietotni, kur pieejams saskaņotais paziņojums, bet tajā pašā laikā nebūtu slikti, ja mašīnā būtu tas papīra formātā, jo negadījumi mēdz notikt arī vietās, kur nav sevišķi labs interneta pārklājums. Ja vien negadījumā nav cietušie, viesi noteikti mudina nelaimes gadījumā iekļuvušajiem vienoties, jo gaidīt jau tā noslogoto policiju būs ilgi un tas raisīs papildus daudz nepatīkamu emociju.

In this episode of TAB Storytellers, Jen and Abi sit down with longtime TAB educator Tom Burkle and preservice art educator Liam Schneider for a beautiful full-circle conversation about teaching, mentorship, student agency, and what it means to grow into TAB over time. Liam was once Tom's elementary art student, later became Abi's student at the University of Northern Colorado, and recently returned to Tom's classroom as a student teacher. Together, they reflect on Tom's early move toward choice, the small classroom moments that can shift an educator's whole philosophy, and the power of seeing students, and future teachers, as capable artists and thinkers.The conversation moves through TAB history in Colorado, curriculum design, artist statements, classroom management, confidence-building, and the real planning and organization behind a choice-based studio. Tom and Liam also talk honestly about behavior, routines, individualized consequences, and the importance of reflective mentorship in helping new teachers stay grounded, curious, and willing to try again.Bonus update: Since this conversation was recorded in March (yes Abi was busy and yes she got behind and is playing catch up), Liam graduated and has found a job! He will be teaching high school pottery next year in the same town near Tom, and they are both excited for this next chapter. Here is a pic of Abi and Liam from the right before Liam graduated.ResourcesTeaching for Artistic Behavior / TAB: Official TAB website and starting place for learning more about TAB pedagogy, practice, professional development, and community.  https://teachingforartisticbehavior.orgTAB Community on Mighty Networks: Online community for TAB educators to connect, ask questions, and share resources. https://teaching-for-artistic-behavior-inc.mn.co/Fred Tjardes School of Innovation, Greeley, Colorado: Mentioned by Liam and Abi as a powerful example of inquiry, student agency, theme-based learning, and choice-centered practice beyond the art room.  https://ftsoi.greeleyschools.org/Understanding by Design by Grant Wiggins and Jay McTighe: Tom mentions this book as part of his early thinking around curriculum, assessment, and how students demonstrate higher-level thinking.  https://www.ascd.org/books/understanding-by-design-expanded-2nd-editionUnderstanding by Design Framework White Paper: A helpful overview of the UbD framework for curriculum planning and assessment. https://files.ascd.org/staticfiles/ascd/pdf/siteASCD/publications/UbD_WhitePaper0312.pdfOlivia Gude's “Postmodern Principles: In Search of a 21st Century Art Education”:  Liam references Connie Stewart introducing him to postmodern principles, which became a game changer in his understanding of choice, meaning-making, and contemporary art education.  https://www.tandfonline.com/doi/abs/10.1080/00043125.2004.11653528University of Northern Colorado:  Referenced as part of Liam's preservice teacher education journey and Abi's teaching context. https://www.unco.edu/pva/art-design/areas/art-education/TAB Colorado:  Mentioned in the conversation as part of the broader Colorado TAB story and community.  https://coloradotabinc.orgMassArt TAB Institute: Referenced in the conversation as part of the broader timeline of TAB professional learning and community-building.  https://pce.massart.edu/programs/tabTeaching for Artistic Behavior: A Definition and Historiography by Abi Paytoe Gbayee: Abi mentions her dissertation and Tom's connection to her research on continuums of choice. https://www.proquest.com/dissertations-theses/teaching-artistic-behavior-definition/docview/2817860186/se-2 Here is a lightly edited transcript of this episode. We recognize that there are probably errors and grammatical issues. If anyone with the time or inclination to edit this wants to do so, please email us at storytellers@teachingforartisticbehaviors.org⁠.

What could be better than a tiny plant with an outsized impact on the world around it? Hornleaf riverweed AKA Podostemum ceratophyllum is one such plant. This tiny aquatic plant has so many mysterious surrounding it but what we do know is that it is foundational to the aquatic ecosystems in which it is found. Join me and Dr. James Wood as we take a deep dive on this unique aquatic plant and learn what you can do to help us understand and conserve it a little bit better. This episode was produced in part by Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie. See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Welcome to the emDOCs.net podcast! Join us as we review our high-yield posts from our website emDOCs.net.Today on the emDOCs cast with Brit Long (@long_brit), we cover how to evaluate and manage acute limb ischemia. To continue to make this a worthwhile podcast for you to listen to, we appreciate any feedback and comments you may have for us. Please let us know!Subscribe to the podcast on one of the many platforms below:Apple iTunesSpotifyGoogle Play Send us Fan Mail

Toasters we are BACK with another romp through someone's online shopping history. It's really the only way to tell a life story, you know.

Our good friend Abi joins us to discuss the new EHRC guidance and the plan to spend billions of dollars on bathrooms. But first… we look to the skies. The truth is out there. In Doncaster. Get more TF episodes each week by subscribing to our Patreon here! RILEY ALERT Check out No Gods, No Mayors here! HUSSEIN ALERT Check out 10k Posts here! MILO ALERT Check out Milo's tour dates here: https://www.miloedwards.co.uk/liveshows NATE ALERT Lions Led By Donkeys will be performing live in London on 29th May and you can get tickets here! Also, Nate's band Second Homes has just released their debut album, which includes the song used in this episode's outro, and you can stream it for free here!

Kung Fu bedeutet harte Arbeit über einen langen Zeitraum. Es muss nicht unbedingt mit sportlicher Höchstleistung und Schmerzen verbunden sein, auch geistige Arbeit zählt. "Es ist die Art, wie man bewusst durchs Leben geht", so erklärt Sacha Wenk die Philosophie des Shaolin Kung Fu. Er hat als Kind zum ersten Mal eine Show von Gleichaltrigen gesehen und war sofort fasziniert. Als Teenager mit Schulschwierigkeiten hatte er in München kurz vor dem Abi keine Lust mehr und ging nach China, um seinen Traum zu leben. Meine Eltern, sagt er heute, haben mir auf meinem Weg immer vertraut. 

Seed storage is one of the most important tools in plant conservation, but did you know you can also store pollen? We still have a lot to learn about storing both pollen and seeds for most species, and people like Dr. Dustin Wolkis of the Center for Plant Conservation are hard at work doing just that. Join us for an interesting look at what he and his colleagues are doing to prevent plant extinction. This episode was produced in part by Elise, Maggie, Mamie, A.J., Dallas, Channele, KC, Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

There is a gap between where your life is and where you thought it would be. That gap has a name. It is grief. A kind of hidden, invisible grief. And most of us are walking around carrying it without ever calling it that, because we have been taught that grief belongs only to those who have lost someone to death. The rest of us are supposed to just get on with it.Dr. Lucy Hone is an adjunct senior fellow at the University of Canterbury, a leading resilience researcher, and one of the world's most trusted voices on loss and grief. Her TED talk on resilience has been viewed more than nine million times. She is also a mother who lost her 12-year-old daughter, Abi, in a car accident in 2014, and who has spent the decade since weaving her scientific training and her lived experience into tools that actually work. Her new book is How Will I Ever Get Through This?In this conversation, we go to the places most conversations about grief are afraid to go.What you will explore:Why grief is not an emotion but a full-body experience that explains the exhaustion, brain fog, and 3 am waking you may have been blaming on other thingsWhat "living losses" are, the griefs that come without a funeral, and why they may be driving far more of our suffering than we recognizeThe difference between acceptance and coming to terms with, and why one word changes everything about how you move through lossWhat the research actually shows about post-traumatic growth, including the statistic that will surprise you about how common it actually isWhy resilience is not about bouncing back, and what Dr. Hone means when she says you do not bounce back from anything that mattersThe one question she asks herself in the hardest moments, and why it is a more useful starting point than any techniqueIf you have ever minimized something you were going through because it did not feel like it counted as real loss, this conversation is for you.You can find Lucy at: Website | Instagram | Episode TranscriptNext week, I am going solo to talk about something that I think a lot of us are quietly carrying, the conversations we know we need to have with the people who matter most to us, and why we keep finding reasons not to have them. The research turns out to be really clear on this: we consistently overestimate how bad it will be and underestimate how much it costs us to stay silent. Be sure to follow Good Life Project wherever you get your podcasts so you don't miss any upcoming episodes!Check out our offerings & partners: Join My New Writing Project: Awake at the WheelVisit Our Sponsor Page For Great Resources & Discount Codes Hosted on Acast. See acast.com/privacy for more information.

Jackie (ginecólogo) y Abi (matrona) se conocieron trabajando en un hospital. Con el tiempo formaron una familia y pensaron que había una manera diferente de hacer medicina, con un servicio al cliente cinco estrellas.En 2016 lanzaron Bmum, centro médico especializado en la mujer y el niño. En este episodio, Jackie nos cuenta cómo consiguieron con mucho esfuerzo y dedicación, sobrevivir a los 3 primeros años, con dificultades para llegar a fin de mes y cómo con su buen hacer, fueron creciendo paso a paso hasta convertirse hoy en un centro de referencia a nivel nacional, donde dan empleo a más de 110 profesionales.

Ārēji spoža, bet saturiski patukša – tā daudzi komentētāji vērtē Savienoto Valstu prezidenta Donalda Trampa vizīti Ķīnā. Naktī no 16. uz 17. maiju Krievija piedzīvoja vēsturiski lielāko ukraiņu spēku gaisa triecienu. ASV kara sekretārs Pīts Hegsets apturējis paredzēto 4000 amerikāņu karavīru nosūtīšanu iepriekš plānotā misijā uz Poliju. Aktualitātes analizē atvaļinātais vēstnieks Gints Jegermanis un politologs Andis Kudors. Maskava dūmos Naktī no 13. uz 14. maiju agresorvalsts Krievija vērsa pret Ukrainu kārtējo slepkavniecisko lidrobotu un raķešu triecienu. Šīs reizes asiņainā bilance ir 27 nogalināti mierīgie iedzīvotāji, tai skaitā 24 vienā Kijivas adresē, kur raķete ietriecās daudzstāvu dzīvojamajā mājā. Tāpat ir desmiti ievainoto, bojāta energoapgādes un transporta infrastruktūra. Tā Kremļa diktators atmaksā Ukrainai par pazemojumu, kuru viņam nācās piedzīvot 9. maijā, kad iespēja netraucēti rīkot parādi Sarkanajā laukumā tika izkaulēta ar Donalda Trampa starpniecību. Taču tie laiki, kad Kremlis varēja nesodīti terorizēt Ukrainu, ir pagātnē. Avoti min, ka naktī no 16. uz 17. maiju Krievija piedzīvoja vēsturiski lielāko ukraiņu spēku gaisa triecienu. Sevišķi iezīmīgi ir tas, ka viens no galvenajiem mērķiem bija Maskava un tās apkārtne, kuru Krievijas pretgaisa aizsardzība sargā sevišķi centīgi ne vien īpašajos datumos, bet arī ikdienā. Kā apgalvo Maskavas apgabala vadība, apmēram 120 lidroboti esot notriekti, taču pietiekami daudzi tomēr tika līdz mērķim. Postījumi nodarīti stratēģiski nozīmīgajām mikroelektronikas ražotnēm Zeļenogradas pilsētā, raķešu ražošanā iesaistītajai rūpnīcai „Raduga” Dubnā, aizdedzināta Maskavas Naftas pārstrādes rūpnīca Kopotņā un degvielas rezervuāri Durnovo pilsētā. Tāpat ukraiņu lidrobotu trieciens izraisījis plašu ugunsgrēku vienā no lielākajām Krievijas naftas pārstrādes rūpnīcām Rjazaņā. Vairākos gadījumos ukraiņu lidroboti trāpījuši arī dzīvojamajām ēkām, ir pieci bojāgājušie, tai skaitā kāds indiešu viesstrādnieks. Maskavas pretgaisa aizsardzības sistēma neapšaubāmi ir visnopietnākā visā valstī, ja neskaita vadoņa Putina ārpilsētas rezidences apkārtni Valdaja augstienē. Tomēr ukraiņu trieciens izrādījies ļoti labi plānots, atrodot sistēmā robus. Tas vēlreiz apliecina modernās karadarbības patiesību, ka dārgas un tehniski sarežģītas pretgaisa aizsardzības sistēmas īsti netiek galā ar lētu un salīdzinoši vienkārši izgatavojamu lidrobotu spietiem. Maskavas un tās apkārtnes iedzīvotājos šī jaunā realitāte ar karu, kurš beidzot pieklauvējis arī pie viņu durvīm, izraisījusi paniku, sašutumu un vaicājumus par to, vai vadonis Putins vispār esot lietas kursā par situāciju. Pekinas vizīšu konveijers Ārēji spoža, bet saturiski patukša – tā daudzi komentētāji vērtē Savienoto Valstu prezidenta Donalda Trampa pagājušās nedēļas vizīti Ķīnas Tautas republikā. Aizokeāna viesim tika izrādīta visa pienācīgā cieņa, taču, runājot par nozīmīgākajiem divu pasaules superlielvalstu attiecību aspektiem, nekāda būtiska attīstība nav panākta. Ir gan arī komentētāji, kā, piemēram, izdevuma „Guardian” citētais konsultāciju kompānijas „Asia Group” līdzstrādnieks Džordžs Čens, kuri pauž, ka pats vizītes fakts un ciešāka dialoga atjaunošana starp Baltā nama saimnieku un Ķīnas līderi Sji Dzjiņpinu ir zināms sasniegums. Šī brīža aktuālais temats, protams, ir konflikts Tuvajos Austrumos un bloķētais Hormuza jūrasceļš, no kā cieš arī Ķīnas ekonomika. Pēc visa spriežot, Trampam nav izdevies panākt, lai Pekina izmantotu savu ietekmi, mudinot Irānu uz piekāpību. Ķīnas ārlietu resors neapstiprināja prezidenta apgalvojumus, ka namatēvs viņam solījis nepiegādāt Irānai militāro ekipējumu. Tāpat Ķīnas amatpersonu izteikumi tikai daļēji apstiprina Trampa teikto par „fantastiskajiem” komercdarījumiem, konkrēti – simtiem lidmašīnu pirkšanu no kompānijas „Boeing”. Toties Ķīnas vadonis Sji, domājams, ir gandarīts par to, kā samitā izvērtās Taivānas jautājuma traktējums. Viņa publiski teiktais bija: nepareiza rīcība no Vašingtonas puses var izraisīt „sadursmes un pat konfliktus” starp lielvarām. Savukārt no Donalda Trampa mutes vizītes laikā izskanēja frāze, ka viņš negribot pieredzēt nekādu Taivānas neatkarības pasludināšanu. Kā zināms, pašreizējais Taivānas prezidents Lai Cjinde pieder tam taivāniešu politikas spārnam, kas principā atbalsta virzību uz pilnvērtīgu valstisku suverenitāti, un tas no Pekinas viedokļa būtu Ķīnas suverenitātes pārkāpums un iemesls karam. Taivānas vadītājs, reaģējot uz Pekinas samitā pausto, izteicies, ka viņa valstij neesot kaut kas jāpasludina, ja tā jau ir neatkarīga un demokrātiska valsts. Tomēr Taipejai netrūkst iemesla bažīties, ciktāl Donalds Tramps joprojām nav apstiprinājis paredzēto ieroču piegādes paketi Taivānai četrpadsmit miljardu dolāru apmērā un dienu pēc vizītes intervijā telekanālam „Fox News'izteicies, ka šīs piegādes esot labs kaulēšanās līdzeklis sarunās ar Pekinu. Pekinas Aizliegtās pilsētas zāles, var teikt, bija tikko izmēztas pēc iepriekšējā rauta, kad vakar Ķīnas galvaspilsētā oficiālā vizītē ieradās agresorvalsts vadonis Vladimirs Putins. Pekina šādi demonstrē visai pasaulei un arī pašmāju sabiedrībai savu ārkārtīgi pieaugušo svaru pasaules politikā. Savukārt Kremlis, atšķirībā no padomiskās pagātnes, tagad kļuvis par ķīniešu „mazāko brāli” un kopš agresijas kara pret Ukrainu eskalācijas ir izšķiroši atkarīgs no Pekinas gan militāri izmantojamu izstrādājumu importa, gan Krievijas energoresursu eksporta ziņā. Tā nu uz „Padebešu impērijas” galvaspilsētu mūslaiku Maskavijas cars devies ne vien pēc apliecinājuma īpašajām stratēģiskajām partnerattiecībām, bet arī cerot uz jaunu vērienīgu naftas un gāzes iepirkuma līgumu. Nepelnīts pliķis sejā Pagājušajā ceturtdienā, 14. maijā, tika oficiāli apstiprināta informācija, par kuru mediji tika ziņojuši jau dienu iepriekš: Savienoto Valstu kara sekretārs Pīts Hegsets pēkšņi apturējis paredzēto 4000 amerikāņu karavīru nosūtīšanu iepriekš plānotā misijā uz Poliju. Sevišķi pārsteidzošs šis lēmums ir tāpēc, ka attiecīgā pārdislocēšanas operācija jau bija praktiski uzsākta. Hegseta pavēle ir pilnīgi negaidīta ne vien Polijas aizsardzības struktūrām un NATO spēku vadībai Eiropā, bet arī procesā iesaistītajiem amerikāņu militāristiem. Pentagona pārstāvis gan apgalvojis, ka tas bijis izsvērts un rūpīgi izstrādāts lēmums, tomēr realitātē par to nekas neliecina. Tas visnotaļ skaidri izskanēja nākamajā dienā notikušajā ASV Kongresa Pārstāvju palātas Bruņoto spēku komitejas sēdē, kur armijas budžeta sakarā tika iztaujāts armijas lietu ministrs Deniels Driskols un Armijas štāba priekšnieka pienākumu izpildītājs ģenerālis Kristofers Lanīvs. Kongresmeņi, kā demokrāti, tā republikāņi, bija visai skarbi savos izteikumos; arī tāpēc, ka Pīts Hegsets šajā gadījumā pārkāpis pieņemto kārtību, kas prasītu šādu lēmumu saskaņot ar likumdevēju. Saskaņā ar pagājušā gada jūlijā pieņemtu Kongresa rezolūciju administrācijai ir ierobežotas tiesības bez likumdevēja ziņas mazināt amerikāņu spēku klātbūtni sabiedroto teritorijā. „Tas ir pliķis sejā Polijai, pliķis sejā mūsu Baltijas draugiem un pliķis sejā šai komitejai,” sacīja republikāņu kongresmenis Dons Beikons no Nebraskas pavalsts. Abi iztaujātie amatvīri tā arī nespēja sakarīgi argumentēt notikušā militāri taktisko loģiku. Kā zināms, Polija līdz šim uzlūkota kā Savienoto Valstu paraugsabiedrotais, kura aizsardzības budžets – 4,8% no iekšzemes kopprodukta – ir proporcionāli lielākais visā aliansē. Poļi allaž centušies radīt vislabākos apstākļus viņu valstī dislocētajiem amerikāņu karavīriem, un viņu politiķi vairījušies jebkādi kritizēt Donaldu Trampu un viņa administrācijas politiku. Arī tagad no Varšavas izskan drīzāk nomierinoši signāli un aicinājumi nepiešķirt notikušajam pārlieku dramatismu. Tomēr tā vien šķiet, ka šis varētu būt Baltā nama saimnieka kārtējais impulsīvais solis, turpinājums viņa nepatikas izpaudumiem pret „nodevīgo Eiropu”, kura nav bijusi gatava pēc pieprasījuma atbalstīt Savienoto Valstu un Izraēlas militāro kampaņu pret Irānu. Sagatavoja Eduards Liniņš.

Abi and Matt name boats. 

Long lived organisms like trees face a lot of challenges throughout their lifetime. Disturbances big and small coupled with climate change are going to continue to stress trees wherever they grow. Which trees have the highest capacity to deal with said stresses? We don't know until we go looking. That is what drives scientists like Dr. Jill Hamilton. Join us as we look at how she is using poplars, spruce, and ash to understand how trees and their hybrids may or may not have what it takes to survive climate stress. This episode was produced in part by Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

A big thank you and welcome to our new members Abi, Carl, Martin, Karina and Michael.Join us this week as we rise and shine with a new brand of cereal, we discover what actually happened to Xander's banana and the Battling Bulls get catty on the outfield.We'd like to invest shadily in the following :Praise the Nord : Erik has Ambridge in creases.Brad or Trad? : Amber views George's antisocials.Craig's List : Ian manages to fail upwards. Again.Produced by Matthew WeirYou can send the most treasured person in your life a Cider Shed Patreon membership as a gift : https://www.patreon.com/thecidershed/giftBecome a beautiful patron of The Cider Shed and receive early ad-free episodes and our exclusive Patreon-only midweek specials. It really REALLY helps us out.https://www.patreon.com/thecidershedTo help us out with a lovely worded 5 star review hit the link below. Then scroll down to ‘Ratings and Reviews' and a little further below that is ‘Write a Review' (this is so much nicer than just tapping the stars

This week's episode all five pastors are fresh off a packed weekend full of Mother's Day celebrations, graduation ceremonies, wedding emotions, and just enough Dollar Tree gifts to keep everyone humble.Jeremy officially “graduamulated” with his Master of Arts in Ministry (yes ma'am), complete with surprise parties, tiny Uno cards, and enough travel-size Connect 4 to last a lifetime. Eric survived marrying off his daughter Abi without completely falling apart… though the father-daughter dance may have tested that. Meanwhile, the team reflects on Mother's Day, family traditions, and why Cilantro's might just be the true love language of ministry families.Then the conversation shifts into this week's 40 Days of Wonder message focused on Thomas—the disciple forever remembered for doubt. Was Thomas really doubting, or was he just grieving? The guys unpack what spiritual doubt looks like, how faith and evidence work together, and why taking every thought captive matters when life gets heavy.Sometimes faith looks like certainty. Sometimes it looks like showing up with questions.And sometimes… it looks like graduation gifts from the Dollar Tree.

What can investigating the genes in flower development teach us about plant evolution? A lot! What started as a simple question about the quirky nature of flower development in the order of plants collectively referred to as "the gingers" turned into multiple threads related to plant evolution and diversity. Join me and Dr. Chelsea Specht as we take a deep dive into the wild world of Zingiberales. This episode was produced in part by Joe, Diane, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Ste is joined by Paul and Abi as they debate the hottest topics ahead of Liverpool's match with Chelsea in the Premier League including whether Mac Allister should start after a poor performance against Man United and who should start on the wings.

Micro moths are a wonderfully diverse group of underappreciated insects living all around us. How they interact with their environment, particularly with the native plants the need to survive, is both fascinating and mysterious. Join me and Dr. Jason Dombroskie as we explore the tiny world of micro moths, their host plants, and all the natural history mysteries in between. This episode was produced in part by Andy, S Heller, Drewsophila, Sascha, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Ste is joined by Paul and Abi as they debate the hottest topics ahead of Liverpool's clash with North West rivals Manchester United at Old Trafford in the Premier League.

The Gulf Coast of southeastern North America is a biodiversity hotspot brimming with cool plants. Everywhere you look, there are plants that grow nowhere else in the world. Why is this region so diverse? How do we try and understand the origins of endemic plants? These are the kind of questions that drive Dr. Elizabeth White. Join us as we explore what it takes to understand plant endemism in a truly special place. This episode was produced in part by Andy, S Heller, Drewsophila, Sascha, Kim, Tanya, Neil, Matthew, April, Dana, Lilith, Sanza, Eva, Yellowroot, Wisewren, Nadia, Heidi, Blake, Josh, Laure, R.J., Carly, Lucia, Dana, Sarah, Lauren, Strych Mind, Linda, Sylvan, Austin, Sarah, Ethan, Elle, Steve, Cassie, Chuck, Aaron, Gillian, Abi, Rich, Shad, Maddie, Owen, Linda, Alana, Sigma, Max, Richard, Maia, Rens, David, Robert, Thomas, Valerie, Joan, Mohsin Kazmi Photography, Cathy, Simon, Nick, Paul, Charis, EJ, Laura, Sung, NOK, Stephen, Heidi, Kristin, Luke, Sea, Shannon, Thomas, Will, Jamie, Waverly, Brent, Tanner, Rick, Kazys, Dorothy, Katherine, Emily, Theo, Nichole, Paul, Karen, Randi, Caelan, Tom, Don, Susan, Corbin, Keena, Robin, Peter, Whitney, Kenned, Margaret, Daniel, Karen, David, Earl, Jocelyn, Gary, Krysta, Elizabeth, Southern California Carnivorous Plant Enthusiasts, Pattypollinators, Peter, Judson, Ella, Alex, Dan, Pamela, Peter, Andrea, Nathan, Karyn, Michelle, Jillian, Chellie, Linda, Laura, Miz Holly, Christie, Carlos, Paleo Fern, Levi, Sylvia, Lanny, Ben, Lily, Craig, Sarah, Lor, Monika, Brandon, Jeremy, Suzanne, Kristina, Christine, Silas, Michael, Aristia, Felicidad, Lauren, Danielle, Allie, Jeffrey, Amanda, Tommy, Marcel, C Leigh, Karma, Shelby, Christopher, Alvin, Arek, Chellie, Dani, Paul, Dani, Tara, Elly, Colleen, Natalie, Nathan, Ario, Laura, Cari, Margaret, Mary, Connor, Nathan, Jan, Jerome, Brian, Azomonas, Ellie, University Greens, Joseph, Melody, Patricia, Matthew, Garrett, John, Ashley, Cathrine, Melvin, OrangeJulian, Porter, Jules, Griff, Joan, Megan, Marabeth, Les, Ali, Southside Plants, Keiko, Robert, Bryce, Wilma, Amanda, Helen, Mikey, Michelle, German, Joerg, Cathy, Tate, Steve, Kae, Carole, Mr. Keith Santner, Lynn, Aaron, Sara, Kenned, Brett, Jocelyn, Ethan, Sheryl, Runaway Goldfish, Ryan, Chris, Alana, Rachel, Joanna, Lori, Paul, Griff, Matthew, Bobby, Vaibhav, Steven, Joseph, Brandon, Liam, Hall, Jared, Brandon, Christina, Carly, Kazys, Stephen, Katherine, Manny, doeg, Daniel, Tim, Philip, Tim, Lisa, Brodie, Bendix, Irene, holly, Sara, and Margie.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.