Podcasts about Slight

But will it hold with Ranked Choice Voting?See omnystudio.com/listener for privacy information.

Hour 2 - After local and national news, we get the Storm Track 3 Forecast. Meteorologist Ronelle Williams says a 30% chance for showers and/or storms tonight.

To get your dose of daily business news, tune into Mint Top of the Morning on Mint Podcasts available on all audio streaming platforms. https://open.spotify.com/show/7x8Nv1RlOKyMV5IftIJwP1?si=bf5ecbaedd8f4ddc This is Nelson John, and I'll bring you the top business and tech stories, let's get started.  Market Holiday Alert Heads up, traders! Indian stock markets will be closed on April 14 (Ambedkar Jayanti) and April 18 (Good Friday). Plan your trades accordingly.   US-China Trade War Reloaded The tariff tussle is back on. U.S. Commerce Secretary Howard Lutnick announced new sector-specific tariffs on smartphones, semiconductors, and pharma, likely within a month. “We can't rely on China for essentials,” he told ABC News, signaling a push to bring manufacturing home. This comes after Trump temporarily exempted some Chinese electronics from a 145% retaliatory tariff, a move that briefly helped companies like Apple, which had lost $640 billion in market value. With fresh tariffs looming, China is urging a rollback, but the tech and pharma trade war may just be heating up again. Summer Surge: Indians Flock Abroad India's scorching summer is sending travelers packing. Outbound travel is up 15–20% year-on-year, say visa providers. Top destinations: Europe, US, Canada, and Southeast Asia. “Plan early,” urges VFS Global, as visa demand jumps 11% since 2024. Peak season might stretch into October, and agencies are leaning on AI to speed up processing. From leisure to study and work, Indians are going global—and not looking back. Cleartrip's Costly Flight Plan Despite MS Dhoni's pilot pitch, Cleartrip's financials hit turbulence. In FY24, the travel portal spent ₹988 crore to earn just ₹97 crore, racking up losses over ₹800 crore—half of it on discounts. Flipkart's 2021 acquisition hasn't paid off, as rivals like MakeMyTrip and Ixigo fly ahead. With new growth head Manjari Singhal, Cleartrip is eyeing hotels, corporate travel, and cabs. But experts say: “Discounts won't fly forever.” Will Cleartrip course-correct or stay grounded? Green Card Setback for Indians The May 2025 US Visa Bulletin brings bad news—EB-5 visas for Indians retrogressed by six months to May 1, 2019, increasing wait times. Other categories remain stuck: EB-2: Jan 2013 EB-3: Slight move to April 2013 EB-4: Still unavailable Blame it on high demand, annual caps, and per-country limits. Experts advise exploring faster tracks like EB1 or NIW—but for many, the American dream is on pause.  HDFC Bets Big on Small-Town Homes HDFC Capital is investing ₹1,500 crore in 18 residential projects with Eldeco Group across Tier-II and III cities. Targeting markets like Panipat, Ludhiana, Rishikesh, and Kasauli, the platform eyes ₹11,000 crore in revenue from 10 million sq ft of new housing. “We're bullish on towns near metros,” says CEO Vipul Roongta, citing rising infrastructure and housing demand. Backed by its $4.2 billion housing fund, HDFC is betting that India's real estate boom is heading beyond the metros.

Your daily news in under three minutes. At Al Jazeera Podcasts, we want to hear from you, our listeners. So, please head to https://www.aljazeera.com/survey and tell us your thoughts about this show and other Al Jazeera podcasts. It only takes a few minutes! Connect with us: @AJEPodcasts on Twitter, Instagram, Facebook, Threads and YouTube

M&A News this morning with an announcement that Wesdome Gold Mines will acquire all of the issued and outstanding common shares of Angus Gold. Defiance Silver has entered into a non-binding letter of intent to acquire Green Earth Metals which is a private company with assets in Mexico. FPX Nickel has extended the company's Global Generative Exploration Alliance with JOGMEC. Kenorland Minerals has obtained the approval from the TSX Venture Exchange for a new normal course issuer bid. This episode of Mining Stock Daily is brought to you by... Vizsla Silver is focused on becoming one of the world's largest single-asset silver producers through the exploration and development of the 100% owned Panuco-Copala silver-gold district in Sinaloa, Mexico. The company consolidated this historic district in 2019 and has now completed over 325,000 meters of drilling. The company has the world's largest, undeveloped high-grade silver resource. Learn more at⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠https://vizslasilvercorp.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Calibre Mining is a Canadian-listed, Americas focused, growing mid-tier gold producer with a strong pipeline of development and exploration opportunities across Newfoundland & Labrador in Canada, Nevada and Washington in the USA, and Nicaragua. With a strong balance sheet, a proven management team, strong operating cash flow, accretive development projects and district-scale exploration opportunities Calibre will unlock significant value.⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.calibremining.com/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Integra is a growing precious metals producer in the Great Basin of the Western United States. Integra is focused on demonstrating profitability and operational excellence at its principal operating asset, the Florida Canyon Mine, located in Nevada. In addition, Integra is committed to advancing its flagship development-stage heap leach projects: the past producing DeLamar Project located in southwestern Idaho, and the Nevada North Project located in western Nevada. Learn more about the business and their high industry standards over at integraresources.com

Shiur given by Rabbi Zev Leff as a guest speaker in Yeshiva. Introduction by Bezalel Rudinsky. Shiur recorded in Yeshivas Ohr Reuven, Monsey, NY. (Slight recording issue in the introduction.)

The Phantoms are back in Youngstown after getting 3 out of 4 wins on a long Western Conference swing. We welcome Assistant Captain Conner de Haro back to the show, and for the first time ever, we recommend that you stick around to the very end of this episode!Send us a textMerch Store Official WebsiteFacebook This recording is the sole view of the members of the Dump & Chase Podcast. This is a non-commercial fan production. We are not affiliated with or compensated by the Youngstown Phantoms, the United States Hockey League, or any league, club, or team. © 2025 Dump & Chase Podcast. All Rights Reserved

The cold weather is still here but a slight warmup is coming this week. Meteorologist Tony Ansuini has the forecast.

An upcoming Bank of Japan "tankan" quarterly survey report is seen showing a slight deterioration in business sentiment among major Japanese manufacturers, according to estimates by private think tanks.

New West Radio ProductionsEmail: newwestradioproductions@gmail.com.Become a supporter of this podcast: https://www.spreaker.com/podcast/new-west-radio-productions--3288246/support.

Hour 2 - Currently the forecast does not have much of a chance for storms in Wichita Wednesday, around a 30% chance. Steve and Ted get the KSN Storm Track 3 Forecast from Kansas Today Meteorologist Ronelle Williams.

In this special Peter (Retrogamepapa) together with Max and Michiel discuss the grading of video games. Why do people do it? Why do these companies exist? Slight spoiler: Max has a different opinion than Michiel and Peter have on grading video games...Next to discussing graded games, they also talk a bit about owning and/or keeping games sealed. This is something which is almost inherently linked to grading video games. Is there actually a difference between the two in regards to why? For which reasons do people keep games sealed? So many questions... It's all talked about in this side-quest!

BRACKET SEASON! After some sloppily presented Longhorn football and basketball talk + personal beefs, Jason, Nick and Dave B unveil the matchups for our Movie/TV Villain Alternative Bracket.Win $100 Pluckers gift card by playing along https://woobox.com/hnxemuThe contest has limited space and entries close Thursday at 5pm. So don't delay!Win $50 Pluckers gift card by playing our actual basketball bracket https://fantasy.espn.com/tc/sharer?challengeId=257&from=espn&context=GROUP_INVITE&edition=espn-en&groupId=c10de33b-0f05-46ae-b942-7a0c6f34c45b(or search Jason Duck and Friends. Yes, duck. ESPN doesn't like my name)Bonus episodes available at patreon.com/jasondick or https://creators.spotify.com/pod/show/jason-dick/subscribe

Which of the two following findings would be anticipated in the normal fundoscopic exam of a healthy 40-year-old woman who is normotensive, generally in good health and without ocular complaint?  A. Arteriovenous nickingB. Optic cup to disc ratio < .0.5C. Retinal arteries are brighter and narrower than veins  D. Slight bulging of the optic diskVisit fhea.com to learn more!

In this episode, we break down what makes a good store of value—scarcity, durability, security, portability, and inflation resistance. Gold has served this role for centuries, but its heavy, confiscatable, and slowly inflating supply limits its effectiveness. Fiat money, while convenient, loses value over time due to inflation. Bitcoin, however, offers absolute scarcity (21M cap), instant portability, and seizure resistance, making it a superior long-term store of value despite short-term volatility. Is Bitcoin the future of wealth preservation? Tune in to find out.Get intouch with Myles at mylesdhillon@gmail.com

Episode: Weekly Crypto, Blockchain & AI UpdateDate & Time: 10:00 am GST, 13th March 2025Hosts:Markose Chentittha (Oort Foundation + Society X)RA George (Blockchain DXB + Bitcoin DXB)In this week's LinkedIn Live episode of Blockchain DXB & Society X - Unfiltered Chat, hosts Markose Chentittha and RA George dive deep into the latest crypto, blockchain, and AI developments. From the recent Pi Network pump to new geopolitical dynamics and upcoming regulatory changes, the hosts discuss crucial updates and analyze their impact on the market.Surge in Pi Network's value over the last 24 hours.Brief history of the Pi Network and its controversy.Debate: Scam or legitimate project?Discussion on the role of Pi Network within DePin and whether it holds OG status.Inflation down to 2.8% (Source: BLS.gov).Slight price uptick observed despite inflation reduction.Real-time information and data-driven decisions discussed, including the possibility of uploading such data on an open blockchain.Hosted by Jerome Powell.Potential outcomes:30-day ceasefire proposed in Jeddah, contingent on Russia's agreement (Source).Discussed the potential impact on Bitcoin and crypto prices.Increased geopolitical stability could reduce sanctions and positively affect crypto adoption.Discussion on Russia's evolving crypto policies and the Bank of Russia's crypto investment portfolio for HNWI.Introduced by Senator Bill Hagerty to regulate US dollar-pegged stablecoins.Tether & Circle identified as the only stablecoins with a market cap over $10B.Provisions include AML measures, liquidity requirements, and transparency mandates.Dubai's VARA stance: No to algorithmically backed stablecoins (via LinkedIn post by CEO Mathe White).Insights from both hosts:Initiative led by the Democratic Party to include Bitcoin in national reserves.Potential launch of a won-backed stablecoin.Reduction in crypto regulations discussed. (Source)Movement of BTC to a new wallet as identified by Arkham Intelligence (Transaction Link).Repayment plan postponed to 31st October 2025.New address not linked to exchanges, raising questions about future movements.DeFi TVL: Down to $88.24 billion.Market Cap Updates:DEX Update:Stablecoin Event: Exploring stablecoins' history, risks, and future.How to Start a Podcast Event: Essential insights for beginners.Central Bank Digital Currency Event: Discussing CBDCs and their future impact.Tune in next week for more updates on crypto, blockchain, and AI, as well as insights into market trends and emerging technologies. Don't forget to subscribe to Blockchain DXB for daily updates and follow us on LinkedIn to catch future live sessions.To support this channel:

This week, Colt, Pat and Wenzel are talking business. Specifically the loss of one of Earth's greatest heroes: Business Baby. They also talk about Invincible, Demon Slayer, My Hero Spin-Off Vigilantes manga, recent theater watches and a little Split Fiction. Slight spoilers ahead so time stamps will be available below! ----------------------------------- Time Stamps: Invincible Show Talk: 2 min to 35 min 7 sec Demon Slayer Anime Talk: 35 min 7 sec to 1 hr More Invincible Discourse: 1 hr 5 min to 1 hr 13 min Pat's Piss Break: 1 hr 13 min 15 sec to 1 hr 16 min Colt & Wenzel's Third Triple Theater Feature for 2025: 1 hr 16 min 8 sec to 1 hr 50 min My Hero Vigilantes Manga Talk: 1 hr 50 min 25 sec to 2 hr 4 min 15 sec Pat's Gambling Addiction: 2 hr 4 min 15 sec to 2 hr 16 min 50 sec Split Fiction Talk: 2 hr 16 min 50 sec to 2 hr 24 min 50 sec ----------------------------------- Episode image created by Wenzel ----------------------------------- Catch up on all of Season 8's episodes here: soundcloud.com/aychpodcast/sets/aych-season-8-2024 ----------------------------------- Check out the entire AYCH Podcast Network! ► Caging Greatness - Nicolas Cage movie review Podcast podcasts.apple.com/us/podcast/cagi…ss/id1553303334 Want even more AYCH shows? Check out our full catalog playlists! soundcloud.com/aychpodcast/sets ►►► Backlog BoyZ: Video Game Discussion Podcast! ►►► The Instruction Booklet: Video Game History Podcast! ----------------------------------- Twitch/Podcast Archive YT: www.youtube.com/@AYCHPodcast If you like what we're doing here, don't forget to leave us a review! You can also follow us on all of our social media below and tell us how we're doing: -- Bluesky: @aychpodcast.bsky.social -- Instagram: @aychpodcast -- TikTok: @aychpodcast -- Twitch: AllYouCanHear Leave us some suggestions in our Suggestion Box as well! goo.gl/forms/AHetCWQ2m7tHDigg1

Slight of hand is not exactly taught by booksAlso, I can almost guarantee that you read the title backwards lol

The boys are finally back!  Slight delays were recently afoot but the February episode is upon us (although it's dropping in March).  This marks the final episode of season 7.  Chris brought a solidly made, surprising and interesting film called Sator that everybody should see.  The boys also give the listeners their top 5 watches of 2024 with honorable mentions.  So that being said, go on and grab those leftover beverages from Valentine's Day, or crack open those brews you're saving for St. Patty's Day, and get ready for a fun episode!  Thanks again for tuning in!!!

A terrific satire on the early Warner Bros. gangster films that Edward G. Robinson made popular, about a bootlegger who decides to go legit once prohibition ends. Directed by Lloyd Bacon.

NOTE: This was recorded last week! Episode 292 of No One's Ready For Wrestling discusses NXT Vengeance Day & AEW Grand Slam Australia. AEW returning to Australia next year and hopefully they learn how to properly promote their show and not screw the fans. AEW Double Or Nothing location revealed. MJF & Hangman Page put on an excellent segment on Dynamite. AJ Styles defends Road Dogg after it was revealed that he's the co lead writer for SmackDown. Asuka revealed that she had her social media account hacked and thankfully she got it back. Roster reveal for WWE 2K25 and my thoughts. The Women's Division is reportedly frustrated with the booking and what WWE needs to do to fix this situation?! Moose makes a shocking appearance on NXT and issues a challenge to Oba Femi. Ricky Starks officially signs his contract with WWE and now goes by the name Ricky Saints! Why I don't have an issue with the name change and Ricky reveals that "veterans" stuck their nose in his creative vision.All this & so much more RIGHT HERE on No One's Ready For Wrestling!

Pope Francis has had a ‘slight improvement' overnight - but remains in critical condition . We get the lates on the health of Pope Francis with Gerard O'Connell, Vatican Affairs Correspondent and author "The Election of Pope Francis: An Inside Account of the Conclave that changed history".

A man is acquitted of murder on perjured testimony and hires Wolfe to locate the real killer.Original Air Date: April 6, 1951Starring: Sidney Greenstreet as Nero Wolfe; Harry Bartel as Archie Goodwin; William Johnstone; Mary Lansing; Jeanne Bates; Barney Phillips; Paul Marion; Ken PetersSupport the show monthly at https://patreon.greatdetectives.netPatreon Supporter of the Day: Alex, Patreon Supporter since August 2020Support the show on a one-time basis at http://support.greatdetectives.net.Mail a donation to: Adam Graham, PO Box 15913, Boise, Idaho 83715Take the listener survey at http://survey.greatdetectives.netGive us a call at 208-991-4783Follow us on Instagram at http://instagram.com/greatdetectivesFollow us on Twitter @radiodetectivesJoin us again tomorrow for another detective drama from the Golden Age of Radio.

Last time we spoke about the liberation of Bataan and Corregidor. The Shimbu Group's commander launched a coordinated raid on northern Manila, aiming to weaken enemy defenses. Despite heavy casualties, the Allies captured key locations, including Nichols Field. Meanwhile, General Chase's 38th Division overcame strong Japanese defenses at ZigZag Pass, while General Hall's forces secured Bataan. Plans for an airborne assault on Corregidor were set for February 16, leveraging surprise against the outnumbered Japanese garrison. American forces launched the strategic attack on Corregidor, dropping paratroopers from the 503rd Regiment. Despite facing sporadic fire, they secured key positions. The following days saw intense skirmishes as the 3rd Battalion, 34th Regiment landed and established a foothold. Over eight days, they repelled numerous Japanese counterattacks, inflicting heavy casualties. By February 26, organized resistance crumbled, leading to the island's capture. Meanwhile, in Manila, American troops advanced, clearing buildings and securing the city, inching closer to victory in the Philippines. This episode is the Invasion of Iwo Jima Welcome to the Pacific War Podcast Week by Week, 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 world war two? Kings and Generals have an assortment of episodes on world war two 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 you can find a few videos all the way from the Opium Wars of the 1800's until the end of the Pacific War in 1945.    A few weeks ago we spoke about Operation Detachment. Admirals Nimitz and Spruance were planning an invasion of Iwo Jima with General Schmidt's 5th Amphibious Corps. During a thorough campaign of preliminary air and naval bombardment against the Volcano Islands, the 4th and 5th Marine Divisions, along with other Corps units, were loading at Hawaii between December 25 and January 25. Once training and loading were complete, Admiral Turner's Task Force 51 and Admiral Hill's Task Force 53 left Pearl Harbor on January 27, initially heading toward Saipan. By February 12, Admiral Spruance's 5th Fleet had gathered in the Marianas and was prepared to sail for Iwo Jima. Additionally, Admiral Mitscher's Task Force 58 had departed Ulithi to conduct a series of supporting air strikes over and around Tokyo, known as Operation Jamboree. Task Force 58 sortied from Ulithi 10 February and shaped a course eastward of the Marianas and Bonins. On the 12th, the air groups rehearsed with the 3rd Marine Division on Tinian. Two days later the task force fueled at sea from one of Admiral Beary's replenishment groups. Everything possible was done to guard against detection. Measures included radio deception, scouting by Pacific Fleet submarines to dispose of any picket vessels there might be en route, scouting by B-29s and Navy Liberators from the Marianas to clear the air. On the 15th a scouting line of five destroyers ranged ahead of the carriers, and antisubmarine air patrol was set up. At 1900 a high-speed run-in began towards launching positions, where the carriers arrived at dawn 16 February. Thanks to these precautions, and to thick weather most of the way, they arrived undetected. General LeMay's 21st Bomber Command, which was being reinforced by the 313th and 314th Bombardment Wings, would also assist Detachment with several strikes against Japan. Following some unremarkable high-altitude daytime missions in late January, 129 B-29s from the 73rd and 313th Bombardment Wings targeted Kobe on February 3, using a mix of incendiaries and fragmentation bombs. This attack caused significant damage to the urban area and local war production, resulting in the loss of 2 bombers and damage to 35 others. Subsequently, on February 10, a precision strike was launched against Ota's Nakajima aircraft factory, with 84 out of 118 dispatched B-29s successfully bombing the site. However, only 14% of the bombs hit the target, leading to the loss of 12 bombers and damage to 29. Nearly one-third of the factory buildings sustained damage, primarily from the incendiaries combined with high-explosive bombs. Five days later, LeMay dispatched 117 B-29 bombers to target Mitsubishi's engine works in Nagoya. However, an unexpected cold front resulted in only 33 bombers reaching the target area, yielding lackluster results. Meanwhile, after conducting some assault rehearsals, Spruance's amphibious support forces and tractor groups set sail for Iwo Jima on February 14, followed two days later by Turner's main assault convoy. At the same time, the reserve 3rd Marine Division continued loading at Guam, with its 21st Marines departing for Iwo Jima on February 16, followed by the main body of the division the next day. On the morning of February 16, Admiral Blandy's Amphibious Support Force arrived off Iwo Jima and promptly commenced the final preliminary bombardment and minesweeping operations, although inclement weather hindered these efforts. However, the next day, Task Force 52 successfully carried out these missions; beach reconnaissance by UDTs faced heavy mortar fire, resulting in the sinking of one LCI gunboat, damage to eleven others, and casualties of 44 killed and 152 wounded. Despite this, the frogmen encountered no obstacles on the beaches and managed to create accurate maps of the approaches. Meanwhile, by February 16, Mitscher's carriers had quietly moved to a position 60 miles off the coast of Honshu, launching extensive fighter sweeps against airfields in Tokyo Bay and bombing raids on aircraft frame and engine plants in the Tokyo area.  About 100 Japanese fighters attacked Admiral Davison's planes as they crossed the coast and about 40 of them were shot down. American pilots found the Japanese on the whole reluctant to engage; Admiral Mitscher had correctly told his pilots, "He is probably more afraid of you than you are of him". In fact the IJAAF 10th Hiko Shidan immediately ordered an IJAAF night-fighter group and all “second-class” personnel to take cover, while all aircraft not intercepting were ordered to be dispersed, fuel tanks drained, and ammunition unloaded. In contrast, American pilots reported Tokyo antiaircraft fire “the most accurate and intense yet encountered.” By nightfall, Rear-Admiral Matthias Gardner's night-flying carrier group conducted a sweep of night fighters to cover the enemy airfields at dusk. This operation was repeated the following morning, but poor weather ultimately forced the carriers to retreat toward Iwo Jima. Despite this, significant damage was inflicted on aircraft frame and engine facilities, with 10 vessels sunk, including the unfinished escort carrier Yamashio Maru. A total of 531 aircraft were reported destroyed, at the expense of losing 88 planes and damaging two destroyers. On February 18, after the enemy battery camouflage had been obliterated during the previous two days of bombardment. This revealed batteries not previously known to exist, the island's defenses were for the first time properly revealed; and formidable they were indeed. Fortunately for the Americans, the support of UDTs with LCI gunboats had convinced General Kuribayashi that the main landing had started, and to repel it he unmasked batteries that would have caused very heavy casualties on D-day had they not been discovered two days before. This was the only serious mistake made by the Japanese general in his defensive tactics, which won the rueful admiration of his enemies. Blandy opted to focus on the immediate area and flanks of the eastern beaches. Heavy ships moved closer to 2,500 yards to deliver concentrated direct fire on all targets. Consequently, bombardment ships provided continuous direct fire throughout the day, effectively dismantling enemy defenses. However, during the night, the Japanese launched a minor raid that caused significant damage to the destroyer minesweeper Gamble and the destroyer escort Blessman. At 06:00 on February 19, Turner's main force arrived off Iwo Jima and began maneuvering into final positions. Simultaneously, Admiral Rodgers' warships executed the last pre-landing bombardment, coordinated with air strikes from Mitscher's carriers. Between 08:25 and 08:55, as the first wave crossed the line of departure and advanced toward the shore under the protective rocket fire of gunboats, shells fell heavily on Iwo Jima, marking the most intense pre-landing bombardment of World War II. At 08:57, as the leading armored amtracs approached their targets, naval gunfire shifted inland and to the flanks. The LVTs of the first wave touched down on Iwo Jima at 09:02 and began moving forward through the high terraces of soft black volcanic ash, engaging inland targets from the water to support subsequent landings. Three minutes later, the Marines of the 4th and 5th Divisions started landing side by side on the Green, Red, Yellow, and Blue beaches. The assault infantry battalions of the Landing Force received assistance throughout D-Day from all the supporting arms available to the Amphibious Support Force. Carrier pilots of Task Force 58 and the escort carriers of Task Force 52 flew missions all day as airborne observers and spotters maintained constant vigilance over the target. Including pre-H-Hour strikes, 606 support aircraft flew 26 missions on February 19 and dropped 274500 pounds of bombs. These planes also fired 2254 rockets into the island defenses and dropped over a hundred napalm bombs. Air and naval gunfire liaison teams remained in communication with both air and sea supporting units through the hectic hours that followed the beach assault. Naval rifles from 5- to 16-inch caliber pounded enemy positions in response to Marine requests. Gunfire support vessels engaged enemy artillery that covered landing areas from high ground to the north, and concentrated on concealed Japanese mortars that shelled landing areas with deadly effect. The units quickly reorganized and began their advance inland, facing only light resistance, although their progress was hampered by the sandy terrain. General Kuribayashi's forces, however, had been waiting in well-fortified underground positions as planned, emerging only after the bombardment ceased to unleash a barrage of machine-gun, rifle, and mortar fire on the advancing troops. As the initial waves of Marines struggled to advance, congestion along the shore became increasingly critical, while the full force of the Japanese defenders was unleashed shortly after 10:00. By 10:30, elements from all eight assault battalions had landed on the island, successfully bringing ashore about 6,000 men and bulldozers that were clearing paths for tank deployment. On the far left flank, Colonel Harry Liversedge's 28th Marines, having landed on Green Beach, initiated a rapid advance across the half-mile isthmus below Mount Suribachi to isolate this crucial position. The attack unfolded in such a way that some units were delayed while others managed to break through and continue westward despite suffering heavy casualties, ultimately crossing the island while the bypassed enemy was being dealt with. By midday, the reserve 3rd Battalion and tanks landed under heavy fire to join the afternoon assault on Suribachi, but intense enemy fire hindered their progress to the assault positions. Consequently, the 2nd Battalion launched an attack on its own, gaining only 150 yards before retreating to regroup with the 3rd Battalion for the night. At the same time, Colonel Thomas Wornham's 27th Marines had landed on the Red Beaches, making swift progress inland despite increasing casualties and bypassing numerous enemy positions. By 11:30, Company A was moving across the southern end of Airfield No. 1, establishing a presence along the western edge while other units continued to advance past the airfield. The 1st Battalion launched an attack on the airfield with tank support but faced strong enemy resistance, resulting in minimal gains. Meanwhile, the 2nd Battalion pushed westward and reached the cliffs overlooking the western coast. Additionally, the reserve 3rd Battalion landed and began clearing bypassed positions, while the artillery units from the 13th Marines and General Rockey's reserve 26th Marines also arrived in the afternoon as the 27th and 28th Marines solidified their positions. By nightfall, although the 5th Marine Division was still a considerable distance from the O-1 Line, it had established a firm foothold on the island, with Mount Suribachi isolated and portions of the airfield under their control. To the east, General Cates' 4th Marine Division also landed successfully, with Colonel Walter Wensinger's 23rd Marines coming ashore at the Yellow Beaches and Colonel John Lanigan's 25th Marines landing on Blue Beach 1 and the southern part of Blue Beach 2. The two regiments began their advance inland, hindered by intense enemy fire but managing to gain between 400 and 600 yards by midday. As tanks were being deployed, the 3rd Battalion of the 25th Marines moved to the right to clear the remaining area of Beach Blue 2 and encircle the threatening quarry zone. At this stage, as the assault battalions continued their advance, Wensinger and Lanigan deployed their reserve battalions to cover the gaps in their attack lines. With the support of tanks that had finally reached the front, the 23rd Marines advanced towards Airfield No. 1 and successfully captured its outskirts. Meanwhile, the 25th Marines initiated a coordinated assault, with the 3rd Battalion advancing about 200 yards along the beach to secure the problematic quarry, while the other two battalions moved north to seize the high ground to the northwest of the quarry. By the end of the day, Cates had also landed half of the artillery from the 14th Marines, along with his reserve 24th Marines, which began to relieve some of the frontline units from both assault regiments. Although the penetration by the 4th Marine Division was not as extensive as intended, by nightfall, the front lines included the eastern edge of the airfield and extended sufficiently inland from the Blue Beaches to ensure the beachhead could be held successfully. The Marines, forced to advance across open terrain while enduring intense fire from well-concealed positions that were difficult to target, fell significantly short of the O-1 objective. Nonetheless, by the end of the day, six Marine regiments, an equal number of artillery battalions, and two tank battalions had landed and were positioned to defend the narrow beachhead against a potential night counterattack.  Throughout this first day, the situation on the beaches prevented landing of any but the highest priority "hot cargo." This consisted of ammunition, rations, water, and signal equipment brought to the beach in LCVPs and LCMs. Shore party teams, working under extremely adverse conditions without sufficient trucks and other heavy equipment, could do little more than stack the supplies on the beach above the high water mark. LVTs and weasels made trips from the beach dumps inland carrying these supplies to the troops and returned bearing wounded men. The busy amtracs also made nonstop trips from LSTs, ferrying critically needed items direct to Marines on the front lines. Most of the transports and other vessels of the task force retired from the island at nightfall, but some command ships, preloaded LSTs, and hospital LSTs remained behind. Emergency items, especially 81mm mortar ammunition, were brought in during the night, but actually very little unloading was accomplished and many of the wounded spent this night on the beach because they could not be evacuated. Some progress was made cutting exits through the terrace and clearing mines, but enemy fire and the shortage of equipment limited this activity. Despite this, the Japanese did not launch any large-scale assaults, although their mortars and artillery relentlessly bombarded Marine lines along the front throughout the night. Consequently, Allied casualties on this first day totaled 548 killed and 1,755 wounded. On February 20, the goal was for the 28th Marines to take Mount Suribachi while other units advanced north to capture the two airfields. Initially, in the south, after a coordinated air and naval bombardment, Liversedge launched another assault on the volcano but managed to gain only 75 yards by midday. During the forenoon, Marines gained only 50-70 yards. Aircraft and ships pounded Japanese positions and the 3d Battalion, 13th Marines fired mission after mission, but stiff enemy resistance continued, particularly from well-camouflaged pillboxes hidden in the brush to the front of the Marine lines. These emplacements, too close to friendly troops to be engaged by heavy support weapons, could only be silenced by coordinated attacks of assault demolition teams using flamethrowers and explosive charges. Tanks then moved in to provide support, allowing the attack to progress from pillbox to pillbox; however, by the end of the day, the Marines had only advanced 200 difficult yards. Meanwhile, Schmidt's other regiments initiated a coordinated offensive to the north following extensive artillery, naval gunfire, and air support. Despite facing heavy resistance, the 23rd Marines successfully overran most of Airfield No. 1 by noon. Wensinger continued to push his units in the afternoon, but progress was limited as tanks were hindered by minefields and rough terrain. Wornham's 27th Marines pressed their attack on the left flank, overcoming enemy mortar and artillery fire to gain about 800 yards along the coast. In contrast, Lanigan's 25th Marines, affected by friendly fire, made only minimal advances against enemy crossfire from concealed positions. At 1600, friendly planes misdirected their fire to the 25th Marine's area, adding terror to the situation. An air strike consisting of .50-caliber machine-gun strafing, rockets, and bombs fell on troops of Company B of the 24th Marines, which was positioned on top of the quarry some 400 yards inland from the eastern shore. This strike was made without a preliminary "dry-run", and despite the fact that yellow front line panels were displayed prior to and during the aerial attack. The 1st Battalion, 24th Marines suffered five killed and six wounded as a result of this misguided effort. Shortly after the planes left the area, this battalion reported that friendly artillery and naval gunfire was being registered on its lines. Due to the slow progress, Schmidt attempted to land his reserve 21st Marines, but high seas and congested beaches ultimately thwarted these efforts. Nevertheless, the remaining 14th Marines were landed, albeit with significant casualties, and elements of the corps artillery began to come ashore. During the night, there were no counterattacks on Mount Suribachi, but the 4th and 5th Marine Divisions had to fend off some small counterattacks on their front lines. On February 21, following a strike involving 40 aircraft, Liversedge's 28th Marines launched another assault on the volcano. The 1st Battalion on the right swiftly advanced along the west beach to the base of Suribachi, while the 3rd Battalion in the center pushed nearly to the foot of the mountain despite facing heavy resistance. Meanwhile, the 2nd Battalion on the left moved cautiously along the east beach toward the volcano's base, with Company F heading toward Tobiishi Point. At the same time, other regiments continued their offensive towards O-1 after a bombardment from air, artillery, rockets, and naval gunfire. Rockey's units made significant progress, advancing over 1,000 yards, while the 23rd Marines achieved similar gains on the left flank, where slightly sheltered areas allowed for local and limited encirclement, but only advanced 100 yards in the right and center. The 25th Marines maintained steady pressure against the strong enemy defenses, gaining between 50 and 300 yards across the front. Colonel Hartnoll Withers' 21st Marines successfully landed this time; due to heavy casualties in the center, they were assigned to relieve the exhausted 23rd Marines. By nightfall, the Marines had to fend off several local counterattacks and infiltration attempts.  During the night, 50 kamikaze planes targeted Blandy's Task Force 52. They were picked up by the radar of the USS Saratoga, a veteran carrier of the Pacific War, and six fighters were sent to intercept. They shot down two Zeros but the remaining Zeros plowed on through the low lying cloud, two of them trailing smoke, and slammed into the side of the carrier turning the hangers into an inferno. Another solitary attacker smashed into the flight deck leaving a gaping hole 100 yards from the bow. Damage control teams worked wonders and within one hour the fires were under control and the Saratoga was able to recover a few of her planes. Another aircraft, a "Betty" twin engined bomber, tore into the escort carrier USS Bismarck Sea. The decks were full of aircraft and the ensuing explosion caused uncontrollable fires. Abandon ship was sounded and 800 men went over the side. Within a few minutes a huge explosion ripped off the entire stern of the carrier and she rolled 38 over and sank. Three other ships were also damaged: the escort carrier USS Lunga Point was showered with flaming debris as four aircraft were blasted out of the sky; the minesweeper Keokuk was damaged when a "Jill" dive bomber hit her deck; and LST 477 loaded with Sherman tanks received a glancing blow. The Saratoga, with destroyer escort, returned to Pearl Harbor, but by the time the damage was repaired the war was over. The kamikazes had done their work well: 358 men killed, one carrier sunk, and another severely damaged. It was a grim preview of the mayhem they would later cause during the invasion of Okinawa in April. On February 22, amidst a dreary cold rain, Liversedge renewed his assault on Suribachi, where only half of the original garrison remained to oppose the Marine advance. There was no let-up in the weather on Wednesday as Marines of the 28th Regiment, drenched to the skin and bent by the wind, prepared to renew the attack on Suribachi. Fresh supplies of ammunition had been brought to the front during the night, but the Shermans were mired in mud and the Navy declined to supply air support in the appalling weather. It was to be up to the foot soldier with rifle, flamethrower, grenade, and demolition charge to win the day. Colonel Atsuchi still had 800-900 men left and they had no intention of allowing the Americans an easy victory. Major Youamata announced: "We are surrounded by enemy craft of all sizes, shapes and descriptions, enemy shells have smashed at our installations and defenses, their planes bomb and strafe yet we remain strong and defiant. The Americans are beginning to climb the first terraces towards our defenses. Now they shall taste our steel and lead." Throughout the day, the 28th Marines engaged Japanese positions on the lower slopes of the mountain, with the 3rd Battalion making the final push to the base of Suribachi while the other two battalions cleared the coastline to completely encircle the volcano. Simultaneously, Schmidt's northern sweep continued, with the 21st Marines replacing Wensinger's troops, and Colonel Chester Graham's 26th Marines taking over on the 5th Division front. The 26th Marines advanced approximately 400 yards in the center but ultimately had to withdraw as the flanking units could not progress; the 21st Marines began their assault on the formidable defenses of Colonel Ikeda's 145th Regiment in front of Airfield No. 2, managing to advance only about 250 yards on the right; and the 25th Marines were unable to launch an attack on the left due to Withers' lack of significant gains and had to fend off several local Japanese counterattacks. Marine "Howlin' Mad" Smith aboard the USS Auburn was counting the cost. Three days of battle and the Regimental Returns listed 2,517 casualties for the 4th Division and 2,057 for the 5th: 4,574 dead and wounded and the O-1 line had just been reached. Little did he know that as his Marines approached the hills, ravines, canyons, gullies, and cliffs of the north the worst was yet to come. Additionally, as the 4th Division remained stalled, Cates ordered Colonel Walter Jordan's 24th Marines to relieve the weary troops of Lanigan on the right. During the night, most of Task Force 58 departed the area for a second air strike against Tokyo, which significantly limited the availability of aircraft for direct support of ground forces on Iwo Jima. On February 23, the 28th Marines under Liversedge launched their final assault on Suribachi. The 2nd Battalion was tasked with scaling the volcano's heights, while the 1st Battalion advanced south around the mountain's western side. To their surprise, they encountered no enemy fire, and small patrols reached the crater's edge by 09:40. 1st Lieutenant Harold G. Schrier, executive officer of Company E, and a 40-man detachment set out to follow the patrols and occupy the highest point of land on Iwo Jima. The number of live Japanese lurking in caves along this north face was unknown, so flankers were sent out to guard against ambush as Schrier's men clawed their way warily upward. Still there was a mysterious lack of enemy activity, and the only Japanese encountered were the harmless dead. Positions along the rim of the crater were reached at about 10:15, and as Marines scrambled over the lip, the tenseness was eased by action. A small defending force challenged the patrol and a short, hot fight developed. Even while this skirmish was in progress, some of the men located a length of Japanese iron pipe, secured a small American flag to one end, and raised the Stars and Stripes at 10:20. It was an inspiring sight for thousands of Americans on Iwo as the flag waved bravely from the summit. Shortly after the mounting of this flag that measured only 54 inches by 28 inches, an unidentified Marine went aboard LST 779, beached near the base of the volcano, to obtain a larger set of colors. As this second and larger (8 feet by 4 feet 8 inches) flag was being carried up the slopes of Suribachi, photographer Joe Rosenthal, who covered the Iwo operation for the Associated Press, noticed it and instantly started in close pursuit. His efforts that morning resulted in the now famous picture of the second flag raising. Also since it's one of my favorite movies, I wanted to add this passage from the book “Flags of our Fathers” by James Bradley The Secretary of the Navy, James Forrestal, had decided the previous night that he wanted to go ashore and witness the final stage of the fight for the mountain. Now, under a stern commitment to take orders from General Holland "Howlin' Mad" Smith, the secretary was churning ashore in the company of the blunt, earthy general. Their boat touched the beach just after the flag went up, and the mood among the high command turned jubilant. Gazing upward, at the red, white, and blue speck, Forrestal remarked to Smith: "Holland, the raising of that flag on Suribachi means a Marine Corps for the next five hundred years". Forrestal was so taken with fervor of the moment that he decided he wanted the Second Battalion's flag flying on Mt. Suribachi as a souvenir. The news of this wish did not sit well with 2nd Battalion Commander Chandler Johnson, whose temperament was every bit as fiery as Howlin Mad's. "To hell with that!" the colonel spat when the message reached him. The flag belonged to the battalion, as far as Johnson was concerned. He decided to secure it as soon as possible, and dispatched his assistant operations officer, Lieutenant Ted Tuttle, to the beach to obtain a replacement flag. As an afterthought, Johnson called after Tuttle: "And make it a bigger one." Following this, the 28th Marines conducted mopping-up operations to eliminate remaining enemy positions and seal off caves at the base of Suribachi. All accessible outer and inner slopes were covered as the Marines annihilated enemy snipers and blasted shut the many cave entrances, sealing in an uncounted number of Japanese. Much observation equipment was found, emphasizing the fact that this had been an excellent point of vantage from which hostile observers directed murderous fire against the entire beachhead. Marine artillerymen, ready and eager to seize this advantage, hastened to move flash-ranging equipment into position. By nightfall, approximately 122 Japanese soldiers were killed while attempting to infiltrate American lines. Over the five-day period, the 28th Marines suffered 895 casualties, while nearly 2,000 Japanese were either killed or trapped in over 1,000 caves in the area. Kuribayashi had not anticipated the loss of this strategically significant location so early in the battle, and the survivors who managed to breach American lines faced severe reprimands upon their return to the north. For the remainder of the month, the 28th Marines focused on clearing out stubborn Japanese forces, reorganizing, and reequipping. Meanwhile, fighting in the north persisted as the three assault regiments advanced toward the O-2 Line. The 26th and 21st Marines faced heavy fire and struggled to make progress, while the 24th Marines advanced along their entire front, gaining up to 300 yards in some areas. On this day, the situation on the beach steadily improved as clearance efforts, construction of exits, and unloading continued, facilitating the arrival of essential ammunition and an additional 25 tanks. On February 24, following extensive air, naval, and artillery preparations, the offensive resumed. However, the initial failure of tanks to join the assault due to minefields and heavy anti-tank fire forced the Marines to advance slowly under intense fire from various sources. In the center, the 3rd Battalion, 21st Marines advanced 800 yards, reaching the north side of the east-west runway of Airfield No. 2, while the 2nd Battalion gradually moved northward around the end of the runway by noon. In the afternoon, as tank support began to arrive, Withers' 3rd Battalion captured the hill north of the airstrip after a fierce hand-to-hand battle. Simultaneously, his 2nd Battalion coordinated with the 26th Marines to seize the elevation beyond the airfield. Graham's troops easily secured the ground in front but had to pause their advance when they found themselves about 400 yards ahead of the 21st Marines. On the right flank, the 24th Marines initially made significant progress alongside Withers' men toward the airfield but were ultimately halted by the strong defenses on Charlie-Dog Ridge.  Running along the southeast edge of the east-west runway of Airfield Number 2 was a ridge known only as "Charlie-Dog Ridge." In prolongation of this ridge, on a lower level to the southeast, was a semicircular rise of ground that formed the "Amphitheater." In this area, Japanese engineers had constructed some of the most formidable defenses on the island. From the south, the approach traversed bare flat ground swept by guns on the ridge. To the east, the route led across a weird series of volcanic outcroppings and draws. It was against these positions that the 24th Marines moved out on D-plus-5. Assault squads then had to methodically clear the ridge, moving from one strongpoint to another, using fire and explosives until Charlie-Dog was secured. While the overall gains for the day were notable by Iwo Jima standards, the casualty figures were also high, with the Marines suffering 1,034 killed and 3,741 wounded during the five-day push to the second airfield. Additionally, the remainder of General Erskine's 3rd Marine Division began landing that day to officially take control of the central area. On February 25, a decision was made to hold back the 26th Marines to allow the 3rd Division to align with them. After another intense bombardment, Colonel Howard Kenyon's 9th Marines advanced through the 21st to continue the assault, but the two-battalion attack only managed to gain a meager 100 yards against Ikeda's determined defenders. Kenyon then deployed his reserve 3rd Battalion in the center, but it also failed to break through. To the east, the 23rd and 24th Marines launched simultaneous attacks, but only the 23rd made significant progress, overrunning the eastern end of the strip and establishing a foothold on the high ground to the north. Meanwhile, in the morning, Mitscher's carriers conducted a second strike on Tokyo. The Japanese sighted 600 US carrier aircraft on February 25, but Rear Admiral “Ted” Sherman reported, “The enemy opposition was only halfhearted and Japanese planes which were not shot down seemed glad to withdraw from the scene … as swiftly and unceremoniously as possible. Even here, over their own capital, the enemy were notably inferior to our naval aviators in aggressiveness, tactics, and determination.” TF-58 aircraft hit the Ota and Koizumi aircraft plants, but increasingly snowy, stormy weather meant Mitscher canceled further Tokyo strikes at 1215hrs. Spruance and Mitscher decided to hit Nagoya instead. En route to Nagoya that night destroyers USS Hazelwood and Murray sank three small Japanese craft. Eventually Mitscher realized TF-58 would not reach launching position on time, and at 0530hrs Spruance and Mitscher canceled the Nagoya strikes and headed south to refuel. TF-58 claimed 47 Japanese planes shot down and 111 destroyed on the ground for a total of 158 Japanese planes destroyed on February 25. Two hangars, one radar station, and two trains were destroyed. About 75 percent of the Ota engine plant's buildings were destroyed and an additional 15 percent heavily damaged. The Koizuma plant had also been heavily hit, and five coastal vessels and several smaller craft sunk, with another 14 vessels damaged. Total US losses were nine aircraft to antiaircraft fire and four to operational causes; four pilots were lost.. After TF-58 aircraft had plastered the Nakajima Ota airframe plant with 45 tons of bombs, February 25 photoreconnaissance revealed Ota to be 60 percent destroyed and 30 percent heavily damaged, although half of this was believed due to B-29s. After the photos TF-58 aircraft dropped another 13 tons on the plant. The Nakajima Koizuma plant was attacked on February 25 with 35 to 40 tons of bombs, with hits concentrated in the center of the plant. Reconnaissance showed 20 percent of the Koizuma roof damaged. The Hitachi–Tachikawa aircraft engine plant was attacked by one Task Group strike, with US airmen reporting “excellent results.” Photographs showed many bomb hits, but smoke made precise damage assessments difficult. Slight damage was also inflicted on the Tachikawa airframe plant. TF-58 planes struck the B-29s' nemesis, the Musashino-Tama aircraft engine plant, with 40 tons of bombs in the center of the Tama complex.  On that day, LeMay also dispatched 231 B-29s to attack Tokyo with incendiaries, with 172 successfully dropping 453.7 tons of bombs, incinerating a square mile of the city. This operation served as the "conclusive" test of the incendiary bombs that the 20th Air Force had requested, with valuable lessons to be learned for future use. The next day, the 26th Marines resumed their attack despite the high ground on the left remaining unclaimed, successfully advancing over 300 yards in the right and center. In the center, the 9th Marines continued their assault with the 1st and 2nd Battalions side by side, but they made no notable gains. On the right flank, the 23rd Marines launched another assault towards Hill 382, facing heavy resistance and managing to advance only about 200 yards. Concurrently, Lanigan's 25th Marines moved through the battered 24th Marines, achieving an advance of approximately 100 yards before encountering intense machine-gun fire from the Amphitheater and Turkey Knob. On February 27, Wonrham's 27th Marines took over from the exhausted 26th and continued to push northward despite rising casualties, successfully overrunning several strongpoints and gaining about 500 yards across the front. In the center, the 9th Marines finally breached the enemy's main defenses towards Hill 199-O and captured Hill Peter, securing Airfield No. 2. Meanwhile, on the right, the 4th Division pressed on against the heavily fortified Japanese positions at the Meatgrinder, advancing only 150 to 200 yards on each flank while struggling to make headway against the Amphitheater and Turkey Knob. In the final attack of the month, the 27th Marines advanced towards Hill 362A, reaching its base but were forced to retreat nearly 100 yards due to Japanese counterattacks and loss of communication. In the center, Withers' 21st Marines moved past the 9th Marines and rapidly advanced north of Airfield No. 2, making significant progress on the right as they swept through Motoyama village and captured the high ground overlooking Airfield No. 3. To the east, Cates continued to send troops into the Meatgrinder, with the 23rd Marines gaining over 200 yards and launching an attack on Hill 382, while the 25th Marines struggled to make any headway against the Amphitheater and Turkey Knob, achieving only minor gains along the coast. 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. And thus we have begun one of the most brutal battles of WW2, let alone the Pacific War. It was a controversial decision to invade Iwo Jima and the Americans could never have predicted how the Japanese would change their tactics to turn the entire ordeal into one giant meat grinder.

Today's episode comes from a question on the Doc On The Run YouTube channel regarding the video entitled “Proof you do not have to stop running with a metatarsal stress response.”  Brian was clearly frustrated. He commented: “I wish… I have a big swollen reason under the second metatarsal. It tingles a bit while running. Slight burning. I have to alter my landing to not irritate it. I'm finished. Rest in peace to my running VO2 max. I got to focus on cycling.” Does a stress response equal "rest in peace" to my VO2 max?  Well, that is a good question and that is what we're talking about today on the Doc On The Run Podcast. 

fWotD Episode 2844: Tropical Storm Gabrielle (2007) Welcome to Featured Wiki of the Day, your daily dose of knowledge from Wikipedia’s finest articles.The featured article for Sunday, 16 February 2025 is Tropical Storm Gabrielle (2007).Tropical Storm Gabrielle was a short-lived tropical cyclone that passed over North Carolina before tracking out to sea. The seventh named storm of the 2007 Atlantic hurricane season, Gabrielle developed as a subtropical cyclone on September 8 about 385 miles (620 km) southeast of Cape Lookout, North Carolina. Unfavorable wind shear impacted the storm for much of its duration, although a temporary decrease in the shear allowed the cyclone to become a tropical storm. On September 9, Gabrielle made landfall at Cape Lookout National Seashore in the Outer Banks of North Carolina with winds of 60 mph (97 km/h). Turning to the northeast, the storm quickly weakened and dissipated on September 11.In advance of the storm, tropical cyclone watches and warnings were issued for coastal areas, while rescue teams and the U. S. Coast Guard were put on standby. The storm dropped heavy rainfall near its immediate landfall location but little precipitation elsewhere. Along the coast of North Carolina, high waves, rip currents, and storm surge were reported. Slight localized flooding was reported. Gusty winds also occurred, though no wind damage was reported. One person drowned in rough surf caused by the storm in Florida. Overall damage was minor.This recording reflects the Wikipedia text as of 01:05 UTC on Sunday, 16 February 2025.For the full current version of the article, see Tropical Storm Gabrielle (2007) on Wikipedia.This podcast uses content from Wikipedia under the Creative Commons Attribution-ShareAlike License.Visit our archives at wikioftheday.com and subscribe to stay updated on new episodes.Follow us on Mastodon at @wikioftheday@masto.ai.Also check out Curmudgeon's Corner, a current events podcast.Until next time, I'm neural Kajal.

Duane's website https://bulletproofpub.com/Make a Donation to Forbidden Knowledge News https://www.paypal.me/forbiddenknowledgenehttps://buymeacoffee.com/forbiddenReconnect to Everything with BrainsupremeGet 25% off your order here!!https://brainsupreme.co/discount/FKN15Subscribe to Cory Hughe's "Bloody History" substackhttps://bloodyhistory.substack.comSign up for the IMT crypto community Imt.networkBook a free consultation with Jennifer Halcame Emailjenniferhalcame@gmail.comFacebook pagehttps://www.facebook.com/profile.php?id=61561665957079&mibextid=ZbWKwLSick of having mediocre health? Transform your health and vitality with Christian Yordanov's program. Learn more and book a free intro call here (mention FKN at time of booking and he will have a special gift for youhttps://christianyordanov.com/fkn/Watch The Forbidden Documentary: Occult Louisiana on Tubi: https://link.tubi.tv/pGXW6chxCJbC60 PurplePowerhttps://go.shopc60.com/FORBIDDEN10/or use coupon code knowledge10FKN Link Treehttps://linktr.ee/FKNlinksForbidden Knowledge Network https://forbiddenknowledge.news/ Sign up on Rokfin!https://rokfin.com/fknplusPodcastshttps://www.spreaker.com/show/forbiddenAvailable on all platforms Support FKN on Spreaker https://spreaker.page.link/KoPgfbEq8kcsR5oj9FKN ON Rumblehttps://rumble.com/c/FKNpGet Cory Hughes Book!https://www.buymeacoffee.com/jfkbookhttps://www.amazon.com/Warning-History-Cory-Hughes/dp/B0CL14VQY6/ref=mp_s_a_1_1?crid=72HEFZQA7TAP&keywords=a+warning+from+history+cory+hughes&qid=1698861279&sprefix=a+warning+fro%2Caps%2C121&sr=8-1https://coryhughes.org/Johnny Larson's artworkhttps://www.patreon.com/JohnnyLarsonYouTube https://youtube.com/@fknclipspBecome Self-Sufficient With A Food Forest!!https://foodforestabundance.com/get-started/?ref=CHRISTOPHERMATHUse coupon code: FORBIDDEN for discountsThe FKN Store!https://www.fknstore.net/Our Facebook pageshttps://www.facebook.com/forbiddenknowledgenewsconspiracy/https://www.facebook.com/FKNNetwork/Instagram @forbiddenknowledgenews1@forbiddenknowledgenetworkXhttps://x.com/ForbiddenKnow10?t=uO5AqEtDuHdF9fXYtCUtfw&s=09Email meforbiddenknowledgenews@gmail.comsome music thanks to:https://www.bensound.com/Become a supporter of this podcast: https://www.spreaker.com/podcast/forbidden-knowledge-news--3589233/support.

A former teacher of the year is now admitting she had sexual contact with 2 of her former students, what she's facing after pleading guilty. A chaotic scene in a Santee hair salon that you might've seen on social media, the man at the center of it is expected in court. Plus a slight chance of rain, your First Alert Forecast is ahead. NBC 7's Steven Luke has what you need to know to start your Thursday.

Mike, Steve, and Hoss hosted Sports Talk live from the Morial Convention Center. The guys spoke to KLFY reporter and food influencer Gerald Gruenig and former two-time Super Bowl-winning cornerback Malcolm Butler. Gruenig celebrated the different food cultures in South Louisiana. Butler remembered his legendary goal-line interception in Super Bowl XLIX and the Patriots' legendary 28-3 comeback in Super Bowl LI. Steve and Jeff interviewed Saints DT Bryan Bresee on Radio Row. Hoss praised Bresee's development in his second year with the Saints and remembered New Orleans' matchups against Philadelphia and Kansas City. Hoss also explained that the Eagles have a roster built to beat the Chiefs. Mike and Steve interviewed Mike Silver, a sportswriter for The Athletic. Silver shared his thoughts on Eagles OC Kellen Moore, the lead candidate for the Saints' head coaching vacancy, Derek Carr's future in New Orleans, and the Super Bowl LIX matchup between Philadelphia and Kansas City. Chris Dodson, an NBA reporter for ClutchPoints, joined Mike and Steve to discuss the NBA's trade deadline. Steve and Mike previewed the Saints' off-season quarterback decision. The guys also listened to Brian Kelly's press conference about Greg Brooks Jr. and the Tigers' transfer portal class. Wilson Alexander, an LSU reporter for The Advocate, joined Steve and Mike to recap the Tigers' off-season work in the transfer portal.

DEAR PAO: Slapping a person in the face may be penalized as slight physical injury | Feb. 4, 2025Visit our website at https://www.manilatimes.netFollow us:Facebook - https://tmt.ph/facebookInstagram - https://tmt.ph/instagramTwitter - https://tmt.ph/twitterDailyMotion - https://tmt.ph/dailymotionSubscribe to our Digital Edition - https://tmt.ph/digitalSign up to our newsletters: https://tmt.ph/newslettersCheck out our Podcasts:Spotify - https://tmt.ph/spotifyApple Podcasts - https://tmt.ph/applepodcastsAmazon Music - https://tmt.ph/amazonmusicDeezer: https://tmt.ph/deezerStitcher: https://tmt.ph/stitcherTune In: https://tmt.ph/tunein#TheManilaTimes Hosted on Acast. See acast.com/privacy for more information.

Jim and friend of the show Derek (of D&J's Epic Quest) get together with Molly Macabre, author of the zombie apocalyptic tale of 2024, Dark Bloom, to get the real dirt on her writing. We question her choices, probe into her motivations, and try to pry out a few secrets no one yet knew. Come learn if Molly is the type of author you'd hope to get more from, or where “one and done” is the better option. Derek and I definitely have a take on this; listen to this episode to see if you'll agree. (Slight spoilers for Dark Bloom) #FantasyForTheAges #readingrecommendations #scifi #sciencefiction #zombieapocalypse #DarkBloom #AuthorInterview #MollyMacabre #SFFH #Horror #SFF #booktube #booktuber Want to purchase the book mentioned in this episode? Dark Bloom: https://t.ly/Y5F_a Channels mentioned in this episode: D&J's Epic Quest: https://www.youtube.com/@djsepicquest226 Geaux Read Books: https://www.youtube.com/@geauxreadbooks Where the Macabre Things Are: https://www.youtube.com/@molly_macabre Check Out Molly's Website: https://macabremolly.com/ Ways to connect with us: Support us on Patreon: https://www.patreon.com/FantasyForTheAges Follow Jim/Father on Goodreads: https://www.goodreads.com/user/show/13848336-jim-scriven Join us on Discord: https://discord.gg/jMWyVJ6qKk Follow us on "X": @Fantasy4theAges Follow us on Blue Sky: @fantasy4theages.bsky.social Follow us on Instagram: fantasy_for_the_ages Follow us on Mastodon: @FantasyForTheAges@nerdculture.de Email us: FantasyForTheAges@gmail.com Check out our merch: https://www.newcreationsbyjen.com/collections/fantasyfortheages Jim's Microphone: Blue Yeti https://tinyurl.com/3shpvhb4 ———————————————————————————— Music and video elements licensed under Envato Elements: https://elements.envato.com/

Chicago firefighters battled two fires on Southwest Side, and more.

Chicago firefighters battled two fires on Southwest Side, and more.

Chicago firefighters battled two fires on Southwest Side, and more.

The guys are no longer brimless! Come through and chill as the guys discuss Skeleton Crew, Golden Globe winners, and the Creature Commandos finale...

You don't need to be a psychic in order to read people's minds. Those around you constantly give away their thoughts, feelings, and intentions without even realizing it. You just need to be really attentive to see right through them. Obviously, everybody's different, each with their own mannerisms and peculiarities. That's why it's so important to understand what behavior is normal for a particular individual. Slight changes in their behavior or body language can speak volumes and allow you to read them like an open book. Analyzing all the information you have, you'll be able to understand someone's personality a lot better without even spending that much time with them. In different cultures, there can be different rules. For example, in some countries, people look away to show their respect, not because they're hiding something or feeling uncomfortable. They say you should never judge a book by its cover. That's good advice and all, but a person's appearance really can tell a lot about them. We like to spend more time with people who share our interests and personality traits. Watch who someone spends most their time with and how they treat other people. See if this person tries to make others comfortable or rudely annoys people without even noticing it. Music: Level Plane - Riot From Russia With Love - Huma-Huma https://www.youtube.com/audiolibrary/... TIMESTAMPS Define the norm 0:20 Observe and compare 1:05 Always mind the context 1:43 Check out how someone is dressed 2:19 What's with the face? 3:26 Watch their behavior in a group 5:12 Listen to how they articulate their thoughts 6:07 Trust your intuition 7:02 SUMMARY -Try to understand what behavior is normal for a particular individual, and then pay attention to anything the person does differently. -Pay attention to the details: how they carry themselves, how they communicate with other people, what secrets their body language reveals. -Always keep in mind the context of the situation: in different cultures, there can be different rules. -People, either willingly or subconsciously, show their true selves through their clothing choices. -Facial expressions can reveal a lot of things people would rather keep hidden. For example, when someone likes you, their facial muscles relax, the head tilts a bit to the side, and blood rushes to their lips, making them slightly plumper and brighter. -Watch who someone spends most their time with and how they treat other people. -Don't just listen to what a person says, pay attention to how they say it. -Intuition can let you down from time to time, but the longer you keep listening to it and observing people, the better it'll work. Subscribe to Bright Side : https://goo.gl/rQTJZz ---------------------------------------------------------------------------------------- Our Social Media: Facebook: / brightside Instagram: / brightgram 5-Minute Crafts Youtube: https://www.goo.gl/8JVmuC ---------------------------------------------------------------------------------------- For more videos and articles visit: http://www.brightside.me/ Learn more about your ad choices. Visit megaphone.fm/adchoices

Joe's Premium Subscription: www.standardgrain.comGrain Markets and Other Stuff Links-Apple PodcastsSpotifyTikTokYouTubeFutures and options trading involves risk of loss and is not suitable for everyone.

John Walt Boatright, director of government affairs for the American Farm Bureau Federation, says that even though the increase in positions certified was small, it still demonstrates how important the program is.

Happy holidays! We'll be sharing snippets from Latent Space LIVE! through the break bringing you the best of 2024! We want to express our deepest appreciation to event sponsors AWS, Daylight Computer, Thoth.ai, StrongCompute, Notable Capital, and most of all all our LS supporters who helped fund the gorgeous venue and A/V production!For NeurIPS last year we did our standard conference podcast coverage interviewing selected papers (that we have now also done for ICLR and ICML), however we felt that we could be doing more to help AI Engineers 1) get more industry-relevant content, and 2) recap 2024 year in review from experts. As a result, we organized the first Latent Space LIVE!, our first in person miniconference, at NeurIPS 2024 in Vancouver.Our next keynote covers The State of LLM Agents, with the triumphant return of Professor Graham Neubig's return to the pod (his ICLR episode here!). OpenDevin is now a startup known as AllHands! The renamed OpenHands has done extremely well this year, as they end the year sitting comfortably at number 1 on the hardest SWE-Bench Full leaderboard at 29%, though on the smaller SWE-Bench Verified, they are at 53%, behind Amazon Q, devlo, and OpenAI's self reported o3 results at 71.7%.Many are saying that 2025 is going to be the year of agents, with OpenAI, DeepMind and Anthropic setting their sights on consumer and coding agents, vision based computer-using agents and multi agent systems. There has been so much progress on the practical reliability and applications of agents in all domains, from the huge launch of Cognition AI's Devin this year, to the sleeper hit of Cursor Composer and Codeium's Windsurf Cascade in the IDE arena, to the explosive revenue growth of Stackblitz's Bolt, Lovable, and Vercel's v0, and the unicorn rounds and high profile movements of customer support agents like Sierra (now worth $4 billion) and search agents like Perplexity (now worth $9 billion). We wanted to take a little step back to understand the most notable papers of the year in Agents, and Graham indulged with his list of 8 perennial problems in building agents in 2024.Must-Read Papers for the 8 Problems of Agents* The agent-computer interface: CodeAct: Executable Code Actions Elicit Better LLM Agents. Minimial viable tools: Execution Sandbox, File Editor, Web Browsing* The human-agent interface: Chat UI, GitHub Plugin, Remote runtime, …?* Choosing an LLM: See Evaluation of LLMs as Coding Agents on SWE-Bench at 30x - must understand instructions, tools, code, environment, error recovery* Planning: Single Agent Systems vs Multi Agent (CoAct: A Global-Local Hierarchy for Autonomous Agent Collaboration) - Explicit vs Implicit, Curated vs Generated* Reusable common workflows: SteP: Stacked LLM Policies for Web Actions and Agent Workflow Memory - Manual prompting vs Learning from Experience* Exploration: Agentless: Demystifying LLM-based Software Engineering Agents and BAGEL: Bootstrapping Agents by Guiding Exploration with Language* Search: Tree Search for Language Model Agents - explore paths and rewind* Evaluation: Fast Sanity Checks (miniWoB and Aider) and Highly Realistic (WebArena, SWE-Bench) and SWE-Gym: An Open Environment for Training Software Engineering Agents & VerifiersFull Talk on YouTubePlease like and subscribe!Timestamps* 00:00 Welcome to Latent Space Live at NeurIPS 2024* 00:29 State of LLM Agents in 2024* 02:20 Professor Graham Newbig's Insights on Agents* 03:57 Live Demo: Coding Agents in Action* 08:20 Designing Effective Agents* 14:13 Choosing the Right Language Model for Agents* 16:24 Planning and Workflow for Agents* 22:21 Evaluation and Future Predictions for Agents* 25:31 Future of Agent Development* 25:56 Human-Agent Interaction Challenges* 26:48 Expanding Agent Use Beyond Programming* 27:25 Redesigning Systems for Agent Efficiency* 28:03 Accelerating Progress with Agent Technology* 28:28 Call to Action for Open Source Contributions* 30:36 Q&A: Agent Performance and Benchmarks* 33:23 Q&A: Web Agents and Interaction Methods* 37:16 Q&A: Agent Architectures and Improvements* 43:09 Q&A: Self-Improving Agents and Authentication* 47:31 Live Demonstration and Closing RemarksTranscript[00:00:29] State of LLM Agents in 2024[00:00:29] Speaker 9: Our next keynote covers the state of LLM agents. With the triumphant return of Professor Graham Newbig of CMU and OpenDevon, now a startup known as AllHands. The renamed OpenHands has done extremely well this year, as they end the year sitting comfortably at number one on the hardest SWE Benchful leaderboard at 29%.[00:00:53] Speaker 9: Though, on the smaller SWE bench verified, they are at 53 percent behind Amazon Q [00:01:00] Devlo and OpenAI's self reported O3 results at 71. 7%. Many are saying that 2025 is going to be the year of agents, with OpenAI, DeepMind, and Anthropic setting their sights on consumer and coding agents. Vision based computer using agents and multi agent systems.[00:01:22] Speaker 9: There has been so much progress on the practical reliability and applications of agents in all domains, from the huge launch of Cognition AI's Devon this year, to the sleeper hit of Cursor Composer and recent guest Codium's Windsurf Cascade in the IDE arena. To the explosive revenue growth of recent guests StackBlitz's Bolt, Lovable, and Vercel's vZero.[00:01:44] Speaker 9: And the unicorn rounds and high profile movements of customer support agents like Sierra, now worth 4 billion, and search agents like Perplexity, now worth 9 billion. We wanted to take a little step back to understand the most notable papers of the year in [00:02:00] agents, and Graham indulged with his list of eight perennial problems in building agents.[00:02:06] Speaker 9: As always, don't forget to check our show notes for all the selected best papers of 2024, and for the YouTube link to their talk. Graham's slides were especially popular online, and we are honoured to have him. Watch out and take care![00:02:20] Professor Graham Newbig's Insights on Agents[00:02:20] Speaker: Okay hi everyone. So I was given the task of talking about agents in 2024, and this is An impossible task because there are so many agents, so many agents in 2024. So this is going to be strongly covered by like my personal experience and what I think is interesting and important, but I think it's an important topic.[00:02:41] Speaker: So let's go ahead. So the first thing I'd like to think about is let's say I gave you you know, a highly competent human, some tools. Let's say I gave you a web browser and a terminal or a file system. And the ability to [00:03:00] edit text or code. What could you do with that? Everything. Yeah.[00:03:07] Speaker: Probably a lot of things. This is like 99 percent of my, you know, daily daily life, I guess. When I'm, when I'm working. So, I think this is a pretty powerful tool set, and I am trying to do, and what I think some other people are trying to do, is come up with agents that are able to, you know, manipulate these things.[00:03:26] Speaker: Web browsing, coding, running code in successful ways. So there was a little bit about my profile. I'm a professor at CMU, chief scientist at All Hands AI, building open source coding agents. I'm maintainer of OpenHands, which is an open source coding agent framework. And I'm also a software developer and I, I like doing lots of coding and, and, you know, shipping new features and stuff like this.[00:03:51] Speaker: So building agents that help me to do this, you know, is kind of an interesting thing, very close to me.[00:03:57] Live Demo: Coding Agents in Action[00:03:57] Speaker: So the first thing I'd like to do is I'd like to try [00:04:00] some things that I haven't actually tried before. If anybody has, you know, tried to give a live demo, you know, this is, you know very, very scary whenever you do it and it might not work.[00:04:09] Speaker: So it might not work this time either. But I want to show you like three things that I typically do with coding agents in my everyday work. I use coding agents maybe five to 10 times a day to help me solve my own problems. And so this is a first one. This is a data science task. Which says I want to create scatter plots that show the increase of the SWE bench score over time.[00:04:34] Speaker: And so I, I wrote a kind of concrete prompt about this. Agents work better with like somewhat concrete prompts. And I'm gonna throw this into open hands and let it work. And I'll, I'll go back to that in a second. Another thing that I do is I create new software. And I, I've been using a [00:05:00] service a particular service.[00:05:01] Speaker: I won't name it for sending emails and I'm not very happy with it. So I want to switch over to this new service called resend. com, which makes it easier to send emails. And so I'm going to ask it to read the docs for the resend. com API and come up with a script that allows me to send emails. The input to the script should be a CSV file and the subject and body should be provided in Jinja2 templates.[00:05:24] Speaker: So I'll start another agent and and try to get it to do that for me.[00:05:35] Speaker: And let's go with the last one. The last one I do is. This is improving existing software and in order, you know, once you write software, you usually don't throw it away. You go in and, like, actually improve it iteratively. This software that I have is something I created without writing any code.[00:05:52] Speaker: It's basically software to monitor how much our our agents are contributing to the OpenHance repository. [00:06:00] And on the, let me make that a little bit bigger, on the left side, I have the number of issues where it like sent a pull request. I have the number of issues where it like sent a pull request, whether it was merged in purple, closed in red, or is still open in green. And so these are like, you know, it's helping us monitor, but one thing it doesn't tell me is the total number. And I kind of want that feature added to this software.[00:06:33] Speaker: So I'm going to try to add that too. So. I'll take this, I'll take this prompt,[00:06:46] Speaker: and here I want to open up specifically that GitHub repo. So I'll open up that repo and paste in the prompt asking it. I asked it to make a pie chart for each of these and give me the total over the entire time period that I'm [00:07:00] monitoring. So we'll do that. And so now I have let's see, I have some agents.[00:07:05] Speaker: Oh, this one already finished. Let's see. So this one already finished. You can see it finished analyzing the Swebench repository. It wrote a demonstration of, yeah, I'm trying to do that now, actually.[00:07:30] Speaker: It wrote a demonstration of how much each of the systems have improved over time. And I asked it to label the top three for each of the data sets. And so it labeled OpenHands as being the best one for SWE Bench Normal. For SWE Bench Verified, it has like the Amazon QAgent and OpenHands. For the SWE Bench Lite, it has three here over three over here.[00:07:53] Speaker: So you can see like. That's pretty useful, right? If you're a researcher, you do data analysis all the time. I did it while I was talking to all [00:08:00] of you and making a presentation. So that's, that's pretty nice. I, I doubt the other two are finished yet. That would be impressive if the, yeah. So I think they're still working.[00:08:09] Speaker: So maybe we'll get back to them at the end of the presentation. But so these are the kinds of the, these are the kinds of things that I do every day with coding agents now. And it's or software development agents. It's pretty impressive.[00:08:20] Designing Effective Agents[00:08:20] Speaker: The next thing I'd like to talk about a little bit is things I worry about when designing agents.[00:08:24] Speaker: So we're designing agents to, you know, do a very difficult task of like navigating websites writing code, other things like this. And within 2024, there's been like a huge improvement in the methodology that we use to do this. But there's a bunch of things we think about. There's a bunch of interesting papers, and I'd like to introduce a few of them.[00:08:46] Speaker: So the first thing I worry about is the agent computer interface. Like, how do we get an agent to interact with computers? And, How do we provide agents with the tools to do the job? And [00:09:00] within OpenHands we are doing the thing on the right, but there's also a lot of agents that do the thing on the left.[00:09:05] Speaker: So the thing on the left is you give like agents kind of granular tools. You give them tools like or let's say your instruction is I want to determine the most cost effective country to purchase the smartphone model, Kodak one the countries to consider are the USA, Japan, Germany, and India. And you have a bunch of available APIs.[00:09:26] Speaker: And. So what you do for some agents is you provide them all of these tools APIs as tools that they can call. And so in this particular case in order to solve this problem, you'd have to make about like 30 tool calls, right? You'd have to call lookup rates for Germany, you'd have to look it up for the US, Japan, and India.[00:09:44] Speaker: That's four tool goals. And then you go through and do all of these things separately. And the method that we adopt in OpenHands instead is we provide these tools, but we provide them by just giving a coding agent, the ability to call [00:10:00] arbitrary Python code. And. In the arbitrary Python code, it can call these tools.[00:10:05] Speaker: We expose these tools as APIs that the model can call. And what that allows us to do is instead of writing 20 tool calls, making 20 LLM calls, you write a program that runs all of these all at once, and it gets the result. And of course it can execute that program. It can, you know, make a mistake. It can get errors back and fix things.[00:10:23] Speaker: But that makes our job a lot easier. And this has been really like instrumental to our success, I think. Another part of this is what tools does the agent need? And I, I think this depends on your use case, we're kind of extreme and we're only giving the agent five tools or maybe six tools.[00:10:40] Speaker: And what, what are they? The first one is program execution. So it can execute bash programs, and it can execute Jupyter notebooks. It can execute cells in Jupyter notebooks. So that, those are two tools. Another one is a file editing tool. And the file editing tool allows you to browse parts of files.[00:11:00][00:11:00] Speaker: And kind of read them, overwrite them, other stuff like this. And then we have another global search and replace tool. So it's actually two tools for file editing. And then a final one is web browsing, web browsing. I'm kind of cheating when I call it only one tool. You actually have like scroll and text input and click and other stuff like that.[00:11:18] Speaker: But these are basically the only things we allow the agent to do. What, then the question is, like, what if we wanted to allow it to do something else? And the answer is, well, you know, human programmers already have a bunch of things that they use. They have the requests PyPy library, they have the PDF to text PyPy library, they have, like, all these other libraries in the Python ecosystem that they could use.[00:11:41] Speaker: And so if we provide a coding agent with all these libraries, it can do things like data visualization and other stuff that I just showed you. So it can also get clone repositories and, and other things like this. The agents are super good at using the GitHub API also. So they can do, you know, things on GitHub, like finding all of the, you know, [00:12:00] comments on your issues or checking GitHub actions and stuff.[00:12:02] Speaker: The second thing I think about is the human agent interface. So this is like how do we get humans to interact with agents? Bye. I already showed you one variety of our human agent interface. It's basically a chat window where you can browse through the agent's results and things like this. This is very, very difficult.[00:12:18] Speaker: I, I don't think anybody has a good answer to this, and I don't think we have a good answer to this, but the, the guiding principles that I'm trying to follow are we want to present enough info to the user. So we want to present them with, you know, what the agent is doing in the form of a kind of.[00:12:36] Speaker: English descriptions. So you can see here you can see here every time it takes an action, it says like, I will help you create a script for sending emails. When it runs a bash command. Sorry, that's a little small. When it runs a bash command, it will say ran a bash command. It won't actually show you the whole bash command or the whole Jupyter notebook because it can be really large, but you can open it up and see if you [00:13:00] want to, by clicking on this.[00:13:01] Speaker: So like if you want to explore more, you can click over to the Jupyter notebook and see what's displayed in the Jupyter notebook. And you get like lots and lots of information. So that's one thing.[00:13:16] Speaker: Another thing is go where the user is. So like if the user's already interacting in a particular setting then I'd like to, you know, integrate into that setting, but only to a point. So at OpenHands, we have a chat UI for interaction. We have a GitHub plugin for tagging and resolving issues. So basically what you do is you Do at open hands agent and the open hands agent will like see that comment and be able to go in and fix things.[00:13:42] Speaker: So if you say at open hands agent tests are failing on this PR, please fix the tests. It will go in and fix the test for you and stuff like this. Another thing we have is a remote runtime for launching headless jobs. So if you want to launch like a fleet of agents to solve, you know five different problems at once, you can also do [00:14:00] that through an API.[00:14:00] Speaker: So we have we have these interfaces and this probably depends on the use case. So like, depending if you're a coding agent, you want to do things one way. If you're a like insurance auditing agent, you'll want to do things other ways, obviously.[00:14:13] Choosing the Right Language Model for Agents[00:14:13] Speaker: Another thing I think about a lot is choosing a language model.[00:14:16] Speaker: And for agentic LMs we have to have a bunch of things work really well. The first thing is really, really good instruction following ability. And if you have really good instruction following ability, it opens up like a ton of possible applications for you. Tool use and coding ability. So if you provide tools, it needs to be able to use them well.[00:14:38] Speaker: Environment understanding. So it needs, like, if you're building a web agent, it needs to be able to understand web pages either through vision or through text. And error awareness and recovery ability. So, if it makes a mistake, it needs to be able to, you know, figure out why it made a mistake, come up with alternative strategies, and other things like this.[00:14:58] Speaker: [00:15:00] Under the hood, in all of the demos that I did now Cloud, we're using Cloud. Cloud has all of these abilities very good, not perfect, but very good. Most others don't have these abilities quite as much. So like GPT 4. 0 doesn't have very good error recovery ability. And so because of this, it will go into loops and do the same thing over and over and over again.[00:15:22] Speaker: Whereas Claude does not do this. Claude, if you, if you use the agents enough, you get used to their kind of like personality. And Claude says, Hmm, let me try a different approach a lot. So, you know, obviously it's been trained in some way to, you know, elicit this ability. We did an evaluation. This is old.[00:15:40] Speaker: And we need to update this basically, but we evaluated CLOD, mini LLAMA 405B, DeepSeq 2. 5 on being a good code agent within our framework. And CLOD was kind of head and shoulders above the rest. GPT 40 was kind of okay. The best open source model was LLAMA [00:16:00] 3. 1 405B. This needs to be updated because this is like a few months old by now and, you know, things are moving really, really fast.[00:16:05] Speaker: But I still am under the impression that Claude is the best. The other closed models are, you know, not quite as good. And then the open models are a little bit behind that. Grok, I, we haven't tried Grok at all, actually. So, it's a good question. If you want to try it I'd be happy to help.[00:16:24] Speaker: Cool.[00:16:24] Planning and Workflow for Agents[00:16:24] Speaker: Another thing is planning. And so there's a few considerations for planning. The first one is whether you have a curated plan or you have it generated on the fly. And so for solving GitHub issues, you can kind of have an overall plan. Like the plan is first reproduce. If there's an issue, first write tests to reproduce the issue or to demonstrate the issue.[00:16:50] Speaker: After that, run the tests and make sure they fail. Then go in and fix the tests. Run the tests again to make sure they pass and then you're done. So that's like a pretty good workflow [00:17:00] for like solving coding issues. And you could curate that ahead of time. Another option is to let the language model basically generate its own plan.[00:17:10] Speaker: And both of these are perfectly valid. Another one is explicit structure versus implicit structure. So let's say you generate a plan. If you have explicit structure, you could like write a multi agent system, and the multi agent system would have your reproducer agent, and then it would have your your bug your test writer agent, and your bug fixer agent, and lots of different agents, and you would explicitly write this all out in code, and then then use it that way.[00:17:38] Speaker: On the other hand, you could just provide a prompt that says, please do all of these things in order. So in OpenHands, we do very light planning. We have a single prompt. We don't have any multi agent systems. But we do provide, like, instructions about, like, what to do first, what to do next, and other things like this.[00:17:56] Speaker: I'm not against doing it the other way. But I laid [00:18:00] out some kind of justification for this in this blog called Don't Sleep on Single Agent Systems. And the basic idea behind this is if you have a really, really good instruction following agent it will follow the instructions as long as things are working according to your plan.[00:18:14] Speaker: But let's say you need to deviate from your plan, you still have the flexibility to do this. And if you do explicit structure through a multi agent system, it becomes a lot harder to do that. Like, you get stuck when things deviate from your plan. There's also some other examples, and I wanted to introduce a few papers.[00:18:30] Speaker: So one paper I liked recently is this paper called CoAct where you generate plans and then go in and fix them. And so the basic idea is like, if you need to deviate from your plan, you can You know, figure out that your plan was not working and go back and deviate from it.[00:18:49] Speaker: Another thing I think about a lot is specifying common workflows. So we're trying to tackle a software development and I already showed like three use cases where we do [00:19:00] software development and when we. We do software development, we do a ton of different things, but we do them over and over and over again.[00:19:08] Speaker: So just to give an example we fix GitHub actions when GitHub actions are failing. And we do that over and over and over again. That's not the number one thing that software engineers do, but it's a, you know, high up on the list. So how can we get a list of all of, like, the workflows that people are working on?[00:19:26] Speaker: And there's a few research works that people have done in this direction. One example is manual prompting. So there's this nice paper called STEP that got state of the art on the WebArena Web Navigation Benchmark where they came up with a bunch of manual workflows for solving different web navigation tasks.[00:19:43] Speaker: And we also have a paper recently called Agent Workflow Memory where the basic idea behind this is we want to create self improving agents that learn from their past successes. And the way it works is is we have a memory that has an example of lots of the previous [00:20:00] workflows that people have used. And every time the agent finishes a task and it self judges that it did a good job at that task, you take that task, you break it down into individual workflows included in that, and then you put it back in the prompt for the agent to work next time.[00:20:16] Speaker: And this we demonstrated that this leads to a 22. 5 percent increase on WebArena after 40 examples. So that's a pretty, you know, huge increase by kind of self learning and self improvement.[00:20:31] Speaker: Another thing is exploration. Oops. And one thing I think about is like, how can agents learn more about their environment before acting? And I work on coding and web agents, and there's, you know, a few good examples of this in, in both areas. Within coding, I view this as like repository understanding, understanding the code base that you're dealing with.[00:20:55] Speaker: And there's an example of this, or a couple examples of this, one example being AgentList. [00:21:00] Where they basically create a map of the repo and based on the map of the repo, they feed that into the agent so the agent can then navigate the repo and and better know where things are. And for web agents there's an example of a paper called Bagel, and basically what they do is they have the agent just do random tasks on a website, explore the website, better understand the structure of the website, and then after that they they feed that in as part of the product.[00:21:27] Speaker: Part seven is search. Right now in open hands, we just let the agent go on a linear search path. So it's just solving the problem once. We're using a good agent that can kind of like recover from errors and try alternative things when things are not working properly, but still we only have a linear search path.[00:21:45] Speaker: But there's also some nice work in 2024 that is about exploring multiple paths. So one example of this is there's a paper called Tree Search for Language Agents. And they basically expand multiple paths check whether the paths are going well, [00:22:00] and if they aren't going well, you rewind back. And on the web, this is kind of tricky, because, like, how do you rewind when you accidentally ordered something you don't want on Amazon?[00:22:09] Speaker: It's kind of, you know, not, not the easiest thing to do. For code, it's a little bit easier, because you can just revert any changes that you made. But I, I think that's an interesting topic, too.[00:22:21] Evaluation and Future Predictions for Agents[00:22:21] Speaker: And then finally evaluation. So within our development for evaluation, we want to do a number of things. The first one is fast sanity checks.[00:22:30] Speaker: And in order to do this, we want things we can run really fast, really really cheaply. So for web, we have something called mini world of bits, which is basically these trivial kind of web navigation things. We have something called the Adder Code Editing Benchmark, where it's just about editing individual files that we use.[00:22:48] Speaker: But we also want highly realistic evaluation. So for the web, we have something called WebArena that we created at CMU. This is web navigation on real real open source websites. So it's open source [00:23:00] websites that are actually used to serve shops or like bulletin boards or other things like this.[00:23:07] Speaker: And for code, we use Swebench, which I think a lot of people may have heard of. It's basically a coding benchmark that comes from real world pull requests on GitHub. So if you can solve those, you can also probably solve other real world pull requests. I would say we still don't have benchmarks for the fur full versatility of agents.[00:23:25] Speaker: So, for example We don't have benchmarks that test whether agents can code and do web navigation. But we're working on that and hoping to release something in the next week or two. So if that sounds interesting to you, come talk to me and I, I will tell you more about it.[00:23:42] Speaker: Cool. So I don't like making predictions, but I was told that I should be somewhat controversial, I guess, so I will, I will try to do it try to do it anyway, although maybe none of these will be very controversial. Um, the first thing is agent oriented LLMs like large language models for [00:24:00] agents.[00:24:00] Speaker: My, my prediction is every large LM trainer will be focusing on training models as agents. So every large language model will be a better agent model by mid 2025. Competition will increase, prices will go down, smaller models will become competitive as agents. So right now, actually agents are somewhat expensive to run in some cases, but I expect that that won't last six months.[00:24:23] Speaker: I, I bet we'll have much better agent models in six months. Another thing is instruction following ability, specifically in agentic contexts, will increase. And what that means is we'll have to do less manual engineering of agentic workflows and be able to do more by just prompting agents in more complex ways.[00:24:44] Speaker: Cloud is already really good at this. It's not perfect, but it's already really, really good. And I expect the other models will catch up to Cloud pretty soon. Error correction ability will increase, less getting stuck in loops. Again, this is something that Cloud's already pretty good at and I expect the others will, will follow.[00:25:00][00:25:01] Speaker: Agent benchmarks. Agent benchmarks will start saturating.[00:25:05] Speaker: And Swebench I think WebArena is already too easy. It, it is, it's not super easy, but it's already a bit too easy because the tasks we do in there are ones that take like two minutes for a human. So not, not too hard. And kind of historically in 2023 our benchmarks were too easy. So we built harder benchmarks like WebArena and Swebench were both built in 2023.[00:25:31] Future of Agent Development[00:25:31] Speaker: In 2024, our agents were too bad, so we built agents and now we're building better agents. In 2025, our benchmarks will be too easy, so we'll build better benchmarks, I'm, I'm guessing. So, I would expect to see much more challenging agent benchmarks come out, and we're already seeing some of them.[00:25:49] Speaker: In 2026, I don't know. I didn't write AGI, but we'll, we'll, we'll see.[00:25:56] Human-Agent Interaction Challenges[00:25:56] Speaker: Then the human agent computer interface. I think one thing that [00:26:00] we'll want to think about is what do we do at 75 percent success rate at things that we like actually care about? Right now we have 53 percent or 55 percent on Swebench verified, which is real world GitHub PRs.[00:26:16] Speaker: My impression is that the actual. Actual ability of models is maybe closer to 30 to 40%. So 30 to 40 percent of the things that I want an agent to solve on my own repos, it just solves without any human intervention. 80 to 90 percent it can solve without me opening an IDE. But I need to give it feedback.[00:26:36] Speaker: So how do we, how do we make that interaction smooth so that humans can audit? The work of agents that are really, really good, but not perfect is going to be a big challenge.[00:26:48] Expanding Agent Use Beyond Programming[00:26:48] Speaker: How can we expose the power of programming agents to other industries? So like as programmers, I think not all of us are using agents every day in our programming, although we probably will be [00:27:00] in in months or maybe a year.[00:27:02] Speaker: But I, I think it will come very naturally to us as programmers because we know code. We know, you know. Like how to architect software and stuff like that. So I think the question is how do we put this in the hands of like a lawyer or a chemist or somebody else and have them also be able to, you know, interact with it as naturally as we can.[00:27:25] Redesigning Systems for Agent Efficiency[00:27:25] Speaker: Another interesting thing is how can we redesign our existing systems for agents? So we had a paper on API based web agents, and basically what we showed is If you take a web agent and the agent interacts not with a website, but with APIs, the accuracy goes way up just because APIs are way easier to interact with.[00:27:42] Speaker: And in fact, like when I ask the, well, our agent, our agent is able to browse websites, but whenever I want it to interact with GitHub, I tell it do not browse the GitHub website. Use the GitHub API because it's way more successful at doing that. So maybe, you know, every website is going to need to have [00:28:00] an API because we're going to be having agents interact with them.[00:28:03] Accelerating Progress with Agent Technology[00:28:03] Speaker: About progress, I think progress will get faster. It's already fast. A lot of people are already overwhelmed, but I think it will continue. The reason why is agents are building agents. And better agents will build better agents faster. So I expect that you know, if you haven't interacted with a coding agent yet, it's pretty magical, like the stuff that it can do.[00:28:24] Speaker: So yeah.[00:28:28] Call to Action for Open Source Contributions[00:28:28] Speaker: And I have a call to action. I'm honestly, like I've been working on, you know, natural language processing and, and Language models for what, 15 years now. And even for me, it's pretty impressive what like AI agents powered by strong language models can do. On the other hand, I believe that we should really make these powerful tools accessible.[00:28:49] Speaker: And what I mean by this is I don't think like, you know, We, we should have these be opaque or limited to only a set, a certain set of people. I feel like they should be [00:29:00] affordable. They shouldn't be increasing the, you know, difference in the amount of power that people have. If anything, I'd really like them to kind of make it It's possible for people who weren't able to do things before to be able to do them well.[00:29:13] Speaker: Open source is one way to do that. That's why I'm working on open source. There are other ways to do that. You know, make things cheap, make things you know, so you can serve them to people who aren't able to afford them. Easily, like Duolingo is one example where they get all the people in the US to pay them 20 a month so that they can give all the people in South America free, you know, language education, so they can learn English and become, you know like, and become, you know, More attractive on the job market, for instance.[00:29:41] Speaker: And so I think we can all think of ways that we can do that sort of thing. And if that resonates with you, please contribute. Of course, I'd be happy if you contribute to OpenHands and use it. But another way you can do that is just use open source solutions, contribute to them, research with them, and train strong open source [00:30:00] models.[00:30:00] Speaker: So I see, you know, Some people in the room who are already training models. It'd be great if you could train models for coding agents and make them cheap. And yeah yeah, please. I, I was thinking about you among others. So yeah, that's all I have. Thanks.[00:30:20] Speaker 2: Slight, slightly controversial. Tick is probably the nicest way to say hot ticks. Any hot ticks questions, actual hot ticks?[00:30:31] Speaker: Oh, I can also show the other agents that were working, if anybody's interested, but yeah, sorry, go ahead.[00:30:36] Q&A: Agent Performance and Benchmarks[00:30:36] Speaker 3: Yeah, I have a couple of questions. So they're kind of paired, maybe. The first thing is that you said that You're estimating that your your agent is successfully resolving like something like 30 to 40 percent of your issues, but that's like below what you saw in Swebench.[00:30:52] Speaker 3: So I guess I'm wondering where that discrepancy is coming from. And then I guess my other second question, which is maybe broader in scope is that [00:31:00] like, if, if you think of an agent as like a junior developer, and I say, go do something, then I expect maybe tomorrow to get a Slack message being like, Hey, I ran into this issue.[00:31:10] Speaker 3: How can I resolve it? And, and, like you said, your agent is, like, successfully solving, like, 90 percent of issues where you give it direct feedback. So, are you thinking about how to get the agent to reach out to, like, for, for planning when it's, when it's stuck or something like that? Or, like, identify when it runs into a hole like that?[00:31:30] Speaker: Yeah, so great. These are great questions. Oh,[00:31:32] Speaker 3: sorry. The third question, which is a good, so this is the first two. And if so, are you going to add a benchmark for that second question?[00:31:40] Speaker: Okay. Great. Yeah. Great questions. Okay. So the first question was why do I think it's resolving less than 50 percent of the issues on Swebench?[00:31:48] Speaker: So first Swebench is on popular open source repos, and all of these popular open source repos were included in the training data for all of the language models. And so the language [00:32:00] models already know these repos. In some cases, the language models already know the individual issues in Swebench.[00:32:06] Speaker: So basically, like, some of the training data has leaked. And so it, it definitely will overestimate with respect to that. I don't think it's like, you know, Horribly, horribly off but I think, you know, it's boosting the accuracy by a little bit. So, maybe that's the biggest reason why. In terms of asking for help, and whether we're benchmarking asking for help yes we are.[00:32:29] Speaker: So one one thing we're working on now, which we're hoping to put out soon, is we we basically made SuperVig. Sweep edge issues. Like I'm having a, I'm having a problem with the matrix multiply. Please help. Because these are like, if anybody's run a popular open source, like framework, these are what half your issues are.[00:32:49] Speaker: You're like users show up and say like, my screen doesn't work. What, what's wrong or something. And so then you need to ask them questions and how to reproduce. So yeah, we're, we're, we're working on [00:33:00] that. I think. It, my impression is that agents are not very good at asking for help, even Claude. So like when, when they ask for help, they'll ask for help when they don't need it.[00:33:11] Speaker: And then won't ask for help when they do need it. So this is definitely like an issue, I think.[00:33:20] Speaker 4: Thanks for the great talk. I also have two questions.[00:33:23] Q&A: Web Agents and Interaction Methods[00:33:23] Speaker 4: It's first one can you talk a bit more about how the web agent interacts with So is there a VLM that looks at the web page layout and then you parse the HTML and select which buttons to click on? And if so do you think there's a future where there's like, so I work at Bing Microsoft AI.[00:33:41] Speaker 4: Do you think there's a future where the same web index, but there's an agent friendly web index where all the processing is done offline so that you don't need to spend time. Cleaning up, like, cleaning up these TML and figuring out what to click online. And any thoughts on, thoughts on that?[00:33:57] Speaker: Yeah, so great question. There's a lot of work on web [00:34:00] agents. I didn't go into, like, all of the details, but I think there's There's three main ways that agents interact with websites. The first way is the simplest way and the newest way, but it doesn't work very well, which is you take a screenshot of the website and then you click on a particular pixel value on the website.[00:34:23] Speaker: And Like models are not very good at that at the moment. Like they'll misclick. There was this thing about how like clawed computer use started like looking at pictures of Yellowstone national park or something like this. I don't know if you heard about this anecdote, but like people were like, oh, it's so human, it's looking for vacation.[00:34:40] Speaker: And it was like, no, it probably just misclicked on the wrong pixels and accidentally clicked on an ad. So like this is the simplest way. The second simplest way. You take the HTML and you basically identify elements in the HTML. You don't use any vision whatsoever. And then you say, okay, I want to click on this element.[00:34:59] Speaker: I want to enter text [00:35:00] in this element or something like that. But HTML is too huge. So it actually, it usually gets condensed down into something called an accessibility tree, which was made for screen readers for visually impaired people. And So that's another way. And then the third way is kind of a hybrid where you present the screenshot, but you also present like a textual summary of the output.[00:35:18] Speaker: And that's the one that I think will probably work best. What we're using is we're just using text at the moment. And that's just an implementation issue that we haven't implemented the. Visual stuff yet, but that's kind of like we're working on it now. Another thing that I should point out is we actually have two modalities for web browsing.[00:35:35] Speaker: Very recently we implemented this. And the reason why is because if you want to interact with full websites you will need to click on all of the elements or have the ability to click on all of the elements. But most of our work that we need websites for is just web browsing and like gathering information.[00:35:50] Speaker: So we have another modality where we convert all of it to markdown because that's like way more concise and easier for the agent to deal with. And then [00:36:00] can we create an index specifically for agents, maybe a markdown index or something like that would be, you know, would make sense. Oh, how would I make a successor to Swebench?[00:36:10] Speaker: So I mean, the first thing is there's like live code bench, which live code bench is basically continuously updating to make sure it doesn't leak into language model training data. That's easy to do for Swebench because it comes from real websites and those real websites are getting new issues all the time.[00:36:27] Speaker: So you could just do it on the same benchmarks that they have there. There's also like a pretty large number of things covering various coding tasks. So like, for example, Swebunch is mainly fixing issues, but there's also like documentation, there's generating tests that actually test the functionality that you want.[00:36:47] Speaker: And there there was a paper by a student at CMU on generating tests and stuff like that. So I feel like. Swebench is one piece of the puzzle, but you could also have like 10 different other tasks and then you could have like a composite [00:37:00] benchmark where you test all of these abilities, not just that particular one.[00:37:04] Speaker: Well, lots, lots of other things too, but[00:37:11] Speaker 2: Question from across. Use your mic, it will help. Um,[00:37:15] Speaker 5: Great talk. Thank you.[00:37:16] Q&A: Agent Architectures and Improvements[00:37:16] Speaker 5: My question is about your experience designing agent architectures. Specifically how much do you have to separate concerns in terms of tasks specific agents versus having one agent to do three or five things with a gigantic prompt with conditional paths and so on.[00:37:35] Speaker: Yeah, so that's a great question. So we have a basic coding and browsing agent. And I won't say basic, like it's a good, you know, it's a good agent, but it does coding and browsing. And it has instructions about how to do coding and browsing. That is enough for most things. Especially given a strong language model that has a lot of background knowledge about how to solve different types of tasks and how to use different APIs and stuff like that.[00:37:58] Speaker: We do have [00:38:00] a mechanism for something called micro agents. And micro agents are basically something that gets added to the prompt when a trigger is triggered. Right now it's very, very rudimentary. It's like if you detect the word GitHub anywhere, you get instructions about how to interact with GitHub, like use the API and don't browse.[00:38:17] Speaker: Also another one that I just added is for NPM, the like JavaScript package manager. And NPM, when it runs and it hits a failure, it Like hits in interactive terminals where it says, would you like to quit? Yep. Enter yes. And if that does it, it like stalls our agent for the time out until like two minutes.[00:38:36] Speaker: So like I added a new microagent whenever it started using NPM, it would Like get instructions about how to not use interactive terminal and stuff like that. So that's our current solution. Honestly, I like it a lot. It's simple. It's easy to maintain. It works really well and stuff like that. But I think there is a world where you would want something more complex than that.[00:38:55] Speaker 5: Got it. Thank you.[00:38:59] Speaker 6: I got a [00:39:00] question about MCP. I feel like this is the Anthropic Model Context Protocol. It seems like the most successful type of this, like, standardization of interactions between computers and agents. Are you guys adopting it? Is there any other competing standard?[00:39:16] Speaker 6: Anything, anything thought about it?[00:39:17] Speaker: Yeah, I think the Anth, so the Anthropic MCP is like, a way to It, it's essentially a collection of APIs that you can use to interact with different things on the internet. I, I think it's not a bad idea, but it, it's like, there's a few things that bug me a little bit about it.[00:39:40] Speaker: It's like we already have an API for GitHub, so why do we need an MCP for GitHub? Right. You know, like GitHub has an API, the GitHub API is evolving. We can look up the GitHub API documentation. So it seems like kind of duplicated a little bit. And also they have a setting where [00:40:00] it's like you have to spin up a server to serve your GitHub stuff.[00:40:04] Speaker: And you have to spin up a server to serve your like, you know, other stuff. And so I think it makes, it makes sense if you really care about like separation of concerns and security and like other things like this, but right now we haven't seen, we haven't seen that. To have a lot more value than interacting directly with the tools that are already provided.[00:40:26] Speaker: And that kind of goes into my general philosophy, which is we're already developing things for programmers. You know,[00:40:36] Speaker: how is an agent different than from a programmer? And it is different, obviously, you know, like agents are different from programmers, but they're not that different at this point. So we can kind of interact with the interfaces we create for, for programmers. Yeah. I might change my mind later though.[00:40:51] Speaker: So we'll see.[00:40:54] Speaker 7: Yeah. Hi. Thanks. Very interesting talk. You were saying that the agents you have right now [00:41:00] solve like maybe 30 percent of your, your issues out of the gate. I'm curious of the things that it doesn't do. Is there like a pattern that you observe? Like, Oh, like these are the sorts of things that it just seems to really struggle with, or is it just seemingly random?[00:41:15] Speaker: It's definitely not random. It's like, if you think it's more complex than it's. Like, just intuitively, it's more likely to fail. I've gotten a bit better at prompting also, so like, just to give an example it, it will sometimes fail to fix a GitHub workflow because it will not look at the GitHub workflow and understand what the GitHub workflow is doing before it solves the problem.[00:41:43] Speaker: So I, I think actually probably the biggest thing that it fails at is, um, er, that our, our agent plus Claude fails at is insufficient information gathering before trying to solve the task. And so if you provide all, if you provide instructions that it should do information [00:42:00] gathering beforehand, it tends to do well.[00:42:01] Speaker: If you don't provide sufficient instructions, it will try to solve the task without, like, fully understanding the task first, and then fail, and then you need to go back and give feedback. You know, additional feedback. Another example, like, I, I love this example. While I was developing the the monitor website that I, I showed here, we hit a really tricky bug where it was writing out a cache file to a different directory than it was reading the cache file from.[00:42:26] Speaker: And I had no idea what to do. I had no idea what was going on. I, I thought the bug was in a different part of the code, but what I asked it to do was come up with five possible reasons why this could be failing and decreasing order of likelihood and examine all of them. And that worked and it could just go in and like do that.[00:42:44] Speaker: So like I think a certain level of like scaffolding about like how it should sufficiently Gather all the information that's necessary in order to solve a task is like, if that's missing, then that's probably the biggest failure point at the moment. [00:43:00][00:43:01] Speaker 7: Thanks.[00:43:01] Speaker 6: Yeah.[00:43:06] Speaker 6: I'm just, I'm just using this as a chance to ask you all my questions.[00:43:09] Q&A: Self-Improving Agents and Authentication[00:43:09] Speaker 6: You had a, you had a slide on here about like self improving agents or something like that with memory. It's like a really throwaway slide for like a super powerful idea. It got me thinking about how I would do it. I have no idea how.[00:43:21] Speaker 6: So I just wanted you to chain a thought more on this.[00:43:25] Speaker: Yeah, self, self improving. So I think the biggest reason, like the simplest possible way to create a self improving agent. The problem with that is to have a really, really strong language model that with infinite context, and it can just go back and look at like all of its past experiences and, you know, learn from them.[00:43:46] Speaker: You might also want to remove the bad stuff just so it doesn't over index on it's like failed past experiences. But the problem is a really powerful language model is large. Infinite context is expensive. We don't have a good way to [00:44:00] index into it because like rag, Okay. At least in my experience, RAG from language to code doesn't work super well.[00:44:08] Speaker: So I think in the end, it's like, that's the way I would like to solve this problem. I'd like to have an infinite context and somehow be able to index into it appropriately. And I think that would mostly solve it. Another thing you can do is fine tuning. So I think like RAG is one way to get information into your model.[00:44:23] Speaker: Fine tuning is another way to get information into your model. So. That might be another way of continuously improving. Like you identify when you did a good job and then just add all of the good examples into your model.[00:44:34] Speaker 6: Yeah. So, you know, how like Voyager tries to write code into a skill library and then you reuse as a skill library, right?[00:44:40] Speaker 6: So that it improves in the sense that it just builds up the skill library over time.[00:44:44] Speaker: Yep.[00:44:44] Speaker 6: One thing I was like thinking about and there's this idea of, from, from Devin, your, your arch nemesis of playbooks. I don't know if you've seen them.[00:44:52] Speaker: Yeah, I mean, we're calling them workflows, but they're simpler.[00:44:55] Speaker 6: Yeah, so like, basically, like, you should, like, once a workflow works, you can kind of, [00:45:00] like, persist them as a skill library. Yeah. Right? Like I, I feel like that there's a, that's like some in between, like you said, you know, it's hard to do rag between language and code, but I feel like that is ragged for, like, I've done this before, last time I did it, this, this worked.[00:45:14] Speaker 6: So I'm just going to shortcut. All the stuff that failed before.[00:45:18] Speaker: Yeah, I totally, I think it's possible. It's just, you know, not, not trivial at the same time. I'll explain the two curves. So basically, the base, the baseline is just an agent that does it from scratch every time. And this curve up here is agent workflow memory where it's like adding the successful experiences back into the prompt.[00:45:39] Speaker: Why is this improving? The reason why is because just it failed on the first few examples and for the average to catch up it, it took a little bit of time. So it's not like this is actually improving it. You could just basically view the this one is constant and then this one is like improving.[00:45:56] Speaker: Like this, basically you can see it's continuing to go [00:46:00] up.[00:46:01] Speaker 8: How do you think we're going to solve the authentication problem for agents right now?[00:46:05] Speaker: When you say authentication, you mean like credentials, like, yeah.[00:46:09] Speaker 8: Yeah. Cause I've seen a few like startup solutions today, but it seems like it's limited to the amount of like websites or actual like authentication methods that it's capable of performing today.[00:46:19] Speaker: Yeah. Great questions. So. My preferred solution to this at the moment is GitHub like fine grained authentication tokens and GitHub fine grained authentication tokens allow you to specify like very free. On a very granular basis on this repo, you have permission to do this, on this repo, you have permission to do this.[00:46:41] Speaker: You also can prevent people from pushing to the main branch unless they get approved. You can do all of these other things. And I think these were all developed for human developers. Or like, the branch protection rules were developed for human developers. The fine grained authentication tokens were developed for GitHub apps.[00:46:56] Speaker: I think for GitHub, maybe [00:47:00] just pushing this like a little bit more is the way to do this. For other things, they're totally not prepared to give that sort of fine grained control. Like most APIs don't have something like a fine grained authentication token. And that goes into my like comment that we're going to need to prepare the world for agents, I think.[00:47:17] Speaker: But I think like the GitHub authentication tokens are like a good template for how you could start doing that maybe, but yeah, I don't, I don't, I don't have an answer.[00:47:25] Speaker 8: I'll let you know if I find one.[00:47:26] Speaker: Okay. Yeah.[00:47:31] Live Demonstration and Closing Remarks[00:47:31] Speaker: I'm going to finish up. Let, let me just see.[00:47:37] Speaker: Okay. So this one this one did write a script. I'm not going to actually read it for you. And then the other one, let's see.[00:47:51] Speaker: Yeah. So it sent a PR, sorry. What is, what is the PR URL?[00:48:00][00:48:02] Speaker: So I don't, I don't know if this sorry, that's taking way longer than it should. Okay, cool. Yeah. So this one sent a PR. I'll, I'll tell you later if this actually like successfully Oh, no, it's deployed on Vercel, so I can actually show you, but let's, let me try this real quick. Sorry. I know I don't have time.[00:48:24] Speaker: Yeah, there you go. I have pie charts now. So it's so fun. It's so fun to play with these things. Cause you could just do that while I'm giving a, you know, talk and things like that. So, yeah, thanks. Get full access to Latent Space at www.latent.space/subscribe

Bishop Michael Martin joins Patrick to discuss Joy (6:02) Why are we called to rejoice by Paul? Who are people that are joyful and how are they joyful? (18:09) Break 1 Mary Lou - how I stay joyful. The ability to feel it without bypassing it. I will feel joy as deep as i feel the sorrow. Sorrow and pain enable us to feel joy. (25:55) Molly - Mass is celebrated in such a solemn manner. Seems like it should be more joyful? Slight disconnect there for me. What if we feel guilty because we don’t feel Joy? (34:32) Bob - Joy. Acronym: Serving Jesus, Other and Yourself. Just open yourself to Jesus and you will experience joy. (37:22) Break 2 How do we become more deeply rooted in the theological Virtues of Faith, Hope and Love? Joy in the hearts of those with special needs?

Wednesday's edition of THE DRIVE got kicked off with some laughs, some delicious cookies, &...Oh yeah a FIRE lol

Second Sunday of Advent Reading I - Bar 5: 1-9 Responsorial Psalm  - Ps 126 Reading II - Phil 1:4-6, 8-11 Gospel - Lk 3: 1-6 Slight truncation at ending

Joe's Premium Subscription: www.standardgrain.comGrain Markets and Other Stuff Links-Apple PodcastsSpotifyTikTokYouTubeFutures and options trading involves risk of loss and is not suitable for everyone.

Jason and Nick open with some news including earthquakes, Florida (wo)Man, and airplane farts. Then they are joined by professional sex counselor Savannah Stuart to discuss all of our fornication struggles. Bonus episodes available at patreon.com/jasondick or on Spotify at https://creators.spotify.com/pod/show/jason-dick/subscribe For more on Savannah check out https://www.savannahsextherapy.com/

You can actively pursue creative breakthroughs by taking deliberate breaks and trying new activities that shift your mindset from stuck to free-flowing. Creative breakthrough is an overflow state—it's living in higher energy and having more to give of yourself, to your art, to the world.  Living in a state of breakthrough requires creating space and avoiding the pitfall of constant busyness. Documenting and writing down your artistic experiences isn't just about chronicling events—it's a fundamental practice for opening yourself up to breakthroughs and keeping creativity alive.  Revisiting past works, surrounding oneself with inspiring objects, and writing down creative experiences are also key strategies for maintaining a continuous creative state. The feeling of that constant creative flow that comes from simple yet profound practices and they help you stay aligned with your intuitive self.  Whether it's choosing to move past feelings of being stuck, setting up a spacious and comfortable environment, or collaborating with others, this episode is packed with insights that will empower you to embrace creativity as a continually attainable state. Slight shifts in perspective and habitual practices lead to a thriving overflow state of high energy and creativity.  Listen if you are interested in... Creative blocks arise from positive overwhelming activities [03:16] Baby sea turtles as a metaphor for moving past challenges and obstacles [09:10] Create without overthinking to give the best results [11:55] Ideas for creative exercises focusing on colors and blind contour drawing [14:08] Creating together shifts perspective and inspires creativity [19:56] Approach life's challenges playfully to get perspective [22:48] Sharing and documenting helps overcome creative blocks [26:41] Create space for reflection and play to avoid feeling stuck [30:06] Resources Mentioned Shazam  Bloom Connect with Nicholas Wilton and Art2Life Get the Free COLOR TIPS PDF here Follow the Sunday Art2Life Vlog here Follow Nicholas Wilton's Art on Instagram Follow Art2Life on Instagram Subscribe on Youtube Subscribe to Art2Life onApple Podcasts, Spotify, Google Podcasts

Thanksgiving episode with the guys breaking down Thanksgiving as well as what they're thankful for! Slight mention of Bloodline Brawl as well.... Artist - Adam SandlerSong - Thanksgiving Song

Raven's podcast https://open.spreaker.com/2wipp5rLPAxXK2cM6Make a Donation to Forbidden Knowledge News https://www.paypal.me/forbiddenknowledgenehttps://buymeacoffee.com/forbiddenReconnect to Everything with BrainsupremeGet 25% off your order here!!https://brainsupreme.co/discount/FKN15Subscribe to Cory Hughe's "Bloody History" substackhttps://bloodyhistory.substack.comSign up for the IMT crypto community Imt.networkBook a free consultation with Jennifer Halcame Emailjenniferhalcame@gmail.comFacebook pagehttps://www.facebook.com/profile.php?id=61561665957079&mibextid=ZbWKwLSick of having mediocre health? Transform your health and vitality with Christian Yordanov's program. Learn more and book a free intro call here (mention FKN at time of booking and he will have a special gift for youhttps://christianyordanov.com/fkn/Watch The Forbidden Documentary: Occult Louisiana on Tubi: https://link.tubi.tv/pGXW6chxCJbC60 PurplePowerhttps://go.shopc60.com/FORBIDDEN10/or use coupon code knowledge10FKN Link Treehttps://linktr.ee/FKNlinksForbidden Knowledge Network https://forbiddenknowledge.news/ Sign up on Rokfin!https://rokfin.com/fknplusPodcastshttps://www.spreaker.com/show/forbiddenAvailable on all platforms Support FKN on Spreaker https://spreaker.page.link/KoPgfbEq8kcsR5oj9FKN ON Rumblehttps://rumble.com/c/FKNpGet Cory Hughes Book!https://www.buymeacoffee.com/jfkbookhttps://www.amazon.com/Warning-History-Cory-Hughes/dp/B0CL14VQY6/ref=mp_s_a_1_1?crid=72HEFZQA7TAP&keywords=a+warning+from+history+cory+hughes&qid=1698861279&sprefix=a+warning+fro%2Caps%2C121&sr=8-1https://coryhughes.org/Johnny Larson's artworkhttps://www.patreon.com/JohnnyLarsonYouTube https://youtube.com/@fknclipspBecome Self-Sufficient With A Food Forest!!https://foodforestabundance.com/get-started/?ref=CHRISTOPHERMATHUse coupon code: FORBIDDEN for discountsThe FKN Store!https://www.fknstore.net/Our Facebook pageshttps://www.facebook.com/forbiddenknowledgenewsconspiracy/https://www.facebook.com/FKNNetwork/Instagram @forbiddenknowledgenews1@forbiddenknowledgenetworkXhttps://x.com/ForbiddenKnow10?t=uO5AqEtDuHdF9fXYtCUtfw&s=09Email meforbiddenknowledgenews@gmail.comsome music thanks to:https://www.bensound.com/Become a supporter of this podcast: https://www.spreaker.com/podcast/forbidden-knowledge-news--3589233/support.

Watch clips on YouTube! Subscribe to the SPEAK YOUTUBE CHANNEL (00:00) Did Aaron Rodgers and the Jets beating the Texans prove anything last night? (18:13) Will the Lions make a statement vs the Packers? (28:20) How should Dak Prescott respond to a slight against him on Micah Parsons' podcast (39:04) Smart to criticize Josh Allen before playing him? (43:49) Speak NFL Picks Learn more about your ad choices. Visit megaphone.fm/adchoices

This week we dive into The Substance! Which scene made Korey faint in his seat, how many people left the theatre at my showing, & which character you should be for Halloween 2024. Plus… A Clown Is Born! Warning: Spoilers ahead! To learn more about listener data and our privacy practices visit: https://www.audacyinc.com/privacy-policy Learn more about your ad choices. Visit https://podcastchoices.com/adchoices

Charlie is reporting from the RNC in Milwaukee, Wisconsin, and he's joined by Dr. Ronny Jackson, Erik Prince, Jack Posobiec, and Kari Lake to discuss one of the most extreme security failures in history — the attempted assassination of President Trump. He asks hard questions like: Who allowed this to happen? Who will be held responsible for it? Did a slight turn of Trump's head save his life? And more.Support the show: http://www.charliekirk.com/supportSee omnystudio.com/listener for privacy information.