Podcasts about forks

In this episode, Brian welcomes Thomas Sewid of the Kwakwaka'wakw people of northern Vancouver Island for a wide-ranging conversation about Sasquatch traditions, firsthand encounters, Indigenous knowledge, and the debate over the more supernatural claims surrounding the subject.Thomas explains that Sasquatch, known by names including Ćunaq̣, Ts'uunaaka, Tl'onaq'a, Junakwa, and Chunag, holds a significant place within Kwakwaka'wakw culture. The figure appears in traditional masks, potlatch dances, crest imagery, totem poles, and generations of oral teaching. Growing up in a commercial fishing family, Thomas spent much of his life along the remote coast of British Columbia, where stories of Sasquatch were part of the cultural landscape long before the subject became popular in modern cryptozoology.He shares reports he gathered from fishermen, loggers, Indigenous communities, and people living throughout the coastal wilderness, along with several experiences of his own. These include a sighting with his father near Sayward and later encounters while Thomas was living and working deep in the bush and serving as a watchman in isolated areas.Thomas also offers his interpretation of behaviors commonly reported by Sasquatch witnesses.He believes some apparent wood knocks may actually be powerful hand slaps used as warning or communication signals and describes Sasquatch groups as operating within a coordinated clan structure that allows individuals to alert and support one another. He also discusses their ability to use terrain, cover, and wind direction to remain aware of people while avoiding detection.The conversation then turns to what Thomas openly calls the “woo” surrounding Sasquatch.He strongly rejects claims involving cloaking, portals, telepathy, and other paranormal abilities, arguing that fear, stress, and trauma can dramatically affect how people interpret unusual encounters. For Thomas, the investigation should remain focused on physical evidence, observable behavior, and claims that can ultimately be tested.Thomas also explores his belief that Sasquatch could represent an ancient or “original human” population and discusses why official recognition of such a species could create complicated questions involving Indigenous rights, land management, environmental protections, logging, development, and regional economies.It is a conversation that brings together generations of cultural tradition, decades spent in the wilderness, firsthand experience, and a decidedly evidence-focused approach to one of North America's most enduring mysteries.Thomas also discusses his Sasquatch Island work, SasquatchIsland.com, SasquatchLegend.com in Forks, Washington, and plans for an upcoming museum dedicated to preserving and sharing the history and traditions surrounding Sasquatch.Visit Sasquatch Island WebsiteVisit Sasquatch The Legend Website Email BrianJoin Our FREE NewsletterGet Brian's Books Leave Us A VoicemailVisit Our WebsiteBecome a supporter of this podcast: https://www.spreaker.com/podcast/sasquatch-odyssey--4839697/support.Have you had a Bigfoot encounter, Sasquatch sighting, Dogman experience, or other cryptid or paranormal encounter? We'd love to hear your story. Email brian@paranormalworldproductions.com to be featured on a future episode of Sasquatch Odyssey.Sasquatch Odyssey is a leading Bigfoot and cryptid podcast exploring real encounters, field research, and scientific analysis of the Sasquatch phenomenon.Follow the show and turn on automatic downloads so you never miss an episode.

For our August Summer Special, we've gone back through six months of Eyes on Tomorrow conversations to bring you some of our favourite moments — the ones that made us think, made us laugh, and occasionally caught us completely off guard.This episode is split into three themes:Forks in the Road - the chance meetings and unexpected turns that shaped our guests' careers. Including how a £20 LinkedIn Premium subscription helped set Pearse Keane on the path toward AI in ophthalmology, and the weekend that nearly saw Keith Martin leave medicine altogether.Eyes on the Future - our guests' visions for where the specialty is heading, from oculomics to AI-assisted decision-making to robot-assisted cataract surgery.Away from the Clinic - some of our favourite answers to the quirky questions we ask every guest at the end of the podcast.Featuring conversations with Pearse Keane, Keith Martin, Dan Milea, Ramesh Kekunnaya, Uday Devgan, Bita Manzouri, Purvi Thomson and Elizabeth Lumb.Three of our featured guests — Pearse Keane, Keith Martin and Dan Milea — were named on The Ophthalmologist Power List 2025, recognised for their influence and impact across Innovation, Glaucoma and Neuro-ophthalmology respectively.Get access to bonus episodes, along with a host of CPD resources, when you subscribe for only £25 per year at https://eyesontomorrow.substack.com/subscribeThanks to Topcon Healthcare and Thea UK for supporting Eyes on Tomorrow.Produced by Matt Hill at Rethink Audio. This is a public episode. If you'd like to discuss this with other subscribers or get access to bonus episodes, visit eyesontomorrow.substack.com/subscribe

This episode of Forks BS opens with local event promotions and community updates, then moves through listener jokes and election reflections before diving into a heated discussion about gender and sports. The hosts analyze the WNBA controversy—Sophie Cunningham's comments, coach Cheryl Reeve's "trans kids belong" message, DeJoné Carrington's post, and Enes Kanter's announced WNBA eligibility—connect it to the Daily Wire film "What Is a Woman?", and touch on related topics like Title IX, professional vs. amateur sports, and broader political stories including Fauci and vaccine debates. Throughout the show they intersperse local ads, bar and concert promotions, and invite listeners to call or text with topics for future shows.

Hello and welcome the 175th episode of Film Freakz, our podcast about movies! This episode we chose to talk about the movie Twilight New Moon from 2009! This podcast features YemmytheFerret (Yemmy), RaeofPositivity (Rae), Taymation Studios (Tay), and JustKalas (Kalas). This movie was chosen by our listener Chamillyon, thanks for the recommendation! Bella Swan is on the cusp of her 18th birthday and blissfully happy with her undead beau Edward Cullen. While celebrating her birthday with Edward's family of 'vegetarian' vampires, a frightening incident convinces Edward that he's simply too dangerous to be around his sweetheart. He decides to leave the town of Forks in order to ensure her safety - leaving her behind, angry and depressed. Directed by Chris Weitz. Thank you for listening on all platforms! We want YOUR recommendations for the FAN VOTE! Send them in by commenting on the YouTube version, messaging us on our social medias, or sending us an email!Twitch: https://www.twitch.tv/yemmytheferretTwitter: https://twitter.com/YemmyTheFerretBlueSky: https://bsky.app/profile/yemmytheferret.bsky.socialJoin my Discord: https://discord.gg/b9NaNgp

This Bonus Episode is brought to YOU by our friends at State Farm! Weirdos!! Get ready to return to Forks for the epic conclusion of our MORBID recap of the Twilight franchise!  Today we're diving into Breaking Dawn (Part 2) and part 3 of the book, and what a gift it is! Bella is the BEST at everything, even though her selfishness gets the Cullens in hot water AGAIN! Jacob is the new creep on the block with his imprinting escapades. And the Volturi are walking... I guess? Prepare yourself for Alaina's masterful impression of Bella's singsong voice, worry with Ash about dear Charlie's heart health, and join us as we attempt to untangle the host of inconsistencies that had us angry, confused or howling with laughter! Grab the nearest tissue box and prepare to cry-laugh with us!   Cowritten by Alaina Urquhart, Ash Kelley & Dave White (Since 10/2022)Produced & Edited by Mikie Sirois (Since 2023)Research by Dave White (Since 10/2022), Alaina Urquhart & Ash KelleyListener Correspondence & Collaboration by Debra LallyListener Tale Video Edited by Aidan McElman (Since 6/2025) Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Kruw (@kruwed) runs one of the highest-volume WabiSabi coordinators, giving him direct insight into how the protocol handles liquidity, Sybil resistance, and real-world usage.Timestamps:00:42 — Wasabi 2.8 Privacy Features 02:45 — Taproot As Wasabi's Default Address07:25 — Pay Inside CoinJoin Saves 40 Minutes10:26 — Auto CoinJoin 12:21 — WabiSabi Blocks Whale Sybil Attacks14:31 — Payjoins16:37 — ClusterMempool Wins for CoinJoins20:00 — Upcoming forks21:14 — CoinJoin: Free Replay Protection Hack22:53 — CoinJoin Ban Myth Debunked25:41 — Black Hole: Earn While MixingLinks: https://x.com/wasabiwallethttps://x.com/Kruwedhttps://wasabiwallet.io/Stephan Livera links:Follow me on X: @stephanliveraSubscribe to the podcastSubscribe to Substack

Today we're talking about Mayor Jacob Frey saying he wants to put Ice agents in prison, Detroit Lakes says no to rainbow displays, and Mike Lindell the pillow guy steps down to run for Governor. For easy access to download or stream past Common Sense UnSensored episodes visit - https://commonsenseunsensored.podbean.com/ Show is recorded at Grand Forks Best Source. For studio information, visit www.gfbestsource.com #PodcastsPolitics #gfbestsource.com #local #grandforksnd #grandforksbestsource #politics #news #hardhittingnews #legislature @grandforksndcommonsenseunsensored

Kenny is 38 years old and has never been to a rock concert! He lives in Forks and he is going to take the wife to see Santana and The Doobie Brothers!

On Bella and Edward's fabulous honeymoon, they do what couples traditionally do on honeymoon: bump it exactly one time and become instantly pregnant with a magic baby. Since it's the kind of baby that eats their mom physically (rather than just hormonally), they must immediately return to Forks to summon the baby drama crew. ★ Support this podcast on Patreon ★ We are Alice Sullivan, Micah Sparkman, and Jeff Lake.Find our other podcasts at armadillo.club!Music: CHASIN' IT by Jason Shaw, licensed under CC-BY 3.0.

It's time for the main course, and the most surprisingly complicated of cutlery items covered so far in the podcast: the fork! Jessica and Matilda dive into the history and archaeology of the fork, and discover that it's not quite such a simple tool as they originally thought. Why do Americans and Germans hold their forks so differently? What's the difference between a fork and a fork-like object? And who was using a spork in the 4th century? Tune in to find out! Transcripts For rough transcripts of this episode go to https://www.archpodnet.com/teabreak/58 Links 4-pronged 4th century Roman fork 2-pronged 6th century Sasanian fork 3rd century Roman spork Bowls with faces (“fiftyeight”) American fork use Contact the Host Matilda's Contact Details Email: matilda@thearchaeologiststeacup.com Website Instagram Newsletter Jess's Contact Details Email: j.vandam.conservation@gmail.com Website Instagram ArchPodNet APN Website: https://www.archpodnet.com APN on Facebook: https://www.facebook.com/archpodnet APN on Twitter: https://www.twitter.com/archpodnet APN on Instagram: https://www.instagram.com/archpodnet APN Shop Affiliates Motion Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

It's time for the main course, and the most surprisingly complicated of cutlery items covered so far in the podcast: the fork! Jessica and Matilda dive into the history and archaeology of the fork, and discover that it's not quite such a simple tool as they originally thought. Why do Americans and Germans hold their forks so differently? What's the difference between a fork and a fork-like object? And who was using a spork in the 4th century? Tune in to find out! Transcripts For rough transcripts of this episode go to https://www.archpodnet.com/teabreak/58 Links 4-pronged 4th century Roman fork 2-pronged 6th century Sasanian fork 3rd century Roman spork Bowls with faces (“fiftyeight”) American fork use Contact the Host Matilda's Contact Details Email: matilda@thearchaeologiststeacup.com Website Instagram Newsletter Jess's Contact Details Email: j.vandam.conservation@gmail.com Website Instagram ArchPodNet APN Website: https://www.archpodnet.com APN on Facebook: https://www.facebook.com/archpodnet APN on Twitter: https://www.twitter.com/archpodnet APN on Instagram: https://www.instagram.com/archpodnet APN Shop Affiliates Motion Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

What if the thing you think disqualifies you is actually the thing God wants to use?In this episode, Pastor Todd Lester teaches from 2 Timothy 2:20-26. Paul pictures the church as a house full of vessels, gold, silver, clay, wood, and says even the ones that have been through the worst of it can still be cleaned up and used for something good. It's a word for anyone wondering if they've wandered too far to come back.Forks of Elkhorn Baptist Church | Midway, KYNew episodes every week. Subscribe wherever you listen.forksbaptist.org

Ever caught yourself going through all the motions of faith and still feeling like something's missing?In this episode, Pastor Todd Lester teaches from 2 Timothy 3:1-9, where Paul warns Timothy about a faith that looks right but has no power behind it — people who love themselves, money, and pleasure more than God. Todd talks honestly about what that looks like in everyday life, and what it means to actually carry the power that's supposed to come with following Jesus.Forks of Elkhorn Baptist Church | Midway, KYNew episodes every week. Subscribe wherever you listen.forksbaptist.org

The gang returns with stories that somehow spiral from Christopher Nolan's The Odyssey into insurance nightmares, coffee raves, racquetball glory, international travel panic, and enough questionable decisions to fill an entire daily podcast.Rizz finally delivers his long-awaited review of The Odyssey, and somehow the movie itself isn't even the weirdest part of the story. Between a theater neighbor who falls asleep almost immediately, another guy choking on popcorn halfway through, thirty minutes of previews that nobody remembers, and the debate over whether Tom Holland belongs anywhere near ancient Greece, the review quickly becomes its own adventure.Meanwhile, weekend plans take a serious turn when a family emergency forces international travel plans to change at the last minute. What should have been a trip to Paris becomes a crash course in travel insurance, refund headaches, rental cars in Ireland, driving on the wrong side of the road, and why nobody actually enjoys calling customer service.Lern attempts to enjoy a trendy coffee rave before discovering that mixing caffeine, heat, and questionable health decisions may not be the best combination. A cute photo booth, mocktails, and dinner plans quickly give way to a racing heart, an emergency exit from date night, and one unforgettable restaurant bathroom experience.Elsewhere, Rafe and Scott accidentally become local sports heroes after a racquetball match attracts an audience of elementary school kids who immediately begin cheering, booing, and turning two middle-aged men into reluctant professional athletes. Turns out cardio is a lot easier when strangers are judging your every swing.The gang talks about Missouri becoming the filming home for the upcoming Smoking the Bandit prequel series and wonders which cast member has the best chance of sneaking into the production. Then it's time for celebrity gossip, Comic-Con announcements, Green Day surprises, Ryan Gosling officially becoming Ghost Rider, Rick Moranis making his long-awaited return to Spaceballs, and Ryan Reynolds finding new ways to troll absolutely everyone.David Lee Roth and Sammy Hagar somehow become the center of another classic rock debate, complete with cocktail analysis, tour cancellations, residency talk, and the eternal question: is extending an olive branch still an olive branch if you're holding a martini?The crew also breaks down Tom Holland's unforgettable Hot Ones appearance, Usher's awkward on-stage rejection, Chris Brown controversy, movie leaks, Marvel news, and enough pop culture commentary to keep your group chat busy all week.Of course, no episode would be complete without Crap on Celebrities, birthday nonsense, ridiculous observations, sarcastic debates, and the kind of off-the-rails conversations that somehow make perfect sense before 10 AM.It's National Chicken Finger Day. The crew dives headfirst into one of the wildest Florida stories we've seen in a long time after a sugar daddy arrangement completely unravels. A first date involving shopping, dinner, foot massages, and a misunderstanding over expectations turns into a police chase, felony charges, and one extremely angry retiree from The Villages. Naturally, the gang spends way too much time trying to understand the mysterious rules of sugar daddy culture, wondering where the boundaries actually exist and how anyone thinks these arrangements are ever going to stay uncomplicated.Along the way there's plenty of classic Rizz Show nonsense. Chicken fingers get the appreciation they deserve. Bagpipes spark an international debate. Houseplants apparently need fresh air now. Florida continues doing Florida things. The crew even detours into celebrity wedding history and why courthouse weddings are becoming cooler than giant expensive ceremonies.Follow The Rizzuto Show → https://linktr.ee/rizzshowConnect with The Rizzuto Show Comedy Podcast online → https://1057thepoint.com/RizzShowHear The Rizz Show daily on the radio at 105.7 The Point | Hubbard Radio in St. Louis, MO.Train derailment near golf courses outside EurekaWorld Naked Bike Ride St. Louis 2026Baileys' Range and Baileys' Chocolate Bar set to close, citing reorganization processApplebee's closes St. Louis County locationInvasive ant with ‘painful sting' found in Missouri, researcher saysCarnival Cruise responds to passenger who horrified shipmates with disgusting act: ‘Forks are intended for food, not foot care'Florida Villages resident hires $1K Tinder ‘sugar baby' — then pulls gun after she tries to run awayCourthouse weddings are booming as many couples skip pricey traditional ceremoniesSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Sometimes the internet gives us a story so unbelievably disgusting that it hijacks an entire morning. This episode begins with one of those moments after a viral video shows a cruise passenger scraping fungus off her foot with a buffet fork... while other people are trying to eat. Naturally, the crew debates hygiene, cruise ships, humanity, and whether Earth deserves another season.From there the chaos keeps rolling.The gang talks about Missouri becoming the filming home for the upcoming Smoking the Bandit prequel series and wonders which cast member has the best chance of sneaking into the production. Then it's time for celebrity gossip, Comic-Con announcements, Green Day surprises, Ryan Gosling officially becoming Ghost Rider, Rick Moranis making his long-awaited return to Spaceballs, and Ryan Reynolds finding new ways to troll absolutely everyone.David Lee Roth and Sammy Hagar somehow become the center of another classic rock debate, complete with cocktail analysis, tour cancellations, residency talk, and the eternal question: is extending an olive branch still an olive branch if you're holding a martini?The crew also breaks down Tom Holland's unforgettable Hot Ones appearance, Usher's awkward on-stage rejection, Chris Brown controversy, movie leaks, Marvel news, and enough pop culture commentary to keep your group chat busy all week.Of course, no episode would be complete without Crap on Celebrities, birthday nonsense, ridiculous observations, sarcastic debates, and the kind of off-the-rails conversations that somehow make perfect sense before 10 AM.If you love comedy podcasts, weird news, celebrity gossip, St. Louis humor, hilarious fails, entertainment commentary, and friends arguing about things nobody else would spend thirty minutes discussing, you've found your people.Grab your coffee.Maybe skip breakfast during the fungus conversation.And definitely leave the buffet forks where they belong.Follow The Rizzuto Show → https://linktr.ee/rizzshowConnect with The Rizzuto Show Comedy Podcast online → https://1057thepoint.com/RizzShowHear The Rizz Show daily on the radio at 105.7 The Point | Hubbard Radio in St. Louis, MO.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Carin Jayne Casey's Standing Through Storms series, Newest Fiction Books·       My Secret Life: Mysterious & Adventurous·       Forks in the Road: The Paths We TakeDuring 2025 through 2026, Carin has been in the process of creating an anthology series that she felt the Lord had assigned to her, namely, “Sharing Our Journey Of Coming To Jesus: Testimony From Twelve Believers.” Book One was published in 2025, and Book Two will be published in 2026.In the midst of her working through this assignment, Carin has been blessed with two dreams that are now published fiction stories:  My Secret Life is page-turner, a crafted blend of crime and romance, within a Christian life. It encourages; we can turn to God through any situation. Reviews indicate: “Great read - finished it in one sitting and had all the emotions! Suspense, fear, romance, trust in the Lord and not able to wait to see what happened on the next page...” signed, Stella“Adventure! Intrigue! Danger! Suspense! All that wrapped up in faith that is woven into the roller coaster of the character's lives! You won't be able to put the story down!” signed, Mary Moss, Author, Coach, Speaker, StorytellerForks in the Road illustrates the many paths we may choose within a lifetime, resulting rewards or consequences we may face, and especially how to overcome along that journey.  A review indicates:  “Carin Jayne Casey has written a book of new beginnings. Valerie reminds us of ourselves, navigating intersections and roundabouts often with rose-colored glasses. We root for her and hold our breath. Forks in the Road invites us to leave toxic relationships without bitterness or regret. [it is] a good read for a quiet night that will resonate long past the last page.” Signed, Angela B. Brown, Support Group Facilitator, Yeshua's House#carinjaynecasey, #turntogodwithcarin, #turn2godwcarin, #fiction, #christianauthor, #amazonbooks, #christianity, #bible, #overcoming, #standingthroughstorms, #lifechoices, “travelbook, #faithhopelove, #Crime, #Romance, #newbeginnings

The war is no longer being fought with dragons alone. Sarah and Will break down House of the Dragon Season 3, Episode 5, "Unbowed and Unbent," as unrest spreads through King's Landing and every side begins using manipulation, insurgency, religion, money, and guerrilla warfare to gain an advantage. They discuss Ormund Hightower's campaign to undermine Rhaenyra, the violent attacks against the Gold Cloaks, and Daemon's growing frustration with how the city is being governed. They also examine Rhaenyra and Daemon's conflicting ideas about power, legitimacy, faith, and what it truly means to rule as a Targaryen. Elsewhere, Alicent attempts to protect Helaena and her unborn child, Mysaria finds herself caught between competing loyalties, and the damaged relationship between Aegon and Aemond reveals how deeply their childhood resentment continues to shape the war. Sarah and Will also explore Ormund's influence over Daeron, Criston Cole's brutal campaign through the Riverlands, Oscar Tully's military tactics, and how the nobles and common people of Westeros are being sacrificed for a conflict built around one family's bloodline. Then, the conversation shifts to the final season of The Bear. Sarah and Will share their thoughts on the season's one-day structure, Carmy's conclusion, Sydney and Tina's expanded roles, and why Episode 7, "Caramel," feels like a spiritual successor to the fan-favorite episode "Forks." They also discuss the series finale, the growth of Richie and the restaurant staff, the moments that worked—and one particular job interview that did not—before ranking all five seasons of the acclaimed series. Topics include: • The Gold Cloak murders and unrest in King's Landing • Ormund Hightower's strategy and support for Daeron • Rhaenyra and Daemon's battle over power and legitimacy • The role of faith, culture, and public favor in Westeros • Alicent, Helaena, Mysaria, and the unborn child • Aegon and Aemond's lifelong sibling rivalry • Criston Cole's legacy and the Riverlands guerrilla campaign • The Bear series finale and final-season reactions • Why "Caramel" continues the character growth of "Forks" • Sarah and Will's complete ranking of The Bear We discuss House of the Dragon strictly from the perspective of television viewers who have not read the source material. Timestamps 0:00 Welcome 0:30 House of the Dragon Season 3 Episode 5 "Unbowed and Unbent" 53:14 The Bear - Season Five  1:08:00 Outro   Follow Sarah on social media at @sjbelmont and Will at @willmpolk. Follow Scene N Nerd on X, Bluesky, Facebook, Instagram, and Threads, and visit SceneNNerdPodcast.com. Rate, follow, and leave a comment on Apple Podcasts, Spotify, YouTube, or wherever you listen to podcasts.  

Notas del Episodio (Show Notes)Viviendo con Coyotes: Lo Más Amable Que Puedes Hacer es Asegurarte de Que Nunca Les AgradesLos coyotes forman parte de la vida en San Felipe. Ya sea que vivas en El Dorado Ranch, Pete's Camp, Campo Ocotillo, La Ventana del Mar o en cualquier otra comunidad de la zona, es muy probable que ya hayas visto uno... o que pronto lo hagas.En este episodio de Forks in the Road, Cal responde una de las preguntas que más hacen los residentes:"¿Qué debo hacer si me encuentro con un coyote?"La respuesta podría sorprenderte.Los expertos en vida silvestre coinciden en que la mejor manera de proteger a las personas, a las mascotas y a los propios coyotes es ayudarles a conservar su temor natural hacia los seres humanos.Descubre qué es el "hostigamiento" (hazing), por qué es una herramienta segura y humanitaria para mantener alejados a los coyotes, por qué alimentarlos suele causar más problemas que soluciones y cómo, en muchas ocasiones, el coyote que ya vive en la zona ayuda a mantener alejados a otros coyotes más agresivos.Además, Cal aborda otra pregunta muy común durante el verano en Baja:¿Debemos dejar agua para la fauna silvestre cuando el calor supera los 40°C?Basándose en las recomendaciones de especialistas en vida silvestre, explica cómo es posible apoyar a los animales del desierto sin acostumbrarlos a depender de las personas.Si vives en Baja o simplemente disfrutas de la naturaleza que hace único este lugar, este episodio ofrece consejos prácticos para convivir de forma segura y responsable con la vida silvestre.En este episodio aprenderás:• Qué significa "hazing" y por qué los expertos lo recomiendan.• Cómo actuar cuando un coyote pierde el miedo a las personas.• Por qué los coyotes residentes pueden beneficiar al ecosistema.• Medidas sencillas para proteger a tus mascotas y evitar visitas no deseadas.• La forma correcta de ofrecer agua a la fauna silvestre durante el verano.• Por qué mantener a los coyotes salvajes es la mejor forma de protegerlos.

Show NotesCoyotes are part of life in San Felipe. Whether you live in El Dorado Ranch, Pete's Camp, Campo Ocotillo, La Ventana del Mar, or anywhere along the coast, chances are you've seen one—or eventually will.In this episode of Forks in the Road, Cal explores one of the questions listeners ask most often:"What should I do if I see a coyote?"The answer may surprise you.Wildlife experts say the safest approach—for you, your pets, your neighbors, and even the coyotes themselves—is to help coyotes keep their natural fear of people. You'll learn why "hazing" is a humane and effective way to discourage unwanted encounters, why feeding wildlife often does more harm than good, and why sometimes the resident coyote is actually protecting your neighborhood from more aggressive newcomers.Cal also tackles another common Baja question:Should we leave water out for wildlife during the extreme summer heat?Drawing on recommendations from wildlife agencies across the Southwest, he explains how water can be provided responsibly without teaching wildlife to depend on people or homes.Whether you're a longtime Baja resident or new to desert living, this episode offers practical, common-sense advice for sharing this remarkable landscape with the animals that were here long before we arrived.In this episode you'll learn:• Why wildlife experts recommend "hazing" coyotes.• How to respond if a coyote seems too comfortable around people.• The surprising role resident coyotes play in protecting their territory.• Simple ways to reduce unwanted wildlife visits.• The right—and wrong—way to provide water for wildlife during Baja summers.• Why keeping coyotes wild is ultimately the kindest thing we can do.

In Episode 369 of The Canine Paradigm, Glenn and Pat catch up after a run of recent adventures, including PSA trials, Red Team work, and the arrival of a new dog. However, the main thread of this episode comes from two powerful episodes of The Bear, titled Fishes and Forks and the phrase, every second counts. Glenn explains how he interpreted those episodes through a dog training lens. Fishes shows chaos, pressure, poor communication, emotional overload, and the damage that can happen when people are stuck reacting instead of leading. In contrast, Forks shows what can happen when someone is placed in the right environment, given structure, trusted with responsibility, and allowed to discover their own value. From there, we connect those ideas back to dogs, handlers, and trainers. Some dogs live in constant noise, pressure, and confusion. Others begin to change when we give them clarity, standards, purpose, and a chance to succeed. The same applies to people learning the craft. Training is not just about commands. It is about environment, timing, leadership, confidence, and creating moments where the learner starts to believe they can do better. This episode is part catch-up, part television breakdown, and part dog training reflection. If you loved The Bear, or if you care about how pressure and purpose shape behaviour, this one will make sense. Further Details Are you in search of top-tier dog trainers and steadfast supporters of the Canine Paradigm? Below is a comprehensive list of individuals and businesses that stand by our mission, contribute to our operational costs, and make significant contributions to the canine community. Glenn Cooke oversees a wide range of canine-related services at Pet Resorts Australia. Pat Stuart offers a full suite of coaching and dog training services through Serious dog business We invite you to support our show and access exclusive content on our Patreon page. Your contributions directly support the show's ongoing production, and we deeply appreciate the wonderful community that has formed around it. If you're unsure how to contribute, feel free to reach out to us for assistance. Explore our complete range of merchandise at our Teespring store. You can also help by spreading the word within the canine community or suggesting special guests for future interviews. For information on how to listen to our podcast, please visit this link. Subscribe to our YouTube channel for video content and updates. If you enjoyed the podcast, we would greatly appreciate your reviews on iTunes, Spotify, and other podcast directories. Details on joining the International Association of Canine Professionals (IACP) can be found here. We highly recommend membership for anyone serious about advancing in the canine industry. We also encourage you to check out Dogs Playing for Life, a transformational rescue process making a positive impact on dogs across the USA. Support Our Supporters Narelle Cooke hosts her own podcast, Natural Health for People and Pets, available on all major podcast platforms. Be sure to listen in. For the finest human-grade supplements for your dogs, visit Canine Ceuticals. Now available in the USA. SHOW SPONSOR Jason Firmin of Einzweck Dog Quip is another proud SHOW SPONSOR. The innovative motorcycle dog kennel can be found at Rowdy Hound. SHOW SPONSOR For daycare and heartfelt training services, check out From the Heart Dog Training. SHOW SPONSOR Our dear friend and frequent contributor, Birdy O'Sheedy, can be found at The magic in dogs Special Thanks A huge thanks to all our contributing artists. Please take a moment to support their amazing work: Jane Stuart Avery Keller Zoie Neidy

Jordan Stranger got started by wheat pasting his art around Winnipeg because it was cheap, fast, and harmless. First came community, then came the city: people began to recognize his work, which led to new opportunities and contracts that displayed his art in a more permanent way. But is public art ever permanent? Today on The Artalogue,  Madison Beale talks with Anishinaabe artist and graphic designer Jordan Stranger (@totemdoodem), originally from Peguis First Nation, about how those early street-level moves grew into iconic Winnipeg murals, major graphic design projects, and public art that people now instantly connect with places like The Forks.We dig into early steps like drawing as a kid, unlocking new confidence through illustration and great teachers at Red River College, and learning how mentors can change the trajectory of an artist's life. Jordan shares how community support helped him take the leap into self-employment, plus what it really looks like when “full-time artist” becomes "full-time everything", with administration taking up lots of an artist's valuable time.Stranger explains how Ojibwe teachings and spiritual practice guide his choices, why he wants his art to encourage reflection as well as connection, and how public art can challenge the way people think about Canada's history, truth, and reconciliation. Jordan closes with hard-earned advice on vulnerability, honesty, and the business side of creativity, with his major takeaway being learning your worth as an artist.  Connect with the Artalogue: Madison Beale, HostBe a guest on The Artalogue Podcast

In this episode, the crew unpacks the debate around BIP 110, why it has become such a lightning rod in Bitcoin, and what it could actually mean in practice. We talked through the core disagreement over what counts as “spam” on the Bitcoin network, the difference between miner-activated and user-activated soft forks, and why some are skeptical that BIP 110 will achieve its stated goal. We also explored the risks of transaction filtering, the role of consensus rules versus individual policy preferences, and how proposals like this expose bigger questions around governance, open-source development, and trust in Bitcoin node implementations.We also shifted into the mining side of the conversation, where we shared exciting progress on Mujina and why open-source mining firmware matters so much. We highlighted recent demos showing extremely fast power ramping, support for mixed hash boards on a single control board, and new community-built tooling and dashboards. To close things out, we gave a shoutout to the hashers supporting 256 Foundation, checked in on the leaderboard, and teased an upcoming guest episode with someone who knows ASIC development inside and out.

In this classic episode, Chuck and Josh sit and converse on the simple, elegant chopstick.See omnystudio.com/listener for privacy information.

Happy 250th America! On this Forks BS episode the hosts celebrate Independence Day, preview local 4th of July events (Sertoma Park, Greenway, River City Speedway) and share practical fireworks safety tips and legal reminders for Grand Forks and surrounding areas. They also discuss national news, including the U.S. Supreme Court ruling on transgender participation in women's sports and local politics such as Minnesota Governor Tim Walz's pay raise. Call in with your thoughts at 701-213-0863 and follow Grand Forks Best Source for more local updates.

Show DescriptionWhat to do when you have more ideas than time, getting new musical gear, nerding out and getting excited about things, the state of conferences in 2026, Cursor being bought, and Dave's got a minimum viable design system idea. Listen on WebsiteWatch on YouTubeLinks FFConf Figma Config 2026 SpaceX locks in $60 billion Cursor deal Google Antigravity Devon: An open-source pair programmer Introducing Composer 2 @function CSS at-rule A tale of two browsers Google's Prompt API SponsorsNotionWrite custom tools for Notion Agents that generate assets, query live data, and hit any API. Listen for incoming webhooks from any app, then run workflows with Notion Agents, pages, databases, and external APIs. All of this, on a hosted runtime. Workers are isolated sandboxes managed by Notion, so the code behind your syncs, tools, and workflows runs on our infra instead of your servers.

(Jun 26, 2026) Nurses at Alice Hyde in Malone have a new contract that includes raises and AI protections; a colorful new mural now covers the side of a historic theater in downtown Au Sable Forks, bringing attention to a years-long effort to transform the building into a new home for the arts; and we get a preview of a Trans Pride punk show in Potsdam, and Independence Day celebration in Clinton County.

(Jun 26, 2026) A colorful new mural now covers the side of a historic theater in downtown Au Sable Forks. It's a small part of a years-long effort to transform the theater into a new home for the arts and a hub for the village. Also: New York and the federal government are engaged in dueling lawsuits over a new bill limiting New York's police agencies from working with ICE.

Gm! In today's episode, we're joined by Hardhat Chad, Foreman at ORE, to discuss the origins and evolution of ORE Protocol, including its transition from proof-of-work mining on Solana to its current grid mining system. We cover mining incentives, token emissions, protocol revenue and buybacks, proof of useful work, community governance, security improvements, quantum-resistant infrastructure, validator decentralization, and future plans for ORE's ecosystem, liquidity, and foundation structure. Enjoy! -- Follow Lightspeed: ⁠https://x.com/Lightspeedpodhq Follow ORE: https://x.com/ORE Follow Hardhat Chad: https://x.com/HardhatChad Follow Danny: https://x.com/defi_kay_ Join the Lightspeed Telegram: ⁠https://t.me/+QHlbNTNS4gc1ZTVh -- Get top market insights and the latest in crypto news. Subscribe to Blockworks Daily Newsletter: https://blockworks.co/newsletter/ -- Timestamps: (0:00) Introduction (1:43) ORE's Origin Story (7:18) Why Bitcoinomics Broke (10:49) Proof Of Work's Value Leak (12:57) Mining Design Tradeoffs (21:42) Revenue, Buybacks, And Burns (23:48) Rewarding Long-Term Holders (28:29) V4 Reduces Roulette Risk (35:33) Forks, Rugs, And Security (44:37) Future-Proofing ORE (52:45) Foundation And Liquidity Roadmap (55:05) Closing Comments -- Disclaimers: Lightspeed was kickstarted by a grant from the Solana Foundation. Nothing said on Lightspeed is a recommendation to buy or sell securities or tokens. This podcast is for informational purposes only, and any views expressed by anyone on the show are solely our opinions, not financial advice. Danny, and our guests may hold positions in the companies, funds, or projects discussed.

From the Williams Broadcasting Studio join John and special guest Emily Yearwood with Northern Outdoors in The Forks, Maine talking about whitewater rafting!

As the place where the Assiniboine and Red rivers meet, The Forks marks an important trade route for Indigenous people that pre-dates colonization by thousands of years. This National Indigenous Peoples Day, Unreserved is live from The Forks on Treaty 1 territory! Rosanna captures some of the magic of this place as communities come together to celebrate and share stories of resilience and resurgence.

Most of us know what a fork in the road feels like. You've got a heavy decision to make. There are at least two possible paths. And when you're at the fork, you know it's time to choose which way to go and that you will have to live with your choice. What can be so surprising is how often fear has been driving the decision-making over the years. Not us. Fear. Dressed up as reason, responsibility, and common sense. In this episode, Suzy revisits the Forks in the Road concept from Episode 335 but takes it somewhere much deeper. She shares a personal realization she had recently about her own 1982 fork in the road, when she was accepted into a university program in the Caribbean and turned it down. She'd told that story before. But this time, she finally connected it to experiences from earlier in her life that explained, clearly and with compassion, why that fear made complete sense at the time…and as an older and wiser woman over 40 years later, why it may no longer apply to the woman she is now.  Learn more here.

Forks BS! "Beat down at the White House" For easy access to download or stream past Common Sense UnSensored episodes visit - https://commonsenseunsensored.podbean.com/ Show is recorded at Grand Forks Best Source. For studio information, visit www.gfbestsource.com #PodcastsPolitics #gfbestsource.com #local #grandforksnd #grandforksbestsource #politics #news #hardhittingnews #legislature @grandforksndcommonsenseunsensored

Welcome to the daily304 – your window into Wonderful, Almost Heaven, West Virginia. Today is Thursday, June 11, 2026. #1 – From WVU TODAY - WVU researcher finds surprising phenomenon in NASA data from Mars A West Virginia University researcher has discovered the first evidence of a protective solar-wind phenomenon occurring inside the atmosphere of a planet that lacks a strong magnetic field. Analyzing NASA data from a 2023 solar storm hitting Mars, planetary scientist Christopher Fowler identified the "Zwan-Wolf effect" interacting much deeper than previously thought possible. The findings advance scientists' understanding of how the sun interacts with unmagnetized bodies across the solar system. Researchers say studying these space weather events is crucial for future space exploration, helping to keep robotic and human missions safe while protecting technology on Earth. Read more: https://wvutoday.wvu.edu/stories/2026/05/28/wvu-researcher-finds-a-surprising-phenomenon-in-nasa-data-from-mars #2 – From WVDNR - Wildlife Education Center offers a fun way to learn about nature The Claudia L. Workman Wildlife Education Center is the ideal day trip for families and nature lovers of all ages. Located at the Forks of Coal State Natural Area in Alum Creek, the center is home to exhibits that help visitors learn about West Virginia's native wildlife and what they can do to improve the health of wildlife populations at home. The land includes three miles of trails for exploring and learning about the flora, fauna, geologic and Coal River history of the area. Admission to the center and its grounds is free, so plan a trip today! Read more: https://wvdnr.gov/claudia-workman-wildlife-education-center/ #3 – From WONDERFUL WV - The Oglebay Good Zoo works to bring back the red wolf The Oglebay Good Zoo in West Virginia is actively working to help save the red wolf, the most endangered wolf species on the planet. Through its participation in a national breeding and sanctuary network, the zoo provides essential space and specialized care to rebuild a critically low population that was declared extinct in the wild in 1980. The expansion of the zoo's facilities with new breeding and holding habitats supports the broader goal of restoring genetic diversity to the species. Wildlife leaders say these intensive conservation and minimal-contact management efforts are vital to successfully raising wolves capable of someday being reintroduced into their natural ecosystems. Read more: https://wonderfulwv.com/on-the-edge/ Find these stories and more at wv.gov/daily304. The daily304 curated news and information is brought to you by the West Virginia Department of Commerce: Sharing the wealth, beauty, and opportunity in West Virginia with the world. Follow the daily304 on Facebook, Twitter, and Instagram @daily304. Or find us online at wv.gov and just click the daily304 logo. That's all for now. Take care. Be safe. Get outside and enjoy all the opportunity West Virginia has to offer.

Today we talk about election results, Karmello's conviction, & bombs over Iran For easy access to download or stream past Common Sense UnSensored episodes visit - https://commonsenseunsensored.podbean.com/ Show is recorded at Grand Forks Best Source. For studio information, visit www.gfbestsource.com #PodcastsPolitics #gfbestsource.com #local #grandforksnd #grandforksbestsource #politics #news #hardhittingnews #legislature @grandforksndcommonsenseunsensored

Topics covered in this episode: CVE-2026-48710: A Maintainer's Perspective daily-stars-explorer Markdown to pdf with pandoc and typst postman2pytest Extras Joke Watch on YouTube About the show Brian #1: CVE-2026-48710: A Maintainer's Perspective Marcelo Trylesinski suggested by Lee Luocks Short version: users of Starlette: upgrade to Starlette 1.0.1 security professionals: we can't treat open source projects like corporations This top link is a Starlette security advisory with the title Missing Host header validation poisons request.url.path, bypassing path-based security checks The CVE apparently caused some negative press targeting starlette. However, “the vulnerability came from the application pattern and the deployment, never from something Starlette intended.” A quote from an OSTIF article: “This bug is a classic “responsibility gap” where if this maintainer didn't patch, thousands of exposed projects would have to individually secure their projects. In doing this work, they've voluntarily taken on the responsibility to protect the ecosystem from long-term systemic harm. As with all open source projects, they owed us nothing and could have left this to be everyone else's problem and took the extraordinary steps of helping the ecosystem.” Both X40 D-Sec and Ars Technica expected immediate fixes and responses from Starlette. That's not good. We can do better. Michael #2: daily-stars-explorer Explore the full history of any GitHub repository.

Send us Fan MailThis week we're spotlighting The Cullen Chronicles: Legacy - 1935. We trace Lily Bellucci's fan-film origin story, unpack Jake Fogg's take on Emmett Cullen, and examine how the project pushes Twilight into darker horror territory. We also explore the Indiegogo campaign, preview the team's Forks festival plans, and celebrate the kind of sanctuary they hope the film creates for Twilight fans.Mentioned in the EpisodeThe Haus of Luce on YouTubeHaus of Luce on InstagramThe Cullen Chronicles: Legacy - 1935 by Haus of LuceThe Cullen Chronicles: Legacy - 1935Twilight (2008)The Twilight Saga: Eclipse (2010)The Twilight Saga: Breaking Dawn – Part 1 (2011)The Revenant (2015)Forever Twilight in Forks FestivalThe Forks Washington Twilight ConnectionSupport the showThanks for listening to Hack or Slash! Want more from the show? Join us on Patreon for extended episodes, bonus reviews, B-sides, watchalongs, behind-the-scenes extras, and more ways to help keep the show alive and slashing.Support us on PatreonYou can also hang out with us between episodes in our community spaces. Join the Discord for watch parties, episode discussions, horror recommendations, and general spooky nonsense.Join our DiscordFollow Hack or Slash:WebsiteYouTubeRedditInstagramTikTokHave thoughts on this week's movie? Leave a comment, send us a voicemail, or tag us online. We love hearing your thoughts on the movies we cover.Happy slashing!Music Credits: "Hack or Slash" by Daniel Stapleton

This week on NLR: Andy has a life changing revelation that impacts his relationship with Ducky, Elizabeth joins an interesting foot panel, Synesthesiacs are in the crosshairs, and much more! It's all covered on this week's Nobody's Listening, Right? Thanks to our episode sponsors: BIOLOGICA - Go to https://Biologica.com/NLR and get up to 32% off your first subscription order today!  GOODR - Head to goodr.com/NLR to claim $10 off your first order Support NLR Join Patreon for bonus episodes! Buy the Merch! Find us on Instagram Find us on TikTok⁠⁠ Watch us on YouTube Shop our Amazon recommendations Here Check out our True Crime podcast: BETH'S DEADLearn more at: https://www.patreon.com/cw/BethsDead ▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬ Chapters: 00:00 Intro 00:59 No Boundaries No Rules 02:02 On The Mic 02:56 The Marriage Suffered 04:04 Making Bids 06:51 Foot Kinks 09:26 Side Toe Jam Business 20:14 Ad Break: Biologica 22:35 What Is More Flattering 24:30 Synesthesia 27:01 Even vs Odd Days 30:11 Ad Break: GOODR 31:42 How Do You See A Calendar  33:35 Forks 35:17 We Support Ballerina Farms 41:07 Average Lifespan 46:44 Snoring 51:31 The Most Handsome Cat Ever Learn more about your ad choices. Visit megaphone.fm/adchoices

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!This was recorded before Railway suffered a major GCP outage on May 19, despite being a multi-AZ, multi-zone mesh ring, with HA fiber interconnects between their Metal GCP AWS, because workload discoverability was unintentionally still tied to GCP. All has been resolved with a post-mortem.Railway did not start as an AI infrastructure company.It was founded in 2020 years before agents became the default way people thought about deploying software. Jake Cooper, formerly at Bloomberg and Uber, started Railway with a simple obsession: the activation energy to ship something to production should be near zero. Push code, get a URL, iterate. No Docker files, no Kubernetes manifests, no Ansible scripts stacked on Ansible scripts.For years, this was a slow grind. Railway spent its first 18 months hand-acquiring its first 100 users with Jake personally greeting every Discord signup on a second monitor.Today, Railway has raised $124m and is growing very fast. A 35-person team supports 3 million users, adding roughly 100,000 signups a week. Their bare metal data centers have a 3-month payback period vs. renting in the cloud, with 70% margins funding aggressive cloud bursting when needed. The servers they own have actually appreciated in value as RAM prices have climbed basically meaning the value of their hardware now exceeds the capital they've raised.From rebuilding Railway's network overlay over a weekend to moving the vast majority of workloads onto its own bare metal data centers, Jake Cooper is trying to build a new cloud for an agent-native world. In this episode, Railway's founder and “conductor” joins swyx and Alessio to unpack why the next era of software infrastructure is not just “Heroku but newer,” what agents need that humans did not, and why the old deployment loop of Git, PRs, CI/CD, and static cloud resources may be heading for a rewrite.We go deep on Railway's infrastructure stack: own-metal data centers, three-month cloud payback periods, cloud bursting, data center debt, Railpack, Nixpacks, Temporal, feature flags, Central Station, content-addressable filesystems, agent-safe production forks, and why the CLI may become more important than the canvas in an agent world. Jake also shares the founder journey behind Railway, how the company survived losing $500K/month, why it now serves millions of users with only 35 people, and why he believes the pull request is dying.We discuss:* How Railway went from a slow six-year grind to adding 100,000 users a week* How Railway thinks about agents as the next dominant software species* Why agents need version control, observability, compute, storage, and orchestration at 1000x scale* The economics of Railway's own-metal data centers and three-month payback* How Railway uses cloud bursting while scaling its own infrastructure* Why data center debt can be a better tool than venture debt for infra startups* Central Station, Railway's internal system for clustering customer feedback and incidents* Why responsible disclosure and over-communication matter for platforms* Why feature flags, progressive rollouts, and shadow traffic are essential for agents* Temporal's strengths, pain points, and why workflows matter for agents* Railpack, Nixpacks, Nix, and lazy-loaded content-addressable filesystems* Why “cattle, not pets” may change if you can clone the pets* Why Railway is building a new cloud from scratch instead of copying hyperscalers* The solo founder path, focus, writing, and how Jake thinks about company buildingRailway:* Website: https://railway.com/* X: https://x.com/RailwayJake Cooper:* LinkedIn: https://www.linkedin.com/in/thejakecooper/* X: https://x.com/JustJakeTimestamps00:00:00 Introduction: What Is Railway?00:02:07 Jake's Path to Railway00:06:13 Railway's Six-Year Growth Story00:08:52 Rebuilding the Business After the Free Tier00:11:17 Agents as the Next Software Platform00:13:29 Railway's Infrastructure Philosophy00:15:42 Bare Metal, Cloud Economics, and the Compute Crunch00:17:22 Cloud Bursting and Five-Cloud Networking00:20:20 Data Center Debt and Infra Financing00:23:31 Data Centers in Space00:25:24 What Agents Need From Infrastructure00:28:24 CLIs, Canvas, and Agent-Native UX00:35:15 Central Station, Incidents, and Responsible Disclosure00:40:30 Safe Rollouts, SRE Agents, and Production Forks00:45:00 AI SRE, Specs, Code, and Tests00:48:24 Self-Replicating Infrastructure and the New Serverless00:53:18 Heroku, Temporal, and Workflow Engines01:04:07 Railpack, Nixpacks, and Lazy-Loaded Filesystems01:06:01 Coding Agents, Token Spend, and Roadmap Acceleration01:10:56 The Pull Request Is Dying01:12:28 Feature Flags and the Agent-Era SDLC01:16:15 Cattle, Pets, and Cloning Machines01:19:29 Solo Founder Lessons01:24:12 Focus, GPUs, and Building a New Cloud01:28:20 Closing ThoughtsTranscriptAlessio [00:00:00]: Hey, everyone. Welcome to the Latent Space Podcast. This is Alessio, founder of Kernel Labs, and I'm joined by Swyx, editor of Latent Space.Swyx [00:00:10]: Hey, hey, hey. Today we're in the studio with Jake Cooper of Railway.Alessio [00:00:14]: Conductor of Railway.Swyx [00:00:15]: Conductor at Railway. Yeah.Alessio [00:00:16]: Choo-choo.Swyx [00:00:17]: Do you actually have that anywhere, like on your business card?Jake [00:00:20]: We call some of our volunteer moderators conductors. I don't have a business card. We're not that big yet. At some point I will. I got handed a nice business card from the Supermicro folks, and I was like, “Damn, this is pretty official.”Swyx [00:00:30]: Business cards are coming back.Jake [00:00:32]: They're cool. They're hip. The conductor thing is good. We're trying to figure out what we want to call each other internally. Some people think it's super cringe and say, “You don't need a name for people internally.” Some people want to call each other something. We still don't have a really good one.Jake [00:00:55]: We've got New Railcrews, Trainiacs. Nothing has stuck yet.Swyx [00:01:00]: I like Trainiac. Trainiac sounds good. Railwayians. For those who don't know, what is Railway? Let's give people a crisp definition up front.Jake [00:01:09]: Railway is the easiest way to ship anything. You go to the canvas, or you talk with Claude, and you say, “Deploy a Postgres instance, deploy my GitHub repository, run this code,” and you're off to the races.Swyx [00:01:22]: You've got a nice animation on the landing page.Jake [00:01:24]: Thank you. None of my work, by the way. They don't let me touch the design stuff anymore.Jake [00:01:25]: We want to make it trivially easy not just to deploy things, but to evolve applications over time. Most tooling right now stacks entropy on top of entropy: Docker, Kubernetes, Ansible scripts, and all these other things. If we can version all of your software and keep track of all the changes, then we can make it trivial to clone environments, fork into a parallel universe, get copies of production data, get copies of any services, make changes, validate them, and collapse them back in without reproducing everything across a staging environment.The Railway Origin Story: From Uber Systems to a New CloudSwyx [00:02:07]: I was looking at your background: Bloomberg, Uber. Nothing immediately stands out as, “This guy is going to found the next great platform as a service.” What prepared you for Railway?Jake [00:02:21]: It was curiosity to keep going deeper. I started out on front-end stuff, working on Wolfram Mathematica and porting it over. Then I briefly moved to Bloomberg, then toward Uber and distributed systems, taking the Jump Bikes systems and moving them to a distributed system built on top of Cadence, the pre-Temporal Temporal.Swyx [00:02:44]: Which, by the way, I'm happy to talk about, pros and cons.Jake [00:02:48]: Totally.Swyx [00:02:51]: But let's do the Railway story.Jake [00:02:52]: It has been a continual step of wanting an experience. Whether it's walking up to a bike, unlocking it, and having it work frictionlessly, or something else, the depth required to make that happen follows from the experience. A lot of the work I do, and a lot of the team does, is in service of that experience. We fundamentally don't care how deep we have to go. We will swim to the bottom of the swimming pool to get the experience.Jake [00:03:17]: I don't have a physics PhD. I did an EECS degree. It has always been about figuring out the next step: how do we get there? That's what led to starting Railway for that experience and then moving all the way to bare metal data centers. I was adding patches to the kernel this week to get the experience there because I can see how much better it can be.Swyx [00:03:49]: Other patches to the Linux kernel this week?Jake [00:03:51]: Yeah. Not upstream. Our fork.Swyx [00:03:52]: That's a flex. Railpack? No, this is different. This is the OS on top of Railpack?Jake [00:03:57]: No, this is an actual kernel patch. It's always literally: what do we have to do to get that experience? Then figure it out. Anything is figureoutable.Swyx [00:04:10]: Would you send the patch upstream, or does it not fit other use cases?Jake [00:04:13]: Maybe. We have to work out the experience internally. It has to do with the storage layer we're building for some of the agentic stuff. Maybe it'll be useful upstream, but it's deeply useful for us internally.Open Source, Forks, and Non-Deterministic VersioningSwyx [00:04:29]: You mentioned open source before. How do you think about starting from open source, and then coding agents letting you do a lot more from forks of it?Jake [00:04:38]: GitHub's original sin is that it's almost a series of broken pointers. You have this thing, then you clone it, and now you've lost the whole upstream. How do we make it trivial for people to modify really small pieces of it?Jake [00:04:51]: We think of Git in a discrete sense: I've either made a change and merged upstream, or I haven't. What would it look like if it were percentage-based, a little more non-deterministic, or a stream of changes that users traverse as a percentage rolled out in general and then rolled all the way up?Jake [00:05:13]: We have the open-source kickback program and let you deploy templates because we want to make it trivial for people to version these shards over time. It solves a large problem around authentication, authorization, and security. NPM has a way to define, “Don't take any new packages.” The ideal end state is that you roll out progressively to users with the minimum impact zone and continue rolling up. JPMorgan should probably be the last one on the patch line, for all our sakes, because our money and livelihoods are there.Jake [00:05:53]: It's okay if Johnny Vibe Coder gets a broken patch because there's so much entropy in the system that the rubber has to meet the road at some point. You have to test at varying levels.The Long Grind: First Users, Free Tier, and Making the Business WorkSwyx [00:06:13]: I wanted to pull up this glorious chart, which is your usage or number of daily signups?Jake [00:06:22]: Daily signups, I think.Swyx [00:06:24]: You started six years ago. It was a slow grind, and now you're on a rocket ship. You say, “Don't doubt your fight and don't quit.” Maybe pick out certain points that were key inflections for the company.Jake [00:06:40]: At the start, it's about getting your first 100 users, hell or high water. We had a website and a support link. The support link was the Discord channel. I had notifications on with two monitors: the monitor I was working on and the other monitor with Discord. If anybody came in, I was immediately like, “Hey, how's it going?” It was rare, so getting those first 100 users to come back was the start.Jake [00:07:14]: Then you build a consultancy factory because users want all these things. You have to go back to the board and ask, “What is the actual product offering I want to build on top of this?”Jake [00:07:28]: VCs want charts that always go up and to the right, but in reality you don't necessarily want charts that look like that. For us, there have been periods of expansion where we add features to test use cases, and periods of compaction where we ask, “If the experience we have is good, how do we make it significantly better?” Maybe we strip out features that don't fit our ICP anymore.Jake [00:07:57]: The boom from 2022 to 2023 came from the free tier. Everybody under the sun was using it.Swyx [00:08:09]: A lot of Reddit bots and Discord bots.Jake [00:08:12]: And crypto miners. When you build an open product on the internet where anybody can sign up, the internet is a horrible place with so many things. You go through periods of asking, “How do I reach as many people as possible?” Then, “How do I fit the exact use case for the people who really matter and are really excited about this specific thing?”Jake [00:08:39]: Then there was a two-year period of making the actual business work. During the free-tier era, we were losing about half a million dollars a month.Swyx [00:08:59]: On a $20 million bank account.Jake [00:09:02]: On a $20 million bank account with maybe $50,000 a month in revenue. That's a horrible business. I don't know how anybody invested. But you have to go through it and say, “We have an experience people love, but the business has to work.”Jake [00:09:17]: There are two schools of thought. You can run the horrible business all the way up with bad margins, or you can go back and make it work. We've always wanted a super lean team. We're 35 people right now. It's very small.Swyx [00:09:36]: Supporting three million already?Jake [00:09:38]: Yeah. We're adding 100,000 users a week right now, so it's growing fast. We don't want to add headcount for the sake of headcount or throw bodies at problems. We want to build systems. It's hard to build systems during expansion because you're adding things to the system because people are asking for them or things are breaking.Jake [00:10:00]: We had to cut off the free users for a little while, rebuild the business, and make sure it worked. We want to reach as many people as possible because software is important. It's become difficult to create things in the physical world, so it's important to make it easy for people to build in the virtual world and have access to creation. But there are legs to that journey.Jake [00:10:30]: You can see divots in the charts. If you follow between 2025 and 2026, it's either summer or winter. People go on holiday with family.Swyx [00:10:50]: It affects that much?Jake [00:10:51]: Yeah. It's kind of B2C and kind of B2B. People are shipping constantly, then they stop. Our activation curve now shows more people activating on weekdays because we have more business users, so it smooths out over time.Agents as the New Interface to DeploymentSwyx [00:11:17]: Was there a point where you started prioritizing AI development or agent development?Jake [00:11:24]: We've prioritized agentic as a top-of-funnel thing. Over the last six months, we've deeply prioritized agentic as a mechanism to build and deploy things because we believe the curve is so steep and that is how people will build and deploy software.Jake [00:11:42]: It almost fundamentally doesn't matter whether this is dot-com or not because we're all on the internet anyway. If agents are going to deploy a bunch of things and we hit an inference wall at some point, we'll fix those problems. The dominant species over the next 10 years is that we've moved from assembly to C to C++ to JavaScript to words. You're going to need to close that loop.Swyx [00:12:13]: When you say this is dot-com, did you mean buying the domain, or the general case?Jake [00:12:17]: I mean the dot-com era, when companies had a huge run-up because people understood the internet was important. Then they hit bottlenecks, fundamental laws of physics, math didn't work, and everybody came back down to earth. But it didn't matter because the internet became so impactful. If you operate on a long enough time horizon, you should build these things anyway because you can see where it's going.Jake [00:12:45]: That's where I think a lot of agent stuff is. You get to a point where you're running thousands of agents in parallel. What is the inference cost? What is the compute cost? How do you make that efficient? How do you coordinate all this? We have issues coordinating humans; we don't even have good tooling for that. Now we have to figure out how to get agents to coordinate, safely version changes, and know when to raise their hand for someone to intervene. Otherwise it becomes an interrupt factory.Railway's Infrastructure Thesis: Network, Compute, Storage, and MetalSwyx [00:13:19]: Let's go right into the technical side. What are the core infrastructure or architectural beliefs of Railway that allow you to do what you do?Jake [00:13:29]: The primitives matter a lot for us. We need network, compute, storage, and orchestration around it. You need control over a lot of those things. We've talked a lot about how we don't really use Kubernetes because we want higher-order control to place workloads in very specific places.Jake [00:13:48]: The reason is that you have to be very efficient with agents: memory reuse and all these other things, or you're going to massively blow up your cost structure. Being able to rack and stack your own servers and build your own metal unlocks performance and cost. Experiences where you're running 1,000 agents in parallel are not massively cost prohibitive.Jake [00:14:13]: Token use and compute use are blowing up. Over time, those things have to get a lot more efficient. You can get a lot of margin to make those experiences solid by building your own metal. That's all in service of offering a differentiated experience to as many people as humanly possible.Swyx [00:14:51]: You have a data center in Singapore.Jake [00:14:53]: Yeah. We have two in every other region now. In Singapore, we're adding a second one in Q3.Swyx [00:14:58]: What's it like? I've never built a data center. Do you go to Equinix and say, “I want some slots?”Jake [00:15:05]: Yeah. Equinix. You basically go and say, “I want power and I want a cage.” They say, “Great, here's what it's going to be.” You rent the cage for a period of time, fill it with racks and servers, and hook up internet to it. That's all the pieces.Swyx [00:15:36]: Then you handle everything else.Jake [00:15:37]: You handle everything else.Swyx [00:15:39]: What's the math versus clouds doing it for you?Jake [00:15:43]: If we rented in the cloud, our payback period when we go to metal is about three months.Swyx [00:15:50]: Which is crazy.Jake [00:15:51]: It's nuts. That's four years of depreciated hardware. You're going to see a lot of this compute crunch because hyperscalers are buying up a lot of stuff. We're working directly with OEMs, resellers, and people building these machines: Supermicro, Dell, and others.Jake [00:16:11]: Upstream, there's a bunch of supply pressure. When we raised our last round, between deploying capital for servers and now, the amount of money we've raised is less than the amount of money we have in the bank plus the value of the servers because the servers have appreciated as RAM has gone up. It's nuts how valuable hardware has become.Jake [00:16:50]: If you look at hyperscalers, they deployed around $80 billion of capital expenditures this year, and next year will be more. That's a massive infrastructure build-out. You look at that and think it's crazy that they're spending way more than the Manhattan Project. But if every person is going to run dozens or hundreds of agents in parallel, you have no conceptual idea how much compute is required to make that experience happen, even if you're deeply efficient and sharing resources. And that doesn't even count inference.Swyx [00:17:22]: How do you plan the build-out? The growth chart is so vertical. Are you usually at 100% utilization as soon as racks are live? How far ahead are you planning?Jake [00:17:33]: We still maintain cloud presence for bursting. We work with AWS, GCP, and a few other clouds. We can rent, and then the moment we get space or power, we compact those workloads off the cloud. We started on the clouds, then built a system to migrate to our own metal. There's nothing that says you can't continually do that again, and that's exactly what we do. We never want to be compute constrained.Jake [00:18:09]: At the start of the year, we actually became compute constrained because one upstream provider wasn't able to give us quota at the rate we needed, and the hardware was slower. I spent a weekend rebuilding our entire network overlay so we could straddle five clouds: Oracle, AWS, ourselves, GCP, and one other one. We can do more than that now.Jake [00:18:38]: We got into a spot where we were trying to pack instances tight because we couldn't get enough compute. That led to a few reliability issues, which are now past us. I made a tweet pointing out that it's becoming harder and harder to acquire compute at the rate these models need to acquire compute. We got bit by it.Swyx [00:19:15]: How do you think about pricing knowing you might not have your own metal available at all times? Are you pricing assuming you need extra margin if you end up going into the cloud?Jake [00:19:26]: Because we've built out our metal data centers, our margins on metal are around 70%. We can deeply subsidize the cloud business if we want to scale at a reasonable rate. We have a few levers: metal, which makes the margins; cloud burst; debt to buy servers; and venture capital. It's an interesting operational problem: how much cash do we have, how much should we raise, how quickly can we deploy it, and can we scale revenue as quickly as we scale compute?Jake [00:20:05]: If we continue making it trivially easy for people to build and deploy, then the faster we close that loop and the more operationally excellent we are with capital, the faster the business can scale. It's almost a straight linear deployment rate.Financing Infrastructure: Hardware Debt, VC, and Operational LeverageSwyx [00:20:20]: I think infra startups raising debt is a tool people don't utilize enough or know enough about. What can you tell us about that? Is it secured against your CPUs?Jake [00:20:32]: It's secured against our hardware.Swyx [00:20:37]: What rates do you get? Who are the lenders?Jake [00:20:39]: We pay prime plus a spread, and we can refinance any of the debt as rates go down. The terms are pretty good. The unfortunate thing is that Twitter has no nuance, so people say, “Venture debt bad.” But as with all things, there are specific tools and areas where you can be deliberate instead of using one tool as a hammer. Venture capital is not the hammer for everything. You have to explore and figure out what works.Swyx [00:21:12]: VC is usually the most expensive financing you can get.Jake [00:21:15]: Yeah. I also think people think about VC incorrectly from a capital-raising perspective. Most people think, “How do I raise as much money as possible from whoever is probably the best I can get at that time?” That's close to right, but what we've tried to do is figure out what unfair advantage we can buy with that equity.Jake [00:21:34]: It's the most expensive equity you're going to give away at that point in time, assuming the company keeps getting better. How do you use it to work with someone stellar who complements you? In the seed stage, I had never started a company. Ray Tonsing had good advice, and I could text him all the time. He was really fast. Awesome.Jake [00:22:01]: Then with John and Erica at Unusual, they said, “You roughly know what you're doing building a product. We'll mostly leave you alone and be available for advice.” Amazing. Then we got to Series A and the business was an operational tire fire because we didn't know how to scale a business. Work with Erica, and Jordan is over at Redpoint, so bonus.Jake [00:22:28]: Now we've raised from TQ and FPV as we're moving into enterprises. Every step of the way, we've asked: who can we partner with at this specific time to unlock the next section of the journey? I don't know enterprise sales. As an engineer, I can eyeball what features we might need, and we have wonderful people internally who can help. But you want boardroom dynamics where everyone is aligned and asking, “How do we win this?” instead of bickering about strategy.Data Centers in Space and the Physics of ComputeSwyx [00:23:31]: You had a tweet about data centers in space. Why no data centers in space?Jake [00:23:37]: It's not “no data centers in space.” My hot take is that I think it is solvable. I've just never seen anybody solve it.Swyx [00:23:49]: You said, “How are you going to dissipate that much heat in a vacuum?” You're making a physics claim.Jake [00:23:55]: I haven't seen anybody prove how you're going to dissipate that much heat in a vacuum. It doesn't mean it's not possible. It just means nobody has brought it up yet.Swyx [00:24:05]: Astrophage.Jake [00:24:06]: I don't know what that is.Swyx [00:24:07]: The Martian thing. Okay, you're very logical.Jake [00:24:09]: It could work. A lot of people are putting the cart before the horse. They say, “We're going to put data centers in space.” Okay, but how? “We have time to figure it out.” It's like in The Martian where they ask how they're going to intercept something and say, “We'll figure it out.”Swyx [00:24:36]: Making a bet on human invention is weird because you blind trust that it can be solved. But with physics, there are first-principles bounds you can put on it. Maybe not. Maybe you're asking to travel time or break a fundamental thermodynamic law.Jake [00:24:57]: I don't know how VCs do this either. How do you know what's not possible and a grift versus what's possible but sounds completely insane? “We're going to put data centers in space.” Coin flip as to which it is, and I guess you'll know in 10 years. That's one cycle.What Agents Need: Versioning, Observability, and 1,000x ScaleSwyx [00:25:23]: Moving back to agents. The branching, fast spin-up, and orchestration you do feels like pre-work that happened to be exactly what agents want. What do agents want differently than humans?Jake [00:25:37]: They want the ability to version things. It's not that different; it materializes slightly differently. Agents want a way to test changes incrementally. Engineers have feature flags. Is there a reason agents can't use feature flags? I don't think so.Jake [00:25:54]: They want version control. Can we use Git or not Git? That one is up in the air. I think something outside Git will emerge for how we version these things over time. They need observability. You need to query what happened, when it happened, which steps failed, traces, logs, metrics, and all the rest. They need network, compute, and storage. They need to write files, save files, iterate on files, and snapshot file systems.Jake [00:26:25]: A lot of what humans needed is in line with what agents need. Branching and forking are not different; we're just moving 1,000 times quicker. It can look like you need something massively different, but what you need is something massively better than what existed. You need orchestration massively better than Kubernetes. You need networking probably better than Envoy. It goes all the way down the stack.Jake [00:26:55]: If the workload profile doesn't change so much as it gets massively compressed because you need thousands of these things, what assumptions change? etcd is going to melt. You need to replace it with something. You can go all the way down the stack and say, “That part has to change, that part has to change, and that part has to change.”Jake [00:27:19]: The interesting thing about the super-exponential curve is that you have to build systems where you can rip out those parts at any time because a new bottleneck might emerge. You get good at parallel agents, and a different part of the system breaks. So it's similar to what humans needed, but at 1,000x scale.Jake [00:27:55]: How do you do code review in the age of agents?Swyx [00:28:00]: You throw more agents at it.Jake [00:28:01]: You don't. But then who reviews for CVEs and all these other things?Swyx [00:28:07]: More agents.Jake [00:28:08]: And that's how we hit the inference wall. You can continually throw agents at the problem, but I think there's a limit to the number of agents you can throw at a problem.CLI, Agent Handles, and Closing the LoopSwyx [00:28:24]: You already had a CLI before it was cool. How is the shape of what you're exposing changing, if at all?Jake [00:28:28]: CLIs have always been cool. The CLI changes because we think about how to give Claude, Codex, ChatGPT, or any model a handhold.Jake [00:28:50]: A CLI is a single command: deploy, get logs, and so on. Things that were prohibitively annoying to humans are not annoying to agents. They're nice. If I handed you a CLI with 40 arguments and 600 flags, you'd think, “I'm never going to use all of this.” But if you hand it to an agent, it says, “This is excellent. I have so many handles to work with.”Jake [00:29:24]: If you're going to expose things to agents that way, you want as many handles as possible where they can get information, query dynamic information, and close the loop quickly. Most problems right now are about how to close the loop as quickly as possible. Where does the agent get stuck, and how can you remove that?Jake [00:29:49]: Telemetry is important. If you can tell where the agent gets stuck from the CLI and say, “12% of people deviate from the happy path because of this, and now I add this argument and drive it down to 2%,” you massively increase the rate of loop closure.Jake [00:30:03]: That's how we think about not just the CLI, but every point in the dashboard. It's a user journey: I hear about Railway. I get something deployed. I get my first green build or aha moment. I see an endpoint, logs, whatever. Then I iterate. The iteration loop is indefinite. The user wants to deploy a new thing, a Postgres instance, change code, and keep iterating.Jake [00:30:36]: If you focus on the iteration loops and what's blocking them from closing quickly, one thing we say internally is: you never want to be waiting on compute anymore. You always want to be waiting on intelligence. If you're waiting on compute, there's a bottleneck that needs to be destroyed because eventually that bottleneck becomes so large that another workflow emerges to change it.Jake [00:31:04]: We've built a product where you push code, build it, and so on. But I fundamentally believe the push-pull loop is going away. We'll get to a point where you make a small change in production, that change is versioned across your infrastructure, you're working alongside copy-on-write versions of your database and infrastructure, and then you merge it in and it's instantaneously live. That's the holy grail of loops. The push-pull-rebuild thing is a point of friction that we're removing entirely.Canvas as Output: Dashboards, Context Anchors, and HyperstructuresSwyx [00:31:43]: It's incredibly fast. If anyone hasn't tried it, that fast feedback is great. My hot take is that Railway was famous for its canvas, which visualizes your infrastructure and lets you manipulate it visually. But that was for humans. For the next phase of growth, Railway CLI is more important than canvas.Jake [00:32:05]: The canvas is funny because it's a mechanism to show changes over time. You're right that previously we used it a lot as an input. Moving forward, its goal is more like an output. You would go to the canvas, make changes, see them, and watch your infrastructure evolve. Now agents have access to the CLI and can make those changes. So the canvas becomes an output: what information does the human need at this moment to make suitable decisions about control requests? Do I approve this or not?Jake [00:32:57]: It also has to be an anchor for your context, a port in the storm. Think of it like layers in a file system. You start with a project, then drill down into services, then into a function or code, because you want to represent the entire thing not just in your head, but in the canvas. Other people can share that representation, think on the same wavelength, and move quickly.Jake [00:33:33]: A lot of organizations get in trouble as they scale because all the context lives in someone's head. “How does this microservice work?” “I have no idea; go ask this person.” Then you have whole categories of products built around context discovery. A lot of that melts away if you have a solid hierarchy and can infinitely nest services, code, context, and everything else all the way down. That's what lets you build these structures over time.Jake [00:34:18]: It's also what lets us build what I've called hyperstructures: things that are way bigger. You look at the Golden Gate Bridge and ask, “How did we build that?” There's a meme that we lost the technology. To some extent, yes, because the coordination that built those things evolved and changed. We lost some of the art of building structure as we jammed everything into Slack.Swyx [00:34:52]: But you jam everything in Discord.Jake [00:34:53]: Same point. It doesn't matter. It's message passing and interrupts, message passing and interrupts.Swyx [00:35:00]: So you're arguing there should be something better and more structured than Slack?Jake [00:35:04]: Yeah. For sure. I think Slack is awful, and Discord is awful too.Central Station: Context Routing, Support, and Incident ClustersSwyx [00:35:09]: This is the equivalent of my mom test. What have you done that has your solution to this?Jake [00:35:15]: Internally, we've built a tool called Central Station that aggregates all the context from our users. Every piece of feedback, every customer support item, everything gets aggregated into clusters. If an incident is brewing, we can determine how many users are affected and break off a discussion based on that.Jake [00:35:40]: That is more helpful than long-running channels where you're trying to decide which channel to put something in. If you can dynamically aggregate information and dynamically route it to the right person based on context, it works better. We know internally that these four people are close to networking. If we see a networking thing, we can drill it down to those four people. If it's with this part, we can look at the commits. This is no longer a manual process internally.Jake [00:36:13]: If you go to station or help.railway.com, that's why we built it. We wanted to scale with a massive amount of leverage by aggregating feedback.Swyx [00:36:27]: This is built in-house?Jake [00:36:28]: Yep.Swyx [00:36:29]: I remember helping out on this one with Angelo in 2023. You scale a lot with a very small team.Jake [00:36:38]: Yeah. We're about 10 times bigger now.Swyx [00:36:40]: You have your full developer code here? Very cool.Jake [00:36:44]: If you go to railway.com/stats, we expose this as a pub-sub-able thing. It's all real-time metrics. There's a way to get it as JSON somewhere if you care.Jake [00:37:01]: We're big on trying to build everything in public and talk about what we're working on. We've had issues in the past, and we'll say, “Here's how we're fixing these things.” We've gotten compliments and flak for incident reports. We're always trying to make them better and talk with people.Incidents, Disclosure, and Progressive RolloutsSwyx [00:37:20]: You had a big one recently. I liked that it was scoped to 3,000. You presumably used Central Station. Talk through what happened and how you address it internally as a team.Jake [00:37:38]: Internally, this one really sucked. It had to do with an upstream provider that didn't do the behavior it said it documented, which is unfortunate given they wrote the RFC for how the behavior should work. We rolled those things out, and Central Station caught it initially when a couple users said caches weren't invalidating. We turned it off immediately.Jake [00:38:03]: When you roll out to a large user base of three million people, you get a lot of disparate behaviors. We tested in staging and had tests, but we hit an edge case. We've hardened those systems, and now we can make that better. But it was a tough one.Swyx [00:38:39]: I always wonder how private disclosure is supposed to work if people find an issue. Are they supposed to contact you first? When you run a platform, these things will happen. What channels should people pursue to quietly resolve it before it becomes a bigger incident?Jake [00:38:59]: There's responsible disclosure. We err on the side of over-disclosing and letting you know something is wrong versus having your provider gaslight you. We've erred on sharing those things more publicly, even if they impact a small subset of users. That's a decision we've made internally. We have four values. One is honor. The honorable thing is to notify people to the widest degree at which they may have been affected or there was an issue, and then confront it head-on: why did it happen, what can we do better?Swyx [00:39:45]: Not the whole user base. That's because of incremental rollouts and other things?Jake [00:39:50]: Yeah. Progressive rollouts.Swyx [00:39:54]: That should be the norm at all large platforms.Jake [00:39:58]: It should. A variety of companies do this. There's the quote that Meta runs 10,000 different versions of Meta. To our earlier point about agents, they need the same thing. They need shadow traffic and all these other things. We've built so much ceremony around production being sacred that we need to make it trivially easy to test different behaviors in a safe environment. Then you can make mistakes in a safe environment.Safe AI SRE: Customer Agents, Forked Environments, and Production ParityAlessio [00:40:30]: Do you see a world where these things get automatically caught, not necessarily by your agent, but by your customer's agent? The cache invalidation issue seems easy to check if you know to look for it.Jake [00:40:44]: It's hard because to determine it, we almost need to hook into your observability infrastructure. That's why we have the template loop on the platform: so you can roll things out progressively. You can roll out to Johnny Vibe Coder initially, or push a shard that someone consumes at their own leisure. Or you can roll it out over weeks: 0.1% of people, 1% of people, early adopters, then all the way up. That's the non-deterministic version control we talked about earlier.Jake [00:41:30]: I believe that's where most things should go, because most companies end up building staged rollout systems in-house. It's the same thing built again and again at every company. There's a massive opportunity to consolidate developer debt.Alessio [00:41:45]: You should have a free tier. Model providers give free tokens if you let them use the data. You could give free compute if someone is the number-one shard that goes out and lets you plug into their observability.Jake [00:41:55]: We do that. That's why we talked about the impact on 3,000 people. We start with lower-impact people. Larger companies on the platform are last to receive those rollouts so they have a version of the platform that's deeply stable.Alessio [00:42:16]: I have three services, so I'm sure I get the first rollout. You can nuke my thing at any time. There are all these SRE agent companies. Observability people also want agents that fix upstream problems. You have your own agent in the canvas now. How do you see that playing out?Jake [00:42:39]: It's the stacking entropy problem. If you don't have primitives to make iteration in production safe, it becomes difficult. If you're an observability provider saying, “Here's the fix to this error,” assume 80% are good and make sense. But in the last 20% long tail of complex issues, if you let somebody stamp it, you create an opportunity for an incident.Jake [00:43:08]: That's why forked environments are important. People have staging, but it always drifts from production. You need primitives, workflows, and experience built first-party on the platform so you can fork any service at any point in time.Jake [00:43:33]: I think of the canvas as a sheet of transparency paper. The agent is a little guy you push up into the canvas. It should say, “I need to copy that service and that service so I can test these two things.” It gets a read-only copy of production. Anything that's PII gets marked as a transform when we clone the database, create a copy-on-write version, or read from it. Then the agent makes changes and asks, “Does this actually work?” as close to production as possible.Jake [00:44:22]: That's how close you have to be, or you get massive drift. The system becomes unstable. You see this with massive systems built on Docker for local, Kubernetes for production, and a specific thing for something else. That complexity slows developers and becomes unstable at scale, making it hard to iterate. We want to compress that way down and say, “As close to prod as possible is where we want to be.”From AISRE Skeptic to Agent BelieverSwyx [00:45:00]: I was texting Erica for questions, and she says you were originally not a believer in AISRE. Have you come around on it?Jake [00:45:10]: I flipped, but I'm still not a believer in AISRE if you don't have the primitives to make it safe. If you unleash AISRE on production infrastructure without safe primitives for copying volumes and making sure things are fine, it's going to nuke your production database. It's not a matter of if, but when. I'm a big believer in making those loops safe.Jake [00:45:33]: I was a deep AI skeptic until 2023. In 2024, I thought, “Maybe I can roughly make this thing do it.” In 2025, I thought, “Now I can hold this.” Over winter break, everybody came back saying, “It's almost impossible to hold this.”Swyx [00:46:01]: Did you see this on the Claude docs? CloudBot? OpenCloud?Jake [00:46:06]: It's gotten to a point where it's harder to hold it wrong than to hold it right. There's a scene in Avengers where Vision picks up Thor's hammer and says it's terribly well-balanced. It self-balances and works well. I'm a deep believer at this point that this will be the dominant species: assembly, C, C++, JavaScript, words.Swyx [00:46:35]: It feels like a big jump.Jake [00:46:37]: It is. But it's not like you abandon CPU-based discrete logic and move straight to fuzzy logic. You need both. Your skills should call code or applications or some static structure. You can use skills to distill what the procedure should be or how the code should act.Jake [00:47:02]: I'm coming to a thesis: you need three points. You need a clear spec defining the system, the code, and the tests. When you say it out loud, if you've been in engineering long enough, you're like, “Of course. That's an RFC, tests, and code.” But they all matter. Having them together lets them reinforce each other: the spec and tests match, but the code doesn't, so reconcile it. Or the tests and code match but the spec doesn't, so reconcile that. That's the iteration loop.Jake [00:47:41]: That's why you're seeing people talk about software factories, docs, and reconciliation. Some of that is architectural astronomy if you don't implement it, but that loop is where most things will end up.Swyx [00:48:07]: For listeners, we've been talking about this on the pod for three years: the holy trinity of specs and tests. Itamar Friedman from Qodo is the reference if people want to look it up.Self-Modifying Infrastructure and the End of Push-Pull-RebuildSwyx [00:48:18]: One thing I want to mention on the OpenCloud idea is self-modification. I don't know how Railway would support it, but I have my OpenClaw, and I just tell it it has the Railway CLI and can do whatever. In theory, whatever capabilities or new infra it needs, it can call the Railway CLI, provision it, and add it to itself. The agent can modify its own infra.Jake [00:48:45]: It's nuts. I have a loop set up where you put the Railway CLI on top of something that runs on Railway. You're authenticated as whatever the current box is, and you can make any changes to it. Then you call Railway deploy, and it deploys itself.Jake [00:49:04]: It's like: “I need to spin up this instance of this environment. I already exist in this environment. Excellent, I have access to a Postgres instance now.” That's where we want to go with agentic, self-replicating infrastructure. That's your loop: iterate in production. You continue making changes. If it works, merge it upstream. If it doesn't, throw it away.Jake [00:49:37]: How do you make throwaway copies trivial to spin up and super cheap? The era of “I have an AWS instance with four vCPU and 16 gigs of RAM” is going to get destroyed. If you do that for agents, you need a thousand of those machines. It's prohibitively expensive compared with what we've spent a ton of time figuring out: the atomic unit of deploy, whether you call it isolates, sandboxes, or something else. Only pay for what you use, spin up instantaneously, and close the loop as quickly as possible.Jake [00:50:15]: If the system can self-replicate safely and say, “This is my environment, I'm making these changes,” it can come back with, “Does this look good? This is a new state of infrastructure given this prompt. I think I've solved it.” Then you go back and say, “Actually, it looks different.” It does the loop again. Then you say, “Cool. Apply.”Swyx [00:50:38]: That's retroactively obvious, which is the most useful kind. Any other comments on agent deployment on Railway?Jake [00:50:51]: It's getting better every day. I'm on X or Twitter. You can always yell at me about the parts not working as well as they should, because plenty of things should work way better.The New Serverless: Stateful, Long-Running, Pay-for-What-You-Use LinuxSwyx [00:51:04]: At this stage, when people want massively or embarrassingly parallel compute, they usually talk serverless. I feel like there's a new serverless compared to the previous five years of serverless. You're in that new bucket. Do you have comparisons or philosophical differences you want to call out?Jake [00:51:31]: It's somewhere in between. It's the ability to run stateful, long-running workflows or executions.Swyx [00:51:42]: Vercel has Fluid Compute, Cloudflare has some container thing, Google has App Runner and others.Jake [00:51:55]: That's where everything is roughly going, and it's why we've been working on this for six years. We believe users need access to a computer: a box that speaks Linux. They need to deploy what they want. Other systems change the surface area of what you can build. For us, users need a computer and need to deploy anything they truly want. That's why we've focused on the primitives: network, compute, storage. If we give you those and expose them so you can run things indefinitely, that's where we believe it's going.Jake [00:52:43]: Twitter has no nuance, so everyone says “servers” or “serverless.” It's always somewhere in the middle: I want to run it for a long time, but I don't want to provision the resource statically or pay for things I'm not using. That's been our thesis from day one: pay only for what you use, run it indefinitely, and it is full Linux.Swyx [00:53:12]: That's why I like the naming of Fluid. It's fluid. Flexible.Heroku, Focus, and Carrying the Torch Without Becoming the PastSwyx [00:53:18]: Another milestone is the Heroku official deprecation. You're one of the presumptive new Herokus. “New Heroku” has been a category for as long as I've been in developer tooling. It's finally happening. What was that like? Any behind-the-scenes of, “This is the moment”?Jake [00:53:42]: You have people where you're like, “You were running stuff on here? You, as this company?” It's crazy that names you would know are running on it and now coming to us saying, “We want to move a lot of this off.”Swyx [00:54:00]: Any behind-the-scenes on why Salesforce let Heroku stagnate?Jake [00:54:05]: I can only guess. It's hard when it's not your business. Salesforce's business is to build a great CRM. That's their focus. Then you acquire a compute business as an offshoot. A lot of early Meta people talk about focus. Boz has a write-up about how in the early days of Meta they had no money, so they were forced to focus. Then they turned on the money tree and had no reason not to split their focus.Jake [00:54:52]: But that dilutes your product. You get offshoots where you ask, “Is this the focus of the business?” If it's not core, it languishes. A lot of companies get in trouble when they split focus because they're fighting a multi-front war, not just externally but internally for alignment. Where are we going? What are we doing? What is our purpose?Jake [00:55:24]: If you're Salesforce-built and mission-driven, you want to work on Salesforce. Heroku is off to the side. It's not core to the business. Getting resources, budget, focus, and alignment internally becomes hard. It was a matter of time.Swyx [00:56:06]: Kudos for them to call it out instead of leaving it unknown.Jake [00:56:12]: Their release was a little odd. They called it out, but they didn't say they were shutting it down. Behind the scenes, I think they issued messages to people saying they should close accounts and that they were going to deprecate and remove things over time.Jake [00:56:30]: It's crazy because some of my first deployment experiences were on Heroku. You start with dragging things into an FTP server, then you try to get a deploy working, and then it's Heroku. It was the on-ramp for us. But the wheel turns. New things emerge. We're happy to carry the torch for a lot of that. But we don't want to be the new Heroku. We want to be the way people build and deploy software, and ultimately the way people monetize software over time.Swyx [00:57:19]: It's still a big crown to be the new Heroku. There are 50 companies that fought for that.Jake [00:57:23]: Everybody is holding some portion of it. We're happy to support people and companies. The platform works differently. The game loop is similar, but we've been dogmatic about where these things are going: primitives, agents, fan-out. Some things fit; some workflows need to change. We have an approximation of Heroku pipelines with the environment system. It's exciting. We've got a ton of people we can support, and it's growing a lot.Temporal, Workflow Engines, and State MachinesSwyx [00:58:12]: I have one more technical question about Temporal. I've sold my shares. You're a power user and one of our earliest customers. I met you through Temporal. You built on Temporal. You have complaints. This may be the most neutral and informed conversation anyone will hear about Temporal without someone working at the company.Jake [00:58:39]: That's fair. I've used Temporal for almost 10 years because of Cadence at Uber.Swyx [00:58:52]: Give people a sense of what Cadence was at Uber.Jake [00:58:57]: Cadence was the precursor to Temporal. It powers trip actions, rides, when you rent a Jump bike or scooter or car. You're running workflows for a period of time and saying, “This ride will run indefinitely until it finishes.” You attach information: you paused in this zone, so add this charge to the bill. When you end the trip, the workflow is done. That experience was powered by Cadence at the time.Swyx [00:59:34]: I used to say it's like programming the entire user journey top-down as one function.Jake [00:59:39]: It's a powerful idea and important. It's also important for the next phase of the agentic journey. You want an agent to do a specific task, be complete or incomplete on that task, and move on to the next thing. You need a way to manage workflows dynamically.Jake [00:59:59]: Temporal was always great in theory, and great when you got it working the way you wanted in production. But it required you to model the entire journey in your head. If you didn't, you could cause issues where replaying the state of the workflow causes non-determinism.Swyx [01:00:25]: Because it works on deterministic workflow history.Jake [01:00:28]: Exactly. I describe it as a jet engine. If you know how to operate it and run it, it's great. But you can't hand it to people trying to build complicated things if they don't have the whole state in their head.Jake [01:00:48]: We run our whole deployment pipeline on top of it. That's a reasonably complicated workflow: pre-commit hooks, signaling, queuing, and all the rest. We ran into the same thing at Uber. As you express a large workflow, it gets more complicated, with more states in the state machine that you have to map back to the workflow.Swyx [01:01:15]: It's a lot of ifs.Jake [01:01:16]: Exactly. At Uber, we built a system for doing the state machine and testing it. We've started to build some of those things here because it's grown heavily. It's not quite love-hate. When it works well, it works super well. But if someone who doesn't have full context puts something into the system that invalidates state or causes non-determinism, or spins off a ton of activities, you have to keep track of underlying SRE knobs like activity slots. Those should scale with memory, vCPU, and so on. It becomes a bear to scale.Swyx [01:02:10]: You need a capable sysadmin running things behind the scenes. If you moved off, what would you do?Jake [01:02:19]: We'd build our own workflow engine. We have a few internally that we've worked on.Swyx [01:02:27]: This is one of those classes of things you typically wouldn't vibe code, but I'm wondering if you can.Jake [01:02:33]: I still don't think you should vibe code it. You still want to run decent tests to make sure it works.Swyx [01:02:39]: Timo didn't invent that from scratch either. There are libraries you can run. On top of that, it's just a state machine that you have to map out. Ultimately, you define the instructions you want and run them through a state machine.Jake [01:03:00]: It's very doable. Workflow stuff is interesting. Restate is doing neat stuff here.Swyx [01:03:10]: You're tied into JavaScript. Are you a JavaScript maxi?Jake [01:03:13]: Internally, we have TypeScript, Rust, and Go. We don't add more languages. Actually, we have a little C because we write BPF code and hooks. But those are the languages.Swyx [01:03:28]: Is this for sidecars?Jake [01:03:32]: No. It's for the networking stack, volumes, and things like that. We use TypeScript a lot because it powers the dashboard, but we're moving a lot of workflow stuff off the dashboard stack and into the infrastructure stack.Railpack, Nixpacks, and Content-Addressable FilesystemsSwyx [01:04:00]: Cool. Any other technical infrastructure stuff? Railpacks?Jake [01:04:07]: We built an engine for determining dependencies based on source code. It's called Railpack. We built the first version, Nixpacks, on top of Nix, and then we moved.Swyx [01:04:17]: People have been trying to get me to adopt Nix and NixOS for four years. Is it ever going to be a thing?Jake [01:04:23]: I don't know. We're excited about it, but it has pain points. Think of it as a stack of versioned binaries at specific slices in time. If you want version X and version Y, you bloat the package space, which blows up image size and makes real-world workloads difficult.Swyx [01:04:53]: But you content-address it and cache it. In theory, there are optimizations.Jake [01:05:00]: In theory, yes. But with a large enough user base and disparate enough machines, you run into a problem Meta described in the XFAAS paper, their internal serverless system. It becomes difficult at scale unless you break out specific runtimes.Jake [01:05:24]: We didn't want to do that because we wanted to truly allow you to deploy anything. That was our initial thing with Nix. But we've moved toward interesting work around content-addressable file systems that can lazy-load anything from any point and page it into memory.Swyx [01:05:48]: Amazing.Jake [01:05:49]: The future is very bright. It's crazy, and it's going to be nuts.Coding Agent Spend, Roadmaps, and Token ROISwyx [01:05:54]: Founder journey stuff?Alessio [01:05:56]: Your cloud usage: you tweeted you're going to spend $300K this month?Jake [01:06:01]: I think we got to $200K.Alessio [01:06:02]: Coding agents?Jake [01:06:03]: Yeah.Swyx [01:06:04]: Across the company?Alessio [01:06:05]: You only have 35 people, so I'm sure they're not all spending $10K a month. What's the distribution?Jake [01:06:10]: I think I'm at about $25K. We have power users all the way down. We came back from winter break, and I basically said, “If you're writing code by hand, you're doing this wrong.” The tools are good enough now that you can move extremely quickly. There are issues and pain points, but you should be reviewing the code you are writing instead of writing it by hand.Jake [01:06:40]: Architectural patterns matter more now than ever, but you shouldn't spend your time generating code you would write. If you know how to write it, ask the agent to write it and reconcile it until it looks like you would have written it yourself.Jake [01:06:58]: People misconstrue my propensity to push people toward agents as connected to our growth and some reliability bumps. They're not necessarily related. The tools are good enough to move extremely quickly and build things way larger than you could before.Jake [01:07:19]: To the earlier point about cooling data centers in space: I don't know. But with software, you can ask, “How would I build block storage from scratch? How would I do these things?” I have ideas because I have history and have read papers. Let me work them out and build massive test benches with thousands of tests, because those are now free to author. If you're not using AI systems to speed-run your roadmap and reconcile your existing system onto the future, you're missing a large point of what's happening.Alessio [01:08:12]: What's the path to spending $3 million a month? Is it bound by ideas and things customers can absorb?Jake [01:08:19]: For most companies, it's bound by deployment at this point. That's why we've seen a massive boom in users and companies, from Fortune 50s down, asking how to get developers to move faster. You'll probably hit your CFO before any technical limits because they'll look at the eye-watering amount of money spent on tokens. Inference costs have to come down, but we're inference constrained now. There will be price discovery around what makes sense for an org to adopt.Jake [01:09:06]: I think you'll end up with the F1 driver concept. If someone is really adept at these things, it makes sense to put them in a $3 million car. If they're not, it probably doesn't make sense. You'll take a few people and say, “You can drive the F1 car. We need to go in this direction. Figure out if it works and prototype it.”Jake [01:09:33]: We've done some of that and vastly accelerated our roadmap. We thought we'd ship something in a few years; now we can probably ship it in a few months because we validated it and don't have to build it incrementally. We can skip steps and move toward our vision.Alessio [01:09:58]: A lot of people are realizing the roadmap doesn't always have a business impact, so they say tokens are too expensive. But if your roadmap were built to make more money by the time you built it, you'd have token pricing for it, the same way you do with sales. You'd spend a billion dollars on sales if you knew you would get $2 billion of revenue.Jake [01:10:19]: Exactly. A naive way to measure this is the percentage of tokens that end up in production. If you can measure impact because those tokens end up in production, that's awesome. But the burden of proof will rise. Internally, we have a growing number of pull requests that haven't merged. The question becomes: how do you get this into production? It's about how quickly you can build and deploy software, which is exciting because that's our whole thing.The SDLC Shift: Prompt Requests, Feature Flags, and Safe RolloutsSwyx [01:10:56]: The SDLC is changing. One thesis is that the pull request is dying. It's going to be the prompt request. Beyond that, code review is also kind of dying if you have all the other systems in place. What else is changing about the SDLC?Jake [01:11:19]: The AISRE and the tools to make it happen. AISRE is pie-in-the-sky aspirational. What does it take to get an AISRE? What tools do you need to build?Swyx [01:11:32]: You should expose your tooling to customers at some point. The Central Station command center.Jake [01:11:39]: We have it for template maintainers. Template maintainers can deploy and maintain templates, and they get feedback. We're going to expose those things incrementally.Swyx [01:11:51]: Clustering around incidents. Everyone has a version of that, but I don't think anyone has solved it.Jake [01:11:56]: I won't say we've solved it internally, but it's gotten so good that we can see incidents forming pretty quickly. At some point, those will be things either someone else builds or we build. We've always built things purpose-built for us. If it makes sense to make it useful for users, monetize it, or turn that loop into a profit center instead of a cost center, we want to do that.Jake [01:12:28]: Pull request is definitely dying.Swyx [01:12:29]: Do you do first-party feature flagging and incremental rollout stuff?Jake [01:12:34]: We have a feature-flagging engine we built internally and will eventually roll out.Swyx [01:12:38]: I don't see it as a user. How come you didn't give us what you have?Jake [01:12:43]: We have to beta test it. We care a lot about the quality of the things. There's plenty we've used internally that doesn't make it all the way through the journey because it fails. It works for one service but not multiple services. We'd have to build it for multiple services and know that if we released it, we'd rebuild it again and again. Some things are worth that, but many inform the roadmap.Jake [01:13:18]: We don't want to dilute the experience by saying, “This works, but only for this service,” unless it's a core initiative. Over the next few months, we'll roll out things that work for a single service, then multiple services, then multiple services across the environment. You have to be deliberate. Otherwise you create broken disparate experiences and support load because people ask how to use the feature.Jake [01:13:52]: It's the earlier expansion and compaction pattern. You expand the company to get features, then compact and smooth them out so the experience is stellar. You told me in the hallway, “It's gotten so much better.” Internally we're saying, “This part really sucks. We need to make it significantly better.”Swyx [01:14:11]: I can attest to that over the last three years watching you build Railway. For listeners, feature flagging is a huge part of Uber culture. So much so that they have too many feature flags and another thing to remove feature flags. Facebook has Gatekeeper. Agents are going to need this. It's fundamental to incremental rollouts. OpenAI acquired Statsig. GPT-5 is routing and flagging through different models.Jake [01:14:56]: It's super important. If the software development lifecycle is going to change because we're doing things 1,000 times faster and 1,000 times more concurrently, what becomes important at scale?Jake [01:15:16]: Before I started Railway, I built a feature-flagging product and tried to sell it. It was an easier version of LaunchDarkly. I ran into a problem: anyone small enough to adopt your technology doesn't care about feature flags, and anyone large enough to need feature flags needs so much scale that you have to build out all the infrastructure. I scrapped it.Jake [01:15:42]: But what is old is new again. Companies are trying to move quickly, but you can't YOLO a vibe-coded thing straight into production. You need to say, “Here's my blast radius, my impact, and I want to shadow it for these users.” Feature flags. You're going to need the tools larger companies built to maintain their structures. Everything gets compressed by 1,000x so everybody can build those structures quickly.Jake [01:16:07]: That's exactly where we are: compressing the software development lifecycle, then expanding it and adding more new things.Cattle, Pets, and Clonable InfrastructureSwyx [01:16:15]: Another term that comes to mind for newer developers is “cattle, not pets.” People treat production like a pet. It has a name. You baby it and keep it alive. With cattle, you can mass farm, roll out, portion parts out, and kill them.Jake [01:16:37]: I think that might change. You can move toward having pets as long as you have a cloning machine for your pets.Swyx [01:16:52]: Yeah.Jake [01:16:52]: If you can snapshot every single thing at every frame, it doesn't matter if something gets obliterated because you have a snapshot of it. The things we've built right now are designed to block changes from the hermetically sealed DevOps line. You have to write a Dockerfile because you nee

Isaiah 30 offers glimpses of both Israel's near future and eternal future. Alex, Jim, and Sam discuss this fascinating passage.

Debates rage on between what a couple, a few and a handful are, as well as a spoon or a fork for mac and cheeseSee omnystudio.com/listener for privacy information.

Debates rage on between what a couple, a few and a handful are, as well as a spoon or a fork for mac and cheese

Matt Farah and Zack Klapman drive the Revology 1967 GT500 and ponder the difference between "replica" and "recreation"; the gov. has mandated your car spies on you; Mercedes project update; and Patreon questions include: Will fun cars get cheaper as people die? Favorite "appropriate" story from a Road & Track trip. How to avoid ruining your canyon car Rich man / poor man: seat setup edition Does the Coyote engine "ruin" an old car? Why LHD cars are worth more than RHD More fun: Fresh summer tires or worn winter tires? Engines that would be improved with more or fewer cylinders VW's sale of Bugatti's effect on car values Rebuild my BMW inline-4 or swap it for a 6? Mustang Dark Horse auto: a buy at $50k? Do only journos care about the Nissan Z chassis Ford ditching the Shelby name Proudest work moment Forks up or down? And more! Recorded May 1, 2026   Show Notes Aura Frames Exclusive $25-off Carver Mat at https://on.auraframes.com/TIRE. Promo Code TIRE   HimsFor simple, online access to personalized and affordable care for Hair Loss, ED, Weight Loss, and more, visit https://hims.com/TIRE.   TrueWerk Upgrade to the T2 WerkPant and stay comfortable no matter what the day brings. Get 15% off your first order at https://TRUEWERK.com with code tire.   Drive Podcast Listen to Drive with Jim Farley Season 4 at https://lnk.to/drivewithjimfarleyPS!thesmokingtire   Enter to WIN our AMAZING 2025 Porsche 911 Turbo S!! https://www.dreamgiveaway.com/tickets/porsche?promo=SMOKINGTIRE   Promo Code Offer: Get 4X bonus tickets with any donation of $25 or more. With every donation you are helping benefit some wonderful veterans' and children's charities.   Podcast Promo Code: SMOKINGTIRE   Your generous donation to Dream Giveaway goes directly to New Beginning Children's Homes, a 501(c)(3) organization (Federal ID# 27-5011514). Thanks to your donations, unrestricted grants are awarded to charities such as Mothers Against Drunk Driving (MADD), Honor Flight of West Central Florida, 4Kids, National Guard Educational Foundation, Victory Junction, Building Homes For Heroes, and Healing4Heroes⁠   ⁠To read more about Dream Giveaway and the charities our giveaways help benefit.  https://www.dreamgiveaway.com/about. Want your question answered? Want to watch the live stream, get ad-free podcasts, or exclusive podcasts? Join our Patreon: https://www.patreon.com/thesmokingtirepodcast Use Off The Record! and ALWAYS fight your tickets! Enter code TST10 for a 10% discount on your first case on the Off The Record app, or go to http://www.offtherecord.com/TST. Watch our car reviews: https://www.youtube.com/thesmokingtire Tweet at us!https://www.Twitter.com/thesmokingtirehttps://www.Twitter.com/zackklapman Instagram:https://www.Instagram.com/thesmokingtirehttps://www.Instagram.com/therealzackklapman

Welcome to episode 387 of Growers Daily! We cover: what our actions today will look like to future generations, we'll discuss horse manure and pouring it over cover crops for a bed, and pitchfork-poloza. We are a Non-Profit! 

After 15 years of being a Bitcoin-only maximalist and about a decade of promoting BIP300 as a soft fork, LayerTwo Labs CEO Paul Sztorc decided to launch Ecash: a hard fork of Bitcoin in which every BTC holder gets free coins. There's a catch, though: while everyone can claim 1 ecash for every bitcoin that they own, Satoshi can only claim half. Meaning that a returning Satoshi will only be able to claim half his coins, while the other half (550k) is currently being sold to investors in order to fund the development and bootstrapping of Ecash. What's more controversial: the hard fork or the SHAD (Satoshi Half Air Drop)? Only time will tell. But the Ecash hard fork is scheduled to happen in August 2026... unless Bitcoin activates BIP300 in the meantime. Game theory at its finest! Time stamps: 00:00:58 – Paul Sztorc announces the new Bitcoin hard fork project, eCash, sharing his motivation for launching it and setting the stage for the discussion. 00:03:02 – eCash's technical details are explained, including its smaller 400kB block size and the integration of drivechains (BIP 300) to enhance scalability and flexibility. 00:04:55 – The initial drivechains launching with eCash are described, such as Thunder for scalability, ZSide for privacy, and additional chains like CoinShift, BitNames, and Photon. 00:09:28 – Security aspects of sidechains are discussed, covering the 256 sidechain limit, potential outcomes if sidechains fail, and the risks users face when moving coins. 00:14:26 – The project's name, Ecash, is revealed, with a comparison to Bitcoin Cash and an explanation of the naming decision. 00:15:40 – Paul delves into the philosophy behind the hard fork, his views on Bitcoin maximalism, and his intention to remain committed to both Bitcoin and eCash. 00:20:35 – Mining dynamics are explored, including SHA256 mining competition, miner incentives, and the potential for MEV (miner extractable value) issues. 00:22:36 – Paul critiques the current state of Bitcoin, highlighting user and developer frustration, stagnation, low transaction fees, and gridlock in development. 00:29:40 – The potential for eCash to attract frustrated Bitcoin builders is considered, with references to similar migrations in crypto history. 00:31:38 – Ethereum's rise is analyzed as a consequence of Bitcoin's block size wars, with discussion on missed opportunities and lessons learned. 00:41:06 – The likelihood and impact of further Bitcoin hard forks are speculated upon, focusing on community fragmentation and effects on value. 00:41:49 – Hard forks are framed as healthy competition that benefits investors by providing free coins and stimulating innovation. 00:48:20 – The decision to reassign half of Satoshi's coins for development and community incentives is explained, addressing concerns about distribution. 00:54:07 – Quantum computing threats, Satoshi's mining behavior, and the rationale for the coin distribution are discussed in the context of long-term security. 01:36:00 – Users are advised to self-custody their Bitcoin to claim eCash, with an outline of the claiming process and best practices. 01:39:01 – Technical steps for claiming eCash using private keys are detailed, including wallet compatibility and the process for users. 01:43:26 – The potential for NFT and ordinal activity on eCash is addressed, along with how LayerTwo Labs will manage onboarding and network congestion. 01:45:35 – Drivechain security parameters are confirmed, with eCash using a 13,000-block security window in line with BIP 300's Bitcoin implementation. 01:52:06 – The transition from a centralized project launch to decentralized development and governance. 01:54:36 – The current developer team size (about nine members) is shared, along with incentives for external developers to contribute to eCash. 01:58:26 – eCash is compared to Bitcoin Cash, with discussion on network effects, competition, and the potential for eCash to drive improvements in Bitcoin. 02:07:22 – The session concludes with future plans, a call for community engagement, and the possibility of follow-up discussions as the project evolves.

A Note from James:People are so afraid of AI, and I get it. They're afraid of how it will affect jobs. They're afraid of bias, manipulation, or even worst-case scenarios like AI turning on humans.That's why I love talking to Peter Diamandis.He wrote Abundance, came on the podcast 10 years ago, and now he's back with his new book, We Are as Gods. He also runs the Moonshots podcast and the Meta Trends newsletter, both worth paying attention to.Peter has this ability to stay optimistic about the future—whether it's AI, longevity, robotics, or virtual worlds. Everything is moving at light speed right now, and while I'm generally optimistic, I still sometimes wonder: what if the pessimists are right this time?But Peter always pulls me back. His view of the future is bold, optimistic, and surprisingly concrete. And honestly, it's exciting.Episode Description:In this conversation, James reconnects with Peter Diamandis to explore what may be the defining shift of our time: the transition into an AI-driven world of extreme abundance—and extreme uncertainty.Diamandis argues that we're not heading toward a traditional crisis, but an “emotional pandemic of fear.” As AI accelerates faster than any previous technology, people are struggling to process its implications: job disruption, societal upheaval, and a complete rethinking of how value is created.But his perspective is fundamentally different. Instead of scarcity, he sees exponential growth—potentially even “triple-digit GDP expansion.” Instead of job loss alone, he sees a massive shift toward entrepreneurship and creation. And instead of humans being replaced, he sees humans amplified.The episode moves between near-term reality and long-term speculation: AI partners that run your daily life, personalized health systems, humanoid robotics, brain-computer interfaces, and even the possibility of digital consciousness.What makes this conversation compelling is not just the optimism—it's the framing. The real divide ahead, Diamandis suggests, won't be between rich and poor, but between consumers and creators.What You'll Learn:Why Diamandis believes the next global crisis is a “pandemic of fear,” not diseaseHow AI could simultaneously cause job disruption and massive economic expansionThe emerging divide between AI-powered creators vs passive consumersWhy mindset—not skills or resources—will determine success in the next decadeHow AI may reshape daily life through personalization, automation, and decision-makingWhat “humanity's forks” look like: longevity, space, AI integration, and digital consciousnessTimestamped Chapters:[02:00] The coming “emotional pandemic” of fear[02:34] Triple-digit GDP growth and AI-driven abundance[03:07] A Note from James: optimism vs fear around AI[04:29] Why AI is accelerating faster than anyone can track[05:53] The problem with traditional publishing in exponential times[07:42] Why abundance and fear are rising at the same time[08:49] Hollywood's role in shaping dystopian tech narratives[10:00] Rewriting the future through optimistic storytelling[11:49] Industry-wide disruption and job anxiety[12:23] AI as the most powerful force ever accessible to humanity[13:10] Partnering with AI vs competing against it[14:20] Scarcity mindset vs abundance mindset[17:41] Why mindset is the ultimate competitive advantage[19:00] The two critical mindsets: curiosity and purpose[20:02] How to find your purpose in an AI world[22:23] The creator vs consumer divide[23:54] Using AI for everyday problem-solving[24:33] When exponential change becomes visible[25:00] Economic disruption and universal income scenarios[27:44] Corporate downsizing vs entrepreneurial explosion[29:00] Inflation vs massive cost reduction through AI[30:10] Free healthcare, education, and transportation?[31:23] Breakthroughs that surprised Diamandis[33:32] Brain-computer interfaces and knowledge uploading[35:39] The future of learning vs effort[37:33] Civilizations, AI, and the scale of the universe[41:00] Are we creating a new “alien” intelligence?[43:46] Humanity's major “forks” ahead[44:35] Longevity and doubling human lifespan[45:48] Digital consciousness and mind uploading[47:06] What daily life will actually look like with AI[49:00] Personalized AI controlling environment, health, and decisions[51:40] How every industry will be restructured[53:00] AI entering the physical world (robots, sensors, health)[55:00] Will AI become a commodity?[56:38] The real value: breakthroughs built on top of AI[57:20] Centralized vs decentralized AI systems[58:00] Closing thoughts and future outlookAdditional Resources:We Are as Gods: A Survival Guide for the Age of AbundanceAbundance: The Future Is Better Than You ThinkXPRIZE FoundationMoonshots PodcastMeta Trends NewsletterSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

See omnystudio.com/listener for privacy information.

This week: Mike and Ian talk with an Olympic Ice Master, help a listener who keeps meeting people with their same name, and get to the bottom of a mysterious survey glitch.You can email your burning questions to howto@npr.org.How To Do Everything is available without sponsor messages for supporters of Wait Wait…Don't Tell Me+, who also get bonus episodes of Wait Wait Don't…Tell Me! featuring show outtakes, extended guest interviews, and a chance to play an exclusive WW+ quiz game with Peter! Sign up and support NPR at plus.npr.org. How To Do Everything is hosted by Mike Danforth and Ian Chillag. It is produced by Schuyler Swenson. Technical direction from Lorna White.Learn more about sponsor message choices: podcastchoices.com/adchoicesNPR Privacy Policy

Weirdos!! It's here! the second deep dive into the twisted world of the Twilight Saga! Grab your brown-tinted filters and emotional support glitter, because Ash and Alaina are back in Forks for a full-throttle deep dive into New Moon. For this month's BONUS EPISODE we're unpacking Edward's dramatic exit, Bella's months-long depression montage (hello, spinning seasons), and the introduction of a jort-wearing werewolf jamborees: Jacob Black. We debate whether ghost Edward is helpful or wildly unhinged, and try to make sense of the Volturi's whole vibe!  There's chaos, hot takes, and Bella imitations that will make you howl!  Light a candle, stare moodily out a window, and join us, because the angst is real, the wolves are howling, and we're all #TeamMessy!