Podcasts about Western Europe

Werner Rügemer discusses his book "Fatal Friendship: First Phase: From World War I to II." From the book jacket: Rising US capitalism presented itself to the world with freedom, democracy, and prosperity. However, the practices of America First-genocide, labor exploitation, and warlike plunder of foreign property-were merely modernized.The First World War became the first major global business venture, making allies dependent. After the war, US corporations invested in Western Europe. Mussolini was showered with loans. US corporations supplied Franco and equipped the German Wehrmacht for a war against Russia.Support Sublation Mediahttps://patreon.com/dietsoap

A guide to restoring the ancient relationship between farming and magic• Explores how to reconnect with nature and use practical, nature-based magic for gardening and farming, fertility, and abundance• Examines Moon work, plant magic, forest deities, Earth energies, weather magic, the cosmology of ritual, and how to work with land spirits• Discusses folk magic traditions of North America and Western Europe, including the grimoire tradition, Western esotericism, alchemy, Kabbalah, and shamanism as well as Taoist principles and ReikiMagic and farming, in the minds of ancient people, were not separate realms of life, but both were woven inextricably into the way people lived. Through libations, prayers, hymns, dances, sacrifices, and rituals, ancient farmers connected to the sacred forces, the gods, nature spirits, and ancestors to make the crops grow, keep the herds healthy, the weather favorable, and release energies of fertility. These rural farmer priests and priestesses of the ancient past are the spiritual ancestors of today's cunning farmers.This book explores folk magic traditions of North America and Western Europe, including the grimoire tradition and the practices of witches and cunning folk for increased fertility. Todd draws on Western esotericism, Taoist principles, alchemy, Kabbalah, Reiki, and shamanism to show how to use practical, nature-based magic, just like our ancestors, for more abundant gardening and farming. He shows how to work with land spirits, including meeting the place spirit of your land—the genius loci. He also explores working with Earth and Moon energies, plant magic and forest deities, and ritual. Learn how to deepen your connection to elemental and celestial forces and explore the idea of rewilding the imagination to enhance your relationship with nature and the spirits that call it home.This book is not just a guide to farming, but to forging a relationship with the living land. It shows that we are surrounded by spiritual powers and, with their help, we can re-enchant and reconnect with the land that gives us life.Todd Elliott is a farmer, earth worker, Reiki master, Druid, and was certified as an Astrological Magician by Renaissance Astrology. A lifelong student of mythology, religion, spirituality, folklore, and esoterica, he lives, works, writes, and studies on a small ridgetop farm in north central Kentucky, where he and his family ethically raise vegetables, fruits, and livestock.https://substack.com/@thecunningfarmerBecome a supporter of this podcast: https://www.spreaker.com/podcast/earth-ancients--2790919/support.

Ukraine has been intensifying attacks across Crimea as it attempts to cut off the peninsula annexed by Russia in 2014. The authorities have been forced to suspend fuel sales to the public.Also on the programme: hundreds of schools in the UK are closed as temperatures in Western Europe hit new highs; and why sperm whales use different dialects depending on where they swim in the Mediterranean Sea.(Photo: A satellite image shows burning oil storage tanks and smoke rising from the Crimea Bridge amid the Russia-Ukraine conflict Credit: Vantor/Reuters)

Record June temperatures have been recorded in several countries, with highs of 44C. As the continent swelters, workers struggle in the heat.Power failure in Russian occupied Crimea after more overnight drone raids by Ukraine.And prices for Grand Theft Auto 6 have been revealed.

Record June temperatures have been recorded in several countries, with highs of 44C. As the continent swelters, workers struggle in the heat.Power failure in Russian occupied Crimea after more overnight drone raids by Ukraine.And prices for Grand Theft Auto 6 have been revealed.

As a record-breaking heatwave continues in western Europe, the United Nations has warned that fossil fuels are driving a climate crisis. France has endured its hottest night in more than eighty years and temperatures are expected to climb above 41C. Spain, Italy, Germany and the UK are also sweltering. Also: the European Union issues single-day visas to a Taliban delegation to attend a migration meeting in Brussels, despite not recognising the government in Afghanistan; the US Secretary of State Marco Rubio heads to the Gulf for high-stakes talks with Arab allies; a major ransomware attack in Romania forces a hundred hospitals offline; Sri Lanka battles its worst dengue outbreak in years; a new study suggests people may be biologically ageing faster than previous generations, raising questions about a rise in early-onset cancers; and we look at the economic impact of Cape Verde's remarkable run at the mens football World Cup, as the tiny Atlantic island nation enjoys global attention.The Global News Podcast brings you the breaking news you need to hear, as it happens. Listen for the latest headlines and current affairs from around the world. Politics, economics, climate, business, technology, health – we cover it all with expert analysis and insight. Get the news that matters, delivered twice a day on weekdays and daily at weekends, plus special bonus episodes reacting to urgent breaking stories. Follow or subscribe now and never miss a moment. Get in touch: globalpodcast@bbc.co.ukPhoto: People cool off in the Trocadero Fountain next to the Eiffel Tower as temperatures rise during a heatwave affecting a large part of the country, in Paris, France, June 22, 2026. Credit: REUTERS/Abdul Saboor

Western Europe is in the midst of a severe heat wave, with the temperature in Paris hovering close to 100 degrees Fahrenheit. An estimated 45 people have already died in France as a result, many from drowning while trying to cool off. Also, a look at how Brexit continues to shape British politics a decade later. And, US funding cuts to South Africa could risk an HIV/AIDS rebound. Plus, a new type of shoe that keeps your feet cool and comfortable.Time is running out and we need your help to reach our goal before our 2:1 match ends! Give now. Learn about your ad choices: dovetail.prx.org/ad-choices

Schools have closed in France. A nuclear power plant near Toulouse has been forced to switch off a reactor. Nuclear power plants cannot operate correctly without enough water of the right temperature to cool down reactors. When these temperatures climb too high, the reactors need to be shut down to avoid environmental damage caused by hot water being discharged into local water courses. Also on the programme: the newly discovered manuscript containing composition lessons by Mozart; and the continuing woes of the Lincoln Memorial Reflecting Pool in Washington DC.(Photo: Young people cool off in the Fontaine de l'Observatoire fountain as temperatures rise in Paris Credit: Reuters/Abdul Saboor)

Europeans are braced for a heat wave that could push the mercury beyond 44 C this week, and cost the lives of elderly residents and people with underlying health conditions.欧洲即将迎来一轮极端热浪，本周局部最高气温或将突破 44 摄氏度，老年人以及患有基础病的人群生命安全将受到严重威胁。The heat wave, which is centered on France but that is impacting much of Western Europe, has prompted the French government to put its emergency services and military forces on high alert, with teams ordered to be ready to attack heat-related wildfires.这股热浪核心影响法国，西欧多数地区均遭波及。法国政府已要求各类应急机构与军队进入最高戒备状态，救援队伍随时待命，扑救高温引发的山林野火。The average temperature in France at this time of year ranges between 15 C and 25 C.往年这个时节，法国平均气温仅在 15 至 25 摄氏度之间。The country has also canceled some outdoor sports events, and restricted alcohol availability at a major nationwide music festival on Sunday, over fears people could become dehydrated by drinking beer to stay cool, instead of more appropriate beverages.法国还取消了多项户外体育赛事，并于周日在一场全国大型音乐节上限制酒水售卖。当局担心民众靠喝啤酒消暑，不饮用补水饮品，进而出现脱水症状。The government said restricted alcohol sales will also help "preserve emergency services and allow medics to concentrate on taking care of the most vulnerable".法国政府表示，限制售酒能够减轻急救系统的负担，让医护人员集中精力照料高危易感人群。Around a third of France is the subject of a red health alert that began on Sunday.从周日起，法国约三分之一国土拉响高温红色健康警报。Thermometers were set to hit 40 C on Sunday and edge several degrees higher on Monday, Tuesday, and Wednesday.周日当地气温攀升至 40 摄氏度，周一、周二、周三还会再升高好几度。The uncomfortably hot weather has prompted popular tourist attractions to set up misting stations and drinking-water fountains.持续酷热之下，各大热门景区纷纷增设喷雾降温点与免费饮水喷头。And the extreme weather is also impacting the United Kingdom, which issued an amber extreme heat warning on Sunday for southern England, the Midlands, and much of Wales.极端高温同样席卷英国。该国周日针对英格兰南部、中部以及威尔士大部分地区发布高温预警。The UK's Met Office said temperatures could hit 36 C or 37 C on Monday and Tuesday. The average temperature in the country at this time of year is between 14.5 C and 15.5 C.英国气象局预测，周一、周二最高气温可达 36 至 37 摄氏度；而当地往年同期平均气温仅 14.5 至 15.5 摄氏度。Italy has also issued what it calls "red flags" for eight of its cities in northern and central parts of the country. Temperatures in those red flag zones are expected to be in the high 30s.意大利也给本国中北部八座城市发布高温 “红旗预警”，预警区域气温预计将逼近 40 摄氏度。The European heatwave is likely to trigger a strong demand for energy — as people crank up their air conditioning units — and lead to water shortages and transport disruption.这轮欧洲热浪会促使居民大量开启空调，电力需求激增，同时还会造成供水短缺、交通运行受阻等一系列问题。The World Health Organization's Europe office said this month that more than 200,000 people have died across the continent from heat-related causes during the past four years, with most of the fatalities entirely preventable.世界卫生组织欧洲区域办事处本月发布消息，过去四年欧洲已有超 20 万人死于高温相关疾病，其中绝大多数死亡事故本可以避免。The WHO urged people to avoid swimming in lakes and rivers that they are unfamiliar with, or that do not have organized swimming areas, because many deaths were caused by people jumping into dangerous bodies of water.世卫组织提醒民众，不要在陌生河湖或是无正规游泳区域的水域下水，许多人都是因贸然跳入危险水域溺水身亡。The WHO also called on governments and employers to offer people respite from the heat and additional breaks or flexible shifts that ensure workers can stay out of the midday sun.世卫组织同时呼吁各国政府和企业设立避暑场所，增加休息时长、实行弹性排班，避免劳动者在正午烈日下作业。Weather experts have said heat waves are becoming increasingly frequent and intense because of human-induced climate change.气象专家指出，受人类活动引发的气候变化影响，热浪发生的频次越来越高，极端程度也持续加剧。mercury /ˈmɜːkjəri/n. 气温；水银vulnerable /ˈvʌlnərəbl/adj. 易受伤害的，体质虚弱的disruption /dɪsˈrʌpʃn/n. 中断，扰乱respite /ˈrespaɪt/n. 喘息，短暂缓解

Architectural Integrity in the Age of Algorithmic Code: Software Engineering and QA Governance with Konstantin KlyaginIn a recent episode of The Thoughtful Entrepreneur Podcast, host Josh Elledge sat down with Konstantin Klyagin, the Founder of Redwerk, to deconstruct the operational liabilities introduced by the rapid adoption of AI-assisted coding tools. Konstantin, a veteran software architect with more than two decades of global technology experience spanning Ukraine, Western Europe, and the United States, shares a critical perspective on why speed should never be mistaken for stability in software delivery. This conversation provides an essential, engineering-focused blueprint for mid-market founders, enterprise product owners, and technical leaders who want to leverage advanced software automation while aggressively protecting their products against technical debt, architectural breakdown, and security vulnerabilities.The Code Optimization Paradigm: Mitigating Technical Debt with Rigorous Quality AssuranceThe widespread corporate directive to accelerate release cycles through generative artificial intelligence has inadvertently created an environment where companies routinely exchange long-term structural stability for immediate development speed. Konstantin Klyagin cautions that while algorithmic coding tools are highly effective for rapid prototyping and generating initial Minimum Viable Products (MVPs), they frequently output thousands of lines of bloated, inefficient, and brittle syntax that lacks any context regarding an enterprise's scaling requirements. When product teams deploy this machine-generated code directly into production environments without strict human review, they inherit severe administrative and technical debt that complicates future software updates and compromises system security. True enterprise scalability is achieved not by handing over core development to complete automation, but by enforcing rigid software architecture guardrails and treating artificial intelligence strictly as a baseline productivity assistant overseen by seasoned human engineers.Transitioning an organization out of reactive code patching requires an absolute commitment to formal Quality Assurance (QA) governance rather than treating software testing as a post-development afterthought. Many founders commit the costly mistake of using their own end-user base as the primary line of bug discovery, which introduces significant friction into customer-facing operations and quietly erodes long-term brand equity. Real-world capital optimization demands that software organizations build sophisticated internal or external manual and automated testing pipelines to evaluate edge cases, business logic compliance, and real-time drop-off analytics long before new features hit the market. For instance, rather than accepting automated outputs at face value, professional engineering teams systematically refactor code lines—frequently condensing massive, AI-generated structures into a few dozen clean, optimized scripts—ensuring the application remains stable under high user loads and protects its core margins.Furthermore, maintaining a premium digital footprint in a highly competitive market demands that corporate leaders balance software innovation with deliberate strategic focus and lifestyle resilience. Drawing from his global journey and personal dedication to demanding outdoor sports like kite surfing, Konstantin highlights that clear executive decision-making relies heavily on maintaining cognitive agility outside the office. When a technology enterprise pairs an advanced, multi-model tech stack with a transparent workplace culture and external diagnostic assessments—such as comprehensive, unbiased software audits—it successfully insulates its bottom line against changing algorithmic trends. Ultimately, permanent industry authority belongs to the organizations that treat software engineering as a strict corporate discipline, balancing backend automation loops with definitive human oversight to predictably scale enterprise value.About Konstantin KlyaginKonstantin Klyagin is the Founder of Redwerk and a premier global technology strategist with over 21 years of specialized experience in software architecture and legacy system modernization. Having successfully scaled complex development structures for international government agencies and award-winning enterprise clients, Konstantin now advises mid-market companies on technical execution and product management. He is a passionate advocate for continuous technical education and high-accountability engineering standards within the global developer ecosystem.About RedwerkRedwerk is an elite, full-service software development agency and technical advisory firm specializing in product engineering, legacy maintenance, and professional quality assurance for mid-market businesses. Operating with a dedicated team of over 90 technical professionals, the company bridges the gap between high-level business goals and technical execution across diverse markets. Through structured implementation playbooks and specialized software bug audits, Redwerk enables organizations to eliminate technical debt and predictably scale their digital infrastructure.Links Mentioned in This EpisodeRedwerk Official Website: redwerk.comKonstantin Klyagin on LinkedIn: linkedin.com/in/thekonstKey Episode HighlightsThe AI Bloat Trap: Understanding why over-reliance on generative coding tools introduces thousands of lines of brittle, unoptimized syntax into production environments.The Architecture Ownership Mandate: Why experienced human engineers must guide all core structural and scalability decisions independent of automated recommendations.The Failure of User-Led QA: Transitioning away from using your active client base as bug testers by installing internal manual and automated verification pipelines.Data-Driven Drop-Off Analytics: Utilizing behavioral tracking tools to precisely map user journeys and resolve technical bottlenecks within the application funnel.The Long-Tail Software Audit: Leveraging objective, third-party code reviews to identify hidden operational vulnerabilities and build credibility with investors.ConclusionThe conversation with Konstantin Klyagin reinforces that true software optimization is an intentional discipline built on clean engineering principles rather than automated volume. By standardizing internal corporate tech governance, enforcing rigorous human-in-the-loop quality assurance, and focusing ruthlessly on long-term architectural health, business leaders can transform a volatile software setup into a highly structured, self-sustaining corporate asset.More from The Thoughtful Entrepreneur

The Red Lady of Paviland.Friends, tonight I'm taking you to a place where the land falls away into the sea, where the wind howls across the cliffs of Gower and the waves whisper against ancient stone. Hidden there is a cave that kept its secret for more than 33,000 years.In the latest episode of The Time Between Times, we journey deep into Ice Age Wales to uncover the extraordinary story of the Red Lady of Paviland — one of the oldest ceremonial burials ever discovered in Western Europe.This is a story that has everything I love: mammoths wandering across frozen landscapes, ancient rituals lost to time, archaeological mysteries, and a remarkable discovery that challenged everything people thought they knew about the distant past.Who was the young man buried beneath a blanket of red ochre? Why was he laid to rest with such care? And what can his grave tell us about the beliefs, hopes and dreams of people who lived tens of thousands of years ago?It's a tale of wonder, mystery and deep human connection — a reminder that even across unimaginable stretches of time, the people of the past are never quite as distant as they seem.So pull up a chair by the fire, settle in, and join me as we step beyond history and into deep time itself.I can't wait for you to hear this one. Welcome… to The Time Between Times.www.welshstoryteller.comwww.ko-fi.com/owenstaton- Please buy me a Ko-fiwww.patreon.com/owenstaton7- Become a Patreon

Iran has closed the Strait of Hormuz again as a new Middle East ceasefire fractures under fresh violence.An out-of-control wildfire near Lytton, B.C. has triggered urgent evacuation orders and shut down a major stretch of the Trans-Canada Highway.A brutal summer heatwave is gripping Western Europe as temperatures approach historic and deadly highs.Portugal's prime minister is expressing shock over a newly uncovered neo-Nazi terrorist plot targeting his home and over 100 public figures.Lawmakers from across Africa are pledging a coordinated crackdown on L-G-B-T-Q rights following a major "pro-family" summit.

In this fifth episode of The Cunning Farmer, Todd Elliott and I tromp-on through Chapter 5 (Moon Work) of his pivotal book, The Cunning Farmer: Agrarian Magical Practices, Mythology, and Folklore, discussing Lunar magic, Moon phases and Mansions, the worldview necessary to hold this, and how to integrate the Lunar Calendar into your agricultural practices....Learn more about our new podcast: The Language of Irish Mythology Podcast.Join the Unshod Substack (for free) and commune with us! Purchase The Cunning Farmer HERE.Learn more about Daniel's work HERE.The Cunning FarmerA guide to restoring the ancient relationship between farming and magicExplores how to reconnect with nature and use practical, nature-based magic for gardening and farming, fertility, and abundanceExamines Moon work, plant magic, forest deities, Earth energies, weather magic, the cosmology of ritual, and how to work with land spiritsDiscusses folk magic traditions of North America and Western Europe, including the grimoire tradition, Western esotericism, alchemy, Kabbalah, and shamanism as well as Taoist principles and ReikiMagic and farming, in the minds of ancient people, were not separate realms of life, but both were woven inextricably into the way people lived. Through libations, prayers, hymns, dances, sacrifices, and rituals, ancient farmers connected to the sacred forces, the gods, nature spirits, and ancestors to make the crops grow, keep the herds healthy, the weather favorable, and release energies of fertility. These rural farmer priests and priestesses of the ancient past are the spiritual ancestors of today's cunning farmers.This book explores folk magic traditions of North America and Western Europe, including the grimoire tradition and the practices of witches and cunning folk for increased fertility. Todd draws on Western esotericism, Taoist principles, alchemy, Kabbalah, Reiki, and shamanism to show how to use practical, nature-based magic, just like our ancestors, for more abundant gardening and farming. He shows how to work with land spirits, including meeting the place spirit of your land—the genius loci. He also explores working with Earth and Moon energies, plant magic and forest deities, and ritual. Learn how to deepen your connection to elemental and celestial forces and explore the idea of rewilding the imagination to enhance your relationship with nature and the spirits that call it home.

The June 15, 2026, edition of the Closing Market Report covers recent agricultural commodity market trends, global supply estimates, and international weather forecasts. Curt Kimmel of AgMarket.net notes that agricultural markets are currently stabilizing, with the recent Iran war settlement expected to reduce transportation and energy costs, thereby boosting investor confidence and global grain demand. Agricultural economist Ben Brown discusses the bearish impact of the latest World Agricultural Supply and Demand Estimates (WASDE) report, which revealed a 14 million metric ton increase in global corn production, largely driven by India. Brown also highlights strong domestic soybean crush demand and notes that global wheat production increases are currently overshadowing tightening U.S. supplies. Furthermore, Brown emphasizes the strong correlation between energy and grain prices while warning of potential agricultural trade disruptions if the USMCA agreement is not extended. Finally, Mark Russo of EverStream Analytics forecasts another round of severe storms and heavy rainfall for the U.S. Corn Belt before shifting to a drier pattern, while simultaneously warning of a prolonged heat wave and declining soil moisture threatening crops in Western Europe, particularly in France.- Ag Markets with Curt Kimmel, AgMarket.net- Commodity Markets Discussion with Ben Brown- Ag Weather with Mark Russo, EverStream.ai ★ Support this podcast ★

The forced migration into Western Europe and the United States is part of a much broader plan to destabilize and ultimately destroy the Western world. Cultural incompatibility seems to be the ultimate goal, and Don Jeffries has been writing about it for thirty years. From Somalia Learing Center scams in Minneapolis to hospice and homeless fraud in Los Angeles, it is becoming obvious that the American Dream has been hijacked by scammers, grifters, and pedophiles intent on ensuring America doesn't get another 250 years.---Guest: Don Jeffries Substack: I Protest | @djeffrieshttps://donaldjeffries.substack.com/---Macroaggressionswww.Macroaggressions.ioMerch StoreLink Tree Video ChannelsRumble | YouTube | BrighteonActivist PostNewsletter Sign UpAudiobooksHypocrazyThe Octopus of Global ControlSupport Our SponsorsReplace Your Mortgage: www.WipeOutYourMortgageNow.comGround Luxe Grounding MatsC60 Power | Promo Code: MACROChemical Free Body | Promo Code: MACROWise Wolf Gold & SilverLegalShield: www.DontGetPushedAround.comChristian Yordanov's Health ProgramThe Dollar VigilanteNesa's Hemp | Promo Code: MACROAugason Farms

Irenaeus lived at a time when the church was being attacked from the outside by persecution and from the inside by false teaching.In this episode of Kitchen Table Theology, Pastor Jeff and Tiffany look at the life of Irenaeus, one of the early church's most important defenders of the gospel. Connected closely to the apostles through Polycarp, Irenaeus helped preserve apostolic teaching, confront the rise of Gnosticism, and guide the church with both truth and grace.Chapters:01:00 Who Was Irenaeus?Irenaeus was one of the most important Christian leaders of the second century. Closely connected to the apostles through Polycarp, his life is bridge between the New Testament church and the generations that followed.02:00 Asia Minor and the Early ChurchAsia Minor, located in what is now modern-day Turkey, played a major role in early church history03:30 Irenaeus' Connection to the Apostle JohnThe Apostle John taught Polycarp, Polycarp taught Irenaeus, placing Irenaeus only one generation removed from an eyewitness of Jesus Christ.05:00 Irenaeus in LyonAfter studying briefly in Rome, Irenaeus moved to Lyon in Gaul, modern-day France. There, he joined the leadership of a growing Christian congregation in one of the most important cities in Western Europe.07:30 Persecution in LyonWhile Irenaeus was away in Rome, severe persecution broke out against the Christians in Lyon. Nearly 50 believers were martyred, including Blandina, Sanctus, and the elderly bishop Pothinus.11:00 Irenaeus Becomes Bishop of LyonAfter returning from Rome, Irenaeus was chosen to replace Pothinus as bishop of Lyon. For the next 25 years, he shepherded the church, trained leaders, sent missionaries, and strengthened scattered congregations throughout the region.12:30 What Was Gnosticism?Gnosticism was one of the greatest challenges facing the early church. Many Gnostics believed that physical matter was evil, denied that Jesus truly became human, and claimed to possess secret knowledge unavailable to ordinary Christians.16:30 Irenaeus and Against HeresiesIrenaeus' most famous work, Against Heresies, exposed the errors of Gnostic teaching and defended the faith handed down from the apostles. His writings helped explain Christian doctrine clearly and earned him the title “the father of Christian theology.” 18:30 The Quartodeciman ControversyAnother major issue during Irenaeus' lifetime involved the timing of Easter. Rather than allowing a calendar disagreement to divide the church, Irenaeus urged believers to maintain fellowship where the gospel itself was not at stake.22:30 What Irenaeus Teaches Christians TodayStay rooted in apostolic truth, guard the gospel carefully, and pursue unity whenever possible. “Irenaeus fought fiercely for essential doctrines while showing remarkable charity to others in secondary matters.” - Pastor Jeff Cranston

## Title **Memes, Migrants, and Mars: Elon Musk vs. Europe's Totalitarian Speech Laws** --- ## Description In this riveting segment, the hosts break down the collision between global capitalism and European speech crackdowns. The monologue begins with the highly anticipated SpaceX IPO, marveling at Elon Musk's unique financial resilience. Despite years of media predictions claiming he was "finished," public faith in his vision has pushed his net worth higher than ever, showing that investors prioritize his track record over traditional business metrics. However, the conversation quickly shifts to the severe legal threats Musk faces overseas. European nations—specifically the UK and Ireland—are threatening to arrest the tech billionaire for violating their restrictive Online Safety Acts. The controversy stems from Musk's refusal to remove a video of a horrific migrant attack in Ireland, exposing a political climate where criticizing migration policy or sharing government crime statistics online is treated as a criminal offense. The hosts detail a series of shocking escalation tactics from European leadership, including Keir Starmer's push for digital IDs to access the internet and algorithmic surveillance tools designed to scan and save private messages before they are encrypted. The segment concludes with a stark warning: under current free speech crackdowns, the world's most successful businessman would face immediate arrest if he stepped off a plane in Western Europe. --- ## Custom Labels Elon Musk, SpaceX IPO, Free speech, Europe speech laws, Keir Starmer, Digital ID, Online Safety Act, Ireland immigration, Tech censorship, Totalitarianism, Political commentary

Rock, Paper, Swords! — Episode: The Crusader Storm with Nicholas Morton Released 12th June 2026Matthew Harffy and Justin Hill are joined by historian Nicholas Morton, associate professor at Nottingham Trent University and author of the new book The Crusader Storm: A Global History of the Wars for the Middle East (out 4th June 2026).The Crusades are one of history's most argued-over subjects — and Nicholas Morton thinks most people have got them wrong. In this wide-ranging conversation, he makes the case that the wars for the Holy Land were never a simple clash between Christianity and Islam, but a messy, many-sided contest between rival empires, dynasties and cultures.Along the way we talk about the extraordinary cast of individuals who populate his book — from a remarkably long-lived Arab nobleman who witnessed nearly the entire era, to Syriac Christians playing the long game between warring powers. We explore how Muslim Bedouin groups allied with the Crusaders, why Islamic medicine was flowing back to Western Europe, and how the demands of supplying the Crusader States drove a dramatic leap forward in medieval shipbuilding. We also get into the evolution of Crusader castles, the trade routes that made the Middle East the most strategically valuable region on earth, and what — if anything — the medieval period can tell us about the modern one.Plus: how do you write popular history without guessing? Can AI translate ancient Syriac? And is Nicholas Morton already thinking about an Ottoman Storm?Support us on Patreon: https://www.patreon.com/cw/RockPaperSwordsPodcastAll podcast links: https://linktr.ee/RockPaperSwords

At Infosecurity Europe in London, Pete Hannah, VP of Sales for Western Europe at Object First, joins Sean Martin to reframe a question many organizations still get wrong. The issue is not only how to keep ransomware out, but how quickly you can recover once it gets in. With Europe's regulatory landscape tightening, that distinction is becoming the difference between disruption and disaster. What does the UK Cyber Security and Resilience Bill actually demand? According to Pete Hannah, it reads less like a checklist and more like an operational resilience standard. It expects organizations to manage threats, prove they have tested their recovery plans, and treat resilience as a board-level responsibility with real financial penalties. More than ninety percent of the bill already applies in practice, so waiting for it to become law is a risk in itself. Why do backups matter so much? Because more than ninety percent of cyberattacks target them first. Pete Hannah explains that "immutable" has become a marketing word, and the meaningful test is whether anyone still holds the access to destroy protected data. Object First answers that with absolute immutability, independently tested, with zero destructive access for admins or compromised accounts. That protection is purpose-built for Veeam environments through the Ootbi appliance, the resilient bunker that stays standing even when every password is known and every other system is compromised. When recovery is guaranteed, teams stop worrying about whether they will recover and focus instead on how fast. How does a stretched IT team adopt this without adding overhead? Pete Hannah describes deployment as taking the appliance out of the box, racking it, connecting it, and pointing backups at it. For boards and CISOs under budget and resource pressure, simplicity is the selling point. It is easy to manage, easy to prove, and dependable when it matters. The proof is in the field. Pete Hannah shares stories of customers who survived worst-case scenarios because Object First was the only thing left standing, and one who tracked him down simply to say thank you. In an era where AI is accelerating attacks and a single compromised password has bankrupted companies, knowing you can recover is the new definition of good enough. This is a Brand Spotlight. A Brand Spotlight is a ~15 minute conversation designed to explore the guest, their company, and what makes their approach unique. Learn more: https://www.studioc60.com/creation#spotlight GUEST Pete Hannah, VP of Sales, Western Europe, Object First LinkedIn: https://www.linkedin.com/in/peterhannah/ RESOURCES Learn more about Object First: https://objectfirst.com Ootbi by Object First (Out-of-the-Box Immutability): https://objectfirst.com Watch: Anthony Cusimano of Object First at RSAC Conference: https://youtu.be/LMWuZ_NH1lA Infosecurity Europe 2026 event coverage: https://www.itspmagazine.com/infosecurity-europe-2026-infosec-london-cybersecurity-event-coverage Are you interested in telling your story? ▶︎ Full Length Brand Story: https://www.studioc60.com/content-creation#full ▶︎ Brand Spotlight Story: https://www.studioc60.com/content-creation#spotlight ▶︎ Brand Highlight Story: https://www.studioc60.com/content-creation#highlight ▶︎ Get your own Brand Briefing at an upcoming event: https://www.studioc60.com/buy-brand-briefings KEYWORDS Pete Hannah, Object First, Ootbi, Sean Martin, brand story, brand marketing, marketing podcast, brand spotlight, immutable backup storage, ransomware recovery, Veeam backup, absolute immutability, Cyber Security and Resilience Bill, cyber resilience, data protection, operational resilience, backup and recovery, Infosecurity Europe 2026 Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Savage warns that we are living through a more militant form of Islam today than we have seen in over 150 years. He examines the past to expose how a sect of Islam has emerged that is intolerant and into total subjugation and conquest. What can America learn from the fall of England, France, and Belgium to radical Muslim conquest? He argues that New York City Mayor Mamdani is the tip of the spear to the Muslim Brotherhood and he should not be dismissed as a friendly, benevolent character. Savage still holds onto hope that the more peaceful coalition of Muslims will prevail, but warns that Western Europe may serve as a warning signal to the United States.

The June 8, 2026, edition of the Closing Market Report provides an assessment of agricultural commodities, upcoming USDA reports, and global weather impacts. Curt Kimmel of AgMarket.net highlights that a recent screwworm outbreak is causing market volatility, though long-term impacts depend on the disease's spread and its effect on available cattle supplies. Kimmel also anticipates minor adjustments in the upcoming WASDE report, projecting slight decreases in new crop corn ending stocks due to old crop demand, with soybeans and wheat remaining largely unchanged. Frayne Olson from North Dakota State University corroborates this subdued expectation for the June WASDE, noting the USDA is unlikely to revise export forecasts without concrete details from recent US-China trade agreements. Olson emphasizes the significance of the June 30th grain stocks report for tracking feed consumption and explains that recent market fluctuations are heavily influenced by index fund investors shifting capital between energy, agriculture, and the stabilizing stock market. Consequently, Olson advises producers to establish predetermined target prices rather than attempting to time volatile market swings. Finally, Everstream Analytics meteorologist Mark Russo reports that beneficial rainfall and above-average temperatures are accelerating crop development across the US Corn Belt, presenting no immediate yield threats. However, Russo warns that a returning, near-record heatwave combined with dry conditions in Western Europe poses a significant risk to their summer crops.- Ag Markets with Curt Kimmel, AgMarkets.net- Commodity Markets Discussion with Frayne Olson, NDSU Extension- Ag Weather with Mark Russo, EverStream.ai ★ Support this podcast ★

Marking the 82nd anniversary of D-Day, Secretary of War Pete Hegseth traveled to France on June 6 to commemorate the troops who helped liberate Western Europe. Hegseth spoke at the Normandy American Cemetery and urged today's generation not to forget those who fought and died on D-Day.U.S. Central Command shoots down four Iranian attack drones heading for the Strait of Hormuz, calling them an immediate threat to sea traffic in the region.As of June 6, former Biden health secretary Xavier Becerra will advance to the November election for California governor, according to a race called by the Associated Press. As vote counting continues, his opponent has not yet been determined.

Mary welcomes Thomas Littleton to this edition of SUFTT to talk about the descent into compromise over LGBTQ inclusion theology in conservative – yes, conservative – churches. Thomas Littleton is an ordained Southern Baptist minister and evangelist with over 4 1/2 decades on the streets of such places as New Orleans, Atlanta, and New York City (while in New York he worked with David Wilkerson’s Times Square Church, author of The Cross and the Switchblade). He has also done extensive outreach at America’s beaches, university campuses, and foreign fields of Eastern and Western Europe and Central and South America. He has a long history engaging the Arts and LGBT community through heading a Christian Arts based ministry in NW Georgia and worked on the front lines of the AIDS health crisis of the mid 80s and 90s. Littleton knows the origins, methods and goals of the LGBTQ activist movement and the faithful Biblical response for believers anchored in the power of the Gospel by the CROSS and resurrection of Jesus. We talk about his fight for truth over the last dozen years to hold high the standard of the gospel and the truth that can transform any sinner by the power of the Holy Spirit.     Stand Up For The Truth Videos: https://rumble.com/user/CTRNOnline & https://www.youtube.com/channel/UCgQQSvKiMcglId7oGc5c46A

We're in This Together. In this episode, we sit with Bo Giertz and read his open letter to the churches — A Shepherd's Letter. As translator, Bror Erickson says of the opening section (we read on the show), "Crises and Sources of Strength": "Christians had been systematically persecuted by the Nazis, and this systematic persecution continued in soviet countries. However, in Western Europe, church leaders like Bo Giertz saw how increasing industrialization was also assisting an increasing secularism. There were huge population shifts into the city, and people lost track of the church even as the church lost track of the people during these shifts. Some political parties were also actively hostile to the church. The trends toward secularism and atheism in the West have continued, of course, and have also become a point of consternation for believers even to this day. This age has not ceased to be evil since Paul designated it as such in Gal. 1:4. So the church continues and will continue to suffer crises, and so the essay "Crises and Sources of Strength" takes on a sort of timeless dimension that way. SHOW NOTES:  Bo Giertz - A Shepherd's Letter https://shop.1517.org/products/9781948969987-a-shepherds-letter   More from 1517: Support 1517 Podcast Network: https://www.1517.org/donate-podcasts 1517 Podcasts: http://www.1517.org/podcasts 1517 on YouTube: https://www.youtube.com/@1517org 1517 Podcast Network on Apple Podcasts: https://podcasts.apple.com/us/channel/1517-podcast-network/id6442751370 1517 Events Schedule: https://www.1517.org/events 1517 Academy - Free Theological Education: https://academy.1517.org/   What's New from 1517: By Water and the Word by Brian Thomas: https://shop.1517.org/products/9781967920013-by-water-and-the-word?srsltid=AfmBOopBUXbtbkYK0o6UHbWQm8_6UA7hG6B4RXYSeMxos6wbtbxX3Hnk Being Family by Dr. Scott Keith https://shop.1517.org/products/9781964419961-being-family?srsltid=AfmBOooZqqK-X8KqD64jZn1qUUrqiRwO-l3S4Z_WtIcfayMLAlTyHgoN A Reasoned Defense of the Faith by Adam Francisco https://shop.1517.org/collections/coming-soon/products/9781964419879-a-reasoned-defense-of-the-faith Stretched: A Study for Lent and the Entire Christian Life by Dr. Christopher Richmann https://shop.1517.org/products/9781964419381-stretched The Essential Nestingen: Essays on Preaching, Catechism, and the Reformation https://shop.1517.org/products/9781964419121-the-essential-nestingen   More from the hosts: Donovan Riley https://www.1517.org/contributors/donavon-riley  Christopher Gillespie https://www.1517.org/contributors/christopher-gillespie   CONTACT and FOLLOW: Email mailto:BannedBooks@1517.org  Facebook https://www.facebook.com/BannedBooksPod/  Twitter https://twitter.com/bannedbooks1517   SUBSCRIBE: YouTube https://www.youtube.com/@BannedBooks Rumble https://rumble.com/c/c-1223313  Odysee https://odysee.com/@bannedbooks:5 Apple Podcasts https://podcasts.apple.com/us/podcast/banned-books/id1370993639  Spotify https://open.spotify.com/show/2ahA20sZMpBxg9vgiRVQba  Overcast https://overcast.fm/itunes1370993639/banned-books    MORE LINKS: Banned Books Wiki https://bannedbooks1517.org  Tin Foil Haloes https://t.me/bannedpastors St John's Lutheran Church (Webster, MN) - FB Live Bible Study Group https://www.facebook.com/groups/356667039608511  Donavon's Substack https://donavonlriley.substack.com Gillespie's Sermons and Catechesis https://outerrimterritories.com/recent-sermons Gillespie Coffee https://gillespie.coffee   Gillespie Media https://gillespie.media  

The UK, Ireland, France, Spain, and Portugal shattered their May heat records last week. Scenes reminiscent of high summer arrived months early, across Western Europe. And like all extreme weather events, there was a human toll. Infrastructure under strain, health services stretched, and lives lost. But as records fell, the political conversation was moving in the other direction. Former UK Prime Minister Tony Blair published a lengthy essay calling on the government to halt its net zero acceleration and prioritise cheap energy. Rory Stewart made a similar case on The Rest is Politics, invoking AI data centres and industrial competitiveness. Both are figures from the centre of British politics. Neither is a climate denier. So what's happening? This week, Tom Rivett-Carnac and Christiana Figueres sit with this dissonance. They ask what it means when hopelessness becomes self-sustaining, a cultural condition as much as a feeling. They ask whether grief, properly faced, might be what unlocks action rather than foreclosing it. And they look at the history of transformations that began long before success seemed likely.Is the real crisis not just the climate, but one of agency? And what does it take to act with conviction when outcomes are genuinely uncertain?Learn More:☀️ See Severe Weather Europe's recap of the historic heat dome across Europe

This week: two audio essays. First up, they're calling it the Poor Man's Tomahawk. Ukraine is firing up to 2000 long range drones a week into Russia. The production facilities supplying them are scattered across Western Europe. These production facilities have an artificial shield, in that they are diplomatically protected. But how long this will last is unclear. For its part, Ukraine would like the West to be more active in the war. And one way to do that would be to antagonise Russia into responding beyond its borders. There is now a 50% chance of erratic strikes into Europe proper within the next year, as Philip Pilkington makes clear in The Escalation Ladder. Meanwhile, Andrew Collingwood has been supping on a 2019 masterwork of geopolitics. Weaponized Interdependence is the title of a Henry Farrell and Abraham Newman paper, in which the pair argue that states with political authority over the central "hubs" in global economic networks: such as those for finance, data, and trade, can exploit this position to gain a strategic advantage. States sitting atop those nodes can exploit two effects: panopticon (information dominance) and choke point (cutting off access to irreplaceable hubs).Hormuz is one hub. Russia has its commodity hubs. And China has its manufacturing hub dominance. Put it all together, and the new Iran war has revealed a structural shift in global power, says Andrew Collingwood. Of course, this is a pay week — if you want access to this episode, you're going to have to go on Patreon, and sign up. Simply type Multipolarity into the search bar and do the needful. Alternatively, you can now get premium episodes and our regular print work over on Substack for 12 USD a month. The choice is yours, but don't get caught in no man's land.

At a workshop owned by Jiangsu Zhufeng Electromechanical Technology Co in Xuzhou, Jiangsu province, a buyer evaluated an electric three-wheeler model destined for Indonesia, discussing modifications with engineers, who took detailed notes on the customer‘s requirements.在江苏省徐州市的江苏珠峰机电科技有限公司车间里，一位买家正在评估一款即将发往印度尼西亚的电动三轮车，并与工程师商讨改装方案，工程师们则认真记录着客户的每一项需求。As concerns over fuel costs and energy security grow globally, China's electric three-wheelers, widely used to transport people and goods, have seen a surge in demand in overseas markets in recent months.随着全球对燃料成本和能源安全的担忧日益加剧，近几个月来，中国用于客货运输的电动三轮车在海外市场需求激增。Jiangsu Zhufeng Electromechanical Technology Co produced nearly 30,000 units in 2025, with exports mainly destined for the United States, Turkiye, Cambodia and Indonesia. With its products having entered Brunei, Vietnam and Laos this year, the company expects its annual production to surpass 50,000 units.江苏珠峰机电科技有限公司2025年产量近3万辆，产品主要出口至美国、土耳其、柬埔寨和印度尼西亚。随着其产品今年进入文莱、越南和老挝市场，该公司预计年产量将突破5万辆。From January to April this year, exports of electric three-wheelers from Xuzhou reached 168 million yuan ($24.8 million), up 87.1 percent year-on-year, while exports of related parts and components totaled 115 million yuan, an increase of 29.6 percent from a year earlier, according to data from Xuzhou Customs.徐州海关数据显示，今年1至4月，徐州电动三轮车出口额达1.68亿元人民币，同比增长87.1%；相关零配件出口额达1.15亿元，同比增长29.6%。Dai Hui, deputy head of Xuzhou Customs, said that three-wheelers made in Xuzhou have reached more than 130 countries and regions.徐州海关副关长戴辉表示，徐州制造的电动三轮车已出口至130多个国家和地区。"In addition to emerging markets, the next frontier is North America, Western Europe and Northern Europe, where exporters are stepping up efforts to expand their presence," Dai said.戴辉说：“除了新兴市场，下一个前沿阵地是北美、西欧和北欧，出口商正在加大力度拓展这些地区的业务。”Ni Xiaofeng, president of Jiangsu Guowei Motorcycle Co, another three-wheeler manufacturer based in Wuxi, Jiangsu, said the growing appeal of low-cost, energy-efficient transportation solutions, coupled with stricter environmental regulations and efforts to reduce reliance on fossil fuels, have further boosted demand for Chinese three-wheelers in overseas markets.江苏国威摩托车有限公司总裁倪晓峰表示，低成本、高能效的交通解决方案吸引力不断提升，加之环保法规日益严格，以及各国努力减少对化石燃料的依赖，进一步提振了中国三轮车在海外市场的需求。"A standard electric three-wheeler and similar models typically sell for $3,000 to $6,000 in European and North American markets," he said.他说：“在欧洲和北美市场，一辆标准款电动三轮车及同类车型的售价通常在3000至6000美元之间。”Li Chengyun, head of the technical unit of Xuzhou Zhibo Locomotive Co in Xuzhou, said most electric three-wheelers on the market offer a driving range of 80 to 100 kilometers with standard lithium batteries. For an additional cost, customers can choose larger battery packs, which increase the range to as much as 180 to 220 kilometers.徐州智博机车有限公司技术部负责人李承运（音译）表示，市场上大多数电动三轮车标配锂电池的续航里程为80至100公里。客户可选择额外付费升级更大容量的电池包，将续航里程提升至180至220公里。"More overseas customers are demanding higher power output, prompting us to equip vehicles with larger motors," Li said. "Buyers are also requesting larger and wider tires and wheel rims, leading the company to adopt aluminum alloy wheels to better meet customers' specifications."李承运说：“越来越多的海外客户要求更高的动力输出，这促使我们为车辆配备更大功率的电机。买家还对更宽大的轮胎和轮辋提出了要求，这使得公司采用铝合金轮毂，以更好地满足客户的规格要求。”Zhang Hui, president of Xuzhou Zhibo Locomotive Co, said that in the long run, concerns over fuel supply disruptions and the search for affordable transportation alternatives will continue to drive the global adoption of electric three-wheelers.徐州智博机车有限公司总裁张辉表示，从长远来看，对燃油供应中断的担忧以及对经济型交通替代方案的探索，将持续推动电动三轮车在全球的普及。Beyond traditional cargo and passenger-carrying three-wheelers, manufacturers are increasingly branching into specialty and recreational vehicles to diversify their product offerings.除了传统的客货两用三轮车，制造商正越来越多地涉足特种车辆和休闲车辆领域，以实现产品线的多元化。He Shan, sales director at Jiangsu Shanming Shuixiu Environmental Protection Technology Co in Xuzhou, said the company's business originally focused on manufacturing cargo three-wheelers, but shifted toward developing and exporting specialty vehicles such as road sweepers after spotting growing demand in niche markets.江苏山明水秀环保科技有限公司销售总监贺珊表示，该公司原本以生产货运三轮车为主，但在发现利基市场需求不断增长后，转而开发和出口道路清扫车等特种车辆。"We are rolling out upgraded models that can sweep streets, wash surfaces, spray water mist and suppress dust. A single sweeper can do the work of more than a dozen people," He said.贺珊说：“我们正在推出能够清扫街道、清洗路面、喷雾降尘的升级版车型。一台清扫车能完成十几个人的工作量。”Household-use three-wheelers, passenger shuttles and leisure vehicles designed for tourist attractions and golf courses have become key growth segments for many traditional electric three-wheeler manufacturers, said Chen Bin, deputy director of the expert committee of the Beijing-based China Machinery Industry Federation.中国机械工业联合会专家委员会副主任陈斌表示，家用三轮车、景区摆渡车以及专为旅游景点和高尔夫球场设计的休闲车辆，已成为众多传统电动三轮车制造商的关键增长领域。Chen said the growing popularity of electric three-wheelers reflects a broader shift toward affordable, energy-efficient mobility solutions, creating new opportunities for Chinese manufacturers in global markets.陈斌指出，电动三轮车的日益普及，反映出全球交通出行正朝着经济型、高能效方向转变，这为中国制造商在全球市场创造了新的机遇。traction /ˈtrækʃən/吸引力，受欢迎程度environmental regulations /ɪnˌvaɪrənˈmentəl ˌreɡjʊˈleɪʃənz/环保法规lithium battery /ˈlɪθiəm ˈbætəri/锂电池driving range /ˈdraɪvɪŋ reɪndʒ/续航里程road sweeper /rəʊd ˈswiːpə/道路清扫车niche market /niːʃ ˈmɑːkɪt/利基市场，细分市场

This episode unpacks how the Marshall Plan transformed postwar Western Europe and why security, allied cooperation, and forward thinking were the real keys to its enduring success.   To mark the 250th anniversary of the U.S. declaration of independence, CFR is dedicating a yearlong series of articles, videos, podcasts, events, and special projects that will reflect on two and a half centuries of U.S. foreign policy. Featuring bipartisan voices and expert contributors, the series explores the evolution of America's role in the world and the strategic challenges that lie ahead.   Host: James M. Lindsay, Mary and David Boies Distinguished Senior Fellow in U.S. Foreign Policy, CFR   Guest: Benn Steil, Senior Fellow and Director of International Economics, CFR   We Discuss: How the British Empire's rapid collapse in early 1947 forced the United States to assume responsibility for Western European security. What George Marshall's six weeks of negotiations in Moscow revealed about Soviet intentions in Germany and Western Europe. How Marshall deliberately crafted the plan's offer to include the Soviet Union while ensuring Soviet leader Joseph Stalin would reject it. How Congress, controlled by Republicans, was persuaded to support a massive foreign aid program from a Democratic administration. Whether the Marshall Plan's $13 billion actually explains Western Europe's economic recovery in the late 1940s. What role NATO played in making the Marshall Plan work, and why the French and British insisted on security guarantees before cooperating. Why security has to precede economic reconstruction—and what Afghanistan and Iraq  reveal about ignoring that lesson. What Senator Henry Cabot Lodge Jr.'s 1947 prediction about sustained alliances tells us about the stakes of U.S. foreign policy today.   Mentioned on the Episode:   The 10 Best and Worst Decisions in U.S. Foreign Policy, Council on Foreign Relations   Benn Steil, The Marshall Plan: Dawn of the Cold War   George Kennan's Long Telegram, February 22, 1946   “Sinews of Peace (‘Iron Curtain' Speech).” at Westminster College, Fulton, Missouri, March 5, 1946.   Harry Truman, “The Truman Doctrine,” Address to Congress, March 12, 1947   George C. Marshall, Commencement Address at Harvard University June 5, 1947   For an episode transcript and show notes, visit The President's Inbox at: https://www.cfr.org/podcasts/presidents-inbox/america-at-250-the-marshall-plan   Opinions expressed on The President's Inbox are solely those of the host or guests, not of CFR, which takes no institutional positions on matters of policy.

Best Esim For Travelers: $27 a month, unlimited data, 100+ countries = pangia pass Use my link for 10% off: https://pangiapass.com/a/bold Find Me Here: https://linktr.ee/bold.perceptions Travel / Lifestyle Consultation, DM Me On Instagram: bold_perceptions #travel #travelblogger #podcast #europe #latinamerica #florida #solotravel #podcasting Al slop summary for keywords : Western Europe is one of the easiest places in the world to romanticize. You step off a train in cities like Paris, Florence, Vienna, or Amsterdam and it feels like centuries of wealth, art, empire, and philosophy are layered directly into the streets. The architecture alone can overwhelm you. Cathedrals built before entire countries existed in the Americas. Cafés where writers, revolutionaries, and painters spent decades shaping culture. The infrastructure is polished, the museums endless, and even ordinary neighborhoods can feel cinematic. But what surprises many travelers is how deeply routine it all is for locals. The beauty becomes normalized. People casually drink wine beside buildings older than most civilizations in the Western Hemisphere. Western Europe feels refined, stable, and historically “finished” in a way few regions on Earth do. Eastern Europe hits differently. It feels heavier, rawer, and in many ways more honest. The scars of war, communism, occupation, and survival are still visible in the architecture and mentality. Cities like Budapest, Belgrade, Kraków, Bucharest, or Sarajevo carry a tension between old-world beauty and recent hardship. You can walk through grand Austro-Hungarian boulevards, then see Soviet apartment blocks only minutes away. The people are often less performative for tourists and more direct in conversation. Prices are lower, nightlife can be wilder, and the atmosphere feels less commercialized than Western Europe. There's also a stronger feeling that history here was not just written in books but lived recently by grandparents still alive today. Eastern Europe often leaves travelers with deeper memories because it feels less filtered and more emotionally textured. One of the biggest differences between traveling Europe and traveling Latin America is the relationship between order and spontaneity. Europe, especially Western Europe, operates with systems that have been refined for generations. Trains run on schedules. Streets were designed for walking centuries ago. Public life functions with a certain predictability. Latin America feels more alive in a chaotic sense. Plans change. Conversations last longer. Bureaucracy can feel irrational one moment and strangely human the next. In Europe, efficiency often dominates culture. In Latin America, relationships dominate culture. Neither is automatically better. One gives structure and reliability. The other gives warmth, adaptability, and energy. Travelers who understand this distinction usually enjoy both regions far more because they stop expecting them to operate the same way.

In this episode of Sharing My Truth, Mel and Suzie tackle one of the most controversial dating trends of the last few years. More and more men are looking beyond North America and Western Europe for love, claiming they can find more traditional values, stronger relationships, and better dating experiences abroad. But does it actually work? Mel and Suzie explore why some men are leaving the Western dating market, what women think about the Passport Bros movement, the realities of international dating, cultural differences, financial expectations, and whether moving across the world is really the answer to modern dating frustrations. Is this a genuine solution for men struggling to find love, or are there challenges that nobody talks about? If you've ever wondered why so many men are looking overseas for relationships, this episode is for you. Join Mel and Suzie for an honest, balanced conversation about one of the most talked-about trends in dating today Want more honest dating advice from women who actually tell you the truth? Check out our free guide: Female Brain Decoded Want more unfiltered conversations? Join us on Patreon for bonus episodes, deeper dives, and behind-the-scenes conversations, you won't hear anywhere else. Meet our partner guybrator.com premium products for confidence, comfort, and discretion. Got a story to share with us? Leave us a voicemail by clicking here. Email us: stories@sharingmytruth.com or DM us on Instagram Follow us on Instagram @sharingmytruthpod, TikTok @sharingmytruthpod Facebook @sharingmytruthpod , YouTube @sharingmytruthpod Sign up to our weekly newsletter and join the Sharing My Truth Community sharingmytruth.com   .

If you enjoy this episode, we're sure you will enjoy more content like this on The Occult Rejects.  In fact, we have curated playlists on occult topics like grimoires, esoteric concepts and phenomena, occult history, analyzing true crime and cults with an occult lens, Para politics, and occultism in music. Whether you enjoy consuming your content visually or via audio, we've got you covered - and it will always be provided free of charge.  So, if you enjoy what we do and want to support our work of providing accessible, free content on various platforms, please consider making a donation to the links provided below.  Thank you and enjoy the episode!Links For The Occult Rejectshttps://linktr.ee/theoccultrejectsOccult Research Institutehttps://www.occultresearchinstitute.org/Substackhttps://substack.com/@theoccultrejects?r=7auau0&utm_campaign=profile&utm_medium=profile-pageCash Apphttps://cash.app/$theoccultrejectsVenmo@TheOccultRejectsBuy Me A Coffeebuymeacoffee.com/TheOccultRejectsPatreonhttps://www.patreon.com/TheOccultRejectsBIBLIOGRAPHYHidden Rooms, Holy Water, and the DeadWhite, L. Michael. The Social Origins of Christian Architecture, Volume I: Building God's House in the Roman World: Architectural Adaptation Among Pagans, Jews, and Christians. Trinity Press International, 1996. Key use: Essential source for early Christian architectural adaptation, especially the shift from domestic and semi-domestic gathering spaces toward more specialized Christian buildings. White's work is useful for showing that early Christian architecture develops inside a broader Roman social and architectural world, not in isolation.White, L. Michael. The Social Origins of Christian Architecture, Volume II: Texts and Monuments for the Christian Domus Ecclesiae in Its Environment. Trinity Press International, 1997. Key use: Companion volume for the textual and archaeological evidence behind the domus ecclesiae, early meeting spaces, and the built environment of pre-Constantinian Christianity.Yale University Art Gallery. “Christian Building.” Dura-Europos: Excavating Antiquity. Key use: Strong anchor for the Dura-Europos Christian building and its wall paintings. Yale notes that the Christian paintings were uncovered in 1932 and that Clark Hopkins described the murals as preserved from more than three-quarters of a century before Constantine recognized Christianity in 312.Yale News. “House Call: A New Study Rethinks Early Christian Landmark.” 2024. Key use: Useful cautionary source for not oversimplifying Dura-Europos as merely a domestic “house church.” The report highlights recent scholarship reexamining how domestic the Dura Christian building really was and why its architectural classification needs care.Smarthistory. “Dura-Europos.” Key use: Accessible overview of Dura-Europos as a multicultural Roman frontier site, including the adapted Christian building used as a meeting place and baptistery in the first half of the third century.Peppard, Michael. The World's Oldest Church: Bible, Art, and Ritual at Dura-Europos, Syria. Yale University Press, 2016. Key use: Major source for the Dura-Europos Christian building, its baptistery, biblical imagery, ritual use, and the danger of reading the site too simply through later church categories.Snyder, Graydon F. Ante Pacem: Archaeological Evidence of Church Life Before Constantine. Mercer University Press, revised edition, 2003. Key use: Important archaeological source for Christian life before Constantine, especially material evidence for worship, burial, symbols, and everyday Christian practice before public imperial privilege. Mercer University Press identifies the book as focused on archaeological evidence of church life before Constantine.Jensen, Robin M. Baptismal Imagery in Early Christianity: Ritual, Visual, and Theological Dimensions. Baker Academic, 2012. Key use: Core source for baptismal images, ritual meaning, water, initiation, death and rebirth, and the way visual programs frame baptismal practice.Jensen, Robin M. Understanding Early Christian Art. Routledge, 2000. Key use: Early Christian visual culture, catacomb imagery, baptismal scenes, Good Shepherd imagery, Jonah, Daniel, Lazarus, and the visual language of salvation and resurrection.Ferguson, Everett. Baptism in the Early Church: History, Theology, and Liturgy in the First Five Centuries. Eerdmans, 2009. Key use: Major historical and theological source for baptismal practice, initiation, immersion, anointing, catechesis, and the development of baptismal rites.Johnson, Maxwell E. The Rites of Christian Initiation: Their Evolution and Interpretation. Liturgical Press. Key use: Development of initiation rites, catechumenate, baptism, post-baptismal rites, and how Christian initiation becomes structured over time.Spinks, Bryan D. Early and Medieval Rituals and Theologies of Baptism: From the New Testament to the Council of Trent. Ashgate, 2006. Key use: Long-range ritual and theological development of baptism, useful for tracking how early baptismal space later becomes more formalized.Britannica. “Catacomb.” Key use: Baseline definition of catacombs as subterranean cemeteries composed of galleries or passages with recesses for tombs; useful for correcting the popular misconception that catacombs were primarily secret churches rather than burial landscapes.Stevenson, James. The Catacombs: Rediscovered Monuments of Early Christianity. Thames & Hudson, 1978. Key use: Classic overview of Roman catacombs, burial architecture, inscriptions, symbols, and early Christian memory.Rutgers, Leonard V. Subterranean Rome: In Search of the Roots of Christianity in the Catacombs of the Eternal City. Peeters, 2000. Key use: Catacombs as archaeological and social evidence, including burial practice, community identity, and the relationship between Jews, Christians, and Roman funerary culture.Fiocchi Nicolai, Vincenzo, Fabrizio Bisconti, and Danilo Mazzoleni. The Christian Catacombs of Rome: History, Decoration, Inscriptions. Schnell & Steiner, 2002. Key use: Detailed treatment of catacomb history, inscriptions, burial spaces, and visual programs.Brown, Peter. The Cult of the Saints: Its Rise and Function in Latin Christianity. University of Chicago Press, enlarged edition. Key use: Essential source for the holy dead, saint veneration, relics, tombs, pilgrimage, and the way corporeal remains became central to Christian religious life. The University of Chicago Press describes Brown's work as exploring how worship of saints and their corporeal remains became central to religious life in Western Europe.Brown, Peter. The Body and Society: Men, Women, and Sexual Renunciation in Early Christianity. Columbia University Press, 1988. Key use: Christian body theology, asceticism, holiness, discipline, and why the body is so central to late antique Christian imagination.Yasin, Ann Marie. Saints and Church Spaces in the Late Antique Mediterranean: Architecture, Cult, and Community. Cambridge University Press, 2009. Key use: Churches, saints, relics, cult practice, community identity, and how sacred spaces are organized around holy bodies and memory.Grabar, André. Martyrium: Recherches sur le culte des reliques et l'art chrétien antique. Key use: Classic work on martyr shrines, relic cult, and the relationship between architecture, art, and the holy dead.van Gennep, Arnold. The Rites of Passage. Key use: Separation, liminality, and incorporation. Crucial for baptism, catechumenate, thresholds, initiation, and the movement from outsider to insider.Turner, Victor. The Ritual Process: Structure and Anti-Structure. Key use: Liminality, threshold states, ritual transition, and communitas. Useful for baptism, catacomb descent, martyr devotion, and controlled access.Kilde, Jeanne Halgren. Sacred Power, Sacred Space: An Introduction to Christian Architecture and Worship. Oxford University Press, 2008. Key use: Christian buildings as arrangements of power, worship, divine presence, and embodied access. Useful for thresholds, sanctuary divisions, nave, altar, and congregation.Kieckhefer, Richard. Theology in Stone: Church Architecture from Byzantium to Berkeley. Oxford University Press, 2004. Key use: Church architecture as theology made spatial. Useful for altar, pulpit, nave, threshold, symbolic layout, and worship practice.Krautheimer, Richard. Early Christian and Byzantine Architecture. Yale University Press / Pelican History of Art. Key use: Classic architectural history for early Christian and Byzantine buildings, including the shift from pre-Constantinian spaces to basilicas, baptisteries, martyr shrines, and later monumental forms.Mathews, Thomas F. The Clash of Gods: A Reinterpretation of Early Christian Art. Princeton University Press, 1993. Key use: Early Christian imagery, visual conflict, ritual meaning, and the development of Christian art within the Roman world.Elsner, Jaś. Imperial Rome and Christian Triumph: The Art of the Roman Empire AD 100–450. Oxford University Press, 1998. Key use: Roman visual culture, Christian adaptation, imperial imagery, and the shift into Christian public art and architecture.MacMullen, Ramsay. Christianizing the Roman Empire: A.D. 100–400. Yale University Press, 1984. Key use: Social and historical context for Christian expansion before and after Constantine, useful for understanding how Christian space changes as Christianity grows.Mango, Cyril. Byzantine Architecture. Key use: LonAlso want to remind people about the website, if you're into reading we have tons of information by multiple contributors, and we got t-shirts up on the site if you're interested. Fun fact, the art is all based on the eyeball. A

Proverbs 13:20-14:4, 2 Samuel 1:1-2:7, John 20:11-31. There are many blessings to living in Western Europe in the twenty-first century However, we live in a society in which respect, awe and reverence do not seem to be as valued as they once were

Proverbs 13:20, 14:2-3, 2 Samuel 1:12-14, 2:1, John 20:11-28. There are many blessings to living in Western Europe in the twenty-first century However, we live in a society in which respect, awe and reverence do not seem to be as valued as they once were

Proverbs 13:20, 14:2-3, 2 Samuel 1:12-14, 2:1, John 20:11-28. There are many blessings to living in Western Europe in the twenty-first century However, we live in a society in which respect, awe and reverence do not seem to be as valued as they once were

In this episode, we speak with Christian Friberg from PPI and Ralf Schopohl from SIZ to explore the evolution of EBICS, the implementation of verification of payee in the European savings banking sector, and the critical role the Mainframe plays in ensuring secure, resilient and compliant transaction processing. We discuss how PPI and SIZ began their collaboration, the origins of EBICS as a German standard now adopted across Western Europe, and how core server-side programs running on IBM Z support the security and integrity of modern banking services.Stay ConnectedBe part of the conversation! Join the ISV Ecosystem User Group to explore the latest blogs, events, videos, and more from IBM Z partners and innovators.And don't forget to subscribe to z/Action!Each month, we spotlight some of the world's most innovative companies and how they're driving success with IBM Z.

We welcome back John Ward as we discuss John Dee, Magick, Occultism, John's Haunted House, UFO's and more... Dr. John Ward is an archaeologist and anthropologist residing in Luxor, Egypt. Over the years, Dr. Ward has conducted numerous investigations of ancient Egyptian architecture and symbolism, while also carrying out research into the many mysteries surrounding medieval Templarism. With the help of his partner, Dr. Maria Nilsson, John has managed to track the use of particular symbols through the various dynasties and the geography of ancient Egypt leading all the way into the present, with similar threads even extending into parts of Western Europe. The symbols that John and Maria have come to recognize play a very important and integral role, based from their studies, regarding ancient Egyptian life. It is through these symbols that they are driven with the passion to continue their work, which has enabled them not only to develop a greater understanding of the various cultures they study, but also to utilize and acknowledge the importance and sanctity of the symbols. These are aspects which, John argues, still remain largely unknown to mainstream academia. Hosted on Acast. See acast.com/privacy for more information.

We are now recording an audio version of written posts that we will upload to Apple, Spotify, and YouTube, which you can listen to by clicking the button the play button above.As the Strait of Hormuz (SoH) Crisis completes its third month and on-again/off-again peace talks drag on, we are starting to see the outlines of various structural themes emerging, and, as importantly, some that are not. Thematically we see the following:* Power Surge! Our Power Surge! super-cycle theme has not only not been knocked off track by the SoH Crisis, but has likely been enhanced based on “the four Ds” of pragmatic energy policy orientation we discuss below. Recently completed 1Q 2026 earnings season shows the AI (artificial intelligence) and broader digital transformation theme is as strong as ever.* Geopolitical Super Vol. Geopolitical Super Vol remains our commodity macro framework, in particular for crude oil prices. Since Russia-Ukraine and through SoH-to-date, we have resisted crude oil super-cycle framings while also, importantly, rejecting perma bear doom-and-gloom. The unforgiving math of global oil demand being forced down to circa 95 million b/d of supply from around 105 million b/d pre-crisis suggests recession is the most likely clearing mechanism rather than a structural increase in long-dated oil prices in the event a significant disruption to flows persists. To be clear, we do see scope for a modest increase in long-end oil on the order of $10/bbl to account for both cost inflation and an increased geopolitical risk premium.* Molecules to markets. In our view, getting molecules to markets is the more pressing strategic imperative for countries than simply trying to find the molecules in the first place. In traditional energy, this puts a premium on well-positioned midstream and downstream assets. In the upstream business, there is always an opportunity to find acreage that is well positioned on the future cost curve. Having a midstream or downstream solution (e.g., LNG) may be an increasing success factor for larger E&P (exploration and production) companies.* New business models > pure-play (for larger companies). The era of extreme pure-play specialization we think will fade, or at least will no longer be the dominant ask of investors. Business model evolution is likely to continue to separate leaders from laggards. Examples we find intriguing include pressure pumpers and midstream companies diversifying into behind-the-meter (BTM) power, US shale gas producers expanding into midstream and potentially LNG, refiners that have grown midstream capabilities, midstream companies that have grown export opportunities, and the expanded commercial trading opportunities that larger companies have pursued. The list is growing.* Brownfield > greenfield (usually). The advantage of doing more from existing assets is something both countries and companies have in common. Brownfield almost always beats greenfield on profitability and speed-to-market, though a best-in-class greenfield project like Guyana oil is the type of exception that exists to the general rule.From an energy policy perspective, the Strait of Hormuz Crisis reveals what we are now calling the four Ds of country-level energy policy aspiration:* Do as much Domestic production as possible;* Diversify energy sources and technologies;* Do more from existing assets; and* embrace Digital transformation and AI.Subscribe to Super-Spiked to receive all content via email. Also available on https://veriten.com.The Four Ds of Pragmatic Energy PolicyThe four Ds are the pragmatic policy implication of country leaders recognizing energy's natural hierarchy of needs (Exhibit 1). On the right side of Exhibit 1, we rank (higher on list is better) resource rich countries and resource challenged areas in terms of federal policy orientation that recognizes energy's natural hierarchy of needs and implementation of the four Ds relative to a given country's strengths and weaknesses.Saudi Arabia and United Arab Emirates among resource rich regions and China among resource challenged areas we see as having favorable federal energy policy orientations. Laggards are not surprising: Western Europe, California, Canada, and Australia. What KSA, UAE, and China have in common are national leadership that emphasizes the ideas of “all of the above,” maximum (or optimal) output of what you can control, and unapologetic “their own country first” mentalities.Super-Spiked subscribers know we have a very favorable view of Canada's oil and gas potential and the leading companies in the province of Alberta. We had an unfavorable view of the federal energy policies pursued by the prior Trudeau regime, with the jury out on the current Carney administration. On the latter, we appreciate that the rhetoric has improved off a low starting point. The proof will be in the policy implementation pudding.No country should aspire to follow the path of California or Western Europe and their “climate first” ideology (dishonorable mention goes to many states in the US northeast). Sadly, poor energy policy choices made in those areas are going to mean that less fortunate consumers and businesses in developing Asia suffer from being outbid for needed energy like LNG, jet fuel, and diesel during times of stress, as we last saw in the early days of Russia-Ukraine. It has been some time since we have done a deep dive on Australia; our sense would be that it is in the Canada category of having substantial oil and gas resources that the world would massively benefit from, but is being held back by ill-advised climate-first ideology by its national leaders.Exhibit 1: A Hierarchy of Energy Needs & Country Policy Objectives and OrientationSource: Veriten.Doing More From Existing AssetsIn previous issues of Super-Spiked, we have discussed three of the Ds: do as much domestic production as possible, diversify energy sources and technology, and embrace digital transformation and AI. Therefore, in this post we will expand on the “do more from existing assets” theme.* A major advantage the developed world has over China, India, and other developing areas is a large installed base of assets and infrastructure. Prematurely retiring old power plants in the name of “energy transition” and “The Climate Crisis” is the type of 2020-2023 mistake that has hurt competitiveness and affordability in the United States and Western Europe. In power generation, we are intrigued with trying to answer the question of how much new generation from legacy sources (e.g., natural gas, BTM, and traditional nuclear) is needed versus how much new generation technology is needed (e.g., fuel cells, enhanced geothermal, advanced nuclear) versus how much can existing grid utilization be improved via flexible loads and various grid enhancing technologies. How much more can we get from existing is important to how much we need from the other two options.* In crude oil markets, we do not believe there is the urgency to figure out “what's next” from a resource perspective as there was in the 2004-2014 super-cycle. To be clear, this comment is intended at the macro level; individual companies are almost always in need of figuring out what's next. Exploration and capital spending is likely to grow but we do not believe the kind of re-rating that happened during China/BRICs is warranted now. Rather we are most intrigued with what companies are doing to extend asset life (i.e., resource to production ratio) via a combination of technology application, business development, and midstream/downstream investment that can ensure molecules get moved to markets and turned into usable end products. Ironically, the Middle East looks like a compelling upstream opportunity for western oil and gas firms, given improved fiscal terms in certain areas. We have long held a favorable view of Canada (our concerns about its federal energy policies notwithstanding) and Alaska. Recent developments in many Latin American countries warrant a fresh look at the region for western players.* The largest areas that seem ripe to “do more from existing” include US shale oil, US shale gas, Middle East oil, Canada's oil sands, Venezuela oil, and developed market power grids.Growth and opportunityThe five areas of energy where we are most confident in growth include:* US and global power generation* Midstream and downstream infrastructure for crude oil and various metals and minerals* Grid enhancing technologies* US and global natural gas* Renewables and storageThe long-term opportunity to grow nuclear power is going to prove to be compelling for many countries, justifying the required patience in terms of time to development. Nuclear is the ultimate baseload, domestic, clean energy source.We remain open-minded about emerging and new energy technologies. We are seeing current growth in fuel cells and optimism about enhanced geothermal on the power generation side of the business. The SoH Crisis will accelerate adoption of electric vehicles and LNG trucks in particular in oil importing countries for diversification and affordability reasons.The success of new business models should diminish investor and activist demand for pure-playsThere is a misperception that investors prefer pure-plays or that investors only want more dividends and stock buybacks. Investors prefer companies that generate superior profitability with differentiated growth. Both are needed to sustainably outperform: profitability AND growth.The challenge in mature, cyclical sectors is that corporate over-enthusiasm for growth usually erodes profitability to the point where investors demand a disavowal of growth in favor of profitability and returning capital to shareholders. To be sure, if structural demand growth for a given commodity is something like 1%-2% per year, the expected growth rates for the largest companies within that sector is unlikely to be any more than +/- 1%-2% of the broader demand trajectory.As businesses mature and growth slows, the demand by investors to focus on sub-parts of the business often increases in order to enhance the combination of per share growth and profitability for a particular business segment. The post-2014 oil super-cycle bust and growth in U.S. shale turbocharged the demand for pure-plays, especially within the traditional oil & gas value chains. Certain pure-play shale oil producers, midstream companies, and refiners in fact performed exceptionally well.Power is clearly in a super-cycle and traditional oil and gas is operating with a Geopolitical Super Vol macro backdrop (a dramatic improvement from the post super-cycle bust phase of 2015-2020) and business opportunities abounding in the different product lines and geographies.SoH Crisis FAQQuestion 1: Has an oil super-cycle begun?Answer: No. Our core view remains Geopolitical Super Vol, not super-cycle.Q2: Have the odds of “peak oil demand” increased?A: No, we don't think so. However, we are concerned that if the Strait remains significantly disrupted that the painful adjustment down in global oil demand could mean that we spend a good part of the remainder of this decade recovering back to pre-crisis demand levels as incremental supply is brought online. In our view, the timing of a more permanent peak in oil demand is unknowable so long as the other seven billion people on Earth continue to use only a fraction of the energy The Lucky 1 Billion of Us take for granted.Q3: Isn't AI and the resulting power demand growth forecasts a bubble waiting to pop?A: No or, perhaps more accurately, not at this time. The fact that numerous stock markets like the U.S. (S&P 500), Japan (NIKKEI), and South Korea (KOSPI) are at or near all-time highs may indeed reflect complacency with the risk of global recession due to the ongoing SoH Crisis. We would differentiate stock market complacency with an AI bubble. We see it in the areas where we spend a lot of time: digital transformation and the application of AI is a game changer for numerous businesses. The stock market may well experience a major correction if the world tips into recession. Whatever short-term setback that might mean for near-term power generation we think would be akin to the Great Financial Crisis hit to oil demand in the middle of the China/BRICs super-cycle of 2004-2014, i.e., it was temporary.Q4: Don't investors prefer “pure-plays” over diversified companies? A: That view is missing our point. Investors prefer companies with competitive profitability and differentiated growth opportunities. The demand for “pure-plays” typically is the result of a mature sector experiencing a structural downcycle and investors being disappointed on both profitability and growth. And for sure, some companies should remain as pure-plays. The larger a company's market capitalization and overall size, the less we think a pure-play business model makes sense, be it basin or geography or asset type or business line. For small-caps and new technologies, the pure-play business model is often logical.Q5: So E&Ps will merge with refiners?A: No, we aren't expecting that type of integration or diversification. A future “integrated E&P” likely means some combination of midstream and commercial exposure as opposed to a historical upstream-refining mix, as an example.⚡️On A Personal Note: Work Hard. Golf Hard.It's been a great three-week stretch of Spring golf ramp-up. 8 rounds in 5 days in and around Troon, Scotland the first week of May and then our NJ club's flagship member-member Governor's Trophy tournament over Memorial Day weekend featuring 45 holes of match play over 2 days. Day 2 of Governor's featured a good Scottish cold snap of low 50s weather and a light drizzle. Glad my rain pants got more work in and happy to be in sunny Houston as I finish writing this.At Governor's you can always see the short-game comfort from the returning Florida crowd versus those that stayed north over what is typically a 4-5 month winter hiatus. I failed to take advantage of part-time Houston residency this past winter and my partner and I didn't win our flight for the first time since 2021. Five 3 puts—FIVE!!!—from yours truly in Round 2 and two more missed make-able putts in Round 3 were seven half-point giveaways we did not overcome. Based on my accounting, my partner cost us only 2 points versus my 3.5, so the disappointing performance is on me. I'll need a stricter winter routine next year.I will say the Scotland golf intensity helped stamina at Governor's. The intensity and deliberate pace of hole-by-hole match play is usually mentally and physically draining. I didn't feel that this year. For future reference: I need to play 36 more often! It forces an easier swing. It improves mental resilience. Seems better than a cold plunge.Does a high level of golf intensity make you a better energy equity analyst, advisor, or board member? For sure it does. There is no question about this. Are we advising our companies to settle for mediocrity? That an 8% return on capital is good enough? That sector average TSR is fine? Of course not.Work Hard. Golf Hard.A Lot of Great Golf In Scotland: Western Gailes Near The Top Of My ListSource: Super-Spiked selfie.The Calm Before The Governor's Trophy StormSource: Super-Spiked.⚖️ DisclaimerI certify that these are my personal, strongly held views at the time of this post. My views are my own and not attributable to any affiliation, past or present. This is not an investment newsletter and there is no financial advice explicitly or implicitly provided here. My views can and will change in the future as warranted by updated analyses and developments. Some of my comments are made in jest for entertainment purposes; I sincerely mean no offense to anyone that takes issue.Subscribe to Super-Spiked to receive all content via email. Also available on https://veriten.com. This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit arjunmurti.substack.com

Watch On Youtube: https://www.youtube.com/watch?v=ad8FPqSKBXg Best Esim For Travelers: $27 a month, unlimited data, 100+ countries = pangia pass Use my link for 10% off: https://pangiapass.com/a/bold Find Me Here: https://linktr.ee/bold.perceptions Travel / Lifestyle Consultation, DM Me On Instagram: bold_perceptions #travel #nomad #latinamerica #southeastasia #colombia #digitalnomad #nomad #podcast #travelblogger #solotravel Al for keywords summary: Eastern Europe offers a compelling mix of rich history, architectural charm, and high digital infrastructure, making it a premier destination for location-independent professionals. In hub cities like Budapest (Hungary), Prague (Czechia), and Kraków (Poland), the lifestyle balances dynamic urban energy with relaxed, old-world leisure, featuring iconic café cultures, historic ruin bars, and extensive green spaces. For digital nomads, these Central-Eastern nations provide ultra-fast fiber-optic internet, expanding networks of modern co-working spaces, and strong English proficiency among locals. Furthermore, the establishment of official digital nomad visas across the region simplifies legal, long-term stays, allowing professionals to enjoy a high quality of life without the administrative stress of frequent border runs. Moving further south into the Balkan peninsula and outward to the Black Sea coast, countries like Bulgaria, Romania, and Albania introduce an exceptionally cost-effective and ruggedly scenic lifestyle. Here, daily life centers around a slower, community-oriented pace, where organic local markets, affordable traditional dining, and easy access to dramatic mountain ranges or pristine coastlines dominate the routine. For remote workers, this subregion is a hidden gem: Romania and Bulgaria consistently rank among the global leaders for average broadband and mobile internet speeds, while towns like Bansko, Bulgaria, have evolved into world-renowned, year-round nomad villages. Whether you are navigating the historical streets of Bucharest or working from a seaside café in Albania—which offers a highly favorable one-year visa-free stay for US citizens—the region combines low overhead costs with robust connectivity, allowing your income to stretch significantly further than in Western Europe. #travel #travelblogger #nomad #easterneurope #digitalnomad #poland #solotravel #podcast

Large parts of Western Europe are currently experiencing an early summer heat wave. In southern Germany, temperatures reach a peak of 34 degrees — and that already in late spring. - In weiten Teilen Westeuropas herrscht derzeit eine frühsommerliche Hitzewelle. In Süddeutschland erreichen die Temperaturen mit 34 Grad einen Höchstwert – und das schon im Spät-Frühling.In Großbritannien werden Rekordwerte gemeldet und in Frankreich starben sogar mehrere Menschen im Zusammenhang mit der ungewöhnlichen Wetterlage.Dem Deutschen Wetterdienst zufolge ist die Tropenhitze die Folge eines sogenannter Hitzedoms, der über Europa lagert.

Authorities in France say at least seven people have died due to unseasonably warm temperatures, while for the second day in a row, the UK has recorded a new record high for May. Much of Western Europe is still dealing with a pre-summer heatwave, leading to health warnings across the continent.Authorities in France say at least seven people have died due to unseasonably warm temperatures, while for the second day in a row, the UK has recorded a new record high for May.Much of Western Europe is still dealing with a pre-summer heatwave, leading to health warnings across the continent.

AP correspondent Charles de Ledesma reports on an Israeli attack against Hezbollah in Lebanon; an early summer heat wave grips parts of Western Europe; a devastating crash in Belgium causes deaths; Australians linked to the Islamic State groups return home; and the Hajj enters a second day.

Bulgaria is the Balkans' best-kept secret, which is both its charm and its tragedy. Sandwiched between Romania, Serbia, North Macedonia, Greece and Turkey, it offers Black Sea beaches, dramatic mountain ranges, ancient Thracian tombs, crumbling Ottoman mosques and an Orthodox monastic tradition of extraordinary beauty – all at prices that make Western Europe weep. The yogurt is excellent, the wine is underrated, and the rose oil is world-famous. Come before everyone else does.Love the pod? Get the guide! Out with each new podcast, we publish a guide to the country. Buy the TrodPod guide to Bulgaria for just $3: https://www.patreon.com/c/trodpod/shop. Better yet, become a TrodPod member for just $5 a month and access TrodPod guides to every country in the world, released weekly with each new podcast episode! Sign up now: https://www.patreon.com/trodpod/membershipThanks for all your support!TrodPod is Murray Garrard and Elle Keymer. Sound editing by Leo Audio Productions. Design and marketing by GPS: Garrard Powell Solutions. Hosted on Acast. See acast.com/privacy for more information.

In Episode 57, we review Luthier published by Paverson Games and designed by Dave Beck and Abe Burson. But, first, we chat about what is bringing us joy: Becky's new year's resolution update, Zenith, Angela's new year's resolution update (including Unmatched Adventures: Teenage Mutant Ninja Turtles), and Root. Luthier takes place in the height of classical music in Western Europe with 1-4 families of artisans eager to pursue prestige by satisfying patron's requests for instruments, performances, and instrument repairs. By keeping your patrons happy through building instruments, performing different styles of music, and repairing instruments, they reward you with gifts, but if you take too long to complete their requests, they will abandon you and speak poorly of your family, decreasing your prestige. The player who gains the most prestige points wins the game.The homies are captivated by this game, but there's still something about it that may see it out of Gillean's collection sooner than later. Get to know us @ https://lnk.bio/BoardGameHomies

Take the 2026 AI Engineering Survey and get >$2k in credits and AIE WF tickets!On the product side, everyone is getting Computer - Perplexity, Manus, Cursor, and so on. Meanwhile on the research side, agentic evals like TerminalBench and GDPVal are also assuming computer (Harbor). On both ends, the consolidating LLM OS stack has become a standard toolkit, and Daytona is one of a small set of AI Infra companies that are booming because of it.“The end of localhost” has been Ivan Burazin's obsession for more than a decade.Something that is all too familiar…Long before agents became the default way people talked about software development, Ivan was already chasing the idea that development should not depend on a fragile local machine. CodeAnywhere, one of the first browser-based IDEs, was an early attempt at that future: move the development environment into the cloud, make setup reproducible, and free developers from the endless “works on my machine” tax.The thesis was directionally right, but the market wasn't ready yet.However, agents changed that. They do not care about a laptop, desk setup, or favorite editor. They need a computer they can access through an API: something stateful enough to keep working, fast enough to spin up instantly, flexible enough to resize, isolated enough to be safe, and composable enough to run the messy real-world workflows that real software engineering actually requires.Daytona isn't just selling “sandboxes” in the narrow code-execution sense. It is the latest version of Ivan's original localhost thesis.In this episode, Daytona's CEO joins swyx to explain why AI agents need more than code execution boxes: they need composable computers, stateful sandboxes, instant startup, dynamic resources, and infrastructure that can survive workloads going from zero to 100,000 CPUs.We go deep on the new agent compute market: Daytona's hard pivot from human dev environments to AI sandboxes, the New Year's Eve MVP that customers begged for, why Daytona runs on bare metal with its own scheduler, how one customer runs almost 850,000 sandboxes a day, and why RL/eval workloads went from 0% to roughly 50% of usage in just months. Ivan also explains why agents need Windows and macOS machines, why CLI may matter more than MCP, why Kubernetes is painful for this workload, and why the future AI cloud may look more like Stripe than AWS.We discuss:* How Daytona grew out of CodeAnywhere, Shift, and the “end of localhost” thesis* Why Daytona pivoted from human dev environments to AI sandboxes* Why agents need composable computers instead of disposable code execution boxes* The New Year's Eve MVP that customers chased API keys for* Why Daytona chose bare metal, stateful snapshots, and its own scheduler* How Daytona spins up one sandbox in ~60ms and 50,000 sandboxes in ~75 seconds* Why Daytona's biggest customer runs ~850,000 sandboxes a day* How RL/eval workloads create zero-to-100,000 CPU spikes* Why RL workloads went from 0% to roughly 50% of Daytona usage* Why customers compare Daytona against EKS/GKS and say they're “never going back”* Why every AI agent may need a computer, including Windows and macOS environments* The Apple licensing constraints that make macOS sandboxes hard* Why CLI gives agents more power than MCP* How open source helps agents integrate Daytona* Why agent-generated PRs may break today's CI/CD assumptions* Why AI SaaS companies reselling tokens may face a cold shower* Why the AI cloud may look more like Stripe than AWSIvan Burazin* LinkedIn: https://www.linkedin.com/in/ivanburazin* X: https://x.com/ivanburazinDaytona* Website: https://www.daytona.io* X: https://x.com/daytonaioTimestamps* 00:00:00 Hook* 00:01:12 Introduction* 00:03:15 CodeAnywhere, Shift, and the end of localhost* 00:05:58 What Daytona is: composable computers for AI agents* 00:08:07 The pivot from dev environments to AI sandboxes* 00:10:17 The New Year's Eve MVP and customers begging for API keys* 00:12:56 Bare metal, stateful sandboxes, and Daytona's scheduler* 00:17:28 60ms startup, 50,000 sandboxes, and 850K daily runs* 00:21:53 Spiky RL/eval workloads and the new agent infra problem* 00:28:12 RL workloads, Kubernetes pain, and dynamic resizing* 00:33:31 Why every AI agent needs a computer* 00:38:48 macOS sandboxes and Apple's licensing problem* 00:44:28 Why CLI may matter more than MCP* 00:48:11 Open source, GitHub stars, and agent integration* 00:53:11 Git, CI/CD, and agent collaboration bottlenecks* 00:58:15 Founder life and building a 25-person infra company* 01:02:44 AI SaaS, token resale, and API-first business models* 01:06:10 GPU sandboxes, data centers, and compute growth* 01:09:48 Why the AI cloud may look more like Stripe than AWS* 01:11:26 Closing thoughtsTranscriptIntroduction: Daytona, CodeAnywhere, and the End of LocalhostSwyx [00:00:02]: Okay, we're in the studio with Ivan Burazin, CEO of Daytona. Welcome.Ivan [00:00:07]: Thanks for having me, man.Swyx [00:00:08]: Ivan, you and I go back.Ivan [00:00:10]: Way back.Swyx [00:00:11]: How I don't even know how, you found, did you reach out or, for Shift.Ivan [00:00:17]: I reached out to you. The reason was you - we were just - we were thinking about I was one of the co-founders of CodeAnywhere, the first browser-based IDE, and so we were thinking a long time of, localhost should die. And you had this article.Swyx [00:00:29]: End of localhost.Ivan [00:00:30]: Then I reached out to you because of that, and then we talked, and I was actually at a different job and learning about I was the head of, developer experience, and you were quite well-versed in that, and I actually reached out to you, among other people, how do we go about that? What are the key things and whatnot at this point in time? And you were nice enough to take the call, and I remember I was late on your call with you.Swyx [00:00:51]: I don't remember.Ivan [00:00:52]: I remember because I was with my then I'm thinking of a girlfriend or wife at that point in time, I'm not sure. It's the same person, so that's great, and I was late ‘cause we were, in, Italy on, vacation, and then I was late for something. I felt so bad, and you were so nice to be, good about.Swyx [00:01:10]: The reason I'm nice is because I'm also late to other people, so it's like, who's, who's without sin here, yeah, so I have to, for those who don't know, InfoBip Shift, there's this whole thing that, you did in the past, and, and that was basically one of the inspirations for me starting AI Engineer, which is like, I have to thank you for giving me that push to be like, “Oh, you can, you can build and sell conferences?”Ivan [00:01:34]: I remember you asked you asked me at the beginning to give me advisory shares, and I was so focused on what we were doing, I said no, and I should've took the advisory shares. So I'm sorry, dude. But anyway.Swyx [00:01:43]: We're not, we're not venture backed.Ivan [00:01:44]: No, it doesn't matter.Swyx [00:01:45]: It's Yeah, anyway, so I think what's impressive about you is that CodeAnywhere is the thing that you've been trying to build, and, you kind of put it on hold and then came back after InfoBip. Just give us the story, do you - the story and the origin story, going into Daytona.From CodeAnywhere and Shift to DaytonaIvan [00:02:05]: Sure. Like, really way back, me and my co-founder have been together. I say this, I've said this multiple times, it's like we were married and divorced and married. Some people actually ask me is my co-founder my partner. they thought it literally. It's not literally, but we have done multiple companies together, and to your point, we had this shift where we went from the CodeAnywhere to the conference called Shift, and then back to, Daytona. We originally started stacking servers, doing like virtualization in the early 2000s and, routers and doing basically all these things, at a foundational level, and that was a services company which we sold to focus on what my co-founder actually invented, which was the very first browser-based IDE, right, I say the first. Before us was actually Heroku. They did it for a very short time until they became Heroku. But outside of them, we were the only one, and it was called.Swyx [00:02:55]: There was Cloud9.Ivan [00:02:57]: Cloud9 came out slightly after us. There was Replit, which came out when we stopped doing it, Replit came out, and they have been successful since then, which is great. There was Nitrous.io. There was quite a few that existed at the time, but it was like too early. But the interesting part is that we, at that point in time, because there was no VS Code, there was no Kubernetes, and Docker had just started when we Or I'm not sure if it was even public at that point in time. And so we had to build everything to the whole stack ourselves and that was the key learning that we brought into and that we've been using in Daytona today. So it was super early. There's about 3 million people used CodeAnywhere. It was slightly, it was angel-backed more than venture-backed. We ended up paying everyone back because it didn't have that sort of scale. But, three years ago, we started something similar with Daytona, which is not what we are today, but it was automating dev environments for human engineers, the basically the underlying stack of CodeAnywhere. And then we did a hard pivot last January to sandboxes. And so here we are.Swyx [00:04:01]: Historic pivot, yeah, and, it's one of those things where, I had independently invested in CodeAnywhere, but also in E2B, and then both of you pivoted into the same thing, and I'm like, “F**k.”Ivan [00:04:12]: You invested, you invested in Daytona. You invested in Daytona. But you were the first If we had not got your check, we wouldn't have done it.Swyx [00:04:18]: No way.Ivan [00:04:19]: No, it was like, “We have to get him on board first,” and you were that kicker that we, that got us off the ground.Swyx [00:04:23]: No, because you were putting me on your pitch deck, man. I was like, “Man, this is like a good trip if I don't invest.”Ivan [00:04:29]: That's because it was your quote. It's like we.Swyx [00:04:30]: Yeah. It's the end of localhost.Ivan [00:04:31]: Did a bunch of research about end of localhost and who was interested in that,.Swyx [00:04:34]: No, that's like, I put, I wrote that blog post, and every single company in that field reached out to me, and then every VC who was receiving those pitches then also had to call me and, talk it, talk through it with me.Ivan [00:04:47]: It's finally happening though.Swyx [00:04:48]: It was really super interesting.Ivan [00:04:48]: It's finally happening.Swyx [00:04:49]: It's finally happening.Ivan [00:04:49]: Yeah, it's finally.Swyx [00:04:49]: It's finally happening, with maybe sort of non-human users. Yeah, so what is Daytona today? Let's get like a quick description. I'm wearing the shirt.What Daytona Is Today: Composable Computers for AI AgentsIvan [00:04:58]: You're wearing the shirt. Yes,.Swyx [00:04:59]: It says, I think your branding is very good. Like, it's very consistent. It runs AI code. Like, it cannot be simpler.Ivan [00:05:05]: Exactly, but we're gonna probably have to change that.Swyx [00:05:07]: Oh, s**t.Ivan [00:05:07]: It's also a subset of what we do. Unfortunately, we really love this, Run AI Code is super simple. People interpret it different ways. I think we've given out 5,000, 6,000 of these shirts. People wear them with pride because it doesn't really market about us.Swyx [00:05:21]: Yeah, Daytona's on the back.Ivan [00:05:22]: It markets the back. It markets to the person itself, so I think we did a really good job on that one. But it is also a subset of what we do, because people, when they think about Run AI Code, they just think about these small, let's call it isolates, code execution boxes that, you send some code, you get an output. Whereas what Daytona is today is essentially composable computers for AI agents. It is, the market calls them sandboxes which can be misleading.Swyx [00:05:44]: All these things. All these things on.Ivan [00:05:45]: Yeah, exactly, ‘cause it can be misleading ‘cause people usually think about sandboxes as a demo or a test environment versus a production-grade environment. But what Daytona does, if you think of the laptop that you have in front of you or the computer that's over there, or, my wife is an architect, so she has like a Windows with a 3D graphics card inside to do 3D rendering. Like, as humans, we have different computers or different compositions of computers. And our belief is strongly that agents today and going forward will need all these different compositions of computers to do different types of tasks. And so we offer that basically through an API.Swyx [00:06:19]: Yeah, to give people - I'm trying to sort of front-load all the aha moments or the wow moments so that people can, stay engaged and click like and subscribe. the market is exploding, right? Like, you have been reporting 74% month-on-month growth, and it also, it's just been growing for a while. Like, it's been going like this. And every single - It's not just you guys. It's every single.Ivan [00:06:41]: Everyone, yeah.Swyx [00:06:42]: Sort of, compute provider. I don't know if you agree with me saying compute provider or not.Ivan [00:06:48]: It's fine.Swyx [00:06:48]: Yeah. So like organically PLG-driven growth, but also enterprise is doing super well, I think I wanna rewind to January of last year when you did the pivot. Like, so you obviously called this market early, and you were positioned for it, and you are now one of the market leaders. But what was the insight that made you do the pivot?The Pivot: From Human Dev Environments to Agent SandboxesIvan [00:07:06]: The insight that made us do this pivot is the quarter before that, so end of 2024, when we had - Basically, we did a demo with - I don't I think we discussed this as well, Devin was not public. You actually gave me access to Devin at that time. So Devin.Swyx [00:07:25]: I did?Ivan [00:07:26]: Yeah, you gave me access.Swyx [00:07:26]: I don't think I was supposed.Ivan [00:07:27]: Yeah, exactly.Swyx [00:07:28]: Yeah, I.Ivan [00:07:28]: So it doesn't matter. You.Swyx [00:07:29]: Yeah. I gave like three friends access.Ivan [00:07:31]: Yeah, or it was a call and you showed it to me. It doesn't matter. but OpenDevin was available, which is now called OpenHands. And so we're like, “Oh, this seems to be a thing. This is not public. Let's take our for human automation of dev environments and take, OpenDevin and launch that as a SaaS.” And we did that. Not very many people signed up and used it, but a lot of people reached out that were building agents, and they were like, “Hey, my agent needs a compute sandbox runtime,” whatever you wanna call it. I forgot what it was called at that point. And then we were like, “Oh, amazing. This is a new market. Here is our infrastructure. Here's our product, and go.” And what we found really fast, soon, was that people did not like what we had built. It didn't work. And I remember talking to people at the beginning when we're doing this, the sandbox we're building for agents. People were like, “Oh, why is it different? It's the same thing. We have like EC2, we have VMs, we have all these things.” But we saw that everyone we gave it to, it was like 20, 30 people, they all said, “No.” Like, “This is not what we need. This sort of breaks.” And basically, me and my co-founder not knowing a lot about - ‘cause we're infra people. We're not AI people. So I basically took it upon myself to like watch every single podcast that exists, including all of, all of these and all that, and sort of get up to date, read all the blogs, like get, understand what's going on.Swyx [00:08:45]: Do you wanna shout out who else was useful, just in case people are also looking.Ivan [00:08:49]: Generally we -, I looked at There's a few of podcast, different segments and different types. So there's you guys, No Priors, Bill Gurley's was great while.Swyx [00:09:04]: VG2, yeah.Ivan [00:09:05]: Yeah, while it was around. So there's a few. 20VC is interesting from a different dynamic, and some are different dynamic. But there was, also Red Points.Swyx [00:09:14]: We're not really about the compute market.Ivan [00:09:15]: It was also already - Sorry?Swyx [00:09:16]: You're, you want - You're looking at the agent infra market.Ivan [00:09:19]: I was looking at the agent market and the AI market in general and sort of understanding who are the players, what the perception, and how that goes. And like obviously you complement this with like going to conferences, going to events, going to meetups, reading white papers, like doing all the things that you have to do to understand what's happening. And so when we figured, when we sort of had an idea of what we had to build, literally over the New Year's Eve, literally on New Year's Eve, I half vibe coded the first MVP, first minimal viable product of what Daytona is today. And I went to sleep at like 3:00 AM or something like that. I was doing - I just put my like baby daughter and wife to sleep and, Happy New Year's, and go back to just, doing this. And I sent it to my co-founder, my CTO, and he saw it in the morning. He's like, “This is absolute garbage.” “Do not show this to anybody at all, but the idea is good.” And so he took two weeks, and he rebuilt it.Swyx [00:10:09]: Did it like look like that? Listen, I - It was rough idea.Ivan [00:10:12]: Oh, not even, not even close. Like it was it was way worse. But it was like a very - It was a simplistic view of what it should be. Like, it worked, but it was not ideal. And so he went, we went down the whole, which is his job as CTO, to go, and he came back with this version. We then called all the people that had said like, “This is garbage,” a quarter ago. And we set up these calls, and we gave it to - We just demoed it to everyone. And all the calls went long, every single one. They were 15-minute calls, and they all went to like 25, 30 minutes or whatnot. And everyone said, “We need, we want access.” There was no login, just an API key, ‘cause it was just a beta or an alpha. And they said, “Oh, we want access.” And we're like, “Sure, yeah. Okay, thank you very much.” But after like the next day, if we'd not send it, every single one, like every call that we did, everyone came back, “Where is my API key?” Like everyone wanted it. We're like, “S**t.” Like this is it. Like I've never felt So one, the understanding to your point was like most people thought it was the same infrastructure for humans and agents. We understood a quarter ago it's not. We just didn't know what was the right primitive. And then when we came, and we can talk about what that is, and we gave it to these people, I've never seen, I've never experienced - I've done multiple companies in my life. I've never experienced this, that people literally call you if you do not give them access. Like they want access right now. And so it's like, okay, they don't want this. the thing that they want doesn't seem to exist, or they have not found it, and they really want what we want. And then when we understood that we're onto something, and then when you think about the size of the market, like the market for human engineers and enterprise is a very large market, so think GitLab or whatnot. But the market for every single agent that will exist ever in the future is just like, what is that market? How big is that? And we're like, “We are all in on this.” And so that is where we made sort of the cut between the old product and the new one.Bare Metal, Stateful Sandboxes, and the Lambda + EC2 ModelSwyx [00:12:02]: Yeah. But it wasn't composable at the time?Ivan [00:12:05]: It was very - It was basically just a Linux box that you could change, that you could define number of CPUs, disk, and RAM. Like that is what you could do, but you couldn't have multiple operating systems, you couldn't resize it on the fly, you couldn't add a GPU, you couldn't do like all the things. It was just the, just the first sort of variation of that, yeah.Swyx [00:12:22]: Was it bare metal from the start?Ivan [00:12:24]: It was bare metal from the start. And so the interesting thing that we thought about right away, so our.Swyx [00:12:29]: Which, give people the background, what is the normal path?Ivan [00:12:32]: Yeah, so, basically most providers run this on top of VMs. And also.Swyx [00:12:37]: Firecracker.Ivan [00:12:38]: Yeah, they run on Firecracker and VM. And so we also fire - We can get - We have multiple isolation layers and we can do that. But the common way to do it is that they, one, that the state of the machine, or the hard disk is not part of the sandbox itself. And the other thing is they're not meant to last forever. So most of them are preemptible, like they can There's a time that they can live. And so our thought was when we were going into this is, agents will be like humans in the sense of you don't want your laptop to be shut down until you're done with work. Like, and you want to close the lid and open the lid, it's the same state. So you - Agents would want that, like the pause and come back. They want those two things. But also agents really want speed, right? Can they get it? So when we thought about it's like we need something insanely fast, how to make it fast, how to make it long-running, and stateful. And so those two things, it's like combining a Lambda and an EC2, right? Those two things together. And so we didn't have an idea how others did it, ‘cause we didn't know too that there was a market around this. It was more like, okay, this is what we need, what they need. And we looked at Kubernetes, it wasn't wasn't good enough for that. We looked at Nomad, it didn't enable that. And so our history in rewriting our own scheduler at CodeAnywhere is basically what my CTO came up with. Like, he's like, “Oh, the learnings from there,” and he brought it. And the funny thing is, our third co-founder, when he saw it, he's like, “Dude, what is this? This is like 2008.” Like, we went back in time, and he's like, “Exactly.” And so the reason why Daytona is like super fast, and you see this on benchmarks, is we essentially, we run on bare metal. We have our own scheduler, we use the underlying, disk, CPU, and RAM of the underlying machine, which means your IOPS are insanely fast because there's no, there's no network between an EBS or something like that. But also the snapshot, the point in time, the templates, are also preloaded on the bare metal machines. So when you fire off a sandbox from a template or a snapshot, you're essentially directed to the bare metal machine where that snapshot is based on that NVMe drive, and then it literally just turns on that machine, and it's local. There's no network latency, anything on there. And so that is sort of the specificities that we, when we're thinking from first principles, what a computer would look like for an agent, that is what we came up with, and that's what we created.Benchmarks, 60ms Startup, and 50,000 SandboxesSwyx [00:15:02]: Yeah. I should maybe, I don't know if you endorse this, but there's someone that does compute SDK, you guys do very well on there, with like the TTI, right? I. is this a, is this a is this a relevant benchmark for you guys? I don't know.Ivan [00:15:16]: I don't know, and it changes every day. So today RKL is.Swyx [00:15:18]: I don't know what RKL is. Never heard of it.Ivan [00:15:20]: Yeah. RK, yeah, so it is there.Swyx [00:15:22]: You are, at least a third of the next tier of performance, and then, there's a lot of other better-known names that are very slow to start.Ivan [00:15:31]: Yeah. We've been the number one by far for a long time, and now there's different, there's different definitions also of sandboxes, different isolation patterns, different other things. So RKL runs it literally on the S3, the data, so it's very different, and they spin up a sandbox, spin up a container for that, so it's a different type of thing. So the definition of a sandbox is something that we can all, we all need to get along with. But yeah, we're insanely fast on getting these things, up and running. And so you can see even there that it's a zero point 0.10 to 0.11, so.Swyx [00:16:03]: Close enough. Yeah. what else do you need, right?Ivan [00:16:05]: Yeah. So the benchmarks itself, so, in this, in I don't think the benchmarks equate to market ownership or revenue or anything like that. and I've seen this with multiple benchmarks, not just in sandboxes, but in general benchmarks around.Swyx [00:16:20]: It's table stakes. It's just like.Ivan [00:16:21]: Exactly. But it doesn't hurt.Swyx [00:16:22]: Just roughly check.Ivan [00:16:22]: Like you definitely have to be up there and you have to be competing so that people know that, oh, this is definitely one of the top. Because this is only one dimension of what customers look for. There's other things like how many can you spin up consecutively? There's a feature set, there's support, there's like all different things that people look at, but you definitely have to be there, on the benchmarks.Swyx [00:16:40]: How many people do people spin up consecutively?Ivan [00:16:43]: So we have.Swyx [00:16:43]: Or concurrently, is the Concurrency, right?Ivan [00:16:45]: There's three metrics that we look at. And so one is like time to spin up one, and so our time to spin up one is 60 milliseconds with network latency. So request, spin up, reply, 60, the whole thing, 60 milliseconds. That is one. But if you wanna spin up 50,000 at once, we are now at about 75 seconds. So it takes about 75 seconds to spin up concurrently 50,000. Some others, there's public data around this, like take 2,000 seconds, which is 30 minutes. Like there's different variations of that. And then there is the so it is speed of one, speed of like multiple, and then how many can you consistently have up and running. And so we basically have right now no limit to how much we can add because we basically own our own metal. But the biggest customer of ours does like about 850,000 every single day is sort of where they're, where they're just shy of a million every single day that they're running, we do have a request for half a million concurrent, which is literally half a million CPUs somewhere running. So that's an interesting.Swyx [00:17:44]: They pay by like vCPU seconds.Ivan [00:17:47]: By seconds, yeah.Swyx [00:17:47]: Or whatever. Yeah. Okay, and so and then, and the other thing is, the sleeping and the resuming, ‘cause it's all the stateful resumption of all these things, how, what kind of workload are people putting through this, right? Like how is it Do we measure by gigabytes in memory, gigabytes in storage? I don't In like network attached storage. I, what are the costly ones of, out of all these features?Workload Economics: CPU, RAM, Network, and StorageIvan [00:18:15]: The most expensive thing are CPU.Swyx [00:18:18]: Okay. Yeah, of course.Ivan [00:18:18]: The second one, yeah Then it's RAM, then it's disk. We actually don't charge.Swyx [00:18:22]: Which is snapshotting, right?Ivan [00:18:23]: No, it's actually the, snapshotting's part of it, but basically the size of your hard disk, of your machine. So do you have 10 gigabytes, do you have 20, do you have 50, do you have whatever? And then the transference of that. Right now, currently we don't charge for, network at all at Polychron.Swyx [00:18:37]: Oh, you gotta, yeah, you gotta fix.Ivan [00:18:38]: Yeah. It is very much a it's a larger and larger part of our bill, so we're working around, that part there. Obviously, that is the least, expensive, so the hard disk is the least expensive, so it's basically CPU, RAM, for us network, ‘cause we don't charge the customer, and then hard disk, is how it's split up. But there's also different types of workloads, so we basically split it up into two types of workloads in Daytona. One is what we call background agents or long-running agents. and the other is, basically RLs and evals, which I put sort of together. And so they have very different patterns of usage, and if you look at the usage of a background And I'll just name names of companies, not specifically.Background Agents vs. RL/Evals: Two Usage ShapesSwyx [00:19:21]: Yeah, open, all hands.Ivan [00:19:23]: Yeah. So like a background agent's a Cognition, a Lovable, a like all these things are Harvey. These are all long-running, background agents. And so if you look at their usage patterns, their usage patterns are similar to human, which is like follow the sun. Basically, the usage patterns of that is like noon is probably the highest, and the midnight is the lowest, and then weekends are lower. weekday is higher.Swyx [00:19:42]: Yeah, that's a fun question. How global is it? Is it very US-centric or?Ivan [00:19:46]: The US is a large part, but we have currently, we have Asia, Europe, and the US regions.Swyx [00:19:52]: So it's quite global.Ivan [00:19:53]: Yeah, it's quite global. We have it all over. It's interesting that our I talked to you a bit about this. Our number one city by user.Swyx [00:20:01]: Hmm.Ivan [00:20:02]: Is Singapore.Swyx [00:20:04]: Oh, wow. Amazing.Ivan [00:20:05]: Which is an interesting one, right? Not by revenue, just by just like by individual head count.Swyx [00:20:09]: Really?Ivan [00:20:09]: Just like an interesting thing.Swyx [00:20:10]: Singapore is, Singapore is weirdly high in the adoption charts of AI for the population. It's like an, seven, eight million population. And it's like keeps showing up.Ivan [00:20:20]: No, it's quite interesting. We were quite shocked, and I was like, “Oh, this is interesting.” And also one that's up there.Swyx [00:20:24]: There's a reason I'm doing AI using Singapore. it's because I'm from there.Ivan [00:20:27]: We're there. We're gonna, we're gonna be there as well. and it's interesting that Japan is in the top or like Tokyo's in the top, which is in all the tech cycles it has never been. It has never been, so it's quite interesting that they're.Swyx [00:20:39]: I think the Japanese just love AI. Yeah. It's that, and then it's Brazil. That's it.Ivan [00:20:44]: Brazil has always been in.Swyx [00:20:45]: I think.Ivan [00:20:46]: Even when I look, if you look at like GitHub's data and ask historically with CodeAnywhere, it was always like US, Western Europe, and then you'd have like India, Brazil, China, like that would be there. But like Singapore was not in, specifically Japan was never in sort of that top, that top.Swyx [00:21:01]: Yeah. Weird pockets.Ivan [00:21:01]: Weird. Yeah, so it's very global.Swyx [00:21:02]: Okay, so actually that, but that's helps you to distribute your load through, all time?Ivan [00:21:08]: The interesting thing is like we have those kind of loads, but if you look at the researcher loads, they're quite different. So what they are is like if you give them concurrency of 10,000 or 50,000 or 100,000 CPUs at ARMb, when they fire off a run, it's just 100%. And then it just runs, and then it stops. So it's very, the usage pattern is squares basically, right? And it's also not follow the sun, because people will fire it off at midnight before they go to sleep but then wake up and so it's very unpredictable, so you don't know where that is. So the shapes of the usage are quite different than we have had before. And also what's interesting is when it's sort of a follow the sun, even if you have a high growth company, you can sort of predict your usage patterns and have enough capacity for that, because it's sort of, it grows in a, in a way you can project. When you have companies doing sort of like evals and RL, they're super spiky. So they're gonna come in, it's like, “We're gonna use nothing, then can we have 100,000?” Right? And then go back down. And then 100,000, go back down. So it's very different, right? And.Swyx [00:22:09]: Do you want to lock them into commits so.Ivan [00:22:11]: Yeah, we do.Swyx [00:22:12]: Yeah, okay.Ivan [00:22:12]: We so we have to lock them into some sort of commits to have that capacity, because we have to have, basically we have to have the capacity for peak. Right? And so right now, Daytona's mean utilization is 15%, 1-5.Swyx [00:22:25]: Oh my God.Ivan [00:22:26]: So it's very low.Swyx [00:22:27]: Because it's very spiky.Ivan [00:22:27]: It's very spiky, but we get up to 90%. so we have these things. And so what we're, what we're looking at right now as a company is similar to Cloudflare where you can like geo move things around, but that works really well for basically the background agent where it's follow the sun. But this, it's not. Like it's a very different shape. Obviously with scale you figure these things out, but that's an interesting new problem that we have, as a compute provider in the agent space. And when we were doing the conference recently, and so we talked to like Nikita from Neon and.Swyx [00:22:57]: I should bring it up.Ivan [00:22:58]: Parag from Parallel and whatnot, everyone has the same problem. Whereas the usage is super spiky, and this is something that has not happened before, that you have these types of like it was always, it the amplitudes were not this high, right? So it's quite interesting use case and problem solve.Compute Conference and Spiky Agent InfrastructureSwyx [00:23:12]: Yeah, I don't know if we're gonna bring this up again, but let's just talk about the conference, you had like 1,000 something people at the Warriors game, at the Sorry, where is it? What's.Ivan [00:23:22]: Chase Center.Swyx [00:23:23]: Chase Center.Ivan [00:23:23]: Chase Center.Swyx [00:23:24]: I went. It was, it was very impressive. Obviously, you can, how to throw a conference, what did you learn? you put, you pulled together all these impressive names.Ivan [00:23:33]: What I.Swyx [00:23:34]: What were you looking for?Ivan [00:23:35]: My thesis behind the Compute Conference was let's bring together people that are building infrastructure for AI agents. Because when I think of what we're building, it is the agent is the primary user, what are the ergonomics and usage patterns of agents, and so we can do that. And what I found, this was a theory, it wasn't proven, is that we all have these problems, as I touched onto. And I was, as I was talking on stage, it was like we all have the same underlying infra problems, which is this spiky workloads, unpredictable workloads that we've never had before, in human, compute or human infrastructure. And it's, again, it's the same when I was talking to Parag or when I was talking.Swyx [00:24:20]: Lynn. Nikita.Ivan [00:24:21]: Lynn, Nikita. Lynn especially, I was talking to her the other day as well. Like the It is a very interesting type of problem to solve because I can touch on Cloudflare because there's a lot of like talk about that recently as to how they solve that, which is they have a bunch of geos, and basically, as users work in different places, and depending on your tier, they can move you around the geos. And so that how, that's how they get the higher utilization. But you can sort of predict these, and it's If it's something in You'll rarely get a spike that is 10 orders of magnitude. Like you'll get a like let's say one of your customers has some like an exponential curve. What is that to I'm using Cloudflare as an example. 10%, 20%, whatever it is. I don't, I don't have this data, I'm just assessing. It's surely not 10x, right? It's surely not something there. And so how do you go out and solve this problem? And we're all solving this in different ways. So we have.Swyx [00:25:11]: She also has the same thing.Ivan [00:25:12]: Yeah, I know specifically that like Neon had that issue as well. Like how are we solving these spiky loads and things like that ‘cause we talked about it. And so the interesting thing for me to actually internalize was, yes, everyone that's building for agents first is going through this, and we're all solving similar problems, which is quite.Swyx [00:25:28]: Let me let me double-click on this. Okay. So for example, Neon, I happen to know that they're very sort of S3 oriented, right? so they're just like fully bet on S3. And you get to benefit from S3's distribution and infrastructure. So I would imagine that Neon doesn't have to care, whereas Lynn maybe has to care a bit more because obviously she's doing GPU inference. And, for listeners, we did an episode with her, one and a half years ago. And you have to care. But like, right?Ivan [00:25:54]: Parag cares for sure, and Nikita.Swyx [00:25:58]: And Parag is C of, Parallel.Ivan [00:25:59]: Parallel, yeah.Swyx [00:26:00]: Former CTO of Twitter.Ivan [00:26:01]: Twitter, yeah.Swyx [00:26:02]: They are the search.Ivan [00:26:03]: Yeah, they're search, yeah.Swyx [00:26:03]: I You and I know but the listeners don't know.Ivan [00:26:08]: Yeah, we can put it down in the screen, and so ‘cause we, when we were talking.Swyx [00:26:11]: I'll put it up on the, on the screen.Ivan [00:26:12]: Yeah, right.Swyx [00:26:12]: People can look it up if they need.Ivan [00:26:14]: Look it up. And, yes, but they still have CPU and RAM, allocation that you have to have up and running. And so CPU and RAM, you have to allocate that and have that ready. And so there's basically two ways to do it. One is you either over-provision and you can handle the bursts, or two, you basically have, I don't know if this is a term, just-in-time compute, which is like as your load becomes, as your usage comes in, you can fire off requests for VMs or bare metals at other cloud providers and then get them up and running.Swyx [00:26:43]: This is if you go above 100%, right?Ivan [00:26:45]: Yeah, this is.Swyx [00:26:46]: Like your overflow.Ivan [00:26:46]: If your overflow, like spillage or whatever you do.Swyx [00:26:48]: You probably lose money on it, but it doesn't matter, right?Ivan [00:26:50]: It, not Well, you might, you might not That is a more cost-effective way to do it but it's a slower way to do it. Because basically what you have to do is you have to like queue your requests, spin up these just-in-time compute, get it all ready, provision it, and then get your workload there. And so if the time isn't important that much, that's fine, and you can do that. But if your customer, and especially for, let's say, the RL training runs, the reason why a lot of people come to us is because GPUs are more expensive than CPUs, right? So you want your GPU running at, what, 100% the entire time. And so when you're running runs on CPUs, when the when the CPU cycle is like down and spinning up the next one, you want that to be instantaneous so that your GPU doesn't go down, right? And if you then have to like go out and provision machines, you're essentially telling the GPU that it has to wait, and that's incurring our cost. So there's things that you have to try to solve for there.RL Workloads, Declarative Images, and Kubernetes ReplacementSwyx [00:27:43]: Yeah, let's talk about the different workload, right? You said that, what was it? A few months ago, you had zero RL workload and now it's 50%.Ivan [00:27:52]: It will be this one, 50%, yeah.Swyx [00:27:54]: Let's talk about how different it is, right? Like I imagine, for example, a lot less dynamic code generation of like arbitrary code. Like here, it's probably all the same code. You're just doing parallel runs or something, I don't know.Ivan [00:28:05]: Yeah. So you'll have multiple Depends on the like for each run, you'll have a snapshot. And they, for the most part, they actually do use our declarative image builder, which is like, “Oh, we, the agent wants these dependencies, these env vars.”Swyx [00:28:17]: These ones, yeah.Ivan [00:28:18]: Yeah, the declarative image builder, it.Swyx [00:28:20]: Which is a very modal like thing that they.Ivan [00:28:22]: Yeah. And so we build it on the fly and then we propagate that snapshot, and you can spin up as many sandboxes as you want against that snapshot. And then if you have to do changes, the model can, or like it could be also be automated. It's like, “Oh, now for the next run, we need to install these things or remove these things or whatever to get, a task done,” and then it goes off and runs that. So yes, that is something that it seems that they prefer. The number one reason I found, or should I say, let's take a step back. What we are competing against in that environment is essentially managed Kubernetes. So EKS, GKE, whatever. That is what the vast majority run on. And anyone that has tried Daytona versus GKE, EKS is like, “I'm never going back.” That has always been. There's a few reasons. One is the ergonomics. So if you have, if you're using Kubernetes to spin that up, you have to essentially manage the interface interactions with that. Daytona, although as a compute provider, it's more akin to a Twilio and Stripe from a consumption perspective than it is an AWS. Like you have an API, an SDK, it's quite like easy and seamless to get these things up and running, that's one. The other is the speed to which we spin up, which we mentioned earlier, which is much faster, and the scale to which we can go to. We haven't got into features, but an interesting feature is that it's very hard to OOM, or out of memory, our sandboxes, because we can dynamically on the fly.Swyx [00:29:48]: Resize.Ivan [00:29:49]: Resize, which is like impossible on almost any other thing. There are some technologies that enable you to do that, but it's like a very hard thing. And so we actually saw this when, the Terminal Revenge team is, brought us actually. So thank you, Alex and the team, that brought us into this whole space.Swyx [00:30:05]: It's just very rare that, a framework would just say, “Guys, just use Daytona.”Ivan [00:30:11]: Yeah, I think it says it somewhere. Yeah.Swyx [00:30:13]: Yeah. I was like, “What is this?”Ivan [00:30:15]: There's all, there's multiple there, but they also mention a few other places. and so Daytona specifically-We have, the, just jumping on themes here We, I don't know where it says Data Center.Swyx [00:30:27]: I, there.Ivan [00:30:27]: Doesn't matter.Swyx [00:30:28]: There's a very strong recommendation, which is, very unusual. Which is, it's.Ivan [00:30:33]: We do not pay them for this, just.Swyx [00:30:34]: I know, yeah. They just like you.Ivan [00:30:35]: Yeah, they like us. yeah, and also a thing, so, Data Center has multiple isolation sets underneath. The customer doesn't have to know what they are. But basically we have Docker, which is a container, that's hardened with Sysbox. So it's Docker's, isolation that is a security equivalent to a VM, but it's still a container. And that is the default, and they, especially in these training workloads, really like that as an interface to be able to use just a basic Docker container, and we enable Docker and Docker. Which for these RL runs, if you need to do a Docker compose or Kubernetes, you can spin up a K3S inside of these things, which unlocks a huge amount of workloads that you can do that you cannot do on other providers. So just on that part is much more interesting. And so we went that, through that. We showed them that we could do that, and they enjoyed that quite a bit. They being the general venture people.Swyx [00:31:28]: Those people, yeah.Ivan [00:31:29]: And Harbor people.Swyx [00:31:29]: Harbor people, do are they, are they a company yet?Ivan [00:31:33]: As far, I do not know.Customer Pull, Slack Connect, and the Computer Use BetSwyx [00:31:35]: Okay. All right. Yeah. It's like super obvious that like, there's a lot of excitement and success around these things, okay, so yeah, tell us more, right? Like, this is an exploding workload, Harbor adopted you, which helped speed things along. But what are you learning as this new workload comes online?Ivan [00:31:53]: There's a couple things that we learned, which we chat about in the beginning. We, and this has led our story, as we mentioned, we like talked to a lot of customers along the way, and we add more features and more tool sets as we talk to customers. And it's interesting that And I think it's that the ecosystem is so small and/or the models get smarter, where when we see one user come with a request, we know it goes on a roadmap if like three to five customers come with the same request in that week. It's like very bizarre. It happens so many times, which is.Swyx [00:32:27]: Because they're all friends.Ivan [00:32:28]: Sorry?Swyx [00:32:28]: They all, they're all friends. They're all in the same group chat.Ivan [00:32:30]: Yeah, probably, yeah. ‘Cause and they're like, “Oh, can you do this?” And I'm like, “Okay, this is interesting. We'll put it on a feature request.” And then the next one's like, “Oh, can you do this?” “Okay.” It's all the same, right? It's always the same. And so what we try to do, and I personally try to do, I try to be on as many call, quote-unquote “sales calls” I can. I'm in every Slack channel. We literally have about 1,000 Slack Connect channels, something like that. It's an interesting, there's so many interesting things you find out when you have all the Slack channels. You can also see where people, transfer between companies. You see leave Slack channel, enter Slack channel. It's an interesting thing. Also, just I digress, I feel that Slack Connect is literally LinkedIn what it should be. You have a list.Swyx [00:33:08]: LinkedIn charges you to, use your own connections, but Slack doesn't, right? Slack is like, do it for free. It's more lock-in. It's great.Ivan [00:33:15]: Yeah. It's amazing. Yeah. It's one of the reasons.Swyx [00:33:17]: You're gonna pay Slack for life.Ivan [00:33:18]: Exactly. You're there for life. So that's interesting. And so one of the things, the newer things we were talking about earlier is we made a big bet and put a lot of investment on computer use. that is not seen publicly the light of day. We haven't GA'd that yet, but we have.Swyx [00:33:32]: Is there a thing I can pull up?Ivan [00:33:33]: There is computer use there. It's right up a bit.Swyx [00:33:36]: Oh, yeah. Okay.Ivan [00:33:38]: What we have, what we talked about and what we've seen publicly is there's this theme now about, the human emulator where And Elon from XAI has talked about this publicly, and if you think about the models today, they're actually quite sophisticated and they can do a lot of work, but they still don't have access to all the tools. Like, I'm a strong believer that the most efficient way for an agent to work is essentially headless or through, terminal or whatnot. But if we, if we look at knowledge work in general, there's about 100 million knowledge workers in the US, about a billion in the world, and knowledge workers, and the salaries of them aggregate to 10 trillion in the US 50 trillion worldwide.Swyx [00:34:24]: Wow.Ivan [00:34:25]: Something like that. And if we look at, the five most important sectors of that, so like healthcare and government and financial services and whatnot, that's about 56% of that. So let's say it's about half of that. So in the US it's about 25 trillion, and most of them, most of that work is actually still locked into legacy apps inside of Windows, which is not going anywhere for a very long time. Like, people just won't invest in that. How much of it? our assumption is the following: if, in the RPA market, which is similar market, well, not the same 25% of, these white collar, workers', work is automated. If an agent is more sophisticated, can go through more runs, figure stuff out, let's say it's, 40%, right? And so if you take 40% of that, you get to essentially, $10 trillion a year.Swyx [00:35:17]: That's a TAM.Ivan [00:35:18]: That is a that is a TAM. So that's the TAM of the models, right? That's not our, essentially ours. But you get to that size, and to be able to do that, you essentially have to give agents these computers with the legacy. So computer use, either Mac or Windows or Linux. Linux we also obviously have and others have. But Windows specifically is something very new, and the only option right now is an EC2 with, Windows or on Azure. Both of them take anywhere from three to five minutes to spin up. We've created an actual sandbox, so it's a second instead of milliseconds, but you have, point in time snapshots, you have, forking, you have all the things that you have from a sandbox, but essentially enables you to hopefully unlock all this value. And so that's been our big push and bet, but we've sort of, kept our ear to the ground. What is sort of the next things in the market?RPA Returns: Why Agents Still Need ComputersSwyx [00:36:06]: Yeah, knowledge work, and building, and sort of RPA, the next wave of RPA. I got very excited about RPA kind of during COVID times. The UI path was IPO-ing. And it was, a very hot Isn't it, Eastern European?Ivan [00:36:20]: It is, Romanian.Swyx [00:36:21]: Romanian?Yeah, it might be the only Romanian, big unicorn okay, yeah. This I don't I don't, I don't have like a I think there's, I think there's a stage being set for the resurgence of RPA, ‘cause everyone understands that, yeah, no one wants to deal with these shitty apps and no one's gonna rewrite them. Like, you just have to do, a remote operation and programmatic operation of them.Ivan [00:36:45]: If you wanna unlock it, my own setup was basically the following. So I was doing a board deck recently, last month, whatever, and I'm like, “Okay, let's just, let's just do automated.” So, all our data's in, ClickHouse and PostHog and QuickBooks, where everyone else's is, and I'm basically, connected that all to, my Cloud code, like go off and go Cloud code whatever. Go off and, here's the integrations, go do that. It pulled out the first report, which was great. It connected to Brex and all these things, pulled it, which was great, and then I say, “Okay, now pull out this, and this,” and I kept getting, really well McKinsey-style design reports, but the data said partial data. all the missing data, partial data. Like, it can't access all the things, and I got so frustrated, and so I got, I got, my Mac Mini virtual sandbox with OpenClaw. I gave it its own account in our company, and then I went to all these services and created a read-only account, so literally like an intern in your company. And so I would say, “Now go and do this report,” and it would get the same, or like, “I can't via the MCP or the API or whatever. I can't get all the information.” I'm like, “Go log in.” And it will log into the website, then go in, export the data. It'll export the data and do the thing end to end. So even for things that have today APIs, not all of it is exposed, and I to get value, I get immense value right now, but it has to be a computer usage, unfortunately, and so I spend a bunch of tokens just on that, but I get the job done. And so if even a startup like ours, and using all the hottest tools, still needs a computer agent what hope does, Goldman have to have a headless, right?Swyx [00:38:22]: Yeah, what a - Why isn't Microsoft doing this?Ivan [00:38:27]: I'm pretty sure, Satya had a post yesterday.Swyx [00:38:29]: Oh, okay. I see.Ivan [00:38:29]: Which was like, “Every agent needs a computer.”Swyx [00:38:31]: I see, I see.Ivan [00:38:32]: So they have launched something recently.Swyx [00:38:34]: Yeah, they have Microsoft Power Automate, I'm sure, I'm sure, they're gonna have their version.macOS Sandboxes, Apple Constraints, and the Windows OpportunityIvan [00:38:39]: Version of that, yeah.Swyx [00:38:39]: You're gonna try to do yours, and it - I always know there's always demand for Mac, but I know it's, tricky to host, macOS sandboxes.Ivan [00:38:49]: We will have macOS sandboxes fairly soon. The problem with macOS, OS sandboxes is, I'm deep in this, I don't know how much interesting is.Swyx [00:38:55]: No, it's.Ivan [00:38:56]: MacOS has this problem.Swyx [00:38:57]: It's a licensing thing, right?Ivan [00:38:58]: Licensing thing. So one, you're allowed to run only two parallel VMs per machine, so that's one. Two, you can only license to a different user every 24 hours. So if you come in and theoretically, if I wanna charge you per second and I charge you one second, I have to have it idle for the rest of the day. I can't have anyone else doing that. So the pricing will be different in the sense that I will have to - we would have to charge for 24 hours, and that's not even, that's not even the most difficult thing. But the, thing above that is, from a security perspective, they enable you to do memory snapshot, pause, resume, but only on the same physical drive, physical machine. And so what you can do in, Windows world or Linux world is that I can move in the background, your snapshot from one to the other and manage load, right? Here, if you wanna do that, you essentially have to have your.Swyx [00:39:49]: Yeah, snapshots. Yeah.Ivan [00:39:50]: Your.Swyx [00:39:51]: It's like.Ivan [00:39:51]: Physical machine.Swyx [00:39:52]: You can't break it up.Ivan [00:39:53]: You can't, you can't move things around that, and all of that is, that part is, from a security standpoint, if it is written. Like, I understand the security aspect of that, but it disables you from doing these agentic, like really scalable agentic workloads.Swyx [00:40:08]: You need to do a vibe-coded, clean room implementation on macOS that you can then - That's like Clean OS or something. I don't know.Ivan [00:40:17]: So. We have.Swyx [00:40:18]: ‘cause like Linux was originally like a clean room rewrite of Unix.Ivan [00:40:21]: Okay. Yeah.Swyx [00:40:21]: Or something like that, right? Like same thing to macOS. Someone needs to do it.Ivan [00:40:25]: Someone will do that, and someone will have some long-running agents for a few days to figure this stuff out. But yeah. So definitely we - we're really close to offering something ‘cause people do want it, but the pricing will be different, and the feature set will be sort of stringent.Swyx [00:40:38]: Yeah, nobody's gonna use this. like, the labs, the labs will because they want to automate macOS.Ivan [00:40:42]: They have to do RL. They have to do RL again. But even if you The - So the point is with the RL part, if you, if you do RL on macOS, then the next iteration of the model comes out, it will be able to use these tools significantly. Then you actually need to run those, that somewhere. So you're gonna have to have that, later on. And from, if anyone at Apple is listening, I very much feel that they are shooting themselves in the foot of the scale of the revenue of compute or licensing they could get if they would just enable a concurrency model similar to what you can get on a Windows and a, and Linux.Swyx [00:41:17]: Yeah. Yeah. And I'm sure they've heard this before. They just don't care. Yeah, it's And maybe they will change their mind with the new CEO.Ivan [00:41:24]: Yeah. We'll see.Swyx [00:41:25]: We'll see.Ivan [00:41:25]: High hopes.Swyx [00:41:26]: High hopes.Ivan [00:41:26]: High hopes.Swyx [00:41:27]: Okay. But I, it's very clear the market opportunity is huge in Windows, and you can go for a long time on just Windows, but your customers are gonna want both. and I think, it is interesting to me that, this is the sort of God application of agents, right? Like, I don't It was - How big was OpenClaw for you guys? Like, was it, was there, a significant bump.OpenClaw, Agent Labs, and the B2B2C Sandbox MarketIvan [00:41:54]: Not for us because we.Swyx [00:41:54]: Because you already.Ivan [00:41:55]: We're kind of positioned differently. Whereas although it's completely PLG and we have individual developers that use it, most of the users that use Daytona are sort of a B2B2C. Sort of it's either B2B or B2B2C. So, in the researcher world, it's B2B, so you're selling to, labs and neo labs and things like that. But on the long-running agents, it's mostly, from a scale revenue perspective, it's mostly B2B2C, where you have a app layer agent that uses you at a big scale.Swyx [00:42:26]: Like a Manus. Yeah.Ivan [00:42:28]: Like a Manus Lovable type of thing.Swyx [00:42:31]: Yeah. I think that's the question of, well how, um-Uh, yeah, B2B to C is basically to me what I've been calling an agent lab, which is kind of like you're not in a model lab, but you're making a very good wrapper that is a platform that other people can sign up so they don't have to code those things. Yeah, it sound, it sounds like a much better market than the direct OpenClaw market.Ivan [00:42:56]: I've like - We I've done multiple things. So the CodeAnywhere's part of our career path R in the calendar, was very much an end user developer product. And so that is great. It You can get a lot of developer love, and I feel that we do as a company have a bunch of developer love. But it's a different type, where it's people building these things. Again, it's more akin to a Twilio because you don't really run - As a person, you wouldn't run Twilio. I don't know how many people remember. It was like ask your developer billboard and whatnot. And people really love Twilio, but they only used it inside of like, “Oh, I'm building this app or service for thing.” And so we're very much directly to that. And you also know that I used to work for a competitor for Twilio, so it's kind of ingrained, in my DNA.Swyx [00:43:35]: People don't know InfoBip is that big.Ivan [00:43:38]: Yeah, it's.Swyx [00:43:39]: Because.Ivan [00:43:40]: It's a billion euro.Swyx [00:43:40]: They're all American. They're like, “Whatever's in Europe doesn't matter to me.” But like it's the, it's the same size or bigger? Same size?Ivan [00:43:46]: It's about half the size.Swyx [00:43:47]: Half the size?Ivan [00:43:48]: Yeah, about half the size.Swyx [00:43:48]: It's like, yeah.Ivan [00:43:48]: Still huge. Multiple billions a year. Yes.Swyx [00:43:51]: That's crazy.Ivan [00:43:51]: Exactly, and so that - These are like really interesting and large revenue-generating, very sticky businesses. Whereas when you're selling to the - When your focus is the end developer, it is a very hard sell because they're very price sensitive, very price conscious, very around that. And there's very It's very hard to scale. Your cap is the number of people that are willing to spin up - First of all, wanna spin that up, and then spin up multiple of these. Whereas if you're in the enterprise one, like we know everyone's talking about like how many tokens they're spending, I'm spending. Like a lot of companies today are like, “If this is our company, spend as much as you can.” Like basically that is where we're going. And so if you think about that paradigm, where you're selling to companies that say, “Spend as much as you can to generate, productivity,” versus, “Oh, I'm a single person. I have this much budget, and I'm doing this thing because it's fun or it's helping me out or whatever.” Like it is a different, it's a different go-to-market, I think, strategy.MCP, CLIs, and Sandboxes as the Agent RuntimeSwyx [00:44:50]: Yeah, there's a lot of discussion. I'm just kind of going through like the mental list of things that are in your favor, which is, for example, MCP versus CLI. Like obviously you want CLI. It's been very good for you. I feel like it's maybe a drop in the bucket or maybe it's huge. I'm just checking whether it's like these are big trends.Ivan [00:45:10]: Those things you - work well in our favor, to your point just because every.Swyx [00:45:13]: They're kind of drop in the bucket, right?Ivan [00:45:15]: I think it's like sort of all the things come together. And so there's so many things that impact that. To your point, like OpenClaw wasn't huge for us, but like having the agent SDK, from Anthropic, so or Cloud Claude Code was very interesting. The reason why it was interesting is that a lot of, let's call them app I don't know what to call them, app layer agent companies, essentially they are like, “Oh, I can create this new app, this new agent. All I need, I just use Claude Code, and I throw it into a sandbox, and then I have my interface to the human to that.” And so that enabled so many more companies to actually offer this, and then they would pull on sandbox. So that was, that was interesting. And to your point, like MCP, versus the CLI, the MCP is an interface against an API, whereas the CLI is like you can actually go do things. Like this is it. The difference between integrations and actually running scripts or data or analysis against a thing. So being able to use a CLI very well enables the agent to do more things, and it's because that people will invoke a sandbox, they'll run it in the CLI, and but it'll do anal-analysis on that data and then give you an actual result versus just, pulling data from an API source.Swyx [00:46:29]: Yeah, it's a layer of indirection basically, it's the same thing as agentic search versus RAG, which where you're.Ivan [00:46:34]: Exactly, yeah.Swyx [00:46:34]: Just like you just win whenever people put more agents into their workflow. And so like it doesn't really matter, but I'm just kinda teasing out like what else have people heard about that like it's sort of, “Oh yeah, this is another sandbox use case. Oh yeah, that's another one.” Am I, am I missing any big ones?Ivan [00:46:51]: The thing, the thing that people, which is the computer use stuff, which I think is probably the most interesting one, is, and to your point, we've talked to so many people over the last year. It's like, “Oh, like why do you need a sandbox? Why do you need this? Why this?” And to your point, it's like, “Oh, I need sandbox for this. I need sandbox for that. I need sandbox-” It's like, “Oh, I need it for every single thing.” And so basically what I, what I - and it sounds like a broken record, it's like you use a laptop every single day, right? And you are n of one. It's just you. But now imagine how And by the way, the laptop, the computer PC market, the PC market is about equal to the cloud market in total. So it's about 150, 180 billion a year. Something like that. It's about roughly the three cloud hyperscalers is about equal to like Apple, HP, Lenovo, whatever, It's a little bit less, but it's sort of like that. And now imagine And that's just like, so how big is the addressable market? What, how many people are there in the world now? What's the last data?Swyx [00:47:45]: Let's call it eight billion.Ivan [00:47:46]: Eight billion. And so let's say you can have two computer, like you have one personal and one business, whatever. Like so it's double that, right? and so that's 16 billion, right? How many agents are gonna be running in two years, in 10 years, in 100 years? Like And for every single task, they will need one of these. And so how big is that? That market is essentially quote unquote “infinite”. You will get to the point, and Dylan Patel was at the conference talking about, from SemiAnalysis, that talks usually about GPUs, was also talking about how CPUs will now be a bottleneck because it will be the constraint. You won't be able to grow, or we won't be able to have enough of these because there won't be enough CPUs to basically do.Swyx [00:48:23]: Yeah. Well, I actually had a really good podcast with Doug Oliphant, who, which was his president at SemiAnalysis, where they've basically been like, yeah, it's been a GPU shortage first, but then it's cascaded down to memory and now to CPUs.Ivan [00:48:35]: CPU, yeah.Swyx [00:48:35]: It-What's next? So networking. So, networking actually has been in shortage for a while if you're looking at, just GPU networking. But, yeah, it's really crazy the amount of computer use that's going on, yeah, cool. I, other questions are, just the one very big part is the open sourceness which you didn't have to do, your competitors don't do, like it's not, a lot of people are worried about keeping their projects open source because some competitor can just slot fork it. I don't know if there's any reflections on just being an open source company.Open Source, Trust, and Enterprise ProcurementIvan [00:49:15]: Yeah. There's a bunch. So we the original product that we did was open source.Swyx [00:49:19]: Yeah. CodeAnywhere.Ivan [00:49:20]: So doing that was actually very good for us. There's basically a saying of, What's the saying? Like, companies that are, that are doing really well, measure themselves against, free cashflow, that are kinda okay, it's EBITDA, then, it's, it goes all the way down.Swyx [00:49:36]: The worst is like GitHub stars.Ivan [00:49:37]: GitHub stars. GitHub stars are the worst, yeah. So you go all the way down to GitHub stars. And so our original one was GitHub stars. That's what we talked about, we're at the point we're talking about revenue, so we're we've gone up the stack on that. And so we started.Swyx [00:49:47]: No, profit.Ivan [00:49:48]: Yeah. We haven't, we're, we'll get there. We'll get there. But basically at that point we did stars and GitHub and it was useful, and the original variation that we did, it we split the core into its own repo and it was Apache 2.0, so very, permissive. And then we basically would bundl

Matthew Shindell discusses the Islamic Renaissance, noting that scholars in Baghdad and Damascus conducted rigorous scientific observations while Western Europe possessed only fragmented ancient knowledge. This era's large-scale translation movement and original astronomical research eventually fueled the later European Renaissance. Shindellalso analyzes Dante Alighieri's reinterpretation of Mars in the Divine Comedy, where the planet represents a celestial sphere of virtue. Moving beyond traditional associations with war, Dante portrays Mars as a symbol of fortitude and holy martyrdom. This literary shift connected the red planet to the sacrifice of Christ and his followers. (2/4)1917 Burroughs

Last time we spoke about the battle of West Suiyuan. The Ma Clique, Muslim warlords controlling Northwest China, led by Ma Hongkui and Ma Hongbin, rebuffed Japanese overtures to ally, citing historical grievances like the 1900 invasion. Driven by patriotism, they aligned with the Nationalists, reorganizing forces into the 17th Army Group. In 1938, Ma Hongbin commanded West Suiyuan defenses, building fortifications in harsh desert and mountain terrain, blending cavalry tactics with modern training despite equipment shortages. In January 1940, Japanese and puppet troops advanced from Baotou, occupying Wuyuan and Linhe. Chinese forces, including Fu Zuoyi's 35th Army and Ma's 81st Army, employed guerrilla and mobile warfare. A major counterattack in March recaptured Wuyuan, killing Lt. Gen. Mizukawa and thousands, forcing Japanese retreat. Through ambushes and night raids, the Chinese recovered territories, securing Soviet aid routes and the Shaanxi-Gansu-Ningxia region. Over 2,000 Ningxia soldiers perished, their sacrifices underscoring peripheral fronts' role in national resistance.   #200 The battle of Yaoyi Welcome to the Fall and Rise of China Podcast, I am your dutiful host Craig Watson. But, before we start I want to also remind you this podcast is only made possible through the efforts of Kings and Generals over at Youtube. Perhaps you want to learn more about the history of Asia? Kings and Generals have an assortment of episodes on history of asia and much more  so go give them a look over on Youtube. So please subscribe to Kings and Generals over at Youtube and to continue helping us produce this content please check out www.patreon.com/kingsandgenerals. If you are still hungry for some more history related content, over on my channel, the Pacific War Channel where I cover the history of China and Japan from the 19th century until the end of the Pacific War. After capturing Wuhan, the Japanese army had already stretched itself dangerously thin. Most regular and Class A reserve divisions were committed to the front, yet they failed to annihilate the main Chinese force. Despite losing its core industrial and resource regions, the Nationalist government in Chongqing refused Japan's peace terms. Japan now found itself trapped in the very protracted war it had desperately sought to avoid. The logical Japanese response was to halt major advances, consolidate control over occupied areas, and conduct limited offensives to pressure Chiang Kai-shek into negotiations—essentially repeating the post-Nanjing strategy of late 1937. But the situation had deteriorated sharply: occupied territory had at least doubled, Japanese garrisons were inadequate, and strategic reserves were nearly exhausted. What might have been prudent a year earlier had become plainly unwise by late 1938.   To stabilize the front, Japan reorganized its China Expeditionary Army at the end of 1938. Large numbers of newly raised independent mixed brigades and lower-quality Class B reserve divisions were sent to relieve veteran regular and Class A divisions. The relieved units were either demobilized back to Japan or shifted north to reinforce the Kwantung Army against the Soviet threat.   By early 1940 Japan maintained roughly 24 divisions, 21 independent mixed brigades, and 2 cavalry brigades in China proper (excluding Manchuria), totaling nearly 800,000 ground troops. The enormous scale and expense strained the home economy severely. Even so, the vast occupied zones could not be effectively controlled: divisions often held only a single mobile battalion while dispersing the rest into scattered platoon- and squad-sized outposts. Guerrilla activity by both Nationalist and Communist forces not only persisted but intensified, occasionally clashing with each other in "friction" incidents.   Beyond mere occupation, Japan sought to wear down Chinese strength. With most elite Central Army units held in reserve in the southwest or around Wuhan, Japanese local offensives targeted the Fifth and Ninth War Zones, aiming to methodically destroy Chiang's best troops. Thus, while other Japanese armies focused on garrison relief and brigade substitution, the 11th Army—still holding Wuhan with seven divisions and three brigades—remained the main offensive instrument. In 1939 it captured Nanchang, then mounted major operations against the Fifth War Zone (Suizao Campaign) and Ninth War Zone (First Battle of Changsha). Except for the seizure of Nanchang, however, these offensives inflicted only limited and temporary damage on Chinese forces.   Japan's domestic economy was in even worse shape. In early 1937, it had approved a massive 2.4 billion yen naval and army rebuilding program aimed at countering the United States and Russia, but implementation had barely started when the Sino-Japanese War erupted. The conflict generated enormous war costs while military expansion continued unabated, rapidly draining the Bank of Japan's gold reserves. By the end of 1938, those reserves (valued at just 1.35 billion yen) had shrunk by more than two-thirds. To fund the Battle of Wuhan that year, Japan postponed key elements of the rebuilding plan. After Wuhan fell, the Army revised its wartime reorganization: the original target of forty divisions grew to fifty-five by early 1938, then to sixty-five divisions plus 164 Army Air Force squadrons by 1942. The funding required to equip and stockpile for this expansion escalated steadily; the 1939 expansion budget alone demanded 1.8 billion yen, pushing Japanese finances to the breaking point.   Japan repeatedly sought a way out of China, but its peace terms remained far beyond what Chongqing would accept, leaving negotiations stalled. Efforts to install puppet regimes in North and Central China—culminating in the Wang Jingwei government in 1940—aimed to "use Chinese to control Chinese" and undermine Nationalist influence, yet produced disappointing results.   The 11th Army's 1939 campaigns yielded only mediocre outcomes, hampered by chronic troop shortages. Even its divisions were tied down in occupation duties; mounting a serious offensive required pulling garrison forces, leaving no reserves to hold the line unless new units arrived. Sustained large-scale operations to seriously weaken Chinese strength demanded a major troop increase—otherwise, Japan was limited to shallow, localized attacks. Lt. Gen. Yasuji Okamura, commanding the 11th Army, recognized this clearly. In a December 1939 report, he argued that diplomacy and small offensives were futile and urged a large-scale operation backed by substantial reinforcements. His superiors, however, were preoccupied with funding the broader military buildup and could offer no extra men. The post-Wuhan "defensiveization" of operations was largely a cost-saving measure to support that expansion. Japanese ground strength in China, which peaked near 850,000 after Wuhan, had already dropped by about 50,000. Full-strength regular or Class A divisions numbered roughly 22,000 men (four regiments), while newer garrison divisions had only about 15,000 (three regiments), and independent mixed brigades just 6,000. Okamura's proposal was sensible but politically impossible; high command was even contemplating slashing China troop levels to 400,000.   The Chinese Winter Offensive of December 1939, together with counterattacks at Nanning and Kunlun Pass, inflicted serious losses and exposed the limited damage done to Chinese forces in 1939 operations. The recapture of Wuyuan in March 1940 signaled the start of a new phase. Shortly afterward, intensified Chinese guerrilla raids deep into Japanese rear areas prompted large Japanese "mop-up" operations in southern Shanxi, central Hubei, southern Jiangxi, and northern Hunan. In the Wuhan sector, repeated blows from the Winter Offensive heightened fears of Chinese forces in the Dahong and Tongbai Mountains, which threatened control over the vital Jianghan Plains rice-producing region. In mid-April 1940, the Japanese abandoned outposts at Macheng (eastern Hubei), Fengxin, and Jing'an (northern Jiangxi), withdrew elements of the 6th Division (northern Hunan), 40th Division (northern Jiangxi), and the 3rd, 13th, and 39th Divisions (Hubei), and concentrated them around Zhongxiang, Suixian, and Xinyang for a maximum-effort push.   These setbacks finally forced Tokyo to abandon deep troop reductions in China and approve reinforcements of two regular divisions for a major 1940 offensive. The revised end-1940 target became 740,000 troops in China. In spring 1940, the 11th Army—backed fully by Imperial General Headquarters and the China Expeditionary Army—began detailed preparations for a large-scale assault on China's Fifth War Zone.   On February 25, 1940, the 11th Army issued its "Guiding Strategy for the Campaign." The operational goal was to defeat the main force of China's Fifth War Zone along both banks of the Han River before the rainy season, inflict further heavy losses on Chiang Kai-shek's army through decisive victory, and thereby advance Japan's overall political and strategic position vis-à-vis China. The guiding principle called for the quickest possible preparations, with the offensive to begin around early May: first destroy Chinese forces on the left (east) bank south of the Baihe River, then completely annihilate the core units on the right (west) bank near Yichang. On April 7, under the new commander Lt. Gen. Sonobe Kazuo (who replaced Okamura Yasuji), the 11th Army produced a more detailed plan. On April 10, Imperial General Headquarters Order No. 426 ("Continental Order") authorized the China Expeditionary Army to conduct operations in central and southern China during May–June, even beyond established boundaries, to fulfill current objectives.   Japanese planners viewed the Fifth War Zone—roughly 50 divisions encircling Wuhan—with its main strength concentrated along the Han (Xiang) River in northwestern Hubei. Striking Yichang would deliver a severe blow to the zone. As the gateway to Sichuan, only 480 km from Chongqing, Yichang held immense strategic value: an inland port, Three Gorges logistics hub, and key base for air raids on Chongqing. Capturing it would directly threaten the Nationalist wartime capital and southwestern rear, advancing political leverage. Still, long-term occupation was not pre-decided; initial plans stressed inflicting maximum damage followed by withdrawal, in line with the post-Wuhan policy of avoiding permanent overextension. China, aware that holding the Jianghan Plain's rice-producing areas enabled sustained attrition against Japan, deployed guerrilla units to harass Japanese rear areas (increasing occupier losses) while tasking the River Defense Force to hold key front-line points: Jingmen, Shashi, and Yichang.   To achieve these aims, the 11th Army committed as much as possible of its seven divisions and four brigades (88 battalions total). Core units included the 3rd Division (Maj. Gen. Yamakoshi Masataka; regiments 6, 18, 34, 68), 13th Division (Maj. Gen. Tanaka Shioichi; 58, 65, 104, 116), 39th Division (Maj. Gen. Murakami Keisaku; 231–233), elements of the 40th Division, detachments from the 33rd and 34th Divisions, and others. Reinforcements comprised the Ikeda Detachment (three battalions from 6th Division), Ishimoto Detachment (four–five from 40th), Ogawa Detachment (two from 34th), and Provisional Mixed Brigade 101. Supporting assets included the 6th Field Heavy Artillery Regiment, 7th and 13th Tank Regiments, 3rd Air Group, Navy 1st China Dispatch Fleet, and 2nd Combined Air Team. The China Expeditionary Army transferred seven battalions from the 15th and 22nd Divisions (13th Army, lower Yangtze). The main effort north of the river involved roughly 48–54 battalions, or 80,000–110,000 men, making the Zaoyi (Zaoyang–Yichang) Campaign the largest Japanese operation on the central front since Wuhan. Sonobe's staff structured the offensive in two phases. Phase One targeted the Fifth War Zone's main force around Zaoyang (east of the Han River) through converging pincer movements: right flank from Xinyang (reinforced 3rd Division), left flank from Zhongxiang (reinforced 13th Division), and central thrust by the reinforced 39th Division from Suixian. The plan exploited terrain—Dahong and Tongbai Mountains—for encirclement. After seizing Minggang (right flank) and advancing from Zhongxiang (left), the pincers would close on Zaoyang, with the center (along the Xianghua Highway from Suixian) drawing Chinese forces into the trap for envelopment. Diversionary attacks south of the Yangtze, propaganda hinting at limited scope, and planted false orders helped mask intentions. Japanese radio intelligence—intercepts and direction-finding of Chinese headquarters signals—provided critical advantages, especially in later stages.   By March 1940, Chinese intelligence had already detected the 11th Army's intent to mount a major offensive from Xinyang and Wuhan into northwestern Hubei. On April 10, Chiang Kai-shek telegraphed Li Zongren and other Fifth War Zone commanders, urging immediate preparations for a preemptive strike against any push toward Shapingba and Yichang. He emphasized proactive flanking attacks on Japanese rear areas via Wusheng Pass and threats to the Pinghan Railway, while keeping main forces east of the Han River for decisive engagement once the enemy committed.   Following Military Commission directives, the Fifth War Zone devised a plan that used part of its strength for forward advances and deep raids into Japanese rear areas to harass and divert. The bulk of forces would hold the rear, seizing chances for preemptive strikes and a decisive battle east of Zaoyang or south of Jingmen–Dangyang. Deployments included: the 33rd Army Group garrisoning the Xiang River; in the center, the 45th Corps (22nd Army Group) west of Luoyangdian–Suixian and the 84th Corps (11th Army Group) north of Suixian–south of Gaocheng; in southern Henan, the 30th Corps east of Tongbai and the 68th Corps north of Pingchangguan–Minggang; the 41st Corps in reserve near Xiangyang; the 29th Army Group (with part garrisoning north of Tongqiao Zhen–Sanyangtien) concentrated in the Dahong Mountains; and the 31st Army Group positioned between Queshan and Ye Hsien as the mobile force to strike invaders. River Defense Army commander Guo Chan controlled the 26th, 75th, and 94th Armies, the 128th Division, and the 6th and 7th Guerrilla Columns. Total Chinese strength approximated 350,000–380,000 men across roughly 50–54 divisions. To mask preparations and mislead, the Japanese conducted a late-April "mop-up" near Jiujiang, staged naval feints on Poyang and Dongting Lakes, and bombed key points in Hunan and Jiangxi, simulating an imminent Ninth War Zone operation.   With forces assembled, the Japanese offensive began May 1, 1940, from Xinyang, Suixian, and Zhongxiang. The advance split into five routes: (1) Changtaiguan–Minggang–Biyang–Tanghe; (2) Xinyang–Tongbai; (3) Suixian–Zaoyang; (4) Suixian–Wujiadien; (5) Zhongxiang–Shuangkou. Employing flanking with central breakthrough, the reinforced 3rd Division (right flank, including Ishimoto Detachment from 40th Division with tanks and engineers) spearheaded from Xinyang toward Biyang, breaching the Chinese Second Army front on day one. By May 1, elements of the 3rd and 40th Divisions captured Minggang, Lion's Bridge, and Xiaolintien; on May 5 they took Biyang and Tongbai. The Chinese 31st Army Group (northeast of Biyang) linked with the 68th and 92nd Corps to hit Japanese flanks and rear. Leaving some forces west of Tongbai to press the enemy, the main 30th Corps struck Japanese flanks. After seizing Tanghe on May 7, the Japanese pushed south toward Zaoyang. On May 8–9, the 31st Army Group retook Tanghe and Xinye, pursuing vigorously. On May 8, the Japanese left flank (13th Division) attacked from Zhongxiang, breaking through the 33rd Army front the same day.   On May 3, the Japanese 13th Division—supported by over 20 tanks, 40 aircraft, artillery, and cavalry—advanced north from Zhongxiang, capturing Changshoudian and Tianjiachi. It seized Fengyao and Changjiachi by May 6. Chinese 33rd Army Group forces used favorable terrain to intercept, while the 29th Army Group struck Japanese flanks and rear at Changjiachi and Wangjiadian, and the 41st Corps fought tenaciously to halt the advance. By May 7, Japanese spearheads reached Changjiachi on the Zaoyang–Xiangyang Highway, with elements entering Shuangkou; their rear cavalry took Xinye on May 8. Fifth War Zone commander Zhang Zizhong personally led attacks along Tianjiachi–Huanglongtang, supported by fierce 29th Army Group assaults on Japanese rear.   The Japanese 39th Division and a 6th Division brigade delayed their assault on the Chinese 11th Army Group until May 4 from Suixian. After overrunning Gaocheng and Anchu on May 5, Chinese forces withdrew to Huantan–Tang Hsien–north of Gaocheng. As the 33rd Army Group faltered, part of the 11th Army Group reinforced it; the 175th Division held at Tang Hsien while the main body fell back toward Zaoyang. During the maneuver, Japanese tanks enveloped at Tang Hsien, cutting the Zaoyang–Xiangyang Highway and forcing bitter fighting by the 174th Division. To break out, Chinese abandoned Zaoyang, using the 173rd Division for rearguard resistance while the bulk shifted west of the Tang and Bai Rivers. Japanese captured Suiyangdian and Wujiadien on May 7, Zaoyang on May 8; the 173rd Division suffered heavy losses, including the death of its commander, Gen. Zhong Yi.   On May 10, Japanese completed an encirclement east of Xiangdong along the Tang and Bai Rivers—but it collapsed as Chinese exterior forces outflanked both Japanese wings and compressed the center, trapping much of the Japanese in the Xiangdong Plains. The Chinese 2nd and 31st Army Groups plus 92nd Corps pressed south, 39th and 75th Corps east, and 33rd and 29th Army Groups north against the pocket. The 94th Corps advanced along the Han–Yichang Highway deep into Jingshan, Zaoshi, Yingcheng, and Yunmeng to sever Japanese rear communications. Meanwhile, the 7th Corps and eastern Hubei guerrillas seized Jigong Shan, Lijiachai, and Liulin station on the Beijing–Hankou Railway. The 92nd and 68th Corps retook Zaoyang, Tongbai, and Minggang, encircling four Japanese divisions in the Xiangdong Plains. By May 11, battered Japanese retreated eastward under pursuit, Chinese flanking and rear attacks leaving many dead on the field. The 31st Army Group recovered Zaoyang on May 16. Chinese reports claimed 45,000 Japanese casualties, plus capture of over 60 guns, 2,000+ horses, 70+ tanks, and 400+ trucks. The 33rd Army Group fought fiercely to intercept retreating columns, driving large Japanese remnants toward Nanguadian.   Tragically, on May 16 noon, Gen. Zhang Zizhong—personally commanding his Guard Battalion and main 74th Division—was killed in action. With pressure eased on the Japanese left, they counterattacked and retook Zaoyang on May 17. Chinese forces withdrew to Xinye on the Tangbai River's west bank and north of the Tang River, regrouping for a renewed counteroffensive.   The Military Commission anticipated a Japanese withdrawal to original lines, likely along the rain-impassable Xianghua Road. Exploiting the enemy's supply shortages, exhaustion, and retreat difficulties, it ordered Fifth War Zone units to encircle and annihilate Japanese forces near the battlefield, then pursue toward Yingcheng–Huayuan. The zone promptly launched a counteroffensive. By nightfall on May 8, Japanese pincers neared junction, having inflicted serious damage on the Chinese 84th Army but achieved little else. Nonetheless, the 11th Army ordered frontline divisions to withdraw to the Tanghe–Baihe line after reaching it, preparatory to encircling Chinese forces west of the Han River. Chongqing issued general offensive orders at 8 PM and 11 PM that night. By then, six divisions of the 31st Army Group advanced south from Nanyang in the north, five from the 33rd Army Group pressed from the south, and five from the 45th and 94th Armies pursued in the southeast—nearly completing the Japanese encirclement. Intense combat erupted.   On May 10, retreating Japanese first clashed with the advancing 33rd Army Group from the south. Seizing the moment, they ordered the 13th and 39th Divisions plus Ikeda Detachment south to smash it, with the 3rd Division covering the northern flank. Full-scale battle broke out on May 12: two Japanese divisions assaulted five Chinese divisions of the 33rd Army Group, plunging them into desperate fighting. Japanese radio intercepts—including telegrams between the Military Commission and Fifth War Zone, plus Zhang Zizhong's report to Chiang on his five divisions' movements—revealed exact positions and plans. Sonobe Kazuo concentrated the 13th and 39th Divisions to strike south along the Han's east bank against Zhang's army group, while ordering the 3rd Division (south of Xinye) back to Zaoyang to guard the rear. Direction-finding had long pinpointed the 33rd Army Group headquarters radio (call signs and bearings) about 10 km northeast of Yicheng. With air support, the Japanese encircled it. On the night of May 15, the 39th Division advanced from Fangjiaji and Nanying toward Nanguadian, completing tactical encirclement by dawn on May 16. Artillery-supported four-sided assaults followed. The defending 74th Division resisted fiercely with repeated counterattacks. Fighting raged into the afternoon, with the Special Service Battalion joining. Japanese attackers swelled to over 5,000, backed by concentrated artillery and 20+ aircraft for a final push. Zhang Zizhong, wounded multiple times, continued commanding calmly until a severe chest wound killed him heroically. The exhausted, isolated 74th Division and battalion suffered devastating losses. That day, the 13th Division also routed the main 33rd Army Group force, breaking the southern encirclement. Japanese then redeployed, concentrating around Zaoyang.   In the north, 17 divisions (including six from the 31st Army Group) attacked the isolated Japanese 3rd Division from east, south, and north, severing its supply lines. With limited ammunition and no resupply, the division faced crisis; its 29th Brigade telegram pleaded: "Enemy fighting spirit extremely high... safe return very difficult; request battalion reinforcements." Yet southern Chinese forces remained undestroyed amid chaos. Japanese choices narrowed to independent 3rd Division retreat or holding for relief. They opted to lure pursuers: ordering the division southeast toward Zaoyang to draw Chinese into pursuit. From May 16–18, the 3rd Division fought a delaying retreat; relentless Chinese pursuit inflicted limited damage due to insufficient firepower, allowing escape. By evening May 18, it reached northeast of Zaoyang and prepared offensives. The 13th and 39th Divisions, after defeating the 33rd Army Group, also advanced north to the Zaoyang line.   The 3rd Division's retreat shortened Japanese lines and hastened convergence. Unsuspecting Chinese pursued to Zaoyang. After a successful counterattack northeast of Yicheng, the 13th and 39th Divisions rejoined the 3rd Division there. On May 19 morning, three Japanese divisions attacked abreast, forcing decisive battle along the Tang River. Chinese divisions collapsed within hours; the 75th Army took heavy losses, others significant casualties. Fifth War Zone ordered hasty retreat. Japanese pursued vigorously. By May 21, the 3rd Division reached Dengxian, 13th east of Laohekou, 39th Fancheng. Early that day, the 39th Division—crossing the Baihe—met fierce west-bank fire, losing Regiment Commander Kanzaki Tetsujiro and over 300 men. That evening, the 11th Army halted pursuit, ending east-bank (Xiang River) fighting. The 20+ day operation east of the Han inflicted heavy Japanese losses, far exceeding the planned duration, leaving troops exhausted. After halting, units withdrew to Zaoyang vicinity for rest and reorganization rather than immediate return to base positions. Commanders debated proceeding to Yichang west of the Han: abandoning the plan would signal Phase One failure, eroding authority and imperial trust. Most argued troop fatigue and casualties should not deter continuation. Over 1,000 tons of supplies rushed forward via six motor companies. Following east-bank termination, Japanese consolidated for the next phase targeting Yichang. Reinforcements arrived: the 4th Division from Manchuria and 18th Independent Brigade from Wuning. The 4th Division assumed Shayang–Zhongxiang positions east of the Xiang River.   The Japanese bombarded the west bank of the Han River for ninety minutes before forcing a crossing at Wangji north of Yicheng. That midnight, the 3rd Division also crossed southeast of Xiangyang. Both met little resistance and completed crossings before dawn. The 11th Army left the 40th Division at Dahongshan for rear-area mopping-up and assigned the Xiaochuan and Cangqiao Detachments to guard mobile supply depots. On May 31 night, the 3rd and 39th Divisions crossed the Xiang River at Yicheng and Oujiamiao. After seizing Xiangyang on June 1 night, the main force split into columns crossing westward. By June 3, Japanese captured Nanzhang and Yicheng. The Chinese 41st Corps fiercely counterattacked, retaking part of Xiangyang while its main body battled around Nanzhang; the 77th Corps also struck hard. On June 4, Chinese recovered Nanzhang, forcing Japanese retreat southward. Meanwhile, the 13th Division and elements of the 6th Division forced a crossing on the Han–Yichang Highway near Jiukou and Shayang to link with southern columns for a joint push. The Chinese River Defense Force shifted its main strength to key positions, using terrain to block southward advances. The 2nd and 31st Army Groups pursued south separately. Chinese abandoned Shayang on June 5; Japanese took Jingmen, Shilipu, and Shihujiao on June 6. The 77th Corps and river defense units resisted stubbornly from Jingmen to Jiangling. After retaking Yicheng, the 2nd Army Group continued pursuit. Japanese concentrated around Jingmen–Shilipu as Jiangling fell.   On June 9 morning, Japanese launched joint air-ground assaults from Dongshi to Dangyang and Yuanan. By afternoon, penetrating the Chinese right flank forced a night withdrawal to Gulaobei–Shuanlianshi–Dangyang along the Zu River to Yuanan. June 10 saw Japanese capture Gulaobei and Dangyang, pushing Chinese to Yichang outskirts. After days of heavy fighting and prohibitive losses, Chinese abandoned Yichang on their own initiative. The 2nd and 31st Army Groups then reached Dangyang north of Jingmen. On June 16, they mounted a general offensive. By June 17, Chinese briefly retook Yichang; the 2nd Army Group linked with the 77th Corps against Dangyang, while the 31st Army Group severed Dangyang–Jingmen communications and assaulted Jingmen violently. South of the Yangtze, the 5th and 32nd Divisions crossed to hit Shayang and Shilipu. By June 18, Japanese main force held stubbornly from Dangyang to the Xiang River with superior equipment. Chinese, fighting on exterior lines, formed an encirclement from Jiangling–Yichang–Dangyang–Zhongxiang–Suixian–north of Xinyang while maintaining surveillance. Thus, the Zaoyi (Zaoyang–Yichang) Campaign ended. No prior decision existed on holding Yichang long-term. Per post-Wuhan Imperial General Headquarters policy, even extended operations aimed only to inflict severe blows and erode Chinese resistance, not expand occupation. On capture day, the 11th Army declared objectives achieved, ordering reorganization, destruction of Yichang military facilities, and dumping irremovable captured supplies into the Yangtze preparatory to withdrawal. At 10 PM June 15, formal orders withdrew to the Han's east bank: 3rd and 39th Divisions first to Dangyang–Jingmen to cover, then the 13th Division. The 13th began retreating from Yichang at midnight June 16, reaching Tumenya (10 km east) by 7 AM June 17. Chinese counterattacked along the route; the 18th Army pursued and retook Yichang morning of June 17. Japanese held Yichang only four days.   Intense debate erupted between frontline commanders and Imperial General Headquarters over retaining Yichang. With Nazi Germany's Western Europe offensive underway—Paris fell June 12, the day Yichang was taken—global upheaval intensified Japanese urgency to resolve China swiftly and free resources for wider competition. Many in high command and China Expeditionary Army argued long-term occupation would threaten Chongqing more directly, aid political maneuvers, and hasten settlement, offering immense strategic value. This swayed the Emperor, who inquired at the June 15 Imperial Conference about securing it. Backed by imperial support, high command ordered temporary retention (one month) on June 16. By transmission through Expeditionary Army and 11th Army channels, the rearguard 13th Division had withdrawn 52 km. With 3rd Division cooperation, it reversed, broke Chinese resistance, and retook Yichang afternoon June 17. On July 1, to offset expanded 11th Army responsibilities, General Headquarters transferred the 4th Division from Kwantung Army (Jiamusi, Heilongjiang) to 11th Army control. July 13 orders confirmed long-term Yichang retention, redefining Wuhan-region operations to Anqing–Xinyang–Yichang–Yueyang–Nanchang. The 11th Army assigned: 13th Division to Yichang, 4th Division to Anlu, 18th Independent Mixed Brigade east/west of Dangyang; remaining units returned to original defenses.   Post-recapture, Chinese continued counterattacks on Yichang and rear lines until ordered to halt: "To adapt to international changes, preserve National Army combat strength, and facilitate reorganization, Fifth War Zone cease attacks on Yichang immediately." A stalemate followed along lines encircling Yichang, Dangyang, Jiangling, Jingmen, Zhongxiang, Suixian, and Xinyang. To shield Chongqing and Sichuan, Nationalists re-established the Sixth War Zone (briefly created post-First Changsha, abolished April 1940), appointing Chen Cheng commander-in-chief with 33rd and 29th Army Groups, River Defense Army, and 18th Army covering western Hubei, western Hunan, eastern Sichuan. The Zaoyi campaign thus concluded. Japanese combat power again proved markedly superior. Official Japanese records (11th Army/China Expeditionary Army) reported 2,700 killed, ~7,800 wounded (total ~10,500; some phases ~1,403 killed/4,639 wounded). Chinese admitted heavy losses: 36,983 killed, 50,509 wounded, 23,000 missing (total >110,000 in some accounts). Wartime Nationalist claims inflated Japanese casualties to 45,000 killed/wounded with major captures (60+ guns, 70+ tanks, 400+ trucks), likely propagandistic; Japanese sources show far lower equipment losses. With 56 battalions deployed, Japanese suffered 12–15% combat casualties; Chinese (54 divisions, ~380,000 men) incurred 25–30% or higher—underscoring firepower/equipment disparity. Japan achieved tactical success by securing Yichang long-term (as a Chongqing bombing base) but failed to annihilate the main Chinese force or compel peace. Chinese resistance thwarted full encirclement and imposed attrition, albeit at crippling cost to the Fifth War Zone—severely weakened and never fully recovering until war's end. Japanese aims were realized to a significant, though not decisive, degree.   The Fifth War Zone's operational plan was fundamentally sound. Chinese intelligence detected Japanese intentions early, accurately predicted the attack axis, and deployed accordingly. The plan included preemptive strikes at Wusheng Pass and the Guangshui section of the Pinghan Railway to harass Japanese rear areas, threaten Wuhan, gather reconnaissance, and disrupt enemy preparations. Though well conceived, these actions never materialized. In the first phase (Xiangdong operations), Chinese forces resisted while shifting the main body to outer lines, securing mobile flanking positions. This frustrated Japanese encirclement efforts in the Xiangdong Plains. Exploiting the enemy's retreat, China launched a timely counteroffensive that encircled the Japanese 3rd Division. Despite breakout support from over 100 aircraft and 200 tanks, the poorly equipped Chinese inflicted heavy casualties during the three-day siege, blunting the division's momentum.    On the southern front, the 33rd Army Group's intercepting deployment was appropriate, but insufficient strength and compromised communications allowed the Japanese 13th and 39th Divisions to counterattack decisively, inflicting major losses and claiming the heroic death of Commander-in-Chief Zhang Zizhong—whose steadfast patriotism remains a lasting source of national pride. Overall, Chinese assessments and deployments in Phase One were largely correct. The battlefield showed China retained initiative and was not wholly dominated by Japanese plans. The core issue was overestimation of Chinese combat power amid severe shortages of heavy weapons. At least three corps suffered heavy attrition, yet Japanese captured only twenty-three mountain/field guns. Relying on manpower for brute force left Chinese units critically undergunned, enabling repeated encirclement attempts but preventing decisive destruction or severe damage to encircled enemies like the 3rd Division.   Phase Two, by contrast, was entirely passive. The initial Japanese Han River crossings were largely feints, yet the west bank received scant attention in overall planning—leaving Yichang virtually undefended as main forces deployed east of the river. Post-Phase One, Japan reinforced the 11th Army with three infantry battalions and one mountain artillery battalion from the 13th Army (lower Yangtze), plus six motor transport companies rushing massive supplies forward. Chinese intelligence missed these moves, remaining complacent in expectation of Japanese withdrawal eastward. After regrouping, Japan abruptly pivoted west with rapid advances. The Military Commission and Fifth War Zone, caught unprepared, made frantic, chaotic adjustments that failed to mount effective defense. The loss of strategically vital Yichang was inevitable, complicating the resistance both militarily and psychologically. This stemmed directly from command misjudgment of Japanese strategic and operational aims. Had plans anticipated a westward thrust and retained strong reserves—or detected the 10-day regrouping window to readjust deployments—China could have retained greater initiative, inflicted more damage, and reduced its own losses.   I would like to take this time to remind you all that this podcast is only made possible through the efforts of Kings and Generals over at Youtube. Please go subscribe to Kings and Generals over at Youtube and to continue helping us produce this content please check out www.patreon.com/kingsandgenerals. If you are still hungry after that, give my personal channel a look over at The Pacific War Channel at Youtube, it would mean a lot to me. Japan's 11th Army launched an offensive in Hubei to encircle Chinese forces in the Fifth War Zone and seize Yichang for bombing Chongqing. Chinese troops countered effectively, encircling Japanese divisions and inflicting heavy losses, though General Zhang Zizhong was killed in action. After intense fighting east of the Han River, Japanese crossed west, captured Yichang, briefly withdrew, then retook and held it long-term. 

Host of the Spacebusters & emcee of Liberpulco, Steve Falconer, stops by to dig into the hidden past of Europe and the role of the Catholic Church's army, the Knights Templar. This group was beyond national borders and operated with impunity for centuries.The role of multigenerational bloodline banking families was crucial in opening up the usury trade throughout Western Europe, and the establishment of city-states that are above the laws of the land even to this day. Steve takes his audience deep down the rabbit hole and back through the centuries to discover what really happened in our past.—Guest LinksSteve FalconerYouTube Channel: https://www.youtube.com/@spacebusters3933—Video ChannelsWatch the video version of Macroaggressions:Rumble: https://rumble.com/c/Macroaggressions YouTube: https://www.youtube.com/@MacroaggressionsPodcastBrighteon: https://www.brighteon.com/channels/macroaggressions/—MACRO & Charlie Robinson LinksHypocrazy Audiobook: https://amzn.to/4aogwmsThe Octopus of Global Control Audiobook: https://amzn.to/3xu0rMmWebsite: www.Macroaggressions.ioMerch Store: https://macroaggressions.dashery.com/ Link Tree: https://linktr.ee/macroaggressionspodcast—Activist Post FamilySign up for the Activist Post Newsletter: https://activistpost.kit.com/emailsActivist Post: www.ActivistPost.comNatural Blaze: www.NaturalBlaze.com —Support Our SponsorsGround Luxe Grounding Mats: https://GroundLuxe.com/MACROReplace Your Mortgage: www.WipeOutYourMortgageNow.comC60 Power: https://go.ShopC60.com/PBGRT/KMKS9/ | Promo Code: MACROChemical Free Body: https://ChemicalFreeBody.com/macro/ | Promo Code: MACROWise Wolf Gold & Silver: https://Macroaggressions.Gold/ | (800) 426-1836LegalShield: www.DontGetPushedAround.comEMP Shield: www.EMPShield.com | Promo Code: MACROChristian Yordanov's Health Program: www.LiveLongerFormula.com/macroAbove Phone: https://AbovePhone.com/macro/Van Man: https://VanMan.shop/?ref=MACRO | Promo Code: MACROThe Dollar Vigilante: https://DollarVigilante.spiffy.co/a/O3wCWenlXN/4471Nesa's Hemp: www.NesasHemp.com | Promo Code: MACROAugason Farms: https://AugasonFarms.com/MACRO—

Dominik Tarczyński says mass amnesty for 500,000 illegal migrants is “suicide,” declares Spain, Rome, Paris and other EU cities culturally dead, and argues only Trump‑style deportations and tough borders can save Western Europe from permanent collapse

Last time we spoke about the first battle of Changsha. Japanese forces under General Okamura Yasuji, including the 6th, 13th, and 33rd Divisions, launched a multi-pronged offensive, crossing the Xin Qiang River and capturing Yingtian amid brutal fighting. Chinese defenses, commanded by Xue Yue in the Ninth War Zone, employed gradual resistance strategies, with units like the 195th Division under Qin Yizhi holding key positions such as Bijia Mountain and Fulinpu, inflicting heavy losses. Battalion Commander Luo Wenlang recaptured Dongtang in a midnight assault, grieving his fallen brother amid Mid-Autumn moonlight. Chiang Kai-shek, from Chongqing, oversaw operations while hosting a festive banquet, buoyed by international support like U.S. loans. By October, Japanese advances stalled; Okamura ordered a retreat on October 2, exposed by a downed plane yielding critical documents. Chinese forces pursued, reclaiming lines by October 8, annihilating over half the invaders per Chiang's commendation.   #198 The Battle of South Guangxi Welcome to the Fall and Rise of China Podcast, I am your dutiful host Craig Watson. But, before we start I want to also remind you this podcast is only made possible through the efforts of Kings and Generals over at Youtube. Perhaps you want to learn more about the history of Asia? Kings and Generals have an assortment of episodes on history of asia and much more  so go give them a look over on Youtube. So please subscribe to Kings and Generals over at Youtube and to continue helping us produce this content please check out www.patreon.com/kingsandgenerals. If you are still hungry for some more history related content, over on my channel, the Pacific War Channel where I cover the history of China and Japan from the 19th century until the end of the Pacific War. In January 1939, the Japanese General Headquarters, responding to naval needs, ordered the 21st Corps to seize Hainan Island. The goal was to establish a base for air operations against southwestern China and to enforce blockade measures. Supported by the Japanese Navy, the Corps deployed the Taiwan Brigade, which landed at Haikou on February 10. After initial defeats, Chinese peace preservation units withdrew to the island's interior and conducted harassment operations. Japanese troops soon occupied northern counties including Qiongshan, Wenchang, Ding'an, Qionghai, and Chengmai, followed by the port of Yulin, which positioned them for southward advances toward Guangxi.   This invasion was part of a broader strategy to disrupt Chinese supply lines and secure a foothold in southern China. Although Chinese resistance on Hainan ultimately failed to repel the invaders, it highlighted the resilience that would define regional fighting.   After the costly Battle of Wuhan, the Sino-Japanese War reached a stalemate in central China, despite ongoing large-scale conflicts and Japanese strategic bombings that caused heavy casualties without breaking the deadlock. Politically, Japan's alignment with the Axis powers and the start of World War II in Western Europe led European nations to bolster ties with China. With major coastal ports under Japanese control, the Nationalist government's main overseas supply route became the Haiphong-Kunming railway in French Indochina, which transported four times more war materials in 1938 than in 1937, including heavy equipment purchased abroad.   The Hainan occupation negatively impacted Japan's war efforts, though diplomatic pressure on Britain and France proved ineffective. Meanwhile, the Imperial Japanese Navy proposed a southward advance: invading from Nanning to Longzhou County in Guangxi by sea to establish an airfield for strategic bombing. An April 15, 1939, Navy Department assessment deemed large-scale inland army operations challenging, recommending instead that the army and navy collaborate to occupy Shantou—the largest trading port on the South China coast—before pushing into Guangxi to seize Nanning and sever China's vital Indochina supply line.   In June, the Japanese General Staff's "Military Geography" emphasized that occupying Nanning would provide convenient transportation in all directions, reaching Guangdong, Hunan, Guizhou, and Yunnan. The Nanning-Lang Son road had become a major artery for Chiang Kai-shek's regime to connect with the southwest. To cut it off directly, Nanning must be captured first. Once occupied, heavy troops near Tokyo Bay would not be needed to achieve the operation's purpose. This idea gained considerable support both politically and tactically. The Army's northward policy had been defeated by the Soviet Union in the Battle of Khalkhin Gol in September 1939. Major General Tominaga Kyoji, the newly appointed head of the First Department of the General Staff, sought to avoid further embarrassments. Supporting the proposal involved transferring the 5th Division of the Kwantung Army, originally intended for Khalkhin Gol, to the south. This prevented front-line units from misjudging higher-ups' positions and allowed implementation without affecting existing troops.   In September, the European war broke out. The Japanese General Headquarters ordered the 21st Army to capture the vicinity of Nanning, cut off the international passage between Guangxi and Vietnam, and obtain a base for air operations in southwest China. Japan aimed to completely sever China's most important supply route. According to Japanese intelligence, the French Indochina line accounted for 85% of China's foreign aid in late 1939, with 12,500 tons transported in September alone.   On September 1, 1939, Germany attacked Poland; on September 3, Britain and France declared war on Germany, igniting World War II. Japan, eager to resolve the China issue and free up troops to seize Western colonies in Asia and the Pacific, stated through Prime Minister Nobuyuki Abe on September 4: "At the outbreak of the European war, the Empire will not intervene and has decided to focus on resolving the China Incident." In Nanjing, the China Expeditionary Army Headquarters was established, with General Nishio Hisazo as Commander-in-Chief and Lieutenant General Itagaki Seishiro as Chief of Staff, overseeing the North China Area Army, the 11th Army, the 13th Army, and the 21st Army.   On September 23, the Japanese General Headquarters issued an order to prepare for a swift response to the China Incident. On October 16, "Continental Order No. 375" directed the Commander-in-Chief of the China Expeditionary Army to swiftly cut off enemy supply routes from Nanning to Longzhou with a portion of the navy. Also on October 16, "Continental Order No. 582," a central Army-Navy agreement, aimed to cut off enemy routes along the Nanning-Longzhou line and strengthen naval air operations against the Yunnan-Vietnam Railway and the Burma Road. The operation was scheduled for mid-November. On October 19, Nishio Juzo issued orders for the Guangxi operation, involving the 5th Division, Taiwan Mixed Brigade, supporting units, the 5th Fleet (renamed the 2nd Expeditionary Fleet in mid-November), and the 3rd Combined Naval Air Group. Total strength: about 30,000 men, over 70 warships, 2 aircraft carriers, and about 100 aircraft. Tominaga Kyoji announced: "This is the last battle of the China Incident."   Politically, the Guangxi Army was a key pillar of the National Government after retreating to Sichuan. Attacking Guangxi could impact the Guangxi clique's stance on continuing the war. Cutting off the Nanning-Longzhou line would affect Vietnam-China transportation security and allow actions against French Indochina amid Europe's distractions. With tactical and political alignment, the plan was approved.   In September 1939, the Chinese repelled the Japanese attack on Changsha. In October, the National Government held the Second Nanyue Military Conference in Hengshan, summarizing the First Changsha Campaign and deciding on a new offensive. On October 29, Chiang Kai-shek announced: "Our future strategic application and the mentality of officers and soldiers must be completely transformed. We must start to turn defense into offense, turn stillness into movement, and actively take offensive measures." On November 5, after the meeting, intelligence indicated Japan's intention to invade the south. U.S. and British agencies reported the Japanese fleet gathering in Tokyo Bay, signaling an imminent operation against Nanning. Chiang flew from Hengshan to Guilin to arrange defenses.   At this time, coastal defense was guarded by the 16th Army Group under Xia Wei (transferred, with Cai Tingkai taking over), a Guangxi clique force comprising the 46th and 31st Armies. Bai Chongxi, director of the Guilin Headquarters, was in Chongqing for the Sixth Plenary Session of the Fifth National Congress of the Kuomintang, while Chief of Staff Lin Wei was in Rong County mourning Xia Wei's mother. The headquarters was essentially deserted. Zhang Fakui, commander of the Fourth War Zone, and Chief of Staff Wu Shiyuan were in Shaoguan, Guangdong. The three-tiered command structure—headquarters, war zone, army group—was practically non-existent.   The Chinese forces north of the pass were commanded by Bai Chongxi's Guilin Headquarters, with Lin Wei as Chief of Staff; they included the Fourth War Zone under Zhang Fakui and the 16th Army Group under Xia Wei. They commanded: the 31st Army (Commander Wei Yunsong; 131st Division under He Weizhen; 135th Division under Su Zuxin; 188th Division under Wei Zhen); the 46th Army (Commander He Xuan; 170th Division under Li Xingshu; 175th Division under Feng Huang; New 19th Division under Huang Gu); and a portion of the 200th Division of the 5th Army (Commander Dai Anlan). Together with the 1st-4th Independent Infantry Regiments of the Guangxi Training Corps, total strength was approximately 60,000 men.   After the Japanese landing, Bai Chongxi was stationed in Qianjiang, while the 16th Army Group headquarters in Xiawei was at Heishiyan near Binyang.   In early November 1939, the Japanese 5th Fleet and the aircraft carrier Kaga escorted the 5th Division and the Taiwan Brigade to concentrate in Haikou. Japanese aircraft bombed important cities in Guangxi. At that time, the Chinese army defended the coast from Nanning to Qinzhou Bay and Fangcheng with part of the 16th Army Group of the Fourth War Zone. The 46th Army was responsible for the coastline of Fangcheng, Qinxian, Hepu, and Liankou, and the 31st Army for key points along the Xijiang River.   On November 9, Japanese troops assembled at Sanya Bay on Hainan Island. Lieutenant General Ando Rikichi, commander of the 21st Army, personally commanded from Sanya. On the 13th, the fleet set sail. On the 14th, vanguard ships feinted at Beihai with over ten ships. A battalion of the 175th Division retaliated and was ordered to destroy Beihai, but Commander Chao Wei of the 524th Regiment believed no landing was intended, avoiding complete destruction. That night, Japanese ships turned toward Qinzhou.   To safeguard the international communications link between Guangxi and Indochina, the Chinese Generalissimo's Headquarters in Guilin assigned defensive missions. The 46th Corps of the 16th Army Group was tasked with defending the coastline from Fangcheng to Qinzhou, Hepu, and Lianjiang. The 31st Corps was responsible for key positions along the Xi River. Defensive positions were prepared in advance, and communications infrastructure was sabotaged to facilitate gradual resistance, aiming to attrition Japanese forces before a decisive engagement along the Yong River.   On November 15, under air and naval fire support, the Japanese 5th Division and Taiwan Brigade executed a forced landing on the west coast of Qinzhou Bay. Following intense resistance, the Chinese New 19th Division withdrew to Pancheng and Shangsi. After capturing Qinzhou, the Japanese 5th Division advanced north along the Yong-Qin Highway, while the Taiwan Brigade moved along Xiaodong–Baiji–Bujin Road. On November 17, the Japanese army captured Qinzhou and Fangcheng. The 5th Division immediately split into three routes along the Yongqin Highway, while the Taiwan Brigade advanced north along Xiaodong-Baekje-Pujin. On the 18th, they attacked Xiaodong, the headquarters of the New 19th Division. Division Commander Huang Gu fled alone in the face of battle. His troops were routed, and the Japanese continued northward. Meanwhile, bandits from the Shiwan Mountains formed numerous plainclothes teams to lead the Japanese advance, accelerating their northward movement. By November 21, they approached the south bank of the Yu River. On December 1, they occupied Gaofeng Pass. On December 4, they occupied Kunlun Pass and then adopted a defensive posture.   On November 16, Chiang Kai-shek summoned Bai Chongxi in Chongqing, ordering him to return to Guilin immediately to command the battle, without attending the plenary session. Bai requested full command without intervention from Zhang Fakui, and that all armies obey the Headquarters directly. Chiang approved and transferred his elite Fifth Army and other units to Bai's command. Bai telegraphed Du Yuming to lead troops by train from Hengyang to southern Guilin and reinstated Xia Wei as commander of the 16th Army Group, with Cai Tingkai awaiting orders. The 16th Army Group assembled, and Deputy Commander-in-Chief Wei Yunsong arrived in Nanning on the 19th. Units rushed to block Japanese advances. Bai flew to Guilin on the 19th and Qianjiang on the 21st, establishing the command post. Thus, as Japanese arrived in Nanning, Chinese reinforcements like the 170th Division reached Yongning on the 22nd, two regiments of the 135th Division entered Nanning on the 23rd, and the 600th Regiment of the 200th Division arrived at Ertang on the afternoon of the 24th. Other armies assembled in Liuzhou and Binyang.   On November 21, Japanese troops approached the south bank of the Yu River. Wu Zongjun, commander of the 405th Regiment of the 135th Division, arbitrarily ordered his regiments to abandon positions and retreat. Wei Yunsong ordered Su Zuxin to intercept, but Wu disobeyed. No troops defended Nanning's front lines. At dawn on the 24th, the 170th Division fought fiercely in Yongning. In the morning, the Japanese 21st Regiment crossed the river. By afternoon, Nanning had fallen. Over the next two days, they swept surrounding positions. On the morning of the 25th, the 600th Regiment of the 200th Division fought alone against Japanese regiments at Ertang. Under air cover, Japanese attacked, but Chinese resisted stubbornly. Regiment Commander Shao Yizhi and Adjutant Wu Qisheng were killed. Given the situation, Division Commanders Li Xingshu and Dai Anlan retreated to Gaofeng Pass after dusk. Though they failed to stop the advance, this was the fiercest resistance since the landing, lasting two days and nights. On November 25, Japanese attacked the 175th Division near Luwu from Xiaodong and the highway. The division moved to Nalong, assembling in villages there. The 175th attacked key points along the Yongqin Highway, including Datang, Naxiao, Dongya, Nabian, Xincheng, Xiaodong, Dadong, and Bancheng.   On November 20, the 21st Army opened its headquarters in Qinzhou. On November 26, Ando Rikichi announced the formation of the Yongqin Corps under Imamura Hitoshi. Ando left for Guangzhou on the 27th. Starting on the 26th, Japanese attacked Gaofeng Pass with aircraft cover. Despite fierce resistance, Chinese lost Gaofeng Pass on December 1. On the 4th, Japanese occupied Kunlun Pass, then adjusted deployment. The two sides confronted each other along the Kunlun Pass mountainous boundary. According to statistics up to December 1, Japanese suffered 145 dead and 315 wounded; Chinese had 6,125 dead bodies and 664 prisoners (but Japanese casualties were underreported; the 41st Infantry Regiment received 727 replacements on January 19, likely matching killed and wounded sent back). Seized in Nanning: 300 tons lead, 200 tons coal, 500 bundles cotton, 321 tons cotton thread, 30 tons iron, 60 tons tin. On December 2, the Japanese 5th Cavalry Regiment and Morimoto Battalion were attacked by about 1,500 Chinese with four tanks at Batang. Japanese dispatched the 21st Brigade (Nakamura Detachment), repelling a mixed force of the 200th and 188th Divisions. Japanese occupied Kunlun Pass but left only a battalion to defend it, withdrawing the rest to Nanning.   Bai Chongxi, director of the Guilin Headquarters and deputy chief of staff, proposed a counter-offensive plan, which was approved by Chiang Kai-shek.   On November 24, when Japanese had just occupied Nanning, Bai Chongxi demanded an immediate counterattack while Japanese were unstable and weak. After failing to gain approval, Bai asked Du Yuming to submit a request. Du sent a telegram on December 1: "The enemy occupying Nanning is less than two divisions. They succeeded by exploiting our dispersed forces, but lack heavy weapons and supplies. Our army should gather superior forces and launch a counter-offensive quickly (before December 10) to defeat them and restore international transportation." Chiang decided on a counter-offensive on December 7. On the 8th, Bai conveyed the objective: "capturing Kunlun Pass and then recovering Nanning." By mid-December, assembly was complete. Chiang dispatched Chen Cheng and Li Jishen to supervise, and Zhang Fakui arrived in Qianjiang.   In the early stages, Guangxi lacked heavy armored forces for counterattacking beyond Guangxi clique troops. The fall of Kunlun Pass prompted Chongqing to deploy the reorganized Fifth Army and its armored corps for a strong attack. The Fifth Army was the main force at Kunlun Pass, with the National Revolutionary Army providing cover while launching a full-scale counterattack in Nanning.   To recapture Kunlun Pass and Nanning, Bai Chongxi dispatched approximately nine armies and twenty-seven divisions, totaling 300,000 troops: Xia Wei of the 16th Army Group, Ye Zhao of the 37th Army Group, Deng Longguang of the 35th Army Group, and Cai Tingkai of the 26th Army Group (31st, 5th, 64th, 46th, and 43rd Armies, etc.) to attack Kunlun Pass. The Japanese, with the Nakamura Brigade as main force and special forces, had strong fortifications. Xu Tingyao of the 38th Army Group, with Li Yannian of the 2nd Army, Gan Lichu of the 6th Army, Yao Chun of the 36th Army, and Fu Zhongfang of the 99th Army. The 5th Army, plus the 1st Honorary Division (Zheng Dongguo), New 22nd Division (Qiu Qingquan), and all armored, cavalry, artillery, and engineer regiments, arrived.   The Japanese forces consisted of the 5th Division (Lieutenant General Hitoshi Imamura; 9th Brigade under Major General Genichiro Ogawa; 21st Brigade under Major General Masao Nakamura; Taiwan Mixed Brigade under Major General Sadashiro Shiota), Marine Corps (over 70 warships), and Air Force (100 aircraft), totaling about 30,000. Later reinforcements: Imperial Guard Division and a brigade from the 18th Division. Total about 100,000, but only 45,000 fought. After a traitor reported over 100,000 Nationalist troops north of Kunlun Pass, Imamura dismissed it as "impossible." Higher Japanese ranks hoped to instigate rebellion by the Guangxi clique. On December 10, Imamura issued a telegram "Letter to Generals Li and Bai," expressing respect and stating the attack on Nanning was to cut off Chiang's lines, hoping for Japan-China cooperation. If insisted, the Japanese garrison would win. Finally: "The more than 4,200 brave soldiers who died in Nanning have been buried in Zhongshan Park and solemnly offered sacrifices. Please rest assured."   On December 15, Bai Chongxi took a decisive step in the escalating conflict by issuing the first counter-offensive order, setting the stage for a coordinated push against enemy positions. He organized the forces into three main route armies, with additional reserves held back for support.   The Northern Route Army, under Xu Tingyao's command, focused its efforts on Kunlun Pass. The 5th Army led the direct assault there, while the 92nd Division from the 99th Army skirted around Lingliwei to strike at Qitang, effectively flanking the pass and adding pressure from the side.   Meanwhile, the Western Route Army, led by Xia Wei, split into two columns to cover multiple fronts. The First Column, commanded by Zhou Zuhuang, targeted Gaofeng Pass in a bold advance. The Second Column, under Wei Yunsong, positioned itself at Suwei to block any reinforcements heading toward Nanning, cutting off potential enemy supply lines.   On the eastern flank, Cai Tingkai's Eastern Route Army aimed to disrupt key logistics. The 46th Army moved against Luwu and Lingshan, intent on severing the vital Yongqin Highway. At the same time, the 66th Army joined the assault on Kunlun Pass before pushing onward to Gula and Gantang. To bolster these efforts, the remaining two divisions of the 99th Army were kept in reserve, ready to reinforce wherever needed.   The very next day, on December 16, Du Yuming—now serving as army commander—gathered his officers for a critical conference within the 5th Army. There, they crafted a clever encirclement strategy dubbed "close the gate and fight the tiger," designed to trap and overwhelm the opposition. The plan's core involved the 200th Division, led by Dai Anlan, and the 1st Honorary Division under Zheng Dongguo launching the primary attack on Kunlun Pass. Flanking from the right, Qiu Qingquan's New 22nd Division would seize Wutang and Liutang, then turn to intercept any incoming reinforcements. On the left wing, Peng Bisheng commanded two regiments in a daring bypass of Gantang and Chang'an, aiming to strike at Qitang and Batang and seal off the enemy's retreat routes.   The enemy at Kunlun Pass was the Matsumoto Sozaburo Battalion of the 21st Brigade. Its 42nd and 21st Regiments were along Jiutang-Nanning. On December 16, Imamura ordered Major General Kawai Genshichi of the 9th Brigade to lead thousands in a surprise attack on Longzhou and Zhennan Pass, departing on the 17th.   At 8 p.m. on December 17, the Battle of Kunlun Pass began.   On December 18, Chinese forces began their attack and captured Kunlun Pass and Jiutang on the same day. On December 19, it captured Gaofeng Pass. On December 20, Gaofeng Pass, Jiutang, and Kunlun Pass fell into the hands of the Japanese army again. At dawn on December 18, the artillery of the 5th Army opened fire. After extension, the 200th and 1st Honorary Divisions attacked. Hundreds of Japanese planes bombed. By night, the 1st Honorary captured Fairy Mountain, Laomaoling, Wanfu Village, Luotang, and Hill 411; 200th captured Hills 653 and 600, taking Kunlun Pass. At noon on the 19th, massive Japanese air raid. Imamura dispatched the 21st Regiment under Colonel Miki Yoshinosuke, recapturing it. Positions were contested repeatedly. The New 22nd occupied Wutang and Liutang; Wutang recaptured by Japanese, but Liutang held, blocking reinforcements. When Imamura ordered Taiwan Mixed Brigade reinforcement, they were blocked at Liutang by Qiu Qingquan. Du Yuming ordered Zheng Dongguo to send Zheng Tingji's 3rd Regiment to encircle Jiutang from the right. They captured high ground west of Jiutang at night. On December 20, enemy at Kunlun Pass weakened, sending urgent reports. Imamura ordered Nakamura Masao with 42nd Regiment to reinforce, but blocked at Wutang for two days, reaching Qitang on the 22nd, blocked again. Nakamura was wounded on the 23rd morning. At 1:30 pm, Miki reported: "If the brigade cannot arrive before dusk, the front line will be difficult to secure."   Imamura ordered Colonel Lin Yixiong's 1st Regiment and Colonel Watanabe Nobuyoshi's 2nd Regiment of the Taiwan Mixed Brigade to reinforce, but blocked by 175th Division on Yongqin Road. Watanabe's regiment blocked at Luwu by 524th Regiment (Chao Wei), and after three days, couldn't pass. Watanabe was killed, remnants fled to Qin County. On the 20th, Imamura ordered the 9th Brigade's 3rd Battalion of Ito's unit back in 105 vehicles to reinforce.   The Japanese confirmed the attack and Imamura ordered Nakamura Detachment rescue. Over two weeks, encirclement and breakout battles occurred on the Nanning-Kunlun Pass highway.   On the 18th, the 170th Division launched the Battle of Gaofeng Pass, capturing a hill on the 19th but ambushed that night. On the 20th, the pass fell, retreating to Gewei. Bai inspected but no improvement; failed to capture Gaofeng Pass or block reinforcements. Ito's unit on Yonglong Road intercepted by 131st at Xichangwei. On the 22nd, Imamura sent two companies from Nanning, intercepted by 188th near Suwei. Ito's battalion besieged in Xichangwei for three days, spared because 131st avoided close combat. Under air cover, both broke through to Nanning on the 26th.   On November 21, Chiang was dissatisfied with Kunlun Pass progress, ordering: "If front-line troops and artillery fail to attack or complete tasks, they shall be punished for cowardice."   By the 23rd, two divisions of 5th Army had over 2,000 casualties; Japanese over 1,000. Six days yielded no results, with reinforcements arriving. Du changed tactics to concentrate forces, tightening encirclement.   On the 24th, Oikawa Detachment ordered back to Nanning, destroying captured materials and withdrawing from Longzhou and Zhennanguan. Bai learned some escaped, telegraphing Wei Yunsong: "If the second batch escapes, it affects the main force. The deputy commander-in-chief should be punished." Main force still escaped; local troops preserved strength, benefiting Japanese.   On the main position, Zheng Tingji spotted Japanese officers meeting and ordered fire, inflicting heavy casualties, requiring airdropped officers.   On the 25th, Second Regiment of First Division captured Luotang South Heights, annihilating over 200. From December 25, Fifth Army and 159th and 92nd Divisions occupied key high grounds. Fierce battle until December 31, capturing Kunlun Pass and Tianyin, killing Nakamura Masao, annihilating over 5,000.   Following the intense clashes at Kunlun Pass, the battle's toll on the Japanese forces became starkly evident in the weeks that followed. On January 19, just a month after the fighting peaked, the Japanese rushed in 3,389 fresh replacements to replenish their battered 5th Division. This influx was distributed unevenly: 1,848 went to the 21st Infantry Regiment and 814 to the 42nd, figures that likely corresponded directly to the number of dead and seriously wounded who had been evacuated back home—though those with minor injuries weren't factored into these counts. The ferocity of the engagement was further underscored by the capture of numerous Japanese strongholds, where Chinese forces found that every defender had been killed, leaving no survivors behind.   In many ways, this outcome represented a stunning annihilation for the Japanese, particularly the 21st Brigade, which was effectively wiped out. Key figures fell in the fray, including Brigade Commander Masao Nakamura, Acting Commander Sakata Genichi, Miki Yoshinosuke, along with various deputies and battalion commanders. The leadership losses were catastrophic: over 85% of officers above the squad leader level were killed. Japanese records themselves acknowledged more than 4,000 soldiers dead, painting a grim picture that their own war histories later described as "the darkest era for the army." On the Chinese side, the victory came at a heavy price, with over 10,000 casualties suffered, yet remarkably, the core officer corps remained largely intact, preserving command structure for future operations.   Zooming out to the broader theater in December 1939, the Japanese 5th Division and the Taiwan Mixed Brigade found themselves holding the line against an overwhelming force of more than 150,000 Nationalist troops. At the same time, the Japanese 21st Army was shifting its focus to Guangdong Province in preparation for Operation Weng Ying, while the Oikawa Detachment—primarily composed of the 11th Infantry Regiment—pushed forward to Longzhou. They captured Zhennanguan on November 21, securing valuable stocks of fuel and arms in the process. However, these stretched deployments and insufficient troop numbers left the Japanese without adequate reserves when encirclement loomed at Kunlun Pass. Ultimately, they were forced to abandon their offensive plans in Guangdong, pulling back to consolidate defenses around Nanning. Meanwhile, from their base in Chongqing, Chinese commanders had meticulously planned the recapture, turning the tide through careful strategy and sheer determination. Shocked, Japanese dispatched Vice Chief of Staff Sawada Shigeru to Guangzhou. On December 29, 21st Army sent staff to Nanning. Failed to change 21st Brigade's defeat. Imamura planned personal charge for revenge on January 1, but Ando ordered holding Nanning for reinforcements: "The 21st Army is transferring powerful force to annihilate enemy. 5th Division secure Nanning and key locations."   After capturing Kunlun Pass and annihilating two regiments of 21st Brigade, 5th Army thought to recapture Nanning. Remaining 21st Brigade and Taiwan regiments between Jiutang and Batang. At noon January 1, 1940, Oikawa's thousands arrived at Batang; Imamura ordered Oikawa replace killed Sakata. First battle on Hill 441. 1st Division held north side; Japanese south. On January 1, Japanese bombed and attacked; 1st Division reduced to hundred but held. At dawn 2nd, counterattack all day, no progress. On 3rd, Du mobilized 200th and part New 22nd; brutal fighting, heavy casualties. At nightfall, Japanese retreated to Jiutang. On 4th, Japanese abandoned Jiutang to Batang. New 22nd moved into Jiutang. 5th Army attacked Batang; by 12th, no progress. Exhausted with heavy casualties, 5th Army ordered to Silong for rest. Mission transferred to 36th Army. 5th Army withdrew.   On January 7, Chiang flew to Guilin, visiting Qianjiang on 10th to discuss plans with Bai, Chen, Zhang, Xu, Lin. Bai proposed offensive with new armies to recapture Nanning. Chiang approved. On 11th, as Bai issued orders, Chiang overturned, changing to defensive. Japanese gained time for counter-offensive.   To salvage defeat, Japanese transferred 18th Division and Konoye Brigade from Guangdong. Combined with existing, formed 22nd Corps under Seiichi Kuno, under South China Front Army commanded by Reikichi Ando, preparing counteroffensive.   On January 25, a brigade from the Japanese 18th Division and elements of the 15th Division attacked frontally along Yongbin Road, while Konoye Brigade flanked toward Guizhou via Yongyong Road, in Binyang Campaign. Konoye crossed at Tingziwei, then Yongchun County, via Gantang, Luwei, Gula, Wuling to Binyang, cutting rear. Bai Chongxi rushed 175th Division of 46th Army north to tail Konoye. After reinforcements, 21st Army launched offensive to drive and encircle south of Binyang; accumulated supplies in Nanning. On January 22, 18th and Konoye reached attack points. 38th Army Group HQ in Binyang bombed, communications cut, independent combat.   On January 28, Japanese launched offensive (Binyang Operation). On February 3, 41st Infantry of 5th Division occupied Kunlun Pass. On February 4, Ando reached captured Binyang. Nationalists lost Kunlun Pass, lines collapsed, many encircled. Battle ended with withdrawal; February 13, Japanese withdrew to Nanning, lines stalemated.   In the wake of the Binyang clashes, the 18th Division was indeed shifted to Guangzhou. Japanese records from January 28 to February 13 painted a picture of their spoils: they claimed to have captured 19 tanks, 5 light armored vehicles, 30 automobiles, 20 field or mountain guns, 13 rapid-fire guns, and 41 mortars. Additionally, they reported counting 27,041 Chinese bodies on the battlefield and taking 1,167 prisoners. The Chinese forces, for their part, regrouped with their main strength positioned east of the Yongqin Highway, while some elements maneuvered west to harass Japanese rear lines and coordinate actions from the north bank.   On February 21, 1940, Chiang arrived in Liuzhou, residing at Yangjiao Mountain. From February 22, he convened over 100 generals for a four-day Liuzhou Military Conference to review Guinan operations. Chiang demoted Bai Chongxi for poor supervision and Chen Cheng for poor guidance from first- to second-class generals. He also punished and rewarded other senior officers. The 46th Army and 175th Division were commended for discipline. On February 26, Fourth War Zone Commander Zhang Fakui announced: "No need for counterattack on Nanning currently." The entire Guinan Campaign ended.   The defeat embarrassed Chongqing; not only disrupted Guangxi-Vietnam traffic, but massive effort ended in rout. Pre-battle, Guilin Headquarters misjudged Japanese intentions; during, both Guangxi and Huangpu clique leaders showed poor performance, infuriating Chiang. Post-battle punishments were unprecedented in the war.   I would like to take this time to remind you all that this podcast is only made possible through the efforts of Kings and Generals over at Youtube. Please go subscribe to Kings and Generals over at Youtube and to continue helping us produce this content please check out www.patreon.com/kingsandgenerals. If you are still hungry after that, give my personal channel a look over at The Pacific War Channel at Youtube, it would mean a lot to me. In November 1939, Japanese forces, including the 5th Division and Taiwan Brigade, landed at Qinzhou Bay, captured Nanning, and advanced to Kunlun Pass. Chinese troops, under Bai Chongxi and reinforced by the elite 5th Army, launched fierce counteroffensives, recapturing Kunlun Pass in December with heavy casualties. 

1. U.S.–Iran Conflict Escalation Negotiations with Iran failed after roughly 20 hours because Iran refused to abandon its nuclear ambitions. In response, President Trump is described as ordering a U.S. naval blockade of the Strait of Hormuz, framing it as a decisive measure to prevent Iran from obtaining nuclear weapons and to stop what is portrayed as Iranian “extortion” of global shipping. The blockade is economic warfare, aimed at cutting off Iran’s oil exports, which are depicted as the backbone of the Iranian economy. 2. Strategic and Economic Impact of the Strait of Hormuz Shutting down the Strait is portrayed as: Crippling Iran financially, by halting oil exports. Pressuring China, described as the primary buyer of Iranian oil. Stress-testing Europe, which is characterized as reluctant to confront Iran directly but still vulnerable to energy shocks. The U.S. control of global sea lanes (“Pax Americana”) gives America leverage over international commerce. 3. Trump Administration’s Policy Framing The Trump approach is: Having clear “red lines”: no uranium enrichment, no nuclear weapons, open shipping lanes, and an end to terror financing. Using maximum pressure before full-scale war, with the blockade portrayed as an intermediate step between diplomacy and total military escalation. Success is defined primarily as preventing Iran from acquiring nuclear weapons, with regime collapse described as a desirable but secondary outcome. 4. Criticism of Prior U.S. Policy The Biden administration is heavily criticized for: Not enforcing existing sanctions, allowing Iranian oil exports to rebound. Enabling the growth of a so‑called “ghost fleet” transporting Iranian oil, mainly to China. The argument presented is that this enforcement lapse indirectly funded terrorist groups aligned with Iran. 5. Internal U.S. Political Commentary Democrats are: Opposing or undermining U.S. military actions for partisan reasons. Failing to support allies and projecting weakness internationally. Western Europe is depicted negatively, while Eastern Europe and Middle Eastern allies are portrayed as more supportive of U.S. actions. 6. Eric Swalwell Allegations (“Bombshell”) A major secondary storyline focuses on Congressman Eric Swalwell: Multiple allegations of sexual misconduct, including assault, by former staffers. A criminal investigation reportedly opened in New York. Swalwell withdrawing from the California governor’s race is framed as: A political calculation by Democrats to limit electoral damage. Evidence of alleged hypocrisy, with claims the party protected him until it became politically inconvenient. Please Hit Subscribe to this podcast Right Now. Also Please Subscribe to the 47 Morning Update with Ben Ferguson and The Ben Ferguson Show Podcast Wherever You get You're Podcasts. And don't forget to follow the show on Social Media so you never miss a moment! Thanks for Listening YouTube: https://www.youtube.com/@VerdictwithTedCruz/ Facebook: https://www.facebook.com/verdictwithtedcruz X: https://x.com/tedcruz X: https://x.com/benfergusonshowYouTube: https://www.youtube.com/@VerdictwithTedCruzSee omnystudio.com/listener for privacy information.